Article View: bit.listserv.coco
Article #426Re: Nitros problems
From: Randy McLaughlin
Date: Wed, 28 Jul 2004 00:54
Date: Wed, 28 Jul 2004 00:54
95 lines
4903 bytes
4903 bytes
"Greg Andrzejewski" <pressyourluck85@yahoo.com> wrote in message news:-7udnSvOptrQb5vcRVn-ug@comcast.com... > > "Randy McLaughlin" <randy@nospam.com> wrote in message > news:lXgNc.4745$Mp1.834@bignews4.bellsouth.net... > > "Greg Andrzejewski" <pressyourluck85@yahoo.com> wrote in message > > news:y9OdnVctbZY-BZjcRVn-oQ@comcast.com... > > > > > > "Randy McLaughlin" <randy@nospam.com> wrote in message > > > news:LAfNc.4150$Mp1.3260@bignews4.bellsouth.net... > > > > > > > Just curious did that get you going? If so I think you'll like 3.5" > > > drives > > > > better. > > > > Randy > > > > > > Unfortunately, no. I swapped the connectors that correspond to wires 10 > > and > > > 12 on the card-edge to pin header converter. I then attatched another > > > card-edge connector on the tandy floppy cable. The one that was on the > > cable > > > alrady was too close to the second connector to allow me to connect it > to > > > the smaller 3.5" drive. That resulted in both drives spinning when any > > > commands are entered. Then I tried with just the 3.5" drive connected > and > > > disk basic wouldn't boot. > > > Just for the heck of it is tried attatching a pin header connector to > the > > > tandy floppy cable. This resulted in me being able to address the > existing > > > 5.25" drive, but commands to the 3.5" drive just caused the motor to > spin, > > > the LED did not come on, and an I/O error was reported. The process of > > > trying to get the pin header connector in the cable pretty well mangled > > the > > > connector, so I decided to try another. Same results. Only this time > while > > > trying to install the pinheader connector, the pliers cut through wire 1 > > in > > > the tandy cable. Rather than try to fix it, I've decided to start fresh > > with > > > a new floppy cable altogether. > > > > > > -Greg > > > > It is simple, but like anything new it can be a pain to get it working the > > first time. > > > > I run 3.5" drives on my system and really prefer it. I have not hooked up > a > > 5.25" in over two years, then just to transfer disks. > > > > As I stated in a previous posing if you need any help building a new cable > > let me know. > > > > Randy > > Okay, I found some more floppy cables and I'm going to try this again. Just > to make sure I'm clear on this.... > WARNING!!! ASCII ART > ________ ___ > | | ______________ | | | ____________ > |FD-501 | CABLE | + | \ | | > |controller|_______________|_ | _| _____/_____|_| = 3.5" floppy > ^ > hooks into | > 5.25" drive wires 10/12 > crossed > > Is this how it's supposed to be? > > Thanks, > Greg Yes, separating pins 10, 11, and 12 just flip them. I usually put two sockets for 3.5" drives one before the twist with the card edge connector so I can have either two 3.5" drives or 5.25" as 0 and 3.5" as 1. A couple of things to note is you use a hair dryer it softens the cable and makes it easier to do, if you add two sockets start with one and add the second later. Randy
Technical Details
Message-ID:
<nOCNc.21950$%S4.6375@bignews1.bellsouth.net>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!bigfeed.bellsouth.net!bignumber.bellsouth.net!news.bellsouth.net!bignews1.bellsouth.net.POSTED!9593b350!not-for-mailReferences:
<6pydnZWjzcxR12LdRVn-ug@comcast.com> <_5QLc.8876$yF.8852@bignews2.bellsouth.net> <fJRLc.15178$GT3.866@bignews6.bellsouth.net> <QtadnQKo5NuPRJ_cRVn-uw@comcast.com> <L8CMc.23172$yF.19697@bignews2.bellsouth.net> <F9KdneSF7rILmJ7c4p2dnA@comcast.com> <K0EMc.23370$yF.19785@bignews2.bellsouth.net> <LAfNc.4150$Mp1.3260@bignews4.bellsouth.net> <y9OdnVctbZY-BZjcRVn-oQ@comcast.com> <lXgNc.4745$Mp1.834@bignews4.bellsouth.net> <-7udnSvOptrQb5vcRVn-ug@comcast.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 110568,614516ce183455d3 X-Google-Thread: 10fd69,54dd3bf5e2cd9aad X-Google-Attributes: gid110568,gid10fd69,public X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!bigfeed.bellsouth.net!bignumber.bellsouth.net!news.bellsouth.net!bignews1.bellsouth.net.POSTED!9593b350!not-for-mail From: "Randy McLaughlin" <randy482@nospam.com> Newsgroups: bit.listserv.coco,comp.sys.tandy References: <6pydnZWjzcxR12LdRVn-ug@comcast.com> <_5QLc.8876$yF.8852@bignews2.bellsouth.net> <fJRLc.15178$GT3.866@bignews6.bellsouth.net> <QtadnQKo5NuPRJ_cRVn-uw@comcast.com> <L8CMc.23172$yF.19697@bignews2.bellsouth.net> <F9KdneSF7rILmJ7c4p2dnA@comcast.com> <K0EMc.23370$yF.19785@bignews2.bellsouth.net> <LAfNc.4150$Mp1.3260@bignews4.bellsouth.net> <y9OdnVctbZY-BZjcRVn-oQ@comcast.com> <lXgNc.4745$Mp1.834@bignews4.bellsouth.net> <-7udnSvOptrQb5vcRVn-ug@comcast.com> Subject: Re: Nitros problems Lines: 97 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-ID: <nOCNc.21950$%S4.6375@bignews1.bellsouth.net> X-Complaints-To: abuse@bellsouth.net X-Abuse-Info: Please forward a copy of all headers for proper handling X-Trace: pcpocbcnbdmdhgfgdbdpiflmbcekedmfhojhikkbagflhcbodjmppofofpkbpepnefhfgmkdifeclmmndkfngaobdpfnapkdhlbjpbippnceoinfiaaahcfbonbkndmjbbanobglegnjkpnlchbgeilhnelphejo NNTP-Posting-Date: Tue, 27 Jul 2004 20:53:39 EDT Organization: BellSouth Internet Group Date: Tue, 27 Jul 2004 19:54:58 -0500