ADFFS now avoids writing game boot scripts to the filesystem when a game is run. This removes the risk of filesystem corruption should a game hard-lock immediately.
It's now aware of the RPCEMu Extended Graphics Card and will switch back to the VIDC20 driver while games are running.
Changes since 2.88
*ADFBootFloppy now uses PipeFS to pipe extracted boot scripts to Obey, which avoids writes to the filesystem and potentially causing filesystem corruption if the game hard-locks immediately
changed ZIP_extract to support appending the extracted file to an existing file handle
Wasn't checking for Bootcommands 1.25, which caused the "X" commands in the ADFFS !Run to fail on OS's that include early versions of the Module
recoded strcmp / strcmp_insensitive and moved to global functions
recoded the checks for ARM / ARM3Support Modules
moved more in-line variables into vars
Switches the RPCEmu Extended Graphics Card off while a game is running
MkSetVars was setting ADFFS$ARMv7 incorrectly on a Pi1
JIT wasn't cleaning the Dcache correctly if the end address of the block was 1 byte short of the next cache line
SWI vector exit error handler was passing to the current Error handler in USR32 instead of USR26 on 26bit machines
ADFBootFloppy now passes command-line parameters correctly to the boot script
JIT fixed an abort while shutting down 26bit Modules when running on IOMD 32bit
reinstated the command table entry for *ADFScreenBorders
JIT LDM with PC continued processing instructions instead of exiting the JIT (fixes Saloon Cars Deluxe)
Allow comments after JITMEMORYA
fixed an issue where DiscOp should suspend creating missing sectors in JFD files (fixes Fire & Ice)
Known issues
Will hard-lock immediately if loaded on a Pinebook Pro. Neither the Pinebook or Pinebook Pro can run ADFFS due to an issue in their video driver
If a WiFi stack is loaded (ROD or ROOL), SDIODriver will randomly get into a race condition and appear to hard-lock the machine. This has been reported, but the root cause has yet to be identified
Audio is glitchy when the blitter is active, which is noticeable on a Pi when in MODE 32
Audio can be glitchy on a RiscPC SA 26bit
F1003801 Battle Chess (1993) (Krisalis Software) - slow on StrongARM
F1006501 Cannon Fodder (1994) (Krisalis Software) - goes into an unsupported video mode on RiscPC
F1060201 Chuck Rock [SA version] (2001) (R-Comp Interactive) - display is wrong when on a RiscPC
F1015401 Fire & Ice (1995) (Warner Interactive Entertainment) - copperbar timing is incorrect on a RiscPC, causing screen flickering
F1054501 Gods [RPC version] (2001) (R-Comp Interactive) - no sound effects and goes into an unsupported video mode on RiscPC
F1059801 Lemmings 2: The Tribes [SA version] (2001) (R-Comp Interactive) - music slows down in places on a RiscPC
R-Comp RPC/SA versions of games mostly rely on Mode definition files to work and return to the desktop in the game mode. eg. James Pond, Chuck Rock, Gods etc
Fixed issues
Games failing to start when run on a Pi1
Missing *ADFScreenBorders
Script changes
F1064501 Elite [v1.14] (1999) (Acorn User) - Corrected the line-fill list terminator check
F1003301 Asylum (1993) (Digital Psychosis) - Corrected two lines that should be commented out
F1070001 Asylum (2002) (Acorn Arcade) - Corrected two lines that should be commented out
F1046101 Burn'Out [SA version] (1997) (Oregan Developments) - Code fixes for self-modifying code and unaligned memory accesses
F1015401 Fire & Ice (1995) (Warner Interactive Entertainment) - Turned off legacy screen memory remapping (needs a fix for the intro)
All script - ensure X RMKill is used for all 26bit Module exit RMKill's
I've just tried this on a Pi 1B with 'RISC OS Pi' with 5.30, and also a recent RISC OS 5.31 ROM, and running Mad Professor Mariarti hard-locks the machine, sometimes with some noise coming from the TV, and 'press SPACE or click mouse...'. The previous release version of ADFFS also does it.
It's been a while since I used the Pi, so it's entirely possible I am doing something daft. I am trying out an 'improved' USBJoystick, but tried disabling that and reverting to the 0.22 supplied with ADFFS. No improvement.
I was able to run Pacmania, so perhaps it is something specific to MadProf? This is using the disc images from here.
I also tried E-Type, which locked the machine after drawing the 'E-Type' graphic (where I would expect the fade and the 'insert tracks disc' bit).
There's actually two issues. The ARMv7 detection isn't correct in SetVars, which causes the ARMv7 version of ADFFS to be loaded and the second issue is cache-line flushing isn't working on the Pi1.
The cache-line flushing is handled by the IMB_List ARMop in the OS, so it might be an OS bug.
EDIT: Not an OS bug, but a rare-case alignment issue in ADFFS. How the problem doesn't occur on SA, Pi2 and Pi3 is interesting.
This may be an issue in that last update: Zool doesn't work (Pi model and OS unchanged). I mount the floppy image (downloaded from this site), choose 'Boot floppy', click 'YES', and nothing happens. I am 99% sure that with the previous version (where MadProf failed), Zool ran OK.
Interestingly, if I try to run MadProf after a failed attempt to run Zool, then MadProf also fails (the screen clears, then it freezes). If I restart and run MadProf first, that's fine, and then attempting to run Zool will always fail. So I assume that once Zool fails, some things within ADFFS (or even RISC OS itself) get into a bad state.