Jump to content











pscEx's Content

There have been 1000 items by pscEx (Search limited from 12-August 10)



Sort by                Order  

#76106 LiveXP -- Anything & Everything

Posted by pscEx on 27 August 2009 - 02:38 PM in LiveXP

yes, i have a slipstreamed winxp with sp2, here is my "hivesys.inf" : h**p://depositfiles.com/files/fq4h994ty


Last line of the file shows:

; Customized by nLite - www.nliteos.com


Looks like we found the reason! :frusty:

Sometimes here has been said that Winbuilder projects need original CD's, nlited ones cause troubles.

Please try an original CD.

Peter



#76127 LiveXP -- Anything & Everything

Posted by pscEx on 27 August 2009 - 04:03 PM in LiveXP

thanks PSC, i will check it out and update soon. thanks :frusty:

can i use manually slipstreamed version?

That's a question I cannot answer, becuse I do not know what the slipstream will change.

The standard way to build a PE with WinBuilder should be:
  • Use original source CD
  • Whatever you want to change, do by script, not by changing the CD
Peter



#76012 LiveXP -- Anything & Everything

Posted by pscEx on 26 August 2009 - 06:10 PM in LiveXP

@Neil:
It is high propable that the PE does not start correctly after errors during build.
(That is the reason that usually build stops after an error, but we switched that off intentionally to get more information).

Your description of boot errors does not help.

I now need the log of the build

Peter

BTW: To let 'Debug' on 3, does not affect your build in any way. It only causes that some files are not deleted.



#75690 LiveXP -- Anything & Everything

Posted by pscEx on 23 August 2009 - 09:28 AM in LiveXP

dear psc, the problem dose not seem to be with "Chinese Support script" at least in my case, even though i am not sure because as i already told you i am doing "hit and run" most of the time :) , i am assuming this because i don't understand Chinese. But anyhow while testing today i enabled "0804 Support" script which produced the same problem once again, well i might be wrong as i am facing some unique problems lately. :)

thanks for ur support :)

Both scripts write into txtsetup.sip something like:
IniWrite,"%TargetDir%\i386\TXTSETUP.SIF","NLS","AnsiCodepage",c_936.nls#$c936

IniWrite,"%TargetDir%\i386\TXTSETUP.SIF","NLS","OemCodepage",c_936.nls#$c936

IniWrite,"%TargetDir%\i386\TXTSETUP.SIF","NLS","MacCodepage",c_10008.nls#$c10008

IniWrite,"%TargetDir%\i386\TXTSETUP.SIF","NLS","UnicodeCasetable",l_intl.nls#$c0804

IniWrite,"%TargetDir%\i386\TXTSETUP.SIF","NLS","DefaultLayout",00000804
That means they change your default Western properties to something Chinese.
For a standard English build the result is unpredictable.

Peter



#74657 LiveXP -- Anything & Everything

Posted by pscEx on 14 August 2009 - 08:16 PM in LiveXP

Tomorrow I'm going to make nativeEx 99% quote-free (some quotes, e.g. in ShellExecute parameters or Echo, Message with spaces inside, are syntay demanded!)

Done!

Now nativeEx is as quote-free as possible.
See in the nativeEx forum.

Peter



#76309 LiveXP -- Anything & Everything

Posted by pscEx on 28 August 2009 - 05:32 PM in LiveXP

A small hint @our new .script developer:

Since a while WinBuilder has a command:
System,GETFREEDRIVE,%var%
:frusty:

Peter :rofl:



#76316 LiveXP -- Anything & Everything

Posted by pscEx on 28 August 2009 - 06:19 PM in LiveXP

:frusty:

Peter



#79809 LiveXP -- Anything & Everything

Posted by pscEx on 25 September 2009 - 08:49 PM in LiveXP

i really don't want to join to yours personal World War

just want to notice:
on Vista host i have problem not only with vdk or vdk_WB

so my experience is that:
when once i stop the service - on Vista host- then
i am unable to start the sevice again in the same boot session

Can you explain a bit more in detail?

Maybe describe step (command) by step.

That would be helpful.

BTW: Vista Host x86 or x64? (or both?)

Thanks

Peter



#79796 LiveXP -- Anything & Everything

Posted by pscEx on 25 September 2009 - 07:34 PM in LiveXP

Just a reminder:

Is it possible to change everything to 'our home-made' imdisk, like I did in nativeEx?


And look at your answer.

What are we doing here:
  • In the community trying to develop usable projects?
  • Moving reproaches forwards and back?
Looks like the second case, so I think that in the future I have to concentrate on WinBuilder, nativeEx, NaugtyPE, YahooUk's Win7PE and Win7RescuePE, and to ignore LiveXP

Peter

BTW: Whenever I see 'read carefully' (maybe with hundreds of links), I close every trial to understand the partner's intention.

Reason: He just tells me that I'm a fool not even able to understand some written text.

'Read careful' topic closed for me. This reply has been only a trial to tell the forum, that I am NOT a fool.

Peter



#78706 LiveXP -- Anything & Everything

Posted by pscEx on 16 September 2009 - 08:00 PM in LiveXP

does not mount vdi image if you select both vdi and vmdk image to mount.

Thanks for the hint. I'll hold it in mind as 'low priority feature request' for this script.
(Or do you need it urgently?)

Peter :unsure:



#78682 LiveXP -- Anything & Everything

Posted by pscEx on 16 September 2009 - 05:51 PM in LiveXP

Hi all,
i cannot run iso in emulators (Finish\3 Emulation) because of empty %burnISO% variable.
in CreateIso.script corresponding IniWrite is uncommented. :unsure:

Replace %burnISO% by %IsoFile%.

%burnISO% is history and now no longer needed, because WinBuilder itself sets %IsoFile% from [Main]IsoFile in script.project

BTW: The newest VirtualBox emulate script does not contain %burnIso%. Therefore it can be used also inside the Vista / Win7 world

@Lancelot: Maybe some scripts in LiveXP should be revised.

I'll do so with nativeEx.

Peter



#74407 LiveXP -- Anything & Everything

Posted by pscEx on 13 August 2009 - 07:46 AM in LiveXP

Do we have a Bug in XPE DirectX Script?

Line 1407 gives me a Regwrite error, guess caused by missing quotes.

RegWrite,HKLM,0x3,"Tmp_software\Classes\DirectShow\MediaObjects\dafd8210-5711-4b91-9fe3-f75b7ae279bf","InputTypes","61,75,64,73,00....
Should be
RegWrite,HKLM,0x3,"Tmp_software\Classes\DirectShow\MediaObjects\dafd8210-5711-4b91-9fe3-f75b7ae279bf","InputTypes","61","75","64","73","00"....


Correct would be to remove all quotes. The single quotes around the single binary values are currently still tolerated by WinBuilder. But who knows how long ...

First some rules:

  • WinBuilder Script Line Parameters are separated by a comma.
    If a comma is inside an argument, it must be 'escaped' by #$c
  • Besides some special cases (e.g. parameters in ShellExecute) generally enclosing quotes are not needed.
  • Enclosing quotes MUST be used if the WinBuilder Script Line Parameters contain spaces
    If the spaces are replaced by the escape #$s, the enclosing quotes should be ommitted.
