Drive handling broken with latest/production MEGA65 bitstreams

[bluewaysw]

GEOS uses parameters to flexible mount different kinds of F011 connected drived to the 4 GEOS drives:

• real internal floppy
• real external floppy
• D81 compatible mount
• virtual D81

For this the following regisister has been used:

• real floppy or SD backed mounted drive 0 or 1
• virtual drive 0
• flipping inernal and external real floppy drive

GEOS strategy so far is to:

• is virtual drive 0 if virtual is activated
• use mounted drive 0 or drive 1 if mount cluster is the expected one (is the image we mounted last time)
• use drive 1 and parameter for real floppy, SD mount and real floppy swap to configure on demant
  • SD mount drive of some image selected by its name
  • internal real floppy
  • extern real floppy

By this GEOS supports mount to mount copying or internal to external floppy copying while still have the other variants accessible.

It seems that with the latest bitstreams at least the contol if F011 drive is accessing SD mount or real floppy is read only for application.

[bluewaysw]

This relates to those bitstream changes:

• MEGA65/mega65-core#193
• MEGA65/mega65-core#192

For this the drive integration logic in GEOS needs some update, that decreases the flexibility how drives may be combined and used together:

• to access SD 81 mountable drive from GEOS there need to be at least one unit configured as mounted SD card when GEOS is started or set via Freezer
• to access real floppy (internal or external) this need to be configured from the outside as well
• if there is on drive in virtual mode and real floppy is active, no SD 81 will be usable

So far the implementation assumes virtual drive if present to be drive 0, all the other drive types are access by configuring drive 1. Base on the referrenced changes this need to change.

[bluewaysw]

Fix implemented and merged to master branch.

[bluewaysw]

Done, Chancen Mercedes to Master.