Customised Windows Install

[ceerp]

I have been working on a customised windows version for some time now - just changing the icons and the theme etc. I've even got a nice install screen and logon screens.

There's one thing spoiling it though. After the install has run (the screen from winntbbu.dll) there is a screen that is very similar to the default boot screen, but where the scrolling bar would be, it 'says please wait'. You see it at full resolution (in my case 1280x1024) and the screen is small so I guess its 640x480.

Does anyone have any idea where the bitmap will live? Its not in ntoskrnl.exe or in ntkrnlpa.exe.

Cheers

[MCT]

its OOBE u can remove it with nlite, or manually edit the files if ud rather

[Ghost82]

its OOBE u can remove it with nlite, or manually edit the files if ud rather

Be warned that if you remove OOBE you can't activate Windows anymore, so only remove if you have a Corp. Edition!

[fillalph]

I am not 100% sure, but I believe removing OOBE will cause a bunch of problems. I know that it used to. I am not sure if nuhi maybe did a fix or something. Just be careful when you remove components.

]Bonkers[

[prathapml]

You don't necessarily need to remove OOBE.

You can disable it from running, through winnt.sif:

[Unattended]
  FactoryMode=yes

[muiz]

runoobe=no

[ceerp]

@muiz

Can you expand on that a bit? Where is that written? Winnt.sif?

I have tried FactoryMode=yes but I don't know enough about it to be happy with my pc being in a factory mode. It seems like it (if it had a rational thought process) would want to be 'closed' like an audio cd when it's burned.

The files of concern are msobmain.dll and intro.wma. If I change the bitmap and delete the .wma, will Windows halt at that piont due to the missing file?

[MCT]

u can remove the files from txtsetup.sif so it doesnt check 4 them