In most cases user violation of that rules are accepted by WinBuilder and processed as assumed.
E.g. unnecessary enclosing quotes or a comma inside an item enclosed by quotes.

But sometimes that can bring unexpected results.


Peter

BTW: The Magic Wand delivers:
RegWrite,HKLM,0x3,Section,Key(Binary),00,01,00
Why so many people neglect this, use quotes and report an error, and somebody else 'fixes' the error by a new error, ... :idea:



#74266 LiveXP -- Anything & Everything

Posted by pscEx on 11 August 2009 - 03:56 PM in LiveXP

@olegpov
ps: thanks for "16 characters long" info

@olegpov
My thanks, too, that you brought my idea about PWD lenght ranges to the knowledge of the project's admins.
Looks like not to be seen here if it is only a post by me fool ...

Peter



#75950 LiveXP -- Anything & Everything

Posted by pscEx on 26 August 2009 - 07:31 AM in LiveXP

hi lancelot and all,

i tried the build on my friends DELL laptop with WinXP with Sp2 (32-bit), i am getting stuck at "HoJoPE Hives Factory" i am getting the following error:


i did a search and found that the PSC in the post what usually causes these types of build errors, trouble with livexp build suggested to clear the Reghive. So, i did a manual search and but found nothing. Also i found that in WB there is an option to clear the Reghive i used it, cleared temp files and restarted WB, but i am still receiving the same error. the version of my "HoJoPE Hives Factory" is v.63. what should i do? :D

--EDIT--
Sorry, here is the log "hxxp://depositfiles.com/files/3efy6ao9m"

Can you please set 'Debug' in 'Basic > !WbManager > Define Fundamentals' to 3 and then post zipped
hojoPE-setupreg.hiv_0409XPSP2BB2.Script.txt

Peter



#73790 LiveXP -- Anything & Everything

Posted by pscEx on 05 August 2009 - 10:09 PM in LiveXP

ok now i m using WB077 RC2. but this time i am receiving the following error:

Errors:

 "Please decide for either Explorer, Xoblite or CMD script"


This only should happen, if you either
  • Did not select any shell script
  • Selected more than one shell script.
If you selected no shell, please select 'Explorer'
If you selected several shells, please only select 'Explorer'
If you selected only 'Explorer' and got this Verify message, something unknown may be wrong.
Then disable Basic > WBManager > Verify, build the project and post the log.

Peter

BTW: A short test maybe helps:
Download NativeEx_barebone_077_RC2', nativeEx_core_077_RC2' and 'Tools' from the nativeEx server and build a PE with them, using WinBuilder 077_RC2

If that works, the troubles are caused by your local LiveXP installation, and you should renew it.
If that does not work, the troubles seem to depend on your local installation, and we have to check in detail.

Peter



#70956 LiveXP -- Anything & Everything

Posted by pscEx on 02 July 2009 - 08:01 PM in LiveXP

Would be nice if some people read AND UNDERSTAND release notes :lol:
Peter

BTW: The 'Wrong' syntax possibly is correct if this logic is intended by the script's author (provided the script's author knows the syntax and knows what he wants to do).
It makes as 'much' sence like writing an Else standelone w/o preceeding If.
The 'Wrong' syntax is only not usable for the here wanted purpose!
So to present this syntax as 'wrong', may confuse unexperienced users and MUST be avoided.



#70894 LiveXP -- Anything & Everything

Posted by pscEx on 02 July 2009 - 10:38 AM in LiveXP

That's a real issue! :lol:
Remove implies Close, so no need to do both.
BTW: I do not understand why to 'not remove'.
Here is a special WB_VDK running (with different service name etc.) and not longer necessary from now on.
It can NEVER affect a running 'standard' vdk.

But might be possible, there is a logical issue, too:

In [Variables] there is the definition:
%BootSDI-VdkExe%=%Tools%\vdk\%root%.exe
When [Variables] is read, %root% is undefined, and later defined by:
If,%architecture_test%,Equal,0,Set,%root%,vdk_wb

If,%architecture_test%,Bigger,0,Set,%root%,vdkx64\vdk
Then the 'final' definition is made:
Set,%VdkExe%,%BootSDI-VdkExe%,GLOBAL
Where propably the %root% in %BootSDI-VdkExe% still has an invalid value.
Propably means, that ;) may occur. Sometimes everything is ok, sometimes there is a failure. That depends on history in the build.

For those purposes the command
System,REBUILDVARS
exists. See it's explanation in the 075 beta release notes.

Peter



#70279 LiveXP -- Anything & Everything

Posted by pscEx on 22 June 2009 - 09:48 AM in LiveXP

No, I can't reproduce with example
The variable lost is %API_TYPE%
I have add a warn each time this variable is reset now in Common_Api (redownload it for test)
Variable is lost first time during MMc.script
and a last time just before HWPnP.script

You can test by running the single script MMC

Thanks, that has been sufficient.

I found the bug and fixed for WB 077 RC 2. ;)

On exit, the Exec command deletes the current variables.

That has usually been no problem, because the variables are rebuilt when they do not exist.
But variables Set with 'GLOBAL' option are lost because they are only in memory ... ;)

This bug exists since 076, but hasn't recognized before.

Maybe some voodoo appearently caused by Regfactory disappears with this fix. :)
Regfactory uses Exec very much ...

Peter



#73863 LiveXP -- Anything & Everything

Posted by pscEx on 06 August 2009 - 07:44 PM in LiveXP

I give up!

For me it looks like that you did not even read my previous post, rather than to try what suggested.

Please have a look at the Forum Rules.

Peter



#73907 LiveXP -- Anything & Everything

Posted by pscEx on 07 August 2009 - 11:03 AM in LiveXP

i am sorry i made you feel that way, well its my mistake that i didn't reply properly and i am sorry for that this is what i did...



i tried it twice but each time it resulted in producing an 67mb even though i had selected all most all application when i tried booting it, it displays the boot screen and then it would show as lsass.exe Application error stating "the application failed to initialize properly (0xc0000142)..." and then it reboot.
the fact that its was producing a 67mb iso was my reason to believe that there was some problem with my local LiveXP installation, as tried again and again cleaning the temporary file and checking all the options in the WB wizard but the result was the same.



i am still in the process of downloading the files for the project NativeEx, so till it completes i tried using the backup copy of live xp and it worked except that it is producing errors as mentioned previously. once the download is complete i will provide u with the results. and plz try to understand i didn't meant any disrespect its just that i am anxious to have an full working copy of live xp. and i am sorry for it...

i hope u understand :P

Accepted :idea:

Next time, please give such explanations, and do not just post new (surprizing) results!

Peter



#74152 LiveXP -- Anything & Everything

Posted by pscEx on 10 August 2009 - 02:56 PM in LiveXP

I hope that somebody can give a post about the allowed length range of the PWD here

Peter :idea:



#74117 LiveXP -- Anything & Everything

Posted by pscEx on 10 August 2009 - 08:07 AM in LiveXP

What am i doing wrong that's making u guys so angry? :idea:

Not really angry, but a bit disappointed.

Sample: The font issue with the Chinese Support script.

Would have been nice if you would have posted here that adding of this script to your (English) project caused the issue.
Such a post could help other users with the same issue.

Peter



#74096 LiveXP -- Anything & Everything

