ADFFS 2.80 public beta
Re: ADFFS 2.80 public beta
@Jon: With regards to Diggers, I typed the command sequence you asked me to, and I can see a blue-ish background with the intro music for a second, then the game hangs completely and I have to reboot the system.
When simply running the !Diggers app after loading ADFFS, this is what I see during the intro before the MILLENIUM logo appears:
It's moving and I can hear the intro music.
After the intro completes in that ugly state, the Millenium logo appears and the game runs fine after that.
When simply running the !Diggers app after loading ADFFS, this is what I see during the intro before the MILLENIUM logo appears:
It's moving and I can hear the intro music.
After the intro completes in that ugly state, the Millenium logo appears and the game runs fine after that.
- Attachments
-
- photo_2022-01-13_18-06-09.jpg (107.51 KiB) Viewed 2916 times
Re: ADFFS 2.80 public beta
It looks like the Pi has gone into a weird resolution. I'm presuming *DigModeOn did result in a working MODE?
Re: ADFFS 2.80 public beta
I've attached ADFFS 2.80k to the OP. This is primarily aimed at RISC OS 3.1x users that want to image floppies in JFD format and is the first update to reduce the memory footprint required. The JFD imager app now requires 1056KB when imaging SD/DD floppies, which is down from 1920KB that it previously required.
Its still reliant on SparkFS to access the two ZIP archives it uses, so actual memory usage is higher, needing several hundred KB free for SparkFS to operate. I'll be looking at removing this dependency in a future update.
Its still reliant on SparkFS to access the two ZIP archives it uses, so actual memory usage is higher, needing several hundred KB free for SparkFS to operate. I'll be looking at removing this dependency in a future update.
Re: ADFFS 2.80 public beta
ADFFS 2.80l now available in the OP. This removes the dependency on SparkFS when imaging floppies, all ZIP file processing is now handled via ZLib.
This reduces the memory footprint by around 300KB, which should hopefully make imaging on 2MB machines viable.
This reduces the memory footprint by around 300KB, which should hopefully make imaging on 2MB machines viable.
Re: ADFFS 2.80 public beta
@Jon
About the Diggers strange video mode, maybe we have different settings in config->screen?
I have these Display Settings:
Monitor type: Generic
Resolution: 1280x720
Colous: 16 million
Frame Rate: 50Hz
Are they OK?
About the Diggers strange video mode, maybe we have different settings in config->screen?
I have these Display Settings:
Monitor type: Generic
Resolution: 1280x720
Colous: 16 million
Frame Rate: 50Hz
Are they OK?
Re: ADFFS 2.80 public beta
Physical screen resolution doesn't matter as the Pi is upscaling. You've already confirmed the bespoke MODE worked as you could see the Supervisor command-line after *DigModeOn.
I don't really know what the issue is. If it was a bug in the game code or ADFFS, I'd expect to see it myself.
How much memory have you allocated to the GPU in CONFIG/TXT?
Re: ADFFS 2.80 public beta
@Jon: I have 64MB allocated to the GPU, but I am pasting my entire config.txt here, in case you see something that could be at play:
Code: Select all
fake_vsync_isr=1
framebuffer_swap=0
gpu_mem=64
init_emmc_clock=100000000
ramfsfile=CMOS
ramfsaddr=0x508000
kernel=RISCOS.IMG
[pi4]
enable_gic=1
# NOOBS Auto-generated Settings:
hdmi_group=1
hdmi_mode=19
#Forces jack audio
#hdmi_ignore_edid_audio=1
#Forces hdmi audio
hdmi_drive=2
force_hdmi_open=1
config_hdmi_boost=4
disable_overscan=1
overscan_left=-32
overscan_right=-32
overscan_top=-32
overscan_bottom=-32
#audio_pwm_mode=2
Re: ADFFS 2.80 public beta
It was just a stab in the dark.
And you see exactly the same behaviour if you perform a SHIFT power-on and manually run !ADFFS, followed by !Diggers without going into the Wimp?
And you see exactly the same behaviour if you perform a SHIFT power-on and manually run !ADFFS, followed by !Diggers without going into the Wimp?
Re: ADFFS 2.80 public beta
If I boot while pressing SHIFT, I get into the desktop.
And the behaviour woth Diggers is the same.
What do you mean by "without going into the Wimp"? Booting to the command line instead of the desktop? How?