Changes
/* Extended 1M-4M Expansions (RAM7/Yarek-style) */
(*) For example 7B01h or 7B7Fh would be no good, because the FDC command register at FB7Fh is mirrored to these locations. Using 7B80h..7BFFh would fix that problem, but might conflict with other connected expansion hardware.
* '''Compatibility''' - The first 512K (Port 7Fxxh) are fully compatible with dk'tronics. Using the next 1.5MB (Port 7Exxh,7Dxxh,7Cxxh) should similarly work without conflicting with the other hardware expansions.
* '''Compatibility Problems''' - The last upper 2MB (Port 7Bxxh,7Axxh,79xxh,78xxh) of a 4MB expansion can conflict with other hardwareas setting A10 to 0 is also used for many hardware expansions. As workaround: Either leave them unused, or If those hardware expansions do not check A15 (and most don't) they might get activated if a RAM bank in the range 2-4MB is accessed. If you need to use RAM in that range make sure to use values for "xx" that do not conflict with your hardware (which values are good for "xx" and which aren't good depends on what other hardware you have connected) (and obviously, different ". If unsure use &FF for xx" may be needed in 7Bxxh as in 7Axxhno custom hardware expansion should react if all bits of the lower byte are set. So e.g. OUT &78FF, for example&C4 or OUT &7AFF,&C5 should always be fine whereas OUT &7800,&C4 or OUT &7AC5,&C5 (as happening sometimes with speed optimised code)might unexpectedly turn on a feature on an expansion.
== Capacity ==
