Jon

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...