dhe

I have a Tomy I'd be glad to send you for a test install when you are ready! I also have an adam, but it's got a HD installed in the case - so kind of dicey to ship! Dano

Thanks pixelpedant, that works like a charm, and I'm a big fan of using batch files.

Matthew, To pose the questions a different way. Did you have to make any hardware or software changes to make either the MKI or MKII work with those two other platforms?

I've been playing with TI ImageTool - it's a really nice tool, with great documentation. Last night I wanted to test a disk image for errors/problems/bad things. It has a really nice check disk feature, and even offers to repairs errors that it finds, and gives you the option to save to a log file. So, when working under linux, I usually start a *.jar file from the command line with: javaws {something}.jar. It would appear Windows 10 doesn't like you to do that, and instead prefers that you just double click on the jar file. javaws - WILL tell you if your Java is out of date, warn you of your potential demise if you don't update immediately and takes you to the updater. Dano

I don't know about that one, I used it to check a 8K static ram. Unfortunately my TL866 is at work - far far away...

Matthew, When designing the MKI or MKII - do you notice differences between how the Tomy or Adam access the TMS9918A socket vs the 99/4a? tx, Dano

Given my recent bad experience with ChinaRam, I believe a basic TL866 programmer is worth the money, just for it's ability to check ram! It would seem the forging bad chips has become a really industry in China.

>I just went back and counted and I've shipped a total of 125 TIPI's to the community.. wow! I wonder how many of us there still are!

classic99 with a ryzen 4 processor and 64gb of memory, win1909 and I have accidentally left classic99 running over night with no issues.

What buttons (figuratively) need to be pressed to tell classic99 to enable the p-code card?

Hi, Are you doing this on a real TI, or an emulator? TurboPascal99 or UCSD?

And, old floppies that might not have been ran for a while, put your fingers in the diskette hole and turn them manually a few times. Sometimes they get sticky-enuf from non-use (poor storage) to ruin a drive. d.

ok, one of the great thing about this hobby is making a machine - yours. Arcade Shopper Turned me on to the trick of replacing 4116 with 4164 If it was my console, I'd 'upgrade' the vram and socket it, in machine screw sockets. Then see if you can source an old black and weight keyboard with mechanical keys, and clean the 9918A and get new heat sinking compound. Use it for the next two to four months, make sure there are no other quirks, and put an F18A later. But this one machine will truely be yours! 😃

1) Noted in the manual, E/A routines are built in. Is there a way to get to or use the interface - say load / run option 3? 2) is there a switch in the pull down menu that will enable super cart memory? Thanks, Dan

Come on ArcadeShopper - I'm thinking commercial product here! 😃

