<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx</link><description>Why you shouldn't do it</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Confusion over whether you have Windows XP SP1 or SP2</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#398974</link><pubDate>Sat, 19 Mar 2005 07:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:398974</guid><dc:creator>The Old New Thing</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=398974" width="1" height="1"&gt;</description></item><item><title>re: What is this Xerox directory doing in Program Files?</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#258674</link><pubDate>Wed, 17 Nov 2004 08:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:258674</guid><dc:creator>The Old New Thing</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=258674" width="1" height="1"&gt;</description></item><item><title>re: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#157785</link><pubDate>Thu, 17 Jun 2004 03:30:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:157785</guid><dc:creator>Raymond Chen</dc:creator><description>Commenting on this article has been closed.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=157785" width="1" height="1"&gt;</description></item><item><title>re: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#148216</link><pubDate>Fri, 04 Jun 2004 06:41:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:148216</guid><dc:creator>Geoff Chappell</dc:creator><description>Perhaps you could all just give away this silliness of editing the kernel and use the /bootlogo option in BOOT.INI instead. I think this may be available only with Windows XP, though. &lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=148216" width="1" height="1"&gt;</description></item><item><title>re: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#123349</link><pubDate>Thu, 29 Apr 2004 21:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:123349</guid><dc:creator>Yoshi</dc:creator><description>What you can do is alter the NTOSKRNL.EXE and save it as another filename (NTOSKRN2.EXE), thus leaving the NTOSKRNL.EXE unmodified.  Then modify your boot.ini to have it point to NTOSKRN2.EXE.  You will still get the modified bootlogo and leave the original NTOSKRNL.EXE intact.  There's an article about this on littlewhitedog.com.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=123349" width="1" height="1"&gt;</description></item><item><title>re: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#115605</link><pubDate>Sun, 18 Apr 2004 21:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:115605</guid><dc:creator>Dan_the_Muse</dc:creator><description>I have changed the bitmap in ntoskrnl.exe and saved it with a new name. In fact I've done this around 40 times with such names as kernel01.exe, kernel02.exe, etc. Altering the c:\boot.ini file, you can use any of these alternate ntoskrnl.exe files. In fact, I have around 40 alternate boot.ini files, each of which uses a different one of these alternate ntoskrnl.exe files. Renaming one of these alternate boot.ini files (e.g. boot01.ini) to boot.ini in effect makes the change. I have a program that does this automatically after each boot. Now, the only potential hangup I know of is if ntoskrnl.exe changes, for instance by virtue of a Windows Update or service pack. This happened a few days ago to me. Fortunately, one of the programs I wrote alerted me to the fact that the Windows Update I just ran did change ntoskrnl.exe and I immediately disabled my alternate logo system and am using the standard (newly supplied) ntoskrnl.exe until I get around to altering the new one (40+ times). If I hadn't caught this I don't know what would have happened.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=115605" width="1" height="1"&gt;</description></item><item><title>RE: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#54609</link><pubDate>Fri, 12 Sep 2003 21:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54609</guid><dc:creator>quanta</dc:creator><description>I just remember to swap it back with the original come patchy time.  And then wait for the hacking community to churn out a logo maker that supports the new ntoskrnl.  Another trick is to use ntoskrnl.exe /kernel=customlogo_krnl_file.exe on [boot] so you never physically mess with the real ntoskrnl.exe, although you have to remember to alter that line every service pack...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=54609" width="1" height="1"&gt;</description></item><item><title>RE: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#54608</link><pubDate>Mon, 25 Aug 2003 16:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54608</guid><dc:creator>Videobruce</dc:creator><description>I have modifyed the ntoskrnl bitmap, but I have the orginal file from the I386 folder back in it's place (by itself in the System32 folder) and still can't upgrade to SP4 running 2k w/SP3!
Any ideas??&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=54608" width="1" height="1"&gt;</description></item><item><title>RE: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#54607</link><pubDate>Thu, 07 Aug 2003 23:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54607</guid><dc:creator>Jake</dc:creator><description>Waikiki tends to be more of a Mai Tai sort of place, rather than Pina Coladas.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=54607" width="1" height="1"&gt;</description></item><item><title>RE: Changing the Windows boot logo</title><link>http://blogs.msdn.com/b/oldnewthing/archive/2003/08/05/54603.aspx#54606</link><pubDate>Tue, 05 Aug 2003 15:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:54606</guid><dc:creator>Raymond Chen</dc:creator><description>It's called branding.  My Sony Vaio doesn't let me change the boot image. Neither does my Toshiba DVD player or my Prius (yes, my car has a boot image).  I bet your TiVo, PS2, Xbox and iMac don't let you change the boot image either.  If you license a McDonalds franchise, I'm pretty sure you aren't allowd to tinker with the McDonalds logo on the front of your store.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=54606" width="1" height="1"&gt;</description></item></channel></rss>