Discussion Locked

Another Western Digital Hardware

0 helpful
22 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok heres the problem My friend recently went down to a computer recycling business and purchased a 4311 mb harddrive. We have attempted to make it a slave on his pentium 120. We had one successful boot but not completely. The OS didn't display thedrive. So we rebooted the system. After we rebooted the system hasn't gone through with a full system boot. I was wondering if anyone could help us out. Never really done this before. The primary drive is configured to master already. We have configure the correct pins on both drives. Master for master and slave for slave. Both drives are not the same. The master is a Seagate w/ 854.7 mb. The total description of the drive is that its a Decathlon 850. The Other drive which is made byWD is a Caviar 24500. We could sure use some help as much as possible. And for those of you that are just responding to this for the points if your response works than you get all. considering its all that I have

22 replies

by timwalsh

First, can you verify the WD drive model number? The WD website doesn't even list a 24500 model. The closest I could find is a AC24200 or AC24300.

Couple of possibilities:

Does the BIOS recognize the drive correctly (correct size)? If not, you may need a BIOS update (if one is even available - this is an OLD computer) or Drive translation software (as many manufacturers include with their drives) (unfortunately WD doesn't even have a version of their software available that will work with this drive.)

IDE controllers were MUCH pickier on older computers. They often would not work correctly with drives from different manufacturers. Does the computer boot correctly if you disconnect the WD drive. Try moving the WD drive to thesecondary IDE controller.

by maxwell edison

You say that you have the jumpers set correctly - the Seagate as the Master and the Western Digital as the slave. Make sure that you have these two drives attached to the same ribbon cable. They should be connected to the Primary IDE channel - Primary Master and Primary Slave.

You say that the operating system does not recognize it. Before Windows will detect this drive, it has to be "detected" by the system. I'll assume that your initial bootup screen (the black screen that lists the detected devices) also does not detect it.

Go into your BIOS at initial bootup, and look for the "Auto Detect IDE Devices" (or something similar). Run that auto-detect, and the drive should then be detected.

by kinneym_98_98_98

The boot up screen did detect he drive the first time and now we are having troubles even getting the system to work. The drives were set properly throught the ribbon cable. We have already tried to get the auto-detect to work and it didn't work.

by cg it

if autodetect in the BIOS doesn't detect the drive then there is a problem. Try moving the drive from the primary IDE channel to the secondary IDE channel with it's own data cable. Retry autodetect. If autodetect doesn't see the drive check the power plug. Make sure its seated properly. If the BIOS still doesn't see the drive, that may simply mean the drive is bad and unusable.

by kinneym_98_98_98

I have found out that the drive is bad but now we have a problem with the primary system. on boot the system seems to be not detecting the drive right away. I brought the system into one of my old networking teachers he thinks that their might be a short in the system somewhere does anyone know how to find the short?

by thechas

The first thing to do, is go back to the original configuration.
Disconnect the WD drive.
Reset the jumpers on the Seagate for a single drive.
Reset the Drive settings as needed in BIOS settings.

If the system boots, then you need to connect the WD drive to the secondary IDE channel.
If the PC has a CD drive, make the WD master w/slave present, and the CD drive as slave.

If the system does not boot, the Seagate drive was setup as something other than the "default" settings.
There areup to 3 different options for setting up an IDE drive on these older motherboards. If the drive is configured for a different setup than the one that auto-detect chooses, you will get the kind of error you are getting.

Use the drive detection option in BIOS settings (this is different than Auto-detect) and choose from the 2 or 3 options given.
Try each option until you have a stable boot with just the Seagate drive.

Now, all new, and most used hard drives are setup with no partitions defined.
Windows will not display a drive that has not been partitioned.
Once you are back to a normal boot, you need to partition the WD drive before you can use it.

To reduce the risk of working on the wrong drive, I recommend that you configurethe PC with just the WD drive setup as a single drive.

Boot from a startup or Windows boot disk for the version of Windows that you are using.
From the DOS prompt, run fdisk and partition the WD drive as desired.
For help with fdisk and partitioning, check out
www.fdisk.com/fdisk
and www.aumha.org

If you are running Windows 95 prior to version 2.1, you will need to setup the WD drive as at least 3 drives.
1 primary DOS partition of up to 2.1GB, the rest as an extended DOS partition. The 2.2GB left will need to be split into at least 2 drives.

Chas

by opatzg9

Hi it looks like your getting some good advice here, what size (watt) power supply do you have, you may be under powered to run 2 drives. Secondly, what operating system are you using 95,98? You've got a good collection of the experts answering here so a little more info would be great. I would have to think try setting the drive up by itself would be the way to go as chas stated above if you're in win 95 the partitions need to be smaller than 2 gig due to a DOS limitation. If the drive isn't findable a few sites to look into woudl be:
http://www.samsungelectronics.com/hdd/support/utilities/ utilities_01.html
http://www.seagate.com/support/disc/drivers/discwiz.html
http://www.maxtor.com/products/DiamondMax/software/maxblast/default.htm
Or go to ibm.com, look for drivesor hard drives and find the ontrac link and download their drive mastering software.
These are all software products to make hardware which bios won't recognize work. They may or may not work for the older WD drive, I don't know whether they would damage it or not but if you feel their worth a try I'ld probably start with the ontrac route from ibm link.
Good luck

by yelhsa3840

go into bios and detect hdd run it then also set the setting for slave drive to auto this should be under CMOS settings then reboot and it should work if the HD is older then the computer it sould usually find a driver for it for more help you can email or instant message me at
yelhsa3840@aol.com

by mmurdock

just a quick thought...Is the primary slave turned on in the bios? if not then set it to auto. Didn't see that in any of the previous comments. hope you get it goin..

later,
mark

by thechas

Hi,

As to the "short".
The only things that you can do are to replace the IDE cables, and verify that all the power supply voltages are correct.

If the problem is not the cables or the power supply, then it is far easier to replace the motherboard than it is to attempt to track down and repair the problem.

If you were not following ESD procedures (wearing a grounded wrist strap) while working on the PC, you may have damaged both the drives and the motherboard.

Sources for a used motherboard include:
ebay
www.compgeeks.com
www.computersurplusoutlet.com
www.pcliquidator.com

They also sell "barebones" systems which may be a good way to upgrade this system.

Chas

by thechas

Socket 7 motherboards go for under $10 at many retailers that deal in used PC parts.

They are running $5 and up on e-bay.

As to finding the 'short', how much do you know about electronics, and what type of tools do you have?

Start by checking and monitoring the on-board power supplies. If 1 supply drops from time to time, you can follow the traces to the ICs connected to it.

Next, check the clock lines. I recommend an oscilloscope.

Nothing yet, then you need a logic anylyser tomonitor the data busses.

If you are lucky, a good cleaning with ESD safe compressed air and a brush will take care of any loose material on the board, and correct the problem.

Chas

by kinneym_98_98_98

k I know that this thread is closed so this is kinda to keep it alive. heres the thing. I have a friend that went to college for computer repair. he thinks that its a bios error. I am currently waiting for him to get a free day to take a thourogh look at it. and the other thing is thats its an 8 not a 7 which is unfortunate. also the motherboard that is current only has a p1.

This discussion is closed to new replies.