hal.dll missing and bootcfg doesn't find 2nd windows

[Christian T]

Hello everybody!

This problem happens to me for the 3rd time now and after two reinstalls I
really want to understand it this time. But after spending hours on Google
and newsgroups I'm not smarter than before. Maybe you experts can help...

Laptop, 1 hdd, 2 primary partitions holding one Windows XP each (I split
business and private XP). Dual booting work perfectly find until days ago.
Then, when trying to boot my 2ND !! installation (without any previous error
or strange behaviour):

WINDOWS could not start because the following
file is missing or corrupt: <WINDOWS ROOT>\system 32\hal.dll
Please reinstall a copy of the above file.

The installation on the 1st partition still works fine.
The files on the 2nd partition are still present and accessible, but the XP
there doesn't start.

Boot.ini (on 1st partition) looks like this:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional"
/NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Private"
/noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

What I did so far:
1. compared hal.dll on 2nd partition with known good file from other
computer => exactly the same
2. compared ntdetect and ntldr on 1st partition with good files => they are
ok, too
3. used diskpart to check that I really have only 2 primary partitions with
numbers 1 and 2 => looks normal
4. used bootcfg /scan to see if both installations are detected => ONLY THE
1ST INSTALLATION IS DETECTED !!

I guess that means that somehow the hal.dll on the 2nd partition cannot be
loaded during boot, which causes the error message.

But why? The partition is there, hal.dll is there, boot.ini is complete and
looks perfectly fine...

Any ideas?

Can someone explain what exactly bootcfg looks for in order to detect a
windows installation? There must be some prerequesites that my 2nd partition
doesn't meet anymore.

Thanks a lot for your help, much appreciated!!

Cheers,

Christian

 

[db.·.. >]

instead of a bootcfg /scan
you might try
a bootcfg /rebuild instead:

here is more info:

http://support.microsoft.com/kb/314477

 

[Christian T]

Thanks for the answer!

I already tried that and it resulted in a boot.ini with only the
installation on the 1st partition being listed.

The way I understand the bootcfg documentation the detection mechanisms of
/scan and /rebuild are the same, but /scan only shows the results, while
/rebuild modifies or recreates the boot.ini.

Cheers,

Christian

instead of a bootcfg /scan
you might try
a bootcfg /rebuild instead:

here is more info:

http://support.microsoft.com/kb/314477


--

db·´¯`·...¸><)))º>

Hello everybody!

This problem happens to me for the 3rd time now and after two reinstalls I
really want to understand it this time. But after spending hours on Google
and newsgroups I'm not smarter than before. Maybe you experts can help...

Laptop, 1 hdd, 2 primary partitions holding one Windows XP each (I split
business and private XP). Dual booting work perfectly find until days ago.
Then, when trying to boot my 2ND !! installation (without any previous error
or strange behaviour):

WINDOWS could not start because the following
file is missing or corrupt: <WINDOWS ROOT>\system 32\hal.dll
Please reinstall a copy of the above file.

The installation on the 1st partition still works fine.
The files on the 2nd partition are still present and accessible, but the XP
there doesn't start.

Boot.ini (on 1st partition) looks like this:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional"
/NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Private"
/noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

What I did so far:
1. compared hal.dll on 2nd partition with known good file from other
computer => exactly the same
2. compared ntdetect and ntldr on 1st partition with good files => they are
ok, too
3. used diskpart to check that I really have only 2 primary partitions with
numbers 1 and 2 => looks normal
4. used bootcfg /scan to see if both installations are detected => ONLY THE
1ST INSTALLATION IS DETECTED !!

I guess that means that somehow the hal.dll on the 2nd partition cannot be
loaded during boot, which causes the error message.

But why? The partition is there, hal.dll is there, boot.ini is complete and
looks perfectly fine...

Any ideas?

Can someone explain what exactly bootcfg looks for in order to detect a
windows installation? There must be some prerequesites that my 2nd partition
doesn't meet anymore.

Thanks a lot for your help, much appreciated!!

Cheers,

Christian

 

[db.·.. >]

unfortunately i am short
on ideas because your configuration
and problem is something
i don't recall seeing or having.

you did mention that you
compared the hal.dll files.
however, it may simply need
to be replaced.

here is some more fyi:

http://pcsupport.about.com/od/fixtheproblem/ht/restorehaldll.htm

however, at this point it is unclear to
me if you can log into that
secondary o.s. via the command
console since i think you would
likely have to log into the
faulty installation in an
attempt to work on it.

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

it might simply be easier to do a
repair installation with
a windows setup cd, again
keeping in mind that you likely
used a cd to create a second
installation anyways.

however, unlike a new install,
the above method would
replace or repair missing
or corrupted system files
without affecting the other
programs "or" your personal
files.

here is a bit more:

http://support.microsoft.com/kb/299340

--

db·´¯`·...¸><)))º>

Thanks for the answer!

I already tried that and it resulted in a boot.ini with only the
installation on the 1st partition being listed.

