From: gst@gnosys.svle.ma.us (Gary S. Trujillo)
Newsgroups: comp.sys.3b1,biz.comp.telebit
Subject: Re: WorldBlazer on 3B1 (aka UNIX PC)
Date: 11 Sep 92 18:58:17 GMT

In <1992Aug30.171052.2646@ceilidh.beartrack.com>
	dnichols@ceilidh.beartrack.com (Don Nichols (DoN.)) writes:

> ...
> 	He also mentioned problems talking to older Telebits via PEP, which
> required that their owners call in for the BC-7 rom upgrade to cure the
> problem.

Here's an article I just posted that deals with this subject:

| Newsgroups: biz.comp.telebit,comp.dcom.modems
| Subject: LA5.01 ROMs fix WB-->TB+ problem!
| Reply-To: gst@gnosys.svle.ma.us (Gary S. Trujillo)
|
| As I reported over a month ago, when I first got my WorldBlazer, I was
| unable to talk to any of several TrailBlazer+ modems in PEP mode.  These
| TB+s were all running using the BA-4 or older ROMS.  Telebit's solution
| was to suggest that the TB+ modems (not under my control) be upgraded to
| the latest rev ROMs (BC-7).  I procured three sets of the new ROMs for
| the TB+ modems, and hand-delivered them to the site where the modems
| are installed, where they were promptly installed in all three modems
| before we discovered that they connect up with the WB just fine, but
| can no longer recognize a BREAK signal, which is necessary to get the
| UNIX getty to cycle through its speed table.  Sigh.
|
| Well, the problem remained as described, with the site that has the TB+
| modems a little annoyed, perhaps (I would be, at least), since they had
| to open up all the modems and plug the old ROMs back in (Grumble) UNTIL
| just a few days ago, when I thought I'd give my buddy at Telebit another
| call to find out when they planned to have new ROMs for the TB+ that
| knew how to respond to BREAK properly AND sync up with the WB.  Turns
| out they still haven't solved that problem - or haven't blasted any new
| ROMs, at least.
|
| HOWEVER, it turns out they had just released a new set of ROMs for the
| WB, called LA5.01, that claims to fix the problem.  Well, it does, and
| I'm now happily using said WB to talk to the TB+, even as I type.
| Whatever else the new ROMs for the TB+ might fix, it seems like a much
| better solution to enable the WB to talk to TB+s with the old code,
| which never gave me any problem when I was using a T-2500 to talk with
| them.

Now for my one remaining problem with the WorldBlazer.  It seems not to
recognize a character string sent by my uugetty (I'm using one written
by Mark Dapoz that does autobauding, and has worked just fine on my
T2500 for the past couple of years) at 19200 baud (I haven't tried other
baud rates, since it would mean recompiling the code).  I'm using HDB
UUCP, BTW.  Here are my current register settings:

| WorldBlazer - SA - Version LA5.01A- Active Configuration
|  B1  E1  L2  M1  Q2  T   V1  X2  Y0 
| &C2 &D0 &G0 &J0 &L0 &Q0 &R3 &S1 &T4 &X0 
| S000=0   S001=0   S002=43  S003=13  S004=10  S005=8   S006=2   S007=40 
| S008:1   S009=6   S010=14  S011:50  S012=50  S018=0   S025=5   S026=1  
| S038=0   S041=0   S045=0   S046=0   S047=4   S048=0   S050:6   S051=255
| S056=17  S057=19  S058:2   S059=0   S060=0   S061:0   S062=15  S063=0  
| S064=0   S068=255 S069=0   S090=0   S092:1   S093:20  S094:0   S100=0  
| S104=0   S105=1   S111:30  S112=1   S151=4   S155=0   S180:3   S181:2  
| S183:180 S190:0   S191:6   S253=10  S254=255 S255=255 

[ Thanks to Kris A. Kugel (kak@hico2.westmark.com), whose article of Tue,
  11 Aug 1992 17:12:09 GMT (Subject: Re: WorldBlazer on 3b1?) was helpful
  in that it helped me figure out a few register settings that would have
  taken me a while to determine, since they're different from what they
  are on the T2500. ]

I've tried playing with S51 (DTE Interface Speed), but nothing short of
setting it to 5 (which would force the interface speed to 19200, and make
auto-bauding impossible) seems to work.  At first I thought the problem
was getty-babble, but then I fashioned a Y-connector, so that I could
"listen-in" on what either the modem or the computer was saying when the
initial string goes out ("aaaaa" to get the modem to the right speed,
before the first "at" initialization string is sent).  The modem is quiet
during this period, and doesn't even echo the string, yet when I connect
using kermit at 19200 baud, it seems to work OK.

Any ideas?

Thanks.

Gary
--
    Gary S. Trujillo                            gst@gnosys.svle.ma.us
Somerville, Massachusetts              {wjh12,bu.edu,spdcc,ima,cdp}!gnosys!gst