Question to Specialists

Some questions to the specialists:

The last script which can be selected in VistaPE CAPI v.12 is "Debug".
- Is this script necessary if an ISO is build for a boot CD?
- What is this script necessary for?

In the most scripts it is possible to select "Run from ram (Boot.wim)"
- When shuold this be selected?

Keyboard:
- Is it possible to select the German keyboard for Vista PE in any of the scripts. I could not found this an have as standard the US Keyboard.

Regards
DaveWa

Some questions to the specialists:

The last script which can be selected in VistaPE CAPI v.12 is "Debug".
- Is this script necessary if an ISO is build for a boot CD?

No, it is not necessary for a boot CD. I've never used it.

In the most scripts it is possible to select "Run from ram (Boot.wim)"
- When should this be selected?

Run from RAM means that it is loaded into a disk image that is loaded into RAM at boot time. That disk image includes FBWF (see the Basic Configuration and Tools script), which uses another chunk of RAM to pretend that the disk image is writable. So the program will run from a writable directory (some programs require this) and will load at RAM speed.

If you do not run from RAM, the program's directory will not be writable (if it is a CD; a flash drive will be writable) and will load at the speed of whatever device it is on.

Keyboard:
- Is it possible to select the German keyboard for Vista PE in any of the scripts. I could not found this an have as standard the US Keyboard.

Try setting Locale to German in Main Configuration. Are you building from a German or English source?

Try setting Locale to German in Main Configuration. Are you building from a German or English source?

Thank you for the information above.
I am building from a German source. Sorry, but I did not see that it is possible to chnage the settings there.

In the Main Configuration script there is a drop-down box labeled Locale. I think the default value is Auto. I am not at home right now and cannot create a screenshot.

In the Main Configuration script there is a drop-down box labeled Locale. I think the default value is Auto. I am not at home right now and cannot create a screenshot.

I chnaged from "Auto" to "German" and run the entire project again. After booting from the new CD I have still the US keybord settings.

Can you post a log, please? ZIP it or 7Z it before posting.

Can you post a log, please? ZIP it or 7Z it before posting.

Please find attached the file log.7z (after run the entire project again)


If it is allowed I have an additional question:
I tried to add a script for the text editor EditPad Lite. I created a new folder "J:\VistaPE\Projects\VistaPE-CAPI\Apps\Editor" and put the script in this folder. But when I run the Sript, neither a folder is created in "J:\VistaPE\Target" nor the file is created there. What did I wrong.
Attached is the script file EditPadDavid.script (most of the encoded file deleted because of upload space) and the log file created after running this script log-EdidPad.7z

Thank you very much for your assistance

You've forgot to unpack the files.

I tried to add a script for the text editor EditPad Lite. I created a new folder "J:\VistaPE\Projects\VistaPE-CAPI\Apps\Editor" and put the script in this folder. But when I run the Sript, neither a folder is created in "J:\VistaPE\Target" nor the file is created there. What did I wrong.

I'm not real familiar with the newer projects. You may need some command in the [process] section that will extract the file from the script and place it in the Target Directory.

http://winbuilder.ne...ipt_syntax.html

ExtractFile,<%ScriptFile%>,<Folder>,<Filename>,<DirToExtract>
This command will extract a single file from a folder inside a given script.

Use %ScriptFile%, and look in the script for the name of the embedded Folder and Filename.

I couldn't guess where the DirToExtract is, because it would need to match up with the created shortcuts, and would therefore need to be determined by whether the program should be in the "Run from RAM" programs directory or in the "Run from Media" programs directory.

Regards

alanf, it's suppose to be a CAPI script, so he needs to use CAPI commands, like unpack.

alanf, it's suppose to be a CAPI script, so he needs to use CAPI commands, like unpack.

Yeah. I knew that. The old "native" winbuilder commands should still work though. And I can't imagine that a new CAPI command could have syntax more simple than the ExtractFile syntax, particularly when the file to be extracted is not archived.