The way I understand the bootcfg documentation the detection mechanisms of
/scan and /rebuild are the same, but /scan only shows the results, while
/rebuild modifies or recreates the boot.ini.

Cheers,

Christian

instead of a bootcfg /scan
you might try
a bootcfg /rebuild instead:

here is more info:

http://support.microsoft.com/kb/314477


--

db·´¯`·...¸><)))º>

Hello everybody!

This problem happens to me for the 3rd time now and after two reinstalls I
really want to understand it this time. But after spending hours on Google
and newsgroups I'm not smarter than before. Maybe you experts can help...

Laptop, 1 hdd, 2 primary partitions holding one Windows XP each (I split
business and private XP). Dual booting work perfectly find until days ago.
Then, when trying to boot my 2ND !! installation (without any previous
error
or strange behaviour):

WINDOWS could not start because the following
file is missing or corrupt: <WINDOWS ROOT>\system 32\hal.dll
Please reinstall a copy of the above file.

The installation on the 1st partition still works fine.
The files on the 2nd partition are still present and accessible, but the XP
there doesn't start.

Boot.ini (on 1st partition) looks like this:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional"
/NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Private"
/noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

What I did so far:
1. compared hal.dll on 2nd partition with known good file from other
computer => exactly the same
2. compared ntdetect and ntldr on 1st partition with good files => they are
ok, too
3. used diskpart to check that I really have only 2 primary partitions with
numbers 1 and 2 => looks normal
4. used bootcfg /scan to see if both installations are detected => ONLY THE
1ST INSTALLATION IS DETECTED !!

I guess that means that somehow the hal.dll on the 2nd partition cannot be
loaded during boot, which causes the error message.

But why? The partition is there, hal.dll is there, boot.ini is complete and
looks perfectly fine...

Any ideas?

Can someone explain what exactly bootcfg looks for in order to detect a
windows installation? There must be some prerequesites that my 2nd
partition
doesn't meet anymore.

Thanks a lot for your help, much appreciated!!

Cheers,

Christian

 

[Christian T]

unfortunately i am short
on ideas because your configuration
and problem is something
i don't recall seeing or having.

Yeah, me neither. And I do have quite some experience in delivering
professional support for Windows based servers so I usually know where to
search. But this one.....

you did mention that you
compared the hal.dll files.
however, it may simply need
to be replaced.

Did a binary file compare, so they really should be ok, but nevertheless
replace them later yesterday. No effect whatsoever...

however, at this point it is unclear to
me if you can log into that
secondary o.s. via the command
console since i think you would
likely have to log into the
faulty installation in an
attempt to work on it.

Yes, I can. Actually, I tried the bootcfg /scan while being logged into the
first, working installation.
But to be sure I started recovery console again, logged into the 2nd (not
booting) installation, and did the bootcfg /rebuild you mentioned.
=> Still only the first installation is found!
Cool, I can log on to a windows that is not visible to bootcfg ;-\

it might simply be easier to do a
repair installation with
a windows setup cd, again
keeping in mind that you likely
used a cd to create a second
installation anyways.

I tried that the last time I had the issue without effect. As it would bring
all my windows files back to SP2 level I'm not really keen to try it again.
Of course I know that this wouldn't hurt my data (which is not in danger
anyway).


More and more I come to the conclusion that this is somehow related to the
partition.
But it would be very helpful to understand what bootcfg is looking for to
identify an installation. Could guide me to the source of the issue.

Thanks a lot for the effort,

Christian

Thanks for the answer!

I already tried that and it resulted in a boot.ini with only the
installation on the 1st partition being listed.

The way I understand the bootcfg documentation the detection mechanisms of
/scan and /rebuild are the same, but /scan only shows the results, while
/rebuild modifies or recreates the boot.ini.

Cheers,

Christian

instead of a bootcfg /scan
you might try
a bootcfg /rebuild instead:

here is more info:

http://support.microsoft.com/kb/314477


--

db·´¯`·...¸><)))º>

Hello everybody!

This problem happens to me for the 3rd time now and after two reinstalls I
really want to understand it this time. But after spending hours on Google
and newsgroups I'm not smarter than before. Maybe you experts can help...

Laptop, 1 hdd, 2 primary partitions holding one Windows XP each (I split
business and private XP). Dual booting work perfectly find until days ago.
Then, when trying to boot my 2ND !! installation (without any previous
error
or strange behaviour):

WINDOWS could not start because the following
file is missing or corrupt: <WINDOWS ROOT>\system 32\hal.dll
Please reinstall a copy of the above file.

The installation on the 1st partition still works fine.
The files on the 2nd partition are still present and accessible, but the XP
there doesn't start.

Boot.ini (on 1st partition) looks like this:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional"
/NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Private"
/noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

What I did so far:
1. compared hal.dll on 2nd partition with known good file from other
computer => exactly the same
2. compared ntdetect and ntldr on 1st partition with good files => they are
ok, too
3. used diskpart to check that I really have only 2 primary partitions with
numbers 1 and 2 => looks normal
4. used bootcfg /scan to see if both installations are detected => ONLY THE
1ST INSTALLATION IS DETECTED !!

