This document includes step-by-step instructions building an AXPbox (1.0.0) Alpha simulator on Linux / Ubuntu 20.04, and installing Alpha VMS 8.4. The simulator emulates an AlphaServer ES40 with 256MB RAM.
This example uses the following node specific values:
SCSNODE: STIMPY
SCSSYSTEMID: 1026
DECnet IV: 1.2
TELNET CONSOLE: 21262
INSTALL DIRECTORY: /opt/simulators/stimpy
For networking exmples elsewhere on this site with another Alpha VMS node, these instructions were repeated by substituting the following node specific values:
SCSNODE: REN
SCSSYSTEMID: 1025
DECnet IV: 1.1
TELNET CONSOLE: 21261
INSTALL DIRECTORY: /opt/simulators/ren
Please adjust these values to whatever is appropriate for your environment.
Part 1 - Build AXPbox Alpha Simulator
1. Install / Upgrade AXPbox Dependencies
# apt install libpcap-dev build-essential unzip libx11-dev libsdl-dev cmake libpoco-dev libxt-dev git
2. Clone Latest AXPbox from GitHub
# cd /opt
# git clone https://github.com/lenticularis39/axpbox.git
3. Build AXPbox
# cd axpbox
# mkdir build
# cd build
# cmake .. -DCMAKE_BUILD_TYPE="Release"
# make -j$(($(nproc) + 1))
4. My first OpenVMS server is named 'stimpy', therefore (substitute throughout if your name is different):
# mkdir -p /opt/simulators/stimpy/iso
# mkdir -p /opt/simulators/stimpy/data
# mkdir -p /opt/simulators/stimpy/rom
# mkdir -p /opt/simulators/stimpy/log
# mkdir -p /opt/simulators/stimpy/bin
5. And configure the /bin/ folder:
# cd /opt/simulators/stimpy/bin
# ln -s /opt/simulators/stimpy/rom .
# cp /opt/axpbox/build/axpbox .
6. Create and link the configuration file:
# vi /opt/simulators/stimpy/data/es40.cfg
sys0 = tsunami
{
memory.bits = 28;
rom.srm = "rom/cl67srmrom.exe";
rom.decompressed = "rom/decompressed.rom";
rom.flash = "rom/flash.rom";
rom.dpr = "rom/dpr.rom";
cpu0 = ev68cb
{
speed = 800M;
icache = true;
skip_memtest_hack = true;
}
serial0 = serial
{
port = 21262;
action = ""
}
pci0.15 = ali_ide
{
disk0.0 = file
{
file = "../data/disk0.img";
serial_number = "VMS";
rev_number = "8.4";
model_number = "OpenVMS8.4";
read_only = false;
cdrom = false;
autocreate_size = 6000M;
}
disk1.0 = file
{
file = "../iso/ALPHA0842L1.ISO";
read_only = true;
cdrom = true;
}
}
pci1.1 = dec21143
{
adapter = "enp0s3";
}
pci0.7 = ali
{
mouse.enabled = false;
vga_console = false;
}
pci0.19 = ali_usb
{
}
}
# cd /opt/simulators/stimpy/bin
# ln -s /opt/simulators/stimpy/data/es40.cfg .
7. Download the ROM image (Thanks Raymii for the mirror!):
# cd /opt/simulators/stimpy/rom
# wget https://raymii.org/s/inc/downloads/es40-srmon/cl67srmrom.exe
Part 2 - Download OpenVMS & License Pack from VMS Software Inc (VSI)
8. From a web browser download the license pack (hash is provided in the e-mail from community@vmssoftware.com):
http://vmssoftware.com/community-license.php?hash={hash-provided}
[Downloads ALPHA_COMMUNITY_LICENSE_PAK_AUG_2023.COM]
9. Download the OpenVMS install (password in the e-mail from community@vmssoftware.com):
# cd /opt/simulators/stimpy/iso
# sftp acommunity@vsiftp.vmssoftware.com
sftp> get ALPHA0842L1.ZIPEXE
sftp> exit
# unzip ALPHA0842L1.ZIPEXE
[Creates ALPHA0842L1.ISO]
Part 3 - Install OpenVMS
10. In one terminal window from a shell prompt:
# cd /opt/simulators/stimpy/bin
# ./axpbox run
...
serial0(serial): Waiting for connection on port 21262.
11. In another terminal window run telnet:
# telnet localhost 21262
...
PA00>>> boot dqb0
12. Start OpenVMS Install:
...
OpenVMS (TM) Alpha Operating System, Version V8.4-2L1
Copyright 2016 VMS Software, Inc.
Please enter date and time (DD-MMM-YYYY HH:MM) 06-AUG-2021 17:15
...
****************************************************************
You can install or upgrade the OpenVMS ALPHA operating system
or you can install or upgrade layered products that are included
on the OpenVMS ALPHA distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS ALPHA Version V8.4-2L1
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1
The following PATCH kits are present on the OpenVMS ALPHA
distribution media.
----------------------------------- ----------- ----------
PRODUCT KIT TYPE KIT FORMAT
----------------------------------- ----------- ----------
VSI AXPVMS TCPIP_NFS_PAT V5.7-ECO5A Patch Compressed
VSI AXPVMS TCPIP_SSH_PAT V5.7-ECO5D Patch Compressed
----------------------------------- ----------- ----------
2 products found
Please consult the OpenVMS ALPHA Installation and Upgrade Manual,
the Release Notes, and the Cover Letter to determine if any or
all of these patches may be required for your system.
Press Return to continue...
***********************************************************
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
There are two choices for installation/upgrade:
Initialize - Removes all software and data files that were
previously on the target disk and installs OpenVMS ALPHA.
Preserve -- Installs or Upgrades OpenVMS ALPHA on the target disk
and retains all other contents of the target disk.
* Note: You cannot use preserve to install OpenVMS ALPHA on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE] INITIALIZE
You must enter the device name for the target disk on which
OpenVMS ALPHA will be installed.
Enter device name for target disk: (? for choices) DQA0
Enter volume label for target system disk: [ALPHASYS] STIMPY84
The target system disk can be initialized with On-Disk Structure
Level 2 (ODS-2) or Level 5 (ODS-5). (? for more information)
Do you want to initialize with ODS-2 or ODS-5? (2/5/?) 5
Hard links can be enabled on ODS-5 disks. (? for more information)
Do you want to enable hard links? (Yes/No/?) yes
You have chosen to install OpenVMS ALPHA on a new disk.
The target system disk, DQA0:, will be initialized
with structure level 5 (ODS-5).
Hard links WILL be enabled.
The disk will be labeled STIMPY84.
Any data currently on the target system disk will be lost.
Is this OK? (Yes/No) yes
Initializing and mounting target....
Creating page and swap files....
You must enter a password for the SYSTEM account.
The password must be a minimum of 8 characters in length, and
may not exceed 31 characters. It will be checked and verified.
The system will not accept passwords that can be guessed easily.
The password will not be displayed as you enter it.
Password for SYSTEM account:
Re-enter SYSTEM password for verification:
Will this system be a member of an OpenVMS Cluster? (Yes/No) no
Will this system be an instance in an OpenVMS Galaxy? (Yes/No) no
For your system to operate properly, you must set two parameters:
SCSNODE and SCSSYSTEMID.
SCSNODE can be from 1 to 6 letters or numbers. It must contain at
least one letter.
If you plan to use DECnet, SCSNODE must be the DECnet Phase IV
node name, or the DECnet-Plus (Phase V) node synonym.
If you have multiple OpenVMS systems, the SCSNODE on each system
must be unique.
Enter SCSNODE: STIMPY
If you plan to use DECnet, SCSSYSTEMID must be set based on the
DECnet Phase IV address.
Do you plan to use DECnet? (Yes/No) [Yes]
DECnet Phase IV addresses are in the format
DECnet_area_number.DECnet_node_number
DECnet_area_number is a number between 1 and 63.
DECnet_node_number is a number between 1 and 1023.
If you plan to use DECnet WITHOUT Phase IV compatible addresses,
enter 0.0.
Enter DECnet (Phase IV) Address: [1.1] 1.2
SCSSYSTEMID will be set to 1026.
This was calculated as follows:
(DECnet_area_number * 1024) + DECnet_node_number
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55) TURKEY
8* BRAZIL 24) GMT-0 40* MEXICO 56) UCT
9* CANADA 25) GMT 41* MIDEAST 57) UNIVERSAL
10) CET 26) GMT0 42) MST 58* US
11* CHILE 27) GMTPLUS0 43) MST7MDT 59) UTC
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) W-SU
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) WET
14) EET 30) HST 46) NZ 62) ZULU
15) EGYPT 31) ICELAND 47* PACIFIC
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 18
You selected EST5EDT as your time zone.
Is this correct? (Yes/No) [YES]:
Configuring the Time Differential Factor (TDF)
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 respects 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.).
This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): yes
Enter the Time Differential Factor [-4:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00
Is this correct? [Y]:
If you have Product Authorization Keys (PAKs) to register,
you can register them now.
Do you want to register any Product Authorization Keys? (Yes/No) [Yes] no
The following products are part of the the OpenVMS installation;
they will be installed along with the OpenVMS operating system:
o Availability Manager (base) for OpenVMS Alpha
o CDSA for OpenVMS Alpha
o KERBEROS for OpenVMS Alpha
o SSL for OpenVMS Alpha (based on OpenSSL V0.9.8)
o SSL1 V1.0 for OpenVMS Alpha (based on OpenSSL V1.0.2)
o Performance Data Collector (base) for OpenVMS Alpha
o HP Binary Checker for OpenVMS Alpha
You can also install the following optional products along with the
OpenVMS operating system:
o DECwindows Motif for OpenVMS Alpha
o DECnet-Plus for OpenVMS Alpha
o DECnet Phase IV for OpenVMS Alpha
o TCP/IP Services for OpenVMS
If you want to change your selections, you can do so later in the
installation by answering "NO" to the following question:
"Do you want the defaults for all options?"
Do you want to install DECwindows Motif for OpenVMS Alpha V1.7-F?
(Yes/No) [Yes] no
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCP/IP.
Do you want to install DECnet-Plus for OpenVMS Alpha V8.4-D?
(Yes/No) [Yes]
Do you want to install TCP/IP Services for OpenVMS V5.7-13ECO5F?
(Yes/No) [Yes]
The installation operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing ?.
Do you always want detailed descriptions? (Yes/No) [No]
The system was booted from a device containing the OpenVMS Alpha distribution.
Validation of signed kits is not supported in this restricted environment.
The following product has been selected:
VSI AXPVMS OPENVMS V8.4-2L1 Platform (product suite)
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.
Configuring VSI AXPVMS OPENVMS V8.4-2L1: OPENVMS and related products Platform
Copyright 2015-2016 VMS Software, Inc.
VMS Software, Inc.
Do you want the defaults for all options? [YES]
Availability Manager (base) for OpenVMS Alpha
CDSA for OpenVMS Alpha
KERBEROS for OpenVMS Alpha
SSL for OpenVMS Alpha (based on OpenSSL V0.9.8)
VSI AXPVMS SSL V1.4-502A: SSL V1.4 for OpenVMS Alpha (Based on OpenSSL 0.9.8ze)
VSI SSL is not Backward Compatible!
The VSI SSL Version 1.4 for OpenVMS is based on the 0.9.8ze baselevel of
OpenSSL. Some of the OpenSSL API, data structure and command are changed
from the previous HP SSL version 1.3 (Based on OpenSSL 0.9.7e).
If you were running a version of HP SSL prior to Version 1.4 and your
application is dependent upon the SSL, you must recompile and relink your
code after you upgrade to Version 1.4.
You must recompile and re-link your code with the latest SSL header files
and shareable images if you see the following error:
$ run ssl_test
%DCL-W-ACTIMAGE, error activating image SSL$LIBSSL_SHR32
-CLI-E-IMGNAME, image file
DWLLNG$DKA500:[SYS0.SYSCOMMON.][SYSLIB]SSL$LIBSSL_SHR32.EXE
-SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image
$
Following list of HP products/components that are dependent on HP SSL.
Look at the product website for these products that is compatible with
HP SSL Version 1.4
LDAP
ENCRYPT
Stunnel
HP System Management Homepage (HP SMH) for OpenVMS
HP WBEM Services for OpenVMS Integrity servers
HP OpenView Operations Agent for OpenVMS
OpenView Performance Agent (OVPA) for OpenVMS
Secure Web Server
ABS
HP Enterprise Directory
If any of the product dependent upon the above list of products, also
will not work.
For example:
- iCAp/nPar depends upon HP WBEMServices also will not work
- "$ backup/encrypt command which is in turn dependant on
Encrypt will not work
Links to the above products are available in the HP SSL home page.
http://h71000.www7.hp.com/openvms/products/ssl/ssl.html
Do you want to continue? [YES]
SSL1 V1.0 for OpenVMS Alpha (based on OpenSSL V1.0.2)
Performance Data Collector (base) for OpenVMS Alpha
HP Binary Checker for OpenVMS Alpha
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
VSI AXPVMS AVAIL_MAN_BASE V8.4-2L1 DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS CDSA V2.4-320A DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS DECNET_OSI V8.4-D DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS DWMOTIF_SUPPORT V8.4-2L1 DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS HPBINARYCHECKER V1.1-A DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS KERBEROS V3.1-152A DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS OPENVMS V8.4-2L1 DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS SSL V1.4-502A DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS SSL1 V1.0-2JA DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS TCPIP V5.7-13ECO5F DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS TDC_RT V2.3-1220 DISK$STIMPY84:[VMS$COMMON.]
VSI AXPVMS VMS V8.4-2L1 DISK$STIMPY84:[VMS$COMMON.]
Portion done: 0%...10%
%PCSI-E-OPENOUT, error opening DISK$STIMPY84:[VMS$COMMON.][SYSHLP]HELPLIB.HLB; as output
-RMS-E-FNF, file not found
%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended. Do you want to terminate? [YES] no
%PCSI-E-OPENIN, error opening DISK$STIMPY84:[VMS$COMMON.][SYSLIB]DCLTABLES.EXE; as input
-RMS-E-FNF, file not found
%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended. Do you want to terminate? [YES] no
Portion done: 20%...30%...40%...50%...60%...70%...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% HP TCP/IP Services for OpenVMS.
%
Portion done: 100%
The following products have been installed:
VSI AXPVMS AVAIL_MAN_BASE V8.4-2L1 Layered Product
VSI AXPVMS CDSA V2.4-320A Layered Product
VSI AXPVMS DECNET_OSI V8.4-D Layered Product
VSI AXPVMS DWMOTIF_SUPPORT V8.4-2L1 Layered Product
VSI AXPVMS HPBINARYCHECKER V1.1-A Layered Product
VSI AXPVMS KERBEROS V3.1-152A Layered Product
VSI AXPVMS OPENVMS V8.4-2L1 Platform (product suite)
VSI AXPVMS SSL V1.4-502A Layered Product
VSI AXPVMS SSL1 V1.0-2JA Layered Product
VSI AXPVMS TCPIP V5.7-13ECO5F Layered Product
VSI AXPVMS TDC_RT V2.3-1220 Layered Product
VSI AXPVMS VMS V8.4-2L1 Operating System
VSI AXPVMS OPENVMS V8.4-2L1: OPENVMS and related products Platform
VSI AXPVMS KERBEROS V3.1-152A
Configure and set up Kerberos
If Kerberos will be run on this system, but has not been
used previously, you need to perform the following steps.
o Run the Kerberos configuration procedure:
@SYS$STARTUP:KRB$CONFIGURE.COM
o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:KRB$STARTUP
o Add the following line to SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
Press RETURN to continue:
VSI AXPVMS SSL V1.4-502A: SSL V1.4 for OpenVMS Alpha (Based on OpenSSL 0.9.8ze)
There are post installation tasks that you must complete
after upgrading from previous SSL versions
including verifying startup command procedures and logical names.
Refer to SYS$HELP:SSL014.RELEASE_NOTES for more information.
VSI AXPVMS SSL1 V1.0-2JA: SSL1 for OpenVMS AXP V1.0-2J (Based on OpenSSL 1.0.2J)
There are post-installation tasks that you must complete.
After upgrading from previous SSL1 versions
Refer to SYS$HELP:SSL100-2J.RELEASE_NOTES for more information.
VSI AXPVMS TDC_RT V2.3-1220: The Performance Data Collector (base) for OpenVMS
Users of this product require the following privileges:
(CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK)
Users of this product require the following process resource limits:
WSQUO minimum 6000
A read-me file is available in SYS$COMMON:[TDC]TDC_README.TXT
Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT
VSI AXPVMS HPBINARYCHECKER V1.1-A: HP Binary Checker
Release notes for HP Binary Checker available
VSI AXPVMS DECNET_OSI V8.4-D: DECnet-Plus V8.4-D for OpenVMS AXP
Release notes are available in SYS$HELP:DECNET-Plus-V8_4.RELEASE_NOTES
It is necessary to reboot your system for the software to take effect.
You may install OSI Applications after rebooting and configuring.
VSI AXPVMS TCPIP V5.7-13ECO5F: VSI TCP/IP Services for OpenVMS.
VSI AXPVMS SSL1 V1.0-2JA: SSL1 for OpenVMS AXP V1.0-2J (Based on OpenSSL 1.0.2J)
There are post-installation tasks that you must complete.
After upgrading from previous SSL1 versions
Refer to SYS$HELP:SSL100-2J.RELEASE_NOTES for more information.
Check the release notes for current status of the product.
%PCSIUI-I-COMPWERR, operation completed after explicit continuation from errors
**************************************************************
* *
* W A R N I N G *
* *
* One or more errors were encountered during installation/ *
* upgrade. The target system may not operate correctly. *
* *
* You should correct the condition that caused the error(s) *
* and repeat the installation/upgrade. *
* *
**************************************************************
The installation is now complete.
When the newly installed system is first booted, a special
startup procedure will be run. This procedure will:
o Configure the system for standalone or OpenVMS Cluster operation.
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Set auto
Process AXPVMS_INSTALL logged out at 6-AUG-2021 21:12:29.15
Press Return to continue...
****************************************************************
You can install or upgrade the OpenVMS ALPHA operating system
or you can install or upgrade layered products that are included
on the OpenVMS ALPHA distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS ALPHA Version V8.4-2L1
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
Shutting down the system
SYSTEM SHUTDOWN COMPLETE
13. Set boot options:
P00>>> set auto_action boot
P00>>> set bootdef_dev dqa0
14. Boot the new OpenVMS installation:
P00>>> boot dqa0
OpenVMS (TM) Alpha Operating System, Version V8.4-2L1
Copyright 2016 VMS Software, Inc.
%DECnet-I-LOADED, network base image loaded, version = 05.17.02
%DECnet-W-NOOPEN, could not open SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
Please enter date and time (DD-MMM-YYYY HH:MM) 06-AUG-2921 21:19
Installing required known files...
Configuring devices...
...
[Configuration, Autogen, Automatic Reboot]
...
OpenVMS (TM) Alpha Operating System, Version V8.4-2L1
Copyright 2016 VMS Software, Inc.
...
Welcome to OpenVMS (TM) Alpha Operating System, Version V8.4-2L1
Username: system
Password:
Part 4 - Install VMS Licenses
15. Generate ISO Disk Image with Licenses (downloaded in Part 2) on Linux (Ubuntu) host (from bash prompt):
# apt-get install genisoimage
# mkdir license
# cp ALPHA_COMMUNITY_LICENSE_PAK_AUG_2023.COM license
# genisoimage -V ALPHA_COMMUNITY_PAK_2023 -o ALPHA_COMMUNITY_PAK_AUG_2023.ISO license
# cp ALPHA_COMMUNITY_PAK_AUG_2023.ISO /opt/simulators/stimpy/iso/
16. Update AXPbox Simulator Configuration with License ISO
# vi /opt/simulators/stimpy/data/es40.cfg
Change disk1.0 file to: "../iso/ALPHA_COMMUNITY_PAK_AUG_2023.ISO"
17. Reboot OpenVMS (while logged in as SYSTEM):
$ @sys$system:shutdown.com
...
Should an automatic system reboot be performed [NO]? Yes
...
18. Login again as SYSTEM and Add License Pak:
$ mount/over=id dqb0
$ set def dqb0:[000000]
$ copy alpha_co.com sys$login:
$ set def sys$login:
$ set file/att=(rfm=stmlf) alpha_co.com
$ @alpha_co.com
19. Reboot OpenVMS to active licenses:
$ @sys$system:shutdown.com
...
Should an automatic system reboot be performed [NO]? Yes
...
20. After reboot, login again as SYSTEM and verify licenses:
$ show license
Active licenses on node STIMPY:
------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units Avail Activ Version Release Termination
ALPHA-LP VSI 1050 H 0 0.0 (none) 22-SEP-2022
ALPHA-SYSTEM VSI 150 A 0 0.0 (none) 22-SEP-2022
Thanks for your great info on AXPbox!
How did you unpack the ROM .exe file in Linux?
Sorry, the first start of the simulator does the unpacking automatically!
Yes, you don’t need to to do anything special, it’s all magic ;-), just drop in the .exe as-is!