Cheers for all of the help guys. Top service as always.

<windows root>\system32\hal.dll
#16
Posted 16 September 2006 - 01:37 PM

Cheers for all of the help guys. Top service as always.
#17
Posted 16 September 2006 - 02:53 PM

SRX660
#18
Posted 23 September 2006 - 01:13 AM


I have 2 hard disks one loads with Win 98SE and another Win XP Pro. Yesterday I re-installed Win XP and I started getting the 'hal.dll missing' errors when I try to load the 98SE.
I checked the boot.ini however I'm not a techie and I'm unsure how to troubleshoot.
MSCONFIG ->'Check All Boot Paths' Option says that 'all BOOT.INI Lines appear to be correct'.
BOOT.INI Loaded from XP:
----------------------
[boot loader]
timeout=30
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" /noexecute=optin
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="MS Windows 98 SE" /fastdetect
----------------------
More info:
- 1 disk - Win XP Pro - Default loader
- 1 disk - Win 98SE
- XP was re-installed and loads fine.
- 98 shows the 'hal.dll' corrupt/missing error after I select 98 from the boot screen.
Glad if you can provide me with some help on this.
10x in advance.
#19
Posted 23 September 2006 - 08:30 AM

SRX660
#20
Posted 23 September 2006 - 08:38 AM

Windows 98 will install over itself very nicely and will ususally resolve this problem. You may have to start the installation using a startup disk...make sure to install to the same directory.
#21
Posted 23 September 2006 - 09:37 AM

Thanks for your suggestions.
I have an update:
I found a hal.dll online, I copied the file in the system32 folder, and that appeared to have solved THIS problem. After rebooting I got the next error which was:
- '<windows root>\system32\ntoskrnl.exe is corrupt or missing'.
I found a copy of ntoskrnl.exe online and placed it in the same folder. Again after rebooting I got a new error:
- 'Load needed DLLs for kernel'

Checked out Microsoft http://support.micro....com/kb/164448/ and this KB says that the Hal.dll and Ntoskrnl.exe files are mismatched, which is most probaby my case.
Unfortunatley I was unable to follow the KB as it's for Win NT.
I'll most probably end up doing what 'wannabe1' suggested, but it looks like I'm soo close.
Any suggestions before I do the next move?

Thanks a lot!
#22
Posted 26 September 2006 - 03:58 PM


#23
Posted 06 February 2007 - 12:09 AM

Well I have exactly the same problem.
One of my RAM sticks went belly up .... memory fail, spots in a matrix on the screen.... then the dreaded <windows root>\system 32\hal.dll is missing.
Tried to do a repair ... failed when halfway
didn't want to format and lose everything.
Then realised I had D partition that I'd emptied all valuable contents onto CD a coupla months back, so I did a clean install on D, changed the bios and loaded my modem and here I am. 4 am start, back online by 7am.
Now how to restore hal to C drive so it's usable again with all my programs... nero's in there too. I ain't got nuthin on D ceptin windows and foxit.
I'm afraid that there will be an endless sequence of missing files...
#24
Posted 06 February 2007 - 01:59 AM


#25
Posted 27 July 2007 - 10:42 PM

Hello Again,
Thanks for your suggestions.
I have an update:
I found a hal.dll online, I copied the file in the system32 folder, and that appeared to have solved THIS problem. After rebooting I got the next error which was:
- '<windows root>\system32\ntoskrnl.exe is corrupt or missing'.
I found a copy of ntoskrnl.exe online and placed it in the same folder. Again after rebooting I got a new error:
- 'Load needed DLLs for kernel'![]()
Checked out Microsoft http://support.micro....com/kb/164448/ and this KB says that the Hal.dll and Ntoskrnl.exe files are mismatched, which is most probaby my case.
Unfortunatley I was unable to follow the KB as it's for Win NT.
To whom it may help:
Do not try the above, as it will get you to the "Load needed DLLs for kernel" error, I just tried it today, same prob. But finally came with an "alternate" solution to Repair Install or "in-place uprgrade". It’s something like what tobyed did.
Since I was afraid of what doing a reapair install might have done to my programs, I installed XP on another partition (in the same computer) and then copied “hal.dll” and “ntoskrnl.exe” over to the damaged ‘system32’ folder. And it works perfectly as before now.
As tobyed posted: “HAL is an acronym for hardware abstraction layer. The hal.dll file is a Windows NT file that is used by windows when communicating with your computer's hardware. It enables hardware from different vendors to allow them to accept a common set of Windows commands. If it is missing Windows will not function.”
For what I understand, it is unique to each computer, depending on the hardware components it has. Thus I am pretty sure using a downloaded one will not work. (If I am wrong please correct me).
Thus, I’m not sure how the method:
“5. At the command prompt type: expand d:\i386\hal.dl_ c:\windows\system32\hal.dll. (where d: is the drive letter of your CD and c:\windows is the location for your Windows installation folder.) If prompted for permission to overwrite an existing version of the hal.dll file select yes.
6. Once you have expanded the file type "exit" to exit the Recovery Console and restart the computer.”
...is to work, as the hal file would be a generic one. Does Windows reconfigure it when it restarts? Or, does the “expand” command configure it? Or does this method work at all? (It did not work for Tobyed)
If I would know how to program, I’d try to write one that would reconfigure the generic hal (and maybe ntoskrnl too?) file with the unique hardware components specifications of the computer it was being executed. Or maybe someone can (if you do, or it exists, please let me know! (maybe some credit?))
I am 90% + sure if tobyed would have copied “hal.dll” and “ntoskrnl.exe” from the re installation he did over to the old ‘system32’ folder it would have booted up fine. I am pretty sure they were there, he just did not find them. Otherwise, how could his Windows boot if the files were not there and the other ones (on damaged install) were corrupted.
That’s officially my first post here, in fact, any 'help' forum. Hope it may help someone. And if anyone can answer my questions, I would be very thankful!
God bless y’all,
-docarii
Edited by docarii, 27 July 2007 - 10:55 PM.
#26
Posted 26 September 2008 - 02:12 PM

