Vista Tutorial - Need Help To Fix Boot Logo

Need Help To Fix Boot Logo
OS…Vista Home Premium/service pack 1

This is the best install I have ever done (or was)…I did a fresh install and followed a tweak guide at NBR Vista Tips and Tweaks Guide - Notebook Forums and Laptop Discussion which was to very enlightening, to say the least. From there I have been to a few other sites and moved on to fully customizing my desktop/login and……well…this is where I stuffed up…My BOOT screen no longer works properly, even with the original “winload.exe.mui” file replaced.

I downloaded and used “Vista Boot Logo Generator” I loved the results on my last install…It worked well. Upon deciding to do a fresh install with Tweaking in mind, I simply coppied over a Boot logo I made previously after allowing permissions and all that as well as changing the NO GUI in msconfig…ect….BUT

The problem is as follows:……..The original auora background comes up?...and without the Windows is Loading Text???......I mean wtf…I just moved and replaced the original file and I get this on reboot. I have tried making more logos but everytime I restart the same thing. I have disable and re-enabled the boot gui option in msconfig…even putting back the original file does not get it working properly as the loading text is gone from that pic???

Is it something I stuffed up with permissions…or some service I tweaked? I would love to fix the problem without reloading as I have put so much effort in thus far…

Any Ideas would be great…I will try them all!

Once again for those that can't understand me or what I want to do.....:

Sorry Jack,
I am trying to coppy over a file called "winload.exe.mui" )which I generated via a specialized program) and have it execute on bootup to show me the awesome art I designed for my bootup screen.

I followed the instructions based on the program and elsewhere on the net by first going runing ms-config and enabling [No GUI] on boot up...After restarting and seeing the original vista "aorua background" I knew things were going OK...I generated a "winload.exe.mui" file by following the instructions of the program called "Vista Boot Logo Generator"...and after giving myself permissions copied and replaced the original "winload.exe.mui" in the specified directory.......

This worked the first time around I tried it...However after I did my second fresh install and after I tweaked my system...I have been unsuccessful trying it out a second time...However the second time around...I just copied other the "winload.exe.mui" file from my storage drive instead of re-creating another one...On reboot...I still get the original "aorua background" but without the "Windows Vista is Loading text"...not only should the original not be there, it no longer works properly as it should (as per the missing text)...

What do I want to do........LOL....a solution would be great...but some discussion on why this may have happened would be good too...

I'll check that link out... but is'nt that buble thing...(as good as it looks a desktop thingy and not a boot thingy?....I'll go check it out....cheers

Hi Davekyn,

This option seems to have been disabled after installing the Vista SP1. Any change from the default boot screen gets you the newer Aurora boot screen instead. It seems for now that these are out only two options.

Hopefully someone knows a way around this change by the SP1.

Shawn

The problem you're perhaps encountering is that periodically Vista will
update certain operating system files which may include winload.exe and
winload.exe.mui. If it does that, then it will throw out changes you've made
at an earlier time.

What I do with XP and what I'd recommend for Vista is NOT to write over the
operating system file, in this case winload.exe.mui - there's actually no
need, and for system stability it's better not to- you can achieve the same
by making a copy in the same place that includes your changes and calling
it say something like JonsWinload.exe.mui (you may prefer another name
-) ).

To be able to do that, at the same time you'd make a copy of Winload.exe in
the system32 directory, calling it with the same prefix as with the new mui
file (this is important since it's used to reference the other file), so in
this case it would be JonsWinload.exe. This won't upset code signing or code
integrity checks since it would basically be the same old Winload.exe, only
renamed.

Finally to finish things off nicely it would help to have 2 boot entries in
your startup menu - one for your modified boot files and one for the
standard loaders. That way if anything goes haywire you can choose the
standard startup, rather than your super logo. If you play around with
bcdedit and its syntax, then you'll probably be able to work out how to do
that, but I just had a play with this and here's an example of a
configuration that works using new logo files ......

#----------------------------------------------------------------------------------
Windows Boot Loader
-------------------
identifier {fce3eef2-0a40-11dd-b526-00402b449c4b}
device partition=C:
path \Windows\system32\JonsWinload.exe
description Windows Vista (boot logo)
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
kernel Ntoskrnl.exe
resumeobject {dadbd8bf-ce3c-1222-b7e9-82407a617fcd}
nx AlwaysOff
quietboot Yes
sos No
#----------------------------------------------------------------------------------

--
Jon


"Davekyn" <Davekyn.3802j5@xxxxxx-mx.forums.net> wrote in message
newsavekyn.3802j5@xxxxxx-mx.forums.net...

Thanks Brink...it seem a lot of people have been talking about the changes service pack 1 makes in relation to this problem...but how about Jon's response...WOW

Thanks Jon....I need a little more time to digest all of that...but really appreciate it!!! By this I mean I am finding it a little difficult to understand everything you just said.

First thing I did was check to see if I have a winload.exe seperate to that of winload.exe.mui.........Unfortunately I can only find the winload.exe.mui file...

I am confused now as to weather when I updated with service pack 1 if it took that file out or if Vista only uses winload.exe.mui......OR if in fact I need to go back in to msconfig Boot options and check the box (No GUI) for windows to generate the winload.exe file?

I'll go do that now...and see if I can find this seem-to-be missing file...BRB

Narrrr.....I only have the winload.exe.mui file in en-US folder.....MMMMMMMM, any sugestion on how to follow your advice now?

I do kinda get what your saying...will try some of what you said...brb

OKOK.........I have not tried it yet because as I understand it....the:
winload.exe file is needed to link to the winload.exe.mui file??? so If I cant find this seperate file I dont think I am going to have much luck....

What can I do....can someone else tell me if they dont have a winload.exe file and only have winload.exe.mui.....................................I dont think even a reistall is going to help this problem as even If I set the boot screen before service pacl one, its still going to wipe it................................your idea sounds good....I just dont have both of the files your talking about is all.............all I got it winload.exe.mui............any ideas.....(

"Davekyn" <Davekyn.381d25@xxxxxx-mx.forums.net> wrote in message
newsavekyn.381d25@xxxxxx-mx.forums.net...

winload.exe should be at

C:\Windows\System32\winload.exe

It should also be visible in the output (in the 'path' line) if you type the
following at an elevated ("Run as administrator") cmd.exe prompt ....

bcdedit /enum {current}

That command shows details of your current main boot entry.

--
Jon

I probably wasn't clear. There isn't a winload.exe in the en-US folder (and
shouldn't be) - in that folder is the winload.exe.mui file (the en-US folder
is also where any substitute .mui file would be placed)

The winload.exe file itself should be located at

C:\Windows\System32\

ie up one directory.

which is where it should remain, and also where any additional renamed copy
of it should be placed.

If it's still missing, then I don't know what to suggest, but that would be
strange.

--
Jon


"Davekyn" <Davekyn.381lez@xxxxxx-mx.forums.net> wrote in message
newsavekyn.381lez@xxxxxx-mx.forums.net...