Author Topic: Making Axe games that uses up to 1.5 MB executable code theoretically possible (Read 1308 times)

xlibman · « **Reply #15 on:** February 21, 2017, 06:44:03 pm »

Does editing it require some ASM knowledge or other tech-savy stuff?

Sorunome · « **Reply #16 on:** February 21, 2017, 06:46:05 pm »

it should require modifying the app header, the branch table and re-signing with rabbitsign. So i guess knowing how to use a hex editor and what to look for would help.

This is OFC just theoretical, i haven't done so myself yet

xlibman · « **Reply #17 on:** February 21, 2017, 08:09:28 pm »

Ah ok. I guess the easiest solution, assuming you have an easy time dealing with external appvars, would be the hybrid TI-BASIC approach. There's also a way to turn programs into appvars with Tokens IIRC as well as Doors CS 7, to avoid having to clutter the PRGM menu, but both ways either requires Celtic III or Doors CS 7 to be installed on your calculator.

At least hybrid TI-BASIC is good for one thing

E37 · « **Reply #18 on:** February 22, 2017, 02:38:41 am »

@Sorunome if you could try that and give me a little tutorial on how to do it, I would be really grateful.
Even a pointer on how the header is structured and how to find what page it is on would be really nice.
Also, do the pages have to be in sequential order in memory?

WalrusIRC

Author Topic: Making Axe games that uses up to 1.5 MB executable code theoretically possible (Read 1308 times)

xlibman

Re: Making Axe games that uses up to 1.5 MB executable code theoretically possible

Sorunome

Re: Making Axe games that uses up to 1.5 MB executable code theoretically possible

xlibman

Re: Making Axe games that uses up to 1.5 MB executable code theoretically possible

E37

Re: Making Axe games that uses up to 1.5 MB executable code theoretically possible