boot.ini on WRONG drive corrected!

  • Thread starter Thread starter npharrison
  • Start date Start date
N

npharrison

Hope someone can help.

I managed to have a power outage and when I switched on my pc I got the
following message:

"Windows could not start because the following file is missing or corrrupt.
Windows\system\hal.dll"

So I went on my son's pc and found Article ID: 945380.

I followed that. Did chkdsk /r and after several hours it finished, but
apart from file allocation tables, didn't report if anything had changed.
This was from the Method/Problem 2 section. So I moved onto Method/Problem 3,
using bootcfg and eventually Windows started and the disk loaded.

However, to my astonishment it was the wrong one!

I've got 2 drives, a 160Gb and a 30Gb. And the repair console had detected
the slave drive, the 30gb and "repaired" that one.

I've tried altering the priority in the bios, but the 30Gb still loads.

So the question is how do restore booting priority to the 160Gb and check
that the boot.ini is working on that one? And whenever it successfully boots
up (touch wood) can I use system restore to use the last good working
configuration?

Many thanks.
 
--
Don't you have Google in your part of the world?
npharrison said:
Hope someone can help.

I managed to have a power outage and when I switched on my pc I got the
following message:

"Windows could not start because the following file is missing or
corrrupt.
Windows\system\hal.dll"

So I went on my son's pc and found Article ID: 945380.

I followed that. Did chkdsk /r and after several hours it finished, but
apart from file allocation tables, didn't report if anything had changed.
This was from the Method/Problem 2 section. So I moved onto Method/Problem
3,
using bootcfg and eventually Windows started and the disk loaded.

However, to my astonishment it was the wrong one!

I've got 2 drives, a 160Gb and a 30Gb. And the repair console had detected
the slave drive, the 30gb and "repaired" that one.

I've tried altering the priority in the bios, but the 30Gb still loads.

So the question is how do restore booting priority to the 160Gb and check
that the boot.ini is working on that one? And whenever it successfully
boots
up (touch wood) can I use system restore to use the last good working
configuration?

Many thanks.
Click to expand...

first off disconnect the 30 gig and see if the 160 tries to boot, let us
know what message you get.
Clark...
 
Funnily enough i decided to do that, and am running windows recovery abd
chkdsk /r to see what happens. It now makes the 160gb drive the c: drive, but
it's the master anyway. So when hopefully everything works again and I
reconnect the slave it'll come in as f: (2 dvd roms)

Many thanks and I'll let you know what's happening, though of to work in 1
hour. 51% completed at the mo.
 
Back
Top