Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Giving Your Windows Cosmetic Surgery

- - - - -

  • Please log in to reply
195 replies to this topic

#1
b0r3d

b0r3d

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 821 posts
  • Joined 03-August 03
Updated: 10/11/03
Fixed: Typo in the bootlogo.cmd

Updated: 03/11/03
Added: msgina.dll Guide
Added: SFC Disable Guide
If you have any questions, comments or suggestions, please ask :)

UXTheme.dll:
To change your boot logo, default theme or to add themes that are able to be seleted by default (like the standard Windows Luna / Silver / Olive themes), then the first thing you need to do is patch your uxtheme.dll file.

Microsoft Windows won't allow you to install any themes that arent digitally signed by Microsoft. Its you're uxtheme.dll that does the checking. So to be able to add new themes to windows, we need a hacked version of this file, that will tell Windows that the themes that we are installing are infact digitally signed by windows. (which ofcourse they arent)

Before you continue, patch your uxtheme.dll by one of the following two ways.

1. Probably the easiest solution would be to download the uxtheme cab file extract it, and place it in your i386 directory.

2. Aaron XP has a guide to paching your uxtheme.dll on the Unattended XP guide website, and also has a download link for the hacked file. Follow this guide

Windows File Protection
If you're having problems getting some of these customizations to work, its most probably because of your Windows File Protection or WFP.

Whenever windows detects that a system file isnt the one that was packaged with Windows, then it attempts to replace the modified version, with the one off the Windows CD. This means, when you're installing your windows with your modified files in your $$\System32 directory, on the next boot, they will be replaced by the origional windows versions.

There are two ways to get around this.
1. Eject your CD when windows has finished copying all the files to the HDD (after the dos portion of the windows install)
2. Disable WFP alltogeather.

To disable your WFP, add this to a reg file (put it in notepad, save it as a .reg):
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogonAdd]
"SFCDisable"=dword:FFFFFF9D
To re-enable your Windows File Protection later on, modify "SFCDisable" to read 0 by navigating to that key using regedit.

Wallpaper:
To change your default wallpapers, simply place the image file which you wish to have as your wallpaper into into $OEM$\$$\Web\Wallpaper - If this directory does not exist, now would be a good time to create it :D

To actually set your default wallpaper to something different, orther than Microsoft's default grassy hills wallpaper (bliss.bmp), you need to use a little regristry tweak.

Add this to your tweaks.reg file: - Thanks to DaveXP for this tweak
[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Desktop\General]
"BackupWallpaper"="c:\\windows\\web\\wallpaper\\xppaper.jpg"
"Wallpaper"="c:\\windows\\web\\wallpaper\\xppaper.jpg"

Ofcourse you will need to replace "xppaper.jpg" with the actual file name of the wallpaper you wish to use, including its extention.

Note: I am not sure if you can use %systemroot%\\Web\\Wallpaper\\name_of_wallpaper yet, but i will try it out, and update this part of the guide.

Note: If you do not have a tweaks.reg file, refer to the Unattended XP Install Guide

Themes:
First off, you need to have changed your uxtheme.dll file, which is the first oder of buisness in this guide. If you have not done so already, please do as it says, as changing and adding default themes to Windows is not possible without it.

Once you've followed that guide, place your themes into $OEM$\$$\Resources\Themes - If you do not have a $$ directory in your $OEM$ folder on your CD, then create it now :D

The next step is to go download some nice themes which you'd like to add to your CD. Once downloaded, extract it, and throw it in your $OEM$\$$\Resources\Themes\ directory.
To change the theme you wish to be applied by default, you need to edit a few lines of your winnt.sif file. Thoes lines are as follows.
[Shell]
CustomDefaultThemeFile="%Systemroot%\Resources\Themes\YOURTHEME.THEME"

Also, in your winnt.sif file, you need to have the following options set:
OEMPreinstall=Yes
OEMSkipEULA=Yes

Your themes (.msstyles) need to have a .theme file to acompany them. The .theme file, simply tells Windows where all your theme files are located. For example, the desktop wallpaper, any special icons, and the theme itself. If you download a visual style, and it does not containa .theme file, read on.

How to make a .theme
To make things tremendiously easy for you, ill post a working .theme here. All you need to do is copy and paste into a word document, change the locations to point to the right place on your CD (marked in red) and save it as a .theme file. In this example, my theme is called CyberField.

; Copyright © Microsoft Corp. 1995-2001

[Theme]DisplayName=CyberField

; My Computer
[CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\DefaultIcon]
DefaultValue=%SystemRoot%\explorer.exe,0

