This is an early version of SquidgeLink. It currently does not support the View, Edit & Move functions, and drag 'n drop functionality has been removed from this version. The copy function does not copy directories in this version either - only files. 

To install: Copy the two files starting with "Squidgelink" to a directory of your choice, and run the executable from there. 

To uninstall: Delete the directory you created in the install phase :)

To use: 

Load the software, connect usb lead and load pc link on your GP32 (in any order). Squidgelink will detect the presence of a GP32 as soon as it is connected and switched on. This state will be displayed to you by the word "Connected" showing in the bottom right of the window. If shows "Disconnected", then ensure GP32 is powered up, lead is connected firmly, and drivers are installed (the drivers do not need to be the ones included in this archive, although these have been tested and work very well on the compatible operating systems specified).

Before sending any commands to the GP32, ensure the a PC Link program is running on the Gp32 itself. Squidgelink is compatible with the original PC Link, so will work with the original BIOS, MultiFW2, PacRom,
Windups, etc. 

Running on WinXP and Squidgelink doesn't like your Windows theme? Although it tries to be consistent, it is possible for it to fall over. In these cases, simply delete or rename the "Squidgelink.exe.manifest" file. This will cause it to run without themes. 

Troubleshooting:

There is still quite a bit of error checking to implement, so if, for any reason, you obtain link errors or timeouts, the best way to get around them is to restart the link software on both ends of the connection. There is no need to disconnect the cable. 

Blue screens: If obtain any blue screens whilst using this software, then the drivers you are using are not fully compatible, and it's recommended you use the drivers supplied (Only if your OS is Win2K, XP or higher however). The drivers need to fully support overlapped I/O, and there are some out there that do not, which causes faults in the drivers when requested to do so. These faults will either cause scrambled data to be transmitted/sent, or the dreaded BSOD. 

Benchmark tests: All benchmarks were carried out using a 9.8mb file using Dark Faders PC-Link via MultiFW2. 

App            PC Link Host 1.3.2      SquidgeLink0.2       SquidgeLink0.3
==========================================================================
Read KB/Sec    48                      51                   54    
Write KB/Sec   74 / 115                81                   115 / 220 *
CPU Usage %    99                       2                   5
==========================================================================
* - second number (if present) denotes actual writing speed. First number includes time taken to update the SMC. 
A Read is from the GP32 to the PC. A Write is from the PC to the GP32. 
