This is a fix that works for now. It fixes a crash that can happen when using e.g., 8MB capacity 512 cluster size. The emulator would try to write to the same memory-mapped register as the C256 path (since they share much of the same code), which doesn't exist on F256.
In the future a better fix will be to really understand the communication between kernel and FAT, and why kernel is requesting what seems like out-of-bounds writes based on what's reported in the boot sector.
This is a fix that works for now. It fixes a crash that can happen when using e.g., 8MB capacity 512 cluster size. The emulator would try to write to the same memory-mapped register as the C256 path (since they share much of the same code), which doesn't exist on F256.
In the future a better fix will be to really understand the communication between kernel and FAT, and why kernel is requesting what seems like out-of-bounds writes based on what's reported in the boot sector.