Posted by pscEx on 09 August 2009 - 09:32 PM in LiveXP

Nice to hear that everything is ok now, inspite nobody knows why.

I think that you do not need further help by me.

Peter



#73936 LiveXP -- Anything & Everything

Posted by pscEx on 07 August 2009 - 07:11 PM in LiveXP

peter, as u suggested i downloaded NativeEx_barebone_077_RC2', nativeEx_core_077_RC2' and 'Tools', when i run the project with the default options every thing works great but when i select all the options and try to run it, the following error is thrown :

Generated by psc program 'WBVerify' version 2.2.3

  Date: 2009-Aug-07 16:53:43

  

  [Counts]

  Missing=0

  Obsolete=0

  Errors=1

  Warnings=0

  

  Errors:

  "When excluding MiscSettings.Script, FixShellWinlogon.Script and ShellSecurity.Script, you must uncheck 'Don't set Explorer as shell' in Explorer.Script"

but when i checked i checked NativeEx_barebone>Basic>Shells>Explorer the option Don't set Explorer as shell' in Explorer.Script" is already unchecked. what should i do next?

so i restarted WB this time when i tried to execute the script i got:

FileRename - Failed to rename file: [%BaseDir%\Target\nativeEx_barebone\I386\WinSxS\manifests\CONTROLS.CAT] to:[%BaseDir%\Target\nativeEx_barebone\I386\WinSxS\manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.CAT]

Looks like that the 'factory settings' of nativeEx_barebone bring a booting and working PE.

That proofs that generally your local host configuration does not cause your troubles.

But it is NEVER wise to 'select all the options'. And here WBVerify tells you that something is wrong.
I do not know what 'select all the options' in your installation means. But when selecting or deselecting a script, the user always should know what he intends. Just to have 'all options' is the worst intention.

Rename-Error: Because I do not have a log, it is impossible for me to say anything to this issue.
Currently I do not find a script in nativeEx_barebone, where this Rename is done.

EDIT: I found it in the Exyplorer script. Maybe I have to adjust this script (also due to the verify issue with FixShellWinlogon.Script and ShellSecurity.Script, whiche are not in nativeEx_barebone). Currently it is the same like in LiveXP, in order to be syncronous.

Peter



#79812 LiveXP -- Anything & Everything

Posted by pscEx on 25 September 2009 - 09:08 PM in LiveXP

sorry,

forget to mention the details

i tried only on Vista x86 host

using the script there is no problem
as it doesn't stop the sevice

Now I really have a PROBLEM ( compare with my signature)
I do not understand what you are trying and what happens:

when once i stop the service - on Vista host- then
i am unable to start the sevice again in the same boot session

Under Host?
Under WinBuilder?
Inside the PE?

Maybe it is a feature Billy the Door gave us?

Peter



#80386 LiveXP -- Anything & Everything

Posted by pscEx on 30 September 2009 - 11:59 AM in LiveXP

(or maybe am i impatient and should wait more time,
in WB078SP1 i didn't noticed such issue,
or simply the new bootsdi.script the new api or the new script.project makes this?)

I built a fresh downloaded LiveXP using BootSDI.
During processing of BootSDI, Taskmanager showed Explorer.exe using 50% of the CPU.

qEmu did not come up, and now since about 5 minutes Explorer.exe uses 99% of CPU.

Both CPUs are on 100%, inspite WinBuilder claims to use only one.

If you have a backup from the WB078SP1 time, try that with WB078SP2

Peter



#87568 LiveXP -- Anything & Everything

Posted by pscEx on 22 December 2009 - 06:41 PM in LiveXP

Thanks psc,

now also on LiveXP server,

btw, knowing the reason of your change, I like your previous avatar more :cheers:

besides, your avatar is the boot-land most famous modified avatar ever :merc:

The new avatar is introduced by Allanf as his personal avatar.
Maybe he has some intention to show the world how to "delete" me.
And to give the world the possibility to decide, I now use this avatar.

And I have no worries to use it. Looks nice (inspite the motive changing is not the best. Could be more professionally. For me it seems to be just a WEB-download of the first GOOGLED file.)
If I personally would try to attack using an image, i would search more professional URLs.
On the other hand I also have no worries to go back to the original avatar, when Allanf explains.

Peter



#87582 LiveXP -- Anything & Everything

Posted by pscEx on 22 December 2009 - 08:00 PM in LiveXP

As known, I do not take care on "Themes", "Avatars", "Styles".

I'm fixed on contents and facts.

And my new avatar is only a reaction to something emotional, aggresive, but not technical based issue in this forum.
I can change tomorrow back to the old one if I see a reason.
I can change tomorrow to a different new one, if I see a reason.
I can give the responsibility for WinBuilder development to somebody, if I see a reason.
But here to see a reason, I need some explanations about A.....'s developer's quality.
Currently I do not feel some developer's qualification.
Currently I have the feeling about having him an opinion like:

"If something is not working like I assume, it is not necessary that I look into my code. It is surelly a bug in the app I use".


Peter :merc:

BTW: Please ICQ or PM me the modified avatar. I like it :cheers:
And I will replace (If I see a reason.)

Peter



#82265 LiveXP -- Anything & Everything

Posted by pscEx on 21 October 2009 - 08:11 AM in LiveXP

Well, you know my english is not very good, I tried, Better JonF or others explains things which I may have diffuculty to explain.

THis time I understood the issue completelly ;)

Peter



#82227 LiveXP -- Anything & Everything

Posted by pscEx on 20 October 2009 - 06:31 PM in LiveXP

try 450 ;)

Seems to me it is the known issue (informed by you before) about space calculation with vista ntfs6, you know we dont have a precaution on bootsdi yet for ntfs6 which results size calculations mismatch on vista's ntfs6.

@Lancelot, @JonF
Depending on having 'hundred' of topics, I sometimes oversee some (maybe) important posts.

Is this one of them, which could be solved by WinBuilder logic? (Of course, the size is no issue)

Or is it just an (project) issue you already solved?

Peter



#81379 LiveXP -- Anything & Everything

Posted by pscEx on 10 October 2009 - 08:46 AM in LiveXP

If,EXISTDIR,%ProjectTemp%\Include,ShellExecute,Hide,"%Tools%\Wim\uumerge\uumerge.exe","-merge -nice #$q%ProjectTemp%\Include\*.txt#$q #$q%ProjectTemp%\IncludeFolderList.txt#$q"
but i dont know the reason ! :thumbsup:

What is when the directory exists, but there is no *.txt.

Peter



#88978 LiveXP -- Anything & Everything

Posted by pscEx on 17 January 2010 - 05:47 PM in LiveXP

@ JonF: You seem to have a 'special configuration'.

Can you try nativeEx_barebone's BootFromRAM and CreateISO script?

Peter



#89089 LiveXP -- Anything & Everything

Posted by pscEx on 19 January 2010 - 01:17 PM in LiveXP

The 'log is lying' is already fixed and will be available next SP

@Lancelot: This is new knowledge after our discussion:
In the 'Complete' download of LiveXP made some minutes ago there are not 'many scripts' like we agreed.
There are only 3 scripts using a comma in the Set command:

Basic\Build\0 - OnProjectRun.script[AddWowCheck] Author: Lancelot
Set,%APISUBDEF%,"%APISUBDEF%,Arch",PERMANENT