I guess that means that somehow the hal.dll on the 2nd partition cannot be
loaded during boot, which causes the error message.

But why? The partition is there, hal.dll is there, boot.ini is complete and
looks perfectly fine...

Any ideas?

Can someone explain what exactly bootcfg looks for in order to detect a
windows installation? There must be some prerequesites that my 2nd
partition
doesn't meet anymore.

Thanks a lot for your help, much appreciated!!

Cheers,

Christian

 

[db.·.. >]

well, i don't think
that the bootcfg command
is the cure, just a convenient
method to fix a common
problem.

However you can go
to microsoft.com and
enter the command
in the search window
and to search the
knowledge base.

you can also go to the
newsgroup website and
enter the filename in
the search window to
search for similar posts
with issues like yours:

http://www.microsoft.com/windowsxp/...-8EB7A22FC6A0&dglist=&ptlist=&exp=&sloc=en-us

briefly, i found a link
from the above, that may
provide further help:

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

-----------
what might be a reasonable
idea to exercise is to boot
into your functional o.s. and
see if you can copy your
personal files off the dysfunctional
one.

this will help in providing
you some freedom to exercise
any methods for repairing that
o.s..
--

db·´¯`·...¸><)))º>

unfortunately i am short
on ideas because your configuration
and problem is something
i don't recall seeing or having.

Yeah, me neither. And I do have quite some experience in delivering
professional support for Windows based servers so I usually know where to
search. But this one.....

you did mention that you
compared the hal.dll files.
however, it may simply need
to be replaced.

Did a binary file compare, so they really should be ok, but nevertheless
replace them later yesterday. No effect whatsoever...

however, at this point it is unclear to
me if you can log into that
secondary o.s. via the command
console since i think you would
likely have to log into the
faulty installation in an
attempt to work on it.

Yes, I can. Actually, I tried the bootcfg /scan while being logged into the
first, working installation.
But to be sure I started recovery console again, logged into the 2nd (not
booting) installation, and did the bootcfg /rebuild you mentioned.
=> Still only the first installation is found!
Cool, I can log on to a windows that is not visible to bootcfg ;-\

it might simply be easier to do a
repair installation with
a windows setup cd, again
keeping in mind that you likely
used a cd to create a second
installation anyways.

I tried that the last time I had the issue without effect. As it would bring
all my windows files back to SP2 level I'm not really keen to try it again.
Of course I know that this wouldn't hurt my data (which is not in danger
anyway).


More and more I come to the conclusion that this is somehow related to the
partition.
But it would be very helpful to understand what bootcfg is looking for to
identify an installation. Could guide me to the source of the issue.

Thanks a lot for the effort,

Christian

Thanks for the answer!

I already tried that and it resulted in a boot.ini with only the
installation on the 1st partition being listed.

The way I understand the bootcfg documentation the detection mechanisms of
/scan and /rebuild are the same, but /scan only shows the results, while
/rebuild modifies or recreates the boot.ini.

Cheers,

Christian

:

instead of a bootcfg /scan
you might try
a bootcfg /rebuild instead:

here is more info:

http://support.microsoft.com/kb/314477


--

db·´¯`·...¸><)))º>

Hello everybody!

This problem happens to me for the 3rd time now and after two reinstalls
I
really want to understand it this time. But after spending hours on
Google
and newsgroups I'm not smarter than before. Maybe you experts can
help...

Laptop, 1 hdd, 2 primary partitions holding one Windows XP each (I split
business and private XP). Dual booting work perfectly find until days
ago.
Then, when trying to boot my 2ND !! installation (without any previous
error
or strange behaviour):

WINDOWS could not start because the following
file is missing or corrupt: <WINDOWS ROOT>\system 32\hal.dll
Please reinstall a copy of the above file.

The installation on the 1st partition still works fine.
The files on the 2nd partition are still present and accessible, but the
XP
there doesn't start.

Boot.ini (on 1st partition) looks like this:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional"
/NOEXECUTE=OPTIN /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Private"
/noexecute=optin /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons

What I did so far:
1. compared hal.dll on 2nd partition with known good file from other
computer => exactly the same
2. compared ntdetect and ntldr on 1st partition with good files => they
are
ok, too
3. used diskpart to check that I really have only 2 primary partitions
with
numbers 1 and 2 => looks normal
4. used bootcfg /scan to see if both installations are detected => ONLY
THE
1ST INSTALLATION IS DETECTED !!

I guess that means that somehow the hal.dll on the 2nd partition cannot
be
loaded during boot, which causes the error message.

But why? The partition is there, hal.dll is there, boot.ini is complete
and
looks perfectly fine...

Any ideas?

Can someone explain what exactly bootcfg looks for in order to detect a
windows installation? There must be some prerequesites that my 2nd
partition
doesn't meet anymore.

Thanks a lot for your help, much appreciated!!

Cheers,

Christian