• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

YAY! Just got a free Seagate 80GB IDE drive

SneakyStuff

Diamond Member
What's the procedure to turn this into a slave drive? I know it has to do with the pins on the back of the card, but could someone with experience advise me here?
 
Thanks, yep, it was there, it was behind a sticker, but it was there. It says for slave, I need to remove all pins. Always there for me nick! 🙂
 
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
 
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
It actually shouldn't matter as long as you set the jumpers correctly.
 
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.

hehe just because I didn't know that doesn't mean i'm computer handicapped. My cables have numbers on them! 😉
 
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
You only need to care about which connector it's on if you use Cable Select. Otherwise, it doesn't matter.
 
Originally posted by: MDE
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
It actually shouldn't matter as long as you set the jumpers correctly.

I disagree.

If you have a drive jumpered for Slave, but put it on the Master IDE connector, AND put another drive jumpered for any position on the acutal IDE cable Slave connector, you will have probs.
 
Originally posted by: MichaelD
Originally posted by: MDE
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
It actually shouldn't matter as long as you set the jumpers correctly.

I disagree.

If you have a drive jumpered for Slave, but put it on the Master IDE connector, AND put another drive jumpered for any position on the acutal IDE cable Slave connector, you will have probs.
No, MDE's right. Position on the cable doesn't matter if one drive's set to master and one's set to slave with jumpers.
 
Originally posted by: hjo3
Originally posted by: MichaelD
Originally posted by: MDE
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
It actually shouldn't matter as long as you set the jumpers correctly.

I disagree.

If you have a drive jumpered for Slave, but put it on the Master IDE connector, AND put another drive jumpered for any position on the acutal IDE cable Slave connector, you will have probs.
No, MDE's right. Position on the cable doesn't matter if one drive's set to master and one's set to slave with jumpers.

That hasn't been my experience. If cable position did not matter, then why are there still Slave and Master positions on the cable?
 
Originally posted by: MichaelD
Originally posted by: hjo3
Originally posted by: MichaelD
Originally posted by: MDE
Originally posted by: MichaelD
Good job figuring out the proper jumper placement for Slave operation. Now just make sure you CABLE it correctly. I.E. For Slave operation, the drive needs to connect to the MIDDLE connector on the IDE cable.
It actually shouldn't matter as long as you set the jumpers correctly.

I disagree.

If you have a drive jumpered for Slave, but put it on the Master IDE connector, AND put another drive jumpered for any position on the acutal IDE cable Slave connector, you will have probs.
No, MDE's right. Position on the cable doesn't matter if one drive's set to master and one's set to slave with jumpers.

That hasn't been my experience. If cable position did not matter, then why are there still Slave and Master positions on the cable?
To remind people that use the Cable Select jumper setting.
 
Yeah...Cable placement doesn't matter when you use the master and slave jumpers...only when you use cable select. Read the manual and it will even tell you.
 
A sorta related story. Yesterday I had some cable trouble when installing 1 HDD and 1 CDROM on my Pentium III system. I had the CDROM drive jumper set to Slave, while the HDD had NO jumper on it (apparently it was lost long ago, the relic is a 1.5GB Samsung). What I did was try to use just the Primary IDE cable with the endpoint connected to the HDD, and the midpoint connected to the CDROM.

Windows 98 booted up, HDD was recognised, but the CDROM wasn't. In the BIOS though, both were recognised. In the end I gave up and used two separate IDE cables, the primary one for HDD, secondary for CDROM, and Win98 was happy.

Funny thing is, I successfully used a single IDE cable with the exact same jumper settings on both HDD and CDROM in an older system (a Pentium 133MHz), running the same Win98 installation. Go figure.
 
ming2020: I've just had something very similar happen to me. My 98SE on my old 450MHz system saw everything easily, but with the new KT400 chipset mobo, it had trouble until I jumpered every IDE device properly. And even then it still insists on putting the Zip drive as a logical letter before the extended partition drive letters, which it shouldn't. But I stopped trying to understand it, it's Windows after all. 🙂
 
In case it means anything, my mobo in that P3 system was an Asus P3BF (solid performer). As for drive letter headaches, I once had a new XP installation assign drive "G:" as my primary boot drive. But that's another story.....
 
I had an Asus P5A, myself. Four year technology leap, and it only took two weeks to make it work properly without losing all my installed programs. :>

Yeah, the XP G: drive boot partition is a well-documented problem on here and even on the MS website...
 
Back
Top