I don't know how clearly you can see that, but that is my Pertelian fully functional on Windows Vista RTM (released version) 64 bit edition.
The install process was not plain sailing, but it seems to be fixable quite easily.
1) Install the Pertelian Software package.
It asked me if I wanted to install J# Redist runtime. I said no to this, as I know that I have J# already installed, however, the installer detected it as J# 0.0. This is probably due to the J# runtime being installed somewhere else in Vista. ##FIXED 14-3-2007##
2) Download the drivers from here: http://www.ftdichip.com/Drivers/D2XX.htm
The drivers in the pertelian download section did not work, however, the set at the top do work.
I didn't test it with the VCP drivers (I have no idea if they will work or not), but I used this set as the files in there seemed to match the ones supplied by you.
Extract the drivers somewhere.
3) Open up the device manager, find the USB <--> Serial device, right click, update drivers, browse, and give it the location. Wait for it to complete.
4) Wait a while, and it will pop up a box, asking you if you want to install drivers for a USB serial port. Tell it you do, again, browse for drivers, and give it the same location as above.
5) Note down from the device manager the com port used (should say something like "USB serial port (Com5)").
6) Close the pertelian client (if it is running) and then open the start menu, all programs, pertelian.
7) Right click the pertelian executable, select properties.
Select compatibility
9) Select run this program as an administrator.
10) Click OK.
11) Reopen the pertelian client, and set the com port. Click connect. You are now working. However, due to pertelian requiring admin permissions, it must be started manually every time the computer boots.
---
Steps 7 to 10 can be eliminated, with an update to the pertelian client.
The vista security model makes programs unable to write to the program files directory by default. This means that config files cannot be saved, hence why you need to at this time run the client in administrator mode.
To get around this, the application needs to be adapted so it somehow gets permission to write to program files, or (probably simplest) save the config file in the users home directory (probably a better idea anyway).
This also needs to be addresses as programs requiring administrative permissions cannot be automatically run on boot.
Also, while not running in administrator mode, the pertelian unit crashes when you exit (the screen freezes and keeps whatever data is on it, and if you repopen the pertelian client, it cannot connect until the unit is physically disconnected and plugged back in.).
If you have any questions, or want me to run any tests, feel free to PM or email me.
I'll add any plugin issues I find as I find them. The network speed plugin seems to be working fine though
