If you were Registered and logged in, you could reply and use other advanced thread options
I had a box with two Win2K SP4 installations on different HDs. The C drive
developed a fault that left it just about useless and I had to replace it.
The second drive will not boot up now. Using its (ERD) repair disk does not
work.
I have been rebuilding the new drive C but as time goes by I wish I could
get the D drive running again.
The boot.ini file has :
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
There are only two installations.
When I try to boot to D I get
"Win2000 could not start because of computer disk hardware configuration.
Could not read from selected boot disk. Check boot path and disk hardware. "
Suggestions please.
developed a fault that left it just about useless and I had to replace it.
The second drive will not boot up now. Using its (ERD) repair disk does not
work.
I have been rebuilding the new drive C but as time goes by I wish I could
get the D drive running again.
The boot.ini file has :
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
There are only two installations.
When I try to boot to D I get
"Win2000 could not start because of computer disk hardware configuration.
Could not read from selected boot disk. Check boot path and disk hardware. "
Suggestions please.
RFR wrote:
boot from your cd and go to the repair console
then try issuing the command fixboot
might as well try fixmbr while you are at it
boot from your cd and go to the repair console
then try issuing the command fixboot
might as well try fixmbr while you are at it
philo wrote:
Thanks Philo. I did many things like you suggest
here but I got nowhere.
Mike hit the situation very close to the "sweet spot."
> RFR wrote:
>> I had a box with two Win2K SP4 installations on different HDs. The C
>> drive
>> developed a fault that left it just about useless and I had to replace
>> it.
>> The second drive will not boot up now. Using its (ERD) repair disk
>> does not
>> work.
>> I have been rebuilding the new drive C but as time goes by I wish I could
>> get the D drive running again.
>> The boot.ini file has :
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
>> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
>> There are only two installations.
>> When I try to boot to D I get
>> "Win2000 could not start because of computer disk hardware configuration.
>> Could not read from selected boot disk. Check boot path and disk
>> hardware. "
>> Suggestions please.
>> drive
>> developed a fault that left it just about useless and I had to replace
>> it.
>> The second drive will not boot up now. Using its (ERD) repair disk
>> does not
>> work.
>> I have been rebuilding the new drive C but as time goes by I wish I could
>> get the D drive running again.
>> The boot.ini file has :
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
>> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
>> There are only two installations.
>> When I try to boot to D I get
>> "Win2000 could not start because of computer disk hardware configuration.
>> Could not read from selected boot disk. Check boot path and disk
>> hardware. "
>> Suggestions please.
>
>
> boot from your cd and go to the repair console
>
> then try issuing the command fixboot
>
> might as well try fixmbr while you are at it
>
> boot from your cd and go to the repair console
>
> then try issuing the command fixboot
>
> might as well try fixmbr while you are at it
Thanks Philo. I did many things like you suggest
here but I got nowhere.
Mike hit the situation very close to the "sweet spot."
Try this syntax:
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
RFR wrote:
>
> I had a box with two Win2K SP4 installations on different HDs. The C drive
> developed a fault that left it just about useless and I had to replace it.
> The second drive will not boot up now. Using its (ERD) repair disk does not
> work.
>
> I have been rebuilding the new drive C but as time goes by I wish I could
> get the D drive running again.
>
> The boot.ini file has :
>
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
>
> There are only two installations.
>
> When I try to boot to D I get
>
> "Win2000 could not start because of computer disk hardware configuration.
> Could not read from selected boot disk. Check boot path and disk hardware. "
> I had a box with two Win2K SP4 installations on different HDs. The C drive
> developed a fault that left it just about useless and I had to replace it.
> The second drive will not boot up now. Using its (ERD) repair disk does not
> work.
>
> I have been rebuilding the new drive C but as time goes by I wish I could
> get the D drive running again.
>
> The boot.ini file has :
>
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
>
> There are only two installations.
>
> When I try to boot to D I get
>
> "Win2000 could not start because of computer disk hardware configuration.
> Could not read from selected boot disk. Check boot path and disk hardware. "
--
Mike Walsh
You do have a stroke of genius Mike :-)
The D drive OS rose from the dead but with a few
hiccups. At one point the installation stopped
with that dreadful blue screen and a message:
"SystemRoot\System32\Drivers\dxapi.sys device
driver could not locate the entry point
KeyIsAttachedProcess in driver ntoskernel.exe" At
that point I had a sinking feeling but soon
afterwards the login screen arrived. I input my
pwd and it all opened up again. Phew! It had
several other stops, some with messages. However,
getting it running again is a huge relief.
Now after all that excitement, I'll spend much
more time with this little box. I'll just keep it
running and I'll sleep beside it at night to
protect it :-)
What is the simplest way to keep a copy of this
system so that, if it ever went belly up again, I
could write it back over the mess - or clean up
the mess and restore a precise copy of the
installation?
It has been years since I had anything to do with
Disc( ) and Rdisk( ) and I had forgotton which
referred to the physical drive. Great work on your
part Mike.
Thanks again.
Mike Walsh wrote:
on D: Drive" /fastdetect
on C: Drive" /fastdetect
on D: Drive" /fastdetect
The D drive OS rose from the dead but with a few
hiccups. At one point the installation stopped
with that dreadful blue screen and a message:
"SystemRoot\System32\Drivers\dxapi.sys device
driver could not locate the entry point
KeyIsAttachedProcess in driver ntoskernel.exe" At
that point I had a sinking feeling but soon
afterwards the login screen arrived. I input my
pwd and it all opened up again. Phew! It had
several other stops, some with messages. However,
getting it running again is a huge relief.
Now after all that excitement, I'll spend much
more time with this little box. I'll just keep it
running and I'll sleep beside it at night to
protect it :-)
What is the simplest way to keep a copy of this
system so that, if it ever went belly up again, I
could write it back over the mess - or clean up
the mess and restore a precise copy of the
installation?
It has been years since I had anything to do with
Disc( ) and Rdisk( ) and I had forgotton which
referred to the physical drive. Great work on your
part Mike.
Thanks again.
Mike Walsh wrote:
> Try this syntax:
>
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Win2K
>
on D: Drive" /fastdetect
>
> RFR wrote:
> RFR wrote:
>> I had a box with two Win2K SP4 installations
on different HDs. The C drive
>> developed a fault that left it just about
useless and I had to replace it.
>> The second drive will not boot up now. Using
its (ERD) repair disk does not
>> work.
>>
>> I have been rebuilding the new drive C but as
time goes by I wish I could
>>
>> I have been rebuilding the new drive C but as
>> get the D drive running again.
>>
>> The boot.ini file has :
>>
>> [operating systems]
>>
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K
>>
>> The boot.ini file has :
>>
>> [operating systems]
>>
on C: Drive" /fastdetect
>>
multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K
on D: Drive" /fastdetect
>>
>> There are only two installations.
>>
>> When I try to boot to D I get
>>
>> "Win2000 could not start because of computer
disk hardware configuration.
>> There are only two installations.
>>
>> When I try to boot to D I get
>>
>> "Win2000 could not start because of computer
>> Could not read from selected boot disk. Check
boot path and disk hardware. "
>

