182 replies to this topic

[maanu]

thanks lancelot . i ll check it .

BUT im getting problems even with v 8 . there is no theme service in services tab written . although building pe ,did not give any error or warning .

and interesting thing is , i have already checked v 8 4 days ago and it worked fine . now i cant find that log file that what scripts were there and whch were not

i ll keep on trying , and will post log if any help needed ...

and inbox is clear now

[was_JFX]

News Version 11:

- lesser Warnings now with "EXISTREGKEY/EXISTFILE "
- fixed Security and FailureActions Regwrites

@jianliulin
Welcome here . Ok let's start me some questions

Who is the developper of the Themes stuff yichya or yamingw?
Is there a Themes working Version of 2003PE on wuyou forum?
And how do we use the Eject feature of PECMD? (Boot-land is very stoneage still using NON-RAM Booting solutions )

Thanks in advance

@Lancelot
Thanks for caughting bugs

@maanu
Please upload your log i will take a look at it.

[jianliulin]

@JFK

There is no development team in wuyou,all are who have the same Interested ,yamingw is Original Author of themes ,and yichya is the one of Practice Members ,

here is xpe with themes :
http://www.namipan.c...d5dab8c01cffb03

win2003PE and xpPE is no difference in the themes


EJEC :


format : EJEC [C-|U-|R:]

Function :Remove or pop-up USB disk or CDROM drive

Parameters : "C-" pop-up all CD-ROM drive

"U-" Remove all USB disk

"R:" pop-up or remove the drive letter designation or USB disk

No parameters will Remove all USB disk or pop-up all CDROM drive

Example: EJEC or EJEC C- or EJEC U- or EJEC H:




in china all winPE are based on pecmd

[was_JFX]

@jianliulin
Thank you very much, I will take a look at it.
Also will add yamingw and yichya to the credits of the Script

Ehm, If you mean LiveXP I guess you mean opposite (stoneage = "most modern")

You should not take this to serious, but here is more playing around with winbuilder and sript issue than actually improving the PE

Thanks for helping with the Script

@maanu

Let me explain the diffrence between WimPack and WimBoot

WimPack using normal Bootsdi and packing boot unneeded files in compressed WIM's
But it have a very dangerous option to Pack System32 folder, I highly disrecommand using this option, you only damage your PE

WimBoot is the most advanced RAMbooting solution today, it packing th hole PE in a WIM file and use it the same Way Vista and Seven using it.
Also WimBoot has the best Bootspeed and using the lesses RAM , the only think it doesn't allow NTFS junctions.

I cannot help you with the files needed for WimPack cause I never will use it. (Sorry)

Are there still problems with EarlyStarter

[Lancelot]

Hi JFX

I created a new topic (here) and moved related posts to this new topic, very sorrry for disturbance, I hope everything okey now

[was_JFX]

Thanks Lancelot

Main focus is get the theming running on every system, but may I have some idea for a third way of WIM-ification

[was_JFX]

Here comes Version 12

- compatible to Wimpack 'Pack System32' option
- New Option to use minlogon

With minlogon it works for me on every Virtual machine, but the boottime is very increased

If someone can gives me a hint what is missing for Win2003, I hopefully can upgrade the patcher to be compatible with 2003 version of winlogon.exe.

[was_JFX]

Version 13 Released

- fixed problem with shutdown / eject
- better minlogon support
- LogonBox can be removed (requires \Projects\Tools\Reshacker\ResHacker.exe)

Important XPThemes has to be extracted to \Finish\1 Optimizations to advoid problems with other Scripts

How to get minlogon:

- download XPeSP2FeaturePack2007
- open XPeSP2FeaturePack2007.iso with 7zip
- right click on XPEFP2007.exe select Open Inside
- browse to \rep and simply type minlogon on your keyboard
- Use drag & Drop to extract minlogon.exe

[MedEvil]

Works like a charm.

Since patching is considered nowadays legal again around here, how about extending the 24 hour limit to a almost 50 days limit?
Does anyone know, where the limit is defined these days?

[was_JFX]

Well til now patching was only be use to enable Themes

The needed file for 24h limit was already being patched 2 times.

But let's wait for someone who can clarify the situation.

[MedEvil]

The needed file for 24h limit was already being patched 2 times.

Are you sure? I think to remember that setupldr needed to be patched.

[MedEvil]

I'm still having timimg problems in VirtualPC.
Sometimes Theming works, sometimes it doesn't. With the same iso!

[was_JFX]

