boot.ini deleting by itself

[wli2k2]

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]

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

 

[Tim Meddick]

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.

 

[Ian D]

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?"

 

[John John - MVP]

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

 

[dennis]

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?

 

[dennis]

Not true at all.

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

 

[db]

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

 

[John John - MVP]

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

 

[db]

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

 

[Peter Foldes]

See the following. It applies to your issue

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

 

[dennis]

your wrong and
a moron too.

He is not wrong.

 

[John John - MVP]

How funny. As usual you don't know what you are talking about, it isn't
surprising as we have gotten used to your nonsense and your posts full
of silly advice an erroneous information.

 

[db]

actually, for an mvp
you are utterly pathetic

perhaps, you should
simply learn to shut up
and post your own
suggestions instead
of being an ass.
--

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

 

[Unknown]

Actually for a retired professional you're kidding yourself.

 

[Unknown]

Why is it a retired 'professional', system analyst, database developer,
veteran, has to resort to name calling?
That is an indication of your personality and, I might add, it stinks.

 

[Peter Gray]

I think I may have found a lot of the cause of this.

I have three clients systems all of which are exhibiting this problem. I've
checked to see what's happening and find that the boot.ini is being deleted
as part of the start up.

Next all three have recently had IE8 installed. One is a MEdia Center, One
an XP Jome and one an XP Pro. I've removed IE8 from two of them and the
problem has disappeared!!

I'm keeping the third machine for a sort while to see if I can find out if
it's a fault in the IE8 installation or a hijack which is using IE8 to
deliver.

The machines have been removed from the internet and still showed this
symptom - so if it is an exploit it's embedded and using the presence of IE8.

Hope this helps

I'm still checking

 

[Jose]

I think I may have found a lot of the cause of this.

I have three clients systems all of which are exhibiting this problem. I've
checked to see what's happening and find that the boot.ini is being deleted
as part of the start up.

Next all three have recently had IE8 installed. One is a MEdia Center, One
an XP Jome and one an XP Pro. I've removed IE8 from two of them and the
problem has disappeared!!

I'm keeping the third machine for a sort while to see if I can find out if
it's a fault in the IE8 installation or a hijack which is using IE8 to
deliver.

The machines have been removed from the internet and still showed this
symptom - so if it is an exploit it's embedded and using the presence of IE8.

Hope this helps

I'm still checking

See if this information applies to your situation.

I have not tried it (and don't intend to), but these folks seem
convinced as to why their boot.ini disappears, and some other poster
pinned the issue on the same environment which led me to the following
link.

It is funny that the vendor vehemently denies it, for a little
while...

http://forum.applian.com/showthread.php?p=8321

 

[wli2k2]

IE8 is the culpit. Removing it fixed the problem.

 

[Jose]

IE8 is the culpit.  Removing it fixed the problem.

Have you concluded that if IE8 is installed, the boot.ini file will be
deleted on a reboot?