The first commit makes sure that AutoSet64k does not reduce the memory of a 128k gigatron to 64k. Note that when 128K is enabled, Memory::getSizeRam() still returns 64k because the memory allocation tracker only knows about the 64k. However, when this is already 64k, there is no need to resize the memory to 64k because it is already 64k or 128k...
The second commit resets the romType of the builtin ROMv5a to 0x40 instead of 0xf8. It seems that this is not a ROMv5a but an early devrom with a couple bug fixes. I left the bug fixes and just changed romType and two comparison tests (one in Apple-1, another in CardBoot). Note that you might have had a reason to do this. Feel free to kill this one.
Hello AT67,
This pull request has two fixes for gtemuAT67.
The first commit makes sure that AutoSet64k does not reduce the memory of a 128k gigatron to 64k. Note that when 128K is enabled, Memory::getSizeRam() still returns 64k because the memory allocation tracker only knows about the 64k. However, when this is already 64k, there is no need to resize the memory to 64k because it is already 64k or 128k...
The second commit resets the romType of the builtin ROMv5a to 0x40 instead of 0xf8. It seems that this is not a ROMv5a but an early devrom with a couple bug fixes. I left the bug fixes and just changed romType and two comparison tests (one in Apple-1, another in CardBoot). Note that you might have had a reason to do this. Feel free to kill this one.