From: CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 2-MAR-1989 21:54 To: MRGATE::"ARISIA::EVERHART" Subj: Re:Re:Re: Configuring Terminals and ALFMAINT Received: From KL.SRI.COM ([0.0.0.0]) by CRVAX.SRI.COM with TCP; Thu, 2 MAR 89 12:05:02 PDT Received: from RELAY.CS.NET by KL.SRI.COM with TCP; Thu, 2 Mar 89 12:00:58 PST Received: from relay2.cs.net by RELAY.CS.NET id af17052; 2 Mar 89 13:57 EST Received: from switzerland by RELAY.CS.NET id ak23168; 2 Mar 89 13:51 EST Received: from ean by scsult.SWITZERLAND.CSNET id a000854; 2 Mar 89 17:58 WET Date: 2 Mar 89 17:48 +0100 From: JS SHINER To: info-vax@KL.SRI.COM Message-ID: <23:infov@PYL.unibe.ch> Subject: Re:Re:Re: Configuring Terminals and ALFMAINT >Mark Hartwell > r >c.nasa.gov> writes: > >>>In article <962@mailrus.cc.umich.edu>, brian@ronin.cc.umich.edu (Brian Wolfe) > writes: >>> Please forgive me if this question is too rudimentary, I'm new to >>> VMS and I have just had several Microvax 3500's put in my charge. >>> >>> All I want to do is hook up some VT100 and Zenith H19's to the serial >>> ports on a 3500 (TXA0-TXA7). I'd like to be able to use Sytek Localnet 20/10 >0 >>> boxes, if possible (seems like it should be). >>> >>> After reading the System Manager's manual it seems to me that I could >>> just put a line in SYSTARTUP.COM like SET TERMINAL TXA0: /SPEED=9600/PERM >>> but this doesn't seem to work. Do I need to use /PROTOCOL or something like >> ~~~~~~~~~~~~~~~~~~~~~~~~~ >>> that? Someone told me that I may have to do something in SYSGEN but I >>> can't find any mention of it in the docs. > >>This posting is too vague to correctly second guess the request. However, >>there is a "one-time" command required when new microvaxen are set up in >>order to initialize the ports (drivers?). Until this is done, one cannot >>login except at the console. >> >>The command even has a well known alien named after it ... >> "ALF" >> >>The Microvaxen may not have had the "ALFMAINT" utility run on it. The >>utility is easy to run, the documentation fairly self explanetory, and >>should be run by typing "RUN SYS$SYSMAINT:ALFMAINT" and initializing each >>port. >> >>Even if this is _not_ the problem, system managers who have to install >>new operating systems on a newly un-boxed vax _sometimes_ initially >>miss this step. Just think of ALF - "Ha! I kill me." > >$ FLAME /ON > Bull! Using the network to distribute misinformation of this magnitude >ought to be a disorderly persons offense at the very least. >$ FLAME /OFF > >ALFMAINT sets up an Automatic Login Facility. A terminal which >is enabled for automatic login is restricted to use by a particular >account. This process has nothing whatever to do with whether or not a >particular terminal or terminal port works or not, nor is it necessary to >use ALFMAINT at any time on a micro-VAX or a big VAX. > > For further information on ALF and ALFMAINT, see section 5.2.9 of "Guide >to VAX/VMS System Security" Order number AA-Y510B-TE for VMS V4. > Every time that I have done a fresh installation (not an upgrade) of microVMS 4.1-4.7 on a microVAX II all serial lines (TT%%,TX%%) other than OPA0 have been set up for automatic login of user USER. To allow any one else to log in, you DO have to first run ALFMAINT to remove the entries for USER. JS Shiner Physiologisches Institut Buehlplatz 5 CH-3012 Bern Switzerland Phone: +41 / 31 / 65 87 22 (or 16 or 11) E-mail: SHINER@PYL.UNIBE.CH