Search the Community
Showing results for tags 'sams'.
Found 4 results
After trying out a new editor that I have been working on Vorticon suggested that I open a topic for the benefit of the greater group. Somebody may find it useful. The ability to copy files and lines and paste them into a new composite file is pretty handy or cut a file up into separate files. It uses key commands for editing and the command line for saving and getting files. DIR and CAT commands are available within the editor because I have a good memory but it's short. ED99-40 column Beta Release 1.1 40 column multi-file editor Changes: V1.1 built on "new and improved" Camel99 Kernel (thanks Tursi) Fixed problem: SAMS card was not initialized on startup. Worked on Classic99 failed on real hardware. Clipboard uses the upper end of SAMS memory so 511 lines can be copied. Fixed the ED99CONFIG file to use DSK1. to find the font to load. Four font files have been included with the release. Feature Additions FCNT 4 (break) will stop file loading. The partial file will be in SAMS memory. Use PURGE if you don't want to keep it FCNT 4 (break) will stop file save. The partial file will be written to disk. CTRL A will copy entire file to clipboard. CTRL P will paste entire file to the END of the current file. (Insert can be too slow at this time) Number of lines in clipboard is displayed on lower right side of editing window PRINT command prints the active file to any DSR enabled device. Examples: PRINT PIO PRINT RS232.BA=9600 PRINT CLIP (Classic99 only) Limitations File size is still limited to 511 lines Inserting to the top of a large file is still slow due to the simple internal data structure. Future 80 Column version and SAMS memory are not playing together nicely. Not sure why yet. Single level undo/redo Document user level editor commands for DSK1.ED99CONFIG Bugs from Vorticon's Beta test Pressing <ENTER> after the first line inputted moves the line down and the cursor is positioned above it. It is not possible to enter text below that first line. Is this a feature or a bug? Pasting with Ctrl-P pastes the contents of the clipboard after the End of File marker and adds yet another End of File marker. I would have thought that the pasted text will appear just above the EOF marker... This should be fixed now. (off by one error...) Below are the contents of the readme file. By the magic of Classic99, in the ED99 command line I typed PRINT CLIP and pasted this into the browser. Pretty cool. README for ED99 Editor Brian Fox July 2, 2020 ED99-40 is a text editor for the TI-99 COMPUTER It requires the Editor/Assembler cartridge. Starting ED99-40 - To start the program select menu option 5 - Place the ED99-40 files on a disk and place it or mount it as DSK1. - At the RUN PROGRAM FILE prompt type: DSK1.ED99-40 ============================= There are 10 files in this package: README.TXT (this file) ED99-40, ED99-41, ED99-42 The 3 binary files of the editor. ED99CONFIG A DV80 text file with editor commands to setup the editor the way you want it . *Type EDIT DSK1.ED99CONFIG to alter the file. ED99DOC A simple list of the key commands and text commands that control the editor FONT FILES - FONT0230 Default font loaded at start up - FONTEDT1 Same font use by EDIT40 V3 of the TI E/A editor - TI99FONT The standard font used by TI99 BASIC - FONT004 Alternative font with correct descending lower case letter Contact info: I am commonly available on Atariage.com in TI-99 development forum as theBF. ED9940.DSK.zip
UPDATE: 2020/07/02 07:05 UTC This thread shall be used for documenting research on Myarc Extended Basic II. Purpose Create a version that can be used with SAMS and a RAM cartridge (superspace) Target modern storage devices like CF7+/Nanopeb, TIPI or HRD4000B. No longer rely on the unobtainable MEMEXP-1 128K/512K memory expansion. Recreate assembly source code Research originated on discussions found here: This post will be updated on a regular basis as more accurate information is collected. BASIC variants (1) Armadillo Basic on the TI-99/8 The new "standard" Basic interpreter on the TI-99/8. Only appeared on some early TI-99/8 prototypes. The plan with Armadillo Basic was that it forms the "basis" for what is later known as Extended Basic II Share as much code as possible between the two basics, Modular setup: One idea was to keep core part of the basic interpreter in ram (statement dispatch table for functions), where it can be modified by the extended basic interpreter startup sequence Interface document exists that outlines the dispatch table Possibility to load & save Extended Basic programs from DV80 files 60K of free space for program code (170K) if 128K memory expansion installed Certain parts rewritten in assembly language for optimized speed (e.g. screen handler) Unknown if source code exists Unknown if ROM dumps exist (2) Extended Basic II on the TI-99/8 Extension of the Armadillo Basic found on early prototype All later TI-99/8 preproduction units had Extended Basic II built-in, instead of Armadillo Basic Unknown if source code exists Confirmed ROM dumps, emulation in MESS/MAME possible. (3) Myarc Extended Basic II on the TI-99/4a is basically (2), the Extended Basic found in the TI-99/8: Written in Assembly language Versions known to exist: v2.10, v.2.11, v.2.12 Memory map changed to match TI-99/4a (+Myarc MEMEXP1) instead of TI-99/8 FREESPACE removed, memory allocation changes, comma instead of dash in list command, ... Removed loading/saving extended basic programs from/to DV80 (at least in >v2.11) Unclear if source code exists (4) Myarc Extended Basic II for the Geneve Written in Assembly language Variant of (3)? It’s the initial version of Extended Basic shipped with the Geneve (5) Myarc Advanced Basic (ABASIC) Written in Assembly language Versions known to exist: 4.04 (last version by Jim Uzzel) 4.05 (~2013 by InsaneMultitasker, fixed assembly language parameter passing bug) Based on (2)? Source code exists, heavily commented Backport to TI-99/4a probably difficult due to the XOP's used (6) Basic on the Tomy Tutor Variant of 99/8 Armadillo Basic Basic tokens compatible with TI Extended Basic GPL involved, but no GROMS (7) TI-Basic on the 99/2 TI internal name “Ground Squirrel BASIC” Developed outside of TI at a contracted university Completely written in assembly language, no GPL involved. Very fast Source code not related to Armadillo Basic (1) on the 99/8 Documents Armadillo Basic on the 99/8 There are actually quite a few documents floating around, created during a 2 years’ period (1982-1984): ?/??/?? - 99/8 Basic / EXT. Basic interface specification ?/??/?? - 99/8 Armadillo Basic specification ?/??/?? - VDP RAM usage in Armadillo Basic 5/26/82 - 99/8 The mapper and us 9/30/82 - Armadillo Basic internal design 3/23/83 - 99/8 Mapper specifications 2/07/84 - 99/8 Bugs found after 7/34/84 release (TI998.BASLCP.BUG) 2/07/84 - Usable XML’s, XOPs (TI998.BASLCP.DOC.ASSM) 2/07/84 - Symbol table entry bits in use for the Armadillo (TI998.BASLCP.DOC.LINKBITS) 2/07/84 - Interpreter variables V0.002 (9/10/82) (TI998.DOC.VARS) 2/07/84 - PAD memory usage (TI998.DOC.PAD) Myarc Extended Basic II on the TI—99/4a Requirements Myarc MEMEXP-1 128K (or 512K) memory expansion card required Has 8K DSR in >4000-5fff (program loader, RAMDISK setup code, spooler?) Myarc Extended Basic II cartridge required It's confirmed that a 8K RAM cartridge (superspace) in >6000-7fff works fine. Disk with Myarc Extended Basic II interpreter Workings When selecting the '128K BYTE O.S.' cartridge option, the file loader in the MEMEXP-1 DSR space is triggered The whole process of loading the Extended Basic II interpreter into the appropriate MEMEXP-1 memory pages seems to be handled from inside DSR space. In the cartridge space the memory management routines required by the interpreter are stored (required for banking the appropriate MEMEXP-1 pages) The code at >6030-7fff seems to be put there are the very end when XBII is loaded into memory. Could be this is part of XBII initialisation itself? When quitting XBII by using "BYE" command the cartridge space >6030-7fff is cleared with >00, only the cartridge header is present. While XBII runs it writes to the cartridge space >6000-61ff (clarify exact memory addresses). This is probably to compensate the fact that the 99/4a only has 256 scratchpad where 99/8 has 1K. Cartridge space: 6000-602F Cartridge header '128K BYTE O.S.' 6030-612F Written to by XBII while running 6130-7fff Appears to be static code, haven't seen any writes here so far Unclarified behaviour The DSR space >4000 is briefly activated every 5-10 seconds while XBII is idling in command mode. This does not happen when a program is running (e.g. 10 GOTO 10). Seems to be a background task: Perhaps the access to the DSR rom space is related to the print buffering code checking to see if anything in the buffer on interrupts?
I'd like to do a little experiment using the TiVi edtor I'm currently working on. What is the largest DIS/VAR 80 file you were able to load and browse on the TI-99/4a? I'm trying to get my hands on some big DIS/VAR 80 files and with "big" I mean that it should be at least > 100 kilobytes. If you have such file and don't mind posting it (as a disk image). I'll try to load it on the TI-99/4a. For further details on the editor see here:
So I'm trying to create a realistic statistics based baseball game and, due to the TI's limitations and my not wanting to learn assembly, I am trying to figure a way to utilize SAMS memory to store, for example, tables of data that I can look up and retrieve into variables, mostly strings. I'd also like to be able to use the extra memory to store in-game statistics like at-bats, RBIs, strikeouts, walks, etc. for each player in the game, as well as team statistics. I'm thinking I'm likely setting my sights too high for this machine, but would love to know if and how this might be possible, especially with 1 MB of memory just sitting there waiting to be used. For example, I'd like to have many detailed plays such as "fly out to center," "6-4-3 double play," "out at first, other runners safe," and plenty others which I can look up in some sort of matrix in memory. I'm finding I'm really having to leave out more than I'd like to include using what's available on a 32K system. Having a way and understanding how to access SAMS memory, maybe even if used as a RAM disk, would be cool. Otherwise, I'll make do with what is possible to utilize, and try my best with what there is to work with. I guess I'm just not understanding what use the extra memory is if it's not possible to utilize it easily. I've seen Rich's In the Dark but I don't think that's anywhere near what I'm trying to do. That game appears to be using the memory to store map sections and then move the data into program (or is it VDP?) memory. Also, I see subprograms in RXB that start with AMS, but I can't seem to make sense of them, likely because I'm clueless when it comes to TI machine language. If someone can point me to a tutorial or even just documentation on ways of using the SAMS memory in programs, especially along the lines of what I'm attempting to use it for (store and retrieve data) it would be appreciated.