The TILP II 1.18 development cycle has officially started

Changes from TILP II 1.17 are few, but important:
* switched the development trees for libti*, gfm and tilp from SVN to Git. Two main repositories are used: libticonv + libtifiles + libticables + libticalcs on the one side ( https://github.com/debrouxl/tilibs ), gfm + tilp on the other side ( https://github.com/debrouxl/tilp_and_gfm ). The https://github.com/debrouxl/tilp_and_gfm/blob/master/tilp/trunk/build/scripts/install_tilp.sh helper script has been updated, you need to re-download it !
* 84+CSE ROM dumping through both I/O ports, by Benjamin Moody;
* 84+CSE screenshots through both I/O ports, by Benjamin Moody (with minor torture tests and translation updates by me).

Sadly, I haven't yet been able to test the new changes on a real 84+CSE...

Mid-level functionality for Jonimus' ROM dumper shall be integrated by creating a fifth libti* library, and moving some common code from gfm, tilp, titools and probably tilem into "tiopers" (current working name for that new library). Jonimus' driver-less Windows serial port backend is planned to find its way into the libticables code base as well.

The usual links:
* Windows installer download: http://tiplanet.org/beta/setup.exe .
* Source code: https://github.com/debrouxl/tilibs + https://github.com/debrouxl/tilp_and_gfm .
* patches not yet committed to Git: none this time
* install script for anything non-Windows which is handled by TILP: https://github.com/debrouxl/tilp_and_gfm/blob/master/tilp/trunk/build/scripts/install_tilp.sh (updated !).

EDIT in 2021: updated the link to the *nix install script.

A few things I have noticed with version 1.17:
the lack of a working silverlink OS sender
when you right click on windows, only one option shows up, and the rest are just separators. I can still click on the options, but I don't know what they say except that I have memorized the ones I use.

Thanks for the report

Adriweb managed to get a ROM dump from his 84+CSE, so 84+CSE ROM dumping is at least not completely broken (anyhow, it worked for Benjamin before he sent me the patch). I should be able to get a 84+CSE in the next few months.

Another problem is that when you install TiLP and request a GTK+ download, if you use a 32 bit Windows install it appears to download the wrong version, because everytime I checked that option, neither TiLP/GTK theme selector would crash on startup, so I had to download it from GTK website everytime.

Odd. TILP being a 32-bit application, AFAICT, it's supposed to use the 32-bit GTK+ runtime.
What GTK+ runtime are you downloading (link) ?

The ROM dumpers do work.  Must be something wrong with the Windows build.  Does ROM dumping work for other models?

the lack of a working silverlink OS sender

Elaborate, please.

when you right click on windows, only one option shows up, and the rest are just separators. I can still click on the options, but I don't know what they say except that I have memorized the ones I use.

I think I saw something similar at one point, probably because of a buggy version of GTK+.  The page DJ mentioned (http://lpg.ticalc.org/prj_tilp/win32.html) appears to be pointing to GTK+ 2.12.9, which is pretty old at this point.  The current TILP installer is using 2.24.8.

(I don't know why 2.24 would be crashing.  Try uninstalling both TILP and any old GTK+ packages, and installing everything anew?  There shouldn't be any 64-bit libraries involved, everything here is 32-bit except for the drivers.)

When I try to send an OS to my 83PSE or 84PSE, it gets through the point where the calculator says '0% Completed', and when it gets past sending the first page of the OS, the calculator says that there was an error, and the computer waits until the timeout time is past until it shows a timeout error. The direct USB OS sending works fine, and I can receive OSs from my friend's calculators with either link cable.

Thanks.  I don't know why it would be doing that, but I'll check it out.  To be clear, are you trying to send an official OS file from TI, or a third party OS?  Also, if you can, it'd be really helpful if you could post the log file (usually stored in "C:\Documents and Settings\username\.tilp.log") after trying to send an OS.

The log is attached. I am sending OS 2.53, I am almost positive it is signed, as the calculator does receive and validate over USB without a problem.

Notifications were broken for every single Omnimaga member except for XiiR3CR34T10N it seems, according to him, since he was getting them fine.

By the way is there any way to install Mallard on a TI-73 using TiLP? Some people have troubles with it it seems. It doesn't work in TI-Connect (anymore) either.