VAX Booting and Startup Dilema (was: VAX console and crossover...)

From: Witchy <witchy_at_binarydinosaurs.co.uk>
Date: Fri Feb 20 18:12:51 2004

> -----Original Message-----
> From: cctalk-bounces_at_classiccmp.org
> [mailto:cctalk-bounces_at_classiccmp.org] On Behalf Of R. D. Davis
> Sent: 20 February 2004 23:51
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: VAX Booting and Startup Dilema (was: VAX console and
> crossover...)
>
> accepted by the VAX. After setting flow control to xon/xoff,
> I could boot the VAX. :-)

Yay. I'd forgotten about the 'don't use hardware handshaking' rule 'cos I
just plug VAXen into a VT these days.
 
> SPAWN
> SYS$SYSTEM:STARTUP
>
> $ sys$system:startup
> %DCL-W-NOLBLS, label ignored - use only within command
> procedures \SYS$SYSTEM:\
> _What:
>
>
> Any thoughts/ideas? If it matters, it's VAX/VMS 5.5.

You've missed the _at_ off the beginning of the line:

_at_sys$system:startup

However, it might also be useful to boot to SYSBOOT with:

>>> B/1 dia0
SYSBOOT> set startup_p1 "min"
SYSBOOT> set startup_p2 "TRUE"
SYSBOOT> C

Which will give you detailed lists of what the VAX is doing as it boots. I
don't remember a VMS 5 system giving the %STDRV message at boot time though,
but then I didn't see every VMS 5 system boot :)

Let us know what you get!

Cheers

w
Received on Fri Feb 20 2004 - 18:12:51 GMT

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:36:43 BST