Yes, it would be best if *nix-using beta-testers ran install_tilp.sh "often"

That said, at the moment, I don't make commits every day, and Windows changes are of no use to *nix users.

Exactly

And a new refresh of the installer
* 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

There have been four minor changes in the code since the previous build; the README.win32 has been modified to include information on installing the filter driver (reproduced below); and most of all, the GTK+ runtime download & install procedure has been completely revamped. It's now fully integrated into the installer, which has three consequences:
* users have visual feedback on what's going on;
* the procedure is much more reliable;
* it reduces the installer's size, and increasing the compression level decreases the size even further: the installer is now only half as big as the previous build


Excerpt from the updated 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).

Well, please be more precise, starting with the OS version (even if I know from another topic that you're probably running 7 x64, otherwise you wouldn't have had to disable the driver signature enforcement with older versions of TILP) and a longer description of the "insta crash" ?

Some issues to report:

1) On the SourceForge download page, the ZIP I got for the Windows latest version is corrupted. I tried opening it with the native (Windows) ZIP opener on XP, and it didn't work. Then I tried my magical 7zip (the open-all archiver), and it said that it couldn't open it as a archive.

http://sourceforge.net/projects/tilp/files/tilp2-win32/tilp2-1.15/tilp-1.15.zip/download

2) When trying out your link above to your new installer, my lovely Norton Antivirus/Internet Security software blocked the download!
(Well, it downloaded, then the scanner went to scan it, and then it called it a "threat" and deleted it. )

I know you guys aren't malware authors, nor do you guys bundle malware with a FOSS program.
You should go to Synmantec (Norton's company) and request that the program be removed from the "bad" list.
I'm not a security expert, so I'm not too sure if it's just a database that they use, or if it's a bit more universal (whether it belongs to them or they source it from a main DB).
Make sure to ask them about that! If it's universal or shared, ask if the removal automatically spreads out. If not, also ask which companies to contact to remove your binary from the list.

It seems that this is a "community-reported malware" - it does NOT match any specific virus definitions.
I've pasted the security software log of the removal below. (And yes, it's not name specific - first time I named it tilp_setup.exe, it rejected it. Then I just left it at setup.exe when downloading/saving again, and it still rejected it. Probably a SHA/MD5 match.)
Full Path: c:\documents and settings\albert\my documents\tilp_setup.exe
____________________________
____________________________
On computers as of:
8/20/2011 at 11:49:22 AM
Last Used:
8/20/2011 at 11:49:21 AM
Startup Item:
No
Launched:
No
____________________________
____________________________
Very Few Users
Fewer than 5 users in the Norton Community have used this file.
____________________________
Medium
This file risk is medium.
____________________________
Threat Details
Threat type: Insight Network Threat. There are many indications that this file is untrustworthy and therefore not safe
____________________________
Origin
Downloaded from  http://lpg.ticalc.org/prj_tilp/beta/setup.exe
http://lpg.ticalc.org/prj_tilp/beta/setup.exe Downloaded File tilp_setup.exe
(WS.Reputation.1) from: ticalc.org


tilp_setup.exe
____________________________
File Actions
File: c:\documents and settings\albert\my documents\tilp_setup.exe
Removed
____________________________
File Thumbprint - SHA:
4638cb5c3fd0be3d5e0187955f68f36bcba64bf7817c079052b7cfe1a51fc161
____________________________
File Thumbprint - MD5:
dfcdff1d389271e405ec2717efff3fba
____________________________

3) Regarding the filter driver installation - I'm not too sure how you guys handle device driver installation (that is, TI-Connect is NOT installed, so your installer would detect that and proceed to install the libusb device driver for the possible USB configs for calc connectivity), but I think you can possibly make the filter driver installation automatic. In the libusb distribution (the ZIP file), bin\x86 contains "install-filter.exe", which is the CLI version of the wizard you mention (which is "install-filter-win.exe"). If you have created INF files for the device driver installation, I think it might be possible to use that same INF file for filter driver installation. You just need to include the libusb distribution, select the appropriate arch., and then run the "install-filter.exe" with proper arguments at the end of install. Of course, I have no idea if you guys even install a driver or not due to the reason above (terrible security software), so I apologize in advance if this doesn't make sense!

Usage of "install-filter.exe":
WARNING:
  Improper use of libusb-win32 install-filter can cause devices to
  malfunction and in some cases complete system failure.

DISCLAIMER:
  THIS SOFTWARE IS PROVIDED IN AN "AS IS" CONDITION. NO WARRANTIES,
  WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED
  TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
  PARTICULAR PURPOSE APPLY TO THIS SOFTWARE. THE ORGANIZATION SHALL
  NOT, IN ANY CIRCUMSTANCES, BE LIABLE FOR SPECIAL, INCIDENTAL OR
  CONSEQUENTIAL DAMAGES, FOR ANY REASON WHATSOEVER.


