R
RicardoUK
A friend recently got me to help with a problem that the PC would not
boot up - it had been working OK for quite a while.
It was stopping during boot sequence with the hal.dll missing or
corrupt message - so I booted up from the XP CD, went to recovery mode
and fixed it. When I originally did a bootcfg /list it said no entries,
so bootcfg /rebuild sorted the problem.
Now the question is what can cause this corruption? There's been no
mucking about with partitions, new disks or anything. There has been
one new app installed, but I don't think this would have mucked about
with boot.ini.
I've seen from various posts that other people get the problem
occasionally - but why?
boot up - it had been working OK for quite a while.
It was stopping during boot sequence with the hal.dll missing or
corrupt message - so I booted up from the XP CD, went to recovery mode
and fixed it. When I originally did a bootcfg /list it said no entries,
so bootcfg /rebuild sorted the problem.
Now the question is what can cause this corruption? There's been no
mucking about with partitions, new disks or anything. There has been
one new app installed, but I don't think this would have mucked about
with boot.ini.
I've seen from various posts that other people get the problem
occasionally - but why?