49 replies to this topic

[smiley]

New version of the CopyAndExpand.Script is ready

-Removed some uneeded Hal*.dll's that were copyed in the system32 and in the drivers folder.
-Added a new image made by TheHive

Standard Copy and expand
Standard Hive script
PicoXP Hive script(updated by psc)
MKIso script

[TheHive]

Can regular users get a direct link please. Too many subfolder to try to find it.

[smiley]

Ok , I have updated the hives.script and the make iso script .Now the Create iso script creates the boot loader and not the hives .script.

The links are int he first post

if you get any errors please post

[Brito]

This is an excellent improvement on the former scripts, thanks for updating!

[pscEx]

I have been working with smiley today to update the upload area. We communicated invisible for the forum by MSN. Now he left the forum and I found two small issues. In order not to introduce troubles for uploaders, I changed two files smiley uploaded: The copy&expand and the hives script. The old scripts are still inside the upload area - renamed to .old. When smiley is back, please check!

Peter

[TheHive]

I will wait to download untill its settled. Please say when they are ironed out.

Why not create an old folder and the version number. If a Scipt developer or someone else changes things in a script they could just name it with an old at the end of the Script. That way if something goes wrong a backup will be available if anyone reports something is wrong with it.

[smiley]

What have you changed?

[pscEx]

I will wait to download untill its settled. Please say when they are ironed out.

Why not create an old folder and the version number. If a Scipt developer or someone else changes things in a script they could just name it with an old at the end of the Script. That way if something goes wrong a backup will be available if anyone reports something is wrong with it.

Apearenty Smiley and me are currently the only ones uploading into this area. We'll discuss your suggestion.
(Currently we agreed that a developer starting an update renames updates.ini to updates.ini.tmp. Tis is a flag to other devvelopers not to download or change anything)

Peter

[phox]

-Removed some uneeded Hal*.dll's that were copyed in the system32 and in the drivers folder.

Thank you! You could also remove Halsp.dl_ and Kdcom.dl_ files from your .script.

If Ove remove from his USBSticks.script folowing files: usbd.sy_, usbehci.sy_, usbohci.sy_, usbuhci.sy_, usbport.sy_, usbhub.sy_ and usbstor.sy_, there will be no more unnecessry files in drivers folder!

[TheHive]

Have the scripts been fixed. And are they fine to download now.

[pscEx]

ProjectInfo.ini is missing on the ISO.

Peter

[TheHive]

There is something wrong with Standard Hive script. If you try to save the Script with a right click and Save Target as you get an extension of htm [Standard-3-Hives.htm]. If you save it as Standard-3-Hives.Script you get the following when you open Winbuilder:


Ill have to wait for this to be fixed in order to try to test them.


The rest seemed to download fine.


I like the naming convention using Standard and Pico, but I dont like that they dont have a version number next to them.

[smiley]

The links and the errors with update are fixed

[TheHive]

Thanks for the fixes.

Create Iso by default has the Run WIndows from RAM active. If you run it like that and you dont know its active the user will get an error once they try to boot, because the files are not present.

Updated to your new Scripts. It seems the building process stops when Winbuilder is processing the Hives Script.

Hives Stops Processing


Log
[attachment=295:attachment]

[pscEx]

Updated to your new Scripts. It seems the building process stops when Winbuilder is processing the Hives Script.

Hives Stops Processing

Check 2 items:
1st You must have version 004 of Basedir\Archives\Build\EmptyHive.Script.
2nd Either WinBuilder.ini or Basedir\Projects\Standard\script.project must contain:

[Variables]

...

%EmptyHive%=%BaseDir%\Archive\Build\EmptyHive.script

Peter

[TheHive]

1. I have EmptyHive Version=042
I dont now if there is a new update im not aware off. Can you attach the update.


2. That line seems to be in the Basedir\Projects\Standard\script.project

[pscEx]

1. I have EmptyHive Version=042
2. That line seems to be in the Basedir\Projects\Standard\script.project

1.
2.
Inspite of the high version number this script is very old (the version 042 remains from the OpenBuilder version when it has been created).

In this special case you cannot make the standard update. You have to download the actual version from here.

Good luck!

Peter

[TheHive]

Thanks. Will test.
The one I had came with Standard Release build 50.

[pscEx]

Thanks. Will test.
The one I had came with Standard Release build 50.

And in the mean time smiley and me did change a lot (including these old versions) inside WinBuilder_sandbox!

Peter

[TheHive]

The Results so far: Desktop looks ugly.



log
[attachment=296:attachment]

[pscEx]

The Results so far: Desktop looks ugly.

What's ugly? your computer in the lower lright and the recycle bin uper left?

Mine is like
[attachment=297:attachment]

Peter

[TheHive]

Youre screenshot looks good. And the icons blend to the blue background.

I actually wouldnt mine if we had the option to move the Recycle bin to the left side. It would be good if we could get an option to where we choose the oder the icons should be in the desktop.

I dont get a Start bar or Taskbar. And the icons dont seem to blend to the background.


I have it running with 256MB of RAM

If I open the MyComputer I get this:

[pscEx]

Youre screenshot looks good. And the icons blend to the blue background.

I actually wouldnt mine if we had the option to move the Recycle bin to the left side. It would be good if we could get an option to where we choose the oder the icons should be in the desktop.

I dont get a Start bar or Taskbar. And the icons dont seem to blend to the background.
I have it running with 256MB of RAM

If I open the MyComputer I get this:

If you mean 256MB for Qemu, I just tried it and got
[attachment=299:attachment]

As you see everything most perfect!

If you have only 256MB RAM in your computer, which is very improbably for me, sorry ....

But I think you have more memory. So allow me some theory:

You are a (or the only one in the forum) real beta tester. That demands frequent downloads of new versions ...
Unfortunatelly the current new versions inside WinBuilder_sandbox not really are built to work with every script from the latest 050 release. Maybe that is the root of all of your troubles.

How I work:

I have
1st the latest released version (here 050) in WinBuilder\...
2nd the always complete actual version from <upload>WinBuilder_sandbox in WinBuilder_01\...
WinBuilder_01 isd also the target where I copy new betas to (like currently 051).

Maybe you try the same!

BTW because of your troubles (maybe tomorrow) I'm going to wrote a titorial 'How To Setup and Maintain a Beta Testing Environment'

Pewter

[TheHive]

Yes! I have more then 256MB actual RAM.

Normally I keep a backup of the old working Scripts and thats one of the reasons I ask authors to put the version number next to the post. Then I back them up and replace them with the new updates.

Your tutorial might help to better organize the beta testing procedure.

It might help also to list the active scripts that you all testing when building the final ISO.

I just updated to the 051 beta 1 but I still get the same results.

[pscEx]

It might help also to list the active scripts that you all testing when building the final ISO.

With one of your first posts I thought about that it would be good to document the script's version.
I changed ProjectInfo to report not only the execute time but also the version of the script.
That could be published now.
(If you would like to have a short view, download it at my FTP domain. It will really not disturbe anything, but some WinBuilder maintenance functions like update etc. are not yet working or work wrong)
But currently I'm working on an extention which writes the version into the log (provided the .script developer calls my new function) and the final upload will take one ro two days..

Peter