Jump to content

Lee Stewart

+AtariAge Subscriber
  • Content Count

    4,748
  • Joined

  • Last visited

Community Reputation

2,688 Excellent

2 Followers

About Lee Stewart

  • Rank
    River Patroller

Profile Information

  • Gender
    Male
  • Location
    Silver Run, Maryland

Recent Profile Visitors

18,581 profile views
  1. Well—in the Forth 2012 standard mentioned by @TheBF, ACCEPT goes EXPECT one better by returning on the stack the actual number of characters entered. ...lee
  2. Which, I suppose, means fbForth 2.0 would run the same way? ...lee
  3. I do not believe the counted string is left on the stack, but, rather, its address. figForth (and its descendants TI Forth, fbForth, et al.) always stashes the parsed char-delimited token as a counted string at HERE and des not leave the address because it is already known. Pretty much the only useful place for WORD in figForth is in a definition because the very next token in the input stream is processed by INTERPRET , which uses WORD to parse it and store it at HERE , overwriting the token you were interested in before you can use it. A word that is more like Basic’s INPUT is EXPECT , which requires the storage address and maximum character count on the stack. Only the entered string is stored. ...lee
  4. Welcome aboard. This is the best place for all things TI-99/4A IMHO! ...lee
  5. It seems you did not read the tutorial. That is exactly what Chris did. There really is no easy way to get at the pins of the socket. It makes sense to expose the pins higher up on the chip by doing the filing rather than unnecessarily modifying (and, possibly, damaging) the board. ...lee
  6. Why? The new battery is in parallel with the old—same voltage. I would think it a problem only if the old battery develops an internal short. Is that likely? ...lee
  7. How much space you allow for the filename (probably should think “pathname”) depends on the DSR. The TI disk controller’s DSR only allows 10-character filenames, but other controllers allow longer paths that include subdirectory names. Even with the TI DSR, your PAB should allow for 25 characters because one way to specify a pathname is DSK.<diskname>.<filename>. Since the diskname can also be 10 characters, that is 3 characters for the devicename (DSK), 10 characters for diskname, 10 characters for filename and 2 characters for the ‘.’ separators. Remember that the namelength in the PAB is a single byte (byte 9). In your scenario, you would need to copy the LSB of COUNT to byte 9 of your PAB in VRAM. If your VRAM address of your PAB is VPAB, say, then something like the following would copy the namelength and the pathname for the file to your PAB: VPAB EQU >1200 VRAM location of PAB * * Copy namelength byte to VRAM location of PAB LI R0,VPAB+9 VRAM address of PAB's namelength byte to R0 MOVB @COUNT+1,R1 namelength byte to R1 BLWP @VSBW write the namelength byte to PAB * * Copy filename (pathname) to VRAM location of PAB LI R0,VPAB+10 VRAM address of PAB's filename to R0 LI R1,FNM RAM address of filename to R1 LI R2,COUNT namelength to R2 BLWP @VMBW write the filename to PAB ...lee
  8. Immediate instructions cannot use contents of addresses (@FNM). They can only use values such as symbols (FNM) and numbers known at assembly time (10). Something like the above that would assemble, though it would be nonsense, is LI R5,PAB+FNM+COUNT ...lee
  9. You need that connector where it is. It contains circuitry for conditioning weakened (due to distance and shielding) signals to/from the PEB. Think of it like the shortstop relaying a throw from centerfield to the plate. You would not put the shortstop in centerfield with the fielder to throw all the way home—kind of defeats the purpose. ...lee
  10. Not sure what you are saying. The caps are certainly removable—I’ve done it. ...lee
  11. It is the “traditional” breakfast spot for the Faire—a block or so from the library. Oh—and, there is no drive-thru! ...lee
  12. fbForth (either one) can handle files of any kind if properly set up. If you want to use the Forth blocks editors, you must use DF128 files. It does not matter what you name them as long as they are DF128. As you know, a Forth block is 1024 bytes (8 DF128 records), so you would need to watch what you do past line 13 character 7 (both zero-based). Beyond that, you would need to write your own editor in Forth because the Forth editors only know how to handle DF128. Anything else requires that you set up file handling with your own PABs. General file handling is built into fbForth 2.0 but needs to be loaded from the appropriate FBLOCKS with fbForth 1.0 (block 47), which adds 1000 bytes to the dictionary. ...lee
  13. Not certain what you mean here. Forth can do whatever you are doing in Assembler, excepting, of course, the cartridge Forths—unless you dispense with the Supercart. You cannot have two cartridges operating at the same time. ...lee
×
×
  • Create New...