Jump to content

RXB

Members
  • Content Count

    3,996
  • Joined

  • Last visited

  • Days Won

    2

RXB last won the day on November 20 2016

RXB had the most liked content!

Community Reputation

1,489 Excellent

About RXB

  • Rank
    River Patroller
  • Birthday 01/22/1954

Profile Information

  • Gender
    Male
  • Location
    Vancouver, Washington, USA
  • Interests
    Computers, Science, Technology, TI99/4A
  • Currently Playing
    World of Warcraft. Left4Dead, CoD4
  • Playing Next
    Mosty TI games and some CoD or Diablo

Recent Profile Visitors

17,348 profile views
  1. The question you did not answer was why is it changing UPPER CASE to lower case?
  2. From TI DIR TI DSK to PC DESKTOP it is changing the CASE for some unknown reason. Look if the file is LRXB6 and after changed to lrxb6 on desktop that is not a copy of the same name, I asked WHY IS IT CHANGING CASE OF NAME? What does the Alpha lock have to this transfer?
  3. Incorrect you can do OPEN and CLOSE from Command Edit mode as I do it all the time >OPEN #1:"DSK1.BATCH",INPUT >CLOSE #1 INPUT and LINPUT need a line number only due to in Command Edit mode used same buffer so crashed.
  4. Ok first off this will open and also put anything in a DV80 file including TI Writer codes or any hidden control characters: 100 OPEN #2:"DSK8.BATCH",OUTPUT 110 LINPUT #1:Z$ Defualts for open are DV80 Also defaults are LINPUT will fetch a line that does not crash the way INPUT does if you have other then characters 30 to 159 in a files. LINPUT is what I always use as INPUT crashes more often.
  5. A much better idea is just dump TI Basic and keep XB and those two GROMs should have been used for more OS features like XB Assembly support and Editor Assembly in Console.
  6. RXB runs BASIC with no modifications, but not with EA Assembly Support. But then TI Basic with Assembly Support is slow and very very limited compared to XB with Assembly support.
  7. Disagree, been updating XB (RXB for over 20 years now).
  8. Yea I have in the package PC Text Source, TI99/4A DV 80 files, GRAM files, XB programs, and even Classic99 package to install unitl Tursi includes it into Classic99 And to top it off a CALL USER demo file that makes a number of XB demo programs.
  9. Yea one anoying thing about TIDIR for me is when you copy a file like say LRXB6 from TI Files directory on Classic99 to desktop PC DOS file it changes the name from LRXB6 to lrxb6 and of course TI99/4A can not use it. Got to ask why is it changing the case?????
  10. RXB 2020 will change the SAMS use and how it is used. Before only Lower 8K of Assembly space was for SAMS, not all 32K pages at 4K boundaries can be saved or loaded. Before only 4K pages both at Lower 8K Assembly space was used for SAMS, now all 32K of pages at 4K boundaries can be used.
  11. Hello Ok I tested CALL PRAM and you can switch to lower 8K to put your XB programs and use the upper 24K for Assembly. But I do not have enough space in RXB to put the other CALL UINIT (Upper INIT) as it takes to much space in GPL. 1268 bytes is just to much space out of RXB 2020 to find. Was cool to see the LINK names in >FFE6 down to >E000 as you could have 1018 CALL LINK names for XB to do this. Would have been a cool feature but space is a huge issue already. *NOTE: all XB support routines had to be adjusted to >A040 added to them as an example is 0110 A042 C534 FFA DATA IFFA FIRST FREE ADDRESS (FFA) POINT 0111 A044 0000 LFA DATA ILFA LAST FREE ADDRESS (LFA) POINT 0112 * 0113 A046 AA55 HAA DATA >AA55 CONSTANT TO SIGNAL INITIALIZED 0114 * 0115 * UTILITY BLWP VECTORS 0116 * 0117 A048 A09A DATA UTILWS,NUMASG NUMERIC ASSIGNMENT 200A A0D6
  12. Crap! RXB 2020 may not work properly from Console only after all, by allowing changes to XB RAM locations the VDP would require more work then I care to put into it. Worst case RXB 2020 will not work properly in Console only mode with no memory expansion. It may run with no problems but any memory changes in Console are out of question a problem that will crash. In that case RXB 2015 is your only option.
  13. I rarely get giddy but WOW this is just so such a first. I have a new routine called CALL PRAM(start-XB-program-address,end-XB-program-address) This works for VDP or RAM and automatically decides which one it uses determined by 32K or just Console only! You can decide how much space is used and where to load every XB Program, with the bonus that you do not need to remember where it loaded or saved. The start and end address can be in VDP or RAM thus say you want in RAM start address of >FF00 and end address of >E000 of a 2K XB program. Or load into VDP at say start address of >2400 and end address of >3500 and move a VDP table to where you want with no crash. Demo will be out soon...
×
×
  • Create New...