Re: Appletalk on IIC

[nathan@visi.com (Nathan Mates)]

In article <3365f714.0@news1.ibm.net>,  <wshek@ibm.net> wrote:
>Look, the macs and gs are more powerful thus may be doing more
>ie require something to manage the function while possibly busy.
>The //c is basically a single threaded straightline process. 

   I don't know if your newsreader is missing a lot of posts here, or
you're not getting the message that's been said a lot of times here:

   THE //c's SERIAL CHIPS CANNOT DEAL WITH APPLETALK. THE GS, MAC,
AND //e WORKSTATION CARD HAVE SERIAL CHIPS THAT CAN.

   Appletalk requires a high speed serial mode that the serial chips
in the //c are physically incapable of dealing with. There's no way
you can feed an Appletalk signal to the //c's serial port and get a
bitstream out of them that resembles the original Appletalk bitstream.

   The Mac, GS, and //e Workstation card all have a _DIFFERENT_ serial
chip, one that _can_ deal with Appletalk's speed and signaling modes.
That is why they can deal with Appletalk. End of story.

   Please drop this idea that the //c could manage Appletalk only by
completing the firmware, because you're denying reality. Extra addon
hardware (namely a serial chip capable of handling it) would be
required.

Nathan Mates

--
<*> Nathan Mates http://www.visi.com/~nathan/      <*>
# What are the facts? Again and again and again-- what are the _facts_?
# Shun wishful thinking, avoid opinion, care not what the neighbors
# think-- what are the facts, and to how many decimal places?  -R.A. Heinlein