FinalGROM 99 request:

[Bill R Sullivan]

33 minutes ago, RXB said:

It only resides in GROM 0, 1 and 2 and I have used GROM 0 only version that worked pretty well.

 

 

SOB.zip 19.75 kB · 1 download

Understood, I've downloaded the SOB.zip file, but it will probably be late afternoon tomorrow before I report back.  Thanks for the download.

[Bill R Sullivan]

17 hours ago, RXB said:

It only resides in GROM 0, 1 and 2 and I have used GROM 0 only version that worked pretty well.

 

 

SOB.zip 19.75 kB · 5 downloads

Well, I will have to admit that SOB is very impressive (OPA MICRO-MANAGER V1.10.9102.27)!  Yes, I can even do a lot with it, but it won't satisfy my desire to complete TIB+.  It will even load an MSAVEd TI Basic program (COLOR VISIONS), and it runs perfectly, but it cannot load TIB+ (also MSAVEd), because it does not have the E/A TI Basic support code: INIT, LOAD, LINK, PEEK, POKEV, PEEKV and CHARPAT (verified with DSRSCAN)!  Should they ever add those very useful CALLs (also remember that they too must work within MSAVEd TIB+ programs, so your version of those CALLs require the Tursi fixes), let me know.

Edited December 8, 2020 by Bill R Sullivan
Added more info.

[RXB]

3 hours ago, Bill R Sullivan said:

Well, I will have to admit that SOB is very impressive (OPA MICRO-MANAGER V1.10.9102.27)!  Yes, I can even do a lot with it, but it won't satisfy my desire to complete TIB+.  It will even load an MSAVEd TI Basic program (COLOR VISIONS), and it runs perfectly, but it cannot load TIB+ (also MSAVEd), because it does not have the E/A TI Basic support code: INIT, LOAD, LINK, PEEK, POKEV, PEEKV and CHARPAT (verified with DSRSCAN)!  Should they ever add those very useful CALLs (also remember that they too must work within MSAVEd TIB+ programs, so your version of those CALLs require the Tursi fixes), let me know.

You mean my REA TI Basic support routines in TI Basic that Tursi fixed?

[Bill R Sullivan]

16 minutes ago, RXB said:

You mean my REA TI Basic support routines in TI Basic that Tursi fixed?

Yes, I spelled them out: INIT, LOAD, LINK, PEEK, POKEV, PEEKV and CHARPAT that require Tursi's fixes.  Any chance that this will happen in the next six months?  They worked as is in TI Basic/TIB+ programs in VDP, but did not work from within MSAVEd TI Basic programs (GRAMs 3 - 7) that used those CALLs.  Jeff White provided program tests that showed the problem, and I provided everything else needed for Tursi to find and fix the problem.  I've been using his modified GK files EABASGRM & EABASGRM1 of your REA TI Basic files ever since.

Edited December 8, 2020 by Bill R Sullivan
Added more details.

[RXB]

I have used XBRAMDISK myself:

 

100 !Saved program will stay in memory as long as you do not CALL INIT or turn memory expansion off.
110 !It will ever stay in memory when switching cartrides with a WIDGET.
200 CALL CLEAR
220 CALL CHAR(42,"AA55AA55AA55AA55",91,"7E8199A1A199817E")
230 CALL CHAR(45,RPT$("0",8)&"FF"&RPT$("0",10)&"10387CFEFE")
240 CALL CLEAR :: CALL HCHAR(2,4,42,26)
250 CALL VCHAR(3,4,42,5) :: CALL VCHAR(3,29,42,5)
260 DISPLAY AT(5,9)SIZE(12):"RAM-DISKETTE"
270 CALL HCHAR(8,4,42,26)
280 DISPLAY AT(12,4):"[ MARTIN KOTULLA 1985"
290 CALL HCHAR(13,6,45,22) :: DISPLAY AT(17,7):"DATAs CHECK?   Y"
296 DISPLAY AT(22,4):"CALL LINK("&CHR$(34)&" LOAD"&CHR$(34)&") retrieve"
300 ACCEPT AT(17,22)BEEPSIZE(-1)VALIDATE("YN"):JN$
310 IF JN$="N" THEN 360
320 FOR I=8192 TO 8458 STEP 2 :: READ A,B :: SUM=SUM+A+B :: NEXT I
330 DISPLAY AT(20,5):"THE DATA-LINES ARE"
340 IF SUM<>20638 THEN DISPLAY AT(22,10):"INCORRECT!" :: END
350 DISPLAY AT(22,11):"CORRECT!"
360 CALL INIT :: RESTORE
370 FOR I=8192 TO 8458 STEP 2 :: READ A,B :: CALL LOAD(I,A,B) :: NEXT I
380 CALL CLEAR :: STOP
390 DATA 032,068,255,255,000,000,170,085,000,000,041,097,032,056,033,126
400 DATA 032,056,033,226,032,056,035,076,032,056,036,050,032,056,036,110
410 DATA 032,056,036,132,032,056,036,144,247,147,248,118,255,231,247,146
420 DATA 255,255,076,079,065,068,032,032,032,196,083,065,086,069,032,032
430 DATA 032,122,000,000,002,001,032,050,002,129,032,066,027,014,192,001
440 DATA 002,002,131,074,140,176,022,006,140,176,022,004,140,176,022,002
450 DATA 192,048,004,080,002,033,000,008,016,239,002,000,037,000,200,000
460 DATA 131,034,002,224,131,224,004,096,000,206,002,224,032,008,192,032
470 DATA 131,132,096,032,131,048,002,032,033,012,002,128,064,000,026,003
480 DATA 002,000,011,000,016,236,007,032,032,048,192,032,131,048,002,001
490 DATA 033,012,220,112,136,000,131,132,018,252,200,032,131,048,032,040
500 DATA 200,032,131,050,032,042,200,032,131,132,032,044,200,032,131,134
510 DATA 032,046,016,029,002,224,032,008,200,032,032,048,032,048,022,003
520 DATA 002,000,029,000,016,204,192,032,032,040,002,001,033,012,220,049
530 DATA 136,000,032,044,018,252,200,032,032,040,131,048,200,032,032,042
540 DATA 131,050,200,032,032,044,131,132,200,032,032,046,131,134,004,192
550 DATA 216,000,131,124,002,224,131,224,004,096,000,112
560 END

 

