From Extended Basic Program to FlashRom99 in 12 minutes and 20 seconds

[twoodland]

Change line 180 to

180 open #1:"PI.CLOCK",DISPLAY, INPUT, FIXED 19

 

Then it should work

 

wolhess, thank you for your help. I tried it and the XB program works just like it did showing the formatted output that Omega posted. However, both the EA5 and BIN file output looks like:

 

 

I have attached my source files along with the XB, EA5 and BIN files.

 

Tipiclock.zip

[senior_falcon]

If this is being compiled there is a problem because the compiler only supports DISPLAY VARIABLE type files.

 

180 open #1:"PI.CLOCK",DISPLAY, INPUT, FIXED 19

[Omega-TI]

If this is being compiled there is a problem because the compiler only supports DISPLAY VARIABLE type files.

 

180 open #1:"PI.CLOCK",DISPLAY, INPUT, FIXED 19

 

The program works just fine WITHOUT the ",DISPLAY, INPUT, FIXED 19" portion in XB. Try removing that and recompile.

[twoodland]

 

The program works just fine WITHOUT the ",DISPLAY, INPUT, FIXED 19" portion in XB. Try removing that and recompile.

 

Thanks Omega, that is what I tried which led me to post the issue. In that case, the XB worked but the EA5 and BIN file had the same result: The screen would look as if it were going to load then it would boot back to the startup screen. Even if I then selected option 2 Tipiclock, the system would look like it was going to load for a sec then just warm boot.

[Omega-TI]

Major Bummer!

 

What would be cool is if there was a way to have a single E/A 5 program load XB -- AND -- a selected program for execution. That is one thing I really miss about my time with the TRS-80. One could type "BASIC program" and it would execute as easily as an assembly language program. I have no clue how something like that would be implemented on the TI though.

[twoodland]

If this is being compiled there is a problem because the compiler only supports DISPLAY VARIABLE type files.

 

180 open #1:"PI.CLOCK",DISPLAY, INPUT, FIXED 19

 

Thank you senior_falcon, I tried changing 180 to OPEN #1:"PI.CLOCK",DISPLAY,INPUT,VARIABLE but I had the same initial result. XB runs fine, EA5 and BIN looks like it will load and then warm boots to the startup screen. I also removed 190 and changed 290 to GOTO 200. I got the same result.

[twoodland]

I am not sure if this is the issue, but I am continuing to RTFM to discover which XB lines are not compiling to produce my expected result. senior_falcon pointed out DISPLAY VARIABLE and I have found this "IF-THEN-ELSE will only work with line numbers, like in TI BASIC. The more advanced XB style of IF-THEN-ELSE is not supported.". Although it is not working as I expect, I am happy to rework and try to think of different ways to produce what I am looking for. I am learning, and more importantly USING the TI equipment I am so fond of. I appreciate all who engage and offer help.

[senior_falcon]

Sounds like you are back in the cretaceous era. You can find the latest version in the thread XB Game Developer's Package on page 22, post #541. This does a much better job of supporting IF THEN ELSE statements.

Edited April 4, 2019 by senior_falcon

[wolhess]

 

wolhess, thank you for your help. I tried it and the XB program works just like it did showing the formatted output that Omega posted. However, both the EA5 and BIN file output looks like:

 

TCLKOutput.jpg

 

I have attached my source files along with the XB, EA5 and BIN files.

 

Tipiclock.zip

Hi twoodland,

 

the tipi also accept variable 19, so the compiler / XB256 will also work.

 

It seems that the compiler reads the entire clock-string into a variable. As in XB does the command LINPUT.

 

Here is my try in XB and EA5 with the same output in XB and in EA5. The EA5 works in 4ADOS too.

Press ENTER for just a second to exit the program

 

CLOCK.ZIP

[twoodland]

Sounds like you are back in the cretaceous era. You can find the latest version in the thread XB Game Developer's Package on page 22, post #541. This does a much better job of supporting IF THEN ELSE statements.

 

Thank you! I will check it out and get updated.

[twoodland]

Hi twoodland,

 

the tipi also accept variable 19, so the compiler / XB256 will also work.

 

It seems that the compiler reads the entire clock-string into a variable. As in XB does the command LINPUT.

 

Here is my try in XB and EA5 with the same output in XB and in EA5. The EA5 works in 4ADOS too.

Press ENTER for just a second to exit the program

 

CLOCK.ZIP

 

Thats It!!!! Thank you so much. Now to learn from your example. I did not think to segment out the data string even though I saw how it presented the data. Are the call sound statements used for a delay? I am guessing that because of the volume level at 30.

 

