Your comments remind me recently of a similar problem I had when
attempting to do some PC based real time data collection. My
problems were the result of a Windows background program called
PCHSchd.exe. Run a program called MSCONFIG.EXE which is located
in your WINDOWS\SYSTEM directory. Then look under the STARTUP tab
for an entry called PC Health. If this item is checked then
uncheck it and reboot PC. The PC Health program and all its
background work has been the topic of many discussions in the
PC groups. The program is absolutely not needed. This program
has some algorithm that senses activity/inactivity and when it
decides to activate the hard disk runs continuously. The process
is interruptable after a delay period of a few seconds but that is
too late. Hope this fixes your problem.
73,
Larry Benko, W0QE
K6RB wrote:
>
> Here are my observations about the erratic CW problems on my end. They occur
> randomly and infrequently. They are always associated with hard-disk
> activity in my laptop, but not the writelog "save" function. My gut tells me
> it's not an RFI problem - when I've had RFI screwing up a keyer, it was
> frequent. I probably won't spring for the $215 for a W5XD keyer because it
> doesn't happen enough to me to warrant the expenditure, and I can't see
> myself ever doing SO2R operation. But from the number of people who seem to
> be having this problem, and the variety and speeds of computers involved,
> I'd say it is some issue with Windows and not speeds or feeds. It also
> happened with another Windows program I've used, so I don't think it's a
> WriteLog problem, either.
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
|