[Bill R Sullivan]

19 minutes ago, RXB said:

I have used XBRAMDISK myself:

 

100 !Saved program will stay in memory as long as you do not CALL INIT or turn memory expansion off.
110 !It will ever stay in memory when switching cartrides with a WIDGET.
200 CALL CLEAR
220 CALL CHAR(42,"AA55AA55AA55AA55",91,"7E8199A1A199817E")
230 CALL CHAR(45,RPT$("0",8)&"FF"&RPT$("0",10)&"10387CFEFE")
240 CALL CLEAR :: CALL HCHAR(2,4,42,26)
250 CALL VCHAR(3,4,42,5) :: CALL VCHAR(3,29,42,5)
260 DISPLAY AT(5,9)SIZE(12):"RAM-DISKETTE"
270 CALL HCHAR(8,4,42,26)
280 DISPLAY AT(12,4):"[ MARTIN KOTULLA 1985"
290 CALL HCHAR(13,6,45,22) :: DISPLAY AT(17,7):"DATAs CHECK?   Y"
296 DISPLAY AT(22,4):"CALL LINK("&CHR$(34)&" LOAD"&CHR$(34)&") retrieve"
300 ACCEPT AT(17,22)BEEPSIZE(-1)VALIDATE("YN"):JN$
310 IF JN$="N" THEN 360
320 FOR I=8192 TO 8458 STEP 2 :: READ A,B :: SUM=SUM+A+B :: NEXT I
330 DISPLAY AT(20,5):"THE DATA-LINES ARE"
340 IF SUM<>20638 THEN DISPLAY AT(22,10):"INCORRECT!" :: END
350 DISPLAY AT(22,11):"CORRECT!"
360 CALL INIT :: RESTORE
370 FOR I=8192 TO 8458 STEP 2 :: READ A,B :: CALL LOAD(I,A,B) :: NEXT I
380 CALL CLEAR :: STOP
390 DATA 032,068,255,255,000,000,170,085,000,000,041,097,032,056,033,126
400 DATA 032,056,033,226,032,056,035,076,032,056,036,050,032,056,036,110
410 DATA 032,056,036,132,032,056,036,144,247,147,248,118,255,231,247,146
420 DATA 255,255,076,079,065,068,032,032,032,196,083,065,086,069,032,032
430 DATA 032,122,000,000,002,001,032,050,002,129,032,066,027,014,192,001
440 DATA 002,002,131,074,140,176,022,006,140,176,022,004,140,176,022,002
450 DATA 192,048,004,080,002,033,000,008,016,239,002,000,037,000,200,000
460 DATA 131,034,002,224,131,224,004,096,000,206,002,224,032,008,192,032
470 DATA 131,132,096,032,131,048,002,032,033,012,002,128,064,000,026,003
480 DATA 002,000,011,000,016,236,007,032,032,048,192,032,131,048,002,001
490 DATA 033,012,220,112,136,000,131,132,018,252,200,032,131,048,032,040
500 DATA 200,032,131,050,032,042,200,032,131,132,032,044,200,032,131,134
510 DATA 032,046,016,029,002,224,032,008,200,032,032,048,032,048,022,003
520 DATA 002,000,029,000,016,204,192,032,032,040,002,001,033,012,220,049
530 DATA 136,000,032,044,018,252,200,032,032,040,131,048,200,032,032,042
540 DATA 131,050,200,032,032,044,131,132,200,032,032,046,131,134,004,192
550 DATA 216,000,131,124,002,224,131,224,004,096,000,112
560 END

 

