System is a AMD 64. Vmware version is 1.0.4. I have a system that runs a win98 guest under red Hat Enterprise 5. This is the only guest on this machine and the only other thing running is the Linux desktop. While just running the win98 guest the clock stays fairly close to normal. As soon as a dos program is run(under the 98 guest), the clock goes haywire. I watched the second hand when opening the dos session and it goes 10x normal.

As soon as the dos session is closed the clock goes back to normal. As I understand it, from reading quite a few posts about clock speed and the timer PDF from here, the dos session is eating up a lot of the clock resources from the system and that's why the clock speeds up. I have run the timer test listed elsewhere here and found that the interrupts for the timing process is at 10k.

I have tried the clock=pit setting to no avail. Is there something else I can look for? Or something else I can try? Just as an FYI we have other linux desktops running the same program without any problems. When runniing the timer count script on these machines they are showing up as 3k interrupts. I assume that's why they are not having the problem.

If I have to I could probably recompile the kernel with the 100/1000 htz setting. But would like to know if there is something else I can try first.

Thanks