I really wanted to call this the tp2020 Challenge (as in finding toilet paper, but my wife advised me that it's still to early to joke about toilet paper). So the challenge is the setup tp99 as found here in dev tools, write a program and share challenges, found and over came! VorTICon write: That's too bad. But then it's not really the best Pascal version to use anyway and UCSD Pascal already runs perfectly in MAME Fortran 99 crammed so much in that package that it makes me wonder why WipoSoft was not able (or willing) to come up with a full Pascal implementation. No to mention that bone-headed memory protection scheme... I think there was a version the Barry Boone broke, disassembled and make some minor tweaks. I'll be trying in the next couple of days to get something working.

ok.. we need a new thread tp99 Challenge! I like tp99, I wrote Dan O'Quinn who wrote a tutorial on it, but now that seems lost in time. I was the original purchaser from LL Connor Enterprises and was very geeked out, when I found out there was additional packages to follow - sound and windows. I think tp99 was another one of those packages, that JUST needs a little more love and care, and had the source code been released at some point...

I'm really hoping Beery can get the source to FORTRAN99, there are a couple of things, I'd like to change, and I think easy fixes and upgrades (even for me). Like, I'd like to normalize more the selections on edit/compiler and link (like on compile, listing file is the third item asked for, on link the first) - consistency would help. I'd also like to modify, so if you have a minimem, or supercart, your default selections would be saved after the first run. fortran99 could have used a few more years of active development and maybe 20 active developers to shake out rough patches.... d.

kj4bdl and I'm a kantronics/hamsoft owner! 😃

What I have been doing, is printing the source {one of the options on the edit menu} to DSK4.?W.{SOMETHING}_LI - and then just navigating to that directory with textpad. Here is another, iteration. ti99dir, in to the source disk and then opening the file. C GRAPHICS EXAMPLE - 04/08/2020 - DHE C2345678 CALL SET32 C THIS GETS YOU COLOR AND SPRITE ROUTINES CALL COLOR ( 10, 10, 1) C CHAR SET, FORE, BACK COLORS CALL CHAR ( 111, '1824429999422418'X ) C SPRITE BUILT WITH FSF.IO SPRITEPAINTER PRINT , 'Hello World' CALL DELAY ( 30 ) C WAITS 3 SECONDS, COMPARE WITH CALL WAIT CALL SPCHAR ( 128, '1824429999422418'X ) C CHARCODE 128-255 ONLY CALL SPRITE ( 1, 128, 5, 92, 1, 24, -1, 3) CALL DELAY ( 40 ) STOP END

Today's quicky. Graphics Experiment. Unlike my previous attempts, this one worked exactly as expected the first time~! 1 99 FORTRAN File: DSK2.GE_S Page 1 1. C GRAPHICS EXAMPLE - 04/08/2020 - DHE 2. C2345678 3. CALL SET32 4. C THIS GETS YOU COLOR AND SPRITE ROUTINES 5. 6. CALL COLOR ( 10, 10, 1) 7. C CHAR SET, FORE, BACK COLORS 8. 9. CALL CHAR ( 111, '1824429999422418'X ) 10. C SPRITE BUILT WITH FSF.IO SPRITEPAINTER 11. 12. PRINT , 'Hello World' 13. 14. CALL DELAY ( 30 ) 15. C WAITS 3 SECONDS, COMPARE WITH CALL WAIT 16. 17. CALL SPCHAR ( 128, '1824429999422418'X ) 18. C CHARCODE 128-255 ONLY 19. CALL SPRITE ( 1, 128, 5, 92, 1, 24, -1, 3) 20. 21. CALL DELAY ( 40 ) 22. 23. STOP 24. END

>Does Fortran default to floating point or integers? variables starting with i,j,k,l,m,n are by default integer.

So, it was asked here, how does fortran99 compare speed wise to other compilers. I decided to write two little programs that looped and printed a value. Our first contender, while not a compiled language, was BASIC 10 FOR I=1 TO 100 20 PRINT I 30 NEXT I This took 19 seconds to run. For a comparison - in BASIC on my little Cambridge Z88 - it took 8 seconds. Next up was FORTRAN99 1 99 FORTRAN File: DSK2.SC_S Page 1 1. C QUICK FOR LOOP SPEED COMPARISON VS TI BASIC 04/07/2020 2. C234567 3. INTEGER I 4. 5. CALL CLEAR 6. 7. I = 1 8. DO 1 I=1,100 9. PRINT , I 10. 11. 1 CONTINUE 12. STOP 13. END This took 8 seconds to run. Of course, even the simplistic program wasn't a walk in the park and included a fight with the compiler and linker. Over and above speed, not being tied to line numbers is great. I think Microsoft realized late in life, line numbers {BAD}, because on the Tandy Model 100, the last machine, I'm told that Bill Gates worked on, when you type edit, the line numbers are there, but your in full screen editing mode. VORTICON again came to my rescue. The take away, I believe, if you want to use call clear (and maybe print) you have to link in the gl (graphics) library. The manual says, you will keep being prompted for libraries, until all dependencies have been resolved. That was not the behavior I was seeing. Instead, I would enter fl, and it would take me to the section about symbolic debugging. To force what I needed to happen, I entered gl on the library line, the linker, then prompted me again, for a library, this time, I entered fl. That did the trick, I was now able to run the program, I did end up with so oddities, in the compiler. It would say I had 1 Error(s) - but it wouldn't tell me what that error was! fortran99 can be a tough task master! 😃 I'm very much, hoping someday the source for FORTRAN99 show up, because, as a new user, I'm seeing a few rough spots, that probably wouldn't be that hard to fix, with specific test cases. d.

Finally got some simple i/o going... Some first observations: 1) I kept getting an odd error - don't understand >eod - Vorticon nailed this error, some junk had appeared after end... ( I think this is a bug)... Easy enough to work around once you know what the problem is..... 2) the end in the read, seems to sense end of data line, not end of file, I had to default to reading for a z (or 9999) record at the end of the data file. 3) could not get Hollerith or S types to work in a file read. 4) could not get just A to work. 5) what ended up working was 8a1 - because, it seems like fortran99 only wants to do single character i/o. 1 99 FORTRAN File: DSK2.FI_S Page 1 1. C FI_S - FILE I/O SOURCE 04/06/2020 2. C2345678 3. C DEFINE DATA TYPES 4. CHARACTER NAME(8) 5. INTEGER ERRSTS, NSTU, GRATOT, AVGGRA 6. 7. INTEGER FILEID(8), GRADE 8. DATA FILEID / 10HDSK2.FI_D / 9. 10. C INITALIZE DATA 11. NSTU = 0 12. GRATOT = 0 13. AVGGRA = 0 14. 15. CALL FILES (3) 16. CALL OPEN ( 3, FILEID, 2, 0, 1, 0, 80, ERRSTS) 17. 18. 1 FORMAT (' ', C12, M1.1, ' *** GRADES ***' ) 19. 2 FORMAT (' ', ' ') 20. WRITE (6,1) 21. WRITE (6,2) 22. 23. 10 FORMAT ( 8A1, I3) 24. 11 READ (3, 10, END=99, STATUS=ERRSTS ) NAME, GRADE 25. 26. IF (GRADE.EQ.999) THEN 27. GO TO 25 28. ENDIF 29. 30. 20 FORMAT (' ', 8A1 , 1X, I3) 31. WRITE (6,20) NAME, GRADE 32. 33. GRATOT = GRATOT + GRADE 34. NSTU = NSTU + 1 35. 36. GO TO 11 37. 38. 39. 25 CONTINUE 40. 30 FORMAT (' ',' ') 41. 35 FORMAT ('+', 'AVG GRADE:') 42. WRITE (6,30) 43. WRITE (6,35) 44. 45. C CALCULATE AVG GRADE - SIMPLE AVG 46. AVGGRA = GRATOT / NSTU 47. 40 FORMAT (' ', I3) 48. WRITE (6,40) AVGGRA 49. 50. 51. C 3 - FILE NUMBER, NO EQ TO A FORTRAN UNIT NUMBER USED IN FORMAT 52. C 2 - INPUT MODE 53. C 0 - DISPLAY 54. C 1 - VARIABLE 55. C 0 - SEQ ACCESS 1 99 FORTRAN File: DSK2.FI_S Page 2 56. C 80 - MAX RECORD LENGTH 57. C ERROR - VARIABLE TO RETURN ERROR IN 58. 59. C SEE PAGE 07-11 - FILE I/O REF 60. C SEE CALC1 FOR FILE I/O EXAMPLES 61. 62. C NAME = 8 HOL 63. C SPACE = 1 HOL 64. C GRADE = 3 INT 65. 66. 67. 99 CALL CLOSE ( 3 ) 68. STOP 69. END and the data file... 1 99 FORTRAN File: DSK2.FI_D Page 1 1. DAN 060 2. SALLY 100 3. BOB 074 4. JOE 097 5. EOF 999 Small working, byte size pieces of code is what you build off of.

Thanks Ksarul, I would have guessed binary on 4 with a 4a PS!