Thanks again I really appreciate it!

[wolhess]

yes, call sound is for delay.

[twoodland]

WOW! I have updated the XB Game Developers Package to ISABELLA! Boy, am I now spoiled. It is sooo nice! Thank you senior_falcon! Using the example solution provided by wolhess, I have learned a great deal and updated the program:

100 REM  *******************
110 REM  * TIPICLOCK v2    *
120 REM  * by TWOODLAND    *
121 REM  * and WOLHESS     *
130 REM  *-----------------*
140 REM  * For TIPI        *
150 REM  * Obetav035       *
160 REM  *******************
170 CALL CLEAR
180 OPEN #1:"PI.CLOCK",DISPLAY,INPUT,VARIABLE 19
190 CALL KEY(0,K,Q)
200 LINPUT #1:A$
202 W$=SEG$(A$,1,1)
204 D$=SEG$(A$,3,
206 T$=SEG$(A$,12,19)
210 IF W$="1" THEN F$="MONDAY"
220 IF W$="2" THEN F$="TUESDAY"
230 IF W$="3" THEN F$="WEDNESDAY"
240 IF W$="4" THEN F$="THURSDAY"
250 IF W$="5" THEN F$="FRIDAY"
260 IF W$="6" THEN F$="SATURDAY"
270 IF W$="7" THEN F$="SUNDAY"
280 DISPLAY AT(2,1):F$$:T$
290 IF Q=0 THEN 190
300 CLOSE #1
310 END

I have attached a zip containing the XB, EA5 and BIN versions. Woo Hoo! This is so much fun!

 

TIPICLOCK.zip

 

[Omega-TI]

I was going to inquire if the program below would compile, but while it APPEARS to run, it will NOT actually set the CorComp's clock.

Could someone please look it over and tell me WHY it's not doing what it is supposed to. It's driving me nuts.

 

10 CALL CLEAR

20 OPEN #1:"CLOCK"

30 INPUT #1:C1$,C2$,C3$

40 CLOSE #1

50 PRINT "RTC: ";C2$,C3$

60 OPEN #2:"PI.CLOCK"

70 INPUT #2:A$,B$,C$

80 CLOSE #2

85 PRINT "RPI: ";B$,C$

90 D$=A$&","&B$&","&C$

100 OPEN #1:"CLOCK"

110 PRINT #1:D$

111 CLOSE #1

115 PRINT "----------------------"

120 PRINT "SET: ";B$;" ";C$

[HOME AUTOMATION]

30 INPUT #1:C1$,C2$,C3$ SAME

70 INPUT #2:A$,B$,C$ SAME

90 D$=A$&","&B$&","&C$ WHAT

110 PRINT #1:D$ DIFFERENT

I am not familiar with the Corcomp clock's input or output formats...
however I doubt TI's "PRINT #" instruction will look at commas inside a string the same way as it will interpret commas(variable list seperators)
in it's command line.

thus

110 PRINT #1:D$
is not equivalent to...
xxx xxxxx #2:A$,B$,C$
even though D$ contains commas.

maybe...

10 CALL CLEAR
20 OPEN #1:"CLOCK"
30 INPUT #1:C1$,C2$,C3$
40 CLOSE #1
50 PRINT "RTC: ";C2$,C3$
60 OPEN #2:"PI.CLOCK"
70 INPUT #2:A$,B$,C$
80 CLOSE #2
85 PRINT "RPI: ";B$,C$
90 D$=A$&","&B$&","&C$
100 OPEN #1:"CLOCK"
110 PRINT #1:A$,B$,C$
111 CLOSE #1
115 PRINT "----------------------"
120 PRINT "SET: ";B$;" ";C$

M@ did say compatible.
...curious why the CLOSE and reOPEN of #1 also...

10 OPEN #1:"PI.CLOCK"
20 OPEN #2:"CLOCK"
30 INPUT #1:C1$,C2$,C3$
40 CALL CLEAR
50 PRINT "RTC: ";C2$,C3$
70 INPUT #2:A$,B$,C$
85 PRINT "RPI: ";B$,C$
90 D$=A$&","&B$&","&C$
110 PRINT #1:A$,B$,C$
115 PRINT "----------------------"
120 PRINT "SET: ";B$;" ";C$
130 CLOSE #1
140 CLOSE #2

REMember this is TI country so... don't expect this to work, ha.

 

Best of luck!

Edited April 13, 2019 by HOME AUTOMATION