by jon3929 » Wed 10.09.2008, 19:58
Well I have done it......
As suspected it was a process issue rather than an incompatibility or something more serious.
I used the same VCP drivers as for XP and the file that ultimately enabled the device was called "ftdibus". Before starting I unzipped all the files onto my desktop asI had no success in getting Vista to searh folders, the files needed to be fully exposed and I just used my desktop for ease.
Here's how i think I did it:
1. When the elanscan interface is first plugged it, it appears as "elanscan interface" but as an "other device" not a port .
2. Right clicking and selecting the driver tab reveals it has no drivers allocated.
3. Following the process to assign a driver, select the manual method under "browse my computer"
4. Then select "let me pick from a list" option
5. Then select the "have disk option"
6. Then select the browse for file option.
7. At this point it is looking for a *.inf file which is not correct
8. Delete the file extension
9. Then select Desktop and it automatically selected the driver file "ftdibus"
10. Select ok and it says the driver has been successfully configured.
HOWEVER - it hasn't.
11. When looking again at the device in the device manager, it now shows Elanscan as a COM PORT, but also showing a yellow exclamation mark indicating a fault, and without a com port number.
12. Repeat exactly, the process from 2-10 above and reassign the driver for a second time.
13. Again it will say the driver has been successfully configured.
14. Checking in the device manager, it now shows the device as a COM PORT and mine defaulted to "COM PORT 13".
I then could set the latency timer to 1 (because it now recognised the device as a comms port), and then set Elanscan to communicate through port 13.
Lo and behold it communicated perfectly and works a treat.
Its nice to actually be able to put up something useful rather than just ask questions. Hope this is useful to others.....
cheers, Jon.