Digg this topic Add to my del.icio.us Submit to SlashDot 2 Pages V   1 2 >  
Reply to this topicStart new topic
> About new version VistaPE 010
online
post Oct 12 2007, 05:32 AM
Post #1


Advanced Member
***

Group: Members
Posts: 199
Joined: 28-July 07
Member No.: 9,829


Italy


Hi all! (IMG:../forums/style_emoticons/default/smile.gif)

I have some questions about topic title that are not very clear for me...

1. Why not provide a Downloads specific section for VistaPE-Beta 010?

2. Is a script created for 008 version compatible with last version (010)?

3. About RunFromRAM option: I see that new sintax provides for this type of string

CODE
RunFromRam,%pCheckBox1%
, but it seems to me that it doesn't work like previous one.
If CheckBox is or is not ichecked seems to me that then program folder creation occurs always in "X:\Program Files" directory... (IMG:../forums/style_emoticons/default/confused1.gif)
Furthermore I saw some scripts in new version that show the following sintax (that I've always use with success):
CODE
If,%pCheckBox2%,Equal,true,SET,"%DestDir%","Program#$sFiles\%OutDir%"
If,%pCheckBox2%,Equal,false,SET,"%DestDir%","Programs\%OutDir%"
If,%pCheckBox2%,Equal,true,SET,"%LinkDir%","%SystemDrive%\Program#$sFiles\%OutDir%"
If,%pCheckBox2%,Equal,false,SET,"%LinkDir%","y:\%OutDir%"
System,RefreshVars
and now I am a bit confused...

4. About RegHive the issue is the same: I see
CODE
RegHiveLoad,WB-Software,%RegSoftware%

and then also
CODE
RegHiveLoad,Tmp_software,"%HIVE_HKU%"

And my confusion is increasing...

Where I'm wrong?
Every suggestion is a lot appreciated! (IMG:../forums/style_emoticons/default/thumbsup.gif)

Go to the top of the page
 
+Quote Post
TheHive
post Oct 13 2007, 06:56 PM
Post #2


Advanced Member
***

Group: .script developer
Posts: 1,858
Joined: 14-July 06
Member No.: 5



QUOTE(online @ Oct 12 2007, 12:32 AM) *
Hi all! (IMG:../forums/style_emoticons/default/smile.gif)

I have some questions about topic title that are not very clear for me...

1. Why not provide a Downloads specific section for VistaPE-Beta 010?

2. Is a script created for 008 version compatible with last version (010)?

3. About RunFromRAM option: I see that new sintax provides for this type of string


1 and 2 are good questions.
Maybe Nuno can create two VistaPE Download sections for scripts. One for 10 and one for 9. That is if they are not compatible to each Vista Projects.
Go to the top of the page
 
+Quote Post
psc
post Oct 13 2007, 07:20 PM
Post #3


Guru
***

Group: .script developer
Posts: 3,049
Joined: 14-July 06
From: Korschenbroich, Germany
Member No.: 3


Germany


QUOTE(TheHive @ Oct 13 2007, 08:56 PM) *
1 and 2 are good questions.
Maybe Nuno can create two VistaPE Download sections for scripts. One for 10 and one for 9. That is if they are not compatible to each Vista Projects.

I see it quite different:
Since some days VistaPE seems to be a 'foreign' project which
  • is moved from here and became 'third party'
  • resides at a server w/o physical connections to boot-land.net (as far as I understood)
  • can still be download by the standard WinBuilder download mechanism
  • must still be 'compiled' by WinBuilder.
For me, the organization of VistaPE download servers is not longer in Nuno's responsibility.

Peter
Go to the top of the page
 
+Quote Post
Nuno Brito
post Oct 13 2007, 07:53 PM
Post #4


Advanced Member
***

Group: .script developer
Posts: 4,207
Joined: 13-July 06
From: Azores
Member No.: 1


Portugal


XP and Vista based projects are merging to a common script format - which is excellent to join forces and avoid having to write a separate script to work with a single project.


This might be confusing at the moment but it will soon make more sense in a couple of months when this new API is well implemented.

The basic goal was to create a new script method that would make our scripts work regardless of the project where they are placed - this also extends any script to work under present day Windows OS's and future ones to come.

-------

If you look on the download section here on boot-land - the section where old VistaPE specific scripts are is now called VistaPE 09.

The new scripts for VistaPE > 010 are all found inside the "Application scripts" category - it's no longer a specific section for VistaPE because this new format makes scripts compatible across all projects that support this new api.

--------

This means that all scripts inside this section work both on VistaPE, LiveXP and NativeEx all the same and without any changes.

But also means that older scripts (both on LiveXP and VistaPE) are no longer compatible on the newer versions - but the good news is that they can easily be converted.

Just post the script you wish to convert and I'll help you.. (IMG:../forums/style_emoticons/default/smile.gif)


----------

Much of this was discussed here: http://www.boot-land.net/forums/index.php?showtopic=2707

This new api is meant to seriously simplify the life for everyone creating new scripts - only a few lines are needed in most cases.

Here's a list of available functions (most are self explaining but don't hesitate to ask in case of doubt):

