G
Guest
I've seen a number of posts referencing this message.
I am installing XP Pro (Upgrade cd) on a new Western Digital hard drive. I've got the WD Data Lifeguard v.11 software that came with the hard drive and nothing else. I ran the installation, copied all the files, rebooted, and got the Hal.dll error message.
I have tried using the XP Installation Repair utility to expand the HAL.DL_ from the installation cd and I get a message that HAL.DLL can't be created at C:\windows\system32. I tried copying a HAL.DLL from a W2K machine and was able to copy it in and overwrite the existing file, but I still get the "Corrupt or missing" message when I try to reboot.
I have tried rebuilding the boot.ini and everything else I've seen recommended in these newsgroups, and I'm stymied. My last option at this point is to try a newer hal.dll from my own XP computer, and/or installing from a different (full install) cd. I'm confused about what could be causing this. The computer I am trying to install is a couple of years old, but it's plenty of system resources, nothing but mouse, monitor, and keyboard are connected to it
Based on all the messages here that talk about this message, I'm surprised Microsoft.com hasn't written a paper discussing it. Might their Support Group be able to asist with this? Could this be corrected in XP SP1?
I'll appreciate any assistance anyone can offer.
I am installing XP Pro (Upgrade cd) on a new Western Digital hard drive. I've got the WD Data Lifeguard v.11 software that came with the hard drive and nothing else. I ran the installation, copied all the files, rebooted, and got the Hal.dll error message.
I have tried using the XP Installation Repair utility to expand the HAL.DL_ from the installation cd and I get a message that HAL.DLL can't be created at C:\windows\system32. I tried copying a HAL.DLL from a W2K machine and was able to copy it in and overwrite the existing file, but I still get the "Corrupt or missing" message when I try to reboot.
I have tried rebuilding the boot.ini and everything else I've seen recommended in these newsgroups, and I'm stymied. My last option at this point is to try a newer hal.dll from my own XP computer, and/or installing from a different (full install) cd. I'm confused about what could be causing this. The computer I am trying to install is a couple of years old, but it's plenty of system resources, nothing but mouse, monitor, and keyboard are connected to it
Based on all the messages here that talk about this message, I'm surprised Microsoft.com hasn't written a paper discussing it. Might their Support Group be able to asist with this? Could this be corrected in XP SP1?
I'll appreciate any assistance anyone can offer.