Link to home
Start Free TrialLog in
Avatar of neomage23
neomage23Flag for United States of America

asked on

Manually change HAL (hal.dll) and Processor support in Windows 2000 and Windows 2003

Hello Experts!@

Background: I've been converting our corporate infrastructure from "physical machines" to "virtual machines" (P2V) and for the most part this has been going well. However, I ran across and incident with an NT 4.0 Terminal Services Edition machine where the CPU was maxed out a 100% on the new/migrated virtual machine. After some research I found this article: http://support.microsoft.com/kb/156358 and was able to follow the procedure and change certain files and now the CPU runs at a normal rate.

So, the question is this:

Does the procedure in this KB Article (http://support.microsoft.com/kb/156358) apply to Windows 2000/2003 servers as well? If not can you point me to the procedure to follow?

Thanks!

-neo
ASKER CERTIFIED SOLUTION
Avatar of sirbounty
sirbounty
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am amazed that you got the P2V to work with NT 4 SMP,because it will generally give you an error saying it is unsupported.

As for W2kX and above,P2V should handle the issue by creating a new virtual HAL.

So I wouldn't worry about it.