OUT_FILE output ROM file (default: replaces FILE extension with. d dump MIO0 blocks to files in 'mio0files' directory a ALIGNMENT byte boundary to align MIO0 blocks (default: 1) p PADDING padding to insert between MIO0 blocks in KB (default: 32) s SIZE size of the extended ROM in MB (default: 64) Just drag-and-drop SM64 ROM on the executable for default settings or run from the command prompt specifying these options: dumps MIO0 blocks to 'mio0files' directory.updates assembly reference to first MIO0 block.creates MIO0 headers for all 0x1A commands.decompresses all MIO0 blocks from ROM to extended area. inserts 32 KB padding between MIO0 blocks.fills extended area with fills with 0x01.accepts Z64 (BE) or V64 (byte-swapped) ROMs as input.works with both US and Japanese ROMs (plays in emulators, but TT and level importer won't work with (J) ROMs).built-in ROM header CRC computation (non-GPL!).option to fill original MIO0 blocks with 0x01.configurable MIO0 block alignment (default 1 byte).configurable padding between MIO0 blocks (default 32K).configurable extended ROM size (default 64 MB).I have tested the resulting extended ROMs with SM64 Importer 1.9.2S and Toads Tool 64 v0.6.2S. I released it under the MIT license so it can be included in any of your projects.īy default, it creates a 64MB extended ROM that is bit compatible with the extended ROM that M64ROMExtender1.3B generates and further extended to 64MB (before the patches are applied by SM64 Importer 1.9.2S). It is written in C and compiles for Windows and Linux 32/64 bit (probably OSX as well, but untested). QueueRAM Wrote: This is a replacement for the M64ROMExtender and adds a few new features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |