How to make a cartridge?

[senior_falcon]

Let's say I wanted to make a custom cartridge, say XB with a different font. With Classic99 I know how to modify the GPL code to give me the font I want. Once the GPL code is modified, how do I create a cartridge from what is in memory?

[HOME AUTOMATION]

Do you mean, you have modified XB GRAM, by running a program from within Classic99 and want to export to a G.BIN file, or do you want to create a physical cartridge?

[senior_falcon]

Good question!
Let's say I've enabled GRAM and made modifications to it. I've tested it and like the changes. Now I want to save this so the next time I use XB I can use the modified one. I'd like to save everything, both GROMs and ROMs. 

When I modified Video Chess someone (I don't remember who) created two files: CHESS_C.BIN and CHESS_G.BIN and these can be loaded and run as a cartridge.

I know this can be done, but don't know how. 

[HOME AUTOMATION]

I remember that thread, somewhat.

I think their method used tools I am not familiar with!

I have had trouble reversing this process myself.

The emulators don't seem to have a simple way to accomplish this.

The SAVE feature in FG99 can be a good way.

Usually I'm working with the MINIMEMORY image... From Win994a, I save >7000 thru >7fff to CS1, than open the .TITape file with a hexeditor... and cut and paste back into an existing .BIN file.

[HOME AUTOMATION]

I looked into a newer Classic99 user manual pdf, it looks like Tursi built some functionality into the DEBUGGER.

see...

7.5 Save Memory as Program.

[+Torrax]

 

How about this:

 

Enable GRAM access.

Make your changes to XB.

Disable GRAM access.

And use an XB Opt5 loader to run CSAVE.

You can then use a Hex editor to remove any headers and concentate the grom files to XB_G.BIN.

And just remove the headers of the rom files to XB_C.BIN and XB_D.bin.

 

 

Edited September 27, 2019 by Torrax

[Tursi]

Classic99 doesn't have a built-in option to save the GROM back out... usually I build cartridges on disk rather than use the tool. (By hex editting or writing little tools to patch the binary). It can only save the CPU data.

 

The disk files themselves have no headers at all, just the raw binary bytes.

 

You could also write a TI program to save the data to disk. Write it as a PROGRAM image file or a DF128 file, and you can just strip off the first 128 bytes and have a working file.

 

[+Torrax]

Here's a console grom modification with CSAVE embedded into it (8K groms with the upper 2K areas used).

You can use it also with a EA grom thats been relocated to g>E000-g>F7FF and a GPL assembler to roll your own modules.

Remember to disable GRAM access from Classic99 when using CSAVE to avoid corruption when saving your work.

 

Classic 99 user cart entry:

 

[usercart99]
; *** CSAVE/BAS/XB
name="CSAVE/BAS/XB"
rom0=G|0000|6000|MODS\BASCSAVG.bin
rom1=C|6000|2000|MODS\XB110C.bin
rom2=X|6000|2000|MODS\XB110D.bin
rom3=G|6000|A000|MODS\XB110G.bin

 

Hope this helps.

MODS.zip