17 Nov
2006
17 Nov
'06
10:21 p.m.
Thanks that's moved me on a bit
Rod
-----Original Message-----
From: cctech-bounces at classiccmp.org
[mailto:cctech-bounces at classiccmp.org] On Behalf Of arcarlini at iee.org
Sent: 17 November 2006 08:24
To: 'General Discussion: On-Topic and Off-Topic Posts'
Subject: RE: Vax 4000-200 - The Saga continues
Rod Smallwood wrote:
SET/STARTUP OPA0:
SET WINDOW_SYSTEM 0
SET WRITESYSPARAMS 0
CONTINUE
OK so this bit says "start fromm OPA0: (the console), don't do any of
this next time".
$ SPAWN
$ @SYS$SYSTEM:STARTUP
After this bit you have enough of OpenVMS running to fiddle with the
system manager's password.
At this stage you would do:
$ SET DEFAULT SYS$SYSTEM:
$ MC AUTHORIZE
UAF> MOD SYSTEM/PASS=somethingmemorable/PWDLIF=0
UAF> EXIT
(It's been years since I've had to break in so I may have mis-typed or
missed a step ... I'm sure someone will chip in if I have)
So now reboot and when the system comes up normally you just login as
SYSTEM with your memorable password.
This is mostly correct.... But what they don't say
is the system gets
left in a minimum condition.
Did you log out and did it reboot?
In my case only the drive it booted from ie no 2/3rd
drives, no tape
and no ethernet devices.
Under the low level prompt (>>>) all devices are shown as present.
i.e. DIA0 (RF71), DIA1 (RF72), DIA2 (RF72) MUA0 (Tape) and EZA0
(ethernet)
I'm guessing that
$ MC SYSGEN A A /LOG
would have sorted you out but ...
OK so lets try reversing the commands at the SYSBOOT prompt
SYSBOOT> SET/STARTUP SYS$SYSTARTUP_VMS.COM;2
Should this not be SYS$SYSTEM:STARTUP.COM? It absolutely should not have
a version number in there.
SYSBOOT> SET WINDOW_SYSTEM 1
SYSBOOT> SET WRITESYSPARAMS 1
SYSBOOT> CONTINUE
startup begins,
Then the following errors:
invalid logical name
previous value of SYSUAF has been superseded
error opening SYS$SYSROOT:[SYSMGR]BT$DEFINE_SYSTEMS.COM; as input
file not found
ON MIN OR UPGRADE START UP CLUE IS NOT RUN
You are using the wrong startup procedure and some pre-requisite has not
run.
Then a load of OPCOM messages
Definitely set the startup procedure properly.
If anybody does know where the answer is a link would
be nice.
After your first reboot the startup would have been restored to the
correct value. WRITESYSPARAMS of 0 means "don't write anything I've
changed back to a file on exit so none of the changes will be present on
next boot". If all you've changed is as described above, then reset the
startup procedure (WINDOW_SYSTEM is fine as is) and you'll be OK.
Antonio