And the problem with your solution is that it requires a special cartridge. Looks like we both strike out when it comes to running on an unexpanded TI, although I would guess that the XB+32K combo is far more common than the RXB cartridge.
Earlier you posted CALL XB(files#open,"DSK5.FILENAME") that will do a CALL FILES(file#open) :: NEW :: RUN "DSK5.FILENAME"
Why is there a "NEW" in there? In XB you do not need a NEW for CALL FILES(N) and RUN "DSK5.FILENAME"
Unlike CALL FILES it does not reset al pointers for VDP, thus the need for a NEW.
Go to XB and type in:
now type in:
See the problem? Now type in:
Now you see why?
When you type in CALL FILES(1) and then SIZE it does not report the correct size until you then type in NEW
This is odd as how can program space remain the same size when that space has increased?
The NEW does something CALL FILES does not do.....UPDATE ALL VDP POINTERS.
Also something is assbackwards here, I increased the size of program space at top of memory,
but the bottom of memory VDP STACK size increased???? WTF????
This gets even more strange, go OLD DSK1.LOAD and turn on Classic99 debugger and first address the
LOAD program uses is >3BE8 which is the correct address.
By the way in RXB 2018 type in:
You get this:
13144 Bytes of Stack Free
24488 Bytes of Program Space Free
8192 Bytes of Assembly Space Free
240 Banks of 4K Pages
* MEMORY USED *
>3CEF VDP Free
>0958 VDP Stack
>FFE7 Program Free
>A040 Program End
>2000 RAM Free
>4000 RAM End
Edited by RXB, Fri Jun 22, 2018 11:10 AM.