Warning

 

Close

Confirm Action

Are you sure you wish to do this?

Confirm Cancel
Member Login

Log In

A valid email is required.
Password is required.
Posted: 1/7/2002 5:12:51 AM EST
A friend's pc crashed and they're in need of help - a while back a friend or relative of theirs installed a large HD and partioned it into multiple drives. Well they're pc crashed late last week during a modem upgrade and it somehow got so bad that they had to reinstall their OS (W'95) and so now the partitions are not coming up. So the ? is - How can they get the OS to recognize the partions? (Based on the assumption they haven't been screwed up.) TIA
Link Posted: 1/7/2002 5:16:17 AM EST
[Last Edit: 1/7/2002 5:25:52 AM EST by ARMALITE-FAN]
When they go into fdisk is C: set as active.The primary DOS usually C: meeds to be active for the OS to recognize it.
Link Posted: 1/7/2002 5:16:45 AM EST
First, try a boot disk with fdisk on it. Go into fdisk and make sure the partitions still exist. If not, they will need to be recreated, and you'll have to reinstall the OS.
Link Posted: 1/7/2002 5:21:53 AM EST
There's a good possibility that before they reinstalled the OS the ran fdisk and the partitions are already destroyed. Does the size of drive C indicate this might have happened?
Link Posted: 1/7/2002 5:38:26 AM EST
I won't be talking to them until this evening so I can't answer any ?'s at this time.
Link Posted: 1/7/2002 6:27:47 AM EST
The primary DOS usually C: meeds to be active for the OS to recognize it.
View Quote
DOS doesn't require that. Some buggy BIOS'es do. The BIOS is simply supposed to read the first physical sector from the floppy, then if it doesn't exist, the hard drive. A few BIOS'es check the partition table on the hard drive to see if there is an active partition before continuing. The BIOS should know nothing about the partition table. It is simply supposed to read the first sector. Then the boot loader reads the partition table. If the partitions show-up under fdisk (but not as drives under DOS), then sometimes running "fdisk /mbr" will fix it. That recreates the master boot record. Simply running fdisk does not recreate this. I don't think this will fix it, but it's worth a try. It's also something nice to try to fix things after getting a virus (they sometimes infect the boot record) or installing a different boot manager.z
Link Posted: 1/7/2002 2:36:52 PM EST
ALSO, if you have to reload the OS try to find them a copy of Windoze 98SE since it recognizes large partitions. You will lose a little drive capacity but you won't have so many logical drives. Much cleaner!
Link Posted: 1/7/2002 4:36:49 PM EST
If they used some crappy partitioning software like OnTrack, you are hosed. Some older machines don't properly recognize large drives without a utility. I hope that is not the case here.
Top Top