[comp.sys.next] TrailBlazer Plus and NeXT UUCP

greid@adobe.com (Glenn Reid) (09/23/89)

Hi.

I have a TrailBlazer Plus hooked up to my NeXT.  It works, but not
quite as it should, I don't think.

Here is the problem.  There is an (undocumented) modem type supported
by "uucico" called "telebittone" that would appear to be the correct
thing for a Telebit modem, although "hayestone" should also work,
since it is basically Hayes-compatible.  But the rub is that "uucico"
insists on sending the string "ATV1E0H" to the modem to start things
out, regardless of whether it is in "telebittone" mode or "hayestone"
mode.  This is supposed to set verbose=1, echo=0, and hang up the
phone.  Unfortunately, "ATH" results in a message of "NO CARRIER" from
the trailblazer, and "uucico" is expecting "OK".  My other Hayes-
compatible modem responds with "OK" when you send it "ATH", and it
all works fine.

This sounds really confusing already, I realize.  I guess what I'm
wondering is this:

	1.  Is there any register I can set in the TrailBlazer that
	    will make it respond "OK" instead of "NO CARRIER" when
	    sent the "ATH" command?

	2.  Is there any other ACU modem type that will work with
	    the TrailBlazer?

At the moment I have gotten it to work by declaring it to be a 'DIR'
connection and putting the ATDTphonenum commands in the chat script
of the L.sys file, but I'd rather it were an ACU entry, if possible.

Oh, and one other thing, that seems contrary to popular belief.  I can't
seem to get the TrailBlazer to behave on serial port A at all, but it
is quite happy on port B, even with a "Mac" cable that's not supposed
to work on the NeXT cube.  On serial port A, the getty process seems
to think there's somebody trying to log in (I guess DTR/DSR is trigger
happy), and it keeps spawning a login process when it shouldn't.

Incidentally, as per the comments in the comp.sys.next groups recently,
just what does it mean for a modem to "appear to work" but not really
be working?  At this very moment I'm logged in remotely to work at 9600
baud with my modem that "appears" to be working, but maybe it isn't and
I haven't realized it yet :-)

Glenn Reid
Adobe Systems
greid@adobe.com