MikeV

It was meant as a simple question. I was under the impression that's part of what these Atari pages are about? I would also trade up without a second thought as well. From past experience the hardware will be rock solid.

The WHT original did not have DSK1 emulation (which is very handy). Will your revision have that capability?

The SAMS is unfortunately one of the most under utilized pieces of hardware in the 99/4a world. It has such potential!

This is the first of 6 planned RXB/ SAMS text adventures. During the covid months I adapted 20 or so adventures from other basics for use on the TI. These literal adaptations repeatedly left a lot to be desired, as they tended to highlight the 99/4a's weaknesses. Long story short, these are the same programs but better suited to the TI with SAMS support. The immediate goal is to reduce the time spent waiting for the TI to respond, or scroll... In addition, the use of SAMS permitted some added features. However, this is still an XB environment. Disk #1; Program: The Ancient Chateau by Tim Hartnell (1984), mixed IF and D&D elements GWBasic original: 24,653 bytes, about 26k to run The TI Version requires a DSSD drive, or something better, RXB and SAMS. Startup time: reasonable Performance: good There are two small pdf manuals included. The first can be viewed as a typical pdf. The second is for anyone who may wish to print it out in booklet form: 1) landscape format 2) print one page at a time (use 'current view') 3) place the first page back in you paper feed, print down with the same orientation as it came out 4) print page 2, etc. Your printer may be different and/ or smart enough to figure it out! There will be 3 double-sided pages. Hopefully there are no bugs... Ancient Chateau.zip

That will be great!

Hey Rich - saw your RXB SAMS video and the concept is great! As part of RXB SAMS would it be possible to include variable length string support with CALL MOVES to populate arrays, etc? It would provide a significant conservation of conventional memory and be very fast. As I am uncertain of the correct terminology I attach a hex-view below: This file was made with CALL MOVES AND PSAVE. As the strings are variable length I used a "FIXED" length of 16 bytes as the baseline maximum. As can be seen when the string length is less than the defined length the last byte value is the string length (same as on disk files when the VARIABLE length attribute is declared). These are indicated in squares. This does not occur with fixed length strings that are fully occupied, e.g. a CALL MOVES("$R",64,...) to move a 64 digit CHAR CODE. I do not know if it is RXB that provides the string length byte or the TI operating system? To use the strings I had to convert them as follows: 4990 FOR J=1 TO 20 5000 CALL MOVES("R$",16,Y2,V$):: Q=POS(V$,CHR$(0),1):: V$=SEG$(V$,1,Q-2):: Y2=Y2+16 This works, but is slow... An RXB conversion routine would be so much quicker! Imagine all the DATA statements, ARRAYS, etc. loaded with PLOAD and stored in SAMS? (But very fast.) A real memory saver. Is it possible that the RXB CALL MOVES could have a "max string length" value vs only a fixed one, find the string length byte and render the variable string?

A copy of the RXB 2024 Reference Guide with navigation links (clickable) for quick referencing. RXB2024.pdf

Been looking for something like this. Thanks!

An interesting map! Anyone who has used (I'm still using!) Realms, will have complete confidence in your ability to complete this project. While I often considered a more versatile TOD, never considered legacy compatibility. Can now see how this could easily work. Best wishes. MikeV.

By all means go for it! Also it would be great to be able to use variable length strings in SAMS without having to convert. It appears that all the info is there, i.e. "string length byte" to make this happen? Thanks.

I ran into the same issue. Searched, found, copied and pasted VCRUNTIME140.DLL from the CONVERT 9918 directory and was good to go.

Hi Fred, This is a really, really great addition to an already very useful program. Thanks for the hard work and continuing to support the TI community.

I could not believe that there were 60 fonts to select from! Nice work.

I actually did not know I had that game, but looked anyways. On an original TI it loaded and ran fine with RXB's 2015, 2022 and 2023. This was from a floppy however, cannot help with the Pi Pico as I do not own one. On Classic it loaded and ran fine except that the fire key 'Q' did nothing. Tried others but they did not seem to work either. Difficult to say for sure as survival time is quite brief without being able to fire. I presume this is a keyboard issue on my setup as the other keys worked.

Chris: sent you a note.