To each their own. I have lots of counter arguments, but none of that has to do with gcc.

(Does anyone really think I waste any time transferring files in my dev workflow when there are 200 ways to automate that for Unix to Unix?)

I can respect your stance on further multi-purposing of the tipi-connected Pi, especially since in increases the likelihood of problems and need for support which is outside the scope of TIPI, but people might still expect you to help.

Also - No, I didn't imagine you were manually copying files. I was referring to the transfer time required, automated or no

I have almost zero knowledge on the use of the Raspberry PI or anything Unix related. I have two PI's, one never even used, waiting for the TIPI. The other I have played around with a bit but beyond getting a working image to get online, that is about it. I did not even know the "lite" version had no desktop.

Myself, I was interested in some of the work Matt was doing and wondering if I could kill two birds with one stone with the gcc utilities and the TIPI. Thought it would make an interesting development platform if the possibility existed for either the TI-99/4A or Geneve.

At some point in time, I will need to get one of those books for "Dummies" to fully understand the layout, directories, etc. At this point in time, I just do not know the system to know what it can or can not do, or its limitations, thus my inquiry.

When I try to take the bin and plop it over into classic99 as PLATO in my DSK1 folder, and load with option 5, I get an I/O error 2...what am I doing wrong? (yes, dsk1 is mounted, and I can run other binaries in that folder)...

When I try to take the bin and plop it over into classic99 as PLATO in my DSK1 folder, and load with option 5, I get an I/O error 2...what am I doing wrong? (yes, dsk1 is mounted, and I can run other binaries in that folder)...

-Thom

You need to make sure the crt module is the first / at the head of your program...

An EA5 file is a memory image, and execution starts at the address where it is first loaded into.

Your code is setup to link into >A000... upper 24k of the memory expansion... good. typical.

But the first instruction in needs to be there at >A000... Just move crt to the top of the list from here:

I found the problem. somehow in my constant compiling and recompiling the toolchain to fix things, I munged up ea5split. Now the binary seems to run, if going to a green blank screen..that's okay.. at least I know it's attempting to load, I'll go forward now and see if I can start filling in the system dependent code....

my immediate goal is to get the terminal to output the protocol-encoded data in splash.c to render the splash screen. Once this works, 75% of the terminal is done, then it's hooking up serial and keyboard I/O.

What are the limitations of color in bitmap (GRAPHICS II) mode? I can try to graft in color support (the protocol decoder supports 24-bit color, but I will try to add support for the default system color constants, at least)

What are the limitations of color in bitmap (GRAPHICS II) mode? I can try to graft in color support (the protocol decoder supports 24-bit color, but I will try to add support for the default system color constants, at least)