Number: 505

Date:  4-Apr-84 13':33':19

Submitter: Sannella.PA

Source: JONL.PA

Subject: Document RS232LOGIN

Lisp Version: 

Description: '
Date':  3 APR 84 18':25 PST'
From': JONL.PA'
Subject': AR 59': autologin sequence for RS232CHAT'
To':   LispSupport'
cc':   masinter, jonl'
'
I''d like to decline this particular in favor of the existing RS232LOGIN'
machinery.  Perhaps another AR needs to be generated "Please document'
RS232LOGIN".  '
'
P.S.  RS232LOGIN currently seems to be broken, and I''ve lent my MODEM'
   out to someone (who? not sure, maybe Halverson), so I''ll have to get'
   it fixed before wanting others to read the documentation.  It got'
   broken once last fall when Bill changed the contents of'
   the data in LOGINPASSWORDS (he flubbed an edit trying to update RS232LOGIN),'
   but the particular problem now sseems to be deeper.'
'
-----'
'
Date': 13 MAR 84 23':49 PST'
From': MASINTER.PA'
Subject': auto login sequences for Chat/RS232'
To':   LISPSUPPORT'
'
My TRS-80 100 lap computer has a feature which is probably necessary for generic auto-login sequences. You get to encode  a string of cddharacters,  interspersed with':'
'
?<char>    wait for char from remote site'
'
e.g., ?←  waits until you see a ←.'
'
=    wait for 2 seconds'
↑<char>   send control-char, e.g. ↑M'
''<char>    send <char> even if escape.'
'
For the Vax/VMS guy, you probably have to wait for the "':" until you send the username and for the next "':" until you send the password, etc.'
'
'


Workaround: 

Test Case: 

Edit-By: Sannella.PA

Edit-Date: 13-Apr-84 15':14':42

Attn: Jonl.pa

Assigned To: 

In/By: 

Disposition: 

System: Communications

Subsystem: RS232

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: 

Frequency: Everytime

Impact: Annoying

Priority: Perhaps

Status: Open

Problem Type: Documentation

Source Files: