Number: 59

Date: 17-Mar-84  0':04':28

Submitter: Sannella.PA

Source: MASINTER.PA

Subject: Want auto login sequences for Chat/RS232

Lisp Version: 

Description: '
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.'
'
-----'
'
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': 11 Apr 84 18':44 PST'
From': JonL.pa'
Subject': Re': AR#59'
In-reply-to': Lispsupport''s message of 11 Apr 84 17':38':13 PST (Wednesday)'
To': Lispsupport.PA'
cc': vanMelle.PA, JonL.PA'
'
The situation is still the same as when commented on Apr 3.'
'
By the bye, I don''t think there is any connection with Ethernet CHAT, so unless Bill explicitly is interested in this problem . . . '
'
-----'
'
From': lispar.auto'
Date': 11-Apr-84 22':52':36 PST'
Subject': Re': AR#59'
In-reply-to': JonL.pa''s message of 11 Apr 84 18':44 PST'
To': JonL.pa'
cc': Lispsupport.pa, vanMelle.pa, Masinter.pa'
'
Aren''t the issues of auto-login for RS232Chat and (PUP) chat and NS chat all the same?'
'
-----'
'
Date': 12 Apr 84 15':46 PST'
From': JonL.pa'
Subject': Re': AR#59'
In-reply-to': lispar.auto''s message of 11-Apr-84 22':52':36 PST'
To': lispar.auto'
cc': JonL.pa, Lispsupport.pa, vanMelle.pa, Masinter.pa'
'
No, I believe that there is a PUP protocol for login.'
'
The RS232 world knows of no such thing -- RS232LOGIN is a "heuristic" based on the assumption that the connection is made into a know Executive, and thus a known string typed at it will suffice to make the login, or set the terminal size, etc.'
'
-----'
'
Date': 12 Apr 84 16':33':57 PST (Thursday)'
From': masinter.pa'
Subject': Re': AR#59'
In-reply-to': JonL''s message of 12 Apr 84 15':46 PST'
To': JonL'
cc': vanMelle, Masinter, LispSupport'
'
but, look, here is the exact same problem': the VAX using chat throws away characters! [Amazing coincidence, I think]'
'
Date': 12 Apr 84 16':08':47 PST (Thursday)'
From': SKobayashi.es'
Subject': Using Chat'
To': vanMelle.pa, LispSupport.PA'
cc': SKobayashi.es'
'
I upgraded to Carol and gave Chat your ADVISE. This solved my problem with CRs. Thanks.'
'
I''d like to invoke "Dribble" in my code in order to read the output from the VAX.  I tried using DOSELECTEDITEM, but that didn''t do anything for me.  Should I be accessing the display stream directly? Any suggestions?'
'
-- Sandy '
'
'
----------------------------------------------------------------'
Date':  9 Dec 83 12':10 PST'
From': vanMelle.pa'
Subject': Re': Using Chat'
In-reply-to': SKobayashi.es''s message of  8 Dec 83 20':29':01 PST (Thursday)'
To': SKobayashi.es'
cc': LispSupport.PA, DEI-Support↑.es, MASINTER.PA'
'
Your statement "I checked the status of the input file after it read in the CR and it was closed." supports the conjecture that the Vax throws away typeahead after the initial CR.  My own experiments with the GSLVAX confirm the conjecture.  You can perform the experiment yourself of typing the initial CR by hand, and then providing your input file via Chat''s "Input" command, and see that this all works fine.'
'
I don''t know how your Mesa tool works, but perhaps it pauses between sending lines, which would be sufficient to get around the problem.  In fact, I found that the following piece of advice, which tells Chat to immediately send out the current packet after every CR (instead of buffering further typein), is sufficient when running on a Dolphin chatting to a Vax that is one hop away':'
'
(ADVISE ''(BOUT IN CHAT.TYPEIN) ''AFTER'
	''(AND (EQ BYTE 13) (BSPFORCEOUTPUT STREAM)))'
'
This seems like a reasonable thing for Chat to do anyway, so I think I''ll make this change next time I''m in that code.  Let me know if this ADVISE fixes your problem.'
'
	Bill'
'
'
----------------------------------------------------------------'


Workaround: 

Test Case: 

Edit-By: masinter.pa

Edit-Date: 19-Apr-84 12':00':18

Attn: vanMelle,JonL

Assigned To: 

In/By: 

Disposition: [lmm': I''m still not sure if this is Documentation or implementation]

System: Communications

Subsystem: Other

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: Moderate

Frequency: Everytime

Impact: Moderate

Priority: Perhaps

Status: Open

Problem Type: Documentation

Source Files: