🚀 go-pugleaf

In article <1992Aug12.192458.7871@pwcs.stpaul.gov>, derekt@merlin (Derek E Terveer) writes:

 > :  > 	2) Connect problem with BA4.00 PROM sets, primarily in TB+s.
 > :  >
 > :  > The second fix means that the owners of BA4.00 TBs need not get the new
 > :  > PROMs in order to allow WBs to connect to them.  At least this is what
 > :  > telebit claims.  We shall see.
 > : 
 > :      Or simply turn PEP micropackets off with S500=2 (register S120=16
 > : on the T2500 and below).
 > 
 > I am not sure what you are trying to say here.  There is no register
 > S500 that I know of on the WB.  Howver, if you mistyped and you really
 > meant S50, that register controls the modulation speed and S50=2 is
 > 1200 baud, which is unacceptable for my applications and probably most
 > other sites as well..  Perhaps you meant the protocol support register,
 > S111 (=30) on the WB and TB+, which controls whether or not UUCP
 > g-protocol spoofing is enabled?  This can drastically affect throughput
 > if turned off.
 > 
 > Furthermore, I am not terribly sanguine that the ability of the WB to
 > connect to the TB+ is purely a function of PEP mode.
 > 
 > Perhaps you could elaborate....?  I would like to be able to keep the
 > same throughput and tell my feed sites what register to change that
 > will allow my WB to connect to their TB+/etc without forcing them to
 > get the new TB PROMs.

     You sound quite confused.

     Are you having problems -connecting- in PEP mode a WorldBlazer to
a TrailBlazer Plus modem with 4.00 firmware or is the -throughput- between
the two in PEP mode lower than what you think it should be?

     If the former, turn off micropackets on the WorldBlazer (via
AT ~D1 S500=2, if your modem only displays the first 255 registers)
or upgrade the TrailBlazer Plus modems to current firmware.

     If the latter, set the S111=30 for UUCP-g as you stated, but
also make sure that PEP LZ data compression is off (S191=6) since
it's enabled by default.

--
Tony Austinson
Minnesota Macintosh UG/MacAddicts