Since this file is padded with 0x200 of nonsense, but the file ends at the correct spot, that means the theoretical "actual save portion" in the file is smaller than normal. It looks like the bytes from 0x200 onwards might contain data for a save file, but trimming this file is useless, as it was cut off at the address where the save file would have ended. How did you obtain such a save file again? Besides, SheepShaver only supports up to NewWorld v1.6 ROMs.
SHEEPSHAVER UNSUPPORTED ROM TYPE CODE
MacOS 9.1 doesn't run because it seems to depend a lot about the new NanoKernel code loaded during boot. Scratch that, I was confused - the SE30 ROM still doesn't work (even with an older build of Basilisk II - still get the 'Unsupported ROM' message). Gwenole Beauchesne - MacOS 9.1 doesnt run because it seems to depend a lot about the new NanoKernel code loaded during boot. Having the lines of 0xFF and a visible "USBC" is not normal, and not what a SWSH save file looks like. Sheepshaver is known to work with MacOS 9.0.4, by the way, which might be a reasonable compromise for you. Sheepshaver is known to work with MacOS 9.0.4, by the way, which might be a reasonable compromise for you. I don't think save files should be like this. Hopefully someone can help me to fix this. Select the 'Built in' output format to enable sound. In MacOS 9 you will find the Sound control panel with the installed control panels in the Apple menu. The reason for using the 4MB OldWorld file in favor of the 1MB NewWorld may be: Compatibility, the Old World ROM seems to be slightly more reliable. Boot images made with the OldWorld ROM will also boot with NewWorld ROM, but not vice versa.
SHEEPSHAVER UNSUPPORTED ROM TYPE WINDOWS
The ROM though is actually part of the classic/blue box (which the binaries for classic are still labeled blue box in a lot of places). SheepShaver does run OS 9.0.4 with the OldWorld ROM or the NewWorld ROM on GNU/Linux, Windows or OSX hosts. Name the volume and choose 'Mac OS Extended' for the format. All other SheepShaver-type emulators that run on Intel hardware are far more complex and less efficient because they have to actually imitate the OS9 functions in a 'foreign' environment. I read many topics here but i can't find the answer. While booting from the CD, the system will encounter the new volume and will ask to initialize it. This could be caused by loading a different generation Pokemon file on an unsupported generation or your file is corrupt. I use the latest version of PKHex (20200314)īut he gives the same error over and over:Īttempted to load an unsupported file type/size.