Error linking scripts from archive

I'm getting strange errors on linked scripts from Archive

#946 [Script] Processing script: Registry Editor

#947 [Info] File [%BaseDir%\Archive\Tweaks\regedit.script] Version [6]

#948 [Failed] FileCopy - Failed to copy [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\regedit.exe] to: [%BaseDir%\Target\i386\system32] 

#949 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\aclui.dl_] Dir:[%BaseDir%\Target\i386\system32] 

#950 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\clb.dl_] Dir:[%BaseDir%\Target\i386\system32] 

#951 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\ulib.dl_] Dir:[%BaseDir%\Target\i386\system32]

Probably, I'm missing something
Once again, I'm asking for a place to get complete information about what's going on
I really need to know answers on following questions:
- How to download last versions of the scripts?
- How to use Sandbox?
- Where to find list of updates in scripting language?
- Where to get information about incompatibility issues like the errors above?

I'm dissapointed
Alexei

I'm getting strange errors on linked scripts from Archive

#946 [Script] Processing script: Registry Editor

#947 [Info] File [%BaseDir%\Archive\Tweaks\regedit.script] Version [6]

#948 [Failed] FileCopy - Failed to copy [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\regedit.exe] to: [%BaseDir%\Target\i386\system32] 

#949 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\aclui.dl_] Dir:[%BaseDir%\Target\i386\system32] 

#950 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\clb.dl_] Dir:[%BaseDir%\Target\i386\system32] 

#951 [Failed] Expand - Failed to expand file: [Warning! This is not meant to run, only to edit scripts from the archive folder\i386\ulib.dl_] Dir:[%BaseDir%\Target\i386\system32]

Probably, I'm missing something
Once again, I'm asking for a place to get complete information about what's going on
I really need to know answers on following questions:
- How to download last versions of the scripts?
- How to use Sandbox?
- Where to find list of updates in scripting language?
- Where to get information about incompatibility issues like the errors above?

I'm dissapointed
Alexei

Did you run the Archive project?

Peter

- How to download last versions of the scripts?

'Official' scripts you can find in the sandbox.
New scripts you can download from the adresses the developer show in their posts.

- How to use Sandbox?

Have a look into the forum and find this

- Where to find list of updates in scripting language?

Hints are in the Beta publications. In a released version use the context menu.
Descriptions in the Wiki are not allways the latest information.
I suggest: If you have troubles with a statement and solved it, go update the Wiki.

- Where to get information about incompatibility issues like the errors above?

Unfortunatelly nowhere - better said: In many posts of users' issues.

@Nuno:
If you have 30(000...) seconds time, think about a version entry in the dependency functionality and a 'Needs WinBuilder version xxx' in the script [Main] section.

Peter

@Alexei - this error shows because of the source folder on the archive project - it's propositated to avoid overwriting existent projects..

@Nuno:
If you have 30(000...) seconds time, think about a version entry in the dependency functionality and a 'Needs WinBuilder version xxx' in the script [Main] section.

I know it was promissed a long time ago, sorry for not adding it sooner..

I've been a bit busier than usual around here - within the next couple of weeks I'll be going back to europe and study a bit more about networking. Hopefully I'll also get a more time to work online and improve these features on winbuilder.exe (and some vacances from work..)


Thanks for the reminder!

'Official' scripts you can find in the sandbox.
New scripts you can download from the adresses the developer show in their posts.

Have a look into the forum and find this

Hints are in the Beta publications. In a released version use the context menu.
Descriptions in the Wiki are not allways the latest information.
I suggest: If you have troubles with a statement and solved it, go update the Wiki.

Unfortunatelly nowhere - better said: In many posts of users' issues.

Peter

Rather poor picture, don't you agree

this error shows because of the source folder on the archive project - it's propositated to avoid overwriting existent projects..

What Archive is for, but to use scripts from it And the only correct way to use archived script (as I see it) is to link it from the project Do you suppose I should manually copy scripts from Archive? In fact, this problem came from saving user settings inside the scripts

@Peter,
Can you, please, make nice (step-by-step) tutorial out of this post and place it to "Tutorials"?
Also, this post describes how to setup the Sandbox. But how to use it on regular basis?

