I don't suspect that this error is always something to do with resizing partitions or running a disk clean as my brother has the same problem and all he did was try to install extra memory and then on a reboot he got he missing hall.dll message.
I suspect this would most likely mean that the dll file is corrupt and as it relates to your hardware, hence the reason you can't boot.
I have suggested that he boots up with ERD Commander 2005 from CD (free software) which 90% of the time fixes any system file corruption.

I had this "missing or corrupt hal.dll" problem after I had tried to merge two partitions on my XP box by using Partition Magic. Since PM removed one drive during the process I ended with an incorrect BOOT.INI.

I compiled a brand new machine (this is the fourth identical one I've built), loaded windows, loaded the software ... rebooted.

Now, about every 1 in 3 boots I got a quick blue screen when loading - so quick I couldn't read it. Then a reboot, then "Windows didn't shut down pro...".

Ignore it, and it boots fine. Reboot, it boots fine. Reboot again - quick blue screen ....

So I pulled all the bits out, formatted the HD, installed all components, drives etc 1 by 1.

Got the same thing. Grrrrrrrrr.

Reinstalled windows over the top - got Hal.dll error.

I think its a hard drive issue - going to replace this PM. One thing I did notice when installing though, is I got a nasty electrical shock from the outside of my network connector cable that was connected to my cable modem while I was touching the PC case (earthed). I thought I may have just touched the connectors, but don't think so now. Can a faulty earth cause a HD to fail - or even the mobo ? I'll check the cable with a multi meter this PM too.

caus he doesnt find my disk, theyre aint a volume to install on or repair, i see my disks in the bios.. running to disks as one.

but just cant install a thing, also in does, i cant find my disks.

typing fdisk doesnt work to, think this will be a jaob for the hardcore expert, caus if needed, i cant reinstall to, to many important files on there tha i have to retrieve in some way..stupid guaranty on my comp, wont let me open my case for myself to.. sealed:S.. else i wold have made a secondary of my hds on this comp, so i could transfer the files, and format them here or something..

this problem sucks bigtime, hadnt heard from it eiter

-i didnt install big programs
-did not remove big rograms
-did no make or removed partitions

-only huge transfers of date (vcd's)

so why this happend i dont know, my comp did scandisk when my comp was shut down correctly, kindah strange.. but that could be cause of overnet.. that is one when running and shutting down my comp?

I have a HP Vectra 500MHz Pentium III

OS is Windows XP Pro

that out of the way, several months ago I tried to install a cd writing software for another hp computer and my system crashed in the middle of the installation. When I rebooted and after the BIOS screen I get the error message, missing or corrupted Hal.dll file, and to that I need to re-insall the missing file.

ok, well when I press any key it does an auto boot. I have the option to F2 to enter Bios and if I catch it just right I can F8 to enter the OS command screen (where you can go into safe mode), but EVERY option in there brings me right back to the missing hal.dll message and again, pressing any key does an autoboot.

ok what I have tried:
Tried changing the order of the boot so I can boot off my original XP Pro CD, and try to fix it. BUT every time it trys to boot to the CDRom it says Drive failure, instert system disk, press any key to continue. I know the cd is a bootable cd, I used it recently on another machine I have, just to check to see its bootable.

o.O

ok so at this point, I created a DOS 6.0 diskett and copied the hall.dll file to it as well. Using the disk it boots into DOS. NOW I CANT FIND MY HARD DRIVE. A:\ and B:\ are the floppy drive, R:\ and S:\ (used to be D:\ and E:\) are my cdroms, and I tried every other letter in the alpha 3x's and no others work. It's like the the drive and only one I ever had (C:\) is gone. I cant replace the file if I have no destination to send it.

I was able to use a backdoor in DOS to access the XP CD and by the following: S:\i386\winnt
This began the setup for XP, but it halted right way, saying there was an interal set up error, somethign about couldnt find where to swap to.

So I thought it was the hard drive goign bad, went out and bought a new one (80 gigs this time vrs the 13 gigs I had) I installed the HDD, making sure that I had the jumper set to Master, since its the only drive on the IDE cord. I double checked the CDRoms to make sure master and slave jumpers were correct. I turned my machine on, and nothing, just hangs on blue screen I can press F2 to enter BIOS. So I went in and under the HDD settings, I changed it to read the HDD as 1023 heads cylinders 16 (or whatever the settings are, Im at work and trying to rely on my memory). I save and exit, and reboot.

And nothing again. So if figured at this point the BIOS needs to be upgraded and I'm to chicken to do that, so I took the new HDD out and put it in my better comp and put the old HDD back in. So basically Im back where I started.

Any suggestions, hints, tips or really good drugs?

My friend decided to reformat...so use windows cd to reformat...then the damn missing or corrupt hal.dll pops up...therefore i:

-reinstalled windows
-used different windows cd
-slow formatted the drive
-chkdsk /p
-bootcfg /rebuild
-copy d:\i386\hal.dl_ c:\windows\system32\hal.dll
-then the last three in reverse order at once

So if anyone who are at the similar problem like mine I found out the problem, well actually after I read all the other comments and solutions too!

This problem occurs most probably you all have a multiple partitions or hard disk, and when I go to the CMOS setup after pressing Del button at the begining, I gone through every single commands and options, then I realize that the problem is at the boot sectors. In my case, I have a few options which is boot from either Floppy, CD_Rom, HDD-0, HDD-1, HDD-2 and so on, here is the key point, for ppl who can input first, second or 3rd boot device, do not have 2 similar HDD, and just have the primary boot will do.

In my case, the default setting is CD-ROM, HDD-0, and HDD-1, but after I change it to Floppy, CD-ROM and HDD-0. The problem solve.

bootcfg /rebuild

www.jsifaq.com/subm/tip6100/rh6138.htm

Rules of thumb:

1. If you haven't been messing with your system, such as deleting or rearranging partitions, etc., or running cleanup programs that delete "duplicate" dlls, etc., and you get the missing or corrupt hal.dll message, then you may well have a hard drive problem, like several of you pointed out. If so, good luck.

2. If, however, you've been "improving" your system by doing some heavy earth moving, like I (and probably most of you) do on a more or less regular basis, then those who suggested that it may well be something as simple to fix as merely editing boot.ini to point Windows to the correct partition are the most likely to be correct.

It was so in my case: 'deleted a useless proprietary partition created by one of the major mass-producers of PCs and broke the 'puter because the surviving partion was now then number 1 (as in only) partition yet the boot.ini file hadn't been advised of all the heavy earth moving and was still pointing proudly to partition 2 as the location of WinXP.

So...in my case a very easy fix, but only because of the fine inputs above. Kudos all.

For those running NTFS....i suggest NTFSDOS Pro to edit from DOS.

What i forgot was that the original hardisk had a hidden primary partition so my original active XP partition was on partition 2 (partition 1 was hidden). When someone mentioned it could be an issue with the boot.ini file, i think in my case they were right.
My new hard disk had only one primary bootable partition even thought the boot.ini file from my original drive imaged XP partition was referencing to load XP from partition 2.

So, i'm guessing, editing the boot.ini for my new DI'ed partition so it references partition(1) like it should and not partition(2), should fix MY prob.

''due to ghost failiure MBR has been wiped''

I have been dealing with this isu for some time now and i found the best way to deal with this problem is:

1: you boot up your pc with your original or a simalar version of OS

2: you start the innstalation prosses and when asked you tell that insted of innstalling the os you want to fix a problem in it (mostly it is the letter e you have to press down)

3: then you have to chose the os that you want to fix

4: you have to get your administrator password on the computer

5: then you run the following command: expand [CDROM DRIVE LETTER]:\I386\hal.dl_ C:\windows\system32\hal.dll

6: then you run the following command: BOOTCFG /REBUILD (remember to give your new found boot system a sutibal name and the second chose you just hit enter)

7: reboot your pc and chose the sutibal name when askd for wich os to start

Running chkdsk /p solved the problem for me.

Missing or Corrupt HAL.DLL error messages are MISLEADING many into actions that may not be at all neccessary.

http://uk.europe.creative.com/support/forums/forum.asp?foru=32

Here's an excerpt:
"If I now go into my BIOS and set my Legacy USB support to "ENABLE", I get - you've guessed it - no sign of the BIOS level option to run the Raid setup routines ...and... <Missing or Corrupt HAL.DLL> with a refusal to boot into XP Pro.

AARGHHHHHHHHHHH

Remember, I HAD this set "ON" when I was happily running XP Pro on the Raid pair with the 120Gb 2nd HDD and the TnT M64 card in place. It is only since the 4600 was introduced to the system that this HAL problem became an issue.

If there is anyone who can shed light on this oddity, please please enlighten me.

you can get this error even if you have an intact NON corrupted Hal.dll and your drive scans perfect.

ok.. truth of the sitiation..
you should NOT have to reinstall windows.
and most of the time this error is NOT due to a failing hard drive.
as posted below.. and has NOTHING to do with windows 9x os's

generally you will recieve this error if you have changed a partition size moved a partion, or cloned a partition with windows NT or 2K or XP installed on it..

the best solution would be to change the drives SID's
there are several utilities out there that can do this..
the best I know if being "system commander" version 7 or higher..

change the drive/partitions sid and then edit the boot ini
to point the correct partition for given operating system.

this should cure your problem..

If you are not familiar with computers, I would take this one to a professional. Make sure that the hard drive is ok. Again, this problem is usually associated with a bad hard drive.

In addition, it is possible that a virus caused this issue. Make sure you have the most current version a an antiviral software.

If you are familiar with computers and have an install disk. Make sure your HDD is operating normally. Keep in mind, a Win95/98/ME startup disk will NOT recognize an NTFS formatted hard drive. Some Windows XP Home users use this format and this would give a false positive to a failed hard drive. If you rule out Hard Drive failure, I would try to repair the MBR. You can do this in the Recover Console by using your startup disk on boot. Type 'Help' and you will find the appropriate commands. If this does not work, do an 'over-install'. Reinstall the operating system over itself. I believe that Windows XP is probably the best for this type of operation, but it is still risky. It is possible that you will regain control of your computer but you could have registry issues.

Good luck troubleshooting. Feel free to post back.

Putting the XP cd in does n't work.

See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q237556

I don't agree with Microsoft, and would prefer to simply extract the file from the install CD and put it back in the Windows/System32 directory.

FYI - Here is Microsoft's KBA on the subject:

http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q320252

Here is what I recommend:

Get to the Command Prompt through a startup disk or the Advanced Startup Options.

With the Windows XP CD in your favorite CDROM drive, type:

extract [CDROM DRIVE LETTER]:\I386\cabs\hal.dll /L [HARD DRIVE LETTER]:\Windows\System32\

Restart Computer

Post back if you still have problems. My commands are weak this morning so I might have missed-typed.

Computerpilot