Basic\Build\8 - FIPS.Script[process] Author: psc, following lines added by Lancelot
Set,%DisplayNameForWBSoftware%,"System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing"
Set,%DisplayNameForWBSoftware%,"Systemkryptografie: FIPS-konformen Algorithmus für Verschlüsselung, Hashing und Signatur verwenden"

Basic\Build\9 - DefineBootsector.script[Process-grub4dos] Author: Galapo
Set,%MenuAdd_GRUB%,"Exec,%ScriptFile%,Add-grub4dos-entry",PERMANENT

I think the easiest way is when we do not manifest on "Worked somewhen" but follow the actual convention and
  • These three scripts are changed and the comma is replaced by the escape #$c
  • In the future no .script developer uses a written comma inside ONE argument
This brings the advantage that 'as a miracle' WB078SP6 can be used and works like the 'official' old fashioned wb077rc2.
I personally trust on miracles, inspite sometimes some people have to spend some minutes of work in order to make the miracle possible.

Peter



#123033 LiveXP -- Anything & Everything

Posted by pscEx on 22 February 2011 - 09:10 AM in LiveXP

Appearently during shortcut generation has %PDRIVE% the value 'B:' (Check with Echo,%PDRIVE%), and that is inserted.

If you want to write the string '%PDRIVE%', you have to use escapes:
Add_Shortcut,Desktop,,,,,,"#$pPDRIVE#$p\portables\%ProgramEXE%"

Program Files <> Portables:

Did you define
[variables]

%ProgramTitle%=???

%ProgramEXE%=???

%ProgramFolder%=???

Correctly?

Peter

EDIT: BTW your syntax defines the icon for the shortcut.
I think you want to define the exe.
That is
Add_Shortcut,Desktop,,"%PDRIVE%\portables\%ProgramEXE%"
or
Add_Shortcut,Desktop,,"#$pPDRIVE#$q\portables\%ProgramEXE%"
resp.
Take care of the TWO commas!

Complete Syntax:

Add_Shortcut,[Type],[Folder],[FullFileName],[Title],[Work Folder],[Parameters],[IconFile( .ico .exe)],[StartMode(1, 2, 3, or 4)]




#89111 LiveXP -- Anything & Everything

Posted by pscEx on 19 January 2010 - 11:00 PM in LiveXP

Did you try what I reported here
If yes, what was the result?
If no, issue closed for me.

Peter



#89095 LiveXP -- Anything & Everything

Posted by pscEx on 19 January 2010 - 04:59 PM in LiveXP

I was just asking if this was the intended Syntax or not (i.e. a "by design" feature).

Sorry that I misunderstood you!

I cannot tell you which syntax is 'intended'. It is from 'ice-age'.

The only thing I now is that in the mean time I added a lot of code to allow the exception 'comma allowed if it is inside quotes' and a lot of exceptions of this exception, and a lot of exceptions of exceptions of ...

And I still do not really know why the #$c escape has been introduced inspite it seems to be possible to live without it, just by setting stupid quotes

Peter :confused1:



#89091 LiveXP -- Anything & Everything

Posted by pscEx on 19 January 2010 - 01:57 PM in LiveXP

As an outsider, and complete n00b, can I ask a question? :)

  • To separate arguments in Winbuilder .script Syntax the "comma" symbol "," is used.
  • Thus you cannot include the "comma" symbol ANYWHERE else, not even in double quoted strings, and you need to use a replacement "#$c".

Is the above correct? :rolleyes:

Wonko

It is only my opinion, too.
But whether it is correct, is decided by the majority ;)

Peter :confused1:

Maybe Wonko the Sane should get a brother Clippy the Sane ...



#81225 LiveXP -- Anything & Everything

Posted by pscEx on 08 October 2009 - 11:35 AM in LiveXP

I think that here are a couple of opinions passing the reality. :thumbsup:
That is mainly my fault, because I did not explain clear enough.

Therefore here a trial to explain:
http://www.boot-land...?...ost&p=81223

Peter



#81179 LiveXP -- Anything & Everything

Posted by pscEx on 07 October 2009 - 03:17 PM in LiveXP

I currently do not remember why in the latest changes I again found %burnIso% to be necessary.

I'll check.

But one is true: The current nativeEx works well with the new constellation.
E.g. there is
StrFormat,FILENAME,%IsoFile%,%tmp%

 StrFormat,EXT,%tmp%,%ext%

 StrFormat,REPLACE,%tmp%,%ext%,,%tmp%

 Set,%ISORootName%,%tmp%,PERMANENT

 Set,%RamISORootName%,%tmp%_RAM,PERMANENT
These variables are only set ONCE and used by all 'Finish' scripts.
That will eliminate JonF's 'multi-ram' issue for ever.

BTW: The reason that I made these changes, was in JonF's 'multi-ram' post.

Peter

EDIT: When any script changes %IsoFile%, we are on the best way to get the JonF issue!!!



#80848 LiveXP -- Anything & Everything

Posted by pscEx on 04 October 2009 - 05:08 PM in LiveXP

@psc
thanks gain, new flag of livexp is BOOTFLAG :D

Please PM me where exactly you changed what?

Then I'll syncronize nativeEx.

Peter :D



#80752 LiveXP -- Anything & Everything

Posted by pscEx on 03 October 2009 - 01:50 PM in LiveXP

In the last few days, my LiveXP builds have grown some errors. The resulting ISO works. BUt I don't like errors. Rebooting, different source, whatever I try doesn't affect the errors. WTF?

In WinBuilder click Tools > Options and uncheck 'Debug Log' in the middle right.

When this option is checked, all warnings and file deletes are shown.
Also 'scheduled errors' which are usually suppressed by System,ErrorOff

BTW: unchecking 'Log Original Statement' makes the log much smaller and better readable.

Peter



#80055 LiveXP -- Anything & Everything

Posted by pscEx on 27 September 2009 - 06:45 PM in LiveXP

AFAIK REMOVE the driver is ok, even under Vista.

Only STOP brings this issue.

What is the reason to avoid the use of REMOVE?

Remember that my changes do not remove any existent 'usual' vdk driver. The remove is only due to vdk_WB.

Moving the driver to a different location is a good workaround, but it does not solve the issue itself, that under Vista there are these troubles with STOP / START or OPEN again.

Peter

BTW: I suggest to continue the discussion in the new VDK topic Jaclaz created. This is neither a question of LiveXP nor a question of BootSDI.

It is a general question of vdk due to different operating systems.



#80031 LiveXP -- Anything & Everything

Posted by pscEx on 27 September 2009 - 02:59 PM in LiveXP

the problem begins only in that case when you also open an NTFS formatted image

Or is it:
the problem begins only in that case when you also open an NTFS Compressed image.

See: http://www.boot-land...?...ost&p=37399

Peter



#80992 LiveXP -- Anything & Everything

Posted by pscEx on 05 October 2009 - 06:56 PM in LiveXP

there were 0 files in it .

and yes thats what i did . i cleaned temp files and then tried super floppy option .

edit :

isn't the following supposed to be the right selection for using bootsdi with 2k3 files >?

...
it is telling me this ,



and i have seen in help but... :D

it has exactly the same scripts as in my last post . only selected 2k3 instead of firadisk


