Jump to content











pscEx's Content

There have been 1000 items by pscEx (Search limited from 15-July 10)



Sort by                Order  

#66996 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 May 2009 - 06:24 PM in Win7PE

with buildings under XP 32 Bit SP3 MUI (english with german language pack activated) and 7' 32Bit german.

Thanks Holger, that is a new point of view which perhaps can can help.
Maybe there is some unknown MUI influence ...

In those configs I'm a noob. Please can you tell me how I can
  • use enu source
  • activate German mui
for my build
(Or is it the installed host OS?)

Peter



#68286 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 25 May 2009 - 07:19 PM in Win7PE

@JonF!

In 'Copy Files', please try 'Standard' rather than 'Full'

Maybe in the 'Full copy' there is an issue.


Peter



#66514 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 April 2009 - 07:00 PM in Win7PE

I work at a University and so the blowing up of computers is not the SOP way of getting rid of them :-)

I have a couple OC3 lines at my disposal for uploading so I should be good. Where would I upload the files to for your browsing pleasure?

Brian

For those special purposes we have the domain 'shared.boot-land.net' and I'll PM you the access data.

Peter



#66155 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 09:24 PM in Win7PE

There are so many posts (partly crossing) that I'm confused.
Maybe it is also a lack of my English knowledge.

Is your answer about my post #189 or #194?

I cannot imagine that the effect of a space in a path in any way depends on

I understand about the different sources and different hardware.
One could go with it but another can't go with the same one.
Even same source, once can go smoothly but not another.
Depending on how many software are installed on it or which type of source they use.
Some use OEM, but many use nLited theseday.

For me these all are no :) but issues which can be solved, if the right people provide the right back information.
Maybe it takes a while.

Nevertheless: Let's start e.g. with the "cscui.dll file" issue.

Peter



#66125 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 06:52 PM in Win7PE

it was zipped, hence why I gave up and pasted it in

Have managed to get a working build by pressing play button on each script in turn and it works okay, but if I press play button on start page, it just stops without seemingly doing anything

Just an addition to Lancelot's post and to explain to less experienced users:
If your 'play button' is the small green triangle, clicking it, starts processing the actual script, and ONLY this script.

In the actual case, the actual script is 'script.project' and in 'script.project' there is (depending on the project) either nothing to be done, or just some small things like defining exit code etc.

But the currently known script.project-s never will process the complete project (that would demand a 'Run' for all scripts beeing included).

Now: See Lancelot's post

Peter



#69098 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 07 June 2009 - 06:38 AM in Win7PE

I get an extract error from the penetwork beta script:

Run - Processing section: [Depack_And_Check_Ext] From file: [%BaseDir%\Projects\win7pe\api.script]
Posted Image with parameters: [files],[#2],[#3],[%BaseDir%\Target\Win7PE\Program Files],[PENetwork],[PENetwork.exe]

#2 should be 'PENetwork.7z'

In your %BaseDir%\Projects\win7pe\project.ini, Section [Win7Info] Key [SysType] is not equal to 'x86'

Peter



#69323 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 10 June 2009 - 07:13 AM in Win7PE

@yahoouk

IMHO additionally in [MountWAIK-imagex] the line
ShellExecute,Hide,"#$q%IMAGEX%#$q","/mount #$q%SDIR%\winpe.wim#$q %pScrollBox1% #$q%BootSRC%#$q"
should be commented out.

Peter

BTW: Here again is the case that WinBuilder does not detect an error, because imagex is STARTED successfull.

Try this in CodeBox (with your specific paths in [Variables])
[variables]

%IMAGEX%="C:\Programme\Windows _AIK\Tools\x86\imagex.exe"

%SDIR%="C:\Programme\Windows _AIK\Tools\PETools\x86"

%pScrollBox1%=2

%BootSRC%="V:\WB\wb debug\Temp\Win7PE\BoorSRC"



[process]

ShellExecute,Hide,"#$q%IMAGEX%#$q","/mount #$q%SDIR%\winpe.wim#$q %pScrollBox1% #$q%BootSRC%#$q"

Echo,%ExitCode%
%ExitCode% = 2 tells about an issue.



#78799 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 17 September 2009 - 04:49 PM in Win7PE

Congratulations for the fix! ;)

@YahooUK: I think that you have to check why this fix is necessary.
That MUST be avoided in the projet's scripts.

Peter ;)



#78905 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 18 September 2009 - 02:12 PM in Win7PE

Just downloaded & built one successfully, couple of Avira errors but as a whole, the thing works. So, should I / we start using the Rescue project instead of just Win7PE?

