Since Virtual PC is not designed for multi-processor/multi-core computers, I had to enter this command to make sure Virtual PC 2007 always starts on CPU processor 0:
#VIRTUAL PC 2007 SOFTWARE#
StartAffinity is a freeware tool that is designed to start software by restricting it to certain CPU affinity masks. Now to overcome this limitation, I downloaded a utility called Start Affinity. And now since newer computers with multi-core processors are replacing older computers with single core processors, the fix would be to set the Virtual PC.exe CPU affinity to a single core before any virtual machines are started. When Microsoft Virtual PC was a Connectix product it was mean to run on a single CPU or single core (up to 4.29 GHz). I've learned that operating systems such as Windows for Workgroups 3.11, Windows 95 and even Windows NT 3.51 won't work correctly leading up to long latency, disk and data corruption errors to a point where the operating system will not even boot at all. I solved it when I stumbled upon this article regarding running Virtual PC 2007 on multi-processor and/or multi-core processors. Is there a permanent solution to overcome this issue? I'm sorry if my comment clearly didn't make since or that I wasn't being all that specific, but I'm tired and I'm heading for bed soon.
It seems to me that Windows NT 3.51 guest under Virtual PC 2007 doesn't even like multiple cores. Other OSes such as MS-DOS, FreeDOS, Windows 3.0, Windows 3.1 and OS/2 Warp all work without problems. Once I close VirtualPC 2007 and restart it, VPC gets defaulted to use four cores which in retrospect that causes data corruption on the Windows NT 3.51 guest to appear.
#VIRTUAL PC 2007 INSTALL#
By setting the Processor Affinity to use only CPU 0 under Windows NT 3.51, I was able to install Windows NT 3.51 successfully. For instance, I used Process Explorer and right =click Virtual PC.exe, set the Processor Affinity to only use CPU 0.
The temporary solution would be to allow Virtual PC 2007 process to use only one processor. If this message reappears,Ĭontact your system administrator or technical support group. Restart and set the recovery options in the system control panel The header checksum does not match the computed checksum. The image advapi32.dll is possibly corrupt.
0 kommentar(er)
