Okay so here's the challenge now... it took me almost a 1/2 hour to create the BMW logo as no stock image was large enough yet simple enough to meet the new smaller image size restriction. So I am taking this GIF

Attachment 5167

and inserting it twice... off to the burner and then the X.

sure paul-- anything we can do to help!

Now that would be totally off the hook if you can make that work :wow:

NO LUCK... created another coaster... "An Error Occurred During Programming!"

No, that didn't work. Same error on attempting the update.

The 'official' T26.09A takes 20 seconds after the progress bar has finished before it states that the installation was successful. All my modified files take much longer (in the order of a minute) and they all fail.

Now... we just need to find that checksum.

Paul Martin
Australia

I wish I was a programmer. I can understand the concept but can't help with the hacking, I mean editing :) .
So, good luck guys. I'll be waiting like the rest of us. :thumbup:

I would bet the Checksum would have a file creation date the same as the navboot file

Only a few files do
GSW_tools
lng_rel.tbl
loader.ini
lowboot
sw_rel_tbl

Now lowboot was the last file created and logically would contain the checksum.

Cruzing thru the lowboot file dec location 413417 shows the Error File %s Size %u does not match chain size of %d x %d bytes

I searched for %d and found the following at dec location 395201

Check CRC Valid modules in bootfile %d size 0x%x -> 0x%x

My guess is that you smart guys can modify the lowboot file to either remove the checksum or modifiy as needed

Also note that I have found CheckCRC=%d

Alrighty then... based on the above and

"A Cyclic Redundancy Check performs a mathematical calculation on a block of data and returns a number that represents the content and organization of that data. The idea is to have the CRC return a number that uniquely identifies the data. You can think of CRC as being the operation that generates a "fingerprint" for a block of data. The actual number, or fingerprint, that is used to identify the data is called a checksum.

The CRC is calculated by performing a modulo 2 division of the data by a generator polynomial and recording the remainder after division."

swapping the images is out and coding is definitely in order... off to the lab.

Just took a look at the old V26 "navboot" and ran Gifextractor against it. It only contained a single version of the "BMW" logo. The new V26.09A has two of the T26.09A just an observation I made. It probably doesn't help with the checksum issue.

Keep up the great work guys :thumbup:

Instead of trying to change the screen. Why don't you try to change a boring bit of text emedded in the navboot file.

Make it a very minor change. And then see if that is loaded ok i.e just swap one letter.

If this is rejected it shows the whole file is CRC checked somewhere. If it isn't rejected then either its just the gif thats CRCed or something more fundamental with the gif swapping.

It might help narrow down the search.