• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help!! I installed XP on my new box, now I get errors!

T

Thanks2C

Member
I just installed XP on my new box that I built (Athlon XP), and as I was installing some SB Audigy drivers, when it was finished it rebooted and now Windows XP won't boot. I get the following error:

Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll
Please re-install a copy of the above file.

Once again I'm using Windows XP on NTFS.

Any help on rectifying this situation would be greatly appreciated. I really just haven't had my luck today, hehe.

--Shawn

This is the place to discuss the latest computer hardware issues and technology. Please keep the discussion ON TOPIC, and covering computer hardware ONLY.


AnandTech Moderator


 
I have an SB Live! and had no problems installing WinXP, Windows didnt even let me install anything it had the SB drivers already.
Try letting WinXP install all the drivers that it can on its own(save yourself the head ackes).
 
I am not positive as to what the hal.dll does, but I am assuming it institutes the HAL (Hardware Abstraction Layer). It is something used to prevent GPFs (General Protection Faults) and other hardware related errors. I say, try reinstalling it. Or, at least try to pull the dll off of the CD. If all else fails, install Windows 2000. I like solutions that are a bit more tried and true. =)
 
Okay, here's another dumb question. How do you make a boot disk in XP? I have XP on my other box. I know how to make a boot disk in 98, just not XP...
 
cant use dos to access ntfs--at least that's what i think.
one question though--is your system OCed?
 
that hal.dll error is a bitch.

anyway, there are so many incidents in MS's knowledge database. I suggest you look there to see stuff.
 


<< i had that same problem.......I just reset the cmos, then turned off the onboard sound and no problems >>



Ah..

Thanks2C, Did you disable any onboard sound?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top