Sorry for the tardy reply but I only receive a daily synopsis from this group.
If you need help with any aspect of running the NBEMS suite (fldigi, flarq, wrap) you will receive a more timely response by posting your questions and problems on the yahoo group dedicated to it's support: nbems...@yahoo.com You should be prepared to enumerate what version of each of the programs you are testing and what hardware you are using for the test. You will probably be asked to provide further information regarding the type of transceiver control being used on both ends of the qso. The person assisting will also ask for the timing settings and what mode you are using for the flarq tests. If you have programming skills that complement your operating skills you have the opportunity to contribute to making any or all of these programs better for yourself and the amateur radio community as a whole. All of the NBEMS programs are General Public License (GPL). That means the source code is ALWAYS available to you. Contributing in this way is far more noble than simply grousing about failures that may or may not be attributed to the software. Binary and/or executable files are simply a convenience for those who are not able to build the application from source. Some mention was made about receiving an OS message during program startup. I have only seen the message on VISTA and it is almost always associated with a change in h/w between a shutdown and subsequent restart of fldigi. Did you unplug either your microphone, line-in, or speaker out from your sound card? If you did then VISTA reports that the sound system is not available. Fldigi is trying to access the sound system and fails (at the OS level) to do so. There is probably a way to avoid this problem, but the Linux programmers who work on fldigi are not aware of how to do so. Here is an opportunity for a Microsoft skilled programmer to lend a hand (see para above). 73, Dave, W1HKJ
