Hal.dll

[Guest]

I did the following mistake,

I tried to install windows 2003 server on my computer, with windows home
edition installed on the hard drive.
I instructed win 2003 setup to do an installation on other folder, \winnt\
but after restart I get the following error:

"Windows could not start because the following file is missing or corrupt:
<Windows Root>\system32\hal.dll
Please re-install a copy of the above file"

Any ideas how to resolve that? I tried to do what the message displays but
no progress.

 

[Steve]

x-no-archive: yes

I did the following mistake,

I tried to install windows 2003 server on my computer, with windows
home edition installed on the hard drive.
I instructed win 2003 setup to do an installation on other folder,
\winnt\ but after restart I get the following error:

"Windows could not start because the following file is missing or
corrupt: <Windows Root>\system32\hal.dll
Please re-install a copy of the above file"

Any ideas how to resolve that? I tried to do what the message
displays but no progress.

See if this helps:
http://terabyteunlimited.com/kb/article.php?id=130

 

[Stan Brown]

I did the following mistake,

I tried to install windows 2003 server on my computer, with windows
home edition installed on the hard drive.
I instructed win 2003 setup to do an installation on other folder,
\winnt\ but after restart I get the following error:

"Windows could not start because the following file is missing or
corrupt: <Windows Root>\system32\hal.dll
Please re-install a copy of the above file"

Any ideas how to resolve that? I tried to do what the message
displays but no progress.

See if this helps:
http://terabyteunlimited.com/kb/article.php?id=130[/QUOTE]

The article refers to BootitNG, but the same thing can occur with
plain-vanilla Windows software after repartitioning.

I don't know if this is the OP's problem, but it might help:

I had a hidden partition and free space before the C: drive, where
Windows lives. (I didn't do it; it was the computer manufacturer.) I
deleted the hidden partition and created one for my Linux install.
That made the C: drive the _second_ primary partition, but BOOT.INI
in Windows was still trying to boot from the first partition. (Only
the partition number had changed, not the location of the Windows
partition.) I got the exact same message about HAL.DLL as the OP.

The solution was to boot into Recovery Console and edit BOOT.INI to
point to partition 2 instead of partition 1. When I rebooted, Windows
came up fine.

Unfortunately, you can't boot Recovery Console unless you previously
activated it while you had a healthy system. (Why on earth Microsoft
didn't make it active by default, I can't imagine.)

N.B. This is Recovery Console, a boot option -- not the System
Restore program that runs under Windows.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Fortunately, I live in the United States of America, where we are
gradually coming to understand that nothing we do is ever our
fault, especially if it is really stupid. --Dave Barry

 

[Steve]

See if this helps:
http://terabyteunlimited.com/kb/article.php?id=130

The article refers to BootitNG, but the same thing can occur with
plain-vanilla Windows software after repartitioning.[/QUOTE]

I assumed the OP could figure out what to do if he knew the cause ...
Because the cause and solution is independent of BootIt NG.

The TeraByte Unlimited site has a freeware utility, EditBINI, that "will
allow you to edit \BOOT.INI in an NTFS partition from DOS or Win9x."

 

[Peter Foldes]

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