@Galapo. @Lancelot:

I can understand the troubles coming up here: Let me exaggerate: To use all the possible options of BootSDI script correctly, you have to study first for two weeks at the 'LiveXP university'. And the 'Help' button is not really a help. It only describes how to define a certain constellation.

I think that is not conforming to the sence Nuno had in mind when founding WinBuilder: "As simply as possible, and the first user should have a success w/o defining options"

Maybe it is possible, to divide the compound scripts into different single scripts excluding each other by using the WinBuilder's feature 'Disable'

A big compound script IMHO in most cases can only be used by experienced users. And I think, that about 28000 of our 288?? users are not experienced.

Peter



#81058 LiveXP -- Anything & Everything

Posted by pscEx on 06 October 2009 - 07:35 AM in LiveXP

Maybe we could have a new 'Enable' option which does the opposite of 'Disable', ie it enables listed (default) script dependencies? This would be one way that we could more consistently make sure the end user has necessary scripts selected. (Trouble is, sometimes it's not just a script itself which needs to be selected, but also an interface option, so not sure how far we should go with this.)

The 'Enable' to just select exists since a long time. Isn't that 'Dependencies'?

Due to the options: I think that we already have something similar: !WBManager.Script
It selects / deselects scripts and sets / changes interface options.

I could make a modfication that it, besides recording the complete project, can record a list of scripts.

Peter



#81146 LiveXP -- Anything & Everything

Posted by pscEx on 07 October 2009 - 07:20 AM in LiveXP

Thanks for reporting, I hadn't gotten around to testing if the issue was still there.

Peter will have to tell us whether it is a bug with '1 - ProjectInfo.Script' or if the problem lies elsewhere.

Regards,
Galapo.


Compare with nativeEx.

Last days I made a big consolidation about %IsoFile%, %RAMIsoFile%, %BurnISO% etc.

look into the scripts' history for 'consolidation'

Peter



#81097 LiveXP -- Anything & Everything

Posted by pscEx on 06 October 2009 - 03:34 PM in LiveXP

:lol: when/if you find sth reasonable things goes pretty quick with you psc, there are also many examples. If you dont find sth reasonable, than xxx, there are many examples :hypocrite: The issue mostly is not about the reasonable of the request, %95 it is (proof: all added later in time), hard part is making you see the request reasonable when you did not :frusty:
now, but will reply as quick as possible).

The main problem issue here is that I in some cases have a different education / business practice etc. than other members.
And therefore the decision for 'reasonable' may be different.

When a "Peace" made between emotional and respective humans, it is wise not to remind old times to each other. After a while of our "peace" agreement i notice you start unlogical (to me) wwx remindings which triggers my emotion reminding you to read carelfully. And if you exaggerate as an emotional human which happens sometimes, Better to draw the line for the goodness of boot-land. Rest is up to you.

<_<
(BTW: My mentioning of WWX was the -appearently wrong- explanation that my post was not trying to confrontate)

Peter



#81091 LiveXP -- Anything & Everything

Posted by pscEx on 06 October 2009 - 02:31 PM in LiveXP

..., still one left waiting another user than me requesting .

Generally I do not postpone reasonable requests / suggestions of a member I'm currently have discrepances with! :frusty:

Please tell me the request / suggestion I missed. And please, do not write (see next topic) <_<

Maybe time to start reading things carelfully which would prevent any wwX !

I'm an emotional human, and the suggestion "reading things carelfully" can bring me to start wwX! :hypocrite:

My day has 24 hours, and inspite I sometimes use the night additionally, I have some troubles to read everything in a topic:

... and BTW a technically oriented mind should refrain from even peeking inside a thread:


LiveXP -- Anything & Everything
Look only Post #1 and Last Posts of this topic

which is clearly, from the title itself, a kind of blog, an unreadable series of unconnected items mixed together and shaken well. (which is BTW a pity, since the contents are often interesting, but they are simply unorganized in such a way that they become useless.

Peter



#81079 LiveXP -- Anything & Everything

Posted by pscEx on 06 October 2009 - 12:23 PM in LiveXP

It's fine to delete the ISOs that LiveXP created in ISODir. It's not OK to delete files that LiveXP did not create.

I for 100% agree with JonF!

Like in this case in many scripts there is no respect to 'What has been done by something / somebody else previously'

Remember the beginning of "World War 3', when I posted about 'cooperative scripts'

Maybe we again think emotionless about the sence of that post.

Just to explain for this case:
"Also delete %ISODir%" should be uncheckedin factory settings.
And there should be the text
"Also delete %ISODir% (not recommended)"

It is not a good way to heal an illness (something left from a previous pass) by hiding the symptoms (delete everything)

Peter



Peter



#70251 LiveXP -- Anything & Everything

Posted by pscEx on 21 June 2009 - 07:08 PM in LiveXP

... after a exec command


I'll check.

Can you try to write a simple script to reproduce?

In process just one line, then do an exec, and when back in process, echo the variable which is lost?
Or is the variable unknown inside the exec?

Peter



#70223 LiveXP -- Anything & Everything

Posted by pscEx on 21 June 2009 - 01:19 PM in LiveXP

I dont like these log lines:

RegWrite - root key&#58; &#91;HKLM&#93; Type&#58; &#91;0x1&#93; A file was not chosen from&#58; &#91;WB-Software\Microsoft\Shared Tools\MSInfo\Categories&#93;

 RegWrite - root key&#58; &#91;HKLM&#93; Type&#58; &#91;0x1&#93; A file was not chosen from&#58; &#91;WB-Software\Microsoft\Shared Tools\MSInfo\Templates&#93;

 RegWrite - root key&#58; &#91;HKLM&#93; Type&#58; &#91;0x1&#93; A file was not chosen from&#58; &#91;WB-Software\Microsoft\Shared Tools\MSInfo\Toolsets\MSInfo&#93;

Fixed.

Has been wrong message number 2178 instead of 2078!

Peter



#65698 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 01:40 PM in LiveXP

BTW: Maybe it is now time to again think about my topic 'LiveXP - Factory settings'. It is really not the best idea to include 'Everything selected' :)

On the other hand, we catch network bugy with that :) :)

Maybe someone can explain me this logic:
  • Put a couple of unneeded scripts into a project:
    A certain script fails
  • Remove the unneeded scripts:
    The previously not running script now runs
  • Tell the world: Introducing the bug gave me the possibility to fix it!
    Everything is running now, and nobody knows why!
@ALL
Please tell me, who needs (and for what) the scripts
  • VirtNet Network Adapter.script
  • VMWareNIC.script
    (VirtualBoxNIC_AMD_PCNET.script delivers a VMWare Ethernet Driver, look at the description)
Peter



#65707 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 02:30 PM in LiveXP

Here the shell folders created under nativeEX_barebone:
shellfolders.gif
?
:)
?
or a new 'conflict of interests' by some LiveXP scripts which do not like each other?
?

Peter



#65693 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 12:59 PM in LiveXP

Congratulations! :)

Now there is the same configuration like in (the allways 3-emulators ready) nativeEx_barebone. :)

Peter

BTW: Maybe it is now time to again think about my topic 'LiveXP - Factory settings'. It is really not the best idea to include 'Everything selected' :)



#65690 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 11:42 AM in LiveXP