@everybody
If you try to make a list of all manual steps (each "look for", each "click", etc.) that have to be done to do every simple thing you would be as terrified as me I bet, you wouldn't have enough patience to do that What I'm saying is not that everything is not good, but that we have to take care of automation of what we're doing on everyday basis.
I always thought that major advantage of using WinBuilder is simplisity and automation. Really, you just select "features" you want from the script list and hit the Run button, then play with your Build in qEmu Unfortunately it's turning into something opposite, that requires a lot of time, patience, and concentration, something complex to use and complicated with unpleasant surprizes, like the one I had today. Isn't it too much manual work for the 21 century?
I strongly believe that tracking updates and using sandbox has to be as simple as building PE with WinBuilder! Otherwise, what we need it for?
Ok, if you disagree, just let me know, otherwise let's decide how and when we gonna fix it.

Thanks,
Alexei

Thumbs up for simplicity!

I strongly believe that tracking updates and using sandbox has to be as simple as building PE with WinBuilder! Otherwise, what we need it for?

When I created the sandbox it has been a collection of running(?) scripts which Nuno could attach as a bundle to the new release.
It was thought to be used by developers.
I did not think about sandbox being an actual repository for all users.

But I'm thinking now ... (and what functionality to add)
Somebody to help me with suggestions?

Peter

Simple solution:
The forums will have an active link for the latest working ziped sandbox. It will be a self extracting 7z or rar exe wich will ask the user to select the folder of winbuilder.Then it extracks itshelf and runs an autoit script that comes with the package and installs the new scripts.

Easy to make - Easy to use

In this way the user and the developers will be sure that evrything are installed corectly.


John

Simple solution:
The forums will have an active link for the latest working ziped sandbox. It will be a self extracting 7z or rar exe wich will ask the user to select the folder of winbuilder.Then it extracks itshelf and runs an autoit script that comes with the package and installs the new scripts.

Easy to make - Easy to use

In this way the user and the developers will be sure that evrything are installed corectly.
John

Good Idea!

I'm thinking about 'make it much easier' without autoit etc; just say 'load to ...', then delete and create 'to' and unzip into 'to'

Question: The 'to' maybe the current %baseDir%?

Peter

Good Idea!

I'm thinking about 'make it much easier' without autoit etc; just say 'load to ...', then delete and create 'to' and unzip into 'to'

Question: The 'to' maybe the current %baseDir%?

Peter

I don't understand well what you mean.
I'll try to make one with my idea. Why don't you make one with yours? We can the select the best.

I don't understand well what you mean.
I'll try to make one with my idea. Why don't you make one with yours? We can the select the best.

tomorrow...
It's late now.

Peter

Well here is my sample.
It can be a good start

Download

If you want to use it keep a backupof you winbuilder directory. It is even better if you download a fresh package of Winbuilder.

BE CAREFULL WHEN YOU USE IT. IT MAY DISTROY YOUR WINBUILDER FOLDER. IT IS CREATED FOR TESTING PURPOSES AND IT IS NOT OFFICIAL.


John

Looks nice and simple. What if they dont have a Winbuilder downloaded. If you try to install it to a folder it reports that it needs Winbuilder and cant find it. When this happnes the user might be given a link to where to get the beta release since most Sandbox releases will work with the latest Winbuilder and might not be compatible with some older Winbuilders.

Also if they do update where the Winbuilder.exe is, the end user might need the latest tools folder. We should start a Sanbox for latest Tools used within the Tools folder.

Download

I can's get URL's like that http://smiley.boot-land.net\winbuilde...61018_1930.exe/
I'm getting "Host Name Lookup Failed"

Alexei
PS
Shouldn't it have at least "readme" ?

I can's get URL's like that http://smiley.boot-land.net\winbuilde...61018_1930.exe/
I'm getting "Host Name Lookup Failed"

Alexei
PS
Shouldn't it have at least "readme" ?

The url is "http://smiley.boot-l...61018_1930.exe"

not "http://smiley.boot-l...1018_1930.exe/"

Download

The url is "http://smiley.boot-l...61018_1930.exe"

