Missing / Corrupt hal.dll...Bad Boot.ini

I had a backup machine that I inadvently installed 2 copies of Win Home XP
on. I decided to clean things up, and now have a problem. I installed SP2,
and removed the 2nd version based on an article I found in the Knowledge
Base. Lastly, I edited the Boot.ini according to the instructions. When I
reboot my machine I get the following error at the DOS prompt:
<Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
installed.

Someone suggested that I download the Windows XP 6-disk restore set, which I
did. When I run it, the 2nd disk produces the following error message:
'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
database which suggested that I select the install SCSI driver, and then
by-pass by clicking F7. The restore software ignores installing the SCSI and
just terminates back to DOS.

Does anyone have a suggestion beyond re-formatting the drive?

Thanks, Steve

Do you have a retail or MFG OEM Win XP version?
boot to the win xp cd. select repair "R" for recovery console.
At command prompt> bootcfg /rebuild

The bootcfg /rebuild command scans the hard disks of the computer for
Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
the results. You can add the detected Windows installations.

You may receive a message that is similar to the following message:
Total Identified Windows Installs: 2

[1] C:\Windows
Add installation to boot list? (Yes/No/All):
Enter Load Identifier: (Custom description for an operating system loading
from the Boot menu)
Enter Operating System Load Options: (that is: /fastdetect)

[2] D:\Windows
Add installation to boot list? (Yes/No/All):
Enter Load Identifier: (Custom description for an operating system loading
from the Boot menu)
Enter Operating System Load Options: (that is: /fastdetect)

should do it!!

"Steve" wrote:

> I had a backup machine that I inadvently installed 2 copies of Win Home XP
> on. I decided to clean things up, and now have a problem. I installed SP2,
> and removed the 2nd version based on an article I found in the Knowledge
> Base. Lastly, I edited the Boot.ini according to the instructions. When I
> reboot my machine I get the following error at the DOS prompt:
> <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> installed.
>
> Someone suggested that I download the Windows XP 6-disk restore set, which I
> did. When I run it, the 2nd disk produces the following error message:
> 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> database which suggested that I select the install SCSI driver, and then
> by-pass by clicking F7. The restore software ignores installing the SCSI and
> just terminates back to DOS.
>
> Does anyone have a suggestion beyond re-formatting the drive?
>
> Thanks, Steve
>

I forgot to mention that the system won't boot from the CD (I happen to have
MFG OEM versions). Regardless of whether the CDROM is even 1st in order, it
won't start the CD up. Thanks

"Dixonian69" wrote:

> Do you have a retail or MFG OEM Win XP version?
> boot to the win xp cd. select repair "R" for recovery console.
> At command prompt> bootcfg /rebuild
>
> The bootcfg /rebuild command scans the hard disks of the computer for
> Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
> the results. You can add the detected Windows installations.
>
> You may receive a message that is similar to the following message:
> Total Identified Windows Installs: 2
>
> [1] C:\Windows
> Add installation to boot list? (Yes/No/All):
> Enter Load Identifier: (Custom description for an operating system loading
> from the Boot menu)
> Enter Operating System Load Options: (that is: /fastdetect)
>
> [2] D:\Windows
> Add installation to boot list? (Yes/No/All):
> Enter Load Identifier: (Custom description for an operating system loading
> from the Boot menu)
> Enter Operating System Load Options: (that is: /fastdetect)
>
> should do it!!
>
> "Steve" wrote:
>
> > I had a backup machine that I inadvently installed 2 copies of Win Home XP
> > on. I decided to clean things up, and now have a problem. I installed SP2,
> > and removed the 2nd version based on an article I found in the Knowledge
> > Base. Lastly, I edited the Boot.ini according to the instructions. When I
> > reboot my machine I get the following error at the DOS prompt:
> > <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> > Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> > installed.
> >
> > Someone suggested that I download the Windows XP 6-disk restore set, which I
> > did. When I run it, the 2nd disk produces the following error message:
> > 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> > database which suggested that I select the install SCSI driver, and then
> > by-pass by clicking F7. The restore software ignores installing the SCSI and
> > just terminates back to DOS.
> >
> > Does anyone have a suggestion beyond re-formatting the drive?
> >
> > Thanks, Steve
> >

