Dmitri Besedin Member
Posts: 934 From: Moscow Registration: Apr 2003
| | posted April 24, 2006 07:20 PM | profile edit reply w/quote IP | nospam This is interesting. I have found that RMClock uses excess CPU only if the DOS box running "dir /s c:\" is viewed normally. If I minimize it, RMClock uses very little CPU. When RMClock is in high-CPU mode, its first thread uses almost all the CPU, and often can be found executing code at RMClock.exe+0x1fedf. I don't have a debugger handy to determine what that code does, but I am using RMClock 2.0, so I hope you can figure it out.
OK, this info should be helpful. As I already said, I wasn't able to reproduce this problem, but anyway, I'll check out what kind of code is located at this address.
Finally, I have located another audio glitching mechanism unrelated to RMClock: the "Power Save Mode" setting for my Broadcom WiFi chipset. I had it set to "fast". When I set it to "disabled", the dropouts disappeared (except when running something that displays lots of text in a DOS box).
Once again, these all are the interrupt handling problems, that is, the hardware problems  |
|