|
|
 |
|
|
Pages: 1
XP Home Boot Problems
(Click here to view the original thread with full colors/images)
Posted by: TwiztidJuggalo
OK it all started with an error message saying that windows cannot boot becuase the file hal.dll is missing or corrupted. At first I tried using a WinXP Pro laptop cd (the only WinXP cd the people had) to use the recovery console to expand HAL.DL_ from the cd into the System32 directory. That did not work. Then I obtained my copy of the WinXP Home cd and used the repair installation option. It went through almost flawlessly, the little flaws were easily fixable, and seemed like it would work. Here's the weird part: when it repaired and restarted, I now get two options at the boot menu, and they are both for WinXP Home Edition, if I choose one I get the same old hal.dll error message above, and if I choose the other one I get as far as the WinXP Boot screen where it shows the logo and the side-scrolling bar at the bottom. Afterthat the comp flashes the WinXP setup screen saying that "Setup is being restarted" ("retarded" is more like it). It then restarts the computer and goes into a restart loop at the same screen.
What the hell?
-matt
Posted by: thtadthtshldntb
the question is why was that hal.dll corrupted?
Perhaps that original install was fragged.
hal stands for hardware abstraction layer. This is the precompiled set of files and drivers which the windows system uses to access the hardware. Direct hardware access in an NT compliant program is a nono.
This link is more informative as to what you should have done. Essentially what you did was restore a "default hal" that came on the cd. Whereas the actual hal.dll needs to be built or rebuilt as needed.
http://www.kellys-korner-xp.com/xp_haldll_missing.htm
Posted by: TwiztidJuggalo
 Quote:
|
Originally Posted by thtadthtshldntb
the question is why was that hal.dll corrupted?
Perhaps that original install was fragged.
hal stands for hardware abstraction layer. This is the precompiled set of files and drivers which the windows system uses to access the hardware. Direct hardware access in an NT compliant program is a nono.
This link is more informative as to what you should have done. Essentially what you did was restore a "default hal" that came on the cd. Whereas the actual hal.dll needs to be built or rebuilt as needed.
http://www.kellys-korner-xp.com/xp_haldll_missing.htm |
But the computer never had this problem. If this dll file was messed up in the first place as it is now the comp would never had run. I failed to mention that the computer was up and running for a while now, probably around a year. And I actually did do one of the things on that page. Under the Updated area, option 2. I did that exact thing. I expanded the exact same way.
-matt
Posted by: thtadthtshldntb
No, that's not what I meant. (Incidently we have the same name)
I meant, and should have used proper tense, perhaps that original install has become fragged, and this is what caused the symptom of the corrupter hal.
Perhaps that hd has suffered some damage.
Anyhoot, I recommend performing a full install with a reformat.
You basically have two windows installs on one harddisk, a corrupted one and an incomplete install. If you need to recover data off the disk, slave it to another computer then delete all partitions and go with a blank install, if you still have mysterious errors like corrupted files you probably have a bad hard disk or a bad disk controller.
|
|
|
|
|