do you have a floppy drive and another working xp computer??
format a floppy. copy ntldr, ntdetect.com, and boot.ini files to floppy disk
and boot from floppy drive.

or go to www.bootdisk.com and download XP Quick boot file. then do the same.

once booted up, repair your boot.ini file!!

"Steve" wrote:

> I forgot to mention that the system won't boot from the CD (I happen to have
> MFG OEM versions). Regardless of whether the CDROM is even 1st in order, it
> won't start the CD up. Thanks
>
> "Dixonian69" wrote:
>
> > Do you have a retail or MFG OEM Win XP version?
> > boot to the win xp cd. select repair "R" for recovery console.
> > At command prompt> bootcfg /rebuild
> >
> > The bootcfg /rebuild command scans the hard disks of the computer for
> > Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
> > the results. You can add the detected Windows installations.
> >
> > You may receive a message that is similar to the following message:
> > Total Identified Windows Installs: 2
> >
> > [1] C:\Windows
> > Add installation to boot list? (Yes/No/All):
> > Enter Load Identifier: (Custom description for an operating system loading
> > from the Boot menu)
> > Enter Operating System Load Options: (that is: /fastdetect)
> >
> > [2] D:\Windows
> > Add installation to boot list? (Yes/No/All):
> > Enter Load Identifier: (Custom description for an operating system loading
> > from the Boot menu)
> > Enter Operating System Load Options: (that is: /fastdetect)
> >
> > should do it!!
> >
> > "Steve" wrote:
> >
> > > I had a backup machine that I inadvently installed 2 copies of Win Home XP
> > > on. I decided to clean things up, and now have a problem. I installed SP2,
> > > and removed the 2nd version based on an article I found in the Knowledge
> > > Base. Lastly, I edited the Boot.ini according to the instructions. When I
> > > reboot my machine I get the following error at the DOS prompt:
> > > <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> > > Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> > > installed.
> > >
> > > Someone suggested that I download the Windows XP 6-disk restore set, which I
> > > did. When I run it, the 2nd disk produces the following error message:
> > > 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> > > database which suggested that I select the install SCSI driver, and then
> > > by-pass by clicking F7. The restore software ignores installing the SCSI and
> > > just terminates back to DOS.
> > >
> > > Does anyone have a suggestion beyond re-formatting the drive?
> > >
> > > Thanks, Steve
> > >

Hi, I'm not sure you will have the answer to this. I heard on "marketplace,"
a program on NPRadio today that Microsoft has a flaw that could allow viruses
and other bad things to enter our computers. They are supposedly trying to
work on a patch. I'm not a technologically savvy person, but I want to
protect my computer. I have windows xp. I am trying to find out about this
problem. I went to microsoft for updates and didn't see anything about this!
Can you imagine? Please respond if you know what to do. Thanks, JB
--
JB


"Dixonian69" wrote:

