22 replies to this topic

[pscEx]

When preparing the release of WinBuilder 078, I made tests with LiveXP (minimum), LiveXP (recommended) and LiveXP (complete).

(I tried with download 'minimum' into an empty directory, then add 'recommended', then add 'complete')

Everything went well besides one issue which in my opinion really is a LiveXP issue (it does not occur e.g. in nativeEx_barebone)

When in (minimum) trying to shutdown the PE using StartMenu, system shuts down.
When in (recommended) trying to shutdown the PE using StartMenu, nothing happens.
When in (complete) trying to shutdown the PE using StartMenu, nothing happens.

For the users who want to hear my IMHO: Everybody knows that I do not like themes etc. And I'm sure that in (recommended) and (complete) there are a couple of them ...

BTW: Crazy idea: Currently maanu reports about 'voodoo' appearences in his PE. May it be caused by some scripts introducing some 'unusual' conditions ?
BTW2: @Lancelot: I do not want to reanimate our personal WW3 (which fortunatelly ended with 2 winners ), but maybe you read again, and emotionless my post about 'cooperating scripts'

Peter

[was_JFX]

I only know one develoopment script that can cause this problem

May take a look if msgina.dll is the renamed pegina.dll (20KB), which does the job from the Shutdown dialog.

No need to tell which one, cause it's not in the (recommended) and (complete) packages.

I only want's to a point to the .dll that runs the shutdown api.

[was_jaclaz]

I only know one develoopment script that can cause this problem

And are you gonna tell us WHICH ONE or we need to put you under torture?



jaclaz

[pscEx]

I only know one develoopment script that can cause this problem

May take a look if msgina.dll is the renamed pegina.dll (20KB), which does the job from the Shutdown dialog.

No need to tell which one, cause it's not in the (recommended) and (complete) packages.

I only want's to a point to the .dll that runs the shutdown api.

I'm not sure whether I understood your post completelly.
Therefore a simple question:

How to enable the shutdown functionality in (recommended) and (complete) ?

Peter

[was_JFX]

Well I'dont have an shutdown problems with today downloaded LiveXP recommanded.

But in a default LiveXP the shutdown is initiated through paraglider's PEGina.dll. May some filecopy goes wrong and you still have the normal msgina.dll insteed of the renamed pegina.dll?

[pscEx]

Well I'dont have an shutdown problems with today downloaded LiveXP recommanded.

But in a default LiveXP the shutdown is initiated through paraglider's PEGina.dll. May some filecopy goes wrong and you still have the normal msgina.dll insteed of the renamed pegina.dll?

I think that is not possible, because, as I explained, I did a download into a new directory. Therefore 'no remainders' and 'nothing known'
As a dummy user, I do not have any opinion on Paraglider's pegina or something else. Did I do something wrong?
Or does it depend on:

• download (minimum), change nothing but the source CD pointer and build >> shutdown ok
• after that download (recommended), change nothing and build >> no shutdown

???

If yes, there is not only something, there is A LOT wrong !!!!

Peter

[dera]

In LiveXP
in the script '\LiveXP\Apps\System\Registry\regshot.script'
in the line #62:
require_file,MSGINA.DLL

[pscEx]

In LiveXP
in the script '\LiveXP\Apps\System\Registry\regshot.script'
in the line #62:
require_file,MSGINA.DLL

Does that mean:

If Galapo / Lancelot do something, my issue from the first post is fixed?

Would be great.



Peter

[was_JFX]

Am I the only one, who doesn't like the taste that require_file overwrites an existing file?

[pscEx]

Am I the only one, who doesn't like the taste that require_file overwrites an existing file?

You really are not
Remember the private WorldWar3 which came up between me and a friend in Izmir when I mentioned such an issue in the log as warning!

Peter

[was_JFX]

Yeap, this was very funny one

As a neutral person at your WW3, how about using parameters:

require_file,MSGINA.DLL,OverWrite

require_file,MSGINA.DLL,NoOverWrite

NoOverwrite shoud be default option, Overwrite should only be used by script writers by good reason.

[pscEx]

That's possible inside WinBuilder with an additional parameter 'PRESERVE'.

But require_file is an API command outside the responsibility of WinBuilder.
And WinBuilder can only process the command the API delivers, either with or without PRESERVE.

Peter

[pscEx]

As a neutral person at your WW3, ...

BTW: Like said above, WW3 is finshed now with two winners ...

Peter

[Galapo]

My suggestion would be to have the api enhanced in the following way, then file preservation would be enabled by default and any overwrites would have to be explicitly specified:

[Expand_file1]

//Syntax==> Require_File,[Folder\]filename,[Source (if different of %Source_Sys%)],[Target(If different of %Target_Sys%)],[OverWrite],[PRESERVE],[NOWARN],[MUI Source (if different of parameter #2)]

Echo,"Copy or Expand  #1"

If,#4,Equal,,Set,#4,PRESERVE

If,#4,Equal,OverWrite,Set,#4,""

StrFormat,filename,#1,#9

StrFormat,path,#1,#8

If,|#2#3|,Equal,||,Run,%API%,Expand_1,#1,%Source_Sys%,%Target_Sys%,#4,#5,#6,#7,#8,#9

Else,Run,%API%,Expand_2,#1,#2,#3,#4,#5,#6,#7,#8,#9

Regards,
Galapo.

[Lancelot]

During capi development (which intersects times with the name psc gave recently "personal ww3") I asked pedrole to add a feature to capi for developers so copy file with api would give warning when file is overwritten, at that times pedrole also added same feature for registry overwrite by api which I also supported that times. Features existed in capi v3

But during capi development, this features removed (I dont know the reason) and I decide not to ask again....

Maybe after this topic pedrole may decide to put this features back !

With other words, What I specifically ask(ed) is "optionality" on api gui so "developers" can easly debug during tests when api used.



@psc

BTW2: @Lancelot: I do not want to reanimate our personal WW3 ......, but maybe you read again, and emotionless my post about 'cooperating scripts'

I remember "read again relevant post" posts written by me, I guess it is already understood this has no end, I write you "read again relevant post", you write me "read again relevant post".... Better no to write "read again" (or anything pointing the ww3 you mentioned) since it is proven this do not have any good result. With our peace agreement offered by you and agreed by me a while ago for the sake of wb development, I believe better not to write anything referring that times in order not to reanimate....etc.
ps: All looses during any war


@dera

Thanks

[Lancelot]

If Galapo / Lancelot do something, my issue from the first post is fixed?

fixed , new script uploaded (certification included )

[pedrole15]

If capi need ehancement ask clearly in corresponding topic

[Galapo]

Which topic? I have something to post there.

Thanks,
Galapo.

[maanu]

fixed , new script uploaded (certification included )

api script ? i mean which script i need to update ?

[Galapo]

I'd say this issue has only appeared with the introduction of the common api, which has file overwriting enabled by default. Old LiveXP api did not overwrite files:

[Expand_file]

...

If,Not,ExistFile,"#3\#4#5",Begin

...

Regards,
Galapo.

[F...youidontcareanymore]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"PowerdownAfterShutdown"="1"

OR

"APM ACPI"

OR

Microsoft System Management BIOS Driver

[pscEx]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"PowerdownAfterShutdown"="1"

Interesting reply
But the issue is here that the shutdown simply is not performed.
Therefore there is no 'After Shutdown'.

Peter

[F...youidontcareanymore]

Can you try;

>shutdown -l -s -f

logoff/shutdown/force

If that works, you have a hung app/dll