[Info-vax] Making a VMS 4.0 Install Tape

H Vlems hvlems at freenet.de
Mon Apr 6 18:40:19 EDT 2009


On 6 apr, 21:11, "Robert Jarratt" <nos... at nosp.am> wrote:
> >> When you say "does not boot" can you specify ? Based on my
> >> understanding, the early portion of VMS purrs along using the hardware
> >> drivers and eventually loads its own drivers. Not sure how VMS behaves
> >> if it doesn't have its own driver for a type of hardware.
>
> > I'll have to go back to check what the problem was, I can't remember now
> > and I am currently trying the SIMH approach using the 780 simulator.
>
> Here is what I did on my MicroVAX 3100 Model 80 with the 4.6 REQUIRED
> saveset:
>
> MOUNT/FOREIGN DKA200:
> BACKUP/IMAGE REQUIRED. DKA200:
>
> Here is what happened:
>
> >>> b dka200
>
> -DKA200
>   83 BOOT SYS
>
> -DKA0
> %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
> %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
> %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
> %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
>    OpenVMS (TM) VAX Version V7.3     Major version id = 1 Minor version id =
> 0
>
> I.e. it ignores the system on DKA200 and just goes to boot DKA0.
>
> I did the same restore on the SIMH VAX 780 and it booted up fine.

83 BOOT SYS is an indication that DKA200 is not bootable. I guess that
DKA0 is stored in the BOOT variable (>>> SHO BOOT) and once DKA200
fails the console retries on its default choice. IIRC the default is
ESA0, an ethernet boot.
So restoring REQUIRE. is not the same as restoring VMSnnn.B.
Hans



More information about the Info-vax mailing list