After much playing around - I have finally managed to find a Linux version that will run it!
What I did:
Install QEMU: sudo aptitude install ubuntu-virt-server (for Ubuntu 10.04 - vary for your distribution).
Download KNOPPIX_V3.3-2004-02-16-EN.iso. This is *very* hard to find. The important piece of magic is that it is running a 2.4 generation kernel (2.4.24-xfs, in particular). Knoppix 3.4 is too recent.
Download setupfw160.bin. Get the one with Java in it.
Create a "disk": tar cf fw.tar setup160fw.bin /bin/bash <-- The /bin/bash is in there to pad out the file, as only full 4K pages will be mapped when we use this as a disk. I don't know if that is necessary or not.
Figure out the USB device ID: lsusb. You are looking for two four-digit hex numbers, the first of which is 0e97. For example, my TouchStream ST/LP is 0e97:090b
Boot the CD: sudo qemu-system-x86_64 -m 2048 -cdrom KNOPPIX_V3.3-2004-02-16-EN.iso -sdl -usb -usbdevice host:0e97:090b -hda fw.tar
Notes on the above:
You probably don't need to use the 64bit qemu
-m 2048: 2GB RAM. Way more than necessary.
-hda fw.tar: you can instead set up networking
After X has started in the VM, you should be able to interact with the VM using the Fingerworks keyboard. The Fingerworks Keyboard will *not* work in the host anymore - So make sure you have another keyboard/mouse!
In the VM: sudo tar xvf /dev/hda
In the VM: chmod a+x setupfw160.bin
In the VM: ./setupfw160.bin. Install to the default location. Use the Java provided by the Fingerworks installer, not the system one.
In the VM: ./FingerWorks/MultiTouch_Utilities
After shutting down the VM, you will have to re-plug the Fingerworks keyboard to get it to be re-recognised by the host O/S.
If you want to copy an .xml file into the system, add in into your tarball *before* the /bin/bash.
If you decide to set up the VM with Networking, you can of course copy setupfw160.bin that way, instead of creating the tarball and using "-hda fw.tar".
I have not worked out a way to copy a modified .xml file out of the VM - I haven't needed to yet - but it shouldn't be hard. Some method of dumping it back out over /dev/hda would be the easiest, assuming that you, like me, didn't want the hassle if dealing with networking.
Last edited by jarrodl
on 30 May 2010, 19:50, edited 1 time in total.