The projects are different, and I have no recommendation, not even an opinion, whether to use #1 or #2.

The user, in this case you, decides.

Peter



#73273 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 July 2009 - 08:37 PM in Win7PE

exactly the same

on root of D in a folder called win7petest and source files are in a folder called win7source

I copied the whole file structure from my Windows 7 PC to my XP machine, so everything is identical

Sorry, if I nerve you with stupid intentions:

Can you post log.html, hives and a 'DIR <target> /B /s' of both?

Peter



#73120 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 July 2009 - 02:41 PM in Win7PE

Running another build now but with the Debug Log enabled for a more verbose output log.

That's nice that you did so. But where is the log :idea:

On the other hand, it would not help more than the previous log.

It just tells us that robocopy copies somethnimg.

But who knows, what is copied ...

No idea, whether a *.wim is generated, and if yes, whith which content.

What is needed, is the complete project's build log.

Peter



#71255 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 07 July 2009 - 08:46 PM in Win7PE

I think the project simply copy the whole 'boot' folder (including the bcd) from the SourceDir's root
(in 'Build\1-files.Script' at line #95 when 'File to copy: full' mode used
or at line # 105 when 'File to copy: standard' mode used)

then modifies it only in the 'Finalize\4-postconfig.script'
at lines #21 and #23:

/set {default} quietboot on
(it is something simmilar as the '/noguiboot' in XP)

/set {default} bootlog on
(Enables the system initialization log)

Yes, that's my opinion in the mean time, too.

But where the corrupted path is coming from?

Maybe after copying the folder including BCD, BCD has to be modified somehow?

Peter



#66086 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 12:03 PM in Win7PE

with winbuilder 077beta2 cannot even download a project as keep getting "list index out of bounds(0)"

I just downloaded the complete project with beta 2 w/o any error.

Peter



#69364 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 10 June 2009 - 02:27 PM in Win7PE

I made a test with the project as 'factory set', including all aps, drivers etc. Source: German W7 RC1. WinBuilder 077 RC1. Host OS: 64 bit W7RC1.

Besides the known trouble with PENetwork on 64 bit host, already apearing in post #450, (http://www.boot-land...?...ost&p=69098), everything went fine: Shortcuts etc ... ;)

A big ;) to all in the team, like yahooUK, Paraglider, Joshua (I'm lazy and stop with #3. That does not mean that I exclude somebody!)

Peter :)



#65370 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 20 April 2009 - 04:53 PM in Win7PE

@YahooUK:

As one test before delivering the new 077 beta 2, I built your project.

Result: This has been my first Vista-World project which created a running PE with 'factory settings'. I just had to define source DVD and WAIK install path.
In the past with other projects I have had usually troubles. Maybe you remember my post 'Vista for Dummies'
:)

But please be not too proud! there are some smaller complains.

Biggest one is that you use a very old VirtualBox script. It only works with versions before 1.6.0.

Attached a script which also works with current versions up to 2.2.0 (Please do not use 2.2.0, use 2.1.?; I wrote a warning anywhere in the forum)

Some smaller:
  • Comment lines should have two hash chars rather than one. Since a while we are trying to define comment as // or ##.
  • The System,RefreshVars command is obsolete and does not do anything. You should remove it.
  • Some Echo commands with spaces in the message should include the message in quotes.
Continue your good way!

Peter

Attached File  VirtualBox.script   35.56KB   20 downloads



#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



#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:



#73965 LiveXP -- Anything & Everything

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

and by the way guys what about my previous query about "character set problem" is it bug?

Here you can see me very confused.

The picture you posted shows some non - western captions for 'back', 'continue' and 'abort'.
But the log tells that you are using a 0409 (English) source CD.

Are you mixing something?

Peter



#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



#76027 LiveXP -- Anything & Everything

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

i have provided the build log, do you require some other log :ermm: ,

As far as I see, you published the build log of the build where the build aborted with the first occurring error in 'Hives Factory'.
I neet the log of the build with "Stop on Error" switched OFF, where (as I think) the build ran into "Build ISO" or "Emulate" or something similar.
(Or did I miss that log?)

Peter



#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,&#34;%TargetDir%\i386\TXTSETUP.SIF&#34;,&#34;NLS&#34;,&#34;AnsiCodepage&#34;,c_936.nls#$c936

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

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

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

IniWrite,&#34;%TargetDir%\i386\TXTSETUP.SIF&#34;,&#34;NLS&#34;,&#34;DefaultLayout&#34;,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



