In the process of making the latest version of Solar89, I got fed up with having to copy and paste *.89t and *.89p files and change their extensions to *.v2t and *.9xt. I wrote a Python script to do it for me called renamr68k.

What exactly am I talking about, you ask? (If you understood exactly what I just said, skip the next two paragraphs).

GCC4TI produces executable files for all three supported 68k calculators- the 92+, the 89, and the V200. However, if an assembly program needs external files, or is coupled with useful TI-BASIC programs (both of which are true for Solar89) and you only have one 68k calculator, you'll need to manually create duplicate versions for the other calculators. So if I need the text file "test.89t", I send it to my computer from my 89, make two copies, and change them to "test.9xt" and "test.v2t".

The same problem is true if you are making BASIC programs with your calculator and would like to support the other 68ks. Yes, in both cases a user could do it themselves, but they may not know that the file formats are identical on all three 68k calculators.

Hence, this Python (2.x) script. Credit to Kerm for coming up with the core of the name- renamr (which I expanded to renamr68k).

It has been submitted to Cemetech and ticalc.org... download here on Cemetech.

Kerm suggested "Renamr" on Cemetech- I amended it to renamr68k. Unless I (or someone else) can come up with a better name, that's what it will be called.

Indeed, the TI-68k Developer Utilities, integrated from GCC4TI 0.96 Beta 10 onwards, do not contain a tool for that purpose specifically.

Ah- I was a little worried something like it already existed and I was reinventing the wheel here.

renamr68k it is.

I've uploaded it to the Cemetech archives, and to ticalc.org. I take it the Omnimaga database isn't finished yet, as there has been no announcement... so not there yet.

EDIT: It's available on Cemetech now.