I have an Applesoft program that PEEKs/POKEs at 125 and 126 for the "next DATA line".
When I compile the software, it seems that the location of that counter changes and the program continues to PEEK/POKE at the 125/126 location, only the results are useless because it now stores that counter in another location.
I am using the Einstein compiler which seems to be the only one working for me/most ideal for my situation)
I'm wondering if someone out there could help me find the new location. I assume because it's tied into its ability to READ DATA lines, the compiler should pick a static place to keep the counter regardless of the software its compiling.
The PEEK and POKE is necessary as I am using DATA lines in a Random Access fashion and require READ/WRITE access to that pointer variable to load SPRITES. I was previously loading the DATA lines into an array, but this is not practical as it eats up all the RAM for both the program DATA listing as well as the loaded array - doubling the RAM needs for simple sprite DATA...
If anyone could help me with finding this new variable location - or could provide me a debugger for Apple II binaries that I could watch for it (it should be obvious to find as it changes with every READ statement) I would be incredibly thankful.
I'm challenging myself to get this game done in a couple of weeks, and I really need the help on this one!
Rather than READ from DATA statements, READ the sprite data into the variables from a file.
I should state that I'm not allowing for any loads from tape/disk for this project. It is going to be a cassette release and must be complete after initial load. I'm being stubborn, but this is my key requirement.