#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 &#39;WBVerify&#39; version 2.2.3

  Date&#58; 2009-Aug-07 16&#58;53&#58;43

  

  &#91;Counts&#93;

  Missing=0

  Obsolete=0

  Errors=1

  Warnings=0

  

  Errors&#58;

  &#34;When excluding MiscSettings.Script, FixShellWinlogon.Script and ShellSecurity.Script, you must uncheck &#39;Don&#39;t set Explorer as shell&#39; in Explorer.Script&#34;

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&#58; &#91;%BaseDir%\Target\nativeEx_barebone\I386\WinSxS\manifests\CONTROLS.CAT&#93; to&#58;&#91;%BaseDir%\Target\nativeEx_barebone\I386\WinSxS\manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a.CAT&#93;

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



#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



#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



#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



#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



#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.



#65187 LiveXP -- Anything & Everything

Posted by pscEx on 18 April 2009 - 05:50 PM in LiveXP

Currently I cannot, because I do not have a running LiveXP project on my PC. But tomorrow I'll try.

Peter



#73703 LiveXP -- Anything & Everything

Posted by pscEx on 05 August 2009 - 09:49 AM in LiveXP

after WinBuilder completed successful, i tried the ISO and the UFD (created using PeToUSB.exe) on VirtualBox both of them are having similar problems, Live XP starts loading saying "Stating Windows PE", after the progress bar is completed it gets stuck saying "Please Wait...", i don't see any activity on the disk (Virtual CD as well as UFD) well.

You use the script 'RestoreBase' which copies cached files into the build.

But appearently you did not build the cache before.

I cannot say exactly what happens with this, but wirh high propability the files in the PE are a bit out of order ...

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



#73771 LiveXP -- Anything & Everything

Posted by pscEx on 05 August 2009 - 08:56 PM in LiveXP

so i should disable the script? will it fix the problem? (or part of it)

secondly how do i add a registry key to acronis disk director 10?

First: To disable the script will make the PE completelly unbootable.
(BTW: As 'standard user' you cannot disable, because it is marked as 'mandatory')

You need a script version which runs with WB 076, or should try WB 077 RC2

Second: Please exscuse me that I do not want to explain this here. This knowledge is a fundamental a script developer should have and can be read in the help.

If there are some open questions due to the help, I'm ready to explain.

Peter



#73704 LiveXP -- Anything & Everything

Posted by pscEx on 05 August 2009 - 10:03 AM in LiveXP

A addon:

The main reason for your troubles seems to be that the Copy&Expand script you use, is a version needing WB 077 RC2.

The functionality 'Expand one file out of a cab file' is not yet provided by WB 076.

So the necessary files 'mouclass.sys' and 'mouhid.sys' are not in the PE.

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



#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



#81200 LiveXP -- Anything & Everything

Posted by pscEx on 07 October 2009 - 06:38 PM in LiveXP

Maybe we only can catch it experimentally using the real project.

@JonF: Is your connection fast enough to upload your complete project?

If yes, for such purposes, we have a server 'shared.winbuilder.net'. I can give you the FTP access data. PM me to get.

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!!!



#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



#81082 LiveXP -- Anything & Everything

Posted by pscEx on 06 October 2009 - 01:00 PM in LiveXP

Crossing of postst!

Lancelot, give me some time to check what you wrote.

I currently do not know the InterfaceMode.

Peter :hypocrite:



#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



#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



#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:



#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



#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



#79782 LiveXP -- Anything & Everything

Posted by pscEx on 25 September 2009 - 06:30 PM in LiveXP

Hi wimb,

copying vdk to a new location was found as a solution for vistasp1 , and "dont use vdk remove" was found as a solution for some other utilities (ghost14) causing vdk fail.

we will have imdisk selected default on bootsdi hoping it will fix vdk problems, coming soon :)

As known, I compiled the VDK_WB with a couple of changes necessary for WinBuilder.
Mainly that have been user inputs. Under WinBuilder you cannot see when vdk demands a user reaction. Therefore it hangs for ever ...

@Sherpya: Maybe that the x64 compile is based on a 'non-WB' version? I think that you do not have the sources I used.

I currently do not know the issues completelly, because I rarelly look into this topic.

If there are x86 issues which can be listed, I can go into the debugger, look, and propably fix.
(Please, not a list of links!)

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



#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



#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:



#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



#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



#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



#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



#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.



#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



#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



#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



#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



#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 :)



#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



#65586 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 01:54 PM in LiveXP

i understand the warnings and fixes are on the way now (currently i havent check fully with wb077b1)

