6 replies to this topic

[charlestek]

I know this is not quite the right forum to post this question, but I'm not sure where to post.

 

I just downloaded WinBuilder 2013.09.01 and used the "Auto" command to build an iso.

3 Years ago I has build some Win7PE disks using a previous version of Winbuilder, so I am at a loss to figure out exactly what kind of animal WinBuilder 2013.09.01 is.  Maybe I should stick to WinPE7?

 

I am having trouble understanding a few things.  First of all, I have no idea what programs/utilities/tools the basic Windbuilder iso disk has, and can't seem to find that documented. I am also assuming that it builds a Win7PE disk, but I can't find that documented either.

 

I am primarily interested in a bootdisk that has basic utilities to repair and troubleshoot Win 7 and Win 8 64 bit installations.  However, on the download page, http://reboot.pro/fi...342-winbuilder/   their is mention of the "INSTALL" command which states: 
"INSTALL - Download and install apps from http://reboot.pro/files"

however when I go to the files page, I have no clue how to use the syntax INSTALL ??? name of what.

 

I would also think that someone may have put together a package of programs to install for various usages, but can't find anything about that either.

 

I cannot find any tutorials on Winbuilder 2013.09.01 in the tutorials section, so maybe I am missing something???

 

One more issue.  I just downloaded Rufus and was trying to use Rufus to create a bootable usb stick with the bootdisk.iso image created when I ran AUTO with windbuilder.  

 

Unfortunately, RUFUS complains: "This version of Rufus only supports bootable ISO's based on bootmgr/WinPE, isolinux or EFI.  This ISO doesn't appear to use either..."

 

So what are you supposed to use to create a bootable USB stick with bootdisk.iso??

[Brito]

Hi Charles

 

The current edition works in a very simple and reliable manner with the auto command. However, it has limited support for plugins since this kind of feature was not yet fully tested on our side. Next version brings documentation and a stable plugin system.

 

 

In the meanwhile, my recommendation is that you use any of the winbuilder projects that are a bit older but with more features available.

 

[MichaelZ]

The current edition [...] 

 

Probably there should be a new name for that software as it has nothing to do with WinBuilder. At least it should be differenciated through an add-on like WinBuilder 100, WinBuilder 2014 or WinBuilder NG? This would make it much easier to distinguish between classic and new scripts. So far I stick with using 082.

 

Many Greetings
MichaelZ

[Brito]

Hi Michael,

To avoid ambiguity, winbuilder 2013 can be used.

We are using the release date of a given winbuilder to distinguish between versions. For example, the next winbuilder could be 2014.02.15 and be simply referred as wb 2014.

There had been a severe lag of new versions after wb 082 since any change/improvement on the engine would stir a pot of trolling. On our side changes and experiments are needed to cope with modern times, so we are sharing what is being done.

The current winbulder is remarkably stable but this is a work in progress.

[paraglider]

Its old history bit the reason test versions of the old winbuilder later than 082 were met with such derision was because a new certification scheme was introduced and forced on project developers. Projects using the macro library ( common api ) would fail to build if the macro library was not certified with the new scheme.

[pscEx]

Its old history bit the reason test versions of the old winbuilder later than 082 were met with such derision was because a new certification scheme was introduced and forced on project developers. Projects using the macro library ( common api ) would fail to build if the macro library was not certified with the new scheme.

 

The previous "Common API" has beed modified by many people for their own projects. Unfortunatelly they did not change the name to "My API".

 

Therefore exist a lot of so called "Common API".

 

Every developer who seriously works in reboot.pro and follows the rules, can get the app to certify his API.

 

Just for record: You have the app!

 

Peter

[paraglider]

Yes its never a problem for me. I just certify the macro library every time I want to use the test version 83.