I actually just remembered the last stupid thing I did on my Titanium, and it was before all of this happened.

I was working on the token file for my project (I was working on it yesterday and that's how I remembered) and I wanted to rename it something like "8xtoks". Unfortunately, the VAR-LINK dialog doesn't let you move a file to something with a number at the front, so I decided to try using Andrew V's cmd program (a DOS-style command line interface) that allows you to do things like move or rename archived files, or delete entire folders- things that the VAR-LINK dialog doesn't let you do.

When I tried, it screwed up my calculator... I don't remember exactly what happened but it was only solved with a combination of a RAM clear and resending the OS (not sure in which order). And after that everything seemed stable, until this...

Could this be related? Or is it still more likely that I ran some incompatible assembly program a while ago too?

Update: All one-byte tokens are now supported.

I've been working on an error-handling system, but it has some bugs at the moment (sometimes it works, sometimes it doesn't)... however, here's how it will work:

-If the converter reduces a line to a single character, and that character is not a token, an error message appears in a dialog box.

-The program then writes a question-mark token (not one of the unused tokens, the actual AFh question mark) in place of that character.

This is necessary because otherwise the program will enter an infinite loop, trying to break down the one-character line further.

I'm glad to see another 68k project on Omnimaga besides mine.  Good luck!

Or, perhaps also like the 89, one key combo (ALPHA + ON instead of SHIFT + ON?) could turn the calculator off but when it turns back on, the screen is saved, whereas the other one just turned off back to the starting screen?

An update- I now have a working tokenizer and converter! Screenshots follow, showing a rather simple program in 89 text file format, then the converter interface, and then the program in WabbitEmu (which is animated because I'm not quite sure how to take a non-animated screenshot).

I still have to write a token file before first release, though. And implement an error-checking system (to write 0x00 or something like that if there's an incorrect token).

After a bit of further thought, I've decided to change the name of the entire project to Solar89. I'm thinking that z89 sounds better for a 68k calc assembler for the z80 calcs... which is also a cool idea, definitely possible (if the z80 calcs themselves can support an on-calc assembler, than the more advanced 68ks can too) but probably a bit harder to do.

Wait, if we could make it so that the 83+ basic prgms made on the 68K calc, wouldnt that be cool?


{we would need some converter though}

I guess you mean, actually run the 83+ programs on the 68k calc?

I think it would be pretty cool. It would be an easier programming language for the 68k calcs (I find 68k Basic to be pretty easy compared to, say, assembly or C, but it is definitely harder than z80 Basic and I know others don't), albeit a less powerful and slower one.

I guess there are two ways it could be done- either make an interpreter for z80 Basic or write a program to convert a z80 Basic program (maybe one generated by Solar89?) to a 68k Basic program.

My favorite Pong game for the 89 is Aaron Miller's, which I think is reasonably obscure but it's definitely pretty good. I'm reluctant to try games made before 2004 on my Titanium (even with Hw3 Patch), and out of the remaining I'd say this is the best. It is simply Pong, not Pong with fancy features. If you want Pong with fancy features, play something else.

Okay, well I guess I've figured it out but I don't know what to do about it.

You can't free a pointer after you've changed it. And in that code, all pointers are either being memset (to reinitialize them to point to nothing) or changed (for instance, the line pointer is incremented).

The advice given in the GCC4TI docs is "preserve the original pointer and pass it to free". How would I do this? Make a function and pass the code where I'm manipulating the pointer there?