Jump to content

Bill R Sullivan

Members
  • Content Count

    141
  • Joined

  • Last visited

Community Reputation

137 Excellent

About Bill R Sullivan

  • Rank
    Chopper Commander

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For anyone who has functional hands and fingers. Remember, I don't "touch type" or solder or attempt to fix malfunctioning computer hardware any more, and picking locks is not something I ever did, as losing or misplacing keys was not something I did either. Yucks! How much my little corner of the world has changed.
  2. That means I'll have to go out and purchase the large document folder to ship those additional manual items along with the Forth+ SCREENs of low level code, as I could not find the key for my large 4 drawer cabinet out in the garage.
  3. Beery, I was just glad to be a part of the 9640 Geneve taking over the TI's Home Computer contribution, as my first 9640 Geneve became a "Guinie pig" for GenMod and 2MB MEMEX; White Pages galore!. We did everything to make the Geneve faster with up-graded components, all for naught. It was almost two years until termination resistors on the 2MB MEMEX address lines cured the abominable White Pages. Anyway, it was only a small matter of time before this GenMOD Geneve died. Bud Mills could not fix it, so he replaced it with a standard 9640 Geneve, and later after several upgrades, it was a very happy PFM 515K+ with 2 MB MEMEX, but can only use 504K of it. At one time I had two GenMOD Geneves, each with one 2MB MEMEX! Now here I am pounding on a PC wireless keyboard, that before I started packing to move, served my TI-99/4A with F18 V1 NanoPEB & USB, Dell E6430 8GB laptop, Dell E6420 4GB laptop, and Dell 7010 Optiplex MT 20GB and 500GB SSD, via 4 port VGA/USB K/V/M. Now the two laptops along with docking stations are packed up for the move. BTW they are both running MINT Linux, while the MT is still Windows 7 PRO, but once moved will also go over to MINT Linux.
  4. The only place I know for this info is Paul Charlton's GenPROG. I paid $75.00 for my copy, which I did not receive until after the MDOS buy out, when GenPROG became part of the buy out! I also contributed to the buy out; twice. Until now I was done with the 9640 Geneve (especially the GenMOD version); so fortunately I will be taking a 6 to 9 month hiatus from AtariAge, 9640 Geneve, MDOS and XOP. Saved by my daughter's desire to move out of this hacienda. Strange what trivia comes to mind by painful past events.🥵
  5. Remember, both text modes in Forth+ are implemented directly, same as TI Forth, and the graphic modes GRAPHIC 2-7 are implemented with MDOS XOPs!
  6. Hi Beery, I think GDMike passed his 9640 Geneve to someone else to test for memory problems, so it will be a while before he can do this, as he only has his TI-99/4A right now. I'm shipping him more pertinent Forth+ info this afternoon, along with other TI, Geneve and maybe Linux stuff to others.
  7. Packing up computer hardware is much more FUN.😄 However, disconnecting, and untangling cables is HYSTERICAL!🥵
  8. Mike have you tried the non-high res graphic modes; GRAPHIC/1/2/3/4/5? This paragraph may hold the reason for your TEXT80 to GRAPHIC6/7 problem.
  9. You should check to see how the MOUSE functions in the simple and hi-res GRAPHIC modes, as I don't recall doing anything like what you're doing in TEXT80, but then I don't recall using the MOUSE in TEXT80 mode. Oops, it's dinner time, so hopefully I'll have time to check in tomorrow.
  10. The MOUSE is available in TEXT80, but not SPRITES. Your MOUSE has to be a text character only.
  11. Are you doing this in TEXT80 or GRAPHICS6/7?
  12. Mike, after today I won't be able to help you any more until after we get moved and settled in. This probably means 6 to 9 months from now. Tomorrow I have to ship my SNUG EVPC off for repair, and some old Red Hat Linux stuff also (I will also send you that other X4th99 document as it explains some Forth+ operations due to adapting that aspect to X4th99); so after that I may monitor activity here from time to time, but that is all. Some of the things you are trying to do make no sense to me. In the beginning a Forth+ user should verify each library loaded and check memory used. Once loaded, any particular library remains loaded until there is insufficient memory to load another, at which time a previously loaded library will be de-activated, and the memory used for the selected library (I don't recall the protocol for selecting the library to be de-activated). Remember, MDOS only has 64K total memory, as you don't have a MEMEX card of 512K - 2MB; like I was using developing Forth+. Which was released early December 1991, almost 30 years ago! My confusion today is between version 1.01 and version 2.00 that I was working on while I was in Poland from late 1996 to late 1997. Which I abandoned when MESS emulation of the 9640 Geneve did not produce a single new Forth+ user (I believed using emulation to do development would prolong the life of Classic Computer hardware, etc.). Also "CALL(" parameter items can also be placed on the standard forth stack outside the "CALL(...library1...library2 )" for faster execution. The procedure for doing this is in the Forth+ Manual, which also limits the entire string of characters and spaces between "CALL(" and ")" to 80 bytes or less. For you it might be better to consider "Chain" or "Batch" files (also covered in the Manual) for increasing the capacity of your Geneve system. Hopefully other forth users here will try to help out more often now. GOOD LUCK!
  13. I missed it because there were so many unread AtariAge emails in my inbox!
  14. It's going to take me quite a while to analyse this, but what I can tell you is that using "CALL(" is really neat once you master the parameter stack outside the "CALL(" and especially inside the "CALL("; another very important aspect of "CALL(" is that, is if you make a single "CALL(" the RETURN parameters to your previous "CALL(" are all there in proper order, and if not used accordingly or removed the "CALL(" RETURN stack will eventually overflow, and probably cause a lockup! This explanation may be too confusing, because it doesn't cover the case of multiple libraries being accessed in a single "CALL(". In any case this is the primary reason for two library zones in version 2.00, and now I have a big headache. Shame on you.🥴 BE CAREFUL OF PAGE 52!!
×
×
  • Create New...