[Color Computer][Coco] Tandy Hard Disk Controller

[Mark Marlette]

Gene,

The 4n1 worked, but it didn't even follow the electrical spec for 
SCSI. I'm sure if you would have loaded the bus with all devices it 
would have failed. Not the case with the TC^3.

Glazing over??? Come on Gene I wanted you to teach me something I 
didn't already know about SCSI. :)

All the flavors of SCSI, the spec is something to get lost in for 
sure. Know it all? Nope, just enough for the CoCo. :)

Mark
Cloud-9


At 3/4/2006 09:57 PM, you wrote:

>On Saturday 04 March 2006 21:47, Mark Marlette wrote:
> >Gene,
> >
> >At 3/4/2006 08:04 PM, you wrote:
> >>On Saturday 04 March 2006 19:44, Mark Marlette wrote:
> >> >Gene,
> >> >
> >> >I would have to go pull the 500 page spec out again. You seem to be
> >> > up on it.
> >>
> >>Only by hazy memory these days Mark.
> >>
> >> >Can you tell me how they are doing collision detection?
> >>
> >>Look at the interfaces pin descriptions.  ISTR there was a slim
> >>discussion around how that worked in there.
> >
> >I know exactly what each pin does on the interface. At least on the
> >TC^3, I did design the CPLD version of this. ;)
>
>The only docs I can find on short notice is the book that came with the
>Maxtor 7120s, written back when drive folks actually told you about the
>drive instead of disclaiming any responsibility in case you cat dies or
>decides to have a sex change operation.
>
>According to that book only the -ATN & term pwr is missing from the 4n1
>interface.  And the rest, mostly grounded, aren't that well explained,
>or I'm looking in the wrong section of this rather weighty tome.  So
>I'd have to assume you have the full interface covered.  This is about
>1/2 way thru a 70-80 page book.  Then it goes into a rather lengthy
>discussion of each of the buss phases and I get a glazed over set of
>eyes.
>
> >So I still ask. What pins are you referring to?
>
>It was pin 18 through pin 32 that were left out of the 4n1.
> >
> ><snip>.....
> >
> >> >Did you ever get your TC^3 running on your system after Boisy and I
> >> >set it all up for you in a standard configuration?
> >>
> >>Yes, but I've never been able to replace the boot image and make it
> >> work with one of mine on a different virtual disk.  I haven't tried
> >> to overwrite the one you put on it however.  That would have the
> >> feel of going out on a limb and then sawing it off behind me.  :-)
> >
> >Well that is easy don't overwrite it. You have 254 other drives to
> >store it on. I have had 4 different boots just DOS x and poof you are
> > there.
> >
> >If you can't create your own boot then are you able to create a boot
> >that already is on your disk. Same applies, save it to another
> >HDB-DOS drive and see if it works. These boots and scripts are so
> > easy.
> >
> >Mark
>
>--
>Cheers, Gene
>People having trouble with vz bouncing email to me should add the word
>'online' between the 'verizon', and the dot which bypasses vz's
>stupid bounce rules.  I do use spamassassin too. :-)
>Yahoo.com and AOL/TW attorneys please note, additions to the above
>message by Gene Heskett are:
>Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco
>
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.1.375 / Virus Database: 268.1.2/274 - Release Date: 3/3/2006
-------------- next part --------------


No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.375 / Virus Database: 268.1.2/274 - Release Date: 3/3/2006