EMpulse logger

I have a PC104-Plus based data logger with custom acquisition software written in C (C++?). The original configuration used a power hungry Pentium SBC along with a high speed 12 channel ADC (24DSI12). I am attempting to run the acquisition software on a new platform using a low power VortexDX3 CPU. I've built a real time OS using TinyCore Linux (2.6.33.3), I've built the kernel module for the 24DSI12, I've got the time synchronization working with the GPS NMEA and PPS strings (with chrony, gpsd and gpspipe) and I've now compiled the acquisition code which consists of two programs, mt_adc and mt_logger. As I understand it, mt_adc is responsible for taking care of the ADC, sampling data continuously at 200 kHz, and then mt_logger is responsible for catching the output of mt_adc, filters and decimates to create (and save) continously sampled data (at 20 kHz output rate) but then also triggering and saving any "tranient" events that may occur, part of mt_logger is a GLADE GTK2.0 GUI where sample rates, window lengths, channel numbers, etc., can be changed, right now when I execute a startup script to both start mt_adc and mt_logger programs, mt_adc starts okay (I think) and the GLADE GUI comes up, but it's totally frozen, none of the little tabs or buttons in the GUI are responsive and the program seems to be stuck in a while loop, or waiting for a callback that never happens ?? I've tried to use gdb to debug where the problem is (assuming it's in mt_logger) but I haven't been successful so far, I think I need the help of an expert else this is likely to take me another 6 months, it's taken me about that long to get to where I am right now ! ! My original developer has unfortunately been unresponsive as well, so I'm on my own unfortunately with this. I would be interested to hear your comments and obtain a quote as to what you think it might cost to solve this problem for me. Thanks, David