"much better interoperability with TI-Connect"I believe he means files retrieved using TI-Connect can be sent using TiLP and vice-versa.
Does this mean both of them will work simultaneously?
EDIT: note, for newer members over here, I am talking about the TI-Graph Link software, not the cable. It was basically TI-Connect's ancestor back in the late '90s until 2001, but also included a program editor.I'm new, but at my school we have three things for calcs: Ti Connect to transfer, Ti Flash Debugger to emulate, and Ti Graphlink for a program editor. (I'm not sure where I'm going with this, but I figured I'd show that it's still being used.)
any reason/need to test with x64 windows seven ?Yes :)
Does this version allows to keep both TI-Connect and Tilp installed? (I think since they use different drivers, it is not very viable)No, not better than the previous versions, because Windows doesn't like having two drivers for the same thing, AFAIK.
And it would be great if tilp accepted all the versions of group file that DJ wrote about.I agree on the principle, but I feel that this kind of new features is post-1.14 stuff ;)
...
2) Keeping a computer at home that has Windows installed. I'm not going to completely switch to Linux, because I keep hearing people complaining that they cannot find softwares for what they want to do under Linux, or they're very buggy. As I also play online games sometimes, Wine may not always be reliable *cough*Starcraft BattleNET*cough*. Another issue is that certain Windows programs don't run properly in Wine, such as RPG Maker database editor menus (I forgot which version of RPG Maker. I would need to ask Tribal).
...
on a side note about the http://www.blogsdna.com/2775/install-unsigned-drivers-on-windows-7-vista-with-driver-signature-enforcement-overrider.htm the program on this makes a annoying test mode thing in the bottom corner and is also a pita to get working at first it takes a lot of patience as you have to disable safety checks then reboot
...
but will instructions on how to get it to work on most new Windows installs be included? For example, my new comp has Windows 7 x64 so I will obviously have trouble with drivers since I never dealt with this before.Yes, such instructions will be included :)
Btw, for GTK+, will we be able to continue using TiEmu, TilEm and GIMP when TiLP is installed?TheStorm / Jonimus recently reported success launching TILP with GIMP's GTK.
The USB romdump is excellent. Now many people can get their roms.Yeah, we have to thank Brandon for this.
I wonder if future versions of Ndless will actually have support for TiLP.Yes, though it can somewhat depend on which kinds of operations are attempted to exploit flaws in them.
Thanks :)Wow, that is pretty obscure bug :O You are a pretty pro bug finder :D
EDIT1: I'm completely at loss about the reasons why the calculator refuses this particular file (even if renamed to let only one dot in the filename), while it accepts just fine e.g. a 1.3 MB TI-68k OS file (renamed to have a .tns extension, with or without multiple dots in the filename) !
EDIT2, 10 minutes later: this file is 32812 bytes, and it won't transfer. If I make it 32813 bytes, it transfers. If I make it 32811 bytes, it transfers. Very interesting.
EDIT3, 5 minutes later: the same behaviour happens with files containing all zeros: 32811 and 32813 bytes work, 32812 bytes doesn't work. Therefore, it seems that TILP (the underlying libraries, actually) somehow doesn't like this particular size. Now to find the periodicity of the size problem, if any.
EDIT4, more than half an hour later:So there's a problem with files whose size modulo 253 is 175. And I don't know why yet.
- files of 32554-32558 and 32560 bytes work, 32559 bytes doesn't work. 32812-32559=253=maximum size of a packet-1. 32559-253=32306 bytes doesn't work either.
- 32812 mod 253 = 175. Files of 174, 176, 427 and 429 bytes work, while files of 175 bytes and 428 bytes don't work.
(on Ubuntu 10.04, if that might help)The script has been reported multiple times to work with Ubuntu 10.04 :)
The terminal appears VERY briefly (with nothing displayed inside it)This is very weird, because the script precisely starts by printing 5 lines to the terminal (the 5 echo -e after handle_one_module()), and then waits for the user to press ENTER.
Do I have to change something inside to make it work?Nope, no modification inside the script is required for the script to work :)
BTW, when you talk about build dependencies, do I need to install those before running the script?Yes, as noted in the script and the pages on the LPG site :)
diff --git a/tilp/trunk/build/InnoSetup/tilp2.iss b/tilp/trunk/build/InnoSetup/tilp2.iss
index 35972b1..d631bdc 100644
--- a/tilp/trunk/build/InnoSetup/tilp2.iss
+++ b/tilp/trunk/build/InnoSetup/tilp2.iss
@@ -117,6 +117,7 @@ Source: "C:\lpg\tilp2\RELEASE"; DestDir: "{app}"; DestName: "Release.txt"; Flags
; Binaries
Source: "C:\lpg\tilp2\build\msvc\tilp.exe"; DestDir: "{app}"; DestName: "tilp.exe"; Flags: ignoreversion
+Source: "C:\lpg\tilp2\build\msvc\gfm.exe"; DestDir: "{app}"; DestName: "gfm.exe"; Flags: ignoreversion
[Dirs]
Name: "{app}\My TI files"; Flags: uninsneveruninstall;
@@ -136,6 +137,7 @@ Name: "{group}\Bug Report"; Filename: "http://sourceforge.net/tracker/?func=add&
Name: "{group}\USB driver installation"; Filename: "{app}\help\usb_driver.html";
Name: "{userdesktop}\TiLP"; Filename: "{app}\tilp.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks: desktopicon
+Name: "{userdesktop}\GFM"; Filename: "{app}\gfm.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks: desktopicon
Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\TiLP-2"; Filename: "{app}\tilp.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks:
[Run]
diff --git a/tilp/trunk/build/InnoSetup/tilp2_cross.iss b/tilp/trunk/build/InnoSetup/tilp2_cross.iss
index a40f3ea..962da10 100644
--- a/tilp/trunk/build/InnoSetup/tilp2_cross.iss
+++ b/tilp/trunk/build/InnoSetup/tilp2_cross.iss
@@ -119,6 +119,7 @@ Source: "C:\tilp\tilp\trunk\RELEASE"; DestDir: "{app}"; DestName: "Release.txt";
; Binaries
Source: "C:\lpg\packages\bin\tilp.exe"; DestDir: "{app}"; DestName: "tilp.exe"; Flags: ignoreversion
+Source: "C:\lpg\packages\bin\gfm.exe"; DestDir: "{app}"; DestName: "gfm.exe"; Flags: ignoreversion
[Dirs]
Name: "{app}\My TI files"; Flags: uninsneveruninstall;
@@ -138,6 +139,7 @@ Name: "{group}\Bug Report"; Filename: "http://sourceforge.net/tracker/?func=add&
Name: "{group}\USB driver installation"; Filename: "{app}\help\usb_driver.html";
Name: "{userdesktop}\TiLP"; Filename: "{app}\tilp.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks: desktopicon
+Name: "{userdesktop}\GFM"; Filename: "{app}\gfm.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks: desktopicon
Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\TiLP-2"; Filename: "{app}\tilp.exe"; WorkingDir: "{app}\My TI files"; MinVersion: 4,4; Tasks:
[Run]
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.--- 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;
Which DLL is missing for you ?It says libticalcs2-10.dll is missing from my computer.
install_tilp.sh automatically updates files from SVN (soon Git), then compiles them :)
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).
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
____________________________
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:Runing the gtk installer manually from temp fixes that. It seems that the administrator "right" isn't passed on by the Tilp installer.
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.
@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...).
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) ;)
[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 :)
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).
Just saying that everything is fine here (w7 64)Good, thanks :)
I just saw one "thing": the OS version of my CX is after Tilp 3.2.1793 instead of 3.0.2.1793 which is a little confusing...Agreed, it's a bit confusing - but 3.2.1793 is a mere dump of what the calculator returns when asked for its information :)
I mean 3.0 != 3.2 :huh:
Refreshed the installer again :)
* binary: http://lpg.ticalc.org/prj_tilp/beta/setup.exe
* patches: http://lpg.ticalc.org/prj_tilp/beta/0001-tilp-installer-upgrade-dependency-on-GTK-runtime-to-.patch , http://lpg.ticalc.org/prj_tilp/beta/0002-libticables-tilp-update-driver-information-improve-t.patch
The older installer (the one posted in my previous post) is http://lpg.ticalc.org/prj_tilp/beta/setup_old7.exe .
The main highlights since the previous beta are:
* added .8xo file support. In fact, these files were already supported, but called "8xgrp" :)
* added MIME types definitions;
* added tentative Nspire CM (CAS) OS upgrade support (untested);
* upgraded the embedded minizip;
* improved drag&drop code by Jonimus/TheStorm: TILP can now accept drag&drop from more programs.
* the usual set of fixes for (potential) crasher bugs, plus a huge pass of argument sanitizing in libti*, which have become much more robust against NULL arguments. Several bugs were found by using the clang-based AddressSanitizer compile-time instrumentation tool to build everything.
* ROM dumping of 84+(SE) and 89T through DirectLink was fixed, and so were computer->calc transfers to 84+(SE) of files of size 244 modulo 250 greater than 244 bytes through DirectLink. The corner cases for sending and receiving files from 89T through DirectLink, and receiving variables from 84+(SE) through DirectLink, seem to keep working;
* fixes for driver install paths that ought to alleviate the problems mentioned above by Deep Thought.
The usual excerpt from README.win32 for installation alongside TI's official software:Quote1°) 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).
patches from where?From the tarball, http://lpg.ticalc.org/prj_tilp/beta/patchset_20120724_1510.tar.bz2 :)
aren't the patches in your last post just for the windows docs?Nope. My mention of "user documentation" was a description of one of the reasons why these patches are not committed yet (the documentation hasn't been fully updated), not what these patches are :)
IOW, the .inf files need adjustment. Thanks for the report :)It may not make a difference, but I would lean towards changing the installed filename rather than changing the inf file.
-A built-in TI-84 Plus C Silver Edition ROM dumper that supports direct USB linking that is also failsafe from any computer CPU spikes (unlike Jonimus' silverlink dumper)The modified DBUS (legacy I/O) and DUSB (DirectLink) ROM dumpers are in my mailbox, I need to apply them (and another, prerequisite patch from Benjamin) :)
-The ability to get a screen capture while in 160x240 resolution mode. TI-Connect only works in 320x240 mode (in 160x240 it says "Error getting screen shot").I definitely see why that would be useful, but I'm unsure we could implement that out of the box:
An assembly program is about to be sent on your calculator.
If you have not made a backup yet, you should do one before
proceeding with ROM dumping...
For the way of proceeding, take a look at the TiLP manual
(especially if you have a USB cable).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.
the lack of a working silverlink OS senderElaborate, 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.
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.
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).
That way, you could use the same frontend for several different backend programs that could function entirely differently for linking purposes.... within some bounds. Nspire support already stretched the envelope of TILP. If the models are too wildly different (the TI-Z80, TI-68k and Nspire series probably weren't), shoehorning support for them under a grand unified interface may prove hard.
Crazy thought: (And I mean REALLY crazy) A libti-based FUSE plugin for linux, so you could simply copy programs and variables over. The plugin would handle allocating the VAT correctly, making sure everything's in place.Making a FUSE plugin for TI calculators is an old idea :)