CODE
[variables]
%ProgramTitle%=My Program
%ProgramEXE%=myProgram.exe
%ProgramFolder%=My_Program


[process]
; Use these examples to see how these commands can be applied inside your app scripts

Add_Shortcut
Add_Shortcut,StartMenu
Add_Shortcut,StartMenu,Games
Add_Shortcut,QuickLaunch
Add_Shortcut,AutoStart
Add_Shortcut,Desktop

require_file,myLibrary.dll

unpack
unpack,AnotherFolder

hive_load,HKU
reg_add,0x1,"%reg%\Classes\filetype","test","1"
hive_unload,HKU


associate_file,html
associate_file,html,open,c:\test.exe
associate_file,html,open,c:\test.exe,/run=%2
associate_file,html,edit
associate_file,html,icon,c:\test.exe
associate_file,html,icon,%systemroot%\System32\Shell32.dll,-153


(IMG:../forums/style_emoticons/default/smile.gif)
Go to the top of the page
 
+Quote Post
phox
post Oct 14 2007, 05:37 AM
Post #5


Advanced Member
***

Group: .script developer
Posts: 495
Joined: 8-August 06
Member No.: 134



QUOTE(Nuno Brito @ Oct 13 2007, 06:53 PM) *
This new api is meant to seriously simplify the life for everyone creating new scripts - only a few lines are needed in most cases.

Here's a list of available functions (most are self explaining but don't hesitate to ask in case of doubt):

CODE
[variables]
%ProgramTitle%=My Program
%ProgramEXE%=myProgram.exe
%ProgramFolder%=My_Program
[process]
; Use these examples to see how these commands can be applied inside your app scripts

Add_Shortcut
Add_Shortcut,StartMenu
Add_Shortcut,StartMenu,Games
Add_Shortcut,QuickLaunch
Add_Shortcut,AutoStart
Add_Shortcut,Desktop

require_file,myLibrary.dll

unpack
unpack,AnotherFolder

hive_load,HKU
reg_add,0x1,"%reg%\Classes\filetype","test","1"
hive_unload,HKU
associate_file,html
associate_file,html,open,c:\test.exe
associate_file,html,open,c:\test.exe,/run=%2
associate_file,html,edit
associate_file,html,icon,c:\test.exe
associate_file,html,icon,%systemroot%\System32\Shell32.dll,-153


(IMG:../forums/style_emoticons/default/smile.gif)


This solution is enough only for single level Start Menu shortcuts.

To preserve Apps folder configuration in Start Menu shortcut structure
a multilevel shortcut configuration is necessary.

This is double level example:

CODE
[Variables]
%ProgramTitle%=sCDWriter
%ProgramEXE%=sCDWriter.exe
%ProgramFolder%=%ParentItem%\sCDWriter
%ParentItem%=CD&DVD
%DestDir%=Program#$sFiles\%ProgramFolder%

[Process]
DirMake,"%TargetDir%\%DestDir%"
ShellExecute,Hide,"XCOPY","#$q%FBox_Source%\*.*#$q #$q%TargetDir%\%DestDir%#$q /e /y"
Add_Shortcut,StartMenu,%ProgramFolder%
If,%pCheckBox1%,Equal,True,Add_Shortcut,Desktop

[Interface]
TextLabel_Source="Source folder",1,1,261,17,87,25,8,Bold
FBox_Source=%BaseDir%\Projects\Programs\CD&DVD\sCDWriter,1,13,253,43,206,28,dir
pCheckBox1="Add shortcut on desktop",1,3,19,191,200,18,True


For multilevel introduction of more Parent Items is necessary.

In Vista type of scripts, generated with MakeScript, used variables are:

%Executable%=sCDWriter.exe
%OutDir%=CD&DVD\sCDWriter
%PName%=sCDWriter

Are those interchangeable with:

%ProgramTitle%=sCDWriter
%ProgramEXE%=sCDWriter.exe
%ProgramFolder%=sCDWriter?

Pedro Le should adapt MakeScript to new api and sctructure.

This script generator should be put in "Tools" folder
and started by selecting "Create script" in WinBuilder.
Go to the top of the page
 
+Quote Post
online
post Oct 14 2007, 11:33 AM
Post #6