not "http://smiley.boot-l...1018_1930.exe/"

Download

Looks very nice.

I think that there has to be a 'background mechanism'.

Your exe has the name of the latest sandbox zip. For easy use it should be named 'Winbuilder_sandbox.exe'.
The link to this 'Winbuilder_sandbox.exe' can be pinned.
When somebody uploads a new ZIP (with date and time in the name) he has also to generate the new exe.

Peter

I tried to follow sandboxing instructions step by step, writing down what happening
Some of the problems I ran into, stil exist with smiley's tool, though it's a very goog beginning

Alexei


1. Copy your current WinBuilder installation to a new location, maybe C:\WBTest.
Understood as:
- Make new directory
- Copy all files from current WinBuilder location to this directory.
Problems:
- What was meant by "installation" is unclear at this point.
- Do we need to copy Source if it's under \Source\ ?
- Do we need to copy contents of \ISO\, \Target\, and \Custom\ ?
Proposed solution:
- Make a script to copy what's needed

2. Delete the folders C:\WBTest\Archive and C:\WBTest\Projects.
Understood as written
Problems:
- User's projects are lost
Proposed solution:
- Make a script that would preserve user's projects

3. Download and unzip the latest WinBuildewr_Sandbox<date>.zip here into C:\WBTest.
Understood as:
- open http://update.boot-land.net/
- find latest WinBuildewr_Sandbox<date>.zip
- download it
- unzip it (allow override WinBuilder.ini as stated in 5.)
Problems:
- "Here" refers to http://update.boot-l...060914_1230.zip, which does not exist.
- Presence of <date> doesn not allow automation
- Overriding WinBuilder.ini mentioned in 5. !?
- User settings in WinBuilder.ini are lost
- updates.ini and other files may be present
Proposed solution:
- Always copy the latest version of WinBuildewr_Sandbox<date>.zip to WinBuildewr_Sandbox_Latest.zip
- Make a script to perform this step (merging WinBuilder.ini).

4. Take care of the changed url http://update.boot-land.net/
Problems:
- This seems to be remark to 3., but it looks like separate step.

5. During unzip allow to overwite WinBuilder.ini.
Problems:
- This seems to be remark to 3., but it looks like separate step.

6. Do not run the project immediatelly
Problems:
- Excessive step. Even starting WinBuilder was not mentioned.

7. First check the paths in the project's tab and the RAM ISO path inside the MkISOFs script!
Understood as:
- Start WinBuilder
- Open Path tab
- Specify your settings
- Open Scripts tab
- Select "Standard XP/2003 project"
- Select "(Build) Create ISO" script (this is MkISOFs.script)
???????
Problems:
- Hard to understand.
- Has to be interpreted along with previous sentense, which looks like separate step.
- Opening Path tab and setting values is missing.
- There is no "project's tab"
- MkISOFs script should be mentioned as "Create ISO" as in scripts list
- "RAM ISO path" is not present in MkISOFs.script
- Missing necessary change of the path in PicoXP "(Addons)Boot from RAM"
Proposed solution:
- Make a script to copy/merge necessay info from scripts in previous WB version to Sandbox.

Thanks for all your responce

But now I need your help.
I have created this package using WinRAR. It is a Rar-Sfx exe that just unpacks and replaces the existing files.

What I need is some help writing a tiny program that will come with the package and do the rest work.
My problem is that I know to write programs ONLY in vb6. So if I create the program and the setup will not work for someone who doesn't have the vb6 runtime dll. So I need a volunteer for this job!
Actually what I have done is to insert the files, the boot-land logo and the icon.


Thanks,
John

@Alexei
A lot of good ideas and suggestions!
One of them I followed immediatelly:

- Always copy the latest version of WinBuildewr_Sandbox<date>.zip to WinBuildewr_Sandbox_Latest.zip

All the others: Give me some time ...

Peter

BTW: You are allways very exact. Should the name really be WinBuildewr_Sandbox_Latest.zip? (I know my typo from the post)

@Alexei
A lot of good ideas and suggestions!
One of them I followed immediatelly:
All the others: Give me some time ...

Peter

