RXB

You could use FinalGROM put the MG Explorer into a another GROM base or ROM and load it like you asked with CALL INIT :: CALL LOAD("EXPLORER") I would copy memory of loaded system into a single file then put that file into the other GROM base of mulitiple ROM banks in FinalGROM. Set up a GPL DSR called "EXPLORER" so when called would move into 32K and return to XB and bang all set. Or do a FAKE DSK like PDISK that was put out for GRAMKRACKER that CALL INIT :: CALL LOAD("EXPLORER") would load it thinking it was a disk file.

RXB was first to support AMS when it was introduced that later became SAMS as I was given a AMS 64K card when it was first shown I first upgraded it to 128K. To make it work loaded a 12 byte Assembly code from GPL into Scratch Pad RAM to run the routines. By changing only 4 bytes I could Read/Write/Map/Turn on or off the card and load values. Bonus was as it was in Scratch Pad and GPL no worries about crashing system by over writing the control program. This is the main issue using the SAMS is where to put the controls that will not be overwritten or changed.

I am more of a Realist. Old story: A Pessimist is dropped into the desert will die by saying what is the use and gives up. A Optimist is dropped into the desert will die by looking for a McDonalds. A Realist is dropped into the desert and finds something to kill and eat and keeps on till he gets out. Moral: Pessimist gives in to easy to apathy. Optimist has unrealist expectations of success. Realist sees the world as it exists and how to deal with it. You can be what you choose but history is not good for Corporations treatment of non stock holders.

History shows that when Corporations take over anything where the people had control it never ends well or fairly treated. Personally, I will never ever trust any corporation for what it says as they are always proven liars. When money is your only goal, service dies fast. My prediction is they cannot find any profit in owning AtariAge so Atari will just kill it on purpose.

Honestly I will never trust anything a Corporation ever says. They will lie to you without a care in the world. Freightliner I worked for was doing business with Haliburton and I told everyone they would rip us off and screw Freightliner over. I was told to shup up and removed from project. 2 years later it cost Freightliner over 3 million in lost funds and 1.6 million just a total rip off of funds. And Chenny bragged 1 year later about screwing us over like it was some kind of a ethical thing. Again never trust anything any corporation says it will do EVER! They are all liars and unethical. Unless those managers are punished for this stuff, they will never be ethical.

Well 32 columns times 24 rows is 768 times 8x8 character is 6144 individual pixels in that mode.

Actually this is due to the 9901 VDP chip. It has modes of several types and 32x24 is the most used one for menus. Every single Cart from Texas Instruments used this mode when you get the title screen or a menu. Thus this VDP chip mode is always the one you see the most often, and the one used by Basic and XB.

Yea sorry it would be 0 to 767 you are correct.

RXB has CALL HPUT(row,col,string or numeric variable) or CALL VPUT(row,col,string or numeric variable) Or if you want to stick with the Assembly Numbering system use CALL MOVES("$V",LEN(string-variable),string-variable,address) $=type of string V=VDP address LEN is the length of the string string-variable is like A$ or X$ address is the vdp address like you see in Assembly Also you could use CALL HGET(row,col,length,string-variable) or CALL VGET(row,col,length,string-variable) to get strings off of screen into a string-variable

Well normally Assembly uses screen location from 0 to 768 if you are talking Characters of 8x8 normal characters. So most of the time the number divided by 32 and the left over is the column of the last row. Example: 736/32=ROW 23 and COLUMN 1 Example: 127/32=ROW 3 and COLUMN 31

When I assembled original XB 110 ROMs and GPL source code was using a few macro routines that did not exist for any 9900 Assembler or GPL Assembler. It was written for the 990 computer to assemble for use in making the GPL and Assembly for the 9900. So DO WHILE and ENDIF routines I had to figure out how to make them work in the Ryte Data GPL assembler and TI Editor Assembler. The source code for XB 110 that I released had the conversions without the Macros. Looking at your source code post of Cortex Basic most of it can be used in a 9900, but some of it does present a problem.

LOL first off I wrote Editor Assembly TI Basic support into TI Basic GRAM 4K space. There is plenty of space left for the CALL FILES routine to. Also once loaded it is way less complicated than what you are doing with 10 times more features. This is all GPL so why you are confused that XB and TI Basic are not all written in GPL is kind of funny, Is it clear?

Do you have the source code for Cortex Basic for the 9900? As I am working on XB ROMs being modified this might be helpful?

My version of CALL FILES(0) is written in GPL so executes before any ROM version in the Disk Controller. I also added a updated section so you can actually use CALL FILES(15) and it works too. Again written in GPL so the DSR one is never used. You could put my GPL version in TI Basic GRAM on Classic99 to test it. *********************************************************** * CALL FILES(number) 0 to 15 * *********************************************************** SFILES DATA SSIZE STRI 'FILES' * FILES DATA $+2 CALL COMB * ( CALL CLSALL * Close all open files CALL RXBFIL * Set files BR RXBNEW * Go do a NEW RXBFIL CALL SUBLP3 * Get Files value DCZ @FAC * Zero? BS RXBF0 * Yes, RXB CALL FILES(0) DCHE 16,@FAC * 16 or more to high BS ERRBV * Yes, BAD VALUE error CEQ RPARZ,@CHAT * )? BR ERRSYN * SYNTAX ERROR XML PGMCHR * Skip ) DCLR @FAC2 * Clear ST @FAC1,@FAC2 * Load file value DST >0116,V@VROAZ * Set files buffer space DCHE 256,@PAD * BR DSRDSS * ADD >10,@VROAZ+1 * DSRDSS DST VROAZ,@FAC12 * CALL LINK * BYTE >0A * ST @ERCODE,@PAD2 * SRL 4,@FAC6 * CZ @FAC6 * BR ERRFE * CEQ >20,@PAD2 * BS ERRFE * RTN * RXBF0 CEQ RPARZ,@CHAT * )? BR ERRSYN * SYNTAX ERROR XML PGMCHR * Skip ) DST >3CEF,@>8370 * Set FILE(0) VDP Highest address RTN * Return You can find the entire thing is RXB 2023 as I include the source code for GPL and Assembly.

RXB 2023 has a working CALL FILES(0) I do not know of any other XB that has CALL FILES(0)