🚀 go-pugleaf

In article <1529@ccnysci.UUCP> alexis@ccnysci.UUCP (Alexis Rosen) writes:
>
>If you are running it without a video card (not a bad idea at all), you could
>wait a few weeks/months for the Moc OS drivers to be released for the CommCard,
>and then you could put in the Commcard in the third slot. That would let you
>run bridging software (Liason) on the same server so it could serve a
>LocalTalk net as well, and bridge the two nets. (Use of the CommCard cuts the
>CPU overhead of bridging, and LocalTalk in general, to an absolute minimum).
>Or you could put in a TokenTalk card, also due in a little while. Why, the
>possibilities are endless! Do I hear someone asking about ArcTalk? :-)

Actually the CommCard's MacOS LocalTalk drivers (for use under the LAP manager)
were released at the same time as the A/UX software (a year ago). It's the 
MacOS serial drivers that have not been released yet ..... For LocalTalk
the CommCard gives <= 1 interrupt/received/sent packet, can buffer 50 packets
(roughly 25 send/25 rcv) and can be sending/reciving one request while the
server is doing the disk IO for another

Anyway enough commercials

		Paul


-- 

Paul Campbell, Taniwha Systems Design, Oakland CA ..!mtxinu!taniwha!paul