Nice to see a new version, I'll have to install it. Does it get around the validation somehow when sending an OS, or is that completely controlled by the calculator's firmware?

TiLP sends validation information and then it's up to the calculator's boot code to determine if it's valid or not.

So by using the link equivalent of a packet sniffer, it might be possible to do away with the whole pull the batteries partway through validation thing?

I've been working on that problem :)

Firstly there is Ponginstaller, which is a little program (currently in the Perpetually-Not-Quite-Finished phase) that sends signed and unsigned OSes via the standard protocol. Using Ponginstaller you still have to pull the batteries if you want to install an unsigned OS, but the timing is not so important. It's also a bit faster and (in my experience) more reliable than the various other link programs I've used.

Secondly, you could install a small OS (think less than 8k) which would be more intelligent than the boot code, and could include automatic patching, on-the-fly decompression, resuming transmission after an error, and other such wonderful things. This is in the Still-Mostly-In-My-Head phase.

And thirdly, there are other exploits you could use...

Great, good to know the project is still alive.

Are they even still releasing new OS es for the 83+ ?

Great. Now I'll be able to unwreck my calc (in the event of a catastrophic system failure) that much faster! =U

*Reading TiLP2 description*

Uhm, whats a "89tm"? I always called it the "89Ti", is tm another abbreviation for titanium?

On that note, does the direct USB cable work with the 89Ti on linux now? That would be nice.

Yes, tm means titanium.

Directlink USB works with the 89T on Linux now with later versions of libusb, although the support is still not very good due to a firmware bug within the 89T itself.

Later versions of libticables2/libticalcs2 actually (like the ones released together with TiLP 1.04 and TiEmu 3.00). The libusb version should be irrelevant.

I don't know exactly what version of libusb I have, but it's whatever came with Slackware 11. SilverLink doesn't seem to work - I haven't tried DirectLink, GrayLink worked once I set all the permissions right. I'm upgrading my libusb to see if that fixes the problem.

You need to make some udev settings in order to get USB to work, unfortunately I do not know what settings you need for Slackware to get USB linking to work.

Well, it's just permissions, so if he got GrayLink working, he should get SilverLink working too...

Of course, Slackware ships old, possibly buggy software...

I'm going to switch to Fedora 7 - have been disappointed with some of Slackware's features. Since you're a Fedora person, I should be able to get better support :)

Has anyone else had problems with TiLP2 for Windows XP (Service Pack 2)? I can click "Have Disk" and select the .inf file in the TiLP program directory, but it tells me that that "the specified location does not contain information about your hardware." All of the files that the TiLP2 setup are in the same directory. I'm using a TI-84 Plus (OS v2.41) with the USB cable that came with it.

Any suggestions?

Um... it looks like the inf file doesn't include the VID/PID for the TI-84+, only the SilverLink, 84+SE, and 89Ti.

You're right, there is no VID/PID for TI84+. I'm about to update driver...

HMA, I need to know the VID/PID of the TI84+. Could you go to Control Panel > System > Hardware > Device Manager, right-click on found hardware > Properties > Details tab. You should have a line such 'USB\VID_0451&PID_E00?\...'. Send it to roms AT tilp DOT info.

Romain, we know it already!

# This file was installed by the libticables2 Fedora package.

# SilverLink
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0451", SYSFS{idProduct}=="e001", SYMLINK+="ticable-%k"
# TI-84+ DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0451", SYSFS{idProduct}=="e003", SYMLINK+="ticable-%k"
# TI-89 Titanium DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0451", SYSFS{idProduct}=="e004", SYMLINK+="ticable-%k"
# TI-84+ SE DirectLink
ACTION=="add", SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0451", SYSFS{idProduct}=="e008", SYMLINK+="ticable-%k"

Moreover, I realized there were in the ticables2 library header! The Win32 USB driver was simply not up-to-date.

This has been fixed and new release have been upload in the ticalc.org archives.

HMA92: if you does not want to wait for driver update, open the tiglusb.inf file and add this line in the [DeviceList] section:
%DeviceDesc%=TIGLUSB.Dev, USB\VID_0451&PID_E003

thx!

Thanks for all the help!
Editing the INF file worked perfectly, and TiLP is now recognizing my calculator.

Note that the libusb code was also missing the device ID for the non-SE TI-84+. This is fixed in libticables2 1.0.6 which is available (as binary and source RPMs) from my Fedora repository at CalcForge. The source tarball is still pending at ticalc.org though as far as I know.