Jump to content

Casey

Members
  • Content Count

    421
  • Joined

  • Last visited

Everything posted by Casey

  1. I had the opposite experience. I had the TI 99/4A first, and then a Commodore 128, which spent 98% of its time in 64 mode. After all the commands that TI BASIC has that the 64’s BASIC 2.0 does not, I felt the Commodore had a steeper learning curve. But I love both platforms. All that said - TIPI and Force Command, and many of the newer things are things that no one who designed the TI could have envisioned. The fact that the TI’s operating system allows for devices that were never pictured to just work when designed properly is a really powerful thing. One nice thing about the TIPI is that the config file can be changed easily within TI BASIC using the normal file processing commands. I suspect if someone ever designed a VICPI, it would be similar though - either with its own device number on the serial bus, or accessed via a SYS if it plugged into the cartridge port.
  2. How hard would it be to have the label printed on it in the style of Hex-Bus Interface seen here ? (With “Speech Synthesizer” of course) - this would match the style of the beige 99/4A perfectly. http://aug.99er.net/unreleased.htm
  3. Here’s my test program for this, in TI BASIC: 100 OPEN #1:”DSK1.TEST”,OUTPUT,INTERNAL,VARIABLE 254 110 PRINT #1:1,2,3,4,5,”CASEY” 120 PRINT #1:6,7,8,9,10,”CASEY” 130 CLOSE #1 140 OPEN #2:”DSK1.TEST”,INPUT,INTERNAL,VARIABLE 254 150 INPUT #2:A,B,C 160 PRINT A,B,C 170 INPUT #2:D,E,F 180 PRINT D,E,F 190 CLOSE #2 Results from running this program: 1 2 3 6 7 8
  4. If I was going to move a + across the screen from left to right in TI BASIC on row 3, I would do it this way: 100 CALL CLEAR 110 R=3 120 FOR I=1 TO 32 130 CALL HCHAR(R,I,ASC(“+”)) 140 CALL HCHAR(R,I,32) 150 NEXT I In Extended BASIC, you could simplify it: 100 CALL CLEAR 110 FOR I=1 TO 28 120 DISPAY AT(3,I):”+”::DISPLAY AT(3,I):” “ 130 NEXT I One thing that isn’t obvious to a person new to the TI: while the screen is 32 columns wide, PRINT and DISPLAY will only use the middle 28 columns, while CALL HCHAR can access all 32. Column 1 for DISPLAY AT is the same as column 3 when used with CALL HCHAR.
  5. This is also possible in TI BASIC, but it’s cumbersome compared to Extended BASIC. Using your example: 100 FOR I=1 TO LEN(A$) 110 CALL HCHAR(10,10+I-1,ASC(SEG$(A$,I,1))) 120 NEXT I
  6. One thing that happened that I didn’t expect. I typed CALL LOAD(-2,244,3) to change the screen colors to white on blue. Leaving XB 2.8 with BYE and coming back in, it remembered that. I turned off the power to 99/4A, turned it back on, and it still remembered that. Then I remembered my Jedimatt 32K was plugged into power, so I unplugged it, plugged it back in after about 15 seconds, and XB 2.8 still remembers the color setting I made. I turned off the console, plugged in TI Extended BASIC instead of the FG99, entered in CALL PEEK(-2,A,B)::PRINT A;B and got back 244,3. Where could these values be kept when the power is off? If I CALL LOAD(-2,244,0) then inside TI Extended BASIC, turn the power off, put back the FG99, and go back into XB 2.8, CALL PEEK(-2,A,B)::PRINT A;B printed 244 and 0. The result of CALL PEEK(-8,etc) you asked for, printed this for me: 145,0,0,16,7,240,244,0
  7. I tried to attach my NanoPEB to see if I could answer a question above. Either it no longer works or I don’t know where I’ve put the proper power supply for it, but I couldn’t get it to work. When I reattached the TIPI, now, I get a purple screen with light blue letters, and CALL PEEK(-2,A,B) returns 93 and 1. The only other change I made was I did an apt update to update the OS on the Pi.
  8. I just did this with my FinalGrom and I got 0 and 0 right after power up and choosing it from the FG99 menu.
  9. This is to the composite input on your monitor/TV? My NIB 99/4A that I got 2 years ago looks like that also - maybe not quite to that extent. But I can see vertical lines going down the screen and some color fringing as well, depending on the colors. Black background with white letters is very rainbowy. It’s always been this way.
  10. DM3 was going to be bundled with the Hex Bus floppy disk controller/drive, right? (That’s my recollection from reading the manual a while back). The Hex Bus controller was designed for 4 drives also? (1 drive/controller, and 3 drives without controllers?). I do wish the Hex Bus interface and peripherals had been released for the 99/4A. Would have made for a much more cost effective system.
  11. Back when I had a 99/4 and a sizable cart collection, the only carts I had that wouldn’t show up on the 99/4’s menu were the ROM only Atarisoft carts. Parsec would show up but didn’t work because of the bitmap mode it requires that the 99/4 doesn’t have. Selecting Parsec from the menu simply cleared the screen and then returned to the color bar screen.
  12. If you read contemporary discussions of these 8-bit machines, the Commodore and Atari machines have what was called a full screen editor. What we think of today as a full screen editor with search and replace is not what they were referring to back in the day. The Coco has an EDIT command. It’s actually very full featured.
  13. I’m the same way. I like my cartridges to run from the FG99, but my BASIC programs to run from the TIPI. A remarkable number of the cartridges that would use a storage device also have no problem using the TIPI for that. The only one that does not that I’ve run into so far is Video Chess, which will only save/load from cassette.
  14. Yes, the Commodore screen editor worked just like that. You could put the cursor anywhere on any line, make a change, and it would take it. In the context of its time, that was what you’d call a full screen editor. Other computers used an EDIT command (TI, TRS-80 Color Computer, I’m sure others). Some used keyboard sequences to pick up characters (Apple). The full screen editor was much simpler than all that.
  15. The original Dartmouth BASIC (where BASIC was developed) ran on a time sharing system and it’s command for retrieving programs from storage was OLD (opposite of NEW as @mizapf noted above). There’s some history of BASIC here - another OS command will be familiar to us as well: https://www.dartmouth.edu/basicfifty/commands.html
  16. I know all of the Commodore 8-bit machines have the full screen editor. Ataris also have that I believe.
  17. I would vote for Commodore BASIC 7.0 and TI Extended BASIC. However, I wonder if the results of your question won’t just be the ones we have fond memories of using when they were contemporary. Certainly that was the case for my answers
  18. Has there ever been a mechanism to take a TI BASIC program and convert it to GROM as documented in the Software Development System manual available to the masses? And how many modules were released that were created this way, do we know? It’s a very interesting concept to me.
  19. Matt, One very minor issue I’ve encountered both before and after 2.0: TIPICFG doesn’t like my WiFi SSID because it has spaces in it. It will let me type it in, but it truncates it after the first space. I was able to get around this by editing PI.CONFIG from TI BASIC and it displays fine on TIPICFG after that and it works fine with the SSID with the spaces. I just can’t input it in TIPICFG successfully. For everyone else so inclined, I did attempt to upgrade my Raspbian stretch to buster in place, mainly just to see if it would work at all. I had saved off all my disk images from the TIPI prior to doing so just in case I bricked my install. The upgrade worked, but the TIPI was not happy after I did that (any access to the TIPI just caused the TI to hand with the TIPI access light stuck on). I then re-flashed my SD card with the 2.0 image and all is well. I was able to upgrade to 2.1 using the touch command provided above, so all seems ok. Thanks!!
  20. I no longer have it, but I had a 99/8 for a time that had a dead-end on the side port connector (there were no actual pins there). It did have the p-system intact (but was obviously not useful since the only peripheral I had was the cassette recorder). Mine also had Extended BASIC II.
  21. I wish I still had the 99/8 I had many many years ago, but times were tough back then. What I’d like to have, if money were no object (and they existed) is the beige sidecar speech synthesizer and hex bus adapter, along with the full complement of the Hex Bus peripherals to plug into my 99/4A.
  22. Interesting. TI BASIC and TI Extended BASIC both change the reference to 32767, so you did make it better
  23. No, this is not at all what he means. What he means is: >100 IF A=1 THEN 200 >110 END >RESEQUENCE >LIST 100 IF A=1 THEN 32767 110 END He isn’t asking the interpreter to magically turn direct statements into program lines. He’s asking for something else. (I’m not sure what the solution is to this - it’s hard for an interpreter to know what you intended, but maybe a message in the output of RESEQUENCE?)
  24. You may never do it, but I would argue that 100 IF EOF(1) THEN CLOSE #1 or 100 IF NOT EOF(1) THEN INPUT #1:A$ makes more sense logically than: 100 IF EOF(1)=-1 THEN CLOSE #1 (The resequence thing where you or someone wants the computer to magically add direct statements to a program is a whole separate bit of nonsense.)
  25. The only problem with this is something like this: 100 OPEN #1:”CS1”,OUTPUT,INTERNAL,VARIABLE 110 FOR I=1 TO 10 120 PRINT #1:I 130 NEXT I 140 CLOSE #1 This produces 10 leader tones while the tape is in the record mode the entire time it is writing. I mean I get why you’d write one out at the beginning of the file, but not at the beginning of each record.
×
×
  • Create New...