Drive options precedence

Disk drive emulation has the fallback order

• true drive emulation (TDE)
• disk image emulation
  • file system access, or
  • raw /dev/fd0 device access, or
  • real IEC device access via OpenCBM.

In detail:

1. Drive #. model must not be None. (None = no drive)
2. If TDE is enabled, this is used. No image attached = empty drive.

These options are relevant:

Drive sound emulation

Drive #. model / * (must not be None)

Drive #. options / Read only access

Drive #. expansion / *

Drive #. 40-track image support / *

Drive #. idle method / *

Otherwise (if no TDE)...

1. ``Enable Virtual devices must be enabled (otherwise there is no drive).
2. If a disk image is attached to the drive, this disk image is used,

regardless of the selection in ``Drive #. device type.

These options are relevant:

Drive #. options / Read only access

Drive #. 40-track image support / *

and this action:

Attach disk image / Unit #....

Otherwise...

1. Drive #. device type = None -> no drive

Otherwise...

1. If no disk image is attached:

Drive #. device type = File system access -> directory is accessed

sets resource FileSystemDevice8 to ATTACH_DEVICE_FS

These options are relevant:

Drive #. options / Read only access

File system directory...

Convert P00 file names

Create P00 files on save

Hide non-P00 files

Otherwise...

1. Drive #. device type = Raw device access -> use a real host OS floppy drive

sets resource FileSystemDevice8 to ATTACH_DEVICE_RAW

These options are relevant:

RAW block device name...

Otherwise...

1. Drive #. device type = Real device access -> access device via OpenCBM

sets resource FileSystemDevice8 to ATTACH_DEVICE_REAL

These options are relevant:

Drive #. options / Enable IEC device

It sets resource IECDevice8

Having these 2 things for IEC devices seems unneeded?

What happens if one of the options is selected but not the other?