Windows Vista Compatability?
Windows Vista Compatability?
I'm planning on getting an HP laptop and it only has Windows Vista. I'm curious if I can still tune my car with ECUFlash, EVOScan and my LM-1. I'm just not sure if these programs are compatible.
64 bit versions of Vista may be an issue for the Tactrix cable, but as long as the drivers work in the 32 bit versions, the apps should work in 32 bit emulation or natively, AS LONG as the drivers work.
Mitsulogger uses .NET 2.0 and should work fine with Any version of XP, Vista, 2003 or later, as long as the app can find the port for the cable.
The short story.. The DRIVER will be the problem in any of these apps.. If it can't detect the cable because of a driver problem, none of these apps will work properly.
Mitsulogger uses .NET 2.0 and should work fine with Any version of XP, Vista, 2003 or later, as long as the app can find the port for the cable.
The short story.. The DRIVER will be the problem in any of these apps.. If it can't detect the cable because of a driver problem, none of these apps will work properly.
It doesn't happen often, but I have to disagree with MJ. So far, and I've tested quite a few apps for several divisions, most compatibility problems have been graphical in nature.
In fact, one application is quite complicated in terms of not just installing USB drivers, but even drivers for a custom file system, and the only crash bug that I found was that the about box exploded. It was using the standard animation control to play an AVI file!
I've already used the Tactrix cable under the last Vista FC (but not EcuFlash). Of course, a driver problem is possible under the actual release, but I'd be surprised.
-jjf
In fact, one application is quite complicated in terms of not just installing USB drivers, but even drivers for a custom file system, and the only crash bug that I found was that the about box exploded. It was using the standard animation control to play an AVI file!
I've already used the Tactrix cable under the last Vista FC (but not EcuFlash). Of course, a driver problem is possible under the actual release, but I'd be surprised.
-jjf
Yeah my entire point is the apps themselves should work, there's nothing really unusual about anything any of them do. But the driver was a problem in 64 bit versions of XP that I tested, so I have to assume it will persist in 64 bit version of Vista and 2003. The exception is Evoscan which (as of now) uses .NET 1.1 which doesnt appear to be available in Vista or 64 bit XP, 2003, or Vista.
I've started to get some feedback that the Tactrix drivers install properly and work fine in 32 bit Vista, this goes along with my testing from a few days ago which I didn't have any problems at all with any of the software or the drivers.
I have a friend testing everything with 64 bit OS's, and for the most part Mitsulogger and ECUFlash work, but the current drivers didn't load on his XP64 install. I'm not surprised though as the current tactrix driver package didn't include 64 bit drivers.
Interestingly he did actually get everything to work using VMWare and 32 bit Windows XP, on a Workstation running a 64 bit XP install. So that is something that can be done as a workaround if absolutely necessary.
Don't "Downgrade" your Laptop purchase just because of this, I'm 100% certain that all of this will be resolved as more of us get a chance to test Vista on 64 bit platforms.
Trending Topics
It was a typo as you can see from my very first post in this thread and thanks for the help
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
I just picked up a new compaq laptop with the 32bit version of Vista basic. I can confirm that ECUFlash and Mitsulogger work fine. However, EVOscan 97 is looking for .NET and cannot find it althought its already part of the OS, so it fails to install.
maybe EVOscan 98 will address this issue??
maybe EVOscan 98 will address this issue??
I just picked up a new compaq laptop with the 32bit version of Vista basic. I can confirm that ECUFlash and Mitsulogger work fine. However, EVOscan 97 is looking for .NET and cannot find it althought its already part of the OS, so it fails to install.
maybe EVOscan 98 will address this issue??
maybe EVOscan 98 will address this issue??
.NET 1.1 has been depricated, many of the API were revised in .NET 2.0 which are pretty stable and continue into 3.0, Evoscan uses .NET 1.1, and if it has any dependencies on depricated DLL's no longer used in later versions, then you will have to install .NET 1.1 on Vista 32 bit, which I'm not even sure will install at all. And I'm fairly certain there is no .NET 1.1 for the 64 bit versions of anything.
I had this problem when I migrated a few apps I had. I had .NET 2.0 only on my machine, and tried loading a project that had dependencies on 1.1, It took awhile to find the equivalent files, and in a few cases (Serial port access) there was no real equivalent and I had to rewrite the code.
I had this problem when I migrated a few apps I had. I had .NET 2.0 only on my machine, and tried loading a project that had dependencies on 1.1, It took awhile to find the equivalent files, and in a few cases (Serial port access) there was no real equivalent and I had to rewrite the code.
.NET 1.1 has been depricated, many of the API were revised in .NET 2.0 which are pretty stable and continue into 3.0, Evoscan uses .NET 1.1, and if it has any dependencies on depricated DLL's no longer used in later versions, then you will have to install .NET 1.1 on Vista 32 bit, which I'm not even sure will install at all. And I'm fairly certain there is no .NET 1.1 for the 64 bit versions of anything.
I had this problem when I migrated a few apps I had. I had .NET 2.0 only on my machine, and tried loading a project that had dependencies on 1.1, It took awhile to find the equivalent files, and in a few cases (Serial port access) there was no real equivalent and I had to rewrite the code.
I had this problem when I migrated a few apps I had. I had .NET 2.0 only on my machine, and tried loading a project that had dependencies on 1.1, It took awhile to find the equivalent files, and in a few cases (Serial port access) there was no real equivalent and I had to rewrite the code.
http://www.microsoft.com/downloads/d...displaylang=en
At least if the supported OS is correct.
Personally for serial ports and stuff I'd rather setup and call the DCB directly through managed C++.
Last edited by codgi; Feb 4, 2007 at 10:57 AM.
I believe MS now does support 1.1 for both x64 and Vista:
http://www.microsoft.com/downloads/d...displaylang=en
At least if the supported OS is correct.
Personally for serial ports and stuff I'd rather setup and call the DCB directly through managed C++.
http://www.microsoft.com/downloads/d...displaylang=en
At least if the supported OS is correct.
Personally for serial ports and stuff I'd rather setup and call the DCB directly through managed C++.
Overall I've had pretty good success with using the RS232 assemblies, the exception being in Windows 2000, I have had some reports about problems.
Thread
Thread Starter
Forum
Replies
Last Post
fas-n-furyus
ECU Flash
11
Jul 29, 2009 12:07 PM









