I started searching for hard disk images that might hold some interesting software and i happened upon this gem: VAX/VMS v4.7 “Turnkey” Distribution.
This site provides a simh setup for a very sophisticated VMS 4.7 VAX. It is fully featured – so fully featured that it is a struggle for a mortal like me to do the simplest of operations. Two distributions are required – one for the VAX 8650 setup and the other with all the distribution media.
My eye lit up when i saw the distribution media which includes various programming languages and the All-In-One office programs. This is the best collection of installation media that i have found so far. It comes in various forms though including CDs, floppy disks, TK50 tapes, TU58 tapes, and 9 track tapes.
To exploit this variety of media, the 8650 setup has to have a lot of I/O devices and this makes it the rosetta stone for DEC media. My current options for reading media are limited. The physical MicroVAX I has only an RX50 floppy drive but one day it may have a solid state hard drive. Similarly, the MicroVAX I simh emulation has an RX50 and two hard drives. Conveniently though these hard drives can accept images from some other systems – even CDs.
My thought was that, if i instantiate this turnkey system, then i might be able to transfer some installation kits from the media library to a hard disk image. Then i could move the hard disk image from the emulated 8250 to the emulated MicroVAX I (or even a solid state hard disk on the physical MicroVAX I). I may also be able to move the kits to RX50 floppy disks for installation on the physical machine.
The first step was to instantiate the 8650 system above. I downloaded the two archives and copied the dist folder from the media tree into the turnkey system tree. I added the 8650 simh executable from the simh distribution. The 8650.ini file was provided as part of the turnkey system.
The setup procedure is provided in a readme.txt file. You fire up the 8650 executable and then initiate the installation. Then you stand back as it all happens. There’s a lot going on!
Eventually there is a setup dialog for passwords and networking – i won’t lie – much of this was completely overwhelming. I wasn’t losing too much sleep over the networking as that’s not my goal at the moment.
At the end, i could log in as “system” using the default password.
Show devices revealed a beast.
$ sh dev
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
795VAX$DDA0: Online 0
795VAX$DDA1: Online 0
795VAX$DJB2: Online 0
795VAX$DMA0: Online 0
795VAX$DMA1: Online 0
795VAX$DRA0: Mounted 0 HOM0 1005738 1 1
795VAX$DRA1: Mounted 0 HOM1 1005741 1 1
795VAX$DRA2: Online 0
795VAX$DUA0: Mounted 0 VAXVMSRL4 233458 272 1
795VAX$DUA1: Mounted 0 SHARE0 1213896 6 1
795VAX$DUA2: Mounted 0 SHARE1 1198935 12 1
795VAX$DUA3: Mounted 0 SHARE2 1181223 9 1
795VAX$DUB0: Mounted 0 SPOOL0 244566 2 1
795VAX$DUB1: Mounted 0 SPOOL1 244623 11 1
795VAX$DUC0: Online 0
795VAX$DUD0: Online 0
795VAX$DUD1: Online 0
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
795VAX$MSA0: Mounted alloc 0 PASCAL 0 1 1
795VAX$MTA0: Online alloc 0
795VAX$MTA1: Online alloc 0
795VAX$MTA2: Online alloc 0
795VAX$MTA3: Online alloc 0
Device Device Error
Name Status Count
OPA0: Online 0
RTA0: Offline 0
RTB0: Offline 0
TDA0: Offline 0
TXA0: Online 0
TXA1: Online 0
TXA2: Online 0
TXA3: Online 0
TXA4: Online 0
TXA5: Online 0
TXA6: Online 0
TXA7: Online 0
TXA8: Online 0
TXA9: Online 0
TXA10: Online 0
TXA11: Online 0
TXA12: Online 0
TXA13: Online 0
TXA14: Online 0
TXA15: Online 0
TXB0: Online 0
TXB1: Online 0
TXB2: Online 0
TXB3: Online 0
TXB4: Online 0
TXB5: Online 0
TXB6: Online 0
TXB7: Online 0
TXB8: Online 0
TXB9: Online 0
TXB10: Online 0
TXB11: Online 0
TXB12: Online 0
TXB13: Online 0
TXB14: Online 0
TXB15: Online 0
TXC0: Online 0
TXC1: Online 0
TXC2: Online 0
TXC3: Online 0
TXC4: Online 0
TXC5: Online 0
TXC6: Online 0
TXC7: Online 0
TXC8: Online 0
TXC9: Online 0
TXC10: Online 0
TXC11: Online 0
TXC12: Online 0
TXC13: Online 0
TXC14: Online 0
TXC15: Online 0
TXD0: Online 0
TXD1: Online 0
TXD2: Online 0
TXD3: Online 0
TXD4: Online 0
TXD5: Online 0
TXD6: Online 0
TXD7: Online 0
TXD8: Online 0
TXD9: Online 0
TXD10: Online 0
TXD11: Online 0
TXD12: Online 0
TXD13: Online 0
TXD14: Online 0
TXD15: Online 0
TZA0: Offline 0
Device Device Error
Name Status Count
LPA0: Online alloc 0
Device Device Error
Name Status Count
CRA0: Online 0
PUA0: Online 1
PUB0: Online 1
PUC0: Online 1
PUD0: Online 1
PYA0: Offline 0
XEA0: Online 0
XEA1: Online 0
XEA2: Online 0
XEA3: Online 0
XEA5: Online 0
XMA0: Online 0
XMB0: Online 0
XMC0: Online 0
XMD0: Online 0
$I found it quite tricky to correlate the VMS devices with the simh devices. I’m sure this is obvious to the more experienced operators but in frustration i turned to AI (Gemini):
Device mapping
1. The MSCP Disks (DU)
In SIMH, you had four controllers (RQ, RQB, RQC, RQD). VMS has mapped them as follows:
• DUA0 - DUA3: These are attached to SIMH's RQ controller. DUA0 is your system boot disk (VAXVMSRL4).
• DUB0 - DUB1: These are attached to SIMH's RQB controller (labeled as SPOOL disks).
• DUC0: This is the first unit on your SIMH RQC controller.
• DUD0 - DUD1: These are the first two units on your SIMH RQD controller.
2. The Massbus Disks (DR)
• DRA0 - DRA2: These map to your SIMH RP device (Massbus Adapter 0).
o Note: VMS is calling them DR (typical for RP07/RM05) rather than DB because of the specific drive type set in SIMH. DRA0 and DRA1 are currently mounted as HOM0 and HOM1.
3. The Tapes (MT and MS)
• MTA0 - MTA3: These map to your SIMH TU device (Massbus Adapter 1). VMS shows these as "Online alloc," meaning they are likely allocated to a process or initialized for use.
• MSA0: This maps to your SIMH TS device (the TS11 tape emulator).
4. The "Old School" Disks (DA and DM)
• DMA0 - DMA1: These map to your SIMH HK device (RK611/RK07).
• DDA0 - DDA1: These map to your SIMH TDC device (the RX211/RX02 floppy controller).
5. The Oddball (DJB2)
• DJB2: This is an RA-series disk on a KDJ11-B or similar controller. In your SIMH list, this corresponds to your CS (Console Storage) unit.
Actually, i also found that it was in the installation script for the turnkey installation.
I tried some experiments and found that the 8650 DUA3: hard disk Shared2 could be copied, and the image mounted on the emulated Microvax I. This opened up a transfer mechanism between the two machines.
I have struggled to get my head around the Storage Library System which seems to have control of MTA*:. The MSA0: device which is for 9 track tapes is unallocated and good to go.
I could then mount a 9 track tape image on MSA0 eg pascal.
$
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
>>> at ts0 "L:\Users\Graham\Onedrive\Computers\_Other\Microvax I\telegraphics2\vms47\dist\media\16mt9\BB-Z912L-BE.tap"
>>> c
mount msa0: pascal
%MOUNT-I-MOUNTED, PASCAL mounted on _795VAX$MSA0:
$ dir msa0:
Directory MSA0:[]
PASCAL037.A;1 6 27-MAR-1988 00:00
PASCAL037.B;1 91 27-MAR-1988 00:00
PASSTR034.A;1 20 27-MAR-1988 00:00
PASCAL037.A;1 6 27-MAR-1988 00:00
PASCAL037.B;1 91 27-MAR-1988 00:00
PASSTR034.A;1 20 27-MAR-1988 00:00
Total of 6 files, 234 blocks.Note that Ctrl-P is required to exit to the simh >>> prompt. By default, it is Ctrl-E.
The tape identifier can be found by mounting the tape with the/foreign option or just having a look at the media file with a hex editor.
The media distribution includes a spreadsheet that makes the association between media images and product identifiers. In this case pascal V3.7 is BB-Z912L-BE.tap. It also includes the volume labels.
Then the kit can be copied over to the transfer disk.
$ create/dir dua3:[kits]
$ create/dir dua3:[kits.pascal037]
$ copy msa0:*.* dua3:[kits.pascal037]*.* /log
%COPY-S-COPIED, MSA0:[]PASCAL037.A;1 copied to DUA3:[KITS.PASCAL037]PASCAL037.A;1 (6 records)
%COPY-S-COPIED, MSA0:[]PASCAL037.B;1 copied to DUA3:[KITS.PASCAL037]PASCAL037.B;1 (91 records)
%COPY-S-COPIED, MSA0:[]PASSTR034.A;1 copied to DUA3:[KITS.PASCAL037]PASSTR034.A;1 (20 records)
%COPY-S-COPIED, MSA0:[]PASCAL037.A;1 copied to DUA3:[KITS.PASCAL037]PASCAL037.A;2 (6 records)
%COPY-S-COPIED, MSA0:[]PASCAL037.B;1 copied to DUA3:[KITS.PASCAL037]PASCAL037.B;2 (91 records)
%COPY-S-COPIED, MSA0:[]PASSTR034.A;1 copied to DUA3:[KITS.PASCAL037]PASSTR034.A;2 (20 records)
%COPY-S-NEWFILES, 6 files created
$Then the hard disk image, share2_795.vhd, can be copied and dropped into the Microvax I simh folder and mounted.
$
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> at rq3 share2_795.vhd
sim> c
$ mount dua3: share2
%MOUNT-I-MOUNTED, SHARE2 mounted on _ANJIN$DUA3:
%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress
$ dir dua3:[kits.pascal037]
Directory DUA3:[KITS.PASCAL037]
PASCAL037.A;2 PASCAL037.A;1 PASCAL037.B;2 PASCAL037.B;1
PASSTR034.A;2 PASSTR034.A;1
Total of 6 files.And then the installation can proceed.
$ @sys$update:vmsinstal pascal037 dua3:[kits.pascal037]
VAX/VMS Software Product Installation Procedure V4.4
It is 4-MAY-2026 at 19:37.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
PASCAL V3.7
Beginning installation of PASCAL V3.7 at 19:37
%VMSINSTAL-I-RESTORE, Restoring product saveset A...
*-----------------------------------------*
* Installation Command Procedure for *
* VAX PASCAL V3.7 *
*-----------------------------------------*
* Do you want to purge files replaced by this installation [YES]?
This kit contains a file summarizing the new features, changes,
restrictions, and compatibility issues in this release of VAX
PASCAL. This file is named PASCAL037.RELEASE_NOTES and is
placed in SYS$HELP:.
This file contains information valuable to VAX PASCAL programmers.
Please inform your user community of this file's existence.
All questions regarding the installation have now been asked.
The installation of VAX PASCAL V3.7 will now continue for
approximately 5 to 120 minutes depending on your configuration.
%VMSINSTAL-I-RESTORE, Restoring product saveset B...
Your VMS system will now be updated to include the following new and
modified files:
SYS$HELP:HELPLIB.HLB [modified]
SYS$HELP:PASCAL037.RELEASE_NOTES [new]
SYS$LIBRARY:DCLTABLES.EXE [modified]
SYS$LIBRARY:LIBDEF.PAS [new]
SYS$LIBRARY:MTHDEF.PAS [new]
SYS$LIBRARY:PASDEF.PAS [new]
SYS$LIBRARY:PASSTATUS.PAS [new]
SYS$LIBRARY:SIGDEF.PAS [new]
SYS$MESSAGE:PASCALER1.EXE [new]
SYS$MESSAGE:PASCALER2.EXE [new]
SYS$SYSTEM:PASCAL.EXE [new]
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
*-----------------------------------------*
* Installation Verification Procedure for *
* VAX PASCAL V3.7 *
*-----------------------------------------*
%PASCAL-F-SENDSPR, Internal Compiler Error
%PASCAL-I-SENDSPR, while processing routine PASCTEST at line 27
%PASCAL-F-ENDDIAGS, PASCAL completed with 1 diagnostic
%VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected event.
VMSINSTAL procedure done at 19:37
This process should work for the other 9 track tapes which include:
- VAX C v2.4
- VAX CDD v3.4-1
- VAX CDD/Plus v4.0
- VAX/VMS v4.6
- VAX COBOL v4.1
- DEC/MMS v2.4
- VAX-11/RSX v2.3
- VAX FORTRAN v4.8
- DEC/CMS v3.0
- VAX BLISS-32 v4.4
- Data Interchange Library v2.0
- VAX DATATRIEVE v4.1
- VAX DATATRIEVE v4.2
- VAX ALL-IN-1 v2.1
- VAX Pascal v3.7
- VAX Rdb/VMS V2.3-0
- Matlab
I added two more TU devices in the 8650.ini file.
set TU4 enable, TU77
set TU5 enable, TU77That got me tape devices MTA4: and MTA5: which are not captured by the Storage Library Service. I found i could mount both TU58 and TK50 cartridges on these devices. The TU58 tapes don’t seem to have a file structure but the TK50 cartridges bring in:
- VAX BASIC v3.2 (needs >=VMS 4.5)
- VAX/VMS v4.x 1–8 Users License
- VAX/VMS v4.x 1–8 Users License
- VAX/VMS v4.x 3–8 Users License
- VAX GKS v3.0
- VAX DBMS v4.0
- Local Area VAXcluster v1.0
These are some that are on the openvms 5.0 CDs that are still good on VMS4, including:
- RPG
- LISPdel
- APL
- CDD
- DIBOL
These distributions work with 4.7; they may not work with 4.4 that is currently on the physical MicroVAX I.