Refreshed again.
* binary: http://lpg.ticalc.org/prj_tilp/beta/setup.exe
* patches: http://lpg.ticalc.org/prj_tilp/beta/0001-libticables-tilp-installer-upgrade-libusb-win32-and-.patch , http://lpg.ticalc.org/prj_tilp/beta/0002-tilp-installer-download-GTK-runtime-directly-from-th.patch , http://lpg.ticalc.org/prj_tilp/beta/0003-tilp-installer-upgrade-dependency-on-GTK-runtime-to-.patch

Three minor changes in the code, fixed the GTK+ runtime installer launch to run as administrator (reported by shrear above) and the GTK+ runtime version has been upgraded to 2.22. This change is not mandatory right now, but it will soon become mandatory.

The older installer (the one posted in my previous post) is http://lpg.ticalc.org/prj_tilp/beta/setup_old6.exe .

Excerpt from README.win32:

1°) It is possible to install TI-Connect(tm) / TI-Nspire Computer (Link) Software(tm)
and TILP side by side, but this requires a manual configuration.
The following steps assume that TI-Connect / TINC(L)S is already installed:
* download the filter driver installer and install it, using the instructions given at
  http://sourceforge.net/apps/trac/libusb-win32/wiki , section "Filter Driver Installation";
* launch the filter wizard (accessible from the new entry in the Start menu) when the
  device (SilverLink, 84+, 89T, 84+SE, Nspire) you want to use with both TILP and
  TI-Connect / TILP and (TINCLS or TINCS) is plugged *in*;
* install the filter driver for that particular device;
* run the TILP installer.
After that, the device ought to work in both TILP and TI-Connect / TILP and (TINCLS or TINCS).

So you didn't fix incompatibility issue with win 7 x64?

There is no "incompatibility", since it worked for shrear on 7 x64 (and a slightly older build worked for me on 7 x64 as well)

I don't know why it crashes so early for you. It's not easy for maintainers to debug problems that they cannot reproduce, you know
Please post the contents of the .tilp.log file that you'll find in your home folder (normally one level above My Documents, in Documents and Settings).
A more advanced help would be to install MSYS with a GDB, run TILP from that GDB (which is not entirely straightforward) and provide a backtrace when it fails. That's how I pinpointed a problem outside of the code of TILP lately.

Your home folder: even on Windows, users have a home folder
I don't have 7 or XP booted at the moment to check, and I'm going to bed anyway, but IIRC, the home folder is C:\Documents and Settings\<your username>.

Indeed, but isn't one is a symlink or junction to the other one ?

[edit]it is possible with your current non beta stable build to use ti nspire linking software, which i do.

No, unless you install the filter driver - which you did
Only the very latest libusb-win32 versions will work (>= 1.2.4.8 ), because the patch that I contributed, after discussing with the maintainers, went in for that release.

Have you displayed hidden files in your home folder ?

[EDIT: prevent silly smiley.]

Hmm, why are you replying that way ? My messages are not aimed at making you believe that I don't believe you !
If the fact that the 1.16 beta does not work for you (while it works for shrear and myself) didn't matter to me, I wouldn't try to understand what the problem is by asking you for a file that should be on your computer
And I have understood your "I just installed filter and skipped the beta build working perfect now ty " line, you know.

So please cool down

Avira gives also now a false positive
"TR/Siscos.dgt" <- whatever that means...
(to the credit of the AV, it's easy to add exception.)

Other thing, is it possible to prevent the console window from opening?
Because I always confuse it in the toolbar with Msys (icon is the same),
and that's kind of annoying.

I'm afraid I haven't yet fully adapted the installation procedure to the newest libusb-win32 versions, and the attempt at making it possible to install the 32-bit libusb and the 64-bit libusb alongside each other doesn't seem to be perfect...
Remind me which flavor and version of Windows you're using, and whether it's a 64-bit edition ?