I have a Windows XP Pro PC that has the error like "boot.ini missing" then
says the hal.dll is corrupted.

I use the XP CD to boot into the Recovery Console and did bootcfg /rebuild.
It then booted into Windows XP. I unchecked the hide system files but cannot
find the boot.ini file on the C:\. I then copied the boot.ini file from
another XP PC but got the same error after rebooting.

I ran the bootcfg /rebuild again and found that the boot.ini file is not on
C:\. What is the problem and how can I keep the boot.ini file from deleting
by itself.

thanks.

what you might have
is a dirty file system
which is causing the
master file table to
be unsynchronized
with your files.

try booting up with
a windows cd and
initiating the repair/
recovery console.

then at the disk prompt
run chkdsk /p

incidentally, hal.dll
errors usually result
by having to o.s.'s
installed on the same
disk.

if you have more than
one o.s. per disk, then
you will always have
some kind of conflict
or corruption.

--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- Microsoft Partner
- @hotmail.com
~~~~~~~~~~"share the nirvana" - dbZen

>
>

"wli2k2" <(E-Mail Removed)> wrote in message news:BA5BA6CD-1A5B-4C2C-ABE4-(E-Mail Removed)...
> I have a Windows XP Pro PC that has the error like "boot.ini missing" then
> says the hal.dll is corrupted.
>
> I use the XP CD to boot into the Recovery Console and did bootcfg /rebuild.
> It then booted into Windows XP. I unchecked the hide system files but cannot
> find the boot.ini file on the C:\. I then copied the boot.ini file from
> another XP PC but got the same error after rebooting.
>
> I ran the bootcfg /rebuild again and found that the boot.ini file is not on
> C:\. What is the problem and how can I keep the boot.ini file from deleting
> by itself.
>
> thanks.

In addition to the most helpful advice posted by "db", I would just like
to remind you that you need to have the option to 'Hide protected
operating system files (Recommended)' is also unchecked to be able to
see your boot.ini file.

I don't doubt you when you say it is being deleted, but you might not
realize when the problem is sorted unless you uncheck this option in the
'Folder Options' control panel.

As "db" says; run chkdsk /p from the 'Recovery Console'

==

Cheers, Tim Meddick, Peckham, London. :-)




"wli2k2" <(E-Mail Removed)> wrote in message
news:BA5BA6CD-1A5B-4C2C-ABE4-(E-Mail Removed)...
>I have a Windows XP Pro PC that has the error like "boot.ini missing"
>then
> says the hal.dll is corrupted.
>
> I use the XP CD to boot into the Recovery Console and did bootcfg
> /rebuild.
> It then booted into Windows XP. I unchecked the hide system files but
> cannot
> find the boot.ini file on the C:\. I then copied the boot.ini file
> from
> another XP PC but got the same error after rebooting.
>
> I ran the bootcfg /rebuild again and found that the boot.ini file is
> not on
> C:\. What is the problem and how can I keep the boot.ini file from
> deleting
> by itself.
>
> thanks.