; My Documents
[CLSID\{450D8FBA-AD25-11D0-98A8-0800361B1103}\DefaultIcon]
DefaultValue=%SystemRoot%\SYSTEM32\mydocs.dll,0

; My Network Places
[CLSID\{208D2C60-3AEA-1069-A2D7-08002B30309D}\DefaultIcon]
DefaultValue=%SystemRoot%\SYSTEM32\shell32.dll,17

; Recycle Bin
[CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\DefaultIcon]
full=%SystemRoot%\SYSTEM32\shell32.dll,32
empty=%SystemRoot%\SYSTEM32\shell32.dll,31

[Control Panel\Cursors]
Arrow=
Help=
AppStarting=
Wait=
NWPen=
No=
SizeNS=
SizeWE=
Crosshair=
IBeam=
SizeNWSE=
SizeNESW=
SizeAll=
UpArrow=
DefaultValue=Windows default
DefaultValue.MUI=@themeui.dll,-2043

[Control Panel\Desktop]
Wallpaper=%WinDir%\Web\Wallpaper\XPPaper.jpg
Wallpaper.MUI=@themeui.dll,-2036
TileWallpaper=0
WallpaperStyle=2
Pattern=
ScreenSaveActive=0

[VisualStyles]
Path=C:\Windows\Resources\Themes\cbfield\cbfield.msstyles
ColorStyle=NormalColor
Size=NormalSize

[boot]
SCRNSAVE.EXE=

[MasterThemeSelector]
MTSM=DABJDKT
ThemeColorBPP=8


Okay, after all that, this is what my directory structure looks like.
$OEM$\$$\Resources\Themes\cbfield.theme
$OEM$\$$\Resources\Themes\cbfield\cbfield.msstyles
$OEM$\$$\Web\Wallpaper\XPPaper.JPG

That should be it :rolleyes::

Boot Screen:
The first thing you need to do is patch your uxtheme.dll file. Instructions are located at the top of this post.

After that, download a custom boot screen, Or if you prefer to make one yourself, then you can use any BMP you like.

Note: If you downloaded a bootscreen, and it contains a file called ntoskrnl.exe, then skip this next parragraph.

Next, what you need to do is make a copy of your ntoskrnl.exe from your \Windows\System32 directory and place it somewhere thats easier to get to and work on. Now, grab a copy of Resource Hacker and open up the copy of your ntoskrnl.exe file.
In the left hand column you will see a list of resources to edit. Open the first tree called Bitmaps and you will see numbers 1-10. Numbers 1, 8, and 10 are the WinXP Pro bitmaps. 1, 7, and 9 are for Home Edition. In this tutorial we will be using Pro. Select number 1 --> Action/Replace Bitmap. Select Bitmap to replace 1, then click on 'Open file with new Bitmap' and locate your edited boot logo. Then click replace. Save your new ntoskrnl.exe file, and you're done. This will replace the main picture of your boot logo. If you wish to customize it even further and change the litle moving blue dots, or save the origional boot screen for editing, then i suggest you follow this more extensive guide.

Still with me? Good.
If you downloaded a ntoskrnl.exe file, this is where you should continue reading.

For adding your ntoskrnl to your XP CD, i will be using the method used by gosh, which will be outlined here.

What we need to do now, is make a directory on your XP CD, under this path:
$OEM$\$$\System32

The next thing you need to do, is rename your ntoskrnl.exe file to oemkrnl.exe and place it in the folder you just created above.

Now, in your winnt.sif file, add these commands:
[Unattended]
UnattendedMode=FullUnattended
OEMPreinstall=Yes
OEMSkipEULA=Yes

[GUIRunOnce]
bootlogo.cmd

Next create a bootlogo.cmd file which contains this:
bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0

Here's a brief explanation of the above code:
When you install Windows XP, it copes the $OEM$\$$\System32 folder to %windir%\system32, thus, placing your oemkrnl.exe file into your system32 folder. When XP Setup then processes the GUIRunOnce section of your winnt.sife file, it adds the switch /kernel=oemkrnl.exe to your boot.ini file, which forces windows to use your edited file, instead of the one shipped with windows.

So why do all this when you can just put your ntoskrnl.exe into the i386 folder? Since this is gosh's method, i'll let him explain.

1 - If you install a windows update that has a newer version of ntosrknl.exe, it'll replace your customized ntoskrnl.exe file. The only fix would be to resource edit the new ntoskrnl.exe. This isn't very practical when you consider there have been at least 4 kernel updates to xp since sp1 was released. Using my method, the custom ntoskrnl.exe is ALWAYS used, even if you do windows update.

