I have successfully run1.3,1.31.1.32 on my xp machine and my vista laptop with no problems. must be lucky

 

no problems here except the documented endian BS

 

I've been testing it for some time on a vista laptop with no issues. I had alot of custom definitions that were impacted by the endian bug, but it took me about 20 minutes to fix a majority of them that turned up. The rest will turn up when I'm trying stuff and I'll fix them as they come.

 

AFAIK we can just change any little's to big's - sh705x is a big endian processor...

 

I'm running 1.31 with no problems, I used notepad search "little" and replace "big"to fix my evo7base xml.

There is another bug though...some tables appear greyed out even with user level set to developer. I fixed each one by clicking on edit map and changing user lever to advanced.

 

Two days ago I was tinkering with my partial throttle timing table using 1.29 with no problems.

Later that night I visited OpenECU.org and downloaded 1.32 here: http://www.openecu.org/index.php?title=EcuFlash

Everything seemed to go fine. I can read my stored maps with no issues, BUT HAVE "NO VEHICLE INTERFACE." I'm ready to just reinstall 1.29, but maybe I can sort this out with some help...

 

^^^ crap, now I can't even log with Evoscan, it is saying it is a USB/cable problem. But other usb storage device works fine from the same port. arrggh.

 

Out of curiosity, is the cable your using a real tactrix cable? I figured I'd ask..

Sounds like your experiencing a driver problem, you need to uninstall the old driver package and re-install the drivers for whatever version, dont remember the name of the file, but its usually in a drivers directory in the ecuflash install directory.

 

Thanks for the support donour, but for some reason ecuflash isn't supported on my hardware. I have OS X on a flower book g4.


I guess I'm doomed to smashing my head into the keyboard.

 

Yes, MJ, that sounds like it might be the problem. Thanks. Yes, it is a real Tactrix cable, but I've shared it so many times around the shop that it could have gotten accidently traded with a different one.

 

Hey MalibuJack, can you throw a computer tard a bone here and tell me why my mac just won't let me use ecuflash?

I keep getting these error messages that its not supported on my architecture.

OS X on a CRAPPER BOOK G4

 

bump for a helpless computer user

 

Got my issue fixed. Thanks.

 

can someone help me? i installed the drivers and installed mitsulogger and ecuflash. mitsulogger works perfectly but ecuflash wont let me read my current map. it says "error occured see log window"

 

^^ and what does the pane on the right say (log window)? Or is this where you found this error message?