STARLAN on AT&T 3B2/400 and 386
fmcgee at cuuxb.ATT.COM
Fri Nov 24 13:51:33 AEST 1989
In article <1989Nov22.160616.10272 at chinet.chi.il.us> les at chinet.chi.il.us (Leslie Mikesell) writes:
>In article <1989Nov21.134118.11677 at nebulus> root at nebulus (Dennis S. Breckenridge) writes:
>>root at mccc.uucp (Pete Holsberg) writes:
>>>Is there a need to change the software on the 3B2s?
>>No not at all!
>Umm... As far as I know, release 1.x of the starlan drivers (which is
>what he has on the 3b2) will *not* talk to 3.x (which is all that you
>can get for the 386). They can co-exist on the same wire and there
>is a software-bridge product available, but to use rfs he's going to
>have to upgrade to release 3.2 starlan on the 3B2.
Les is correct; you need to upgrade to an ISO version of the software.
Starlan versions prior to 3.0 talk the Universal Receiver Protocol
(URP) which is not compatible with ISO protocols (although they can
co-exist on the same network). Here's the quick and dirty info on
Starlan versions. The information is the same for 3B or 386 Unix.
2.0 - URP Starlan. Only talks to 1.0 or 2.0 software
(URP Starlan), runs on 3.1 Unix, DOES NOT run on
3.0 - internal distribution, only runs on 1 MB hardware,
implements ISO protocols, only talks to 3.0 and
higher Starlan software, runs on 3.1 Unix, DOES
NOT run on 3.2 Unix
3.1 - includes all the features of 3.0, and runs over 1
or 10 Mb hardware, DOES NOT run on 3.2 Unix
3.1a - includes all the features of 3.1, runs on 3.2
Unix, DOES NOT run on 3.2.2 Unix
3.2 - includes all the features of 3.1a, and runs on
I also highly recommend you upgrade to 3.2 Unix if it's at all
Frank McGee, AT&T
Tier 3 Indirect Channel Sales Support
More information about the Comp.unix.i386