#Ti 99 4a bios software

If the ROM file is 8k, it's a 'C', always. (Whether it's ROM or GROM is usually known by SOMEONE. If you have just received a file and want to rename it, you can narrow it down by size. So how do you select which one to use? If you're the programmer, you probably have some idea what you have created.

#Ti 99 4a bios software

Internally it's a 'type 9', I don't expect too many new pieces of software to use this. V9T9 used this for the second file of 16k cartridges such as Extended BASIC (which is really 12k, but they duplicated the common 4k block in the two banks). This supports up to 32MB of ROM.įor legacy reasons, there's another autodetected name, and that is 'D.BIN'. The '378' was one of the chips that worked this way, so I selected '8.BIN' as the filename ending for this type. It is called non-inverted because when you select the 'first' page by bank, you get the first 8k of the EPROM. ROM (paged non-inverted) - This is the newer style, including the FlashROM99. Because of the chip in use, I selected '9.BIN' as the filename ending for this type. It is called 'inverted' because when you select the 'first' page by bank, you get the last 8k of the EPROM. ROM (paged inverted) - This was for cartridges on the original release of the '379' switching PCB.

Ending your filename with 'C.BIN' (for 'CPU' memory) allows autodetection of this. ROM (not-paged) - This is the standard 8K of ROM memory. The maximum size of a GROM cartridge auto-loaded into the cartridge port is 40k, GROM paging must be specified in the INI. Ending your filename with 'G.BIN' allows autodetection of this. So for auto-detection, you first need to know 'what kind of cartridge ROM is it?' There are four types today: In particular, it assumes that you are loading at the base address of the cartridge port (>6000), so you can't split, say, a bank-switched program over multiple files. The 10 character limit is a TI Disk Controller limit, and ROM files aren't loaded by the TI Disk Controller, they are loaded by the emulator itself.Īuto-detection is more restrictive than the Classic99.ini. The other thing to note is there is no 10 character limit on a ROM filename (*when used directly by emulation). There's no naming restrictions there because you tell the emulator everything. You can make any filename work just fine in Classic99 by defining the cartridge in Classic99.ini.

The scheme was developed for the V9T9 emulator in the 90s and I extended the concept for newer types because I like loading cartridges lazily. I wanted to note that this is not 'so it works with Classic99', it is 'so Classic99 can auto-detect the type'.