January 24th 2011 pre-release

[Blacky]

I've just heard of another similar complaint but with a T43 controller. I'm still investigating, but it is possibly that the file that causes the $0502 error is an old file and does not contain enough (or incorrect) information in the meta data section of the *.ctd file. Specifically the OS and/or Stream settings. Can you please send me (paul@efilive.com) the file that works and the file that does not work and I'll check.

Regards
Paul

[swingtan]

On their way.....

[oztracktuning]

Update everything, including saving the old tune file with the new version.
Also do bootblock, firmware and
reload the BBX settings using EFILive Scan and Tune.

I thought you enjoy challenges like that Simon.!

[Blacky]

I can see what the problem is, but not what is causing it.
The problem is that the "failed" file is missing a "magic identifier" in the header section (see image).
Compounding the problem was a bug in the V7 and V8 software that did not "notice" that the magic number was missing - making the software "assume" that the file was invalid which in turn caused the script file name (i.e. object file) to not get initialized correctly which in turn led to the $0502 error "Object file not found". So I need to fix the magic number not being recognized as missing and I also need to make it return the correct error number in the case of a missing magic number.

However, that still does not address the underlying cause of why the magic number is blank in the first place. How did you create the "failed file"?
- did you read it using pass-thru V7 (which build number?)
- did you read it using pass-thru V8 (which build number?)
- did you read it using BBR (which firmware version?)
- did you open it from disk and re-save it using V7 (which build number?)
- did you open it from disk and re-save it using V8 (which build number?)
- some other option that I haven't thought of?

Regards
Paul

[Chuck CoW]

Well, for me... I sent the guy a file (which I've used before) and it failed to flash... I noticed the serial and vin # missing which

I thought was the initial problem... (not sure why it returned a script file missing error) and then after Paul's request, I

created the new tune file from the customers original .ctd read of the T43... Customer has not yet tried to remote flash it yet,

but I guess Paul still sees the missing magic identifier.....

Strangely enough, I've had customers install the latest software (as did this guy) and nobody has complained yet....

Also, I did update the customers firmware and latest scripts.

Yes, my laptop has the latest software and the V2 has the latest firmware.

Chuck CoW

[swingtan]

How did you create the "failed file"?
- did you read it using pass-thru V7 (which build number?)
- did you read it using pass-thru V8 (which build number?)
- did you read it using BBR (which firmware version?)
- did you open it from disk and re-save it using V7 (which build number?)
- did you open it from disk and re-save it using V8 (which build number?)
- some other option that I haven't thought of?

1. Yes. It was a copy of my original file from 2007. So what ever version of V7 was around then.
2. No
3. No
4. Yes, opened in V7 but unsure of the build number as I went to 149 to see if it fixed the problem. I think it was 147 or 148 though.
5. No

Finally, I did open it as a .tun file, then applied a script to it generated from the COS tun before saving it as the .ctd file.


Steve, I'm already on latest BB/firmware. I also formated the config directory and reloaded all the config files. Also saving the file with the newer version makes no difference.

Simon

[swingtan]

Oh, did you want a copy of the original .run file?

Sent from my HTC Desire

[Blacky]

Oh, did you want a copy of the original .run file?

Sent from my HTC Desire

No thanks, I've got all the info I need... I'll be working on it tonight until I figure it out.
Regards
Paul

[swingtan]

Oh, OK. I sent it anyway, so just delete it :p

[GMPX]

Sent from my HTC Desire

Do we care