2 - If you need to install a service pack, all you do is delete the /kernel= part in your boot.ini. If you integrated a custom ntoskrnl.exe file, you would have to use the switch -o to install a service pack. My method is more service pack friendly.


Once you've done all that, go grab yourself a coke. You've earnt it.

msgina.dll

The msgina.dll contains lots of little windows goodies to change and configure. It contians some windows images, and also some interesting strings of text. This guide will teach you how to change this image, and others like it.
Posted Image

The first thing you need to do, is grab a copy of the msgina.dll from \Windows\System32\ and open it with resource hacker.

Next, open the key bitmap --> 101 --> 1033. You’ll see the image here that we want to change. You can either save a copy of this image for editing (right click --> save [bitmap : 101 : 1033]), or make your own image, and replace the windows one (right click --> replace resource). For thoes of you who are like me, and like to make your own images, the dimentions of this image are 413 x 72.

Windows uses two different images (allthough identical) in your msgina.dll. They are as follows:
101: ctrl + alt + del (win2k style), Applying settings box, Shutdown dialog
107: login box
The only difference i can see in the two images, is that the one for your login screen is a little bigger than that for the end task menu. To change your login box pic, replace the key located in 107 --> 1033. Once again, for thoes who like to make their own images, the dimentions for this one are 413 x 88

If you have a little browse through the other keys in your msgina.dll, you'll notice these two images for other operating systems. I think that the reason for this is, windows just packages each operating system with the same msgina.dll, and which picture is used, depends on the version of windows. This file also contains lots of string values to dialogs, that you may want to fiddle with. For example, i changed the text on my End Task.. button to read Kill Programs..

Anyways, back to the task at hand. Once you've changed thoes two images, save your msgina.dll, and throw it in your $$\sytem32\ folder on your windows CD, and that should be it!

Below are images of my two edited images in use.
Posted Image Posted Image Posted Image

Happy cutomizing!

Note: Windows XP Home users can apply new images to their version of Windows by editing the 128 and 129 keys respectively, instead of the keys mentioned in the guide.

Edited by b0r3d, 09 November 2003 - 11:14 PM.

Remember, you can wear your underpants four times without washing.
Forwards. Backwards. Inside out forwards, and inside out backwards.


How to remove advertisement from MSFN

#2
XtremeMaC

XtremeMaC

    MSFN SuperB

  • Member
  • PipPipPipPipPipPipPipPipPipPip
  • 5,070 posts
  • Joined 13-October 03
  • OS:Windows 7 x64
  • Country: Country Flag
thanks for this all combined version :)
really appriciated!!!!



#3
Aaron

Aaron

    The MSFN Banana

  • Patrons
  • 5,767 posts
  • Joined 17-August 01
  • OS:Windows 7 x64
  • Country: Country Flag
b0r3d, I'm gonna change that page soon - to use a different UXTHEME.DL_ which setup won't halt on, you can get it from here: http://www.MSFN.org/...?showtopic=9871

#4
b0r3d

b0r3d

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 821 posts
  • Joined 03-August 03
Okay. I changed the URL to point to your file link.
Remember, you can wear your underpants four times without washing.
Forwards. Backwards. Inside out forwards, and inside out backwards.

#5
rstryker

rstryker

    "I will show you fear in a handfull of dust"

  • Member
  • PipPipPipPip
  • 594 posts
  • Joined 21-June 02
  • OS:XP Pro x86
  • Country: Country Flag
Thanks dude...good info :)
Love to Drive !!!

Posted Image

#6
webmedic

webmedic

    fixer of things broken

  • Member
  • PipPipPipPip
  • 621 posts
  • Joined 15-August 03
he he. Was wondering how far you all were on this. I had the custom theme thing going but had not added the boot logo's. I do it a little different but not to terably. I add the themes the same and then use the hacked uxtheme.dll as aron mentioned above. The only thing I think I do diferently is that I dont use guirunonce to get any of this done. I finnaly got it all running durring the first install part without needing to use guirunonce.

The inf files are working well now also. I'm quite happy with it all. and i use a little progie called cmdow to hide the command prompt windows durring install.

I'm trying to think if there is anything you missed but i can think of anything right now. Well other than small regestry tweaks but those are kind of personal depending on the look and feal each person wants. For me I want a default theme that looks nice under windows xp but I also add few things to the desktop to make it look a little more like windows 98 so others can get used to it easier.

all in all thanks for the guide.

#7
eXPerience-XP

eXPerience-XP

    The Offical MSFN Newbie

  • Member
  • PipPipPip
  • 365 posts
  • Joined 23-September 03
thx man i been waiting for this... nice guide :)

