|Re: [hatari-devel] Reload ROM/floppy on reset|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Reload ROM/floppy on reset
- From: Vincent Rivière <vincent.riviere@xxxxxxxxxxx>
- Date: Sun, 10 Apr 2016 00:38:28 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=zlI2O7JYaIMyFruEZHDqaW+ayFO8b9jfvJZpt/9uBKo=; b=uVhaG6q0j/l6lVeb5c0eYRFImNC7hnAxyOs2x9tXzVaSKEr0JGLiM5uoROCYA+/9B6 Sm3jkj5QtpxRdpaUOMXqzwkDwuLxAxyea+8tW6iqZ9u2TTFf0bpqTons9vYaGqnFi8tx q8otd3GOVRKOktJ8OnwTNlQIsjRg9ohq9OhJPcZFyN7YekW6Jevs5dwuCu6kIcBJu6sn p9OIN1Mc2BB0BCtQ2eO5ISrk95KiMuD0c/GQA7wa98ot9nLkaEkoEbNtv6FQf5R7JRh3 lUUnyBL1kC0zQhbbsA/eRJ1RoIFI6LoRHcJnimsAltpiksIPQxz+U9sJ83G6zpZkRAKB KDAQ==
On 09/04/2016 22:06, Thomas Huth wrote:
That's maybe doable for ROM images, but I think it's not so straight
forward for floppy (and other writable) images:
Ah, I forgot the question about writable media.
My initial wish was about a developer working on a read-only media, such as
a custom ROM or a game/demo boot floppy. The kind of media which is never
written from the ST side.
For example, I'm currently working on the bootsector of emutos.st.
The Hatari debugger is a key tool to debug that stuff. But working managing
the floppy image in Hatari is a real pain: I have to go to the UI to eject
it, then it loses the path, I have to browse folders again... And finally
On the other hand, Steem is much better regarding to this aspect. In the
cross-tools window, I just have to type "make". Then Alt+Tab to switch to
Steem, press the Reset hotkey, and voilà. Actually, I just miss a debugger
with Steem. IIRC, there was a special Steem Debug build, I should try that.
By looking more closely, Steem sets some kind of lock on the floppy image,
as it can't be deleted while running. However, it can be written, which can
cause the kind of issues you described. But that's not a real problem. Who
is going to write to a floppy while an emulator is running? No one, except
developers who knows what they do.
If really unexpected data corruption is a problem, then there should be an
option to mount floppies as read-only (I look at the UI... it is already
here!). In this case, the whole floppy data could be cached in RAM, and no
need at all to lock the floppy image.
to be really save, you always have to eject the floppy image from the
emulator first before you change it directly in the host.
My wish would be that Hatari automatically does that on reset.