The *.cpp files are all c++ source files, the *.hpp files are all c++ header files.

compiledm.bat compiles everything if you're using Windows. First, it compiles the c++ stuff using Digital Mars' C++ compiler (which is free, and available at digitalmars.com, if I recall correctly - if not, ask Google where to find it), assuming you have it installed into c:\dm (the default location). If compiling any file fails, it will not try to compile the rest, and will show the errors and pause to wait for you to press a key (to close the window when you're done with it).

compiledm.bat also attempts to use py2exe to package update.py into an EXE. If that fails*. But considering that you'd already need python 2.3 to stick update.py in an EXE, you might as well just use update.py directly (unless you're modifying it for other than personal use and want to redistribute it with the maximum convenience). Anyways, all the files that are created in dist/ are REQUIRED for update.exe (which is also in dist/) to work. At least, I THINK they're all required (All I know about py2exe I learned in the past 15 minutes).

It will fail if you don't have python 2.3 installed to c:\python23, or if you don't have py2exe installed. Or it could fail if you break something. About it only checking c:\python23 for Python instead of checking your registry to see where it is installed, batch files are too dumb to read the registry to find out if you have it installed somewhere else, and it's easy enough to cange the batch file to look in the right place anyways if you DO have it installed somewhere else.

If you don't care about making an update.exe, then you don't need to. It's the last thing that's done, so even though compiledm will think something failed, it doesn't do anything afterwards except close the window, so just bash your keyboard with your TI-89 so the window goes away. Or you could just press a key. Whichever is more satisfying to you.

distupdate.py is what tells py2exe to do its stuff.

compile.sh is the compile script for Linux. I've tried to keep it up to date even though I haven't tested it or any of this stuff on Linux, since I haven't had Linux installed for in months and months. compile.sh does not try to turn update.py into an EXE, for obvious reasons. If you're using linux, you probably already have python installed, and when you want to run update.py, you can probably just do ./update.py.

89tformat.txt is just documentation of the file format of 89t files. You can find more comprehensive (and prettier) documentation about all sorts of things (link protocol, file formats, and more) for all sorts of TI calculators at http://www3.sympatico.ca/michel.brodeur/michel.brodeur/ - if that link dies, ask google about 'ti-89 text file format' or something like that (that's how I found it). I checked that after I initially figured out most of the 89t file format, and it clarified things and answered several questions that I had.

Okay, now the source files:
	update.py is the (source to the) update script. (I probably didn't even need to say this, but I'm being thorough)
	FromTxt.*, ToTxt.*, and Sync.* are respectively the main source files for FromTxt, ToTxt, and Sync89t.
	Shared.cpp and shared.hpp are needed to compile all three of those.

That's all.
	