forums.jaspp.org.uk

1. Take a backup of everything personal on your SD...just in case
2. Download the Nightly HardDisc4 image and copy the contents over your SD card from within RISCOS
3. Save your CMOS to the DOS partition via *SAVECMOS $.!Boot.LOADER.CMOS
4. Update the Pi firmware files (BOOTCODE.BIN, FIXUP.DAT, START.ELF) - make copies of the originals just in case
5. Replace RISCOS.IMG with the latest Nightly build
6. Add the following lines to CONFIG.TXT
ramfsfile=CMOS
ramfsaddr=0x508000
7. Reboot and keep your fingers crossed

Hi,

I've just discovered this project and I'm so pleased I have. Thanks Jon for all your hard work! I does mean I'm very new to everything and am trying to understand it all...

I've just set up my Pi B (the original one) and got it working. It plays Lemmings and Cannon Fodder (with a few oddities that I'll put in a different post). However all I did was:

Install RC15
Download the nightly ROM and replace the riscos.img
Installed anymode
Disabled GPU mode change support
Downloaded and used adffs261

Regarding the instructions above...
What does the CMOS change do?
Do the Pi firmware files need to be updated if I use RC15?
What do the CONFIG.TXT files change?

Thanks in advance

Gareth

gareth wrote:What does the CMOS change do?
Do the Pi firmware files need to be updated if I use RC15?
What do the CONFIG.TXT files change?

The CMOS change is only required when upgrading from RC14...it was a change to the OS.

Yes, firmware files will need updating for RC15.

CONFIG.TXT configures the Pi firmware blob, so things like resolution, upscaling type, CPU speed etc

Hello Jon

I have recently set up my Pi2 with Risc OS 5.23 (RC15) and changed the RISCOS.IMG file to the latest nightly build. Pretty much everything I've tried works fine via ADFFS.

However I find that most of the games which are intended to run natively don't work - they give error messages saying they are not 32 bit compatible. This doesn't affect Zool, but does affect Hamsters, Exodus, Chocks Away, Darkwood, Revolver, Sunburst etc.

Is this normal? I know about the differences between 26 bit and 32 bit applications, but equally (a) I thought these versions could run natively and (b) Under ADFFS, some really old games run - surely these are not 32 bit compatible, and yet they work!

I'd be interested to understand what is going on here, even if it isn't fixable.

Thanks -- john

None of those games (except SunBurst 32bit) will run natively, they're all 26bit. Most of them will run under ADFFS if you use the appropriate boot script in !ADFFS.Obey.

The ID's are all listed at the bottom of the Help file, or you can look at the known working list which details all the games that work on the Pi.

Thanks Jon,

I take it all I need to do is swap the !Run file, not actually move the game onto a floppy image?

Tried it on a few games, and it works - thanks for the advice!

Sunburst is definitely the 32 bit version though, and whilst it loads to the icon bar ok, if I click on its icon, it crashes out with (I think) abort on data transfer at line 188. I can bring up the exact memory location if it would help.

Sounds like you figured it out, essentially replace !Run and then remove the first few lines that switch to ADFS and set Obey$Dir to point to the floppy drive.

SunBurst - yes, crash info may help diagnose the issue.

It's:

Abort on data transfer at &0002F230 at line 188

jms2 wrote:Abort on data transfer at &0002F230 at line 188

It's an alignment fault in one of the plot routines, I'll need to have a look at the source and figure out a fix.

Ok Jon - I've never actually played Sunburst so there's no urgency at all as far as I'm concerned! I just wanted to make you aware in case it was a clue to some wider underlying issue.