Anyone tried ecuflash and supporting tools (evoscan, mitsulogger) on windows xp 64 bit version?

Got a new laptop comming next week, turion 64 cpu, does not have xp64 loaded yet and don't want to go to the trouble if the tools won't run.

 

I'm pretty sure all 64 bit cpu's will run 32bit programs. So you shouldn't run into any problems.

 

Not sure about EcuFlash, but the logging tools are mostly written with .Net so you should expect them to work.

ECUFlash should also work as well, but I can't say for sure.

 

The loggers should work no problem because of the .NET stuff.. Its the drivers that are where there's concern, the ECUFlash app itself should actually work though.

 

Actually.. Mitsulogger should work because .NET 2.0 is definitely available on 64 bit Windows OS's.. I don't know if .NET 1.1 is though, which means there could be some trouble with Evoscan.

 

Certainly not. Consider Itanium or Alpha.

d

 

True, maybe not natively but there is always emulation

 

I haven't tried it (no x64 machine at home) but I doubt that EvoScan works on 64 bit because of its dependency on 1.x.xxxx of .Net which does not exist for 64 bit Windows (.Net 2.0 or greater is available though).

32 bit programs run under a special "emulation" mode on 64 bit windows OSes called WOW64:

http://en.wikipedia.org/wiki/WOW64

 

I'm actually curious about it now.. My code was written to be flexible, but I think you'd be at the mercy of driver support.. I looked at the FTDI Driver package for ECUFlash and don't recall seeing any 64 bit native drivers.

 

Malibujack's right. The big difficulty is assuring that the drivers work. FTDI does provide 64bit windows drivers.

http://www.ftdichip.com/FTDrivers.htm

The linux drivers certainly build in 64bit mode so there's probably not a big deal there. I don't know what will appen with the brand new intel macs (as of three days ago) that re 64bit. The ppc64 macs should work with the regular OS X driver.

I'm reasonably confident that I could make make ECUflash build in 64bit mode on either OS X or linux.

d

 

O.K.,
Some good points raised here. So the main issue I have run into in the past with XP64 is that many installers will not run unless they are written to support xp64. ALso, the drivers, if there is no driver support for xp64 you are kinda hosed.

I do have a dual core athlon 64 running XP64 for my desktop at home, but I am very hesitant to try to install EcuFlash. I run several vmware machines for all of my day to day needs (newsleacher, msoffice, gentoo linux, vpn machine for work, etc etc) in order to keep my base os clean, got real tired of rebuilding my rig every 6 months.

I suppose I can build a xp64 virtual machine and try the installs there first and see if it borks on the driver install.

 

Building and XP64 Virtual Machine right now... Will post updates in a bit.

 

Initial results are not looking so good,

EcuFlash installs up to the driver install then says you have to use the 64bit driver installer, install does not bomb out, but the driver does not get installed.

Went and got the 64bit driver install kit from the link above, tried to install that and got an ugly error:
Error creating process
<C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\IXP0000.TMP\DL LSWA~1.exe>. Reason:
This application has failed to start because the application configuration is incorrect.
Reinstalling the application may fix this problem.

 

Well I guess its a no

 

I definitely figured the drivers would be the sticky point..

The drivers from FTDI need to be massaged to recognize the ECUFlash cable.. Since it has a unique ID associated with the device, and you have to get the description right..

Being the person that I am, if I were running 64 bit, I'd probably have already created a modified package just as I did with the first Openport cable drivers when 1.26 was released for testing on the Evo..