Necro bump for good reason

I'll have to try this sometime. I'm sure people have asked this before, but should I completely uninstall TI-Connect first?

Last time I tried to do that I found I'd accidentally deleted TI-Connect uninstall software. Half an hour of nerve-wracking manual registry editing (nearly deleted OS files, too)

Oh thanks, I guess that would explain why I never got TiLP to work.

EDIT: Do you know how to do that in Vista?

I have now released TILP II 1.15
Packages are in the process of being uploaded to ticalc.org.

It's a significant new release. Excerpt from the release notes:
New capabilities:
-----------------

- tilp: improved UI, by Jon Sturm (Jonimus / TheStorm).
- tilp: use more native, themable icons.
- libticables: libusb 1.0 backend, for users of the many Linux distros which don't package libusb 1.0 proper anymore.
- libticalcs: OS 2.x and 3.x support, variable deletion, folder creation, folder deletion, OS 1.x dumping.



Improvements:
-------------

- libticables: cope with 84+(SE), 89T and Nspire (CAS) USB controller stacks, which want dummy reads or writes in some circumstances.
  Most of the causes of variables of peculiar sizes failing to transfer have been fixed.
- tilp: compatibility fixes for recent GTK+ versions.
- all: commit MSVC 2008 build files.

Bug fixes:
----------

Between others (see the Changelog files for complete lists):
- all: change encoding in .rc files.
- all: lots of fixes for compiler warnings, memory leaks, crasher bugs
- libticalcs: fix 86 ROM dumping.
- libticalcs: cope with "-1" delays sent by the 84+ when writing to Flash memory, which used to hang (almost) forever.
- libticalcs: Nspire ID retrieval.
- tilp: fix display of files whose size is exactly 1 KB or 1 MB.
- libticalcs, libtifiles: don't crash upon sub-folders of folders (Nspire OS 2.x and 3.x support them).
- libtifiles, libticables, libticalcs: turn abrupt program aborts such as assert() and exit() into tests + ti*_critical().
- libticalcs: fix a declaration after statement.
- libticalcs: cope with martian packets sent by Nspire OS >= 1.7 when replying to a session close packet.
Many thanks again to Jon (TheStorm on this forum, IIRC) for the UI changes and the libusb 1.0 backend

We're currently trying to upgrade the libusb DLL and SYS files for Windows, so as to fulfill the long-standing feature request that TI-Connect + TILP II, and TINCLS + TILP II, become usable side by side.
Status: TI-Connect and TILP II on the one side, and TINCLS and TILP II on the other side, can be made to both work on a given computer without having to uninstall either - in fact, they do so on my father's computer running native Win7 x64
(but I seldom have access to said computer - and in fact, at the time of this writing, it's not here anymore)

For now, it's a manual process (for which I'll try to streamline my rough notes - I think that there are two ways of achieving the effect), but it's certainly going to be possible to automate it into the installer. I need to integrate the updated INF + CAT definitions kindly generated by the INF wizard provided by the newest versions of libusb-win32, and probably add several lines to the TILP II installer. Maybe more changes currently unforeseen, we'll see.


On a side note: for a while (seemingly before I became the maintainer, two years ago), TILP has been (or should have been, because the InnoSetup installer script doesn't reference the modified binary anymore) shipping with an unmodified libusb0.sys binary. As a consequence, TILP II 1.15, and a number of earlier builds, don't work well with Nspires - and testing on the native Win7 x64 computer seems to show that it's worse than on my virtualized XP (where it was more tolerable). Nobody reported it, which shows that people using TILP for interacting with Nspires on Windows are few

Technical details: the reason why a modified binary needs to be shipped, is that the Nspire's USB controller / stack somehow doesn't like the thorough reset procedure sent to it by libusb under Windows. TINCLS sends only the first half of it, and the Nspire is fine with that; but libusb sends the full reset, and after receiving that, something is wrong with the calculator's USB state. It needs to be unplugged and plugged back in...
Romain described the problem in http://sourceforge.net/mailarchive/forum.php?thread_name=473B0743.7020705%40lievin.net&forum_name=libusb-win32-devel / http://svn.tilp.info/cgi-bin/viewvc.cgi/*checkout*/libticables/trunk/src/win32/usb/libusb-win32.html?rev=4162. The corresponding diff is the following:

--- src/driver/reset_device.c.orig      2007-03-20 05:33:29.000000000 -0500
+++ src/driver/reset_device.c   2009-05-07 10:41:28.331560796 -0500
@@ -32,14 +32,14 @@
     {
       DEBUG_ERROR("reset_device(): IOCTL_INTERNAL_USB_RESET_PORT failed: "
                   "status: 0x%x", status);
-    }

-  status = call_usbd(dev, NULL, IOCTL_INTERNAL_USB_CYCLE_PORT, timeout);
+      status = call_usbd(dev, NULL, IOCTL_INTERNAL_USB_CYCLE_PORT, timeout);

-  if(!NT_SUCCESS(status))
-    {
-      DEBUG_ERROR("reset_device(): IOCTL_INTERNAL_USB_CYCLE_PORT failed: "
-                  "status: 0x%x", status);
+      if(!NT_SUCCESS(status))
+        {
+          DEBUG_ERROR("reset_device(): IOCTL_INTERNAL_USB_CYCLE_PORT failed: "
+                      "status: 0x%x", status);
+        }
     }

   return status;

Since it was not integrated at the time, we need to somehow get this patch upstream, under this form or another

Thanks this is the only TI-LP version that i could get to work

ben_g, calcdude84se: thanks, but is the version that works for you TILP II 1.15, or the testing build of 1.16 ?

Thanks

EDIT: 4 p.m. CEST: I have refreshed the installer and the patch, after changing the VendorName attribute in the INF files, so that TI's drivers and TILP's drivers are easier to distinguish. Thanks to JosJuice for the test and report

Thanks for the report.

Even if I shipped gfm.exe in the last beta build for TILP II 1.15, TILP II 1.15 and this testing build, the TILP installer is far from fully integrating GFM. For example, the GFM shipped by the TILP installer is missing three files (you can copy them from an older install: logo.xpm -> pixmaps directory, a couple .glade files -> glade directory), besides the documentation. GFM and TILP, however, use the same DLLs.
Which DLL is missing for you ? If it's a libti* older than libticonv-6, libtifiles2-8, libticables2-5 or libticalcs2-10, then I think that an old version of GFM is referenced (perhaps by the GFM group in your Start menu ? The TILP installer doesn't take care of that group).