Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are in the situation that we need to migrate our windows 95 systems (i know, that is so last century ). There is no hardware for a reasonable price available to run our windows 95 systems. So we are extending the overdue lifetime of it, by making them virtual.

Now we see that VMware reports 100% CPU utilization of a windows 95 VM. This is because windows 95 doesn't know how to manage a CPU. For this reason software like rain or Waterfall, or CPUCool are introduced. The they are sending a HLT instruction to the CPU. This causes the CPU to halt and wait for new triggers to work.

I've tested the mentioned programs in the VM, but they don't work, but generate errors.

anyone has a valid workaround, solution ??

btw. I know that the best solutiuon is to replace the windows95 with windows XP. But in our situation that will take at least 5 years. Our windows 95 systems are running factory process control software.....

share|improve this question
how does support for this control software work as the OS was OEL'ed a long time ago? – Chopper3 Feb 18 '10 at 9:29
also have you installed the vmtools into the VM? what version of ESX are you using? – Chopper3 Feb 18 '10 at 9:36
"There is no hardware for a reasonable price available" - I bet I could go to the tip and get some for free – Mark Henderson Feb 18 '10 at 10:18
@Chopper3 - "how does support for this control software work as the OS was OEL'ed a long time ago?" i didn't get what does it mean, unfortunately. Could you rephrase it? – brtlvrs Feb 18 '10 at 15:51

Windows ME has HLT support -- does your software run under that OS?

Windows ME is still the Windows 95 kernel underneath, technically, so I suspect it might run your software fine.

share|improve this answer
I do believe this is the first business case I have ever seen for ME, well done! – Greg Askew Feb 18 '10 at 12:13
Another is if you like your mouse pointer to not flicker like it does in Windows 95-98 ^^ – Oskar Duveborn Mar 8 '10 at 9:58 is what I followed when I needed to create a windows 95 virtual machine.

share|improve this answer

The issue is that win95 can't manage the CPU. For that reason programs like CPUIDLE or DOSIDLE were invented.

DosIdle will work in a virtualized dos 6.22 enviroment. CPUIDLE doesn't work in a esx4.0 win95 VM. It generates general exeption errors.

The workaround for now is to limit the CPU resources. When you check the performance graph in VMware, Vmware displays that the win 95 vm claims 100% of the allocated CPU but uses 40% of it.

I'm pesimistic about finding a solution... but if anyone has one..... :-)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.