I don't understand the purpose of this as I don't run XB programs.  I do occasionally use Super-XB loaded from FG99, when I have a major re-arrangement of code to do, but before and afterwards it will not run in XB!  Therefore, it is necessary to select Editor/Assembler or Assembler/Editor by Winfred Winkler from FG99 or insert my SuperCart in the TI port.  Right now I have my 80K MG GramKracker in the TI port with SOB and a few MSAVEd programs which work well if they don't contain any of the CALLs that this topic thread is about.  Which I must also report that SOB operations and features are not well documented.  So how about a manual for OPA MICRO-MANAGER V1.10.9102.27?

[Bill R Sullivan]

On 12/6/2020 at 4:20 AM, ralphb said:

The SuperCarts are not compatible with the FinalGROM, because they have their RAM at a different address than the FG99 (even with options R, G, X).

Hey Ralph, another thought crossed my mind as I was browsing though this topic thread; What addresses are used by FG99 for default, "R" and "X"?  I can change the address for BCART in source or object code.

Edited December 8, 2020 by Bill R Sullivan
Fixed typo

[Bill R Sullivan]

On 11/24/2020 at 6:47 PM, HOME AUTOMATION said:

There are different references as to how to create TI BASIC sub-programs, to be found here and there ...here is a somewhat useful one:

 

http://www.nouspikel.com/ti99/titechpages.htm

 

This would probably mean programming in assy. ...but that might not be what you want to do.

 

I don't know how MSAVE works... I'm guessing it can load a saved file into GRAM?

 

Setting up GRAM on FG99 shouldn't be too difficult... just need to create the desired size file, set the RAM byte, and perhaps set-up a header, using a hex-editor ...then end the filename with G.bin.

 

So, we could make an image similar to that of the Super Space II, but using virtual ROM pages instead of RAM. Does TIB+, truly require RAM, or is RAM needed only to load??? Perhaps we could find an alternate way to load instead.

 

Page switching would be through writes to ROM, rather than CRU switching, but could still be done through CALL LINK or CALL LOAD.

 

 

Hey Alex, since Ralphb's response negated any chance of actually doing SuperCart/SuperSpaceI/II emulation I've reconsidered your idea: "Page switching would be through writes to ROM, rather than CRU switching, but could still be done through CALL LINK or CALL LOAD."  Is this something you would still be willing to explore?  If not I'll understand, as I don't want to waste your time.

[HOME AUTOMATION]

31 minutes ago, Bill R Sullivan said:

Is this something you would still be willing to explore?

Sure? ...however, I can't promise I'll be much help. Plus, it seems that my time is my own, less and less these days. I don't think you'll need an assy. subroutine to switch pages, as I believe you can just poke the addresses directly from BASIC, unlike with the SUPER SPACE II.

 

I think the "R" or "X" need to be in the header, in order for FG99 to recognize them. That means that if your image includes GROM, then they should be specified there, instead of from the ROM's/RAM's .BIN. Although I have experimented with using 2 separate headers in such a case, usually there is only one... I think that is the way FG99, sees it ...Dunno for sure right now though.
 

[Bill R Sullivan]

6 minutes ago, HOME AUTOMATION said:

Sure? ...however, I can't promise I'll be much help. Plus, it seems that my time is my own, less and less these days. I don't think you'll need an assy. subroutine to switch pages, as I believe you can just poke the addresses directly from BASIC, unlike with the SUPER SPACE II.

 

I think the "R" or "X" need to be in the header, in order for FG99 to recognize them. That means that if your image includes GROM, then they should be specified there, instead of from the ROM's/RAM's .BIN. Although I have experimented with using 2 separate headers in such a case, usually there is only one... I think that is the way FG99, sees it ...Dunno for sure right now though.
 

Yes, this is the idea, and I have asked Ralphb for the default, "R" and "X" addresses, so that aspect can be handled.  RXB has put me onto SOB, OPA MICRO-MANAGER" that is helpful to TI Basic users/programmers, but is NOT a replacement for my TIB+ by any degree.  My AL is much better when done in forth, which was the first computer programming language I learned back in the mid-70's, about 7 years before we got our first TI-99/4A for Christmas 1982.  Let me know how you think we should begin, and when you might have a little time to do so, as I'm in the same boat, because my daughter wants to sell this house and move into a smaller house ASAP, and it's my house for as long as I'm alive.  I wonder if I need to watch my back??

