[final5-0]

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

[mricci]

Thanks for the info, with what i have been reading up on the tweecer i have not heard that yet. I just bought mine from IEatRiceGT. Hopefully ill have it and can start using it next weekend. So just so you guys know you will probably be hearing from me lot more on this forum.

[mootang]

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

[final5-0]

Originally Posted by mootang

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

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

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

Grady

[mootang]

what are the bugs in version 1.2?

[final5-0]

Originally Posted by mootang

what are the bugs in version 1.2?

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]

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

[final5-0]

Originally Posted by vristang

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

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

[mootang]

vristang, thats a nice little website you got there. It has some very usefull info.

[blksn955.o]

I make a point to make a whole "new" tune when I change anything. That way it has to load the whole tune and not the "same" one with a few changes.

Maybe thats why I have not had this issue of part tune/full tune loading.

I do have the DL spikes and filter them out with EA, yet another good point about EA.

[Zero Signal]

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.

[final5-0]

Originally Posted by Zero Signal

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.

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

[SVTCobra306]

It's the "update only" option. My 1.30A9 is set to a full rewrite as default. That is what you want to do. I haven't even tried the Update only yet, probably won't until A10.

I know the final release of 1.30 is in testing right now, and 2.0 is gonna be next.

I'm personally having excellent luck with 1.30 and EA.

[vristang]

Interesting point; A10 may have fixed it.

I think I was using A9 when I had the issues before.

I will have to try the update only option a few times with A10 and see what happens.

Is anyone else using A10?

jason