CalEdit V1.30 Software Bug

We've gotten a new crop of Tweecer folks here lately

I wanted to pass along some info that very well could save them a lotta heartache and grief

It is no secret ... I'm not a fan of V1.30

I've refused to even load it ...... just to look at it!

I've seen some say its very hard to get all traces of that version removed from your registry. You try to go back to V1.20 and its just never the same as it was

All that...simply because...you thought...you were upgrading

Shoulda said something sooner I guess but .......... I don't often think of it.

Before the Tweecer support site server crashed I saw many peeps gripe and complain about having their file corrupted with this nasty bug

Bad thing is ... they had to suffer all kinds of weird happenings with their car before they finally discovered the corruption ...

Then they had to do a fresh Read EEC or, in my case, had to find a fresh bin/cal file for a foundation to reload ALL past tweecs to obtain a corrupt free file once again ... even more

I'd like to point out this info comes from peeps on the old site I consider to be trustworthy and have a strong knowledge of Tweecer use

It seems the 1.30 version has a choice of how you upload your smoke to the Tweecer. One is just your recent tweecs and the other is a COMPLETE upload.

The file corruption seems to be caused when you pick to upload only the recent tweecs option.

Another totally hosed up thing about this ugly bug is ............
DEFAULT choice = recent tweecs

which means

If you don't pay close attention or, if you happen to forget to choose the complete option ANY time you upload ..........

You stand a chance of file corruption

Those of you who use 1.30, please feel free to correct my terms or choice of words if I did not describe things exactly as it is displayed in the newer software version but ...... I think I got close enough to show everybody what the concern here is

Happy Tweecing

btw ...... A second little tip to all the NOOBS

Regular file saves to floppy/cd .......... its is a good thing

Grady

mootang said:

thanks for the tip grady. I don't have my tweecer yet but the check is in the mail. I already loaded 1.3 on the laptop but I guess I will dump that and download version 1.2

Click to expand...

Well ...................................

It ain't like V1.20 is bug free or anything like that as well

Grady

mootang said:

what are the bugs in version 1.2?

Click to expand...

Its got to do with datalogging act & ect

You can't see either if both are in payload

You can see act if it only is in payload

You can never see ect, well kinda never
If you have it only in payload ...............
IIRC, when dl is started, same value will be present for entire dl

Bottom Line here is ... I've seen 1.18, 1.20, & 1.30

None of em are bug free

Grady

vristang said:

Thanks Grady

I have had a few files not work for no apparent reason.

I only made little changes, like bumping up the idle speed.

I just save all of my old files that worked.
This way I always have a way to get the car to run.

Save, save, save!!!

Does anyone know how to change between loading the changes and loading the entire file?

Maybe the best solution would be to just avoid the method with the bug?

jason

Click to expand...

All I can say is I saw them Smart Boys post over and over ....

DON'T do the partial load

ALWAYS do the complete load

Grady

Zero Signal said:

Grady, are you talking about the 'update only' option?

Also, do you think you could email me the 1.2 install files? I may try cleaning out 1.3 and going back to 1.2. I've been using 1.3 for quite awhile and did find that sometimes the tunes would get wacky after uploading them.

Click to expand...

Well John

I can't say for certian
but
that sounds like what it might be

Not sure if I have 1.2

Anybody know what the file name is

Grady