i am using usb.
i am using usb.
I removed all and started with a clean install of wine 1.2 then used winetricks to install dotnet 1 and 2. Reisntalled evoscan 2.5 and ecuflash.
For the first time ever the tactrix drivers installed without errors! I setup the symbolic link for wine to see my usb cable as a virtual com, but still no luck...
However I feel more confident I am closer to making this work :)
sorry i haven't been trying much lately. I have been assembling a megasquirt and last weekend I went down to the rally-america event in missouri :rock:.
Anyway, i am not sure that getting the windows driver installed should solve anything. Windows drivers are useless to wine. It just seems like evoscan is only searching to see if the ftdi drive is loaded and then gives up. Although I don't know much about the inner workings of a dotnet program or the wine API, I think the answer lies in first fooling evoscan into thinking that the ftdi driver is loaded, and then redirecting communication to the already driver-ed com port.
There are already a few problems with ftdi drivers in wine like this: http://bugs.winehq.org/show_bug.cgi?id=8783
Maybe if we do some more digging on less specific ftdi problems in wine, we may find a bit of an answer.
I also wonder if a driver wrapper like they use with ndiswrapper could be an answer. I had read a few years ago on progress towards using a more general wrapper for any windows driver -- not just ndis wireless drivers.
also, check out this page (a bit older): http://wiki.jswindle.com/index.php/Drivers
at the risk of flooding, also check out this link: http://wiki.winehq.org/USB