defaults to 'TRUE' (same as previous versions of MMFS) and uses same
filesystem number and range of file handles as DFS
if set to 'FALSE', will use distinct filesystem number (&74) and range
of file handles (starting at &70) to be distinct from DFS and not clash
with any other known filesystem -- this is to support co-operation with
a standard DFS, in particular when using FileSwitch on the BBC Master,
allowing '-MMFS-' filename prefixes to be supported (which previously
would cause a clash with DFS, when switching temporary filesystem)
when this option is enabled, the ROM title (as displayed by *ROMS) will
show ' (xFS)' on the end, to indicate it is NOT emulating DFS
the version number has been changed to 1.41M, just to indicate that
it's distinct build from the release 1.41
a better long-term fix would be to support *OPT 5 to disable/enable
this at run-time, but users with DFS lurking about may still prefer
this to be set to FALSE by default, in their build
this is specified in the top_xxxMMFS.asm files
defaults to 'TRUE' (same as previous versions of MMFS) and uses same filesystem number and range of file handles as DFS
if set to 'FALSE', will use distinct filesystem number (&74) and range of file handles (starting at &70) to be distinct from DFS and not clash with any other known filesystem -- this is to support co-operation with a standard DFS, in particular when using FileSwitch on the BBC Master, allowing '-MMFS-' filename prefixes to be supported (which previously would cause a clash with DFS, when switching temporary filesystem)
when this option is enabled, the ROM title (as displayed by *ROMS) will show ' (xFS)' on the end, to indicate it is NOT emulating DFS
the version number has been changed to 1.41M, just to indicate that it's distinct build from the release 1.41
a better long-term fix would be to support *OPT 5 to disable/enable this at run-time, but users with DFS lurking about may still prefer this to be set to FALSE by default, in their build