Guys, Jim is correct. A PC running windows and most contest/ham
programs will key the K2 (or any other CW-capable rig) very nicely. But
only if the computer is fast enough to handle all its tasks AND the CW
functions as well. Don't expect an old slow Pentium 3 system to handle
it very well. I use a 1.7 GHz Celeron running N1MM logger with great
success (except for RFI problems...). If you are trying to do this with
a 350 MHz P3 system, then it is definitely time to trade up.
At the same time, it is good to bug the software authors to add support
for the K2's KY command. This command is also supported in newer
Kenwood transceivers, so adding it for us also gets a lot of other
rigs.
On May 11, 2005, at 12:30 PM, Dan Barker wrote:
That's silly! Modern computers are WAAAAAY more capable than that.
Someone
in charge of one of these keying programs needs to look into the
Win-32 API
for starting threads with differing priorities. I'm not one of those
programmers, but I KNOW you can make the opsys dispatch you often
enough, if
you "promise to be good" (ie, not loop<g>).
Dan / WG4S / K2 #2456
<snip>
... Windows NT based OS (NT/2000/XP), the cw timing problem is an
artifact
of Windows.
</snip>
- Jack Brindle, W6FB
------------------------------------------------------------------------
---------------------
_______________________________________________
Elecraft mailing list
Post to: [email protected]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
