Those are the results I achieved. I think I confused the splash screens. All this back and forth has got my marbles in a tizzy. Anyway when I meant the old splash screen, I meant the "T26.09A" and not the "==BMW==" Sorry.

Although, I have another motive here. And that's to allow the use of any splash screen that one desires. Aand have the new enhancements that V26.09a brings.

Looks like we're on the same page though as far as moving the new beta files to the old V26 0101 directory. Great work :thumbup:

the only thing is that you moved over the entire contents of the flash directory. Now if you go to change the map directions, I do not think you will see all three options!!!!

A thought guys what if the checksum is only part of the requirement

During installation these files are being written to memory in the Nav Computer what if they have to be a very specific size in order to be placed in the correct position in the firmware and if the installer can't write the files to the correct area of memory it just bombs?

Or could it be that once the installer has written the files it then writes something else somewhere that tells the Nav comp bios what is where?

And it is at that stage that things don't add up so it bombs again?

Okay, my thought process is that based on the above we can not enable 3d view. So I intend to restore (since we know it was part of the original v26 but disabled) the beta to v26 and then try to enable all features and modify the splash screen.

If I am merely chasing my tail please stop me. Otherwise back to the lab...

-RSZ

Quite to the contrary, I have moved effortlessly back and forth between modes and photographed it just in case we are on the right path.

Help me understand what you are saying. Are you suggesting that adding the directory structure to the V26 image gives you perspecitve view, and the software version is 6.00 instead of 0.00?

That's correct, that's what I achieved yesterday. The only issue is the splash screen "T26.09A" which I'm in the process of fixing.

Right, now that makes sense. What you are doing is taking the entire firmware string and moving it to a new CD. I can not see how this is different from just loading the V26.09 Software disk by itself.... Or am I missing something????

I have an image that loads a custom logo that works. I think the better strategy towards this hack is to just hack the v26 disk and enable the 3d mode. I have swapped around individual files from the alpha disk to the released version one at a time and can not locate which one flips the register to enable perspective mode IF using the V26 disk files.

I guess you are right, if you compare navboot files from V26 and 26.09 there is about 840KB size difference between those so something is missing.

So Bishop, you believe that v26beta is nothing more than a patch. Therefore we are only replicating to one disk the act of installing v26 and then the beta?