Re: [hatari-devel] Floppy images cached?

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


Le 01/07/2025 à 07:40, Thorsten Otto a écrit :
On Montag, 30. Juni 2025 23:08:55 CEST Eero Tamminen wrote:

 > There's no locking between TOS (or some Atari floppy manipulation

 > program) running inside Hatari, and some external program user may run

 > outside Hatari to also modify the floppy image FS content directly, or

 > any co-operation in how they cache the FS contents.  And I do not see

 > how there could...


Yes, but that also applies to HD-images.


I understand that floppies are different, because they can also have formats that cannot be easily accessed using seek/read/write, but it would be nice if atleast *.st format could be treated the same as HD images, and not cached in memory.



depending on the type of disk image, this can be complicated to write data as soon as they are changed (for example MSA is compressed, so changing 1 sector in the middle of the file can shift the whole image).

In such case, whole image would need to be flushed after a write, which would add some overhead. Or there could be some kind of deferred write after a small amount of time, but all in all, this requires some work to be done in the floppy part of Hatari.

..ST images are simpler, but some work needed nevertheless, so, depends on who could volunteer to have a look at this.

Nicolas



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/