Certain bin files when I try and open them, say for example the S_AUJP, I get an error box that reads this:



Then to read the file I have to re-select the .ecu file. No matter what I try like removing the option to load last ecu file on startup, or load last bin on startup, or reselect the ecu file then try opening the file, I still get the same error. I get it with different bins too, like I also get this with a $58 bin. Most bins I don't but some I do.

What's going on?

Tuner Pro RT registered, XP Pro.

 

Heh. Look at that, I can't type none too good. ("Could open default definition" - should be "Couldn't).

The file you specified to open the bin (the ECU file) in preferences is no longer there. Go to preferences, select "default definitions" tab, and re-browse to the default definition for the mask of the bin you attempted to open.

If that fails, delete the TunerProSettings.dat file in the TunerPro directory and re-open TunerPro.

M

 

Ummm, nope:



Deleting the TunerProSettings.dat file did the trick though.

Any idea what causes that and why you need to delete that file? I'm just curious...

 

Ummmm, yup. Thats why I gave you the second option. ;-)

Sure, I know why. Somehow your settings file got corrupt - specifically, the portion of the file that tells TunerPro what ECU to open when it encounters a specific mask byte. The crash you saw was likely TunerPro shutting itself down (unhandled exception) as a result of trying to do work on a file or at a path that doesn't exist.

Glad you got it sorted out.

 

And we truly are sorry for the inconvenience. (Just like the Crash report says).

 

Hey I blame windows and microsoft too. I'm sure if you had written it for linux and I was running it on my Debian rig I'd never have any problems right

 

You don't know what you're saying.

 

It was a joke Microsoft = Instability, TunerPro = Perfect....

Sorry I guess it was in bad taste...

 

I know... my reply was actually a joke (very inside) too. You're cool, no worries.