BTW: You are allways very exact. Should the name really be WinBuildewr_Sandbox_Latest.zip? (I know my typo from the post)

Yes, you may notice w is next to e on eng kbd. I was so bored, my finger slipped

On serious note, I don't know how you gonna manage to make developers upload fresh scripts to the sandbox
BTW, very nice feature would be to log all uploads and let this log be available for viewing

On serious note, I don't know how you gonna manage to make developers upload fresh scripts to the sandbox
BTW, very nice feature would be to log all uploads and let this log be available for viewing

Currently I upload on request of the developers or if I changed something.
The number of requesting developers is not very large. The list contains smiley.

For the log: Good idea

There is a scriptdata.ini which shows some info about the files in the sandbox. I update this file on every upload. I'm going to look whether I can change it to something like a log.

Peter

Thanks for all your responce

But now I need your help.
I have created this package using WinRAR. It is a Rar-Sfx exe that just unpacks and replaces the existing files.

What I need is some help writing a tiny program that will come with the package and do the rest work.
My problem is that I know to write programs ONLY in vb6. So if I create the program and the setup will not work for someone who doesn't have the vb6 runtime dll. So I need a volunteer for this job!
Actually what I have done is to insert the files, the boot-land logo and the icon.
Thanks,
John

I see three cases here:
- Initial rollout of freshly downloaded WinBuilder.
- Merging downloaded updates with what user already have in another directory.
- Merging previous SnadBox with updates (in-place).
What you did is perfect for the first case.
Merging is rather difficult, but it can be done in any prog language, including VB6
BTW, in VB it's so easy to do really tricky system things and it's becoming de-facto standard for scripting (making cmd-scripts obsolete), so don't be shy about VB6 I always wanted to learn it, even bought a thick book "VB Developer's Guide for the Win32 API"

Merging scripts with downloaded ones is a real PITA. It's tempting to do it with WinBuilder script, but I'm afraind the implementation may become too cryptic and therefore unmanagable. Theoretically, it can be done with cmd-scripting, but it's sooo hard to deal with % and " in it However, in any "normal" prog language merging two scripts (I mean user-settings) is not a big deal.

So, having simple app that sets parameters in downloaded scripts out of old ones, using WinBuilder script for the rest becomes reality In addition, such application can produce a nice log about all updates and changes in the scripts, which is essential for troubleshooting and just a good educational reading

And, additionally, initially upacked WinBuilder may contain just two scripts:
- SetStable.script
- SetSandbox.script
So it would be like:
- download your Rar-Sfx
- run it
- start WinBuilder
- choose setup of your choise
- click "Run"
- when done, click "Refresh" and you have everything almost ready to go

What do you think?

Alexei

- Initial rollout of freshly downloaded WinBuilder.
- Merging downloaded updates with what user already have in another directory.
- Merging previous SnadBox with updates (in-place).

Let's achieve on by one. I have a good solution for merging Winbuilder default scripts,previous Sandbox and new Sandbox:

In the Winbuilder directory, there will be a file that holds a list of scripts and link including their path. The sfx exe will extract all it's contents in a folder named Updates in the winbuilder directory. Then the Install program will read the list of the existing scripts and will will compare it with its list. Then it will copy the needed files.

Let's achieve on by one. I have a good solution for merging Winbuilder default scripts,previous Sandbox and new Sandbox:

In the Winbuilder directory, there will be a file that holds a list of scripts and link including their path. The sfx exe will extract all it's contents in a folder named Updates in the winbuilder directory. Then the Install program will read the list of the existing scripts and will will compare it with its list. Then it will copy the needed files.

@smiley, alexei and all others

Let's slow down!

When I created the sandbox I wanted to have a repository of latest(?) versions which Nuno could use for releases.

Never it has been my intention (as the name says) to have an 'official' database of scripts.

So, let's use the sandbox as an inofficial script collection and work with it like it is!

Peter

When I created the sandbox I wanted to have a repository of latest(?) versions which Nuno could use for releases.

Never it has been my intention (as the name says) to have an 'official' database of scripts.

So, let's use the sandbox as an inofficial script collection and work with it like it is!

Why not use the contents of Sandbox as an official updates collection?