This screen mode is not suitable for displaying the desktop

Anybody tried making the image file read only?

Go back four posts. Repeat as necessary.

Unless you mean the image file Boot:Loader – unfortunately that’s the only place RISC OS can store changed CMOS values (whether it is inside the ROM image or a separate file called ‘CMOS’) so that they can be seen on start up, before RISC OS boots.

Anybody tried making the image file read only?

Ah – you mean the file containing the ROM image on the SD card, RISCOS/IMG as opposed to the card itself (where we’re talking about a non-partitioned card, but keeping all the RISC OS stuff on a memory stick/pen)!

That way we have a suitable for filing system, ie; changed to SCSI for the Boot – already in a default image, but this is changed/swapped-out on the RO side for an editable/save-able “CMOS” file in Boot.

Does the RPi boot respect DOS file access settings? I don’t see why it shouldn’t!

The possibilities may still remain!

OK – how do I start a new thread?

Go to the main forum index, click on the link to the forum you want, and then above the list of topics there’s a “new topic” link.

David: Can you try posting the mode file created by *CreateModeFile? ScreenModes’ EDID handling isn’t perfect, but it will be a lot more complete than Chris’s code.

ScrHelp version 1.04 now decodes EIA/CEA-861 extension blocks containing VDBs with SVDs and containing DTDs as well as the established timing bitmaps, standard timing information and the four most preferred DTDs from block 0 that the previous versions 1.00 onwards decoded.

As none of my monitors use extension blocks testing has been rather limited though (one of my monitors specifies 80 odd extension blocks to follow but they are all blank)..

ScrHelp version 1.04

The RPI firmware here is on a single FAT partition SD card at SDFS::0.$

!ScrHelp 1.04 only looks for START/ELF in Boot:Loader

!ScrHelp is a very useful tool, it even reminds me I have over-volted my RPi3.

David Pitt
Your instructions for booting from a SCSI USB pen works fine for a Kingston DataTraveler 8 GB USB pen.
But i wanted to use an old 2,5 inch from my Mac mini as USB Harddisk and than it doesn’t work.
After a lot Googling i discovered that it doesn’t work because when you use *co. FileSystem SCSI in fact you make a bootdrive on SCSI::0 (This is a removable USB pen)
When you use an USB harddrive and format it with !Hform it wil get SCSI number 4.
In stead of using *co. FileSystem SCSI you have to use:
*Configure SCSIFSDrive 4
*Configure Boot
When i did that it worked fine after a Reboot.
So I do have now a Raspberry Pi 2 with an old Mac mini Harddisk and it boots from the Harddisk.

Maybe this was obvious for seasoned RISCOS users, but not for me. But in the end I managed it and learned a lot.

By the way I like the ROOL RISC OS Pi desktop more than the Standard Desktop and I wanted to have the third party applications from RC14 so I copied the RC14 image to the Harddisc and that worked fine to. I have now a RPi 2 with RC14 booting from a USB harddisk.

I learned from Raspberry.org that you can boot Raspbian from a USB harddisk without a SD card. I wil try to do that with RISCOSpi. You can do that only with the Raspberry Pi 3 and not with the older ones (RPi B+, RPi 2 and so on).

Configure SCSIFSDrive 4

I have added that now My apologies it was an omission.

David

Thank you for changing it. It works fine now. For me it wasn’t an omission but a learning moment ;-)
I am new to RISCOS (about a year) and i have to learn a lot, but that’s the fun of it.