fxscrpt

new mmc on server :)

on nativeEx server, too!

Peter



#65646 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 09:03 PM in LiveXP

not sure about the meaning of filled out

Ask babylon for [German] ausfüllen.
Here we have the lack of (our both) English knowledge.
Your Computer translations are correct.

It means: Write into the empty, predefined text box.

And simply: "define value"

Peter



#65709 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 02:42 PM in LiveXP

WOW!!!!

Here the Turkish Shell folders:
shellfolders_TR.gif

You should learn German if you need the AppData key!

Peter :)

Currently no idea where to search, but I start to search! :)



#65715 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 02:56 PM in LiveXP

Testing with enu is much easier for me :)
And the EaryStarter is the latest one I got from LiveXP!

Maybe something has been mixed. Thanks!
OR: You downloaded at the wrong time.
I made several tests with new genUpdates, and the test candidate has been EarlyStarter. Maybe you jumped in the middle of the test session. Just try to redownload EarlyStarter again.

Peter



#65760 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 06:19 PM in LiveXP

Thanks Lancelot!

i'm out now, but firtst:
WB077b1 BootSDI bug found (i hope)
this code

//_Calculate,&#34;Ceiling&#40;DirGetSize&#40;&#39;%TargetDir%&#39;&#41;/100*%pNumberBox2%/1048576&#41;&#34;,ImgSize

 Retrieve,FOLDERSIZE,%TargetDir%,%ImgSize%

 message,%ImgSize%,information

 StrFormat,DIV,%ImgSize%,100

 message,%ImgSize%,information

 StrFormat,MULT,%IMGSize%,%pNumberBox2%

 message,%ImgSize%,information

 StrFormat,DIV,%ImgSize%,1048576

 message,%ImgSize%,information

 Run,%ScriptFile%,ImaFile
shows me these numbers:
103052700
1715335408
17153354
-727711744

%IMGSize% < 0 :)

bug in DIV > img file not created by fsutil > vdk.exe hangs ....

:)

Peter

I'm trying to test in the debugger.

For that I need the contents of %pNumberBox2%

Peter



#65733 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 04:01 PM in LiveXP

This is Houston. Say again please.


Houston, we've had a problem. We missed some necessary folders in the ISO's tree.

Peter



#65726 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 03:39 PM in LiveXP

Testing with enu is much easier for me :)


HUSTON, WE HAVE A PROBLEM!

With German, English, and Turkish XP source, in the ISO the registry contains the 'AppKey'.

But in English and Turkish it disappears during PE boot, while in German it remains.

:) is no explanation.

What happens?
Which startup task does delete the values (not the keys!)?
How it can be avoided?

The causer truelly is a 'fundamental' task, because also in nativeEx_barebone with nearly no additional apps this happens.

Peter



#65724 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 03:29 PM in LiveXP

wrong, v13 is on livexp server, and i wish you dont change the icon of earlystarter :)

If you have version 14 or 12, you really got one of my experiments.
(And I self have been a victim of my experiments: actually there has been version 12; corrected)

Peter :)



#65641 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 08:16 PM in LiveXP

Peter

Is there any reason to keep these values empty on PE !?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Common AppData"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"AppData"

if not, should i do it with a seperate script or what you suggest..... ????

ps: i will look forward on lan issue tomorrow, enough for today :) .

For me it is also enough for today.

But I think that these reg keys are filled out by nativeEx core. If not: Today is :) Day! :)

Peter



#65620 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 05:57 PM in LiveXP

So that seems not to be only a question for Holger, but also a question for the 'project management'?

Just a crazy idea:

What about including and excluding the corresponding NICs depending on the selected emulator?

Peter



#65268 LiveXP -- Anything & Everything

Posted by pscEx on 19 April 2009 - 02:42 PM in LiveXP

OKI.

Please give me a day to try to reproduce on my system.

Peter



#65263 LiveXP -- Anything & Everything

Posted by pscEx on 19 April 2009 - 02:13 PM in LiveXP

wb077b1 --> can not finish bootsdi
wb076 --> no problem

The line

ShellExecute,Hide,"cmd.exe","/c #$q#$q%VdkExe%#$q open * #$q%RAMFolder%\i386\%BootSDIname%#$q /rw /p:0 >> #$q%VdkLog%#$q#$q"

in the failure situation causes a 'STOP'.
I heve no oipnion about reason, maybe the user by mistake dis sth.

Can you test again?

why warning with

wait,2
?

No opinion, and with my current version this does not appear.

If you are playing with some trash, just forget it for the moment.

Peter



#65168 LiveXP -- Anything & Everything

Posted by pscEx on 18 April 2009 - 03:26 PM in LiveXP

You know that I'm a 'WIM-Novice'
And I have the feeling that here I cannot help. :)
I do not find any reason (from the log) that in the PE the B: drive is not 'as usual'.

Let's hope the 'WIM-Master' will see this soon and has the technical ability to help.

Peter



#65150 LiveXP -- Anything & Everything

Posted by pscEx on 18 April 2009 - 01:57 PM in LiveXP

Hallo my friend Lancelot!

Please excuse me that I did not try to research fundamentals (I'm currently rather engaged in W"B internet features) and remain on the 'log level'.

Currently I do not see anything really 'wrong' in the logs.

Because :) seems not to be actual, let's see.

Can you explain your 'causing trouble'?

What happens (or does not happen)?

Peter



#65518 LiveXP -- Anything & Everything

Posted by pscEx on 21 April 2009 - 09:38 PM in LiveXP

Bad news if WB077b1 files are significantly different.

Sth where I can do sth?

Peter



#65529 LiveXP -- Anything & Everything

Posted by pscEx on 21 April 2009 - 10:13 PM in LiveXP

i will test tomorrow.

@Peter
i dont know winbuilder or hojope issue, but this line (HIVESFT.INF)

HKLM,&#34;SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Locations&#34;,&#34;DisableCallWaiting1&#34;,0x00000002,&#34;70#,&#34;
creates this value in pe registry: "70#$c" :)

Peter

OKI
Tomorrow ... :)
"70#$c" or
"70##$c" ?

Should be really "70#," ?
If yes, Bullsh...
Will take some time, because it disturbes all internal definitions ... :)

Peter



#65611 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 05:11 PM in LiveXP

in virtualbox v.2.1.4 i see 2 network adapters.
'virtnet network adapter' > ok
'vmware accelerated amd pcnet adapter' > exclamation mark

if you remove 'vmware accelerated amd pcnet adapter'
and start hwpnp 'vmware accelerated amd pcnet adapter' will be redetected (exclamation mark)

if you remove both in device manager, then rescan using device manager,
then start Penetwork you will get 'amd pcnet family adapter' (driver is pcntpci5.sys)
>Network is ok.

So that seems not to be only a question for Holger, but also a question for the 'project management'?

Peter



#65606 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 04:36 PM in LiveXP

I suggest that you and me currently do not spend more time on this issue.

I think that this is an interesting question for Holger, and I'm going to PM him.

Peter



#65599 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 04:03 PM in LiveXP

The LiveXP project downloaded today morning, does not bring PE network connection, even if built with WB 076.