#27
Posted 26 September 2008 - 02:21 PM


Please leave this topic alone for help for tobyed only.
Thanks,
Fenor
Edited by Fenor, 26 September 2008 - 02:22 PM.
#28
Posted 21 January 2009 - 03:45 PM

Hi.
Whenever I try and boot my computer I get the error message: "<windows root>\system32\hal.dll is missing or corrupt. Please reinstall it." - or something along those lines.
I've trawled through the internet looking for solutions. I initially tried just repairing the installation of the OS, as I have done numerous times in the past. This option actually wasn't available to me, my only option was for a complete format or to go into the recovery console.
I've tried various commands in the console but none have worked for me.
Here's the solution that I followed:
What is the boot.ini file and how do I repair it?
This is the file that is used that identifies the location of Windows. It is a hidden system file located in the root partition of the primary hard drive ©. It identifies which hard drive, which partition on the drive and the folder where Windows is installed.
The steps to repair a missing or corrupt boot.ini file are:
1. Insert and boot from your Windows XP CD.
2. When you receive the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.
3. When you receive the "Welcome to Setup" message, press R to start the Recovery Console.
4. Press the number that corresponds to the correct location for the installation of Windows you want to repair, typically this will be #1.
5. Type bootcfg /list to show the current entries in the BOOT.INI file. At this point you may get a message telling you that the boot.ini file does not exist. The next step will correct this error.
6. Type bootcfg /rebuild to repair it. This will scan your hard dives for installations of Windows XP, 2000 or NT and display the results. Follow the on-screen instructions to add your Windows installations to the boot.ini file. Those step will be:
1. Total Identified Windows Installs: 1
(1) C:\Windows
Add installation to boot list? (Yes/No/All)
Type y and hit enter
2. Enter Load Identifier
This is the name of the operating system. When you receive this message, type the name of your operating system, and then press ENTER.
3. Enter OS Load options
When you receive this message, type /fastdetect, and then press ENTER.
Note: The instructions that appear on your screen may be different, depending on the configuration of your computer.
7. Take out the CD ROM and type exit.
The rebuild command came up with an error message due to a corrupt file system.
Next I tried this:
What is the hal.dll file and how do I repair or replace it?
HAL is an acronym for hardware abstraction layer. The hal.dll file is a Windows NT file that is used by windows when communicating with your computer's hardware. It enables hardware from different vendors to allow them to accept a common set of Windows commands. If it is missing Windows will not function.
In situations where it has become damaged, either from virus activity or hardware failure, it may be necessary to replace it with an undamaged copy. Here are the steps necessary to replace the hal.dll file with an undamaged copy from the Windows CD:
1. As above, insert and boot from your Windows XP CD.
2. When you receive the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.
3. When you receive the "Welcome to Setup" message, press R to start the Recovery Console.
4. Press the number that corresponds to the correct location for the installation of Windows you want to repair, typically this will be #1.
5. At the command prompt type: expand d:\i386\hal.dl_ c:\windows\system32\hal.dll. (where d: is the drive letter of your CD and c:\windows is the location for your Windows installation folder.) If prompted for permission to overwrite an existing version of the hal.dll file select yes.
6. Once you have expanded the file type "exit" to exit the Recovery Console and restart the computer.
Doing this lead to the message - 'There is no CD or Floppy disk in the drive', when the recovery disk was.
If anyone can point me in the right direction with this problem it would be greatly appreciated. A complete format of my hard drive isn't something I want to resort to just yet.
Thanks.
#29
Posted 25 October 2009 - 08:33 PM

#30
Posted 25 October 2009 - 10:02 PM

Please start your own topic
Although your issue may seem similar there can be other factors that may need to be resolved.
By bumping on someone's topic especially one that is realistically over a year old. It makes it confusing for the tech to understand who they are helping. This can in turn cause the wrong support to be given and can cause instability or worse to happen to your system. Thank you for your cooperation.
Similar Topics
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
As Featured On:






