Drive options precedence: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
'''WARNING''' this page is outdated and incomplete, move over to [[Drive Emulation Type Cleanup]] | |||
Disk drive emulation has the fallback order | Disk drive emulation has the fallback order | ||
* true drive emulation (TDE) | * true drive emulation (TDE) | ||
| Line 8: | Line 11: | ||
In detail: | In detail: | ||
# Drive #. model must not be None. (''None'' = no drive) | # ''Drive #. model'' must not be ''None''. (''None'' = no drive. Stop.) | ||
# If TDE is enabled, this is used. No image attached = empty drive. | # If ''TDE'' is enabled, this is used. No image attached = empty drive. | ||
#: These options are relevant: | #: These options are relevant: | ||
#* Drive sound emulation | #* Drive sound emulation | ||
#* Drive #. model / * (must not be None) | #* Drive #. model / * (must not be ''None'') | ||
#* Drive #. options / Read only access | #* Drive #. options / Read only access | ||
#* Drive #. expansion / * | #* Drive #. expansion / * | ||
#* Drive #. 40-track image support / * | #* Drive #. 40-track image support / * | ||
#* Drive #. idle method / * | #* Drive #. idle method / * | ||
#: Note that if ''TDE'' is enabled, and you want to use disk files, then ''Enable Virtual devices'' should be disabled, otherwise there are buggy side-effects (see [https://sourceforge.net/p/vice-emu/bugs/580/ Bug #580]). Unfortunately, to use a printer, this option should be enabled... | |||
#: Otherwise (if no TDE)... | #: Otherwise (if no TDE)... | ||
# ''Enable Virtual devices'' must be enabled (otherwise there is no drive). | # ''Enable Virtual devices'' must be enabled (otherwise there is no drive. Stop.). | ||
# If a disk image is attached to the drive, this disk image is used, regardless of the selection in ''Drive #. device type''. | # 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: | #: These options are relevant: | ||
| Line 26: | Line 30: | ||
#* Attach disk image / Unit #.... | #* Attach disk image / Unit #.... | ||
#: Otherwise... | #: Otherwise... | ||
# Drive #. device type = None -> no drive | # Drive #. device type = None -> no drive. Stop. | ||
#: Otherwise... (no disk image is attached) | #: Otherwise... (no disk image is attached) | ||
# Drive #. device type = File system access -> directory is accessed | # Drive #. device type = File system access -> directory is accessed | ||
| Line 49: | Line 53: | ||
#: Having these 2 things for IEC devices seems unneeded? | #: Having these 2 things for IEC devices seems unneeded? | ||
#: What happens if one of the options is selected but not the other? | #: What happens if one of the options is selected but not the other? | ||
[[Category:Deprecated]] | |||
Latest revision as of 18:27, 23 March 2023
WARNING this page is outdated and incomplete, move over to Drive Emulation Type Cleanup
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:
- Drive #. model must not be None. (None = no drive. Stop.)
- 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 / *
- Note that if TDE is enabled, and you want to use disk files, then Enable Virtual devices should be disabled, otherwise there are buggy side-effects (see Bug #580). Unfortunately, to use a printer, this option should be enabled...
- Otherwise (if no TDE)...
- Enable Virtual devices must be enabled (otherwise there is no drive. Stop.).
- 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...
- Drive #. device type = None -> no drive. Stop.
- Otherwise... (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
- Drive #. options / File system directory...
- Drive #. options / Convert P00 file names
- Drive #. options / Create P00 files on save
- Drive #. options / Hide non-P00 files
- Otherwise...
- 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...
- 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?