182 replies to this topic

[MedEvil]

In my mind it works like this.

Bootup:
- Design service is already running
- 'theming' starts up and checks itself if design service is running

Restart:
- Design service is restarted
- 'theming' was already running and does nothing itself, but waits to get informed about stuff like a restart

[was_JFX]

Here is Version 15

- PELoader is now compatible with minlogon
- Patcher now fully supports Windows 2003 SP1/SP2



Interesting is that the minlogon delay is not present when using cmd.exe as Shell.
But when using explorer or blackbox (and may every other shell replacement) there is a ca. 30 seconds delay, maybe a timeout for something

Hope for Windows 2003, someone has an idea why the Themes Service not start at boot.

[MedEvil]

I guess the delay compared to cmd.exe comes from the part that our registry is not complete upon build, but get's completed during boot up.
If i recall correctly, a reg file worth about 2MB made the difference between a booted PE registry and a non booted one, not counting hardware.

[was_JFX]

Well I know, usually all PE 1.x Projects register dll's and some other stuff via RunOnceEx. But I never see much sense in this, so I merged them at build time. What gives me better boottime.

But I still have this delay pushing me from 26 seconds to almost a minute boottime

[MedEvil]

Not all needed installs are explicitly called. Some happen automaticly when important settings are missing, that's part of windows self healing abilities.

You can try the following:
- Set cmd.exe as shell and then run each runonceex entry by hand (do not use a bat file!!! as this will trigger the install routines)
- make a snapshot of the registry or even the whole system
- call explorer.exe
- PE will get quit busy writing registry entries and even start creating folders

[was_JFX]

Yep actually what I have done. Saving from everything the registry entires and merging them into the PE build.

Such a PE would boot faster and doesn't create relevant registry entries cause they are already there.

And you know explorer doesn't create a single key it only execute Run[Once(Ex)], Active Setup, ....

So I would say this has nothing to do with our delay problem.

[MedEvil]

When explorer starts, it loads a bunch of dll, which in turn start crearting registry entries and folder structures, if they arn't there.
Starting a bat or cmd file will cause the same.

But if you already have your PE fixed to be 'perfect', then this can not be the cause of the delay.

You could log the boot of your PE to see where you loose time.

[was_JFX]

I wouldn't say perfect, only said that there is absolutely no need to do same things every boot, when a simple merging of registry settings give the same result, using RunOnceEx or don't use it.

But back to topic, what would you suggest for logging boot process. Should give much details and also have to work in PE.

[MedEvil]

You need to have %systemdrive% writable, for those cause they always write there, without an option to change the location of the log.

For a simple loging of when which file is loaded and how long it takes to the next, you can use M$ BootVis.

For a more in depth log use Filemon and Regmon from systernals.

Maybe the new process-mon or explorer is worth a look too. It combines the two tools and will put possibly the registry keys and files into a better context to eachother. But havn't used it yet myself.

[MedEvil]

Anyone any idea, no matter how far fetched, what the difference might be between starting the Design service before bootup and after. That PE does not recognize the running service, if it is started to late?

Excluded as reason thus far (we hope ):
- missing registry entries (JFX)
- missing files (MedEvil)
- missing files which need to be registered, missing registration of files (MedEvil)
- missing services (MedEvil)
- since PEgina is no longer used as proxy dll, it also can't cause the problem

[fxscrpt]

Hi JFX,

Themes.script does not work in newest Winbuilder.
(there is always BSOD 0x0000007B)

this code

Set,%Current%,NIL

If,EXISTREGKEY,HKLM,WB-Setup\ControlSet001\Control\ServiceGroupOrder,List,RegRead,HKLM,WB-Setup\ControlSet001\Control\ServiceGroupOrder,list,%current%

If,EXISTVAR,%Current%,Set,%Write%,%Current%#$cUIGroup

Else,Set,%Write%,UIGroup

RegWrite,HKLM,0x7,WB-Setup\ControlSet001\Control\ServiceGroupOrder,list,%Write%

writes this REG_MULTI_SZ value :

"drivers","Boot Bus Extender","System Bus Extender","Input Device Support",UIGroup

i'm sorry for bad news, posting in bugtracker...

Peter

[was_JFX]

Thanks fxscrpt! Ok, hope this can fix it.

-Changes Version 16

• Soved Problem with Winbuilder 78 Sp2
• 'Remove please Wait dialog' no longer depends on Reshacker
• Patcher more clean, easier to read

This will be the last version from me, I want to say good bye!
Not to the boot-land community, but to all winbuilder related projects.
Further work with scripts/projects would only result in waste of time, ranting or even frustration, what is not my aim.

Currently it's more a prove that theming is possible in PE.
I hope this last Script and the Patcher is easy to understand.
There are still some problems, so if someone can fix these, feel free to do it.

 XPThemes_v16.7z   367.97KB   553 downloads
JFX

[Lancelot]

This will be the last version from me, I want to say good bye!

Further work with scripts/projects would only result in waste of time, ranting or even frustration, what is not my aim.

Bad news, verry sorry because of the annoyance, I fully understand your feelings, I only can do what i can, From livexp part i downgrade livexp winbuilder version to wb077sp2 after i read fxscrpt reports which may effect other scripts too....

