Open SIMH V3 is the legacy version of Open SIMH. It contains fewer features than V4, and is in maintenance mode. It is currently the most stable version, although we recoomend that new users start with V4.
Select the operating system on which you want to run Open SIMH below.
Open SIMH V4 is the version of Open SIMH in active development. It contains more features and simulators than the legacy branch. Many of the features make it more convenient to use. We recoomend that new users start with V4. Over time, we expect that users of the legacy version will migrate to V4.
Select the operating system on which you want to run Open SIMH below.
Simulators in this directory run under the Windows operating system. Select "Releases" for the most tested version. Select "Snapshots" for the daily snapshots of work in progress.
Snapshots capture the development work in progress, and are a good choice if you are comfortable living on the bleeding edge.
Releases are issued when development has reached a stable milestone, Our current process is somewhat informal, but will improve.
Windows currently runs on the 32-bit x86 architecture, the 64-bit x64 architecture and the 64-bit ARM architecture. We currently build Open SIMH for x86 and x64.
Each kit on this page consists of an archive or installer that contains executable images of all supported simulators.
The kit names are in five parts - but the latest version will be first!
The date of the last commit (change) incorporated in the kit.
A unique identifer ("commit id") of the contents that can be used to get the corresponding sources from our git repository.
The platform name on which the simulator will run.
The architecure on which the simulator will run.
"Release" is the recommended, and optimized version. "Debug" indiates a simulator built with features useful for debugging the simulator.
To see the contents of an archive without downloading it, click on the icon. To download a kit's signature, click on the icon.
These kits are provided in two formats: zip archives and Windows (MSI) installers. To unpack the zip archives, use Windows explorer in recent versions of Windows. For older versions of Windows, use an external tool such as PKWARE's Zip Reader, available here. To use the Windows installers, simply download and click on them; you'll get the usual dialog from which you can customize the installation. Both formats provide the same simulators and come with digital signatures.
Terms of use: This project is run by dedicated volunteers.
While the information provided on this website is believed to be accurate, we make no guarantees.
You rely on it at your own risk.
To provide assurance that they have not be modified, kits are digitally signed by the robot that builds them.
To verify that a kit has not been modified, you need GNU Privacy Guard (GPG), or one of the programs that provide a graphical interface for it, such as Kleopatra.
the first step, which only needs to be done once (or if the robot's signing key changes) is to import the robot's signing key:
Click on the Bot signing key and import it into your GPG keyring. If you have a graphical interface, this should happen automatically. On the command line, use
gpg --import open_simh_kit_signing_key.asc
Certify the key, either directly, or by certifying the key of the Steering Group member who certified it.
Kleopatra will prompt you; For GPG, use
gpg --edit-key
gpg>trust
The Steering Group member's key can be found on the Open SIMH website.
With that in place, to verify a kit:
click on the icon adjacnet to the kit's link.
.
Save the signature in the same directory as the kit.
From the command line, type
gpg --verify kitname.sig
Here is a sample verification (the kit name has been shortened):
gpg --verify 2023-02-11-13-51-50-05-00-2d7d1ca7a4...-Win32-x64-Release.zip.sig
gpg: Signature made Wed Feb 15 09:21:25 2023 EST using RSA key ID 3A8F0169
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u
gpg: Good signature from "Open SIMH build bot <admin@opensimh.org>"
Note that in this case, "depth: 1" indicates that the signing key was certified by a trusted Steering Group member's key for additional assurance.