senior_falcon

That is font 11 in XB 2.9 G.E.M. Font 3 is a similar bold font that I like better. The capital letters are 6 pixels wide, so unfortunately this would not work on a TI99 in 40 column text mode.

However, the typical top speed of a stock Grom with a 125cc engine is generally around 55 to 60 mph.

Bruce Harrison wrote some short stories that were on his web site at one time. Are these available anywhere?

Turns out there is a style of fonts called "Small Caps" https://www.fontsc.com/font/tag/small-caps I have a book about the interurban railroad running from Ithaca to Auburn that uses a small caps font. That is the only time I have other seen that, other than on the TI99/4a. Actually, it seems odd to have to learn the alphabet twice, once for upper case, and once for lower case.

No, the XB/TML code with the error that I posted that you said crashed the computer. Here is the program modified to avoid having to use COS. This is compiled and you can see it is a bit less leisurely.This is running at normal speed, not CPU overdrive. But of course, although it works the same, it is no longer the same program. 100 DIM SINE(11) 110 FOR I=1 TO 11 :: READ SINE(I):: NEXT I 120 CALL SCREEN(2):: PD=1 130 A=0 135 IF PD=1 THEN CALL LINK("PENHUE",3+INT(RND*14),2) 140 FOR I=1 TO 11 150 CALL LINK("PUTPEN",100,120,A) 160 W=A/180*SINE(I) 170 R=9+A/18 180 CALL LINK("PU"):: CALL LINK("FWD",R-W/200) 190 IF PD=1 THEN CALL LINK("PD")ELSE CALL LINK("PE") 195 CALL LINK("FWD",W/100) 200 A=A+3 :: IF A>1453 THEN 230 210 NEXT I :: GOTO 140 230 PD=PD+1 :: PD=PD AND 1 :: GOTO 130 240 DATA 0,51,97,136,164,178,178,164,136,97,51,0

Don't know why it would not work for you. I just copied and pasted the code above and it works fine.

How funny! I never noticed that before. Looking at the code it is obvious it was done on purpose. It falls right in the middle of some DATA bytes.

The RND in BASIC is over 5x faster than RND in XB. Both RXB and XB2.9 G.E.M. now use the faster TI BASIC random number routine. I have a feeling that it may not be as random as the XB one though. Random numbers in a compiled XB program are different than they are in a BASIC/XB program. Compiled code can only use integer arithmetic. That is a problem, because in BASIC a random number is from 0 to .9999999 The work around is to multiply the random number by another number. i.e. instead of: 10 IF RND<.5 THEN 100 ELSE 200 you would use 10 IF RND*2<1 THEN 100 ELSE 200 RND*2 gives a random integer from 0 to 1 RND*6 gives a random integer from 0 to 5 and so on....

If you came up with a programming language like that, you would be a VERY wealthy man!

I think that is right. I must have gone dyslexic for a moment. Now I am totally baffled as to why my way would work at all!!! I am tempted to compile this, but it would have to be converted to integer math. Maybe I will get around to it.l

Not trying to hijack the thread, but I couldn't resist seeing this in The Missing Link. This is in CPU overdrive on my geriatric Dell computer. It takes about 2.5 minutes at normal speed. 5 CALL LINK("COLOR",3,2):: CALL SCREEN(2) 10 FOR A=0 TO 1440 STEP 3 20 CALL LINK("PUTPEN",96,120,A) 23 W=(A/180)*COS(A*5.5*180/PI) 25 R=9+A/17 26 CALL LINK("PU"):: CALL LINK("FWD",R-W) 27 CALL LINK("PD"):: CALL LINK("FWD",W*2) 30 NEXT A 40 GOTO 40

Haven't forgotten you. I have been sidetracked by the XB256 sound player, but that's wrapping up and I should get back to this soon.

I have ironed out all of Cheung's problems and now his sound lists play properly when running in XB256 and when compiled. The hardest problem to fix was getting the XB 2.9 G.E.M. version to handle CALL LINK("XB256",1905) so it actually worked as described to save a 1905 byte long buffer for the sound list. This took days of head scratching but it finally has been fixed so it now behaves the same as the disk version. Another "bug" was that F3 did not work to disable the interrupt driven autocomplete routine. As it turns out, I changed that key to ESC or F9 but forgot that I did that. I found this out by reading the manual! I am now working on the docs to make them a little clearer. Using sound lists is a bit tedious, but the versatility and compactness is worth it.