Yet another of my classic "unanswerables":
Take part of the solution of the 90M (turn off software flow control) and add in
a code modification to the handheld device to only transmit a <LF> when sending
the login id and the password instead of the <CR><LF>.
I saw another reference to this problem on a site I found using DEC's AltaVista
to look up xmodem:
http://www.hiwaay.net/hiwaay/faq/faq3e.html. They state
that their Digital server "has a little trouble with doing crlf translations
during the login,". They also state that "Digital has been informed of the
problem and is working on it." Yet, when I called DEC and repeatedly stated
that I thought that login was having trouble processing CRLF, I was told that
they did not think there was a problem. (Bulletin to DEC: WAKE UP AND SMELL
THE LOGIN THROUGH LAT/STREAMS!) It appears that login works just fine through
the serial port with crlf. But not in any other manner.
This was only about three months worth of irritation between DEC, Digi and
myself that could have been avoided. But, it all works fine now. Just be aware
if you're trying anything similar through the LAT/STREAMS modules.
Bob
>I had sent this out back in May with no response, so I'm trying again to see if
>anyone might have an answer. We should have Digi on site here this week, so
>we'll see what happens.
>
>Quick Summary of Problem: Looks like we're getting <LF><LF> when a <CR><LF> is
>passed in instead of just <LF>. Tried tweaking stty to no avail. Since this
>is a STREAMS device, the Digi folks say that they pass through everything fine
>and that perhaps LDTERM is not doing the proper translation.
>
>===============================================================================
>
>I'm dealing with modems again and this time I'm trying to go through a
>DigiBoard EISA/Xem configuration. I have a modem connected through COM1 and it
>works fine. I have an another modem of the same model (US Robotics Sportster
>28.8 FAX) with an identical configuration connected to the DigiBoard
>concentrator via a full 10-pin RJ-45 cable as directed in the DigiBoard manual.
>
>###################################
># The ATI4 output from the modem: #
>###################################
>
>USRobotics Sportster 33600 Fax Settings...
>
>B0 E1 F1 M1 Q0 V1 X4 Y0
>BAUD=2400 PARITY=N WORDLEN=8
>DIAL=HUNT ON HOOK
>
>&A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 &M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1
>
>S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060 S08=002
>S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S16=000 S18=000 S19=000
>S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128
>S32=002 S33=000 S34=000 S36=014 S38=000
>
>LAST DIALED #:
>
>We have a hand-held communications device for bar-code scanning and remote data
>entry. This device can dialup and connect to the Alpha fine over the COM port.
>When we try to connect to the modem connected to the DigiBoard, I get SIA
>ERRORS in /var/adm/sialog stating that there was a "Failure to authenticate
>session for <userid> on /dev/ttya01m". THEN I get a "Failure to authenticate
>session for <password> on /dev/ttya01m" message and a "Failure to authenticate
>session for (null) on /dev/ttya01m" message.
>
>Upon connecting the handheld is supposed to send <CR><LF> and then wait for
>"login: " at which point it should send the <userid><CR><LF> and then it should
>wait for "Password:" and then it should pass <password><CR><LF>.
>
>###############################
># The line from /etc/inittab: #
>###############################
>
>digia01m:23:respawn:/usr/sbin/getty -h /dev/ttya01m M2400 vt100
>
>##############################
># The line from /etc/remote: #
>##############################
>
>modem:dv=/dev/ttya01m:br#2400:pa=none:
>
>##################################
># The lines from /etc/gettydefs: #
>##################################
>
>M300# B300 HUPCL CS8 # B300 SANE IXANY TAB3 HUPCL #login: #M1200
>
>M1200# B1200 HUPCL CS8 # B1200 SANE IXANY TAB3 HUPCL #login: #M300
>
>M2400# B2400 HUPCL CS8 # B2400 SANE IXANY TAB3 HUPCL #login: #M1200
>
>################################################### # The 'file' output for the
>DigiBoard port modem: # ###################################################
>
># ditty -a ttya01m
>onstr \033[5i offstr \033[4i term vt100 maxcps 100 maxchar 50 bufsize 100
>-forcedcd -altpin -fastbaud (9600) -printer edelay (100) rtspace -dtrpace
>ctspace -dsrpace -dcdpace
>DTR+ RTS+ CTS+ CD- DSR- RI-
>#2 disc;speed 9600 baud; 0 rows; 0 columns
>erase = ^H; werase <undef>; kill = ^U; intr = ^C; quit = ^\; susp = ^Z dsusp
><undef>; eof = ^D; eol <undef>; eol2 <undef>; stop = ^S
>start = ^Q; lnext <undef>; discard <undef>; reprint <undef>; status <undef>
>time = 0; min = 1
>-parenb -parodd cs8 -cstopb hupcl cread -clocal
>-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc ixon
>-ixany -ixoff -imaxbel
>isig icanon -xcase echo -echoe -echok -echonl -noflsh -mdmbuf -nohang -tostop
>-echoctl -echoprt -echoke -altwerase -iexten -nokerninfo opost -olcuc onlcr
>-ocrnl -onocr -onlret -ofill -ofdel tabs -onoeot
>
>I've tried changing &H1 and &I0 to &H2 and &I2 (based on USR's UNIX modem setup
>recommendations), switching to an 8-pin RJ-45 and using ditty's 'altpin'
>setting, changing the getty prompt to include more output (like the console
>line in gettydefs) since in connecting via a PC terminal the prompt was
>"swallowed up" and I would frequently only see an "n: " instead of "login: ",
>and I've tried changing the linespeed in the gettydefs file. I've tried all of
>these with no success.
>
>So, if anyone has any clues as to what I can do to have this handheld device
>dial into the DigiBoard modem, I would appreciate any guidance.
>
>Thanks,
>Bob Capps
Received on Wed Sep 04 1996 - 22:35:13 NZST