>W9CF, Kevin, wrote:
>>It sounds to me like some other TSR or something has grabbed the clock
>>interrupt in such a way that TR can't find it.
>The offender is RighTime, which does a really good job of making the
>computer clock get super-accurate.
I use a similar DOS TSR called Clock to keep the clock on time, and
haven't seen any problem yet up to v. 6.34. Thanks for the heads-up,
TSR conflicts are worth watching for.
I recently had to replace the CMOS battery on a motherboard, it's worth
having the part number or even a new spare for older computers; the
first symptom was clock drifting way off time and date while the shack
computer was just sitting there off for weeks at a time.
Dave, W6NL
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|