Filetype corruption with SparkFS on recent 5.25 builds

If no one has any complaints I’ll make 1.45 the latest version.

No complaints here, but I must say thank you for resolving the the issue, I can’t be without SparkFS.

I’m going to do a new version of SparkFS that handles the zero load/exec address case. If no one has any complaints I’ll make 1.45 the latest version.

No complaints here, but I must say thank you for resolving the the issue, I can’t be without SparkFS.

Agree on both counts; 1.45 does the trick.

RISC OS documentation needs updating or at some point all this will happen again.

I’ve split the middle sentence to make it clear what FileSwitch really does.

As a wiki person, I’ve edited the docs too:

If R2 and R3 are both zero your filing system should not try to restamp the file.

This can occur because:

You returned from the FSEntry_Args? 9 (or ImageEntry_Args? 9) call with these values indicating that your filing system doesn’t support stamping open files
FileSwitch knows that the file has not been modified
FileSwitch does not want you to restamp the file

I hope that is the end of me messing you about (for now).

I’ve made the fixed version the latest version, you can upgrade from here:

https://www.davidpilling.com/sfs145.zip

I’m saying this because the “beta” link above is about to disappear. This upgrade link results in a SparkFS identical to the “beta” version, so no need to download again.

What is the mechanism that prevents someone installing RISC OS 5.25, copying files using SparkFS, losing data, and blaming me… Does it say in release notes “upgrade SparkFS”, or does the OS warn about old versions of applications. I now see SparkFS should say “new version available”. Hmm.

What is the mechanism that prevents someone […] blaming me…

A note in the ReadMe inviting users to periodically check such and such a website for updates?

RISC OS has typically completely avoided the automated update checking thing. I tried to write one for Manga, but it only works for the beta track as I have control over the server used (there is no information on how to interact with the !Store server to check versions). Worse, !Store doesn’t appear to keep any record of what you have installed so it can’t notify of available updates. It’s still a very manual thing, updating most RISC OS software…

!Store does have a way of knowing what you have downloaded if you are a registered user, it keeps track of what software you have downloaded and tells you if there are updates for those software packages.

It’s still a very manual thing, updating most RISC OS software…

One of these days we’ll get you over to PackMan, kicking and screaming… :)