EDIT: bor3d the color red doesnt show up instead it shwos up as color= red so u might wanna edit that :rolleyes:
Images in signatures shall NOT exceed a total of 300x100 and 80kb.

#8
miso1391

miso1391

    Newbie

  • Member
  • 35 posts
  • Joined 31-August 03
Hi
It's more easier to put the theme and wallpaper in SFX archive and put it in svcpack.inf

and in winnt.sif make it like this

[Shell]
DefaultStartPanelOff = Yes
CustomDefaultThemeFile = "%WinDir%\Resources\Themes\CoolXP blue.theme"

*since you choose the theme it will get it's own wallpaper

want more explain ask !

#9
gamehead200

gamehead200

    SEARCH!!! SEARCH!!!

  • Super Moderator
  • 7,039 posts
  • Joined 02-September 02
  • OS:Windows 7 x64
  • Country: Country Flag

b0r3d, I'm gonna change that page soon - to use a different UXTHEME.DL_ which setup won't halt on, you can get it from here: http://www.MSFN.org/...?showtopic=9871

Yea, Aaron, thanks for that! I was wondering what had happened to the other technique! :)

#10
b0r3d

b0r3d

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 821 posts
  • Joined 03-August 03
If anyone has a better way of doing things, than let me know!
I only know what people tell me :)
Remember, you can wear your underpants four times without washing.
Forwards. Backwards. Inside out forwards, and inside out backwards.

#11
ahmedramzi

ahmedramzi

    Member

  • Member
  • PipPip
  • 258 posts
  • Joined 08-June 03
I don't know.. In my openion, the best way to add my own wallpapers, is to rename them as the original windows wallpapers, use the command "MAKECAB wallpaper.jpg Bliss.JP_", and so as for the rest of the pictures.
Then all you have to do is to replace the existing files with the cabinet files you've just made.
This method is the best as it doesn't inscrease the CD size

#12
webmedic

webmedic

    fixer of things broken

  • Member
  • PipPipPipPip
  • 621 posts
  • Joined 15-August 03
ah well that explains it I have done a guide on how to use 2 cd's but I also now use a dvd. I'm anly about 1/3 of hte dvd now so I have allot of extra room yet.

#13
ahmedramzi

ahmedramzi

    Member

  • Member
  • PipPip
  • 258 posts
  • Joined 08-June 03
DVD is the best invention in the written history!

#14
ahmedramzi

ahmedramzi

    Member

  • Member
  • PipPip
  • 258 posts
  • Joined 08-June 03
speaking on CD sizes, does anyone know how the winbeta guys made their fancy CD's: 5in1, 6in1 ...?
I have their copy of Media Center 5in1, when i tried to copy it on my Hard Drive, it took about 3.5 GIGABYTES!!

#15
webmedic

webmedic

    fixer of things broken

  • Member
  • PipPipPipPip
  • 621 posts
  • Joined 15-August 03
well ofr the most part they use barts eltorito multi boot setups.

#16
iN2Fun

iN2Fun

    Junior

  • Member
  • Pip
  • 51 posts
  • Joined 21-October 03
what about the welcome and logon screens. is there anyway to change them?
Love the work you are all doing. Ive been an avid reader for awhile now. :)

#17
miso1391

miso1391

    Newbie

  • Member
  • 35 posts
  • Joined 31-August 03
Hi
This is my way "You can reduce the size of theme and wallpaper up to 90% by this method"


---------------------------------START---------------------------------



[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=1
BuildNumber=2600

[SetupData]
CatalogSubDir="\i386\Update"

[SetupHotfixesToRun]
WMP9.EXE
DIRECTX.EXE
FAV.EXE
JS56NEN.EXE /Q:A /R:N
KB822603.EXE /n /q /u /z
KB823182.EXE /n /q /u /z
KB824105.EXE /n /q /u /z
KB824141.EXE /n /q /u /z
MSN.EXE
KB825119.EXE /n /q /u /z
KB828035.EXE /n /q /u /z
MIDEAPL.EXE
MSJAVWU.EXE /Q:A /R:N
NETFW.EXE
Q322011.EXE /n /q /u /z
Q327979.EXE /n /q /u /z
Q330994.EXE /Q:A /R:N
Q814995.EXE /n /q /u /z
Q823718.EXE <<----- You can unpack the orignal and pack it again with switch
Q828026.EXE /n /q /u /z
Q828750.EXE /Q:A /R:N
CODEC.EXE
QL.EXE
THEMES.EXE <<------ This the archive "SFX"
TOOLS.EXE
update.EXE /n /q /u /z
WALLPAP.EXE <<------ Do the same with theme except the path
qchain.EXE

[ProductCatalogsToInstall]
KB826939.cat



Step 9:WINNT.SIF

[Shell]
CustomDefaultThemeFile = "%WinDir%\Resources\Themes\CoolXP blue.theme"

---------------------------------------END-------------------------------

for me I save 100MB by this way
my orignal theme size was 114MB
the SFX archive size is 14.1MB


*The owner of the web site "www.2mj.com" told me he well keep the pic's only for one week !
:)

