0 Members and 2 Guests are viewing this topic.
Quote from: Deep Thought on March 22, 2011, 10:45:26 amIf you're making it a program, the entire program should be under 8811 bytes. This is because Axe puts its own routines after the data, so things still get run at the very end. There are ways to get around this and put the data after that, however.I haven't tried this myself, but try disassembling the executable once as it is, then using TI-Coder or a similar utility to move all of the data to the end of the source, then dissassemble the final source. I would like to see if that puts all of the data at the end. If you don't want to scroll down to the bottom of the source to edit your data, include it in an Axe Library and put the reference at the bottom.
If you're making it a program, the entire program should be under 8811 bytes. This is because Axe puts its own routines after the data, so things still get run at the very end. There are ways to get around this and put the data after that, however.
Well, I'm aiming to not make this an app.Wasn't there a way to stick all the data at the beginning of a program to not make it count in the 8801 byte limit?
Estimated release date has been set to less than five weeks from now.Progress coming along good.Maybe somebody can help me figure out the data after I finish the entire map.
you can try a method using Pt-Mask(