hal.dll

[Marty]

I have 2 bootable hard drives. One I use as a slave for backup. To try and
solve a problem with that one, I formatted the data partition and then copied
all the files from the other HDD using WD's "Data Lifeguard". Theoretically,
all the system files were copied to the bootable slave along with all the
application and data files. A cursory review of the contents of the drive
seems to confirm that. However, when I try to boot with that drive I get the
message, "Windows could not start because the file <Windows
Root>System32\hal.dll is missing or corrupt." (I assume <Windows Root> =
C:\Windows. Is that correct?) I then booted with the other drive, which makes
the slave Drive D: and checked in D:\Windows\System32 to see if the file was
missing. It was not. So I copied "HAL.DLL" from Drive C:\Windows\System32 and
pasted it into D:\Windows\System32 and tried again to boot with that drive as
primary. Same message. What if anything have I done wrong? Any and all advice
will be received with appreciation.

 

[JS]

Since you are trying to boot using the slave or D: drive (I am assuming the
C: drive is still installed and the drive jumpers are set as master and
slave) when the problem occurs.

First disconnect the data cable from the C: drive and change the jumper on
the D: drive from Slave to Master and see if the PC will boot.

Also check your Boot.ini file, is there one or two entries (drive 0 and a
drive 1)?

JS

 

[Touch Base]

I have 2 bootable hard drives. One I use as a slave for backup. To try and
solve a problem with that one, I formatted the data partition and then
copied
all the files from the other HDD using WD's "Data Lifeguard".
Theoretically,
all the system files were copied to the bootable slave along with all the
application and data files. A cursory review of the contents of the drive
seems to confirm that. However, when I try to boot with that drive I get
the
message, "Windows could not start because the file <Windows
Root>System32\hal.dll is missing or corrupt." (I assume <Windows Root> =
C:\Windows. Is that correct?) I then booted with the other drive, which
makes
the slave Drive D: and checked in D:\Windows\System32 to see if the file
was
missing. It was not. So I copied "HAL.DLL" from Drive C:\Windows\System32
and
pasted it into D:\Windows\System32 and tried again to boot with that drive
as
primary. Same message. What if anything have I done wrong? Any and all
advice
will be received with appreciation.

"HAL is Microsoft's abbreviation for the Hardware Abstraction Layer, the
technology and drivers that let the Windows NT, 2000, and XP operating
systems communicate with your PC's hardware."

As JS suggest check your boot.ini file

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

 

[Marty]

Sorry I didn't explain more exactly. I had done what you suggest.
Specifically, I disconnected the data cable from both drives, changed the
jumper on the D: drive to single without a slave, connected the data cable to
that drive only and tried to boot. That's how I discovered the problem.

At the moment I have both drives connected as master and slave. In that
configuration, the boot.ini file reads as follows:

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Whistler
Personal"/fastdetect /NoExecute=OptIn

Since the D: drive made C: will not boot, I can't check the boot.ini file on
it. Or can I?

Each drive has 2 partitions. One for HP Recovery (4.41 GB FAT 32) and the
other 32.86 GB with the C: drive as System and the D: drive for data backup.
Both are listed as "Healthy" by Computer Management.

 

[Marty]

Thanks for your reply. I had seen the info in Kelly's Corner. As I understand
it, that describes a dual boot situation on the same drive rather than 2
drives as with me. Actually, I'm not trying for a dual boot situation. Just
to have 2 bootable drives in case one crashes.

 

[JS]

This may help
"Invalid Boot.ini" or "Windows could not start" error messages when you
start your computer:
http://support.microsoft.com/kb/330184/en-us