:) :) :) :(

LiveXP with qEmu has network.

nativeEx with VirtualBox.Script version 20 works fine.

LiveXP, even the (copied from nativeEx) version 20 of VirtualBox does not have network.

:) :) :) :(

Peter

BTW: LiveXP VMWare.script brings an error and does not start the emulator.



#65560 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 08:46 AM in LiveXP

Is "70#$c" , should be "70#,"
:)

Fixed!

Next beta

Peter



#65764 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 06:49 PM in LiveXP

Thanks Lancelot!

i'm out now, but firtst:
WB077b1 BootSDI bug found (i hope)
this code

//_Calculate,&#34;Ceiling&#40;DirGetSize&#40;&#39;%TargetDir%&#39;&#41;/100*%pNumberBox2%/1048576&#41;&#34;,ImgSize

  Retrieve,FOLDERSIZE,%TargetDir%,%ImgSize%

  message,%ImgSize%,information

  StrFormat,DIV,%ImgSize%,100

  message,%ImgSize%,information

  StrFormat,MULT,%IMGSize%,%pNumberBox2%

  message,%ImgSize%,information

  StrFormat,DIV,%ImgSize%,1048576

  message,%ImgSize%,information

  Run,%ScriptFile%,ImaFile
shows me these numbers:
103052700
1715335408
17153354
-727711744

%IMGSize% < 0 :)

bug in DIV > img file not created by fsutil > vdk.exe hangs ....

:)

Peter

You should have put it to the bug tracker, rather than discussing here!
Retrieve,FOLDERSIZE,%TargetDir%,%ImgSize%

  message,%ImgSize%,information

  StrFormat,DIV,%ImgSize%,100
Results in

103052700
1715335408

103052700 / 100 = 1715335408?

Sorry. It is a random success, that I detect bugs in a forum's topic.
When they are written in the bug tracker, the 'detect success' is 100%

But I think that this bug is fixed in beta 2

Peter



#65768 LiveXP -- Anything & Everything

Posted by pscEx on 23 April 2009 - 06:59 PM in LiveXP

Peter psc

just reminding the old man, :)
at wb77beta2, also please dont forget wait, warnings i got :)

check log_20090419_061927_wb077b1_bootsdi_fails.html file in http://lancelot.winb...9_062832_wb.rar

I never saw Wait,? warnings in my (currently still private) beta 2!

Peter :)



#69417 LiveXP -- Anything & Everything

Posted by pscEx on 11 June 2009 - 08:31 AM in LiveXP

But I found in HoJoPE that an non existing Reg_Multi_sz is just not written, rather writing an empty key.
For full 076 compatibility I'll write the empty kex.


Done!

Next RC or 078.

Peter



#69555 LiveXP -- Anything & Everything

Posted by pscEx on 12 June 2009 - 06:35 PM in LiveXP

I'm not home right now .. I think it's WB076. I don't know about %API% right now ... but the script line that causes the error does not include %API%. All the variables that do appear are defined. So I don't see how %API% comes into the picture.

This happens in project runs. I haven't tried a single-file run or codebox.

Looks like we again have to explain some ;)

There is any difference between your PC contents and the 'standard WB user's' PC content.

I like these expeditions! ;)

BTW: Nice to hear that it is not WB077 RC1 :)

Also nice to hear 'project run'. Makes it easier :) ?

I'm going to make some experiments and maybe will ask you tomorrow for some more info.

Peter



#69412 LiveXP -- Anything & Everything

Posted by pscEx on 11 June 2009 - 08:09 AM in LiveXP

wb077RC1 - Is it a bug, or a new feature ?

when hex(7) values are 00 00 00 the value is not written on the reg

There are missing with compare to wb076 ? maybe this is a new feature !!!! I hope you clear that !!
[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Control\ProductOptions]
"ProductSuite"=hex(7):00,00,00,00
[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Control\Session Manager]
"BootExecute"=hex(7):00,00,00,00
[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Services\IpNat]
"DependOnGroup"=hex(7):00,00,00,00
[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Services\SharedAccess]
"DependOnGroup"=hex(7):00,00,00,00

In the actual 'Complete' download of LiveXP there is no script line writing the four keys which are found in 076.

But I found in HoJoPE that an non existing Reg_Multi_sz is just not written, rather writing an empty key.
For full 076 compatibility I'll write the empty kex.

Peter



#69333 LiveXP -- Anything & Everything

Posted by pscEx on 10 June 2009 - 09:22 AM in LiveXP

This is i guess mostly about hojope+wb and 'author' of both wb and hojope is Peter ... I am sure you will find much quickly than me what is going on with being the author of both....

It is in MMC.Script and the author of the version 17 change is galapo.

Peter



#69332 LiveXP -- Anything & Everything

Posted by pscEx on 10 June 2009 - 09:16 AM in LiveXP

The WinBuilder script command which is the 'author' of the result.

I found it by myself.

The new 'feature' (In multi_sz entries space is interpreted as delimiter) will be fixed in the final version.

BTW: Would be much easier to write into the bug tracker:
RegHiveLoad,WB-Setup,%target_sys%\setupreg.hiv

RegWrite,HKLM,0x7,&#34;WB-Setup\ControlSet001\Control\Session Manager\Memory Management&#34;,&#34;PagingFiles&#34;,&#34;NUL&#58; 0 0&#34;

RegHiveUnLoad,WB-Setup
results in:

[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Control\Session Manager\Memory Management]
wb076--> "PagingFiles"=hex(7):4e,00,55,00,4c,00,3a,00,20,00,30,00,20,00,30,00,00,00,00,\
wb077--> "PagingFiles"=hex(7):4e,00,55,00,4c,00,3a,00,00,00,30,00,00,00,30,00,00,00,00,\


Peter



#69557 LiveXP -- Anything & Everything

Posted by pscEx on 12 June 2009 - 07:09 PM in LiveXP

@JonF

You are now in the best hands to solve your issue.

I'm only one of the three programmers in the WinBuilder development team, with a restricted knowledge about the real demand of users.

The latest answer brougth you into the helpful hands of a professional user with propably no programming experience, but with a series of ideas.

In this special case the new situation seems to be the best root to solve your issue. The issue is on 'user' side.

I'm going to strike-through (for me) your question and go back to my personal ToDo list.

Peter



#69702 LiveXP -- Anything & Everything

Posted by pscEx on 14 June 2009 - 08:21 PM in LiveXP

That is not a fact, that is an order.

Peter



#70154 LiveXP -- Anything & Everything

Posted by pscEx on 20 June 2009 - 12:55 PM in LiveXP

(post #1525) Fixed!

It was a 'feature' in AddVariables which added the complete section to variables, including macro definitions. ;)

Peter



#70100 LiveXP -- Anything & Everything

Posted by pscEx on 19 June 2009 - 07:18 PM in LiveXP

Thanks again!

A good base to catch the bug!

Peter

EDIT: I have the feeling that it depends on the 'Generate empty keys' feature.

In 076 an empty key was not written to registry.

But on demand (missing keys caused troubles) I implemented in 077. And appearently not 100% successfull ...



#70094 LiveXP -- Anything & Everything

Posted by pscEx on 19 June 2009 - 06:47 PM in LiveXP

Thanks JonF!!


Hi, i can reproduce now. Reported in bug tracker: bug id #199.
Thank you

;)

Peter


;) :) :)

