ADFFS 2.84 public beta

[JonAbbott]

It's caused by issues in the BCMVideo implementation of overlays. I've raised them and until they're resolved I'm not sure there's any more workarounds I can implement. I've got several already to cover most of the issues, this isn't one I can workaround though.

[Idge]

Hi Jon,
I have noticed an odd issue with imaging that has cropped up with the latest version.

If I try and image Heimdall disk 0 with the latest version (5th July 2024), it images ok, however if you try boot floppy or by running the game directly from !Heimdall it gives an error Internal error: address exception at &001601E4

I have tried using the recording file within ADFFS as well as a custom recording file with the same results. I have also tried a shift boot and I get the same error.

I am imaging it on an a3010.

If I use ADFFS 2.83 to image it, it images fine and also runs that image without issue from 2.84 Beta.

[JonAbbott]

If I try and image Heimdall disk 0 with the latest version (5th July 2024), it images ok, however if you try boot floppy or by running the game directly from !Heimdall it gives an error Internal error: address exception at &001601E4

Thanks for the report. The only change to the imager that isn't GUI related was:

Code: Select all

JFD imager now compresses sector data in track chunks to improve Wimp updates/responsiveness

Although I wouldn't expect that to cause any issues as it only changed the timing of the compression step.

I'll see if I can reproduce the issue. I have imaged a few games with 2.84 without issue, so it might be specific to that disc.

[JonAbbott]

If I try and image Heimdall disk 0 with the latest version (5th July 2024), it images ok, however if you try boot floppy or by running the game directly from !Heimdall it gives an error Internal error: address exception at &001601E4

Try the latest version in the OP.

The only file that's changed is !ADFFS.imaging.imageJFD3. The issue was caused by the compression being done in track chunks so I've recoded the compression loop from scratch.

NOTE TO SELF: Before formally releasing, drop imageJFD3 from ADFFS 2.83 into a copy of ADFFS 2.84 and confirm via binary compare that the output is the same across a random selection of JFD's.

[Idge]

Thanks Jon,
I can confirm that has fixed the issue.

Cheers