Are you sure? I think to remember that setupldr needed to be patched.

Well minlogon works so it was nothing to do with setupldr.

I would try it that way:

24 * 60 * 60 * 1000 = 86400000 millseconds

86400000 = 5265C00

5265C00  = 005C2605

005C2605 gives me only one occur in winlogon.exe



EDIT: Yeah we still missing a solution for the timing problem.

EDIT2: I was right with this patch, it just reboot with new given time

[fxscrpt]

Theory:
Something kills theming if not already startet.
And sometimes 'something' is faster then the service.
(maybe shell /themeui.dll?)

in conrast to real os ,if themes service is stopped, theming will never work again.
(i guess there will be no timing problem, if restarting the service will work in PE)






Peter

[MedEvil]

Well minlogon works so it was nothing to do with setupldr.

A real XP does not reboot after 24hours despite the fact that it uses winlogon.exe so acording to your logic, it can't be in winlogon eighter.

But you're right. I corrected my old textfile.

@fxscrpt
Yes, that theming can be started at boot up, but not anymore afterwards is really strange.

[was_JFX]

i guess there will be no timing problem, if restarting the service will work in PE

Yep, if we found a way to start the service manually, this problem would be solved,
and may this would be also the solution for Win 2003 PE's

BTW: If nobody say no, next Themes script will have a option the break 24h limit.

[MedEvil]

Do 'we' have any idea, why the service can't be started manually?

Not being able to start it during bootup, can come from the service not being allowed to be started due to missing registry settings.
But manually starting it, after switching systemsetupinprogress to 0, would not be affected by this.

[was_JFX]

Okay try new Version 14
- update PEGina to version 1.0.0.5
- optional increase of time limit



@MedEvil,
well sorry of course service can be started manually but theming cannot be started manually
'Me' don't have an idea, tryed this a long time without success

[MedEvil]

well sorry of course service can be started manually but theming cannot be started manually
'Me' don't have an idea, tryed this a long time without success

Ok, got this wrong. Thought theming meant theming service.

So theming service can be started, but still themes will not start working.

Is it just like that in BartPE+XPE?

[MedEvil]

When i stop the Design service and then restart it, it is shown in services as started.
But when i try to load a theme, i get an error message that the design service is not running and i should start it first.

So eighter services is lying and the service is not really running or the fact that it is running is not properly communicated through the system. ?

[maanu]

So eighter services is lying and the service is not really running or the fact that it is running is not properly communicated through the system. ?

well it is very much possible that it " lost in translation " by NOT finding the right strings that it needs to communicate with . thats the only reason it 'd say something like that .

i remember it happened once when i was messing around with avira (b4 JFX came up with his script ) , v 8 once complained about scheduler service not running , while it was running actually .

[Galapo]

Well til now patching was only be use to enable Themes

The needed file for 24h limit was already being patched 2 times.

But let's wait for someone who can clarify the situation.

I would say that so long as we don't distribute patched files that that's OK. Everything is up to the end-user and whether to make use of the script or not.

Currently on LiveXP there are options for patching various files. On the main interface of script.project, there is the option to disable all patching options if the end-user prefers not do this.

Regards,
Galapo.

[fxscrpt]

When i stop the Design service and then restart it, it is shown in services as started.
But when i try to load a theme, i get an error message that the design service is not running and i should start it first.
...

This check (design service running/not running) is imlemented in
themeui.dll's function QueryThemeServices.
The function should return 3 , if Themeing is enabled.

Remember :themeui.dll can block using unsigned themes.
Maybe files (luna.theme...) are classified as unsigned for PE?


Peter

[was_JFX]

@Galapo

Sounds good, giving end-user choice of patching. Could you add
'#$q%Core%\Finish\1 Optimizations\XPThemes\Themes.script#$q' to 'remove_patching_options' of LiveXP?

@fxscript

according to this Wine page is an undocumented function from uxtheme.dll

And also Process Monitor gives me this command when apply a style

rundll32.exe uxtheme.dll,#64 C:\WINDOWS\resources\Themes\luna\luna.msstyles?NormalColor?NormalSize

But the error messages in PE definitly comes from themui.dll

I also would say it's a communication issue between service an Theme Manager.

[Galapo]

@Galapo

Sounds good, giving end-user choice of patching. Could you add
'#$q%Core%\Finish\1 Optimizations\XPThemes\Themes.script#$q' to 'remove_patching_options' of LiveXP?

Sure. I'll add tomorrow.

I'm working on a few extra things at the moment.

Regards,
Galapo.