Sample 'Dual Boot' Boot.ini file
[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="Windows XP Pro Drive1"
/fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP Pro Drive2"
/fastdetect

How to edit the Boot.ini file in Windows XP
See: http://support.microsoft.com/kb/289022/en-us
and: http://support.microsoft.com/kb/314081/en-us

Boot.ini switches explained:
http: http://www.microsoft.com/technet/sysinternals/information/bootini.mspx

JS

Sorry I didn't explain more exactly. I had done what you suggest.
Specifically, I disconnected the data cable from both drives, changed the
jumper on the D: drive to single without a slave, connected the data cable
to
that drive only and tried to boot. That's how I discovered the problem.

At the moment I have both drives connected as master and slave. In that
configuration, the boot.ini file reads as follows:

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Whistler
Personal"/fastdetect /NoExecute=OptIn

Since the D: drive made C: will not boot, I can't check the boot.ini file
on
it. Or can I?

Each drive has 2 partitions. One for HP Recovery (4.41 GB FAT 32) and the
other 32.86 GB with the C: drive as System and the D: drive for data
backup.
Both are listed as "Healthy" by Computer Management.

Since you are trying to boot using the slave or D: drive (I am assuming
the
C: drive is still installed and the drive jumpers are set as master and
slave) when the problem occurs.

First disconnect the data cable from the C: drive and change the jumper
on
the D: drive from Slave to Master and see if the PC will boot.

Also check your Boot.ini file, is there one or two entries (drive 0 and a
drive 1)?

JS

 

[Marty]

Thanks, JS! What the link instructs would no doubt help if I had an XP CD,
which I don't. I do have HP Recovery CD's, vintage 2001. I'll see if I can
make the boot.ini change with those. If not, I think I'll just leave it as it
is and be content to use the drive as a slave. I appreciate your responses.
Thank you very much.

This may help
"Invalid Boot.ini" or "Windows could not start" error messages when you
start your computer:
http://support.microsoft.com/kb/330184/en-us

Sample 'Dual Boot' Boot.ini file
[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="Windows XP Pro Drive1"
/fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP Pro Drive2"
/fastdetect

How to edit the Boot.ini file in Windows XP
See: http://support.microsoft.com/kb/289022/en-us
and: http://support.microsoft.com/kb/314081/en-us

Boot.ini switches explained:
http: http://www.microsoft.com/technet/sysinternals/information/bootini.mspx

JS

Sorry I didn't explain more exactly. I had done what you suggest.
Specifically, I disconnected the data cable from both drives, changed the
jumper on the D: drive to single without a slave, connected the data cable
to
that drive only and tried to boot. That's how I discovered the problem.

At the moment I have both drives connected as master and slave. In that
configuration, the boot.ini file reads as follows:

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Whistler
Personal"/fastdetect /NoExecute=OptIn

Since the D: drive made C: will not boot, I can't check the boot.ini file
on
it. Or can I?

Each drive has 2 partitions. One for HP Recovery (4.41 GB FAT 32) and the
other 32.86 GB with the C: drive as System and the D: drive for data
backup.
Both are listed as "Healthy" by Computer Management.

Since you are trying to boot using the slave or D: drive (I am assuming
the
C: drive is still installed and the drive jumpers are set as master and
slave) when the problem occurs.

First disconnect the data cable from the C: drive and change the jumper
on
the D: drive from Slave to Master and see if the PC will boot.

Also check your Boot.ini file, is there one or two entries (drive 0 and a
drive 1)?

JS

I have 2 bootable hard drives. One I use as a slave for backup. To try
and
solve a problem with that one, I formatted the data partition and then
copied
all the files from the other HDD using WD's "Data Lifeguard".
Theoretically,
all the system files were copied to the bootable slave along with all
the
application and data files. A cursory review of the contents of the
drive
seems to confirm that. However, when I try to boot with that drive I
get
the
message, "Windows could not start because the file <Windows
Root>System32\hal.dll is missing or corrupt." (I assume <Windows Root>
=
C:\Windows. Is that correct?) I then booted with the other drive, which
makes
the slave Drive D: and checked in D:\Windows\System32 to see if the
file
was
missing. It was not. So I copied "HAL.DLL" from Drive
C:\Windows\System32
and
pasted it into D:\Windows\System32 and tried again to boot with that
drive
as
primary. Same message. What if anything have I done wrong? Any and all
advice
will be received with appreciation.

 

[Marty]

Perhaps you can help me with another question. How can I reformat the drive
in question to erase the 2 partitions that are on it?

Thanks, JS! What the link instructs would no doubt help if I had an XP CD,
which I don't. I do have HP Recovery CD's, vintage 2001. I'll see if I can
make the boot.ini change with those. If not, I think I'll just leave it as it
is and be content to use the drive as a slave. I appreciate your responses.
Thank you very much.

This may help
"Invalid Boot.ini" or "Windows could not start" error messages when you
start your computer:
http://support.microsoft.com/kb/330184/en-us

Sample 'Dual Boot' Boot.ini file
[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="Windows XP Pro Drive1"
/fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP Pro Drive2"
/fastdetect

How to edit the Boot.ini file in Windows XP
See: http://support.microsoft.com/kb/289022/en-us
and: http://support.microsoft.com/kb/314081/en-us

Boot.ini switches explained:
http: http://www.microsoft.com/technet/sysinternals/information/bootini.mspx

JS

Sorry I didn't explain more exactly. I had done what you suggest.
Specifically, I disconnected the data cable from both drives, changed the
jumper on the D: drive to single without a slave, connected the data cable
to
that drive only and tried to boot. That's how I discovered the problem.

At the moment I have both drives connected as master and slave. In that
configuration, the boot.ini file reads as follows:

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Whistler
Personal"/fastdetect /NoExecute=OptIn

Since the D: drive made C: will not boot, I can't check the boot.ini file
on
it. Or can I?

Each drive has 2 partitions. One for HP Recovery (4.41 GB FAT 32) and the
other 32.86 GB with the C: drive as System and the D: drive for data
backup.
Both are listed as "Healthy" by Computer Management.

:

Since you are trying to boot using the slave or D: drive (I am assuming
the
C: drive is still installed and the drive jumpers are set as master and
slave) when the problem occurs.

First disconnect the data cable from the C: drive and change the jumper
on
the D: drive from Slave to Master and see if the PC will boot.

Also check your Boot.ini file, is there one or two entries (drive 0 and a
drive 1)?

JS

I have 2 bootable hard drives. One I use as a slave for backup. To try
and
solve a problem with that one, I formatted the data partition and then
copied
all the files from the other HDD using WD's "Data Lifeguard".
Theoretically,
all the system files were copied to the bootable slave along with all
the
application and data files. A cursory review of the contents of the
drive
seems to confirm that. However, when I try to boot with that drive I
get
the
message, "Windows could not start because the file <Windows
Root>System32\hal.dll is missing or corrupt." (I assume <Windows Root>
=
C:\Windows. Is that correct?) I then booted with the other drive, which
makes
the slave Drive D: and checked in D:\Windows\System32 to see if the
file
was
missing. It was not. So I copied "HAL.DLL" from Drive
C:\Windows\System32
and
pasted it into D:\Windows\System32 and tried again to boot with that
drive
as
primary. Same message. What if anything have I done wrong? Any and all
advice
will be received with appreciation.

 

[JS]

You don't need a CD, just use notepad to edit the boot.ini files for either
drive.

As to your second question:
You have two choices:
1) With only the drive you want to delete partitions connected use a
bootable CD of Data Lifeguard.
How do I create a Data Lifeguard diagnostics Bootable CD?
http://wdc.custhelp.com/cgi-bin/wdc...XJjaF90ZXh0PWJvb3RhYmxlIGNk&p_li=&p_topview=1
How to use Data Lifeguard to partition and format:
http://wdc.custhelp.com/cgi-bin/wdc...new_search=1&p_search_type=answers.search_fnl


