31 May
2002
31 May
'02
1:24 a.m.
On Fri, 2002-05-31 at 00:10, Antonio Carlini wrote:
6.2 when booting on simh looks like this:
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
I just tried,
my VAX 7.2 VMS CD also boots into a minimal VMS from SYS1
on my MicroVAX. So I guess they changed it between 7.1 and 7.2.
I don't know where they changed but I looked
at a V7.1 binary disk and it had a [SYS1]
directory with many files underneath. The
easy-to-spot difference between S/A BACKUP
and full OpenVMS boot is the number of files.
I don't have either V6.2 or V6.1 to hand so I
don't know if this (undocumented and
unsupported) facility was there back then.
>>boot dua1/r5:10000000
(BOOT/R5:10000000
DUA1)
2..
-DUA1
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version XI06-67K Major version id = 1 Minor version
id = 0
%SYSTEM-I-MOUNTVER, DUA1: has been write-locked. Mount verification in
progress.
I assume that there's a bug in SIMH causing the mount verification to
take forever....and that if it completed it would be in a minimal
environment.
Brian