Xoutpost.com

Xoutpost.com (https://xoutpost.com/forums.php)
-   Navigation System (https://xoutpost.com/electronics/navigation-system/)
-   -   Changing splash screen on a Mk3 - here's how (https://xoutpost.com/electronics/navigation-system/24730-changing-splash-screen-mk3-heres-how.html)

KiwiJochen 12-26-2006 05:54 AM

Changing splash screen on a Mk3 - here's how
 
I did this on mine today, just to proove to everyone it can be done :-)

Full instructions and photos are here:
http://www.bimmerboard.com/forums/posts/293615

Jochen

jammykam 12-29-2006 11:28 PM

Thanks for the info Jochen. I figured out the usw_load part (well, I hadn't verified since it killed the mk3, I edited all 3 using NavTweak though) but hadn't realised about the mode2 burning. I used UltraIso which changed the cdd image from mode2 to mode1.

Well, mk3 is dead at moment, but trying to revive with a mode1 disk and modified startup screen probably doesn't help :rolleyes:

Will gice this a go tomorrow :nervous:

KiwiJochen 12-31-2006 05:00 PM

Any luck?

jammykam 01-01-2007 08:07 PM

I've not had any luck with this unfortunately. My first port of call was to fix the broken system, so I loaded a v22.1 disk (unmodified) which brought it back to life. I then tried it with a v23 modified disk and so far no luck. I wasted a few disks cos I'd burnt it wrong. I noticed you can create a mode2 cd using Nero, but that one didn't work either.

Quote:

Originally Posted by KiwiJochen
Command line was
mode2cdmaker.exe -o "image" -v "NAV_SW" -e "dat" -ccd -f
I used m2cdmgui.exe (UbiK mode2cdmaker GUI v1.6)

When you used mode2cdmaker, I assume you used something like UltraIso to extract all the files, modified the usw_load file and then 'dragged & dropped' to the mode2cdmaker gui. If I drap&drop the iso, it just makes another image with an iso in, not the files. I assume after the '-f' you had a whole bunch of other stuff there as well.

When going up from v22, do I need to go down to something lower (to less than software 3-1/63, i.e. v21) and then back up again. Or should using a v23 disk cause it to reload? Reason I ask is because v23 has the same software 3-1/63 on it as well.

It's weird cos when the mk3 was dead, it did exactly what you said and the disk would not eject. With the new disks it just spits them straight back out again, so i assume i am doing something wrong in burning the disk.

I'm fairly happy to give any suggestions a try, now that I know I have a working v22.1 disk, at least I know it will revive should something go wrong!

thanks and happy new year.

KiwiJochen 01-02-2007 02:43 AM

Quote:

Originally Posted by jammykam
I've not had any luck with this unfortunately. My first port of call was to fix the broken system, so I loaded a v22.1 disk (unmodified) which brought it back to life.

v22.1 would have been Mode2/Form1

Quote:

Originally Posted by jammykam
I then tried it with a v23 modified disk and so far no luck. I wasted a few disks cos I'd burnt it wrong. I noticed you can create a mode2 cd using Nero, but that one didn't work either.

Probably has wrong TOC. You need correct TOC for nav to recognise CD.

Quote:

Originally Posted by jammykam
When you used mode2cdmaker, I assume you used something like UltraIso to extract all the files, modified the usw_load file and then 'dragged & dropped' to the mode2cdmaker gui.

Correct.

Quote:

Originally Posted by jammykam
If I drap&drop the iso, it just makes another image with an iso in, not the files.

Of course. You tried to make a image with one .ISO file :-)
Don't make an image of an image.

Quote:

Originally Posted by jammykam
I assume after the '-f' you had a whole bunch of other stuff there as well.

-f means file name. every file has the -f in front of it. The GUI makes the command line for you.

Quote:

Originally Posted by jammykam
When going up from v22, do I need to go down to something lower (to less than software 3-1/63, i.e. v21) and then back up again. Or should using a v23 disk cause it to reload? Reason I ask is because v23 has the same software 3-1/63 on it as well.

If you have 3-1/63 loaded, then it won't load anything newer.
I made my modified OS CD v3-1/64, to ensure it would be loaded.
Or just give it the wildcard 00 version (3-1/00) and it will load regardless.

Quote:

Originally Posted by jammykam
It's weird cos when the mk3 was dead, it did exactly what you said and the disk would not eject. With the new disks it just spits them straight back out again, so i assume i am doing something wrong in burning the disk.

Wrong TOC. Nav system looks for certain files in the Table Of Contents (TOC). Thats what the modified mode2cdmaker does, it writes the correct TOC.

Regards, Jochen

jammykam 01-02-2007 08:54 AM

Hi Jochen

Looks like I need to modify the sw version then, is it in the usw_load file? I'll do a search to find out what string to change, do remember reading this before.

I've sent you a PM with my email address, could you email (or put on megaupload) the modified mode2cdmaker that you are using.

Thanks,
Kam

KiwiJochen 01-02-2007 01:54 PM

Instructions are all here:
http://www.bimmerboard.com/forums/posts/293615

jammykam 01-02-2007 05:44 PM

Jochen, brilliant stuff mate, you seem to have done the impossible and updated the logo of a mk3 system! :bow: :thumbup:

I can verify this works, I've just created a "v3-1/64" disk (modded v23 disk) and loaded with a custom splash screen. Woohoo!

You need Jochen's updated mode2cdmaker so that it writes the correct TOC. I've uploaded to rapidshare http://rapidshare.com/files/9948166/...maker.rar.html

If you need a easy to use hex editor try http://www.chmaas.handshake.de/delph...2.htm#download
It's freeware and you don't need to "install" it and clutter up your system.

Jochen, one thing I have noticed now though is that the splash screen doesn't come up straight away (i.e. when I open the door), only very briefly when I put the key in. I'm gonna keep checking this. I know it isn't anything to do with your instructions since other users have complained about it. My splash screen is actually smaller than the original ==BMW== one, so guessing it is not that. Any ideas?

thanks again, you're a genius :thumbup:

KiwiJochen 01-02-2007 08:37 PM

Splash screen comes up when nav is booting only.

So if you turn off ignition, and then turn imediately back on, you get no splash screen, as nav is already booted.

But if you unlock car, wait a bit for nav to boot, open drivers door - splash screen will show.

This is all linked to the boot process for the nav computer. Can't change it :-)

Glad you got your Mk3 working !! Yay....

Symbian 01-03-2007 03:20 PM

Hi all, hi Jochen

I didn't understand what and where should I change in hex editor to get a "wild" version of sw so I haven't to charge a previous version before charge modified mine...
Someone can explain me please?
Thnks


All times are GMT -4. The time now is 12:20 PM.

vBulletin, Copyright 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.6.0
© 2017 Xoutpost.com. All rights reserved.