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

can i use manually slipstreamed version?

• Use original source CD
• Whatever you want to change, do by script, not by changing the CD

System,GETFREEDRIVE,%var%

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

; Customized by nLite - www.nliteos.com

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

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

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

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

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

• In the community trying to develop usable projects?
• Moving reproaches forwards and back?

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

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

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

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.

RegWrite,HKLM,0x3,Section,Key(Binary),00,01,00

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?

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

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"

• Did not select any shell script
• Selected more than one shell script.

%BootSDI-VdkExe%=%Tools%\vdk\%root%.exe

If,%architecture_test%,Equal,0,Set,%root%,vdk_wb

If,%architecture_test%,Bigger,0,Set,%root%,vdkx64\vdk

Set,%VdkExe%,%BootSDI-VdkExe%,GLOBAL

System,REBUILDVARS

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

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

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

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

(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?)

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

Thanks psc,

now also on LiveXP server,

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

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

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

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

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.

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 !

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

• 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

[variables]

%ProgramTitle%=???

%ProgramEXE%=???

%ProgramFolder%=???

Add_Shortcut,Desktop,,"%PDRIVE%\portables\%ProgramEXE%"

Add_Shortcut,Desktop,,"#$pPDRIVE#$q\portables\%ProgramEXE%"

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

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

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?

Wonko

Compare with nativeEx.

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

look into the scripts' history for 'consolidation'

Peter

• %RamISORootName%
• %ISORootName%
• %burnISO%

• %IsoFileName%
• %IsoFile%
• %ISODir%

[SourceDisksNames.x86]

1="Boot Disk","\BOOT",,\i386

[SourceDisksNames.x86]

1="Boot Disk","\Lancelot",,\i386

FileCreateBlank,%TargetDir%\Lancelot

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?

anyway it is a very annoying thing
that using WB 078 SP2
i am unable to create the log file after a complete build
(either the build is successful, either the build is failed)

@psc
thanks gain, new flag of livexp is BOOTFLAG

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

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

StrFormat,FILENAME,%IsoFile%,%tmp%

 StrFormat,EXT,%tmp%,%ext%

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

 Set,%ISORootName%,%tmp%,PERMANENT

 Set,%RamISORootName%,%tmp%_RAM,PERMANENT

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 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
now, but will reply as quick as possible).

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.

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

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

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

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

... after a exec command

I dont like these log lines:

RegWrite - root key: [HKLM] Type: [0x1] A file was not chosen from: [WB-Software\Microsoft\Shared Tools\MSInfo\Categories]

 RegWrite - root key: [HKLM] Type: [0x1] A file was not chosen from: [WB-Software\Microsoft\Shared Tools\MSInfo\Templates]

 RegWrite - root key: [HKLM] Type: [0x1] A file was not chosen from: [WB-Software\Microsoft\Shared Tools\MSInfo\Toolsets\MSInfo]

fxscrpt

new mmc on server

not sure about the meaning of filled out

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 .

Thanks Lancelot!

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

//_Calculate,"Ceiling(DirGetSize('%TargetDir%')/100*%pNumberBox2%/1048576)",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 currently use virtualbox portable ( Portable-VirtualBox.exe ) which helps me a lot when migrating from x64 <-> x86 (both app32 and app64 folders there )
Is it possible to use virtualbox portable with this new script ?? (checking for if regkey not exists, if file exists (%Textbox%) --> )

a line from ReadMe.txt (never tested)

Testing with enu is much easier for me

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

you enabled sth you shouldnt, probably a mistake when clicking by mouse (i love my keyboard style on wb )

anyway
Solution probably is: disable shell security script before building (Basic--->Shells--->Explorer tweaks--->Shell Security) which is not selected as default (check here )

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.

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

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

why warning with

wait,2

?

• What happened between post #1314 and now?
• Is it concerning a dummie user like me?

i will test tomorrow.

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

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Locations","DisableCallWaiting1",0x00000002,"70#,"

creates this value in pe registry: "70#$c"

Peter

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

yep i definately need a break

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

Thanks Lancelot!

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

//_Calculate,"Ceiling(DirGetSize('%TargetDir%')/100*%pNumberBox2%/1048576)",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

Retrieve,FOLDERSIZE,%TargetDir%,%ImgSize%

  message,%ImgSize%,information

  StrFormat,DIV,%ImgSize%,100

103052700
1715335408

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

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

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.

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

RegHiveLoad,WB-Setup,%target_sys%\setupreg.hiv

RegWrite,HKLM,0x7,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management","PagingFiles","NUL: 0 0"

RegHiveUnLoad,WB-Setup

[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,\

fixed - Bug in RegWrite with comma in value

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)

If,Not,EXISTFILE,blabla,CopyFile,blabla, ...

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.

Thanks JonF!!


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



Peter

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

@Peter psc, i cant since i dont understand the question + which post 60

Hi JFX, Not my fault, as written post 60 this is sth forgetten during 075betas to final 076... Hopefully we will have stable wb with a nightmare of bug catching sooon

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

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

does current script (on nativeex barabone) works with vbox1 too??

reg_add=Run,%API%,_reg_add

[_reg_add]

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,"HKLM",0x2,"%reg%\ControlSet001\Services\XCOMM","ImagePath",%Write%

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.

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

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

But it's of course your decision

How about to always create ALL the "Shell Folders" and "User Shell Folders" by ModelRam.

This seems to solve some problems with apps like O&O Defrag or MS Office

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