M
Michael
The basic setup:
Two harddrives. Primary master/Secondary slave. The cdrom is on the
primary master.
I've had, for years, W2k in the first partition of Drive "0" as well as
in the first partition of Drive "1".
It's and old Mitsumi CDrom (pre PnP), but has always worked in two OS's,
two drives---Even worked through win95/98/NT situations.
!!!! RED MEAT !!! A few days ago I booted into W2k on drive "1" (the
secondary slave) and NO cdrom. (Error 31, couldn't load drivers.)
Simple?...I re-loaded the drivers (cdrom, redbook and
storprop)..reboot..nuttin'.
Next, I uninstalled the rom, rebooted---W2k sees/says I have new
hardware, reboot...still nuttin'.
This is tough because the rom "shares?" resources with the primary
master drive and I can't really separate it's "resources" from the
resources of that drive.
However..., it appears to have the same profile(s) (Irq,IO, etc) in
device manager as it does when it is running (just fine) under W2k under
the install on the primary partition.
I suspect it is beyond a software/hardware problem? I think something
caused my bios to change (Me?), but I don't now exactly why what I did
had any bearing---now.
Sometime ago the second harddrive wasn't "recognized" (after I installed
some Dos stuff.)
I believe (I was fiddling about trying to get drive two recognized) I
changed (in the Bios) "enable both" PCI/IDE. It worked.
(However, "that" was both the "Setup" and "Default" in the Bios
anyway--I simply put it back to it's original state) That solved "that"
problem. (Further, and not related--I have always used "auto" to detect
the drives and they are working fine in LBA mode.)
So, is my problem in the Bios and where should I turn?
Or, is there a workaround in my system--though I have tried everything I
can imagine! I even reloaded the registry (a backup) that is "probably"
from before the "mystery failure"...to no avail. I am out of tricks.
Michael
Two harddrives. Primary master/Secondary slave. The cdrom is on the
primary master.
I've had, for years, W2k in the first partition of Drive "0" as well as
in the first partition of Drive "1".
It's and old Mitsumi CDrom (pre PnP), but has always worked in two OS's,
two drives---Even worked through win95/98/NT situations.
!!!! RED MEAT !!! A few days ago I booted into W2k on drive "1" (the
secondary slave) and NO cdrom. (Error 31, couldn't load drivers.)
Simple?...I re-loaded the drivers (cdrom, redbook and
storprop)..reboot..nuttin'.
Next, I uninstalled the rom, rebooted---W2k sees/says I have new
hardware, reboot...still nuttin'.
This is tough because the rom "shares?" resources with the primary
master drive and I can't really separate it's "resources" from the
resources of that drive.
However..., it appears to have the same profile(s) (Irq,IO, etc) in
device manager as it does when it is running (just fine) under W2k under
the install on the primary partition.
I suspect it is beyond a software/hardware problem? I think something
caused my bios to change (Me?), but I don't now exactly why what I did
had any bearing---now.
Sometime ago the second harddrive wasn't "recognized" (after I installed
some Dos stuff.)
I believe (I was fiddling about trying to get drive two recognized) I
changed (in the Bios) "enable both" PCI/IDE. It worked.
(However, "that" was both the "Setup" and "Default" in the Bios
anyway--I simply put it back to it's original state) That solved "that"
problem. (Further, and not related--I have always used "auto" to detect
the drives and they are working fine in LBA mode.)
So, is my problem in the Bios and where should I turn?
Or, is there a workaround in my system--though I have tried everything I
can imagine! I even reloaded the registry (a backup) that is "probably"
from before the "mystery failure"...to no avail. I am out of tricks.
Michael
)