196 replies to this topic

[phox]

DisplayProperties.Script is too big due to encoded Wallpaper.

It would be better solution to change it so that user could add
its own image during build to avoid unnecessary download.

It is valid for LiveXP and nativeEx project.

Edit: Explorer.Script v016 has option for including Wallpaper and
it should be removed from DisplayProperties.Script altogether.

[TheHive]

Thats one of the reasons I asked to keep the Wallpaper part as a different Script by itself. So that others may improve the Wallpaper addon methods. The way we have it now. THe user is limited and developers have to mess with a working Shell script. I agree that the wallpaper should be taken out of there and just have a solid color. 1MB is just to big.

[pscEx]

Thats one of the reasons I asked to keep the Wallpaper part as a different Script by itself. So that others may improve the Wallpaper addon methods. The way we have it now. THe user is limited and developers have to mess with a working Shell script. I agree that the wallpaper should be taken out of there and just have a solid color. 1MB is just to big.

I agree that wallpaper has to be moved to a separate script.
I (and I think other people, too) do not want to use wallpaper.
So it is much more better to uncheck one script than to search in different scripts whether there is someting abot wallpapers.

Peter

[Brito]

Peter, would you please remove the wallpaper from the explorer script and provide a new script for selecting wallpapers?

Garfield, thanks for the code snippet - will try to add it - my only concern is when a user places the window outside the viewable screen area - but there are also a few workarounds for this task.

Will work next on those network startup issues, I wasn't online when I was working on them so it was something that didn't occured - I'm really looking forward to see more custom distros..

[Holger]

BTW: it wasn't me who included this wallpaper in the "DisplayProperties"-script!

I know this was discussed already: For the future it is good if someone changes the script of another person he should at least give info to the original script-developer.

P.S. cause I will put a new "screensaver.exe" into the "DisplayProperties"-script the problem with the big file should solved then...

[pscEx]

@Nuno
@Holger

I removed the wallpaper from explorer and display properties.
I added a new wallpaper script.

All inside nativeEx_barebone.

@Ove
Please catch the explorer script from nativeEx_barebone and add your latest changes.


Peter

[Brito]

Thanks for the quick script!

Better email or PM Ove - he only catches up with the changes on the end of week..

[MedEvil]

I agree that the wallpaper should be taken out of there and just have a solid color. 1MB is just to big.

Use a jpeg! Despite of what i've read in the forum, it works fine.

[TheHive]

@Ove
Please catch the explorer script from nativeEx_barebone and add your latest changes.
Peter

Thanks for the update.

[TheHive]

Use a jpeg! Despite of what i've read in the forum, it works fine.

I tried selecting a jpg but it doesnt show up.

[MedEvil]

I tried selecting a jpg but it doesnt show up.

Then you havn't included the picture and fax viewer in your build.

[MedEvil]

@Nuno
Hadn't noticed your new folder view for the scripts!
Very nice!

[TheHive]

Then you havn't included the picture and fax viewer in your build.

I just checked and yes the Explorer script says to include them.




I just noticed Winbuilders blinking where Source is needed. Very nice.

[pscEx]

Three issues to new update mechanism:

• Is there a way to upload no-script files from WinBuilder?
  I had to upload WBverify.ctl and finally did id by usual FTP.
• In a test project, the new WBverify.ctl was not regognized as new and not checked in the Update Center tab.
• In the project where it was upload from, it was checked as new!

Peter

[pscEx]

Three issues to new update mechanism:

• Is there a way to upload no-script files from WinBuilder?
  I had to upload WBverify.ctl and finally did id by usual FTP.
• In a test project, the new WBverify.ctl was not regognized as new and not checked in the Update Center tab.
• In the project where it was upload from, it was checked as new!

Peter

My own answer to #2 and #3:
I did not upload the new updates.ini

Peter

[Brito]

Peter: At the moment it isn't yet possible, but might come handy to have this feature so I'll also work on it..

