Missing <WINDOWS ROOT> \sytem32\hal.dll / Cannot use Recovery Cons

[Guest]

When attempting to boot my Windows XP Pro, IBM Laptop I get an error that
reads could not start because the following file is missing: <WINDOWS ROOT>
\sytem32\hal.dll Please reinstall a copy of the above file.

I have done the following:

I boot with a Windows XP disk and enter the Recovery Console. When doing so,
it does not prompt me for an admin password and automatically enters to a c:\

I attempt to run bootcfg /rebuild and get an error stating that it can't
complete the scan for windows installations that could be caused by corrupt
file system and recommends to run chkdsk.

I have run chkdsk /r a couple of times and it tells me that I have some
irrecoverable errors

When attempting to expand the hal.dll from the disk I get an access denied
error message. From the C:\ when I simply type cd windows , I get and access
denied message.

I have attemted to change the allowallpaths of the recovery console with the
set command and have been denied because the set command is disabled without
being logged into the admin which I never get a chance to do.

HELP???

 

[Detlev Dreyer]

When attempting to boot my Windows XP Pro, IBM Laptop I get an error that
reads could not start because the following file is missing: <WINDOWS ROOT>
\sytem32\hal.dll Please reinstall a copy of the above file.

I have done the following:

I boot with a Windows XP disk and enter the Recovery Console. When doing so,
it does not prompt me for an admin password and automatically enters to a c:\

See if this article helps.
"Error Message: Windows Could Not Start Because of a Computer Disk Hardware
Configuration Problem" http://support.microsoft.com/kb/314477/en-us

 

[Guest]

That was the article that led me to where I am now. It doesn't address what
to do when the "access denied" message is received and bootcfg /rebuild.
Conceptually, I need to change the access rules of the Recovery Console to
copy and save the hal.dll .

 

[Detlev Dreyer]

That was the article that led me to where I am now. It doesn't address what
to do when the "access denied" message is received and bootcfg /rebuild.
Conceptually, I need to change the access rules of the Recovery Console to
copy and save the hal.dll .

Sure that "hal.dll" is really missing and did you read the posted article
KB314477? Excerpt:

| CAUSE
| This behavior can occur if any or some of the following conditions are
| true:
|
| • The Default value in the [Boot Loader] section of the Boot.ini file
| is missing or invalid.
| • Windows XP is not installed in the location specified in the Boot.ini
| file.
| • The Ntoskrnl.exe file is missing or damaged.
| • The partition path in the Boot.ini file is not set correctly.
| • General hardware failure.

A missing or damaged "Hal.dll" is not even listed as possible cause.
It might be best to perform a repair installation at this point, good
luck.

 

[Guest]

Year. I got to that article in a round about way trying to understand the
Recovery Console. As I'm not sure the XP disc I have is the one that
actually came with this computer as I've had a couple over time.
Interestingly, I have been able to extract the hal.dll to the root directory,
I just can't put it in the windows directory.

That was the article that led me to where I am now. It doesn't address what
to do when the "access denied" message is received and bootcfg /rebuild.
Conceptually, I need to change the access rules of the Recovery Console to
copy and save the hal.dll .

Sure that "hal.dll" is really missing and did you read the posted article
KB314477? Excerpt:

| CAUSE
| This behavior can occur if any or some of the following conditions are
| true:
|
| • The Default value in the [Boot Loader] section of the Boot.ini file
| is missing or invalid.
| • Windows XP is not installed in the location specified in the Boot.ini
| file.
| • The Ntoskrnl.exe file is missing or damaged.
| • The partition path in the Boot.ini file is not set correctly.
| • General hardware failure.

A missing or damaged "Hal.dll" is not even listed as possible cause.
It might be best to perform a repair installation at this point, good
luck.

 

[Malke]

Year. I got to that article in a round about way trying to understand the
Recovery Console. As I'm not sure the XP disc I have is the one that
actually came with this computer as I've had a couple over time.
Interestingly, I have been able to extract the hal.dll to the root directory,
I just can't put it in the windows directory.

Extracting hal.dll isn't going to fix it anyway and you don't fix it
from the Recovery Console. I'm sure you've seen this, but here is
information from the late MVP Alex Nichol:

That message is rather misleading. It happens because the boot.ini file
that tells the boot where to look for 'Windows' is damaged, so it is
looking for files in the wrong place - hal.dll just happens to be the
first one it looks for. Set the BIOS to boot CD before Hard Disk. Boot
the XP CD and, instead of Setup, take the immediate R for Repair.
Assume any password requested is blank, and TAB over.

Use
Attrib -H -R -S C:\boot.ini
DEL C:\boot.ini
to delete the bad one
BootCfg /Rebuild

to search for Windows installations and make a new one.

As for not having the correct XP disk, you only need to have one that
matches the installed version - Home/Pro, retail/OEM.


Malke