Edited by miso1391, 15 February 2006 - 11:31 PM.


#18
webmedic

webmedic

    fixer of things broken

  • Member
  • PipPipPipPip
  • 621 posts
  • Joined 15-August 03
there is a major problem with adding hotfixes in the svcpack.inf. I know it's the proper way but after working with a microsft employee for a few weeks on this some other guys in another department told him that they were not really made for it and it will break things that is why I no longer work o nthe hotfix scripts I was doing and also why I just use cmdlines.txt to install everything now. There is nothing wrong with svcpackinf for the other things but cmdlines.txt is easier to use and since the hotfixes are broken I find no need to use svcpack.inf. You will find the last roll up is probably a direct result of the work we were doing when we found out how broke the hotfixes are.

I hope this info helps you all as we found some major problems with it. I did however get some other goodies that work very well but the hotfixes will never slopstream and apply right and they cause other issues.

For instance I hope you all are running a lejit copy of windows beacuse if you aren't in about 6 months to a year you are going to hate life. Well you will hate it if you love windows. This is going to be so bad. If you love windows you will go buy a copy but you will loose all your data on your hard drive. If you are borderline now you will go get linux.

#19
Alanoll

Alanoll

    CODE tags people, CODE tags!

  • Patrons
  • 5,496 posts
  • Joined 25-September 03
webmedic could you describe you way of bootscreens in more detail?

as for the other method, since there are two main different kernels, one for multiprocessor and one not, how can you do the boot screen change if you don't know which to use on the computer?

how can you put it directly into the i386 folder? to replace the ntoskrnl?
Welcome to the Forum! Please READ Me!!
Alright, that's it for the site for now. Now on to the next project....which could concievable replace the current site :)

#20
Geckotek

Geckotek

    Slave to M$

  • Member
  • PipPip
  • 255 posts
  • Joined 21-June 03
Hmmm....the boot screen didn't work for me. Gonna try again soon.

I would also like to see info on changing the logon screen. It should be similar right?

Thanks for all your hard work bor3d! GJ!

#21
b0r3d

b0r3d

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 821 posts
  • Joined 03-August 03
The logon screen is a little different. I *think* that the logon screen is located in a dll file somewhere. But i dont know what one exactly. Im sure when we find out, it'll be as simple as changing the bitmap using reshacker, and throwing it back in your windows drive. Just like the setup screens.
Remember, you can wear your underpants four times without washing.
Forwards. Backwards. Inside out forwards, and inside out backwards.

#22
Alanoll

Alanoll

    CODE tags people, CODE tags!

  • Patrons
  • 5,496 posts
  • Joined 25-September 03
uh....
for logon screen, are you refering to the welcome screen logon screen thats fills the screen? or the classic?

the WinXP style logon with the clickable buttons for users is in logonui.exe

Someone else describing that logon

i'm still interested in hearing about webmedic's bootlogo and about the multiple kernels in winxp and having boot screens
Welcome to the Forum! Please READ Me!!
Alright, that's it for the site for now. Now on to the next project....which could concievable replace the current site :)

#23
webmedic

webmedic

    fixer of things broken

  • Member
  • PipPipPipPip
  • 621 posts
  • Joined 15-August 03
I dont rememebr saying naything about boot logo's specificly. I think I ment more that I would like to use the method gosh was refering to.

But there is also a little app I use now that lets me change boot logos and login screens and it is free. I rather like it. It's something you use after you setup windows though and not as part of the install as gosh was suggesting.

#24
XtremeMaC

XtremeMaC

    MSFN SuperB

  • Member
  • PipPipPipPipPipPipPipPipPipPip
  • 5,070 posts
  • Joined 13-October 03
  • OS:Windows 7 x64
  • Country: Country Flag
i'm using bootxp works great.



#25
Alanoll

Alanoll

    CODE tags people, CODE tags!

  • Patrons
  • 5,496 posts
  • Joined 25-September 03
ah pooh.
any solution to the multiple kernels? or just hold hands and pray?
Welcome to the Forum! Please READ Me!!
Alright, that's it for the site for now. Now on to the next project....which could concievable replace the current site :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users