Thanks, Peter.

With RC1 I can reproduce.

Good and Bad News:
Good: With my current RC2 this does not happen.
Bad: With my current RC2 I get other errors like 'Index out of bounds'

That means that there is some misinterpretation of the command line or a non catched user syntax error, I have to look for.

Peter



#69727 LiveXP -- Anything & Everything

Posted by pscEx on 14 June 2009 - 10:18 PM in LiveXP

JonF, never seen this error in WB076, but 2-3 times using 077 betas.
( ;) i dont know how to reproduce)

Can you do HARD WORK trying to reproduce?

You know, solving an ;) is not so easy.

Peter :)



#69330 LiveXP -- Anything & Everything

Posted by pscEx on 10 June 2009 - 08:40 AM in LiveXP

Comparing RESULTS does not give any help to explain and maybe fix an issue.

What is NEEDED:

The WinBuilder script command which is the 'author' of the result.

BTW: I cannot understand how this can be an issue of RC1.
The last change in registry work has been made in beta 3

fixed - Bug in RegWrite with comma in value


Why did this not appear in beta 3?

Peter



#69324 LiveXP -- Anything & Everything

Posted by pscEx on 10 June 2009 - 07:38 AM in LiveXP

There should be a "defination of warning by Peter" around somewhere..........

Whatever Peter's defination is, WARNINGS disturbs most people, ESpecially a new user.
Probably casual user will have a mixed mind when he see warnings at log !
...
For a user who is adding his apps, scripts to projects, no way to hide from copy overwrite warnings ;) ;)
...
@Peter psc
Therefore I suggest to select "Warning on Copy OverWrite" False as a Winbuilder.exe default ??????? on next RC or stable (or an early RC maybe very nice too)


Again my definition:
The warning tells the user that something is different from the assumed situation. Assumed is that target file does not exist yet.

It is in the responsibility of the .script developers to write scripts avoiding the warning by NOT trying to overwrite existing files.

There is a nice, but too rarelly used command
If,Not,EXISTFILE,blabla,CopyFile,blabla, ...

Peter



#66357 LiveXP -- Anything & Everything

Posted by pscEx on 29 April 2009 - 10:50 AM in LiveXP

I did not follow the complete bitdefender discussion.
What is the 'common mistake'?

Peter



#65926 LiveXP -- Anything & Everything

Posted by pscEx on 25 April 2009 - 09:35 PM in LiveXP

yes peter, i saw it before and also remembering old false positive with wget
...
and a norman user (with being in %15) will not be able to use slock.exe as it will be moved to quarantine and probably causing winbuilder give warning.

As seen, it falls remarkably below the 'VirusTotal virus detection percentage' I proposed here.
And therefore, on MY system, I would not worry about this warning.

But unfortunatelly, WinBuilder cannot make any influence on the local antivir programs.
It is really a task for the user to
  • tell his local antivir progarm 'Here you are wrong'
  • tell the antivir developer about wrong positive

@Lancelot:
As the project's admin, you (and not the currently unavailable Galaop) :) have to decide (maybe by help of any WEB virus check apps) whether to let the suspicious app in the server or not. :)
Peter



#65918 LiveXP -- Anything & Everything

Posted by pscEx on 25 April 2009 - 06:42 PM in LiveXP

See here

Peter



#65849 LiveXP -- Anything & Everything

Posted by pscEx on 24 April 2009 - 04:41 PM in LiveXP

@Peter psc
VirtualBox 1.6.6 (released Sep 2, 2008), anyway i uploaded new script....

The changes fxscrpt made now, are based on an old script by me.

And long time ago I implemented the different reg key query for different VirtualBox versions.

BTW: Because of the ERROROFF command WB should have version > 074. But I think that a lot of other scripts also demand this.

Peter



#66360 LiveXP -- Anything & Everything

Posted by pscEx on 29 April 2009 - 11:28 AM in LiveXP

Any help of WinBuilder.exe, like a warning, would demand that WinBuilder.exe reacts on a hardcoded string.

And that is not wise!

Suggestion: Let it do the API:

Change the definition
reg_add=Run,%API%,_reg_add
And define _reg_add:
&#91;_reg_add&#93;

Set,%Write%,#4

If,%Wow64%,Equal,True,Begin

  StrFormat,POS,#4,##$pprogramfiles##$p,%num%

  If,Not,%num%,Equal,0,StrFormat,REPLACE,#4,##$pprogramfiles##$p,##$pprogramfiles##$p,%Write%

End

RegWrite,&#34;HKLM&#34;,0x2,&#34;%reg%\ControlSet001\Services\XCOMM&#34;,&#34;ImagePath&#34;,%Write%

Peter



#66682 LiveXP -- Anything & Everything

Posted by pscEx on 02 May 2009 - 01:28 PM in LiveXP

Thanks guys.

Another thing I have to remember to re-set after downloading! It takes two or three builds after a download to get everything working again. (WBManager doesn't help because of the way I work).

I really don't like the fact that a download overrides local settings. I suppose it's so deeply buried in the paradigm that there's nothing that can be done.


Did you already try the myOptions script?

Peter



#69263 LiveXP -- Anything & Everything

Posted by pscEx on 09 June 2009 - 02:06 PM in LiveXP

There comes no error message and not even a warning that this file could not be copied. ;)

In ShellExecute, WinBuilder can only check the successful start of the external app, not the app's result.

@Pedro, that seems to be the API's responsibility to check the existence of the file after ShellExceute expand.exe

It is possible for the script / API to check %ExitCode% after ShellExecute

@Lancelot, please explain me the correlation between 'missing quotes' in post #60 and ShellExecute expand.exe.

Peter



#67938 LiveXP -- Anything & Everything

Posted by pscEx on 19 May 2009 - 03:43 PM in LiveXP

Hi,

Somtimes things already done.
Copy [FixShellFolders] from 1-Regfactory.script
Only one 'hardcoded' directory
for 'all users' : common documents
(English: Documents / German : Gemeinsame Dokumente).

Currently there is no string for common documents
in %ProjectInfo%. For now use
Set,%DirCommonDocuments%,"Documents" at first line to
assign different value.

Peter

Peter!

Lack of my English

Please send me a PM (German) and explain what is missing.

Peter



#67931 LiveXP -- Anything & Everything

Posted by pscEx on 19 May 2009 - 02:22 PM in LiveXP

Well I think some (0 bytes) empty folders would not make it bigger, but solve strange errors of some applications.
Also an explorer shell PE should have it's special explorer folders :D

But it's of course your decision

Currently buildModel does not create any folder. It only provides information.
My decision is: It should continue to work in this way.

Explorer shell: One of many scripts using buildModel information.
My decision: Not applicable, because I do not have any influence on scripts. They have to provide what they need.

Peter :D



#67636 LiveXP -- Anything & Everything

Posted by pscEx on 15 May 2009 - 11:15 AM in LiveXP

PE resets any preconfigured value for ImagePath to 'partmgr.sys'


Can EarlyStarter re-reset?

Peter



#65134 LiveXP -- Anything & Everything

Posted by pscEx on 18 April 2009 - 11:44 AM in LiveXP

Hi Lancelot! Welcome back!

What do you think about to 'ask in the newbie question format':
Use a minimized build and post the two logs!

Peter :)