Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!amdcad!sun!pitstop!sundc!seismo!uunet!munnari!basser!john
From: john@basser.oz (John Mackin)
Newsgroups: comp.dcom.modems,aus.acsnet
Subject: Re: Trailblazers on full-duplex protocols
Summary: ... but for Sun IV, it seems they will.
Message-ID: <1188@basser.oz>
Date: 9 Feb 88 22:51:59 GMT
References: <231@stcns3.stc.oz> <1187@basser.oz>
Reply-To: john@basser.oz (John Mackin)
Organization: Dept of Comp Sci, Uni of Sydney, Australia
Lines: 33

In article <1187@basser.oz>, I wrote:

> We tried a pair [of Traiblazers] between here and
> the University of Queensland last year.  The best we could get was
> about 100 characters/sec [...] i.e. far short of normal 1200 baud modems.
> [...]  Piers made vague noises at the time about doing
> a protocol module for them, but unless and until that happens,
> they're no good for Sun III.  (Or Sun IV for that matter.)

Piers responded with the following, which he asked me to post:

    From piers@cluster.cs.su.oz Wed Feb 10 09:16:12 1988
    To: john.basser 
    Subject: trailblazer modems and Sun4

    The new Sun4 protocol will drive trailblazers flat-out in both
    directions, since it is designed to work in such conditions,
    and consists of two de-coupled half-duplex protocols driven by
    separate processes (ie: the protocol will not be affected by
    sub-protocol buffering, the problem with the Trailblazer,
    and CSIRONET, for that matter.)

So, that's all you have to do, just wait for Sun IV to come out.
And in case you're wondering when that will happen, Piers says
``it's still on schedule'' -- meaning that will go into alpha testing
at the end of March.  I know it's doing something, I get the
occasional badhandler message from it :-).

John Mackin, Basser Department of Computer Science,
	     University of Sydney, Sydney, Australia

john@basser.oz.AU (john%basser.oz.AU@UUNET.UU.NET)
{uunet,hplabs,mcvax,ukc,nttlab}!munnari!basser.oz!john