So! What is the CAPI command and syntax? Does it automatically know where to extract the file (RAM or Media)?

Regards

alanf, it's suppose to be a CAPI script, so he needs to use CAPI commands, like unpack.

I think it's fine to use base commands where applicable. In a lot of situations both Unpack and ExtractFile can do the job, and ExtractFile is infinitesimally faster and produces an easier-to-read log.

Please find attached the file log.7z (after run the entire project again)

There's a bug. I'm testing the fix. In some hours ...

I think it's fine to use base commands where applicable. In a lot of situations both Unpack and ExtractFile can do the job, and ExtractFile is infinitesimally faster and produces an easier-to-read log.

This is a part of the script

[variables]
%ProgramTitle%=EditPad
%ProgramEXE%=EditPadLite.exe
%ProgramFolder%=EditPad
[EncodedFolders]
Folder
[EncodedFile-Folder-EditPadLite.exe]
lines=445

When I use
[process]
unpack

without any additional parameters like filename or Folder or whatever it workes fine. The folder is build and the file is extracted there.

The command ExtractFile needs additional parameters:

ExtractFile,%ScriptFile%,Folder,Filenam,DirToExtract

I testet a lot but is does not work. Is it realy necessary to add the name of the scriptfile (with or without .script or %)? and what exactly means DirToExtract? The whole Directory like "J:\VistaPE\Target\VistaPE-CAPI\Programs\EditPadDavid" ?

I testet a lot but is does not work. Is it realy necessary to add the name of the scriptfile (with or without .script or %)? and what exactly means DirToExtract? The whole Directory like "J:\VistaPE\Target\VistaPE-CAPI\Programs\EditPadDavid" ?

It works with:
"ExtractFile,%ScriptFile%,Folder,EditPadLite.exe,%Target_Prog%\%ProgramFolder%"

This is a part of the script

[variables]
%ProgramTitle%=EditPad
%ProgramEXE%=EditPadLite.exe
%ProgramFolder%=EditPad
[EncodedFolders]
Folder
[EncodedFile-Folder-EditPadLite.exe]
lines=445

When I use
[process]
unpack

without any additional parameters like filename or Folder or whatever it workes fine. The folder is build and the file is extracted there.

The command ExtractFile needs additional parameters:

ExtractFile,%ScriptFile%,Folder,Filenam,DirToExtract

I tested a lot but is does not work. Is it really necessary to add the name of the scriptfile (with or without .script or %)? and what exactly means DirToExtract? The whole Directory like "J:\VistaPE\Target\VistaPE-CAPI\Programs\EditPadDavid" ?

ExtractFile,%ScriptFile%,Folder,%ProgramEXE%,%Target_Prog%\%ProgramFolder%

I don't know if there is a good list of %xxxx% variables around.

The specification of the script file is necessary, but I've never had to use anything but %ScriptFile%.

In your case "unpack" probably is best because it handles "Run from RAM", whereas ExtractFile does not. I know that your script does not do "Run from RAM" ... ... ... but there is a global switch you can set to run all programs from RAM, and I think that using ExtractFile might not work properly in that case.

I changed from "Auto" to "German" and run the entire project again. After booting from the new CD I have still the US keyboard settings.

OK, try a download in WinBuilder and try again.

IF it works, please try again with "Auto" selected as the locale.

OK, try a download in WinBuilder and try again.

IF it works, please try again with "Auto" selected as the locale.

I did a download of the entire project again and selected "German". But I am still using WinBuilder 078 SP2 because of the Preloader Error with SP4.
Running the project I get error messages that at least SP3 is necessary (see attachements)

The preloader error has nothing to do with WinBuilder SP2 or SP3, it has to do with the version of %BaseDir%\Projects\VistaPE-CAPI\Base\07-config.script. Try the version I just posted in that other thread. If you need an old version I can dig one up.

The requirement for WinBuilder SP3 has to do with the version of %BaseDir%\Projects\VistaPE-CAPI\Base\Common_Api.script, which I do not control.