[UK-CONTEST] N1MM and Microkeyer

[Frank Hunter]

John and Chris thanks for your replies. As promised I'll outline the 
problems I've recently been experiencing. I have both a Microkeyer and a 
CW keyer and both have until now performed flawlessly with N1MM and SD 
with either my laptop or desktop computer (the desktop was recently 
upgraded) both are now AMD 64 cpu based, the desktop has a dual core 
cpu. The problems first occurred when activating GB2MGY onboard the SS 
Nomadic using the laptop, CW keyer and SD. At the time we put it down to 
dodgy "mains", power was supplied by a shonky generator and we even lost 
power during the event. The problem manifests itself by truncating 
either or both the exchange and call sign and ultimately the keyer 
becomes unresponsive to the paddle ie to all intents and purposes it's 
dead. Before reaching the dead stage temporary relief can be had by 
exiting and then relaunching urouter upon doing which it seems to flush 
its buffer and send what should have been sent previously(!) but at this 
point the speed pot ceases to work allowing a maximim speed of 30wpm 
although it can still be altered via the log entry window. Now you have 
a working keyer again albeit temporary until it chucks the next wobbler 
which in all likelihood is worse than the previous one perhaps needing 
both urouter and N1MM rebooted and finally leading to an unresponsive 
keyer at which point the only option is to remove power and restart it. 
I need hardly tell you how infuriating or embarrassing this is during a 
contest, it happened when G3YMC called me on 40m and during numerous 
pileups, BTW it has yet to happen when operating search and pounce style.

I have followed the advice given on the relevant relectors ie I removed 
all usb devices and made sure the keyer was the only thing on a root 
hub, heck I even tried it off an external powered hub but it still 
crashed! In desperation I even rolled urouter back to a previous version 
with no luck. Frankly I'm at a loss what to do next. Has anyone else 
experienced similar problems?

73, Frank GI4NKB

--