Am I correct in assuming this will all be transparent to the program and that ANY pre-existing TI Extended BASIC program will work in it?
Yea unless you have something goofy like VPEEK for a string or symbol or VDP Stack, those will all be in RAM on the SAMS.
There is no logical reason to use VDP for Strings and symbols or stack when we can use the SAMS RAM which is much faster and more of it.
Also I will remove all the VDP pointers and temporary buffers for XB, except for of course Device Buffers at top of VDP RAM.
So yea all XB and BASIC programs will work in SAMS RXB just fine, well except they will run faster.
VDP is much slower than RAM by anyones standards.
Now any Assembly Language CALL LINK program will be a little faster to as the normal LINK used VDP to store variables and strings.
Thus if you have a Assembly Language program that needs the old access to VDP you can not use SAMS RXB as the locations have changed from VDP to RAM.
I can think of a few Lower 8K Assembly programs that did this like XBDETECTIVE for example that read string variables from VDP which will not work as SAMS RXB have them in SAMS RAM.
I do not think people understand how many times per subprogram Extended Basic used VDP and how it really slows down XB.
Edited by RXB, Sat Apr 15, 2017 10:14 AM.