- Trying to Recover a Crashed System
- 05-31-2009
- Transferring data from old, crashed hard drive to new system
- February 24, 2006, 10:34 am
- how to recover My Documents?
- June 8, 2006, 7:10 pm
- recover data from reformatted hard drive
- January 23, 2008, 2:54 am
- Need to recover (encrypted) files from XP install on another hard drive
- August 28, 2006, 11:03 am
- Re: Help with my next system upgrade (not a new system): Athlon 64 X2? Conroe Duo? ...
- November 11, 2006, 7:51 am
- Will XP 64 like this system?
- May 18, 2007, 10:55 pm
- new system
- June 15, 2007, 6:05 am
- New System
- December 2, 2007, 2:29 pm
- Z80 system
- December 30, 2008, 8:51 pm
- System not powering up
- April 5, 2005, 12:55 pm
- System for Battlefield 2 (1 gig or 2?)
- September 6, 2005, 2:42 pm
- system need more power
- October 7, 2005, 7:00 am
- Will this system work for me?
- October 17, 2005, 11:11 pm
- OMG please help - system stability
- May 4, 2006, 10:37 pm
- Re: OMG please help - system stability
- May 4, 2006, 10:37 pm







XML Sitemap
> developed a fault that left it just about useless and I had to replace it.
> The second drive will not boot up now. Using its (ERD) repair disk does not
> work.
>
> I have been rebuilding the new drive C but as time goes by I wish I could
> get the D drive running again.
>
> The boot.ini file has :
>
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2K on C: Drive" /fastdetect
> multi(0)disk(1)rdisk(0)partition(1)\WINNT="Win2K on D: Drive" /fastdetect
>
> There are only two installations.
>
> When I try to boot to D I get
>
> "Win2000 could not start because of computer disk hardware configuration.
> Could not read from selected boot disk. Check boot path and disk hardware. "
>
> Suggestions please.
>
>