pjh@mccc.UUCP (Pete Holsberg) (05/17/88)
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?