From:	SMTP%"wall@rndhse.enet.dec.com" 29-JUL-1993 10:10:43.24
To:	EVERHART
CC:	
Subj:	Re: [Q] How to do conversational boot w/Alpha 3000/400?

X-Newsgroups: comp.os.vms
From: wall@rndhse.enet.dec.com (David F. Wall)
Subject: Re: [Q] How to do conversational boot w/Alpha 3000/400?
Message-ID: <1993Jul28.184013.391@jac.nuo.dec.com>
Lines: 46
Sender: news@jac.nuo.dec.com (USENET News System)
Reply-To: wall@rndhse.enet.dec.com (David F. Wall)
Organization: Digital Equipment Corporation
Distribution: usa
Date: Wed, 28 Jul 1993 18:40:13 GMT
To: Info-VAX@KL.SRI.COM
X-Gateway-Source-Info: USENET


In article <1993Jul28.140608.17485@erenj.com>, crumrine@crsgi1.erenj.com (MDCRUMR  Crumrine) writes:
>Hi,
>
>Just got a loaner - no docs - need the right boot params...
>
>Thanks!
>
>mike
>crumrine@erenj.com
>

For purposes of this dicusssion, boot commands look like this:

>>> b -flags rrrr,fffff ddcu

Where rrrr is the system root (usually 0, till clusters gets involved)
fffff are the flags you want to supply to the bootstrap, ddcu is the boot 
device of choice.

Set the bits in the flags to 1 and get the following:

bit 0 -- conversational bootstrap
bit 1 -- load XDELTA, the VMS system debugger
bit 2 -- take breakpoints at the end of SYSBOOT and EXEC_INIT
bit 4 -- take breakpoints in APB and SYSBOOT
bit 16 -- extremely verbose -- I want to see every QIO
bit 17 -- Not quite so verbose

Verbose boots take longer.

To get conversational bootstrap, any value for fffff where bit 0 is a 1 will
do, the simplest command being b -flags rrrr,1 ddcu

This basic idea applies to every AXP platform out so far (and, with any luck
it will apply every one we ever make)

--
Me, not Digital

David F. Wall (Digital Equipment Corp., Nashua, NH)
 
UUCP		...!decwrl!rndhse.enet!wall
Internet	wall@rndhse.enet.dec.com	
	- or -	wall%rndhse.enet@decwrl.dec.com
---