Floppy Image Runner - ideas for new version:

[Petari]

I'm thinking about some new solutions in Floppy Image Runner :

Current versions work in way that load floppy image in RAM, and reading/writing from/into it. Bad side is that any writings (saves) to current "floppy A" when it is installed go to RAM, so will be lost after removing it from RAM. There is of course solution against it: if saving to 'floppy B' it goes on real floppy A.
But we like more saving to hard disk, I guess. And we would like support for multi floppy games.

So, the new concept is: instead copiing image(s) to RAM   working with them from hard disk during gameplay. It needs some more advanced coding, hard disk driver reinstall etc. , but all it I done already in some adaptations ...  The benefits:  less RAM occupied - even with many floppy games.
Saves go in images self, so will be permanent.

The biggest problems to solve I see  'disk' changing - actually setting current active image (when game asks to insert some cpecific floppy).
We need some good way to do it, while screen is occupied with game content. Likely giving some infos by border color.
Ideas: RED means: waits for image change - then by pressing keys 1-9 set active image. Feedback by border color change to green for instance ...
It will need some extra code too in some cases - as games may complete disabling IKBD access for TOS . Will see ...

Last question is what games will work with it, and are not already hard disk adapted ?
Of course, only games with regular files on floppies have chance to work .  Some adventures for instance. Please give some titles what you think that may work - multi floppy ones in first place. (Check first h.d. adapt list, please).

[Anemos]

Oh i think first time i see that thread ..
The idea using the HD space ram to run routine like cache is sound good.
Any way.. maybe stupid thing ,but i dreaming the future Floppy Image Runner like this:
one panel with a lot virtual drive slots A: B: ect.. to put there the images of multi disks games..
And.. run..