Jump to content

MikeV

Members
  • Content Count

    142
  • Joined

  • Last visited

Community Reputation

150 Excellent

About MikeV

  • Rank
    Chopper Commander

Recent Profile Visitors

429 profile views
  1. Thank you for these, great job. This one in particular clarifies the rationale behind the method used by TI in TOD for graphics.
  2. Thank you for the list.
  3. Good video. That CALL IO has been a bit of a puzzle to me; the example (chimes) helped. Hope to see some more in the future.
  4. Some would say, "Its a keeper". However, the module and all the original Scott Adams' games are integral to Classic99.
  5. This is a great game, quite worthy of module status. It is difficult to imagine it being originally XB, compiled or otherwise.
  6. Thank you for the assistance. I think I'm finally getting there. Everything is actually still there... Just for grins I asked the wife yesterday, "What do you know about memory maps?" She replied, "It's what you use when you are trying to find things, doesn't seem to work very well at all." My question was apparently successful as she was grinning from ear to ear!
  7. That will have its uses. I've done it from Classic as well.
  8. That went well!!! I have the sidecar SAU as well. The SAU will provide 32K if another memory card is not present. In addition try this: Have the SAU powered, switch up. Turn on the TI without powering up the PEB. Go to XB and do a SIZE command and you will get 24,488 bytes of Program Space and 13,918 bytes of Stack Free. If you work from TI Basic in this setting you can load and run the large TI Basic programs originally written for cassette, e.g. Starship Pegasus, from the ramdisk and still have sufficient memory. As you pointed out it does not provide additional RAM beyond 32K to my knowledge. My earlier post was in regard to its ability to sense another card, act accordingly and why couldn't the SAMS do the same. I believe Asmusr answered that question, though I'm still mulling that over...
  9. It certainly does help. I was definitely looking at it as 32K + 1M (or 32K + 256K in my instance). Thank you!
  10. I had the CorComp 512K specifically in mind when I posted the initial question. It turns on/ off as a 32K, as necessary, without any to do. So I wondered why couldn't SAMS do this? It lives well with SAMS, can be used to load and run all the old TI Basic cassette programs, which are too long for a disk system. No CALL FILES required, etc.
  11. Once I finally figured out the BLOAD/ BSAVE command (a lot of experimentation) I really liked it. Not certain 'how' it worked, but it did (now replaced with PLOAD/ PSAVE). CALL SAMS seems to add more flexibility, but will require some study. (Good examples always help!)
  12. Thank you for the explanation. I certainly did not know that stuff at least in any usable, coherent fashion. How memory works, or is addressed on computers is a bit nebulous to me. However, the street address example was quite good, thanks for that. More memory is usually better. Circuits are generally on or off. When SAMS memory is accessed, does the identical memory address (and its contents) in SAMS overwrite its counterpart in the 32K, or is the circuit (pathway) simply rerouted to its SAMS counterpart and the 32K address then ignored? What do the 'mappers' actually do? ChrisB. said more or less the same thing about a DSR approach. However, over the last 30 years or so, ramdisks (which have DSRs) have been used many thousands of times in conjunction with TIs. SAMS - not so much. I am puzzled why this flexibility has not proven itself and become commonplace by now.
×
×
  • Create New...