but with a quick test using wb076, network working nicely with virtualbox, i guess no problem you testing with 076 too.

Lancelot, take a coffee, take a lot of fresh air (maybe also a Raki can help, if it is not too early for that). And then read my post again :)
I have the troubles with 076, too!

But I currently do not remember whether I deleted the registry cache before testing (I usually do so). Give me some minutes to do a new test.

Peter



#66389 LiveXP -- Anything & Everything

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

PS: A 64Bit version of WB would solve the problem without the need to depend on a glitch. :)

See here: http://edn.embarcade...m/article/39174

64 bit Delphi compiler estimated to be ready in mid 2010.

And to port WB from Delphi to C++ would need a comparable time.

So currently we have to try to do the best of the situation, rather than to complain.

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



#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



#65746 LiveXP -- Anything & Everything

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

Q&D test:

Your new script with NAT unchecked and checked (adapter #1) allowed me to google. :)

Small concern: You should use the actual script version 20 (nativeEx server) for changes. There are some enhancements with installing / deinstalling components to the VM.

Peter



#65739 LiveXP -- Anything & Everything

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

I know Explorer deletes some Shell Folders values, if
corresponding Folders are not present!
Add these folders to modelram!

Thanks PeteĀ®

Exactly this I found and reported three posts before.

I think that it is now only a question of some Mediterrean minutes to present the final solution.

Peter :)

EDIT: Funny, I wrote the 'r' in parenthses. And the clever forum's software upgraded to a registered trademark.

You can be proud, Pete[r]!



#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



#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



#65623 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 06:30 PM in LiveXP

I dont know the reason, but my tests shows issue solved after updating "5 - CopyAndExpand.Script" to v22 , currently available on livexp server.

Maybe we do a break for a week, get new power, and continue then!

I was going to test the latest LiveXP version (including the Copy&expand 22).
I did a download of 'Everything new'

The PE started with "Bootdisk expired" and asked me for a password :)

Peter



#65699 LiveXP -- Anything & Everything

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

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

a question for the nativeex barabone 'project management'?


:) :) (red added by me) :) :)

Thanks for the applause!

As to be seen, nativeEx_barebone from the very beginning works well with the three popular emulators.

Peter



#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



#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 :)



#65581 LiveXP -- Anything & Everything

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

In order to test for 077 beta 2 publishing, I made a fresh download (complete) and tested with 'factory settings'.

In the PE the network did not work.

I tried the 'Actualize WinBuilder' button in the project's GUI and downloaded the recommended, tested WB.

But this also did not work.

I also tried to uncheck HWPNP and VirNet driver: Did not help.

To compare, I built nativeEx barebone with the beta candidate:

Network working.

As result, it looks like the new (unpublished) beta is not responsible for this LiveXP behaviour.

There seems to be something in the project causing the network failure.

Peter

Attached File  log.7z   145.88KB   202 downloads



#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



#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



#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



#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 :)



#69334 LiveXP -- Anything & Everything

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

From not answering mmc question, i assume i will write mmc v30 for livexp, coming soon, need a break


I do not read everything.
And you should not assume that I know a question you asked once ;)

What's the MMC issue? Best place to answer is the bug tracker, but please one contigous description, no links!

Peter



#69689 LiveXP -- Anything & Everything

Posted by pscEx on 14 June 2009 - 03:40 PM in LiveXP

Is it possible that the 'voodoo around' really is a 'feature' of WinBuilder?

Please give me more concentrated information (I do not follow this forum regularly) in order to check whether a WB bug has to be killed.

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 :)



#65622 LiveXP -- Anything & Everything

Posted by pscEx on 22 April 2009 - 06:02 PM in LiveXP

I am only a mini helper around for LiveXP and aware that definately not qualified to manage a project (especially LiveXP).
I try to do things as far as i know and still learning.

You never know what you can do, before you tried it!

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



#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



#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



#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



#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



#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



#65479 LiveXP -- Anything & Everything

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

Maybe you can confirm that new script works for nativeEx.

The new version brings in nativeEx (FBWF build and all options checked) a bootable and (as far as I decided in some minutes) working PE.

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



#69274 LiveXP -- Anything & Everything

Posted by pscEx on 09 June 2009 - 03:10 PM in LiveXP

hmm using both new scripts still not copying swmidi.sys ;)

@Lancelot: In xpe-pnp-aio.script %SP% is undefined!
Maybe this can help:
IniRead,%ProjectInfo%,OS,ServicePack,%SP%

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



#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