Thread: Hal32.dll (error) Help quick
January 25th, 2003, 06:37 AM #1
Hal32.dll (error) Help quick
Just received a Hal32.dll (error) on boot. System won't boot. It said to install a copy of the file to correct the problem. So I go and copy the file (win XP) from my other pc and run in dos mode:
a:/copy hal32.dll c:/windows/system32
It tells me "Access denied"
How do I correct this. I ran chkdsk /R and it said "unrecoverable"
January 25th, 2003, 10:14 AM #2
Never mind, I blew away the OS and saved as much as I could. Not sure why I got the Hal32.dll error? Oh well. Hard drive checked out ok. I tested it, and no bad sectors???? We'll see....
January 26th, 2003, 01:42 AM #3
January 26th, 2003, 06:14 AM #4
Thanks for the links!!! But, the problem was I couldn't copy the Hal32.dll file from the floppy to the windows/system32 directory. All it said was access denied. That's the part I was confused on....
January 26th, 2003, 06:35 AM #5
- Join Date
- Oct 2001
Do you mean by dos mode that you put in a win9x boot floppy, and you wxp fs is ntfs?
If you do so, c:\ will most likely be a ramdrive/cdrom drive to which you can't write.
Also, you could've checked the attribs of the file to be replaced.
And then unset the permissions that were blocking (+r/+s)
January 26th, 2003, 09:50 AM #6
I was able to see the C: directory at the C:\ prompt. So I am pretty sure it was seeing C: correctly. Problem was getting it to accept the command to copy from the floppy to the Windows\system32 directory. Oh well. It's working now. Not sure why I got the stupid hal32.dll error anyway.
January 26th, 2003, 11:20 AM #7
That file is the Hardware Abstraction Layer and as such is machine dependant, so I am not sure if you will be able to just download another version & drop it in. I had a similar problem on an NT4 server & ended up trashing the install.
eddyI dreamt that a large eagle circled the room three times and then got into bed with me and took all the blankets.
January 27th, 2003, 04:09 PM #8
Hmm... maybe I can help. The way I see it, the problem here isn't about HAL; it's about the DLL - the Dynamic Link Library, a library of programming code that other programs dip into and use. Also this isn't a hardware problem so you don't need to download anything. This is more of a Windows problem: Windows is trying to load that file but couldn't find it. Why? Usually this occurs because the program was delted -- usually after uninstalling some hardware. In short Windows can't load the DLL because there's nothing there: it was removed together with whatever hardware you removed.
The good news is since you removed hardware associated with this, this hal32 is relatively useless; you just need to delete it.
Here's some quick solutions which I hope will help you:
1. Remember the name of the file causing the error; better yet, write it down - hal32.dll. Then back-up your hard drive just in case.
2. Choose START, then RUN then type system.ini in the open text box then press ENTER. Choose SEARCH, FIND, then enter the name of your missing dll in the find text box; press ENTER.
3. If the search finds the hal32.dll, make a record of the line it's in (probably by printing it!). Then... are you ready for this... DELETE THE ENTIRE LINE!
4. If you're the paranoid type of guy, you could repeat steps 2 and 3 all over again - up to 100 times if you want . Once you're satisfied, save then close the notepad.
5. Choose START, then RUN then type regedit in the open text box then press ENTER. This should lead you to the left and right panes of the Registry Editor. Click EDIT, then FIND then enter hal32.dll in the find text box making sure the keys, values and data check boxes are all checked then press ENTER.
6. Look at your editor's left pane; if the search finds a match there, first write down or print the exact entry for the keys, values and data for that search (in case you need to recreate them). Look at your editor's right pane for search matches and do the same. Then once again, delete all entries pertaining to hal32.dll
7. Press F3 to find the next match and repeat these steps until the find feature reports there are no more matches. Then choose REGISTRY then EXIT.
Hopefully that hal32.dll message will disappear. If not or something goes wrong you can always run your back-up (you did do step no. 1 right )Thanks for the reply; sorry if I can't answer quickly :)
April 30th, 2003, 08:41 AM #9
I just got this problem today with Win XP Pro.
Missing or corrupt <Windows root>\system32\HAL.DLL
It said HAL.DLL not HAL32.DLL.
The HAL.DLL is necessary as it is the part of the OS that prevents software from directly talking to the hardware.
I'm going to try to take it from another Win XP PC. If that doesn't work, I suspect it is the boot.ini file not the HAL.DLL.
One can expand it from the original install disk too.
If all else fails, I'll reinstall Win XP PRo. The 2nd time in a year I'll need to do this - pretty aweful for Microsoft's most reliable OS.Conservatives: "If the facts disagree with our opinion, ignore the facts -- or at least misrepresent them."
April 30th, 2003, 03:20 PM #10
Perhaps this link would help now or in the future.
You can't get there from here
April 17th, 2012, 11:27 AM #11
- Join Date
- Apr 2012
I got a partition for windows and a partition for my files i want
to keep on the same drive.
In the KEEP partition i noticed boot.ini ,ntldr and ntdetect,
i thought these should be on the windows partition and
The computer then rebooted to the message NTLDR missing
so i loaded up XPUD(small linux os on usb) i managed
to download the missing files and put them where the
others had been.
I restarted and got HAl32 message,rebooted to XPUD
then edited the boot.ini file as i had 2 partitions
and changed the lines
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws XP" /fastdetect
so it read partition(2) instead of (1) and the xp loaded after reboot!
Dunno if this helps but its always handy to have xpud on a bootable usb
or mp3 player(cuz it detects wireless internet most linux usb dont,handy for laptops)
also its good for getting rid of self replicating viruses that you cant delete!
Im not saying get xpud just look at your boot.ini files see if its changed
may help(if you can access it somehow)
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)