RXB Posted March 28, 2022 Share Posted March 28, 2022 RXB 2022 DETECTIVE WORK Quote Link to comment Share on other sites More sharing options...
1980gamer Posted March 29, 2022 Share Posted March 29, 2022 Couple of observations, In the TI Basic version, You use an UNDER SCORE _ instead of MINUS - in the PEEK. I didn't even know you could PEEK in Normal TI Basic? Then you change the GOTO in 130 from 110 to 100, but never changed it to 100. Bad idea? Maybe, I think clever. It is simply an Extended Basic program, not an RXB or BASIC program. And, you just bummed me out! I have a similar "mini game" in one of my games. Didn't know about LEMON DROP TREE. LOL Don't know how you discovered this? Was it random chance, no pun intended. Or were you testing RXB? Great job if it was the later! Oh, I also heard an ERROR during the PASTE into RXB. Like LINE length to long or something? Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted March 29, 2022 Share Posted March 29, 2022 17 hours ago, RXB said: RXB 2022 DETECTIVE WORK First off, as pointed out by @1980gamer, you did not actually change the GOTO in line 130 to 100—it remained at 110. Next, again as pointed out by @1980gamer, the first argument of CALL PEEK is _31808, not -31808. This means it is reading the value of variable, _31808, as the address to read. That variable, of course, contains 0, the beginning byte of the console ROM, which is >83 (13110). As you will recall, 131 was the number that was read every time. Lastly, -31808 is >83C0 (ISR’s R0 and Random Number Seed), not >83C8 (ISR’s R4). This means that CALL PEEK(-31808,D) is reading the MSB of >83C0, the Random Number Seed. The reason this works in XB is that XB’s RANDOMIZE calls GPL RAND four times, which operates on the full word at >83C0. The reason the above PEEK does not work in TI Basic and RXB is that TI Basic’s RANDOMIZE does not change the MSB of >83C0. Rather, it stores the current value of the VDP Timer Byte (>8379) in the LSB of the Random Number Seed (>83C1). This means that the above PEEK, indeed, is reading an unchanging value each time it reads >83C0. ...lee 1 Quote Link to comment Share on other sites More sharing options...
RXB Posted March 29, 2022 Share Posted March 29, 2022 9 hours ago, 1980gamer said: Couple of observations, In the TI Basic version, You use an UNDER SCORE _ instead of MINUS - in the PEEK. I didn't even know you could PEEK in Normal TI Basic? Then you change the GOTO in 130 from 110 to 100, but never changed it to 100. Bad idea? Maybe, I think clever. It is simply an Extended Basic program, not an RXB or BASIC program. And, you just bummed me out! I have a similar "mini game" in one of my games. Didn't know about LEMON DROP TREE. LOL Don't know how you discovered this? Was it random chance, no pun intended. Or were you testing RXB? Great job if it was the later! Oh, I also heard an ERROR during the PASTE into RXB. Like LINE length to long or something? Yea in the video I noticed 130 GOTO 110 I typed wrong Ti Basic but was just showing what I found in testing long before I made the video. I write in GPL and Assembly to make RXB since 1986 so this project has been around for awhile and I test just about everything I can before release. Yea the ERROR HONK you heard was me pasting into Classic99 before RXB 2022 was finished looking for a key press for Drive for LOAD program. It just did not load the first line "100 ! ********************" so why I said no problem. 1 Quote Link to comment Share on other sites More sharing options...
RXB Posted March 29, 2022 Share Posted March 29, 2022 1 hour ago, Lee Stewart said: First off, as pointed out by @1980gamer, you did not actually change the GOTO in line 130 to 100—it remained at 110. Next, again as pointed out by @1980gamer, the first argument of CALL PEEK is _31808, not -31808. This means it is reading the value of variable, _31808, as the address to read. That variable, of course, contains 0, the beginning byte of the console ROM, which is >83 (13110). As you will recall, 131 was the number that was read every time. Lastly, -31808 is >83C0 (ISR’s R0 and Random Number Seed), not >83C8 (ISR’s R4). This means that CALL PEEK(-31808,D) is reading the MSB of >83C0, the Random Number Seed. The reason this works in XB is that XB’s RANDOMIZE calls GPL RAND four times, which operates on the full word at >83C0. The reason the above PEEK does not work in TI Basic and RXB is that TI Basic’s RANDOMIZE does not change the MSB of >83C0. Rather, it stores the current value of the VDP Timer Byte (>8379) in the LSB of the Random Number Seed (>83C1). This means that the above PEEK, indeed, is reading an unchanging value each time it reads >83C0. ...lee Yea like I said in last post above this one to 1980gamer. Either way figured the RXB and TI Basic 100 RANDOMIZE line was the issue in the game and test program. This is why you do not assume nothing changes ever in programming, dependence on that is an address that is only used for 1 thing ever. And this also assumes no changes ever exist. Besides my RANDOMIZE and RND are 5 times faster then XB too so this like replaced that CALL PEEK(-31808,D) line with this: 550 X=INT(RND*28+1) :: IF Z(X,1)=0 THEN Z(X,1)=B :: Z(X,2)=C ELSE 550 Moved RAMDOMIZE to: 540 RANDOMIZE 545 FOR A=1 TO 27 :: READ B,C This makes RANDOMIZE only called one time in program and as RXB RND works like it is supposed to is better then the CALL PEEK. I had a couple EYE floaters that day so mistook >83C0 as >83C8, always gives me a headache. 1 Quote Link to comment Share on other sites More sharing options...
GDMike Posted March 29, 2022 Share Posted March 29, 2022 8 hours ago, Lee Stewart said: Lastly, -31808 is >83C0 (ISR’s R0 and Random Number Seed), not >83C8 (ISR’s R4). This means that FYI.. i forgot about where this was located, and it was under my thumb all last weekend. Thanks Lee for RE pointing this out. 1 Quote Link to comment Share on other sites More sharing options...
GDMike Posted March 29, 2022 Share Posted March 29, 2022 6 hours ago, RXB said: I had a couple EYE floaters that day so mistook >83C0 as >83C8, always gives me a headache. I had a boat load of that myself last week, had to look it up and find out what th it was. Then the headache hit, not too bad, but it appeared. 1 Quote Link to comment Share on other sites More sharing options...
RXB Posted April 3, 2022 Share Posted April 3, 2022 RXB 2022 DEMO 12 Demo of RANDOMIZE and RND and HCHAR and VCHAR in RXB 2022 RXB 2022 DEMO 12 - YouTube 3 1 Quote Link to comment Share on other sites More sharing options...
RXB Posted April 6, 2022 Share Posted April 6, 2022 RXB 2022 RELEASED RXB 2022.zip 2 1 Quote Link to comment Share on other sites More sharing options...
+TheBF Posted April 7, 2022 Share Posted April 7, 2022 On 4/3/2022 at 6:10 PM, RXB said: RXB 2022 DEMO 12 Demo of RANDOMIZE and RND and HCHAR and VCHAR in RXB 2022 RXB 2022 DEMO 12 - YouTube That's a great improvement. Nice work. 1 1 Quote Link to comment Share on other sites More sharing options...
senior_falcon Posted April 7, 2022 Share Posted April 7, 2022 On 4/3/2022 at 6:10 PM, RXB said: RXB 2022 DEMO 12 Demo of RANDOMIZE and RND and HCHAR and VCHAR in RXB 2022 RXB 2022 DEMO 12 - YouTube It would be interesting to see how XB 2.9 G.E.M. and RXB 2022 compare when running this demo program. Congrats on releasing RXB 2022! 2 1 Quote Link to comment Share on other sites More sharing options...
HOME AUTOMATION Posted April 7, 2022 Share Posted April 7, 2022 I'm ascared! 3 2 Quote Link to comment Share on other sites More sharing options...
+TheBF Posted April 7, 2022 Share Posted April 7, 2022 It got me curious too about my system and I owe Rich a thank you because it pointed out that I had not build protections into my HCHAR and VCHAR. I don't use them much because I normally read, write and fill VDP RAM directly but... they should work as advertised. So THANKS Rich. 3 Quote Link to comment Share on other sites More sharing options...
RXB Posted April 7, 2022 Share Posted April 7, 2022 4 hours ago, TheBF said: It got me curious too about my system and I owe Rich a thank you because it pointed out that I had not build protections into my HCHAR and VCHAR. I don't use them much because I normally read, write and fill VDP RAM directly but... they should work as advertised. So THANKS Rich. I had the suggested version of CALL HCHAR(row,column,character#,-repetitiion) but after converted to assembly you could not tell if going forward or backward it was just to fast to tell. So the -REPETITION was not used due to the speed increase. Best feature is running TI Basic games on Console only USING RXB 2022 so a demo video is coming soon... 3 Quote Link to comment Share on other sites More sharing options...
SteveB Posted April 7, 2022 Share Posted April 7, 2022 ... and here is the update Package-File for TiCodEd. Only minor adjustments as most changes are speedups and few new subroutines. RXB 2022.xbpkg 2 Quote Link to comment Share on other sites More sharing options...
RXB Posted April 20, 2022 Share Posted April 20, 2022 Bug fixes but no new release: RXB 2022 BUG FIX FOR PERIOD KEY - YouTube Quote Link to comment Share on other sites More sharing options...
RXB Posted April 20, 2022 Share Posted April 20, 2022 Well update figured out how to double size of REA buffer for Directory, not sure yet how many files but could be as almost double. Original size of VDP buffer for REA Directory was 6784 bytes, new size is 12032 bytes. Thus around 200 filenames vs 127 so that is an improvement. With some work could bump it up to 250. 2 Quote Link to comment Share on other sites More sharing options...
RXB Posted April 24, 2022 Share Posted April 24, 2022 RXB 2022A released Fixed the issue pointed out by Tursi and updated a better SAMS initialization routine. Also changed menu of REA Directory to make more sense. RXB 2022A.zip 3 Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted April 25, 2022 Share Posted April 25, 2022 Up and running on my HSGPL emulation in MAME. Thanks! 1 Quote Link to comment Share on other sites More sharing options...
+mizapf Posted April 27, 2022 Share Posted April 27, 2022 Here's the RPK. rxb2022a.rpk and the disk images. The DSK1 folder in In The Dark requires more than 360K, so I'm not sure whether this should be split to two images, or whether I should create an 80 track image (which would require to mount an 80-track floppy drive in MAME). rxb_inthedark.dsk rxb2022_games.dsk rxb2022_sams.dsk rxb2022a.dsk 2 1 Quote Link to comment Share on other sites More sharing options...
RXB Posted May 14, 2022 Share Posted May 14, 2022 RELEASE RXB 2022C updated bugs found by Archadeshopper and optimized Assembly so works better. RXB 2022C.zip 6 Quote Link to comment Share on other sites More sharing options...
HOME AUTOMATION Posted May 15, 2022 Share Posted May 15, 2022 Looks like CALL CLEAR has been ...cleared! This could perhaps effect compatibility. Quote Link to comment Share on other sites More sharing options...
Tursi Posted May 15, 2022 Share Posted May 15, 2022 22 hours ago, HOME AUTOMATION said: Looks like CALL CLEAR has been ...cleared! This could perhaps effect compatibility. To be a little more direct, it does appear that 2022C does not recognize CALL CLEAR... unless I ported it incorrectly into Classic99? 1 1 Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted May 15, 2022 Share Posted May 15, 2022 Same error in MAME 1 Quote Link to comment Share on other sites More sharing options...
+DuaneAL Posted May 16, 2022 Share Posted May 16, 2022 So to be clear, you are saying it is unclear,? 2 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.