but I have to say that I've the feeling that little by little we are re-creating a BartPE, a UBCD4WIN or a Reatogo, i.e. a portable system with (hopefully) hundreds of plug-ins (or scripts) that can run hundreds of apps......
....I am not so sure that this is the right way for the evolution of winbuilder, but however I am here proposing an alternate path, which is not incompatible with the main one, and that could give some more practical uses of Winbuilder.
Starting from the excellent results of picoXP/hojoPE, why don't we start thinking about "specialized" builds?
I mean VERY small builds that ONLY perform a few chores, but do them very efficiently, without "bell and whistles".
As an example, in my post here:
I enumerated what I think are the possibilities to install 2K/XP/2003 when booting from a USB stick.
there are at least 4 possible ways to install XP:
1) from a booted 16-bit environment through WINNT.EXE
2) from a booted 32-bit environment through WINNT32.EXE
3) from a \I386 or \minint folder by invoking SETUPLDR.BIN (which is what the normal install CD does)
4) from an "expanded" pre-install bootfolder $WIN_NT$.~BT like in the flyakite multiboot DVD tutorial
to which you can add:
5) from an .iso using Windows Server 2003 Sp1 or greater SETUPLDR.BIN and RAMDISK.SY_ a method that needing a HUGE amount of RAM for a RAMDISK
Method 1) is fully documented here:
Method 2) is (partially) documented here:
Methods 3) and 5) are in the works here, thanks to cdob:
Method 4) is in the works here, thanks to porear:
As I see it, a derivative of picoXP/MojoPE would be the ideal solution for method 2), with a minimal overhead (cd/disk occupation).....