> do you have a floppy drive and another working xp computer??
> format a floppy. copy ntldr, ntdetect.com, and boot.ini files to floppy disk
> and boot from floppy drive.
>
> or go to www.bootdisk.com and download XP Quick boot file. then do the same.
>
> once booted up, repair your boot.ini file!!
>
> "Steve" wrote:
>
> > I forgot to mention that the system won't boot from the CD (I happen to have
> > MFG OEM versions). Regardless of whether the CDROM is even 1st in order, it
> > won't start the CD up. Thanks
> >
> > "Dixonian69" wrote:
> >
> > > Do you have a retail or MFG OEM Win XP version?
> > > boot to the win xp cd. select repair "R" for recovery console.
> > > At command prompt> bootcfg /rebuild
> > >
> > > The bootcfg /rebuild command scans the hard disks of the computer for
> > > Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
> > > the results. You can add the detected Windows installations.
> > >
> > > You may receive a message that is similar to the following message:
> > > Total Identified Windows Installs: 2
> > >
> > > [1] C:\Windows
> > > Add installation to boot list? (Yes/No/All):
> > > Enter Load Identifier: (Custom description for an operating system loading
> > > from the Boot menu)
> > > Enter Operating System Load Options: (that is: /fastdetect)
> > >
> > > [2] D:\Windows
> > > Add installation to boot list? (Yes/No/All):
> > > Enter Load Identifier: (Custom description for an operating system loading
> > > from the Boot menu)
> > > Enter Operating System Load Options: (that is: /fastdetect)
> > >
> > > should do it!!
> > >
> > > "Steve" wrote:
> > >
> > > > I had a backup machine that I inadvently installed 2 copies of Win Home XP
> > > > on. I decided to clean things up, and now have a problem. I installed SP2,
> > > > and removed the 2nd version based on an article I found in the Knowledge
> > > > Base. Lastly, I edited the Boot.ini according to the instructions. When I
> > > > reboot my machine I get the following error at the DOS prompt:
> > > > <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> > > > Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> > > > installed.
> > > >
> > > > Someone suggested that I download the Windows XP 6-disk restore set, which I
> > > > did. When I run it, the 2nd disk produces the following error message:
> > > > 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> > > > database which suggested that I select the install SCSI driver, and then
> > > > by-pass by clicking F7. The restore software ignores installing the SCSI and
> > > > just terminates back to DOS.
> > > >
> > > > Does anyone have a suggestion beyond re-formatting the drive?
> > > >
> > > > Thanks, Steve
> > > >

Of course you didn't enlightnen us on what you heard!!!
Which makes it real difficult to respond, too!!!
at least nothing at all specific!!

one other post said something about ther being a possible threat when using
Windows viewer program!!

Is this what you're talking ABOUT??

http://www.theregister.co.uk/2005/12..._trojan_alert/

The WMF vulnerability exists in computers running Microsoft Windows XP with
SP1 and SP2, and Microsoft Windows Server 2003 and stems from a flaw in a
utility used to view picture and fax files. The security flaw might be
exploited by inducing victims to view maliciously constructed sites,
particularly where IE is used as a browser, or when previewing *.wmf format
files with Windows Explorer.

How do I turn off the Windows Picture and Fax Viewer as my default image
viewer?

http://www.annoyances.org/exec/show/article03-201





"accursed B" wrote:

> Hi, I'm not sure you will have the answer to this. I heard on "marketplace,"
> a program on NPRadio today that Microsoft has a flaw that could allow viruses
> and other bad things to enter our computers. They are supposedly trying to
> work on a patch. I'm not a technologically savvy person, but I want to
> protect my computer. I have windows xp. I am trying to find out about this
> problem. I went to microsoft for updates and didn't see anything about this!
> Can you imagine? Please respond if you know what to do. Thanks, JB
> --
> JB
>
>
> "Dixonian69" wrote:
>
> > do you have a floppy drive and another working xp computer??
> > format a floppy. copy ntldr, ntdetect.com, and boot.ini files to floppy disk
> > and boot from floppy drive.
> >
> > or go to www.bootdisk.com and download XP Quick boot file. then do the same.
> >
> > once booted up, repair your boot.ini file!!
> >
> > "Steve" wrote:
> >
> > > I forgot to mention that the system won't boot from the CD (I happen to have
> > > MFG OEM versions). Regardless of whether the CDROM is even 1st in order, it
> > > won't start the CD up. Thanks
> > >
> > > "Dixonian69" wrote:
> > >
> > > > Do you have a retail or MFG OEM Win XP version?
> > > > boot to the win xp cd. select repair "R" for recovery console.
> > > > At command prompt> bootcfg /rebuild
> > > >
> > > > The bootcfg /rebuild command scans the hard disks of the computer for
> > > > Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
> > > > the results. You can add the detected Windows installations.
> > > >
> > > > You may receive a message that is similar to the following message:
> > > > Total Identified Windows Installs: 2
> > > >
> > > > [1] C:\Windows
> > > > Add installation to boot list? (Yes/No/All):
> > > > Enter Load Identifier: (Custom description for an operating system loading
> > > > from the Boot menu)
> > > > Enter Operating System Load Options: (that is: /fastdetect)
> > > >
> > > > [2] D:\Windows
> > > > Add installation to boot list? (Yes/No/All):
> > > > Enter Load Identifier: (Custom description for an operating system loading
> > > > from the Boot menu)
> > > > Enter Operating System Load Options: (that is: /fastdetect)
> > > >
> > > > should do it!!
> > > >
> > > > "Steve" wrote:
> > > >
> > > > > I had a backup machine that I inadvently installed 2 copies of Win Home XP
> > > > > on. I decided to clean things up, and now have a problem. I installed SP2,
> > > > > and removed the 2nd version based on an article I found in the Knowledge
> > > > > Base. Lastly, I edited the Boot.ini according to the instructions. When I
> > > > > reboot my machine I get the following error at the DOS prompt:
> > > > > <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> > > > > Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> > > > > installed.
> > > > >
> > > > > Someone suggested that I download the Windows XP 6-disk restore set, which I
> > > > > did. When I run it, the 2nd disk produces the following error message:
> > > > > 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> > > > > database which suggested that I select the install SCSI driver, and then
> > > > > by-pass by clicking F7. The restore software ignores installing the SCSI and
> > > > > just terminates back to DOS.
> > > > >
> > > > > Does anyone have a suggestion beyond re-formatting the drive?
> > > > >
> > > > > Thanks, Steve
> > > > >

steve-u could try a floppy startup bootdisk from bootdisk.com, which will
load drivers for the cd and force it to work--ive also had luck with bootit
partition utility--just install it from the floppy version and leave the
partitions alone, and it will act like an interface between. when i had
errors and not booting and such, somehow bootit managed to start xp--or if it
wont start, if u wanted, u could partition, install some os, and get your
files over to it, or another hd, if you get my drift--its a long way around
and probebly not addressing whats wrong, but its one way u could at least not
lose all your personal files. im no expert, but it saved me from loseing
160gb of files

"Steve" wrote:

> I had a backup machine that I inadvently installed 2 copies of Win Home XP
> on. I decided to clean things up, and now have a problem. I installed SP2,
> and removed the 2nd version based on an article I found in the Knowledge
> Base. Lastly, I edited the Boot.ini according to the instructions. When I
> reboot my machine I get the following error at the DOS prompt:
> <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> installed.
>
> Someone suggested that I download the Windows XP 6-disk restore set, which I
> did. When I run it, the 2nd disk produces the following error message:
> 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> database which suggested that I select the install SCSI driver, and then
> by-pass by clicking F7. The restore software ignores installing the SCSI and
> just terminates back to DOS.
>
> Does anyone have a suggestion beyond re-formatting the drive?
>
> Thanks, Steve
>

also steve i could be wrong, but if u can get your cd to work with a
bootdisk, if u tell xp to just reinstall, but not totally reformat, im not so
sure you would lose your files, but i wouldnt try it unless you can find out
for sure

"Steve" wrote:

> I had a backup machine that I inadvently installed 2 copies of Win Home XP
> on. I decided to clean things up, and now have a problem. I installed SP2,
> and removed the 2nd version based on an article I found in the Knowledge
> Base. Lastly, I edited the Boot.ini according to the instructions. When I
> reboot my machine I get the following error at the DOS prompt:
> <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> installed.
>
> Someone suggested that I download the Windows XP 6-disk restore set, which I
> did. When I run it, the 2nd disk produces the following error message:
> 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> database which suggested that I select the install SCSI driver, and then
> by-pass by clicking F7. The restore software ignores installing the SCSI and
> just terminates back to DOS.
>
> Does anyone have a suggestion beyond re-formatting the drive?
>
> Thanks, Steve
>

