I believe that When XP installs, it figures out the correct hal.dll at installation time - it picks one of seven based on your hardware and that becomes the hal.dll for your system. If I am not right about this, I hope somebody will straighten me out.
So to extract from an installation CD would require extracting the correct one, which is ascertainable, but the chances of it happening to be hal.dl_ are one in seven. Even though hal.dl_ seems like the right thing to extract - for me, it would be very wrong.
For example, if I wanted to expand mine, I would need to expand halaacpi.dl_ (I figured all this out one day). If I extracted hal.dl_, I would get the wrong one for my system.
I extracted mine here from RC several times just a while ago and can't recreate your extract error message, but you would still have to know the correct one to extract (do you?). Are you able to rename the suspicious system32\hal.dll file and then try the extract?
I cannot remember your extraction problem and what it means and can't reproduce it though I have seen it before
but so for in my experience the missing or corrupt hal.dll message points to a botched boot.ini.
If your system cannot boot, how are you copying a hal.dll from a working system to your afflicted system?
How did you get that contents of your boot.ini? Did you type all that stuff into your message here by hand or copy/paste it somehow by booting some other method and if yes, what is that method? It just looks pretty good for a typing it in by hand job. How did you see the contents of your new boot.ini file so perfectly if you are booting using Recovery Console (this is not a trick question).
When you boot RC are you at the C:\WINDOWS prompt?
You say you have run chkdsk /r from RC with no errors?
chkdsk c: /r
In a general configuration with one boot partition, you don't even need a boot.ini to boot. XP will complain about it, but still boot just fine, so from RC you could rename your c:\boot.ini to be sure you do not have one at all and remove that variable from the equation. Something like this from the C:\WINDOWS prompt after RC is loaded:
cd \ (back up a folder to C:\ from C:\WINDOWS)
attrib -shr boot.ini (remove system, hidden, read only attributes)
dir boot.ini (you should see it listed)
ren boot.ini boot.ini.bak
dir boot.ini (you should not see it listed)
Also, if you use bootcfg /rebuild and you already have a boot.ini (even if it is not broken), you will build on top of the potentially broken one adding more confusion unless you delete the old one first. If I was going to do bootcfg /rebuild, I would make sure I renamed or deleted the current c:\boot.ini file first.
That might be okay for the moment if there was nothing wrong with your original one to begin with, but since you don't even need a boot.ini to boot in the first place (if nothing else is broken), just try to boot without a boot.ini and then see what happens and what to do next.
Edited by joseibarra, 10 March 2010 - 03:28 PM.