Advanced Member
***

Group: Members
Posts: 199
Joined: 28-July 07
Member No.: 9,829


Italy


@ Nuno and @ phox

(IMG:../forums/style_emoticons/default/thumbsup.gif) Thank you so much! (IMG:../forums/style_emoticons/default/thumbsup.gif)


Sooner or later (thank you all for helping) I should wish reach perfection... (IMG:../forums/style_emoticons/default/rolleyes.gif) (IMG:../forums/style_emoticons/default/smile.gif)









OT/"vanity" (IMG:../forums/style_emoticons/default/blush.gif) /btw: hey, Nuno: what do you think about this? (IMG:../forums/style_emoticons/default/tongue.gif)


Go to the top of the page
 
+Quote Post
Nuno Brito
post Oct 14 2007, 11:44 AM
Post #7


Advanced Member
***

Group: .script developer
Posts: 4,207
Joined: 13-July 06
From: Azores
Member No.: 1


Portugal


Phox, adding a parent item would break away flexibility inside the script itself.

The part that should be improved is api.script itself to correctly identify the multilevel folder structure.

QUOTE
%ProgramFolder%=%ParentItem%\sCDWriter
%ParentItem%=CD&DVD
%DestDir%=Program#$sFiles\%ProgramFolder%


A code like the one you've posted will make your app script static again don't you think? (IMG:../forums/style_emoticons/default/wink.gif)
Go to the top of the page
 
+Quote Post
phox
post Oct 14 2007, 11:52 AM
Post #8


Advanced Member
***

Group: .script developer
Posts: 495
Joined: 8-August 06
Member No.: 134



QUOTE(Nuno Brito @ Oct 14 2007, 10:44 AM) *
Phox, adding a parent item would break away flexibility inside the script itself.

The part that should be improved is api.script itself to correctly identify the multilevel folder structure.
A code like the one you've posted will make your app script static again don't you think? (IMG:../forums/style_emoticons/default/wink.gif)


I agree if api is addapted accordingly and MakeScript too!

What about compatibility of variable names from VistaPE and LiveXP?
Go to the top of the page
 
+Quote Post
Nuno Brito
post Oct 14 2007, 12:41 PM
Post #9


Advanced Member
***

Group: .script developer
Posts: 4,207
Joined: 13-July 06
From: Azores
Member No.: 1


Portugal


QUOTE(phox @ Oct 14 2007, 11:52 AM) *
I agree if api is addapted accordingly and MakeScript too!

What about compatibility of variable names from VistaPE and LiveXP?



This was already introduced in the latest versions nativeEx, liveXP and VistaPE projects - all present app scripts can be exchanged between each other without changes.

There are still some rough edges needed to solve regarding read only media vs rewritable media but this is still under discussion.

App scripts are no longer static to VistaPE nor LiveXP - from here forward it's the respective project who will adapt itself to the script and not the script who will need to use each project custom variables.

It's much simpler to modify and continue to improve a script.project and api.script files than it would be re-writting hundreds of app scripts available. (also worth mentioning that this way we're assuring that app scripts can be recycled and used for years and years without changes)

Imagine it as the CSS stylesheet on the HTML world - it's much simpler to modify the template rather that it would be modifying the style manually on each page, wouldn't it?



If we want to install an app script on our computer - just adapt the settings on script.project and off you go installing your program inside your own windows or even an offline windows (great for unattended installs).

MakeScript only needs to use the proposed api functions and variables as it is already doing.

------

Peter also created a very important feature that allows to install DLL and OCX files on the target OS and now we get scripts that rival with features that don't even exist on professional .MSI installers since these scripts have no restrictions regarding where they can be installed.

In the unattended world it's also common the use of "Addons" which are packages that install silently on the host system. They are mostly used by nlite and other programs and will install themselves when Windows is being installed on the computer.

Now imagine the power of these app scripts - you can literally integrate them inside the Windows Install files and create a new DVD that installs windows and already includes all these apps installed. Instead of waiting an extra hour to see everything installed you substancially decrease the needed time to install - which is a real time save when doing several of these installs a day.

It has nothing to do with VistaPE or liveXP - but it's another feature that can be explored soon and this is one of the reasons why only generic values are used and a good argument to keep only using the bare minimum - which also helps others understand quickier how to create their own scripts since this template will become fairly stable and flexible to use throughtout the years to come.

We're really growing to a "universal" method.. (IMG:../forums/style_emoticons/default/cheers.gif)
Go to the top of the page
 
+Quote Post
phox
post Oct 14 2007, 01:44 PM
Post #10


Advanced Member
***

Group: .script developer
Posts: 495
Joined: 8-August 06
Member No.: 134



