my old master drive is an ibm 40gb+ 75gxp...
i have an old Award 4.51 bios which exibits the 33gb+ lockup...
i fixed this using the ontrack dynamic drive overlay software...
this was as per instructions on ibm website with no problems...
then the 75gxp suffered a corrupt registry and wouldn't boot...
of course it contains many files that i need to retrieve...
i have now installed it on a new system as a slave...
however! even though it is recognised by ez-smart software,
recognised by windows device manager (type 47 working properly),
and fit and healthy as pronounced by ibm drive fitness test,
windows will not assign it a drive letter and it does not
appear in "my computer"...
i have a feeling it needs some driver or something installed in
some way unknown to me, and that i haven't discovered on ibms site...
something to allow windows to view the files on the "ontrack drive
overlay" system... something that was installed on the drive and is
accessed on boot, but not when the drive is a slave...
i'm sure there must be a way to access the drive, i cannot find out
how to do it though, and i wonder if anyone else here has some
knowledge of this problem and what i might do?
thanks all...
i have an old Award 4.51 bios which exibits the 33gb+ lockup...
i fixed this using the ontrack dynamic drive overlay software...
this was as per instructions on ibm website with no problems...
then the 75gxp suffered a corrupt registry and wouldn't boot...
of course it contains many files that i need to retrieve...
i have now installed it on a new system as a slave...
however! even though it is recognised by ez-smart software,
recognised by windows device manager (type 47 working properly),
and fit and healthy as pronounced by ibm drive fitness test,
windows will not assign it a drive letter and it does not
appear in "my computer"...
i have a feeling it needs some driver or something installed in
some way unknown to me, and that i haven't discovered on ibms site...
something to allow windows to view the files on the "ontrack drive
overlay" system... something that was installed on the drive and is
accessed on boot, but not when the drive is a slave...
i'm sure there must be a way to access the drive, i cannot find out
how to do it though, and i wonder if anyone else here has some
knowledge of this problem and what i might do?
thanks all...