Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!sdcrdcf!trwrb!scgvaxd!ashtate!unisol!haral
From: haral@unisol.UUCP (Haral Tsitsivas)
Newsgroups: comp.unix.wizards
Subject: Re: Boot Problems
Message-ID: <272@unisol.UUCP>
Date: Sat, 18-Apr-87 17:25:05 EST
Article-I.D.: unisol.272
Posted: Sat Apr 18 17:25:05 1987
Date-Received: Sun, 19-Apr-87 17:55:15 EST
References: <6932@brl-adm.ARPA>
Reply-To: haral@unisol.UUCP (Haral Tsitsivas)
Organization: UniSolutions Associates, Culver City, CA
Lines: 31

In article <6932@brl-adm.ARPA> stubblef@ALMSA-1.arpa (Glenda Stubblefield) writes:
>I am having a problem when trying to boot after a power off...
>I am running 4.2 BSD on a VAX 750.  I have one RP06 and one RM80...
>I do not understand why I can't boot off the RM80 after the power
>down.  If I shutdown the system at any other time (without powering
>off) I'm fine and can boot from the RM80.

Yes, I seem to recall a similar problem under 4.1BSD with RP07 type disks.
The problem was something being reset on a power down on the drive and
it was leading to a "bad format" error when trying to startup immediately 
after a power down.  My 4.3 hp.c driver seems to be doing the right thing,
but I cannot check this for 4.2 since I don't have 4.2 sources on line.

What you probably have to do is make sure that hpaddr->hpcs1 is set
to HP_DCLR|HP_GO and HP_PRESET|HP_GO (also HPOF_FMT22) when first coming
up, otherwise they will never be set.  That should either be done
in the hpustart (as done in 4.3) or the hpstrategy routine (I think where
the problem was in 4.1).

The culprit in 4.1 was a missing test for initialization of the drive like:

	if (hpaddr->hpds & HPDS_VV) == 0 ) {

instead of the (4.3) correct:

	if ((hpaddr->hpds & HPDS_VV) == 0 || !sc->sc_hpinit) {

If sc->sc_hpinit does not exist in your driver you have to define an
array which you have to manage yourself...

--Haral Tsitsivas
  scgvaxd!ashtate!unisol!haral