Search the Community
Showing results for tags 'ed-assem'.
Found 3 results
Are there any gotchas involved in using CALL FILES (>16) subprogram? I think an obvious one would having no files open at the time, lest the table or the files get corrupted. In 1985 I wrote a text editor in Extended BASiC and used CALL FILES (1) to free some memory. I seem to recall seeing something somewhere, back then, that CALL FILES had to be the very first statement (at least in X-BASIC), but cannot find the reference. How about in assembly? I search the forum but did not find anything. K-R.
While fiddling with my K-Loader program, I thought it might be nifty to be able to reset the symbol table at the top of low RAM. For example, if I load the wrong object file by mistake, I thought it might be nice to reset the RAM free-space pointers and clear the symbol table to start over without having to reboot and reload the loader. I assume that everything between >3F38 and >3FF8 is assigned by the system when the user selects EA3 or EA5 on the Editor/Assembler menu. I was thinking that setting the eight bytes, starting at >3F30, to zeroes and then set LSTLOW to >3F38 would reset the table to the state that existed upon program start-up. When I do so, and then try to load a file, I get an "Illegal operation" (Error 3, I think). Anyone tried doing this? And succeeded? K-R.
While trying to load object files with EA3, I found that an object file larger than 5254 (>1486) bytes will fail with "Error 3." An file of 5254 bytes will load normally. After disassembling the TI LOADER code, I did not find any indication of a file-size limitation. I found this using TI994w, most recent version. Have not tried it in a real TI, yet. K-R.