ENVY 1 CPU on Windows Issue

[andit]

ENVY has an issue with Window on multiple CPU machines. These are starting to become increasing hard to find. Since its been outstanding as an issue for many years I'm not expecting it to be suddenly fixed, but surely someone needs to start thinking about it.

In the meantime, can anyone tell me if a Windows Virtual Machine (VmWare, VirtualBox, etc) configured to have only 1 CPU but running on a multiple CPU machine will be subject to the same windows bug and manager corruption issue?

[Eric Clayberg]

ENVY has an issue with Window on multiple CPU machines. These are starting to become increasing hard to find. Since its been outstanding as an issue for many years I'm not expecting it to be suddenly fixed, but surely someone needs to start thinking about it. In the meantime, can anyone tell me if a Windows Virtual Machine (VmWare, VirtualBox, etc) configured to have only 1 CPU but running on a multiple CPU machine will be subject to the same windows bug and manager corruption issue?

ENVY does not have an issue with multiple CPU machines using Windows 2000 or later. See the VAST FAQ...

There are no known current issues with multiprocessor boxes under any recent version of Windows since Windows 2000. Under much older versions of Windows such as Windows NT, repository corruption was observed on multiprocessor machines. It was never reproducible or diagnosed, but speculation at the time was that the problem was a file sharing bug in Windows itself (that has likely been long since corrected). As far as we know, no fix is necessary under any recent version of Windows.

As long as you us the -mp switch, you should not have any problem using EMSRV under any recent version of Windows. We have had no reports of manager corruption in the past 5 years or more. Many customers are running with the -mp override.

[andit]

I sit corrected.
Thanks Eric.

[wembley]

In addition, if you don't like using the -mp commandline switch, you can run in a single CPU VMware session.