Boot partition corruption?

This is a Loader partition created with SystemDisc. I update ROM images by simply dropping them into the Loader partition. It’s still the last file in and worked OK. Since the beginning of last week I’ve found that my Beagleboard -xM will fail to start after doing this. If I replace all the files (MLO, U-BOOT/BIN, BOOT/SCR, UENV/TXT) then there’s no problem.

Any ideas as to what’s changed?

Though dropping the ROM into the partition then dismounting it works.

Any ideas as to what’s changed?

The usual issue is that a file has ended up as an extended filename (i.e. not 8.3 capitals). One suggestion is that you make sure that you dismount the boot partition after copying something into !Boot.Loader, remount it and examine Loader to make sure it looks right. That way you can sort out the issue from RISC OS without having to take the SD card out.

One suggestion is that you make sure that you dismount the boot partition

Yup, that works. Dismounting means there is no issue. I’m just puzzled as to why closing down doesn’t have the same effect given that all should be dismounted at that point. Used to be OK.