accursed B wrote:

> Hi, I'm not sure you will have the answer to this. I heard on
> "marketplace," a program on NPRadio today that Microsoft has a flaw
> that could allow viruses and other bad things to enter our computers.
> They are supposedly trying to work on a patch. I'm not a
> technologically savvy person, but I want to protect my computer. I
> have windows xp. I am trying to find out about this problem. I went
> to microsoft for updates and didn't see anything about this! Can you
> imagine? Please respond if you know what to do. Thanks, JB


You are presumably talking about this:
http://www.microsoft.com/technet/sec...ry/912840.mspx

Also read here:
http://sunbeltblog.blogspot.com/2005...f-exploit.html


--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

I am having a similar problem. Tried the simple sets you oulined, but the
bootcfg /rebuild fails with a message "error: falied to successfully scan
disk ...." Use chkdsk to detect any disk errors" I've already tried the
chkdsk with and without the /p and /r flags, both apparently have no affect.
Any suggestions.

Tom


"Dixonian69" wrote:

> do you have a floppy drive and another working xp computer??
> format a floppy. copy ntldr, ntdetect.com, and boot.ini files to floppy disk
> and boot from floppy drive.
>
> or go to www.bootdisk.com and download XP Quick boot file. then do the same.
>
> once booted up, repair your boot.ini file!!
>
> "Steve" wrote:
>
> > I forgot to mention that the system won't boot from the CD (I happen to have
> > MFG OEM versions). Regardless of whether the CDROM is even 1st in order, it
> > won't start the CD up. Thanks
> >
> > "Dixonian69" wrote:
> >
> > > Do you have a retail or MFG OEM Win XP version?
> > > boot to the win xp cd. select repair "R" for recovery console.
> > > At command prompt> bootcfg /rebuild
> > >
> > > The bootcfg /rebuild command scans the hard disks of the computer for
> > > Windows NT 4.0, Windows 2000, or Windows XP installations, and then displays
> > > the results. You can add the detected Windows installations.
> > >
> > > You may receive a message that is similar to the following message:
> > > Total Identified Windows Installs: 2
> > >
> > > [1] C:\Windows
> > > Add installation to boot list? (Yes/No/All):
> > > Enter Load Identifier: (Custom description for an operating system loading
> > > from the Boot menu)
> > > Enter Operating System Load Options: (that is: /fastdetect)
> > >
> > > [2] D:\Windows
> > > Add installation to boot list? (Yes/No/All):
> > > Enter Load Identifier: (Custom description for an operating system loading
> > > from the Boot menu)
> > > Enter Operating System Load Options: (that is: /fastdetect)
> > >
> > > should do it!!
> > >
> > > "Steve" wrote:
> > >
> > > > I had a backup machine that I inadvently installed 2 copies of Win Home XP
> > > > on. I decided to clean things up, and now have a problem. I installed SP2,
> > > > and removed the 2nd version based on an article I found in the Knowledge
> > > > Base. Lastly, I edited the Boot.ini according to the instructions. When I
> > > > reboot my machine I get the following error at the DOS prompt:
> > > > <Windows Root>\system32\hal.dll is missing or corrupt. More likely, the
> > > > Boot.ini is probably the corrupt file, but I can't get to it since NTFS is
> > > > installed.
> > > >
> > > > Someone suggested that I download the Windows XP 6-disk restore set, which I
> > > > did. When I run it, the 2nd disk produces the following error message:
> > > > 'File /ntkrnlmp.exe can be loaded- error Code 7'. I looked in the tech
> > > > database which suggested that I select the install SCSI driver, and then
> > > > by-pass by clicking F7. The restore software ignores installing the SCSI and
> > > > just terminates back to DOS.
> > > >
> > > > Does anyone have a suggestion beyond re-formatting the drive?
> > > >
> > > > Thanks, Steve
> > > >