A small beta (6) has been uploaded to avoid confusions and replace the previous wich had the startup bug, this one will ensure that the web adress is placed on the box before trying to download an updates.ini when internet is available.

[TheHive]

The update beta (6) works as expected when first launched it has default webserver addresses to go to.

[MedEvil]

I just checked and yes the Explorer script says to include them.
I just noticed Winbuilders blinking where Source is needed. Very nice.

That's curious. I can use jpeg as wallpaper.
Get back to you, when i have figured out what's going on.

[pscEx]

In beta 6, there is still a Download Center issue.

Currently there are two URLs hardcoded inside WinBuilder (for short, let's call them A and B ).
BTW to the forum's administrators: If I ommit the space following the B, I see a smiley!

Start WinBuilder in a new folder, download from A and exit WinBuilder.
Start WinBuilder again. You do not see B.

Reason: When leaving WinBuilder, WinBuilder.ini is written with the used URLs. Should be with available (hardcoded) and additionally used URLs.

Peter

[MedEvil]

@Hive
Sorry, completely forgot, that was one of the things i fixed in my project, when i started with WB. Silly me!

Did some more checking and it's a really stupid idea, since it causes more waste of space, not less.
If you use a bmp you may need about 1MB.
If you use a jpeg you only need 150KB - On the CD! As soon as windows starts, there is a bmp created from the jpeg on the Ramdrive. So now you use 150KB+1MB.

So, the only nice thing to add, would be if the script that adds the wallpaper, could convert a jpeg to bmp on the fly.

[thunn]

Couple quick notes:

New WB, v68b6, upper progress not working with downloads.

Also, the Boot-Land forum keeps asking me to re-enter my credentials.
Maybe these two things are related by some twisted cosmic string.
(like my thrashed OS)

Guess I'll restore the last backup image shortly just to be sure all's well here.

Thanks for the update Nuno!!!

[TheHive]

@Hive
Sorry, completely forgot, that was one of the things i fixed in my project, when i started with WB. Silly me!

Did some more checking and it's a really stupid idea, since it causes more waste of space, not less.
If you use a bmp you may need about 1MB.
If you use a jpeg you only need 150KB - On the CD! As soon as windows starts, there is a bmp created from the jpeg on the Ramdrive. So now you use 150KB+1MB.

So, the only nice thing to add, would be if the script that adds the wallpaper, could convert a jpeg to bmp on the fly.

Is this the way it works on a real PC also?

[MedEvil]

Is this the way it works on a real PC also?

Yes!

[ktp]

Hello,

I only see this short description:
> WinBuilder is a free application designed to create small bootable environments.

Could somebody tell me more details on WinBuilder, is it another BartPE-like ? If yes, so what are its added value vs. BartPE/UBCD4Win etc.. ?
From the screen shots it seems interesting. Thanks in advance.

[TheHive]

Hello,

I only see this short description:
> WinBuilder is a free application designed to create small bootable environments.

Could somebody tell me more details on WinBuilder, is it another BartPE-like ? If yes, so what are its added value vs. BartPE/UBCD4Win etc.. ?
From the screen shots it seems interesting. Thanks in advance.

Hi ktp and welcome to the board. Yes the projects are very interesting.

you can read the WinBuilder's History and get an overall impression of the project.
http://www.boot-land.....der's_History

Let me quote some things from another post.

I believe I read somewhere that WinBuilder is not meant to be a replacement for BartPE. Maybe, maybe not. But is WinBuilder really lacking any significant features found in Bart et. al.?

Yes and no. Winbuilder is meant to stand by its own. But its roots are from the BartPE forum.

WinBuilder's History
http://www.boot-land.....der's_History

What is not?

Taken the features from the scripts and the application itself, WinBuilder is definitively not intended to be a bart's PE builder alternative, replacement nor a OEM builder from bart.

Bart's PE builder creates nearly flawless good bootable PE discs.