QUOTE(Nuno Brito @ Oct 14 2007, 11:41 AM) *
This was already introduced in the latest versions nativeEx, liveXP and VistaPE projects
- all present app scripts can be exchanged between each other without changes.


Folder structure in "Program Files" and "Start Menu" shortcuts scructure,
should mirror folder structure of "Apps" in all Projects to benefit from UniScripts!

QUOTE
MakeScript only needs to use the proposed api functions and variables
as it is already doing.


Api and MakeScript should support multilevel (presently three levels),
folders/shortcuts structure.

MakeScript v14 doesn't do it correctly:

1. Vista type:

CODE
[Variables]
%Executable%=Ghost.exe
%OutDir%=Ghost
%PName%=Ghost
%ParentItem%=BackUp
%DestDir%=Program#$sFiles\%OutDir%
%LinkDir%=%SystemDrive%\Program#$sFiles\%OutDir%

[SetVariables]
Set,"%DestDir%","Programs\%OutDir%"
Set,"%LinkDir%","y:\%OutDir%"

[Process]
If,%CheckBox_RunFromRAM%,Equal,True,Run,%ScriptFile%,SetVariables
System,RefreshVars
DirMake,"%TargetDir%\%DestDir%\Ghost"
// FileCopy,"%FileBox_Source%\*.*","%TargetDir%\%DestDir%\Ghost"
ShellExecute,Hide,"XCOPY","#$q%FileBox_Source%\*.*#$q #$q%TargetDir%\%DestDir%\Ghost#$q /e /y"
TXTAddLine,%ES%,"!CD\%DestDir%\%Executable%,%ParentItem%\%PName%.lnk,!CD\%DestDir%","Append"

[Interface]
Bevel_1=Bevel_1,1,12,21,12,171,39
CheckBox_RunFromRAM="Run from ram (boot.wim)",1,3,33,23,168,18,False
Bevel_Source=,1,12,233,12,243,69
TextLabel_Source="Source folder",1,1,261,17,87,25,8,Bold
FBox_Source=F:\F\Programs\BackUp\Ghost,1,13,253,43,206,28,dir


2. Api type:

CODE
[Variables]
%ProgramEXE%=Ghost.exe
%ProgramFolder%=Ghost
%ProgramTitle%=Ghost
%ParentItem%=

[Process]
RunFromRam,%CheckBox_RunFromRAM%
Add_Shortcut,StartMenu,%ParentItem%
Add_Shortcut,Desktop
DirMake,"%TargetDir%\%WorkDir%\Ghost"
// FileCopy,"%FileBox_Source%\*.*","%TargetDir%\%WorkDir%\Ghost"
ShellExecute,Hide,"XCOPY","#$q%FileBox_Source%\*.*#$q #$q%TargetDir%\%WorkDir%\Ghost#$q /e /y"
Process_log

[Interface]
Bevel_2=Bevel_2,1,12,21,12,171,39
CheckBox_RunFromRAM="Run from ram (boot.wim)",1,3,33,23,168,18,False
Bevel_Source=,1,12,233,12,243,69
TextLabel_Source="Source folder",1,1,261,17,87,25,8,Bold
FBox_Source=F:\F\Programs\BackUp\Ghost,1,13,253,43,206,28,dir


Both ask for ParentItem and I doubt that they are compatible.
Go to the top of the page
 
+Quote Post
« Next Oldest · VistaPE · Next Newest »
 

2 Pages V   1 2 >
Fast ReplyReply to this topicStart new topic

Collapse

> Similar Topics

  Topic Replies Topic Starter Views Last Action
No new Pinned: Topic has attachmentsVistaPE new site and new version
08.10.2007
58 NightMan 1,849 Today, 01:57 PM
Last post by: NightMan
No new Pinned: Topic has attachmentsNew nativeEx WEB site
31 psc 2,041 Yesterday, 08:56 AM
Last post by: psc
No new Pinned: New features on WinBuilder.exe
Post your ideas and suggestions for the next version
35 Nuno Brito 3,327 14th October 2007 - 10:00 PM
Last post by: TheHive
No new votes Poll: New slogan for WinBuilder
Replacing the "Build bootable Environments"
30 Nuno Brito 1,597 14th October 2007 - 03:39 PM
Last post by: online
No new votes Poll: New name for WinXPE/WindowsXPE project
8 h7se 687 13th October 2007 - 07:16 PM
Last post by: TheHive


 

Display Mode: Standard · Switch to: Linear+ · Switch to: Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum

- Lo-Fi Version Time is now: 16th October 2007 - 01:59 PM

MKPortal ©2003-2006 mkportal.it