HELP! missing hal.dll, no access to root

[six3077]

so i turn on my machine and I get this error
'windows cannot start because the following file is either missing or corrupted: hal.dll'

So, I put in the xp cd boot from that and try to use recovery console. ( i was hoping that there was an automated repair option, but i gues not)
Anyways, I cannot access the windows root directory in recovery console. Which means I couldn't even add hal.dll in there if I wanted to.

Anybody help me here with a step by step how to?
by the way, I am using Maxtor SATA 120GB, where I have to install a 3rd party driver for windows to even detect the drives.
The other q I have is, how did this file even go missing??? I've only had xp on for about 2 weeks?? (with all the updates too)

thanks to anyone with good suggestions

 

[bcastner]

I would suspect a hardware failure of the drive, or the controller.

The MS KB discusses possible workarounds if the boot.ini file is incorrect, or files are missing:

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

You might try from Recovery Console:

. chkdsk /r
. bootcfg /rebuild
. fixboot c:

 

[bcastner]

As a repair reinstallation of XP is likely, make sure before doing so that:

. You have made any BIOS updates that may exist for your motherboard;
. That you have updated your SIL driver set for the SATA drive, including expanding the download to a floppy disk.

http://support.microsoft.com:80/support/kb/articles/q315/3/41.asp&NoWebContent=1

 

[guaranteed]

INformation I used from a prior problem of this sort, may be of help.
Bruce



Missing Windows hal.dll file:


--------------------------------------------------------------------------------

Issue:

Missing Windows hal.dll file.

Additional information:

Additional information about the definition for HAL can be found on our HAL dictionary definition page.

Cause:

The missing or cannot find hal.dll, \windows\system32\hal.dll, or \winnt\system32\hal.dll error message may be experienced on a Microsoft Windows 2000 or Microsoft Windows XP system when the boot.ini becomes corrupted or when a user is attempting to dual boot a computer.

Solution:

Verify that the computer boot.ini is present and not corrupted

Verify the boot.ini file is found on the computer by using a boot diskette or use your Windows CD to get to the MS-DOS "C:\>" prompt.
From this prompt edit the boot.ini, verify that it is pointing to the correct operating system, and that no anomalies are found within the file. Additional information about editing the boot.ini as well as additional information about its available options can be found on document CH000492. Below is a listing of what to verify
If only one operating system is on the computer verify that the boot.ini only has one operating system listed. In some situations an alternate configuration line may be added for the same operating system, leaving the improper line.
Verify that the "default=" line as well as the operating system line are the same and that they are pointing to the correct operating system.
Verify that the computer has the hal.dll file

From the MS-DOS "C:\>" prompt quickly determine if your computer has the "hal.dll" file by typing "dir hal.dll /s" at the prompt. If the computer returns a "File not found" message, the hal.dll has been deleted.

To recover this file boot the Windows operating system CD and choose the option to "restore", "repair", or "recover". This option will prompt you for the Windows installation to use, the administrators password and will allow you to restore the proper file. At the MS-DOS prompt type the following command:

expand x:\i386\hal.dl_ y:\windows\system32\hall.dll

In the above example "x" would be the letter of your CD-ROM drive and "y" the letter of the drive your operating system is installed on. If you need to determine the drive letters of your devices type "map".

Additional information about the expand command can be found on our expand help page.

Reinstall the operating system

If the boot.ini is found on the computer and does not appear to be corrupted and/or if the hal.dll file is missing it is recommended that you reinstall your Windows operating system.

 

[kengadd]

HAL = Hardware Abstraction Layer....this is a portion of the boot up that scans your hardware. If you have changed your hardware you can get this problem.....If you have lost or corrupted the file then go for a fresh install ....(change your BIOS to boot from CD and insert your XP disk)

 

[bcastner]

kengadd,
While I have never been happy with the notion of changing the HAL through Device Manager, there are many who do so routinely and happily.

One can easily force a different HAL with a repair reinstall of XP and not be forced to lose everything with a clean install. Microsoft agrees:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;299340

 

[ba2486]

HAL.DLL is Missing

Boot from your CD and follow the directions below to start Recovery Console.

Insert the Setup compact disc (CD) and restart the computer. If prompted, select any options required to boot from the CD.
When the text-based part of Setup begins, follow the prompts; choose the repair or recover option by pressing R.

If you have a dual-boot or multiple-boot system, choose the installation that you need to access from the Recovery Console.
When prompted, type the Administrator password. (if you didn't create one try pressing enter).

At the system prompt, type Recovery Console commands; type help for a list of commands, or help commandname for help on a specific command.

Most likely you will need to expand the file from the CD. The command would be expand d:\i386\hal.dl_ c:\windows\system32\hal.dll. Substitute d: for the drive letter of your CD. Once you have expanded the file type "exit" to exit the Recovery Console and restart the computer.

Error Message: Cannot Find \Windows\System32\hal.dll

http://www.kellys-korner-xp.com/xp_haldll_missing.htm

 

[Caitlinjo]

I am using windows xp pro and I had the identical problem within a week of installing XP. This occurred just after the release of XP so there weren't as many people familiar with XP's quirks as there are now. As a result it took me damn near forever to figure out what was wrong. In that initial case and in several others involving other computers, every indication of a missing hal.dll file has in actuality been a problem in the boot.ini file. Even when the boot.ini file read correctly, somehow it didn't work as it should. Try replacing it with another with the same contents. On the machine where I originally installed XP I retained windows 98 and used Boot Magic to shift between 98 and XP. Here are two copies of the boot.ini file, one for a single operating system and the other for a hard drive containing two operating systems.

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

The only difference between the two is the number of partitions containing an operating system. I don't know how this will look when it is posted. As I see it now, the last line occupies two lines. There are five lines total, the last line begins with multi and ends with fastdetect. When you make the file just be sure to have five lines instead of six.

As a suggestion to a good file program to use in DOS or when booting from a floppy, try Volkov Commander. I use it frequently and consider it invaluable. You can get it at:

http://www.egner-online.de/vc/

 

[six3077]

Took a while to get back, but I eventually fixed it.
I am still not sure what caused this because the boot.ini file but it obviously has something to do with the boot.ini file.
After reading the suggested methods by MS, to which every single command was unsuccessful (apparently didn't have the proper 'rights' in the recovery console)
I did recall that the files that 'were missing' were in fact NOT missing.
I think I would have to go with Caitlinjo idea that the boot.ini for some reason was just not reading right.
After tinkering for a while, I said 'F*$k it' and went for the reinstall. I decided to save it to a renamed directory so I didn't lose files in my documents it mentioned a reboot, I pulled the cd, and voila it came back up.
The first thing I did once I got back to my o/s was back up EVERYTHING. Then I went in search of my favourite version of linux and have it sitting next to the machine, for the next time something goes wrong with xp.
(which won't be much longer now)
Thanks to all for the suggestions.