[squeak-dev] Older VM's won't start the latest beta images

David T. Lewis lewis at mail.msen.com
Sun May 29 14:03:52 UTC 2022

On Sun, May 29, 2022 at 08:06:59AM +0000, Jaromir Matas wrote:
> Hi,
> I wonder what?s changed that the images starting from Squeak6.0beta-21772-64bit on won?t start with the previous release VM (squeak.cog.spur_win64x64_202003021730) or even with pre-release new VMs (e.g. version 3154).
> I?m on Win10, the process explorer (windows) shortly runs WerFault.exe and than the Squeak process is closed/disappears.

The change is here:


The current release candidate image does not have this, but it will be
applied as soon as you update that image, and it expected to be part of
the final release. The update applies a new image format number to the
saved image files (stored in the first 4 bytes of the image file) when
multiple bytecode set support is required from the VM. Effectively, the
means that the image is using the Sista bytecode set. Older VMs can
run the Sista bytecodes but do not yet have the code for recognizing
the additional image format number.


More information about the Squeak-dev mailing list