Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!cornell!rochester!udel!princeton!mccc!pjh
From: pjh@mccc.UUCP (Pete Holsberg)
Newsgroups: comp.dcom.modems
Subject: Trailblazer, 3B2, and SysVR3.1
Message-ID: <657@mccc.UUCP>
Date: 16 May 88 19:22:51 GMT
Reply-To: pjh@mccc.UUCP (Peter J. Holsberg)
Distribution: na
Organization: Mercer College, Trenton, NJ
Lines: 60


Based on a recent posting, I changed my Dialers and Devices files to
incorporate the ",M", "\M", and "\m" goodies in SysVR3.1's BNU.  Then, I
changed my Trailblazer to S53=1 ("DSR is on when modem is ready to
accept commands or data.  DCD is on when the carrier is detected).  This
is "CD-is-real" mode, no?

Well, here's what happens:

Device Type ACU wanted
mlock tty11 succeeded
opening with O_NDELAY set
clear O_NDELAY
filelock: ok
fixline(6, 19200)
processdev: calling setdevcfg(uucico, ACU)
gdial(tbfast) called
expect: ("")
got it
sendthem ()
CLOCAL set
PAUSE
DELAY
aPAUSE
aPAUSE
aPAUSE
t^M)
expect: (OK)
^Xx~xx^@^@timed out   <=== LOOKS LIKE WRONG BAUD RATE
set interface UNIX
mlock tty12 succeeded
opening with O_NDELAY set
clear O_NDELAY
filelock: ok
fixline(6, 19200)
processdev: calling setdevcfg(uucico, ACU)
gdial(tbfast) called
expect: ("")
got it
sendthem ()
CLOCAL set
PAUSE
DELAY
aPAUSE
aPAUSE
aPAUSE
t^M)
expect: (OK)
^@timed out   <==== STILL LOOKS LIKE WRONG BAUD RATE
set interface UNIX
getto ret -1
Call Failed: CALLER SCRIPT FAILED
exit code 101
Conversation Complete: Status FAILED

TM_cnt: 0

When I try "cu -d -ltty11", it connects and then says "carrier lost,
disconnected"!  If I reset the Trailblazer, I can once again talk to it,
but then I don't have "CD-is-real".  Can anyone shed any light on this?