OK- so I now understand what is happening here.
The 3.2 OS booted the Emax.
but when you switch floppy image, every single disk “image” section on the SD must have this SAME OS.
That is what is wrong.
To be clear.
You booted an OS.
Then by switching hfe image file, you are now swapping out this WORKING virtual floppy disk with working OS to a diffferent VIRTUAL floppy disk that has different version OS.
Now next time you go to operate a function, the OS module will attempt to load to perform that function.
But the OS function is different / has changed - checksum failure. OS module load failure.
Your mentality is that once you have loaded the OS, it’s done… but Emax doesnt’ work that way due to it’s limited available operating memory.
Every time you use a different function, Emax has to access the OS module specific to that function on disc.
Now, this is the difference between HXC and SCSI HD.
On an actual SCSI drive (CF media, or real HD, Zip, etc.) You have 1 OS that is loaded on the hard drive.
All the 35 banks access and use this same single copy of the OS for the module access, thus preventing what you encounter here.
But on HXC, each floppy virtual image MUST contain the same (correct working) OS.
So you will have to rebuild all the other hfe images using the working one as your starting point.
Hope that is helpful for your understanding.
-T