Win 98 won't recognize slave hard drive
Started by
reddogracing
, Sep 20 2005 07:33 PM
#1
Posted 20 September 2005 - 07:33 PM
#2
Posted 21 September 2005 - 03:23 AM
Only reason I can think of, provided you've set the drive's jumper to slave, is that there are no partitions on the drive --- so no drive letter.
Incidentally, Device Manager doesn't show drive letters - that's normal.
You only see drive letters in Windows Explorer/My Computer. Try booting in to pure DOS (not a DOS window), then type FDISK and from the menu choose the option see the partition details for that drive, just to confirm that it does have at least one partition. And while your in DOS, log on to that drive and type DIR to see if DOS can access the drive.
Incidentally, Device Manager doesn't show drive letters - that's normal.
You only see drive letters in Windows Explorer/My Computer. Try booting in to pure DOS (not a DOS window), then type FDISK and from the menu choose the option see the partition details for that drive, just to confirm that it does have at least one partition. And while your in DOS, log on to that drive and type DIR to see if DOS can access the drive.
#3
Posted 21 September 2005 - 04:36 AM
Fdisk from DOS mode:
Partition: 1
Status: A
Type: Non-DOS
Volume Label: (blank)
Mbytes: 1032
System: (blank)
Usage: 100%
It doesn't have a drive letter assigned under DOS either.
The drive functioned perfectly well in another machine underWindows 95 before I put it in this machine. Is it possible it has some sort of drive management software (Western Digital) to allow a large drive under Win 95 that's messing thiings up? Or can the FAT16 vs. FAT 32 be messing things up?
Partition: 1
Status: A
Type: Non-DOS
Volume Label: (blank)
Mbytes: 1032
System: (blank)
Usage: 100%
It doesn't have a drive letter assigned under DOS either.
The drive functioned perfectly well in another machine underWindows 95 before I put it in this machine. Is it possible it has some sort of drive management software (Western Digital) to allow a large drive under Win 95 that's messing thiings up? Or can the FAT16 vs. FAT 32 be messing things up?
#4
Posted 21 September 2005 - 02:04 PM
It's possible that it might have fat12 or earlier. If win95 was installed over 3.1 and that was installed over dos, which it has to be, then 98 will have trouble with it. I just had such a drive with that and it had compressed files as well, and win98 couldn't work with it. Even fidsk and format couldn't deal with it. I had to write it to zeros in another machine to resinstall dos and WfW. If you can network the two machines you can probably get your files out. Otherwise if they aren't too large use floppies.
PS: I just rememberd that you may have a file conversion utility.
PS: I just rememberd that you may have a file conversion utility.
Edited by Tyger, 21 September 2005 - 02:05 PM.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users