Pi400 RiscOS query

Hello All,

I’m new to these forums and practically new to RiscOS. I had prior knowledge of it as I used it in school on the A3010 and then the RiscPCs so know a little bit about it but not used it at all since those days. I’m not sure if this is a bug so sorry if this has been posted in the wrong place.

I wonder if you can help me out here. I don’t know how many of you own a Pi400 and have RiscOS Open running on it (RiscOS 5.28).

I have a little problem, I’ve got a 16GB Kingston data traveller USB stick that I use for some APDL software to run on the RiscOS. When I put it into any of the USB sockets on the back of the Pi400 the system crashes. I can still move the mouse pointer about but can’t click on anything. The only way to resolve it is to reboot the Pi400.

I also have a Sandisk Cruzer 8GB USB stick, I’ve copied the files onto it from the 16GB stick and now the system recognises there is a USB stick there however, when I click on the USB stick icon it brings up an error message: ‘Error when reading SCSI::0.$ – Disc not understood – has it been formatted?’.

I’ve ben doing some research and found that it is something to do with the Fat32FS module. It doesn’t appear to be loading at boot time for some reason. The files are located in !Boot.Choices.Boot.Predesk.Fat32FS and I can double click on the module and the USB stick can then be read.

I guess my question is, why isn’t the Fat32FS being loaded at startup? I have updated it with the latest version from Jeffery Doggett’s site however, it still doesn’t appear to be loaded at boot time.

Has anybody else had this happen to them and how did you fix it?

The same thing happens on the Pi4 too. I get the error message when trying to open the Sandisk Cruzer USB drive. I don’t get a system crash though when I put my Kingston 16GB Drive in however, I still get the error message being displayed when clicking on it.

Kind Regards,

Brett

When I put it into any of the USB sockets on the back of the Pi400 the system crashes.

If you’ve got a USB2 hub, plug the hub into the Pi400 then plug the USB stick into the hub. It’s not guaranteed to work, but it’s worth a try.

I guess my question is, why isn’t the Fat32FS being loaded at startup?

You may have copied only the Fat32FS module – there’s a !Run file that needs to be copied as well. This is done by means of the Copy_To_Boot Obey file inside the Fat32Fs ZIP archive:

1. Delete Fat32FS from !Boot.Choices.Boot.Predesk
2. Unpack Fat32FS.zip (e.g. to a RAMDisc)
3. Double-click on the “Predesk” folder thus created
4. Double-click on “Copy_To_Boot”. This will copy Fat32FS and the !Run file to !Boot.Choices.Boot.Predesk
5. Reboot and check that Fat32FS is loaded by issuing the command:
   *Help Fat32FS

Hi Stuart,

I haven’t got a USB hub unfortunately to try this with.

I have got both files in !Boot.Choices.Boot.Predesk and the *Help Fat32FS command doesnt work upon reboot. It says it’s not found. It’s pretty odd really.

It does the same on the RiscOS Direct too.

Regards,

Brett

What other things do you have in PreDesk? It is possible that something that would be run before Fat32fs is failing, causing the remaining items in PreDesk to be skipped. Are you sure the boot process is completing fully?

If you copy the Fat32fs directory out of PreDesk and run it manually after boot, does Fat32fs then load and function?

Edit: Sorry, I see you have already done this.

*Help Fat32FS command doesnt work upon reboot

OK not sure if you have manually run the !Run file in the Fat32FS directory so can you confirm you have done this and then check *help Fat32FS.

It certainly sounds as if your Boot sequence is bailing out.

One of the MUG members had an issue with a similar outcome brought about by the Monitor type set/they were using.

Are you usiung the same monitor and what does your Pi400 say it is using in !Boot>Configuation>Screen

Reporter
is your friend so download it via this link

Update: You can manually check the !Boot.Choices.PreDesk.Configure.Monitor file as well.

I’m not using a specific monitor, it comes up as unspecified. When I try to set the screen resolution it says something about the edid not being found. I’m using a 1080p TV that has HDMI on it. Everytime I reboot the Pi400 or Pi4 I end up having to reset the screen resolution again.

When I manually run the module by double clicking on it I can access the Sandisk Cruzer USB stick with no problem. But even with the Fat32FS running if I plug the Kingston Stick in everything grinds to a halt, I’ve no idea why as I’ve used it before with no problems on other OS’s on both the Pi4 and Pi400.

I wonder whether Harinezumi’s BootLog file might reveal something useful.

It looks as if the EDID process errors. The error stops the boot so Fat32FS does not get set up.

The simplest thing to try is to manually set up the display. Double click on !Boot, single click on Screen, click on the Monitor type menu pop-up, go to Other then Generic. Select a Resolution of 1920×1080.