dosfs problem?

I’ve been running RO 5.19 for a couple of months on my Iyonix and have come across the following problem. The process is as follows:

1) I create a file on windows
2) On windows copy and paste it to the SD card (fat formated)
3) read the file from the card on my iyonix

This is repeated a number of times

If at stage 2 the copied file already exists on the SD card and I elect to replace it, at some point as the file gets bigger the Iyonix will not be able to read all of the file (it is truncated) – windows reads it correctly.

If at stage 2 I delete the file on the sd card in windows before pasting everything works ok

It seems to me that when windows increases the file size (pasting over the original file) by fragmenting the file iyonix can’t read the fragmented part.

Presumably deleting the file first makes windows find a contiguous block for the file.

I don’t know if this is a known problem but I thought I’d mention it.

Does the same happen with FAT32FS and 5.18?

Is it the latest 5.19?

I’m still on 5.18, (on my Iyonix) what improvements does 5.19 have?

I’m afraid I don’t know anything of fat32fs I just plug my card reader in so presume its using dosfs

No its not the latest 5.19. I made a Serial Port pic programmer and in writing the software for it discovered that 5.18 has a bug in the hal_uart code which mean’t I didn’t have low level access to the uart. This is fixed in 5.19 and I daren’t upgrade the version I’m using as its working ok – I had to work around saving the monitor definition not working but I expected problems with a beta version.

Unless you need something I wouldn’t bother upgrading until 5.20. The problem for me is not so much the rom upgrade but !boot. You’re not sure if things that are run in !boot at startup should be changed with the rom upgrade and if you do change !boot how does that effect going back to 5.18 if you have to.

Do think the new usb drive icons (a usb plug) look like a soldier in a beefeater hat – even more so when there is a row of them.

FAT32FS might be a work around.

No its not the latest 5.19.

You might want to check if you’re new enough to have DOSFS 0.95 which may well have fixed the problem you’re seeing.

You’re not sure if things that are run in !boot at startup should be changed with the rom upgrade and if you do change !boot how does that effect going back to 5.18 if you have to.

!Boot retains full backwards compatibility (right back to RISC OS 3.50 currently). It doesn’t attempt forward compatibility, if such powers existed they should be used for buying lottery tickets not writing software. So, newer !Boot will still allow you to drop back to 5.18 in ROM if you wish.

I am running DOSFS 0.95 unfortunately. Its not really a problem for me I can work around it.

Its not the !Boot application itself which confuses me its whether the files in predesk which are essentially, it seems to me, part of the operating system are still relevant to the updated rom or even whether there are updated versions to go with the new rom. When updating the rom should I:

1) Leave my !boot alone and work around things that don’t work – like saving of the monitor definition in my case
2) Replace my !Boot from the latest harddisc4 and reinstall all my apps
3) Merge my !boot with the new !boot – presumably removing !System and !Fonts before merging them separately