USAGE: install-filter [install|uninstall|list] <-ac> <-dc> <-ad>
                                               <-c=> <-d=> <-f=>
                                               <-p=> <-w=>

Commands:             Compatible Switches:
  install   (i/-i)      <-ac> <-c=> <-d=> <-f=> <-p=> <-w=>
  uninstall (u/-u)      <-ac> <-c=> <-d=> <-f=> <-p=> <-w=> <-ad>
  list      (l/-l)      <-ac> <-dc> <-c=> <-p=> <-w=>

NOTE:
  * If no switches are specified, the default class key list is used.
  * 64bit OSes must use the 64bit version of this application.

Switches For Class Filters:
  --all-classes         (-ac)
    install  : Adds libusb-win32 as an upper class filter for all
               classes in the USB enumerator. (Same as -dc in install mode)
    uninstall: Removes libusb-win32 as an upper class filter for all
               known classes.  This is a FULL class removal.
    list     : Displays all known classes.

  --device-classes      (-dc)
    install  : Adds libusb-win32 as an upper class filter for all
               classes in the USB enumerator.
    uninstall: Removes libusb-win32 as an upper class filter for all
               classes in the USB enumerator.
    list     : Displays all classes in the USB enumerator and the devices
               contained within them.

  --class=<nameOrGuid>  (-c=)
    install  : Adds libusb-win32 as an upper class filter for the
               specified class only.  Classes can be specified by name or
               guid.
    uninstall: Removes libusb-win32 as an upper class filter for the
               specified class only.  Classes can be specified by name or
               guid.
    list     : Displays information about the specified classes and the
               devices contained within them.

Switches For Device Filters:
  --device=<hwid>       (-d=)
    install  : Adds libusb-win32 as an upper device filter for the
               specified device.
    uninstall: Removes libusb-win32 as an upper device filter for the
               specified device.
    list     : <NA>

  --all-devices         (-ad)
  install
    install  : <NA>
    uninstall: Removes libusb-win32 device filters from all devices in the
               USB enumerator.
    list     : <NA>

Switches For INF Files:
 --inf=<your_file.inf> (-f=)
    install  : Installs usb device(s) from an inf file.
    uninstall: Attempts to roll back a device driver installation. If
               rollback fails or is unavailable, the device is removed and
               all root hubs are restarted.
    list     : <NA>

Common Switches:
 --prompt=<your_prompt_string> (-p=)
   Prompts the user with the specified string before running. To include
   spaces in the prompt string, place the entire switch in double quotes.
   Example: "-p=Are you sure?"

 --wait=<your_wait_string>     (-w=)
   After the operation completes, displays the specified string and waits for
   user input. To include spaces in the prompt string, place the entire
   switch in double quotes.
   Example: "-w=Press any key.."


Examples:
  install-filter install --device-classes
  install-filter uninstall --all-classes
  install-filter list --device-classes
  install-filter install --class={00000000-0000-0000-0000-000000000000}
  install-filter install "--device=USB\Vid_04d8&Pid_000c&Rev_0000"
  install-filter install --device=USB\Vid_04d8.Pid_000c.Rev_0000
  install-filter install --inf=your_file.inf

Unable to execute file:
C:\Users\olivier\AppData\Local\Temp\is-3PC28.tmp\gtk-2.12.9-win32-2.exe

CreateProcess failed; code 740.
The requested operation requires elevation.

Runing the gtk installer manually from temp fixes that. It seems that the administrator "right" isn't passed on by the Tilp installer.

Else it seems to work as it should.

btw I'm on w7 x64

@runeazn: well, I haven't seen this behaviour myself, and the other people in this topic don't seem to have seen it (on older versions, at least). I'll try to reproduce it...


@alberthro:
1) Thanks for the report.
At least one of the files used to be invalid, but I thought I had uploaded a fixed file... Maybe the one I uploaded on ticalc.org is better. Anyway, you have already found the newer beta in this topic

2) Ah, the joys of false positives produced by the defective products of the highly lucrative AV software industry scam / circus...
Looks like some members of the AV industry scam allow random people to indicate that a piece of software (at that, one generated under Linux by a cross-compiler and assembled by InnoSetup running in Wine...) is malware, without screening the results. Why would they trust anyone - even a maintainer - to indicate that the report is incorrect, as far as he knows ? Authors of genuine malware (the one that only at best 20% of AV software can detect - over the years, I've fixed a number of computers of relatives that were struck despite the presence of various AV software made by various members of that bunch of crooks...) could do exactly the same with their products, since the AV vendor evidently doesn't check the results.
It's like the no-fly list: it's very easy to be put in it, but it's nearly impossible to get out...


3) Well, automatic installation of the libusb filter driver is not recommended by its authors, so I'd rather not go that route
At least, not for TILP II 1.16, all the more it may indeed increase the AV false positive rate even further (I had never thought of that downside of embedding the filter driver installer, but since you mention it...).

could you replicate it?