HAL.dll missing or corrupt

G

Guest

I am running Windows XP Pro. I booted the other day and got through all
system checks and when windows should have started I received a message
"Hall.dll missing or corrupt". I searched for a resolution and found I could
repair the file from Windows XP Pro install disk. I booting from install
disk and system freezes at blue screen "Windows Setup" in the top left
corner. I am not sure what my next step should be. Any help would be
appreciated.
 
J

John

Pytheas said:
DOH, yes it is HAL.DLL. But how do Install to alternate location if windows
setup hangs at blue screen? Literally, windows setup stalls just as it
starts. I tried hitting all the F keys at "Inspecting hardware…." to no
avail. All that happens is “Inspecting Hardware….â€, to blue screen with
“Windows Setup†in top left corner. That is as far as I get. :( From what I
have read is that windows uses HAL to determine configuration of computer.
If windows setup uses this file and it is corrupt, how could I repair using
windows install disk?

:

You boot from the XP disk *not* the hard drive. He is saying to add a
2nd instance of XP on the computer. Once the 2nd install is up and
running replace the corrupt file on the original XP. Actually a repair
install makes more sense to me. But either way you boot from the *XP
disk* not the hard drive.

John
 
J

John

John said:
You boot from the XP disk *not* the hard drive. He is saying to add a
2nd instance of XP on the computer. Once the 2nd install is up and
running replace the corrupt file on the original XP. Actually a repair
install makes more sense to me. But either way you boot from the *XP
disk* not the hard drive.

John

Opps sorry, I replied to the wrong message ;(

But now that I look at what I replied to do you need a driver to access
your hard drive? The hit F6 and supply 3rd party drivers from floppy trick?

Sorry,
John
 
G

Guest

OK, here is where I am. After messing with my computer for an extended
period of time, I have determined that the issue of windows freezing up at
startup is bad memory. I downloaded a memory tested (memtest86) and
determined that 1 stick is completely gone and the other has errors. Thanks
for the help.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top