Ref: Your note of Sat, 10 Dec 94 16:05:01 GMT
Alan,
CT runs OK under OS/2 2.0 or later, but the CW timing problem is still
there. However, it is not nearly as bad as the situation you describe
under Windows. It seems to be somewhat CPU dependent. On a 386SX,
running CT under OS/2 in CW mode is very choppy. On a 486-66 or
faster, it is much better, but still not perfect. The CW will sound
funny if you move windows around on the desktop or get the CPU busy
doing some other task at the same time.
Phone contesting with the DVP under OS/2 works just fine as long
as you use IRQ5 or IRQ2 and no other devices are using those IRQs.
OS/2 uses IRQs for smooth multitasking during printing, so avoid using
IRQ 7 with the DVP under OS/2. You do not need any special OS/2
device driver for the DVP. Just run your DVPTSR and COMTSR drivers in the
OS/2 DOS session before firing up CT, just as you would under vanilla DOS.
OS/2 lets you play some neat games with CT, such as firing up two
independent versions and connecting them together in a "network" (e.g.,
connecting COM1 to COM2 on the same machine). I used this trick for testing.
In general, everything works with CT under OS/2 except the CW timing is off.
I know K1EA wants to make an OS/2 32-bit Version of CT. He just needs
to find the time. In the mean time, I have been experimenting with
WriteLog for Windows by W5XD. Wayne designed an outboard one-chip
keyer (takes some time to build), that solves the CW timing problem
quite nicely. It even has paddle input. CW with WriteLog for Windows
running under OS/2 sounds fine (if you use the outboard keyer). CT
for DOS could also support this keyer, and that would solve the
problem (and also give you the long awaited paddle input feature).
However, few people have time to build such a keyer from scratch, and
K1EA has to make modifications to CT to support it.
Weird idea: use the timing chips in the DVP (and the PTT line) to key
accurate CW under multitasking operating systems. What say Ken, too
crazy to work?
73,
Bob, N6TV
|