2) If you want to delete the partitions on the Slave drive, boot to the
primary drive (be absolutely certain of this)
and the use Windows's 'Disk Management's tools.

To format a drive go to Disk Management on your Windows PC, (right click on
the My Computer
icon, then select the Manage option, then in the Computer Management window
select Disk Management).

For more details on formatting see:
http://support.microsoft.com/kb/309000/en-us

JS

Thanks, JS! What the link instructs would no doubt help if I had an XP CD,
which I don't. I do have HP Recovery CD's, vintage 2001. I'll see if I can
make the boot.ini change with those. If not, I think I'll just leave it as
it
is and be content to use the drive as a slave. I appreciate your
responses.
Thank you very much.

This may help
"Invalid Boot.ini" or "Windows could not start" error messages when you
start your computer:
http://support.microsoft.com/kb/330184/en-us

Sample 'Dual Boot' Boot.ini file
[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="Windows XP Pro Drive1"
/fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP Pro Drive2"
/fastdetect

How to edit the Boot.ini file in Windows XP
See: http://support.microsoft.com/kb/289022/en-us
and: http://support.microsoft.com/kb/314081/en-us

Boot.ini switches explained:
http:
http://www.microsoft.com/technet/sysinternals/information/bootini.mspx

JS

Sorry I didn't explain more exactly. I had done what you suggest.
Specifically, I disconnected the data cable from both drives, changed
the
jumper on the D: drive to single without a slave, connected the data
cable
to
that drive only and tried to boot. That's how I discovered the problem.

At the moment I have both drives connected as master and slave. In that
configuration, the boot.ini file reads as follows:

[boot loader]
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Whistler
Personal"/fastdetect /NoExecute=OptIn

Since the D: drive made C: will not boot, I can't check the boot.ini
file
on
it. Or can I?

Each drive has 2 partitions. One for HP Recovery (4.41 GB FAT 32) and
the
other 32.86 GB with the C: drive as System and the D: drive for data
backup.
Both are listed as "Healthy" by Computer Management.

:

Since you are trying to boot using the slave or D: drive (I am
assuming
the
C: drive is still installed and the drive jumpers are set as master
and
slave) when the problem occurs.

First disconnect the data cable from the C: drive and change the
jumper
on
the D: drive from Slave to Master and see if the PC will boot.

Also check your Boot.ini file, is there one or two entries (drive 0
and a
drive 1)?

JS

I have 2 bootable hard drives. One I use as a slave for backup. To
try
and
solve a problem with that one, I formatted the data partition and
then
copied
all the files from the other HDD using WD's "Data Lifeguard".
Theoretically,
all the system files were copied to the bootable slave along with
all
the
application and data files. A cursory review of the contents of the
drive
seems to confirm that. However, when I try to boot with that drive I
get
the
message, "Windows could not start because the file <Windows
Root>System32\hal.dll is missing or corrupt." (I assume <Windows
Root>
=
C:\Windows. Is that correct?) I then booted with the other drive,
which
makes
the slave Drive D: and checked in D:\Windows\System32 to see if the
file
was
missing. It was not. So I copied "HAL.DLL" from Drive
C:\Windows\System32
and
pasted it into D:\Windows\System32 and tried again to boot with that
drive
as
primary. Same message. What if anything have I done wrong? Any and
all
advice
will be received with appreciation.

 

[Lil' Dave]

Just a few comments.

Boot.ini is sought and acted upon well before ntldr looks for ntoskrnl.exe
and hal.dll.

The PBR and disk signature in it should be identical, otherwise some things
will foul up as result.

--
Dave

Hypocrisy. Big SUV, filament lights on all night. You think your neighbor
should be changiing to compact fluorescent light bulbs and driving the
hybrid.