[Info-vax] Need some special help changing the system password

[VAXman- at SendSpamHere.ORG]

In article <glv4jq$alu$1 at ruby.cit.cornell.edu>, Carlos E Murillo-Sanchez <cem14 at cornell.edu> writes:
>Thanks to all of you who have replied for your help.
>
>First of all:  I managed to do the system startup,
>run authorize and change the system password.  I suspect
>that the first time around I mistyped "OPA0:" and
>corrected it using backspace, which ended up looking
>right on the screen, but not in the parsed string.
>So, those of you that started talking about typing errors
>had it right.  But also, thanks for the UAFALTERNATE method;
>it is mentioned in the FAQ but not explained.
>
>I am using a cable that I wired eons ago, using the
>same connections as in the bcc08 cable.  This has always
>worked fine, except for the fact that when DTR is
>dropped, the VS2000 halts; as far as I know,
>this is normal.  Perhaps one day I'll wire DSR back
>into DTR; if the VS2000 keeps DSR up, I'll be able
>to turn the terminal off without having the VS2000 halt.
>
>Now I have, however, another question:  I think that after
>several tries in the conversational boot, I mixed the
>order of the SET WRITESYSPARAMS 0 command and the
>SET/STARTUP OPA0: command; as a result, now when I boot
>with
>   b dka3
>I get dumped to a $ prompt and I have to issue the
>@SYS$SYSTEM:STARTUP command manually.  So, how do
>I change this back? Do I boot conversationally
>and type
>   SET/STARTUP SYS$SYSTEM:STARTUP
>   CONTINUE
>
>Do I need quotes or something?  What is the kosher
>form of the string here? ( I had done SHOW /STARTUP but
>forgot to write the exact result before, argh...)

That should get you there.  Don't quote the filespec.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

  "Well my son, life is like a beanstalk, isn't it?"