Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Sir Xetwnk)
Newsgroups: comp.os.vms
Subject: Re: SYS$ANNOUNCE/WELCOME length
Message-ID: <2213@bsu-cs.UUCP>
Date: 26 Feb 88 21:28:55 GMT
References: <8802231609.AA21202@ucbvax.Berkeley.EDU> <10721@cgl.ucsf.EDU>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 31
Summary: Kill welcome message display

In article <10721@cgl.ucsf.EDU>, seibel@cgl.ucsf.edu (George Seibel%Kollman) writes:
> In article <8802231609.AA21202@ucbvax.Berkeley.EDU> RAND@merrimack.EDU ("Rand P. Hall") writes:
> >Can anyone provide a rational for SYS$ANNOUNCE and SYS$WELCOME's limit
> >of 63 characters? 
> 
> I for one sure hate to sit around watching 1000 bytes of somebody's
> dumb welcome message scroll by at 1200 baud...  maybe someone's trying
> to tell us something.
> 
> George Seibel
> UCSF

George, you might find THIS trick handy; I do the following for the very
reason you mention -- too-long welcome text on too-slow terminals:

Enter your username as usual.
Enter your password as usual, but IMMEDIATELY after pressing return, press
CONTROL O ("oh," not "zero").  If you catch it fast enough you can turn
the *OUTPUT OFF* before any welcome text spews out at you.  This disables
ALL output until you are actually logged in; output resumes somewhere be-
tween that point and execution of the system LOGIN.COM (basically, what I
mean is that any output in YOUR login.com will come out as always, and that
by the time you get to type anything, output will have been restored for you).

Chris Chiesa
Ball State University

-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><>
<> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa                              <>
<> cfchiesa@bsu-cs.UUCP                                                       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>