Computing.Net > Forums > Windows 3.1 > Slaving a Connor HD

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Slaving a Connor HD

Reply to Message Icon

Name: Fatal_Error
Date: July 23, 2001 at 16:40:34 Pacific
Comment:

hey there. i have a Connor CP30174E that has some programs from a past computer. i need to slave it so that i can get GenericCAD off of it but can't find a way to get it to work. If you could help me i would greatly appreciate it.



Sponsored Link
Ads by Google

Response Number 1
Name:
Date: July 23, 2001 at 23:30:56 Pacific
Reply:

This should help:First goto
http://www.seagate.com/support/disc/specs/conner/cp30174e.html
This will show you the slave/jumper config. Set your other drive's jumpers to master. Then use Auto detect hard disk in BIOS/CMOS setup. This should find your C drive then your new D drive.(if all is well) Accept settings, write to CMOS and exit.
Good Luck

PS repost if you need more.


0

Response Number 2
Name: Fatal_Error
Date: July 24, 2001 at 12:44:10 Pacific
Reply:

yeah i did that. the thing is my comp will autodetect it when it's set to master but when i try to slave it it won't autodetect.

p.s. i went to the seagate website ;-)


0

Response Number 3
Name:
Date: July 25, 2001 at 01:13:06 Pacific
Reply:

Well! If your jumpers on the first drive are set to master,not single, check your cable. When I did mine, I didn't pay attention to the plug config and it took a while to figure that the center plug on the ribbon wire had to connect to the card so autodetect would find both drives instead of the first one in line(master or slave)Also I assumed the stock drive was set at master. But, it was set at single. Which caused a similar problem in whcich it wouldn't find D at all.Finally, after setting the jumpers on both drives,rechecking the cable,and autodetecting again (all more than once) It went together. I'm FAR from being a pro but, it's actually pretty easy.It's usually the little things that are overlooked or assumed.
With patience, we'll get it done. It might take a few tries to work out the bugs, we'll getit. It sounds like your main drive is set at single.That would cause autodetect to look for the first master/single. At master, it then looks for slave.At single, it stops looking and decides no other drives connected.That could be why it detects your secondary only at master.Especially if it is first in line on the cable.If that be the case, it will report the drive's paramaters right,but will call it C:not D: It would also cause it not to look past your main drive when you set your second at slave.Cause single tells it last drive to detect, msater tells it to look for slave.
Hope this helps and isn't too redundant


PS.Make sur your main drive's jumpers are set at master not single(usual factory setting)


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More


Iomega 100 zip drive targeta mf-009



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 3.1 Forum Home


Sponsored links

Ads by Google


Results for: Slaving a Connor HD

Adding a Second HD www.computing.net/answers/windows-31/adding-a-second-hd/3222.html

Additional HD doesn't have boot sector? www.computing.net/answers/windows-31/additional-hd-doesnt-have-boot-sector/6149.html

Windows 3.1 on a 1+GB HD www.computing.net/answers/windows-31/windows-31-on-a-1gb-hd/11561.html