|Re: [hatari-devel] TOS v4 / TT-RAM issue with floppy images|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 27/11/2017 à 11:17, Thorsten Otto a écrit :
On Montag, 27. November 2017 10:35:24 CET Nicolas Pomarède wrote:
maybe an extra
program would be needed at boot to intercept TOS accesses and ensure FDC
data are transferred between RAM and TT RAM.
It depends on where the access is coming from. You could catch calls like
Floprd/Flopwr (maybe that can already done by Hatari, without the need of an
extra program), but if the hardware is accessed directly, it will be too late.
The bios of TOS 3.06 at least will call the internal routines directly,
without going through the BIOS trap, so that might be difficult. For this you
have to hook also at least the hdv_ system vectors. Another difficulty might be
if some XHDI-capable driver is used, don't know how they behave if you are
trying to access a floppy through this.
That would be lots of change for no real use and as this is not a real
Falcon setup, maybe just leave it as is and add a note that TT-RAM for
falcon is an emulation hack and might cause errors with floppy (would
not be a problem most of the time as people using TT-RAM are certainly
likely to use HD emulation at the same time, not floppy)