[Bill R Sullivan]

On 11/10/2020 at 6:26 PM, acadiel said:

Bill, @FALCOR4 is here on the forums and can likely help troubleshoot your GK.  We also have the test utilities (burn in) that I uploaded to Whtech that can help diagnose what’s malfunctioning. 

I just want to thank you for putting FALCOR4 the Master MG GramKracker Repairman in touch with me, as he received my MG 80K GramKracker one day and the next day it was fixed (two problems, at least one caused by me), and then put into an overnight auto test, and will be shipped back to me today.  Truly amazing!  So thanks again, and all my best to you.

 

RetroBill (fdos)

[+acadiel]

1 hour ago, Bill R Sullivan said:

I just want to thank you for putting FALCOR4 the Master MG GramKracker Repairman in touch with me, as he received my MG 80K GramKracker one day and the next day it was fixed (two problems, at least one caused by me), and then put into an overnight auto test, and will be shipped back to me today.  Truly amazing!  So thanks again, and all my best to you.

 

RetroBill (fdos)

He's an amazing guy.  I really am thankful we got him back in touch with the community!

 

[Bill R Sullivan]

28 minutes ago, acadiel said:

He's an amazing guy.  I really am thankful we got him back in touch with the community!

 

Me toooooooooooooooooooooooooooooooooooooooooooooooooooo!

[Bill R Sullivan]

I've totally checked out my 80K MG GramKracker, and all aspects are working as they should, so I'm a very satisfied customer.  I still need to find someone willing to fix my SNUG EVPC, then all my systems that I kept will be operational.

[Bill R Sullivan]

On 11/9/2020 at 2:56 PM, Bill R Sullivan said:

A couple of years ago I requested GROM0, GROM1 & GROM2 be made available as GRAM0, GRAM1 & GRAM2, which would not only be very useful for my TIB+ project, but also to XB users (4ADOS,OS99 and others).  Nothing came of it, so this request is for Super Space II, as I don't know if I'll ever get my actual Super Space II to ever work again, even for just BANK 0 (SuperCart) only operation.
RetroBill (fdos)

I'm glad to report that I myself found the actual Super Space II problem and fixed it, as I can now select all four banks and save BCART Basic programs in each using HOME AUTOMATION'S FDOS or just CALL LINK the object file.  So my plan for this module will succeed.

 

And a huge thank you to FALCOR4 for finding all the problems in my 80K MG GramKracker and fixing them in less than two days.  There are some really great guys, and probably gals, here.  Unfortunately, it is not possible to BCART save Basic programs in the MG GramKracker RAM banks, so I will have to make do with 40K of MSAVE space by avoiding RESTORE line numbers which do work in BCART.

[+Torrax]

What was your fix to your Super Space problem??  Were the jumpers misconfigured?

[Bill R Sullivan]

13 hours ago, Torrax said:

What was your fix to your Super Space problem??  Were the jumpers misconfigured?

Uh ha, I knew leaving out the full solution would be the only way to get a response.  No, it was not a jumper problem, as I tried every strapping option in the manual except those that were for smaller chip sizes.  I scrounged a true 32K (8K x 4) memory chip out of my bad early CF7A+ sidecar (currently using a NanoPEB F18 V1 sidecar), and it works almost perfectly using CALL LINK("BANK",x); x= 0,1,2 or 3, of course.  The almost means that a power reset defaults to BANK 3, not BANK 0, but I can live with this anomally.

 

Any more comments?  I'm listening........

[Bill R Sullivan]

On 1/19/2021 at 11:20 AM, Bill R Sullivan said:

Uh ha, I knew leaving out the full solution would be the only way to get a response.  No, it was not a jumper problem, as I tried every strapping option in the manual except those that were for smaller chip sizes.  I scrounged a true 32K (8K x 4) memory chip out of my bad early CF7A+ sidecar (currently using a NanoPEB F18 V1 sidecar), and it works almost perfectly using CALL LINK("BANK",x); x= 0,1,2 or 3, of course.  The almost means that a power reset defaults to BANK 3, not BANK 0, but I can live with this anomally.

 

Any more comments?  I'm listening........

I'm still listening......  And now I have an update, as the 32K chip from my old damaged CF7A+ sidecar bit the dust over a month ago, but I've managed to purchase 5 used original 8K x 4 chips specified in the Super Space II Manual, and the first one is in and working!  Funny/strange thing though is that it too defaults to bank 3, not bank 0!  I suspect that the PAL may indeed be damaged in some minor way, as bank switching has been consistent for several days now; even though the bad chip kept draining the batteries very quickly, which is not the case now.  So it seems what I believed to be an anomaly is now my normal bank switching process.  If anyone can offer an explanation for this anomaly, please do so.