Before this starts a long thread on the evils of running CT in a Windows
shell, I suggested that K4OJ do that only to see if his internal speaker
problem somehow had something to do with Windows (very unlikely but I was
running out of suggestions). What he did not re-copy was a couple of
sentences from me saying it is never a good idea to run CT in a Windows
shell and to only do this one time as a test. If he has been a subscriber
to this reflector for very long he already knows to run CT in DOS mode only.
So he's innocent. I'm still guessing his problem is that his internal
speaker has come unplugged from the motherboard but I've not heard back from
him.
As I wrote in one long thread last year where several users swore they had
no problem running CT in a Windows shell and never had it lock up in a
contest -- "they are truly blessed". For the rest of us in the real world
of sudden unexpected IRQ and port conflicts we run CT in a Windows shell
only at great risk and probable disaster.
73
Gary, W0TM
gary@W0TM.com
@9,000 feet 20 miles West of Vail, Colorado
Please visit my Web site www.W0TM.com to view pictures of my station and the
mountains of Colorado
--
WWW: http://www.k1ea.com/
Submissions: ct-user@contesting.com
Administrative requests: ct-user-REQUEST@contesting.com
Problems: owner-ct-user@contesting.com
|