old packard bell computer hard drive not detected after installed new hard drive >EDIT FIXED<

SillyMan

Senior member
Jan 25, 2001
295
0
0
the old hard drive had < 1 gig > a lot of bad clusters on it so decided to replace with a < 2.5 > hard drive when did fdisk kept getting
no fixed disk no hard drive detected etc
any suggestions ?
 

VBboy

Diamond Member
Nov 12, 2000
5,793
0
0
I would not mention "Packard Bell" if I were you.

So did you take out the old HD and replace it with the new(er) 2.5 GB one? If so, did you set the jumpers on the newer one for Master?

It's not clear whether you were actually able to access that newer HD and to fdisk it. After FDisking it, you need to format it or you won't be able to access it from your OS, but BIOS will still report that drive as found.

You can access BIOS on your Packard Bell, can't you? :)

Depending on your OS, you may need to actually partition it into several partitions so DOS can recognize it. Also, your BIOS (your Packard Bell has BIOS, doesn't it? :)) may be too old to recognize drives that large. You will need to either flash it or to get a special program to be able to use it. Western Digital provides such a program, but I don't remember the name.
 

Jiggz

Diamond Member
Mar 10, 2001
4,329
0
76
If the old HDD is < 1 GB then maybe the bios does not support hdd in excess of the 540 Mb limit. In this case, you will have to use an overlay software which basically allows you to use a hdd larger than 540mb. Check with the hdd manufacturer's homepage on what kind of overlay software they use. WD uses the EZ drive and also the Ontrack's Disk Manager.
 

Dan

Diamond Member
Oct 9, 1999
5,080
0
0
SillyMan: Do you have your original PB install disk? Assuming you get the system to recognize the new drive, you'll need to run the PB install disk.
 

SillyMan

Senior member
Jan 25, 2001
295
0
0
thanks for the replies
no could not fdisk it
was set to autodetect in bios but didn't detect it
will try your suggestions
it had a 1 gig drive in it and I put a 2.5 in so your right the bios may
not be up to date enough to reconize it
 

SillyMan

Senior member
Jan 25, 2001
295
0
0
found problem the person I bought the drive from had it set up as
slave not master had to change the jumpers that was it
thanks for all your replies