"db" <databaseben at hotmail dot com> wrote in message
news:7E7E9850-B55D-46A1-BA5E-(E-Mail Removed)...
> what you might have
> is a dirty file system
> which is causing the
> master file table to
> be unsynchronized
> with your files.
>
> try booting up with
> a windows cd and
> initiating the repair/
> recovery console.
>
> then at the disk prompt
> run chkdsk /p
>
> incidentally, hal.dll
> errors usually result
> by having to o.s.'s
> installed on the same
> disk.
>
> if you have more than
> one o.s. per disk, then
> you will always have
> some kind of conflict
> or corruption.
>
> --
>
> db·´¯`·...¸><)))º>
> DatabaseBen, Retired Professional
> - Systems Analyst
> - Database Developer
> - Accountancy
> - Veteran of the Armed Forces
> - Microsoft Partner
> - @hotmail.com
> ~~~~~~~~~~"share the nirvana" - dbZen
>
>>
>>
Shouldn't that be, "more than one OS per disk or partition?"






>
> "wli2k2" <(E-Mail Removed)> wrote in message
> news:BA5BA6CD-1A5B-4C2C-ABE4-(E-Mail Removed)...
>> I have a Windows XP Pro PC that has the error like "boot.ini missing"
>> then
>> says the hal.dll is corrupted.
>>
>> I use the XP CD to boot into the Recovery Console and did bootcfg
>> /rebuild.
>> It then booted into Windows XP. I unchecked the hide system files but
>> cannot
>> find the boot.ini file on the C:\. I then copied the boot.ini file from
>> another XP PC but got the same error after rebooting.
>>
>> I ran the bootcfg /rebuild again and found that the boot.ini file is not
>> on
>> C:\. What is the problem and how can I keep the boot.ini file from
>> deleting
>> by itself.
>>
>> thanks.
>

db wrote:

> incidentally, hal.dll
> errors usually result
> by having to o.s.'s
> installed on the same
> disk.
>
> if you have more than
> one o.s. per disk, then
> you will always have
> some kind of conflict
> or corruption.

Not true at all.

John

wli2k2 wrote:

> I ran the bootcfg /rebuild again and found that the boot.ini file is not on
> C:\. What is the problem and how can I keep the boot.ini file from deleting
> by itself.

Are you sure that C: is the partition which contains the boot-files?

John John - MVP wrote:
> db wrote:
>
>> incidentally, hal.dll
>> errors usually result
>> by having to o.s.'s
>> installed on the same
>> disk.
>>
>> if you have more than
>> one o.s. per disk, then
>> you will always have
>> some kind of conflict
>> or corruption.
>
> Not true at all.

I must agree with John. Having a boot.ini pointing to the wrong place
results in such a hal-error.

its safer to have one
o.s. per disk.

of course you can
attempt to install
more than one o.s.
on one disk.

but ultimately and
unexpectedly,
something will fail
causing the hal
error.

another safe method
to install more than one
o.s. on one disk is to use
virtual pc or virtual box

the virtualization of
additional o.s's will
keep the primary o.s.
from becoming corrupt.



db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- Microsoft Partner
- @hotmail.com
~~~~~~~~~~"share the nirvana" - dbZen

>
>

"Ian D" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>
> "db" <databaseben at hotmail dot com> wrote in message news:7E7E9850-B55D-46A1-BA5E-(E-Mail Removed)...
>> what you might have
>> is a dirty file system
>> which is causing the
>> master file table to
>> be unsynchronized
>> with your files.
>>
>> try booting up with
>> a windows cd and
>> initiating the repair/
>> recovery console.
>>
>> then at the disk prompt
>> run chkdsk /p
>>
>> incidentally, hal.dll
>> errors usually result
>> by having to o.s.'s
>> installed on the same
>> disk.
>>
>> if you have more than
>> one o.s. per disk, then
>> you will always have
>> some kind of conflict
>> or corruption.
>>
>> --
>>
>> db·´¯`·...¸><)))º>
>> DatabaseBen, Retired Professional
>> - Systems Analyst
>> - Database Developer
>> - Accountancy
>> - Veteran of the Armed Forces
>> - Microsoft Partner
>> - @hotmail.com
>> ~~~~~~~~~~"share the nirvana" - dbZen
>>
>>>
>>>
> Shouldn't that be, "more than one OS per disk or partition?"
>
>
>
>
>
>
>>
>> "wli2k2" <(E-Mail Removed)> wrote in message news:BA5BA6CD-1A5B-4C2C-ABE4-(E-Mail Removed)...
>>> I have a Windows XP Pro PC that has the error like "boot.ini missing" then
>>> says the hal.dll is corrupted.
>>>
>>> I use the XP CD to boot into the Recovery Console and did bootcfg /rebuild.
>>> It then booted into Windows XP. I unchecked the hide system files but cannot
>>> find the boot.ini file on the C:\. I then copied the boot.ini file from
>>> another XP PC but got the same error after rebooting.
>>>
>>> I ran the bootcfg /rebuild again and found that the boot.ini file is not on
>>> C:\. What is the problem and how can I keep the boot.ini file from deleting
>>> by itself.
>>>
>>> thanks.
>>
>
>

db wrote:
> its safer to have one
> o.s. per disk.
>
> of course you can
> attempt to install
> more than one o.s.
> on one disk.
>
> but ultimately and
> unexpectedly,
> something will fail
> causing the hal
> error.

That is nothing but BS. Having more than one operating system on one
disk will not ultimately and unexpectedly cause anything to to fail and
cause hal errors. Disks with single operating systems get as many of
these errors as do disk with multiple operating systems. Millions of
people have been running multi-operating system disks for years without
ever having a single hal error.

John

your wrong and
a moron too.


--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- Microsoft Partner
- @hotmail.com
~~~~~~~~~~"share the nirvana" - dbZen

>
>

"John John - MVP" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> db wrote:
>> its safer to have one
>> o.s. per disk.
>>
>> of course you can
>> attempt to install
>> more than one o.s.
>> on one disk.
>>
>> but ultimately and
>> unexpectedly,
>> something will fail
>> causing the hal
>> error.
>
> That is nothing but BS. Having more than one operating system on one disk will not ultimately and unexpectedly cause anything to
> to fail and cause hal errors. Disks with single operating systems get as many of these errors as do disk with multiple operating
> systems. Millions of people have been running multi-operating system disks for years without ever having a single hal error.
>
> John