This document includes step-by-step instructions for building a SimH (4.0) VAX simulator on Linux / Ubuntu 20.04, and installing VAX/VMS 7.1. The simulator emulates a VAX 8650 with 512MB RAM.
This example uses the following node specific values:
SCSNODE: GEORGE
SCSSYSTEMID: 1027
DECnet IV: 1.3
TELNET CONSOLE: 21263
INSTALL DIRECTORY: /opt/simulators/vax8600
Please adjust these values to whatever is appropriate for your environment.
Note that since VAX/VMS licenses are no longer available as part of the OpenVMS Hobbyist program, DECnet networking is not functional. However, the Carnegie Mellon University TCP/IP package can be installed without a license to provide TCP/IP networking.
Part 1 - Build SimH VAX Simulator
1. Install / Upgrade SimH Dependencies
# apt-get update
# apt-get install make libsdl2-dev libpng-dev libpcap-dev libvdeplug-dev bridge-utils
2. Get SimH from GitHub:
# cd /opt
# git clone https://github.com/simh/simh.git
3. Build a VAX 8600 simulator
# cd simh
# make -j4 vax8600
4. Create a new emulator directory and copy the emulator binary
# mkdir -p /opt/simulators/vax8600/iso
# mkdir -p /opt/simulators/vax8600/data
# mkdir -p /opt/simulators/vax8600/log
# mkdir -p /opt/simulators/vax8600/bin
# cp /opt/simh/BIN/vax8600 /opt/simulators/vax8600/bin/
5. Download the VAX/VMS 7.1 disk image using a web browser & install into the ISO directory
http://vaxhaven.com/cd-image/AG-QSBWB-BE.iso.zip
# cp AG-QSBWB-BE.ISO /opt/simulators/vax8600/iso/VAXVMS071.iso
6. Create an emulator initialization file in a new data directory, and link to it within the bin directory
# vi /opt/simulators/vax8600/data/vax8600.ini
; Set the memory size to 512 megabytes
set cpu 512M
; Use a TCP socket for the console
;set console telnet=5724
; Set the CPU idle detection method to VMS to improve performance when OpenVMS isn't doing anything
set cpu idle=vms
; Set the CPU to a model 8650
set cpu model=8650
; Configure an 1.5 gigabyte RA92 disk on interface RQ0
set rq0 ra92
; Attach a disk image to interface RQ0 - SimH will create this on boot
attach RQ0 /opt/simulators/vax8600/data/rq0-ra92.dsk
; Configure a CD-ROM drive (RRD40) on disk interface RQ3
set rq3 cdrom
; Attach the installation disk ISO image to interface RQ3
attach RQ3 -r /opt/simulators/vax8600/iso/VAXVMS071.iso
; Disable the RP Massbus controller
set rp disable
; Disable the RL11 cartridge disk controller
set rl disable
; Disable the RK611 cartridge disk controller
set hk disable
; Disable the RX211 floppy disk controller
set ry disable
; Disable the TS11 magnetic tape controller
set ts disable
; Disable the TUK50 magnetic tape controller
set tq disable
; Disable the DZ11 8-line terminal multiplexer
set dz disable
; Disable the LP11 line printer
set lpt disable
; Enable the Ethernet controller
set xu enable
; Set the MAC address to use for the Ethernet controller
set xu mac=08-00-2B-E5-40-03
; Attach the Ethernet controller to a TAP interface 'vaxa'
attach xu enp0s3
# ln -s /opt/simulators/vax8600/data/vax8600.ini /opt/simulators/vax8600/bin/
Part 2 - Install OpenVMS 7.1 Kit
7. Start the VAX emulator
# cd /opt/simulators/vax8600/bin/
# ./vax8600
VAX 8600 simulator V4.0-0 Current git commit id: c808256e
/opt/simulators/vax8600/bin/vax8600.ini-17> attach RQ0 /opt/simulators/vax8600/data/rq0-ra92.dsk
RQ0: Creating new file: /opt/simulators/vax8600/data/rq0-ra92.dsk
/opt/simulators/vax8600/bin/vax8600.ini-23> attach RQ3 -r /opt/simulators/vax8600/iso/VAXVMS071.iso
RQ3: Unit is read only
RQ3: '/opt/simulators/vax8600/iso/VAXVMS071.iso' Contains ODS2 File system
RQ3: Volume Name: VAXVMS071 Format: DECFILE11B Sectors In Volume: 800000
/opt/simulators/vax8600/bin/vax8600.ini-56> attach xu enp0s3Eth: opened OS device enp0s3
sim>
8. Boot the CD ROM into stand-alone backup
sim> boot rq3
Loading boot code from internal vmb.exe
...
OpenVMS (TM) VAX Version X6NO Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 24-AUG-2021 16:40
Configuring devices . . .
Now configuring HSC, RF, and MSCP-served devices . . .
...
Enter "YES" when all needed devices are available: yes
%BACKUP-I-IDENT, Stand-alone BACKUP V7.1; the date is 24-AUG-2021 16:43:37.12
$
9. Restore VAX/VMS install image to DUA0: (press ^E when completed)
$ backup dua3:vms071.b/save_set dua0:
%BACKUP-I-PROCDONE, operation completed. Processing finished at 24-AUG-2021 16:46:08.21
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue: ^E
Simulation stopped, PC: 81A02F47 (BBC #3,26C(R3),81A02F9B)
Part 3 - Install OpenVMS
10. Boot OpenVMS 7.1 install kit
sim> boot rq0
Loading boot code from internal vmb.exe
%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
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version BI71-6NO Major version id = 1 Minor version id = 0
OpenVMS VAX V7.1 Installation Procedure
Model: VAX 8650
System device: RA92 - _DUA0:
Free Blocks: 2877504
CPU type: 04-00
* Please enter the date and time (DD-MMM-YYYY HH:MM) 24-aug-2021 16:51
...
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
If this system disk is to be used in a cluster with multiple system
disks, then each system disk must have a unique volume label. Any
nodes having system disks with duplicate volume labels will fail to
boot into the cluster.
You can indicate a volume label of 1 to 12 characters in length. If you
want to use the default name of OpenVMS071, press RETURN in response
to the next question.
* Enter the volume label for this system disk [OpenVMS071]:
* Enter name of drive holding the OpenVMS distribution media: dua3
* Is the OpenVMS media ready to be mounted? [N] y
%MOUNT-I-MOUNTED, VAXVMS071 mounted on _DUA3:
Select optional software you want to install. You can install one
or more of the following OpenVMS or DECwindows components:
o OpenVMS library - 52200 blocks
o OpenVMS optional - 19000 blocks
o OpenVMS Help Message - 10400 blocks
o OpenVMS Management Station - 20000 blocks
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts - 6200 blocks
o DECnet-Plus networking - 80000 blocks
Space remaining on system disk: 2877324 blocks
* Do you want to install the OpenVMS library files? (Y/N) y
Space remaining on system disk: 2825124 blocks
* Do you want to install the OpenVMS optional files? (Y/N) y
Space remaining on system disk: 2806124 blocks
The Help Message utility (MSGHLP) provides online explanations
and user actions for OpenVMS messages in place of the hardcopy
OpenVMS System Messages and Recovery Procedures Reference Manual,
which is now separately orderable.
The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA,
consumes approximately 10400 blocks and will be
placed by default on your system disk in SYS$COMMON:[SYSHLP]
unless you specify an alternate device when prompted.
* Do you want to install the MSGHLP database? (Y/N) y
You can install this database on your system disk in SYS$COMMON:[SYSHLP]
or on an alternate device. If you specify an alternate device, but no
directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When
prompted, take the default of the system disk or specify an alternate
device using this format:
device:[directory]
* Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]]
Space remaining on system disk: 2795724 blocks
The OpenVMS Management Station is a client-server application
that provides OpenVMS system management capabilities through a
client application on a personal computer (PC) running Microsoft
Windows. The server application runs on OpenVMS systems and is
automatically installed as part of the OpenVMS operating system.
This option provides the files used to create the installation media
for the PC client software. If you want to use the OpenVMS Management
Station, you must install these files on at least one OpenVMS system to
create the installation media, which can then be used to install the
PC client on one or more PCs.
Note: To use the OpenVMS Management Station on your PC, you must be
running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1)
software.
The OpenVMS Management Station optional files consume approximately 20000
blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].
* Do you want to install the optional OpenVMS Management Station files? (Y/N) n
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the installation.
Some media, TK50s in particular, can be very slow when tailoring on files.
You might want to select DECwindows now and tailor off unwanted files later.
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.1.
The DECwindows components provided in this kit requires approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* a VAXcluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
* Do you want the DECwindows base support? (Y/N) n
Beginning with OpenVMS V7.1 DECnet-Plus is provided with the
OpenVMS operating system. Digital strongly recommends that DECnet
users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is available for separate installation. Please see the
"OpenVMS V7.1 Release Notes" for important information regarding
DECnet Phase IV support.
If you plan to install DECnet Phase IV do NOT select DECnet-Plus.
* Do you want to install DECnet-Plus? (Y/N) n
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Help Message
DECnet-Plus
Space remaining on system disk: 2795724 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Help Message save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
You can now remove the distribution kit from DUA3:.
Creating [VMS$COMMON] directory tree ...
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.
Cluster configuration cannot be done at this time because no network
is present. In order to configure a cluster you must FIRST do one
or both of the following:
o Install DECnet-Plus (or DECnet Phase IV), or
o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the
comment delimiter ("!") from the line
$! @SYS$STARTUP:LAN$STARTUP
in SYS$MANAGER:SYSTARTUP_VMS.COM.
Then configure the cluster by executing the following command:
@ @SYS$MANAGER:CLUSTER_CONFIG
See the OpenVMS System Manager's Manual: Essentials for more information.
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
* Enter password for SYSTEM:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-PWDLESSMIN, new password is shorter than minimum password length
%UAF-I-MDFYMSG, user record(s) updated
* Enter password for FIELD:
* Re-enter for verification:
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, rights database created
%UAF-I-RDBADDMSGU, identifier DEFAULT value [000200,000200] added to rights database
%UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights database
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights dataase
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights database modified
Creating MODPARAMS.DAT database file, SYS$SYSTEM:MODPARAMS.DAT
* Please enter the SCSNODE name: george
* Please enter the SCSSYSTEMID: 1027
After the installation finishes, you might want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system
libraries are shipped in a data-compressed format. If you have
enough disk space, you can decompress the libraries for faster access.
To data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you do not decompress these libraries, you will experience slower
response to the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in the upgrade and installation supplement"
supplied for your VAX computer.
o TAILOR THE SYSTEM DISK - You might want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR
NOTE: The tailor procedure cannot be used to TAILOR ON or TAILOR OFF
files located on an alternate disk.
=================================================================
Continuing with OpenVMS VAX V7.1 Installation Procedure.
Configuring all devices on the system ...
If you have Product Authorization Keys (PAKs) to register, you can
register them now.
* Do you want to register any Product Authorization Keys? (Y/N): n
********************************************************************************
After the system has rebooted you must register any Product
Authorization Keys (PAKs) that you have received with this kit.
You can register these PAKs by executing the following procedure:
$ @SYS$UPDATE:VMSLICENSE
See the OpenVMS License Management Utility Manual for any additional
information you need.
********************************************************************************
Now registering the OpenVMS operating system in the
POLYCENTER Software Installation product database
The following product will be registered:
DEC VAXVMS VMS V7.1 Transition (registration)
The following product has been registered:
DEC VAXVMS VMS V7.1 Transition (registration)
%UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE]
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore
10) GB-Eire 20) MET 30) SystemV
0) None of the above
Select the number above that best describes your location: 33
You selected US as your time zone.
Is this correct? (Yes/No) [YES]:
US Time Zone Menu
1) Alaska 4) Central 7) Hawaii 10) Mountain
2) Aleutian 5) East-Indiana 8) Indiana-Starke 11) Pacific
3) Arizona 6) Eastern 9) Michigan 12) Samoa
0) None of the above
Select the number above that best describes your location: 6
You selected US/Eastern as your time zone.
Is this correct? (Yes/No) [YES]:
Default Time Differential Factor for standard time is -5:00.
Default Time Differential Factor for daylight saving time is -4:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most repects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
Is Daylight Savings time in effect? (Yes/No): yes
Enter the Time Differential Factor [-4:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00.
Is this correct? [Y]:
DECnet-Plus will now be installed.
Media containing the DECnet-Plus kit must be available.
If you are installing OpenVMS from an Infoserver (DAD1)
or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.
If you are installing from a cartridge tape (TK50) or
from an open reel tape, you should have a DECnet-Plus kit
on cartidge tape or open reel tape.
An appropriate DECnet-Plus kit may also be available on
the Consolidated Distribution CD-ROM, or you may have a
separate DECnet-Plus kit.
NOTE: You may choose any available media for the
DECnet-Plus kit. It is NOT NECESSARY to use the same
type of media that contained the OpenVMS kit.
If you do not have a DECnet-Plus kit available, or if you
have decided NOT to install/upgrade DECnet-Plus, you can
bypass the DECnet-Plus installation by entering "EXIT"
for the "name of drive holding the DECnet-Plus kit".
* Enter name of drive holding the DECnet-Plus kit: dua3
* Is DUA3: ready to be mounted? [N] y
The following product has been selected:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX
Copyright ? Digital Equipment Corporation 1994. All rights reserved.
Digital Equipment Corporation
This product requires one of two PAKs: DVNETEND or DVNETRTG.
Do you want the defaults for all options? [YES]
Do you want to review the options? [NO] yes
DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX
DEC VAXVMS VMS V7.1 [Installed]
VAX P.S.I. or P.S.I. Access software: NO
VAX Wide Area Device Drivers: NO
DECdns Server software: NO
DECdts Server software: NO
Are you satisfied with these options? [YES]
Execution phase starting ...
The following product will be installed:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
Portion done: 0%...10%...20%...30%...40%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.1 Layered Product
********************************************************************************
Running AUTOGEN to compute the new SYSTEM parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 created
%SYSGEN-I-CREATED, DUA0:[SYS0.SYSEXE]ERRORLOG.DMP;1 created
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found
SHUTDOWN message from user SYSTEM at Batch 09:49:11
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
...
Loading boot code from internal vmb.exeent, the OPCOM process is not running
Rebooting...
...
*****************************************************************
OpenVMS VAX V7.1
You have SUCCESSFULLY installed the OpenVMS VAX Operating System.
The system is now executing the STARTUP procedure. Please
wait for the completion of STARTUP before logging in to the
system.
*****************************************************************
Thankyou for this guide, using it I was able to get OpenVMS running under simh. I used to work for a UK MOD sub-contractor, and we had a MicroVAX 2 in the beginning, and later a VAX 4000 and a DEC Alpha of some kind.
Thank you so much for this. I have been struggling to get vax running for a while and this was an enormous help.
This was fun. I haven’t touched a VAX in 30 years. I now have it running on Debian 13.
Memories, was a vax systems manager 80s/90s, also at UK MOD for part of it but then ended up in finance. Many thanks.
I’ve got two issues. One deals with my inability to figure out how to tell what disk drives are available to which VMS computer emulation in SimH. I used the early part of your example to build a SimH simulator for a MicroVAX II. We would like it to emulate existing MicroVAX II’s (actually VAX 4000’s of which there does not seem to be any build targets) but ours have DKAx SCSI drives connected to them and wanted to emulate the same. The commands to do so put in the .ini file failed and SHO DEVICE at the SimH prompt does NOT show any DK or DQ drives of any type available.
Secondly, is an issue with this example:
5. Download the VAX/VMS 7.1 disk image using a web browser & install into the ISO directory
http://vaxhaven.com/cd-image/AG-QSBWB-BE.iso.zip
# cp AG-QSBWB-BE.ISO /opt/simulators/vax8600/iso/VAXVMS071.iso
How do you go from from downloading the zipped ISO file to copying the unzipped file into the directory?
You can’t unzip a VMS ISO file onto a Windows, Unix or Linux system without corrupting the VMS file system, at least I’ve never been able to get it to work. I’ve always had to copy or FTP the zipped file onto a running VMS system and do the unzip there in order to maintain the VMS file attributes intact so that the ISO remains readable to boot from.
What am I missing here?
===
You should be able to unzip the compressed .iso image, because the entire disk image / filesystem is a single compressed file. I believe I understand what you are saying, and unzipping individual files may munge the RMS attributes, but here it is disk image containing an entire VMS filesystem, and not individual VMS files in a zip archive. I hope that makes sense.
I do not have any detailed information regarding the specific hardware supported by SimH. That would probably be a question to post to the SimH developers (and may change from one release of SimH to another).
Adding my thanks as well. Worked perfectly, till I tried to do something clever with the disk, re-installed and worked perfectly again. Our high school had an 11/780 that was upgraded to an MV2000 my freshman year. Four years later my first job in the defense industry I got because I was the only person in my age bracket that still knew VMS. Haven’t touched since 9/11. 🙂