Jump to content
Posted Mon Apr 5, 2010 6:51 AM
Posted Mon Apr 5, 2010 12:03 PM
[Usercart0] name=Tutankham rom0=3|0000|8000|D:\Projekte\tutankham\tms9900\TUT.bin
[roms] cartgroup 0 Apps 1 Games 2 User cartidx -1 No cartridge selected ?? index of the cartridge from the appropriate menu [UserCart0] (and so on up to 99) name Name of the cartridge. If blank or missing, the cartridge is ignored. message Compatibility notes, if desired rom0 (0-3 for a total of 4 ROMs per cartridge) Contains notes for loading the cartridge. This is a pipe-limited row of data, formatted like so: T|AAAA|LLLL|filename T is the single character ROM type. Most carts only use G, C and X types. C CPU ROM D DSR ROM E DSR ROM bank 2 (used for p-code) G GROM* P P-Code GROM R CPU RAM - this is loaded like CPU ROM but is not flagged as read-only! S Speech ROM V VDP RAM X XB Bank 2 ROM (called 'D' in some systems, but I used D already) A AMS memory, RLE encoded (not working correctly yet) K Paste string for the keyboard after boot (to autostart tasks, not a filename) 3 Packed banks with a '379 style decoder. Similar to XB style but more banks and all in one file. Note that this assumes a load at >6000, so you are specifying the offset in the banking space, with bank 0 at >0000, bank 1 at >2000, etc. SuperSpace carts (CRU >400) can be loaded this way for now, too, but will likely split them up later. Max size is 64k. (* GROM is special - to support multiple GROM bases, you can now load GROMs into different memory bases - up to 16 of them! By default, GROMs load into memory base 0. Append a hex number 1-F after the G to specify a different base (like: G1). The console will detect these and add them to the start menu! Note that not all GROMs will work at alternate bases. Also note, in the real console, the console GROMs appear at all bases, so you can't load alternate bases at less than >6000. Classic99 does not support using this with cartridges that include CPU ROM. Each GROM base is offset 4 from the previous, ie: GROM Read is >9800, >9804, >9808, etc.) AAAA - load address in hexadecimal LLLL - length of data in hexadecimal (will override actual size of file) filename - filename on disk to load This system supports both raw ROM files, and ROM files with a 6 byte GRAM Kracker style header. The header is detected by checking if the first byte is >00 or >FF, and if the 5th and 6th bytes represent the load address. The header will be ignored if detected - the data in this INI file is considered authoritative.
Posted Mon Apr 5, 2010 4:19 PM
Edited by Tursi, Mon Apr 5, 2010 4:20 PM.
Posted Mon Apr 5, 2010 6:03 PM
Edited by unhuman, Mon Apr 5, 2010 6:14 PM.
Posted Mon Apr 5, 2010 6:19 PM
0 members, 0 guests, 0 anonymous users