Actually I do not think it is just a patch although the complete code. I think the reasons the softwre guys said "required" that you update from V26 is so that they had a baseline to work from. If some people were reporting errors it would be easier to determine that the issue stemed from the code or some legacy crap in there.

I could be todally wrong...., just ask my wife. I am sure she remembers enough times. :-)

Anyway I have jacked with this too much.

Here is where we stand.

1) You can change the logo with whatever build you want.
2) Whoever made the cool logo swap tool can add in a CRC check adjustment tool. The CRC24 bits are in each individual files so the process would be quite simple. Identify the CRC prior to making a change, and then update that line of code once you insert your custom logo. The poster Nomad figured out the process to adjust the CRC

Now, some users were reporting issues with the search feature not working properly. I did not try this, but I think the best goal would be too try and hack the V26 released code to add perpective mode. It might not be simple, but that would be the correct method.

So we have a few accomplishments.
1) a new tool for customizing your logo (just a small refinement will need to be made to adjust the CRC in the new file)
2) Ability to run perspective mode and the v26 firmware until you change it.
3) a baseline to start from in hacking out the extra features such as off road guidence, perpective mode, taxi mode (why I do not know) and other

At this point, I think it is left to the software pros on making those last changes.

2Wires, how big of a task is this? Much appreciated if you can do it. (Also sent him/her an email)

-RSZ

PS... just got word that he is working on it

I got word that nomad is working on it as well. He is also looking at the V26 code to see if he can turn it on with the released version.

Below are the details from Nomad that should be helpful to anyone trying to make an image swap program. Nomad has already proven that this process works in an earlier post. I installed his navboot file in my V26.09 image and it worked perfectly. Although his test version has the HACKED BMW logo, with skull and crossbones.... Not sure my wife would be hip to that splash screen.

http://www.bimmerboard.com/members/a...l/logohack.jpg


System works on MIPS CPU and OS-9000 software by Microware.
Each program, library or data file stored in a structure called 'module'
Each module has a header, body and CRC value.

First thing you need to do is extract all modules from 'navboot' file.
Here is some tips:
WORDs and DWORDs are stored in big endian format (most significant byte
first)

Each module started from 'magic' bytes sequence: 4D AD 00 02 which indicates the start of module header.

DWORD at offset 0x04 is the module full size DWORD at offset 0x0C is offset to module name (ASCIIZ string) DWORD at offset 0x24 is offset to module body

There are a lot of other fields such as module type, access rights, creation date etc.
Last 3 bytes is module CRC.


Martin
www.bimmernav.com

Ok, I am looking into it.
I just implemented CRC24. It is an unusual check so I had to implement it by myself (with a little help from jacksum ;) ).

I try to exchange the image and also change the checksum now.

Thanks Martin for the extraordinary effort... this goes well beyond just upgrading the Nav software. :thumbup:

By reading the complete thread I think that not only turning the Perspective on in the release version is the sure way to go, I think that keeping the Perspective on while reloading release V26 could be another way of looking at this and probably more direct.

Right now I am running the V26 back in my Nav but with the Perspective on. We already know that if the map orientation is changed then the Perspective disappear as a selection, so what about finding whatever "flag" keeps the Perspective selection on until changed and just set the sucker as a constant instead of a variable? :confused:

:goodluck: you guys. Keep up the great work!!

Okay... so help me with a dummies version of this... so I can understand :) .

1. Open navboot in a Hex Editor, remove old gif and replace with new GIF89a file.

2. Remove the last 6 characters (00 xx xx xx) of the file and calculate the 24bit CRC checksum using Jacksum.

3. Convert the checksum into Hex (not sure how you did this) and add it as the last 6 characters of the file.

4. Save the new navboot and then overwrite the navboot in the iso with the new navboot.

5. Burn, install and enjoy?

I completed the CRC24 routine but I cannot find out about what to calculate the checksum.
I tried it with the header and took 2, 4, 6 and 8 bytes away. But no luck.

Maybe someone can connect me with Nomad. He also seems German.

his email address was sent via PM

I contacted him. So we have to wait now.
I tried some more ways for the checksum but couldn't get it.