Printable View
I have a western digital caviar 21600 drive that my bios detects if it is in the slave postion only....If I change the jumper to master and move it to the end connector on the cable and try to boot that machine no dice it freezes at the auto detect drives part...I can put another hard drive on the master and put the WD back to slave boot the machine into windows and use the drive as a slave but I want to use it as a Master....please offer any suggestions on this....I am at a loss
Hi sarrkazztic:
Run FDisk and see if the drive is set up as a Secondary DOS drive. If so run FDisk again and set it up as a Primary DOS drive. Format it /s and see if it doesn't work as the master then.
Good Luck, https://discussions.virtualdr.com/
DA
If that drive is the only drive on the cable (single drive installation), then remove all jumpers.
PS. In a master/slave setup the position on the cable does not really matter.
------------------
Bookmark your post to make it easier to find.
And remember, please post back whether the problem is resolved or not.
I fdisked the drive as primary dos partition and then set the jumper to master position and on the end of the 2 connector ide cable the computer will not boot...I put it on the 2nd connector still no boot...I put it as a slave and on the 2nd connector with a 200 mb drive on the primary end of connector and computer boots fine loaded win95 on this drive and was able to access the drive from my computer......If I attempt to make the WD drive master of any sort the bios will not recognize the drive at all...no autodetect and the computer freezes at boot...weird I have never seen this before...If I have to I can use this drive as a slave for saving files but It is one of those things that I would really like to see a solution for...
DrMDJ has the answer. If it the only drive in the PC it does not need a jumper. If it jumpered as master it will not work unless there is also a slave.
------------------
I have a similar problem with an old
motherboard which i know is fine...
The new harddrive has no jumpers on it,
and all cables are connected correctly,
but when i boot, the computer just says
"wait" and goes nowhere. also, if i
enter setup, and try to autodetect,
nothing happens... thanks in advance for
any insight!
As I said, then tward said, now I'll say again: the drive needs to be set without a jumper when it is the only drive on the cable (or the jumper can be put in a "neutral" position). It is called a Single Drive Installation. Take a look at the documentation that came with the drive and you will see.
------------------
Bookmark your post to make it easier to find.
And remember, please post back whether the problem is resolved or not.
Just thought I would get back to you....I had already tried this drive on both connectors of the ribbon with and without jumper settings but I went back because DR was so adamant about it and tried it again with no jumpers for some unknown reason this drive will only work with the jumper on the slave I have never seen this before....
Is that a 1.2GB harddrive??
I,ll bet it originally was set for cable select and that means you will need a new cable, I do believe. Went and got the following. 1.6GB and maybe someone can help you with the rest. I can not. https://discussions.virtualdr.com/
AC21600 1,624.6 3148x16x63 UDMA if CCC is A8-AG (AH is not UDMA), D5-D7, Bx, or Cx
All others -- PIO Mode 4
------------------
SMILE
and post back
[ Book mark this post to find it again]
[This message has been edited by Train (edited 04-21-2001).]
Try another IDE cable. The one you have is either defective, or as Train suggests, you have a cable select cable there (which you don't want). In a master/slave setup position on the cable (end, middle) does not matter. That's only a concern if you're using Cable Select. And don't forget, everytime you move the position of that (or either drive) it ould be a good idea to go in to bios setup and Reset the Configuration Data and save.
------------------
Bookmark your post to make it easier to find.
And remember, please post back whether the problem is resolved or not.
[This message has been edited by DrMDJ (edited 04-21-2001).]
I think it must be a problem with the drive becuase I tried it on several different cables and the same thing each time....
I've seen 2 or 3 drives over the years that displayed the same symptoms - would only work when attached as a slave drive.
Must be something wrong with the circuitry, but never did find out exactly what. And, since they still worked, well, they stayed attached as a slave drive.
thats what I am going to do...I am putting this system together for my nephew who does not have a computer and is going to be a junior in highschool next year so I put a 3.2 gig drive as master and loaded win98se on it and made the 1.6 a slave for file storage...I went with 98 over ME purely because it is more of a failsafe operating system with him living an hour away I dont want to be running up there every weekend when he messes something up...