Not to the boot-land community, but to all winbuilder related projects.

Well, this is very good news, At least with your support (+with your approval) i can convert your findings/utilities to scripts and maintain

since you annonce it is the end of the development I will implement v16 to livexp project when i find time.

See you around

[TheHive]

Thanks fxscrpt! Ok, hope this can fix it.

Currently it's more a prove that theming is possible in PE.
I hope this last Script and the Patcher is easy to understand.
There are still some problems, so if someone can fix these, feel free to do it.

 XPThemes_v16.7z   367.97KB   553 downloads
JFX

I thought it was said and conlcuded that theming was not possible in a PE without WindowBlinds.

Just tested you're plugin. Its working. Very sweet contribution. Sniff! Sniff! I love it.



You mention that there are some problems. Can you mention what they might be.

Thanks!

[Galapo]

Not to the boot-land community, but to all winbuilder related projects.
Further work with scripts/projects would only result in waste of time, ranting or even frustration, what is not my aim.

That is sad to hear because your a good .script writer! But I know what you mean about frustration at times.

Regards,
Galapo.

[TheHive]

You ever think of adding an auto changing Theme style on every reboot. Or is there a way to change the style once in the PE.

Or ability specify fonts to use with it.


I like this THeme Style. Semi Windows 7 Meets Vista.
SevenVG Black

[Ariom]

Hi JFX...

For me, as far as I remember I didn't find problems since i using your script. In fact I', still using it now everytime I build. including in version 078sp2.

I'm really thankful for yuor "XP styles" in LiveXP.
Especially to Lancelot for some additions.

Ariom

[was_JFX]

Thanks for your understanding guys

Well, this is very good news, At least with your support (+with your approval) i can convert your findings/utilities to scripts and maintain

That would be very nice

since you annonce it is the end of the development I will implement v16 to livexp project when i find time.

Development doesn't have to end here, I don't lost interest in Themes.

You mention that there are some problems. Can you mention what they might be.

The only problem, what I see, is the timing problem.
If the theming don't apply at logon, there seems no way to get it started manually.
I never had this problem on a real PC but on some Virtual PCs, specially qemu.

You ever think of adding an auto changing Theme style on every reboot. Or is there a way to change the style once in the PE.

You can register themeui.dll (regsvr32 themeui.dll /s)
After this you can doubleclick an msstyle and apply it.

It should be possible with a batch file to randomly apply styles, running at RunOnceEx or Autostart folder

There is a nice utiliy on wuyou (the last attchment on the site) what can change Themes (by apply *.theme files)
This should also apply font settings

BTW: Some of my BartPE builds have working Themes without using the SystemSetupInProgrest patch.

I think everythink depends on the 3 files winlogon.exe, msgina.dll and shsvcs.dll

[TheHive]

There is a nice utiliy on wuyou (the last attchment on the site) what can change Themes (by apply *.theme files)
This should also apply font settings

The file contains 3 files.

++¦s.reg
++¦s¦-++.txt
ChangeStyleXP.exe

I tried putting a Theme in its same directory but it wont apply it. It gives a popup which I cant read.

[was_JFX]

hmm, was for a long time I used it.

try this one  ChangeThemeXP.zip   236.08KB   539 downloads

[TheHive]

The one you provide is in english. I tried testing it in PE and tried to follow the readme but I dont seem to be getting it.

You happen to be able to take some screenshot on how to get it working.

I saw the option in the gui to use the fonts used with the theme but where are the fonts folder suppose to be.Are they suppose to be in the same folder as the Theme. For example
SevenVG Black.msstyles
Fonts\
Shell\
Wallpaper\Dark_Aurora.jpg

[was_JFX]

The fonts have to been put in the %windir%\fonts folder

The shell folder allways have to be next to the *.msstyle.

The *.theme file is only a text file with the information for the ThemeManager.

It conatins the location of the msstyle and the wallpaper. The pathes have to match the location of this files and cannot be relative.

So easiest would be to put SevenVG Black folder and SevenVG Black.theme inside the Resources folder of your WinPe just like the Theme.exe from the SevenVG sytle would do

Then you could use to apply theme

ChangeThemeXP "%windir%\Resources\Themes\SevenVG Black.theme"

[TheHive]

Thanks for the info. Its very helpful in understanding how this works.


I believe the gui might need the ability to add font's from the Theme you choose to the Windir.

"fonts have to been put in the %windir%\fonts folder"

This would make it more complete.

Or is that what the option in the gui is suppose to do. Will this option move the font to the %windir%\fonts folder
Add Fonts used by Default Xp Style

If it is. Where are the fonts suppose to be compared to the mmstyles.
\SevenVG Black\Fonts
\SevenVG Black\Shell
\SevenVG Black\Dark_Aurora.jpg
\SevenVG Black\SevenVG Black.msstyles


The *.theme file is only a text file with the information for the ThemeManager.

Does the Script support selecting the *.theme file or does it only accept .msstyles file for "Custom MsSTyle"

[was_JFX]

Yes adding the fonts from the Theme would be nice.

But the big problem is that the default font settings are compiled into the *.msstyle

"Custom MsSTyle" only support *.msstyles. Support for *.theme would be a nightmare to implement by the amount of different settings it can have.

[TheHive]

I see. Not an easy task.