[Kullenen_Ask]

Opened this topic just want ask for anybody interested and willing to code a program to build a winpe as a hobby or in his free times. With support of scripts to add programs in it. Custumization support. Different shells support. Preferably open source (Can help other programmers to add their skills). Just as BartPE, Winbuilder, MakePE3 ... I think there is enough people in this forum capable of coding but just less people to open topics about WinPE

[dencorso]

With all due respect, why? Aren't BartPE, Winbuilder, MakePE3 ... enough, already? What's the point in coding yet another PE builder?

[Lancelot_Real]

dencorso, on 07 September 2011 - 03:30 PM, said:

enough, already? What's the point in coding yet another PE builder?

Maybe you are mixing projects with builders because of hybrid designs back to roots....

Yet another PE project not much required, but you can be sure there is high requirement for a Real Good builder.

ps: Kape1-2 , some series of batch builds for pe2/3, and a new coming builder can be added to list, still all not fit builder requirements for various reasons.


I also have same wish with Kullenen_Ask for some years now, hoping a real good programmer, seeing such high requirement on internet, having some freeware open source soul, with free time to develop such thing, one day.

[jaclaz]

Lancelot_Real, on 07 September 2011 - 04:24 PM, said:

.... and a new coming builder can be added to list, still all not fit builder requirements for various reasons.

Not being a programmer, I cannot be of help, even if I wanted to.
But I would like to understand what are these "builder requirements" or, if you prefer, before reinventing the wheel, in which way wheel 2.0 should be made "rounder"?

jaclaz

[Kullenen_Ask]

I do not want to open a hot conversation what is advantages or disadvantages of builders because the topic will change and lose it's aim. X person will say good for his builder, Y person will say no. The aim of the topic is to search and find such a programmer. New ideas and a one more option to choose a builder can not be bad is not it.

Quote

But I would like to understand what are these "builder requirements" or, if you prefer, before reinventing the wheel, in which way wheel 2.0 should be made "rounder"?

It should be as simple as the end user can modify and change everyhing and scripts without losing lots of time.

I found the some way to grap the changes from windows embedded. And want try to suppy. Forexample for media player package i will supply.

1-) Base language independent registry for media player.
2-) Base language specific registry for media player for dependent language
3-) Base language independent file list
4-) Base language dependent mui file list

That winbuilder developers are not yet sure or capable to find the way. There can be dependency resolver in the winpe builder also. For users selected features it can advise as "you should select this scripts, because it is dependent etc." Can not have a media player support without sound support.

Also main script of the new winpe builder already very clear with the only explorer and shell. Maybe i should supply core scripts and wait for anybody can achive to convert them a soft.

This post has been edited by Kullenen_Ask: 08 September 2011 - 02:36 AM

[jaclaz]

Kullenen_Ask, on 08 September 2011 - 01:26 AM, said:

There can be dependency resolver in the winpe builder also. For users selected features it can advise as "you should select this scripts, because it is dependent etc." Can not have a media player support without sound support.

Yes, this is an issue, that I have also being talking about since years, but as I see it is "independant" from the actual builder.

Kullenen_Ask, on 08 September 2011 - 01:26 AM, said:

Also main script of the new winpe builder already very clear with the only explorer and shell. Maybe i should supply core scripts and wait for anybody can achive to convert them a soft.

Yes, but I don't really see problems in the actual tool (one may be sllightly better than another, but not that much) rather I see a lot of "missing" knowledge or settings or the way the available knowledge is scattered around.

As you might know I once put together in a weekend a (very limited and as always half-@§§ed) builder in batch for a very small project, the issue as I see it is not the actual builder but "all the rest".

jaclaz

[Tripredacus]

Wouldn't it be easier to join one of the existing projects and help them complete those goals?

[Kullenen_Ask]

For me not.

[allanf]

Kullenen_Ask, on 07 September 2011 - 01:12 PM, said:

Opened this topic just want ask for anybody interested and willing to code a program to build a winpe as a hobby or in his free times. With support of scripts to add programs in it. Custumization support. Different shells support. Preferably open source (Can help other programmers to add their skills). Just as BartPE, Winbuilder, MakePE3 ... I think there is enough people in this forum capable of coding but just less people to open topics about WinPE

Good idea!

However, the aim is not clear enough... "With support of scripts". What do you mean?

Regards

[Kullenen_Ask]

It means extensions/add ons or what ever it called in english. Probably you understood. If somebody want to add winrar, will add winrar extension. I just called as what winbuilder calls it. I am against the term "script developer" everybody should be capable of writing add ons and everybody should be developer, just it should be easy

[allanf]

Thanks for the quick reply. But please think about your aim. You want someone to develop a whole new scripting language? That anyone can use?

As you know, building a custom PE can be boiled down to just a few fairly basic functions. These things could be presented to a user as a simple scripting language.

Another approach might be for you (yes, you ... ...) to maintain a backend database of all the popular programs and their settings, and a new user is only ever exposed to a GUI for basic customization, and forget about user-scripting altogether. That way, you could end up with a rounder wheel.

Regards

[Kullenen_Ask]

I do not want anybody to develop a new scripting language. It can use just reg files,inf files (as BartPE) and copy file list. And a nice gui.

Kape builder as gui looks like very nice and as expected, just need to be improved of that with more options and customization. Maybe we should ask for author to make it open source.

This post has been edited by Kullenen_Ask: 09 September 2011 - 02:40 AM

[jaclaz]

Kullenen_Ask, on 09 September 2011 - 02:34 AM, said:

I do not want anybody to develop a new scripting language. It can use just reg files,inf files (as BartPE) and copy file list. And a nice gui.

This is what my half@§§ed batches did (obviously without a GUI, let alone a "nice" one).

Kullenen_Ask, on 09 September 2011 - 02:34 AM, said:

Kape builder as gui looks like very nice and as expected, just need to be improved of that with more options and customization. Maybe we should ask for author to make it open source.

as allanf pointed out, to me the real problem is the "fuel", NOT the "engine".

jaclaz

[Kullenen_Ask]

Quote

as allanf pointed out, to me the real problem is the "fuel", NOT the "engine".

Ok. Than, before demand fuel, first of all invent a good engine.

This post has been edited by Kullenen_Ask: 09 September 2011 - 03:22 AM

[jaclaz]

Kullenen_Ask, on 09 September 2011 - 03:20 AM, said:

Quote

as allanf pointed out, to me the real problem is the "fuel", NOT the "engine".

Ok. Than, before demand fuel, first of all invent a good engine.

I would gladly, if I could.

If a batch (no GUI) is OK for you or if you can live with the graphical limitations of a pseudoGUI such as WizApp:
http://wizapp.sourceforge.net/
I could be game.

If what you will provide is:

Quote

1-) Base language independent registry for media player.
2-) Base language specific registry for media player for dependent language
3-) Base language independent file list
4-) Base language dependent mui file list

It can be done in batch allright, it might not be the fastest build engine in the world, but it will work allright, and once the format for the 4 elements above has been established, we may find someone willing to write a "proper" program using the same "fuel".

How will be the ""dependencies" (I mean cross dependencies) managed?
(this is the issue around which I am revolving, creating an effecitve way of represent such dependencies in a database or something like that)

jaclaz

[Kullenen_Ask]

About features when used the Embedded SIM manager it resolves the dependencies. We can use them first of all. But if you talk about file base dependencies i can suppy them also with procmon. All should be teamwork. All will be resolved after the project started. I think early for to talk about such things in this phaze.

In my mind it should be 3rd. levels of core.

*Classes key
*Shell
*Services

I think now services will be default and seperate from features. User could be not selected the winbio but it will be default and working under base wim. He should select winbio from features part to really use it. With working all services base wim not bigger than 170mb. Just the current idea of me. Also can be vlite style and selectable. For the selected service it is not more than a few files and registry. But when selectable also it's dependent services adds on the subject if there is.

So we can not always start from perfect. We should start from somewhere and have improvement. First need to walk, after try to run. Aim should be just try to keep difference between walk and run small.

Most difficult part is Classes key. It is big over 10mb and language dependent. To suply language independent part and to suply different language addons is not seems effective. Probably it will work as what other builders process it.

This post has been edited by Kullenen_Ask: 09 September 2011 - 04:30 AM

[jaclaz]

Kullenen_Ask, on 09 September 2011 - 03:46 AM, said:

I think early for to talk about such things in this phaze.

Well, no.
IMHO most of the problems with existing builders is that they started (mostly) without a "plan" and were adapted/changed n times (or were NOT changed where needed), and this exactly because there was not a "model" of the elements and not much thinking of how to put elements together BEFORE actually starting putting them together.

jaclaz

[allanf]

Kullenen_Ask, on 09 September 2011 - 02:34 AM, said:

I do not want anybody to develop a new scripting language. It can use just reg files,inf files (as BartPE) and copy file list. And a nice gui.

Kape builder as gui looks like very nice and as expected, just need to be improved of that with more options and customization. Maybe we should ask for author to make it open source.

OK. That's clearer. The term "plugin" might be more appropriate. But it's still not for any old noob to come along, write out a few scripts/plugins and have customized versions MediaPlayer, IE9, MMC, explorer and .NET up and running in a PE in half an hour.

Some ideas... The proposed program has a set of directories and a prescribed format for the plugin files. The files are placed in the directories. When the program starts, it enumerates all the valid plugins in the directories and presents the user with a checklist. When an item is checked, its dependencies are automatically checked also. When the "Build" button is pressed, the program parses the plugin files into one big .reg file and one big file-copy list. Then it mounts a wim image (rw), loads the registry hives, runs the big .reg file, copies the files in the big file-copy list, unmounts (commits) the wim image and makes an .iso for CD and/or "flat" structure for UFD. There are scores of other options that could be considered - relating to the PE generally and to the plugins specifically. Where do they all fit in? Each item in the checklist could have it's own configuration window - say a pop-up dialog of radio-buttons, textboxes, etc that would adjust the standard plugin variables.

KAPE looks to have solid mechanics for handling wim files. It's not a bad template in that regard. It's lacking the plugin capability though. PEBuilder's plugin method plus winbuilder's configuration interfaces could provide inspiration and ideas.

It all might seem very familiar, but I think if it is well thought-out, it could be a major improvement on what's already out there.

[jaclaz]

allanf, on 09 September 2011 - 11:23 AM, said:

Some ideas... The proposed program has a set of directories and a prescribed format for the plugin files. The files are placed in the directories. When the program starts, it enumerates all the valid plugins in the directories and presents the user with a checklist. When an item is checked, its dependencies are automatically checked also.

Don't want to seem too "captain obvious", but till now you have described the interface of *any* installer, including that of .msi files or common NSIS ones.
In this respect NSIS could be a very good "scripting engine".

allanf, on 09 September 2011 - 11:23 AM, said:

When the "Build" button is pressed, the program parses the plugin files into one big .reg file and one big file-copy list. Then it mounts a wim image (rw), loads the registry hives, runs the big .reg file, copies the files in the big file-copy list, unmounts (commits) the wim image and makes an .iso for CD and/or "flat" structure for UFD.

That's perfectly fine and presents not much of a problem.

allanf, on 09 September 2011 - 11:23 AM, said:

There are scores of other options that could be considered - relating to the PE generally and to the plugins specifically. Where do they all fit in? Each item in the checklist could have it's own configuration window - say a pop-up dialog of radio-buttons, textboxes, etc that would adjust the standard plugin variables.

That is one of the problems, the other being, still, HOW to manage the "interconnectedness of all things".

allanf, on 09 September 2011 - 11:23 AM, said:

KAPE looks to have solid mechanics for handling wim files. It's not a bad template in that regard. It's lacking the plugin capability though. PEBuilder's plugin method plus winbuilder's configuration interfaces could provide inspiration and ideas.

But is the theme making a rounder wheel or on inventing a new kind of wheel (which incidentally runs smoother)?

allanf, on 09 September 2011 - 11:23 AM, said:

It all might seem very familiar, but I think if it is well thought-out, it could be a major improvement on what's already out there.

Yes, but these would be improvement to the same "paradigm", I had the impression that Kullenen_Ask was pursuing a "new" one.

I will add to my previous notes that - no matter how the actual plugin is built or the code executed of whatever - the thing that I find extremely frustrating and "wrong" is EXACTLY the current paradigm.

The current one (pebuilder) is:

• tick (or untick) a number of checkboxes/radioboxes (possibly add some other settings)
  
• build
  
• if failed try to rebuild changing the checkboxes/radioboxes you set or unset previously

and (winbuilder)

• navigate/expand a tree
  
• tick (or untick) a number of checkboxes/radioboxes (possibly add some other settings)
  
• build (this consists mainly in watching senseless information across your screen and a blue progress bar)
  
• if failed try to rebuild changing the checkboxes/radioboxes you set or unset previously

This is not in any way different from the "installer paradigm", with the difference that the "installer" has a small, finite number of possibilities, is by far "narrower" in scope and it is (normally) duly tested in the few possible configurations.

We all know how many BartPE plugins or winbuilder .scripts are written by people that though good willing have often no idea (or a very little one) on how respectively a plugin or a .script should be written and how it should be tested.

Since the actual engine has no (or very few) provisions for error checking BEFORE build time, the result is the current "click/build/fail/click somethnig else/build fail/loop" situation.

As you might remember I tried to point out this problem since the very early times of winbuilder, but the paradigm has not changed and was on the other hand aggravated by the known syntax changes problems.

jaclaz

This post has been edited by jaclaz: 09 September 2011 - 12:11 PM

[Kullenen_Ask]

The main problem of building a winpe is the user should not have a BSOD after he/she built his/her winpe. The user probably can resolve the problems source if he/she can boot but can not get a feature to work. Main reasons of BSOD's are service errors. To give all services in a main script/add on/extension will solve the main problem i guess. I added theese packages.

Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Application-UX.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-AppSupport-ComBase.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-AppSupport-ComPlus.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-AV-Core.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-DeviceFoundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-DIMS.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-DirectoryServices-AD.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-DriverFoundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Font-Western-Required.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-FS-Core.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Graphics-Platform.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-IE-Core.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-IE-Explorer.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-IE-Foundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-61883.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-acpipmi.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-adp94xx.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-adpahci.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-adpu320.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-amdsata.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-amdsbs.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-arc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-arcsas.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-avc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-bth.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-bthmtpenum.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-bthpan.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-bthprint.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-bthspp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-circlass.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-compositebus.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-digitalmediadevice.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-djsvs.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-dot4.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-dot4prt.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ehstorcertdrv.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ehstorpwddrv.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-elxstor.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-gameport.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hcw85cir.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hdaudio.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hdaudss.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hidbth.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hidir.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hidirkbd.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-hpsamd.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-iastorv.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-iirsp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-image.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-iscsi.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ks.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-kscaptur.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ksfilter.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-lsi_fc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-lsi_sas.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-lsi_sas2.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-lsi_scsi.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmbtmdm.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmgen.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmgl006.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmgl010.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmgsm.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmirmdm.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mdmwhql0.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-megasas.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-megasr.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-mf.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-msclmd.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-msdri.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-msdv.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-multiprt.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-net1k32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-net1q32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-net1y32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-net8187bv32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-net8187se86.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netbc6.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netbvbdx.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netbxndx.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netgb6.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netimm.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netirda.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netk57x.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netl160x.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netl1c86.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netl1e86.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netl260x.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netmyk01.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netnvmx.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netr28.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netr28u.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netr73.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-nettun.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netvfx86.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netvg62.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netvwifibus.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netw5v32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-netxe32.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-nfrd960.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-nvraid.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-pcmcia.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-qd3x86.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ql2300.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ql40xx.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-rawsilo.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-rndiscmp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-scrawpdo.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sdbus.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sensorsalsdriver.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sffdisk.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sisraid2.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sisraid4.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-stexstor.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-sti.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-tape.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-tdibth.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-tpm.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-transfercable.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-tsprint.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ts_generic.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ts_wpdmtp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-umpass.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-usbvideo.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-vhdmp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-vsmraid.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-v_mscdsc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wave.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wceisvista.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wdmaudio.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wdma_usb.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-windowssideshowenhanceddriver.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-winusb.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wnetvsc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wpdcomp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wpdfs.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wpdmtp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wpdmtphw.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-ws3cap.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wsdprint.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wsdscdrv.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wstorflt.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wstorvsc.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wudfusbcciddriver.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wvmbus.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wvmbushid.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wvmbusvideo.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-INF-wvmic.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Installers-MSI.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Interface-Explorer.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Lpk-Setup.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Media-Support.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-MediaPlayer.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-NetFx20.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-NetFx20Client.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-Base.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-Bluetooth.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-Devices.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-EAP.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-Foundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-IAS.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-NASC.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-QoS.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-RAS.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Networking-Services.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Peer-To-Peer-Networking.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Photos-Viewer.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PowerManagement.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-DOLBY-AC3-AudioEncoder.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-MPEG2-Decoder.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-MPEG2-Encoder.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-MPEG2andDolbyDecoder.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-MPEG3.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-MPEG4.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-PremiumCodecs-WMV.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Role-Authorization.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-RPC.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Security-Base.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Security-Credentials.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Security-EFS.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Security-SecureStartUp.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Security-TPM.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-SensorAndLocation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Shell-Accessories.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Shell-Core.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Shell-Foundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Sync.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-SystemControlPanel.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-SystemManagement-AdminTools.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-SystemManagement-MMC.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-SystemManagement-WMI.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-TapiClient.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-TerminalServicesClient.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-usb.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-VSS-Foundation.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-VSS-Service.cab
Dism /image:C:\a /Add-Package /PackagePath:C:\s\WinEmb-Wireless.cab

And result registry hives is 11,7 MB and compressed 1,60 MB in size also with the "Classes" keys language independent. It will only take 4 seconds to add them into the build. There is approximately 7000 files. If we think apporximately 3000 files exist in base winpe winpe builder should copy 3000 files (All are my approximate numbers with my experiences). It will probably take 1 minute to copy all of them (i do not know how much it will take). As we want a componentisezed structure we will not want to give all registry whole but we will seperate them and give as it is but the size probably will be same. I do not think the language dependent part will be big in size probably very very little. My friend ludovici used same keys and he said he can boot with same keys {They are optained without adding a language pack to the build} (i do not know detailed info, he has some explorer crashes (probably because most of language dependent classes missing, it can be only reason such crashes in my side if it works) but it is a big success)

I do not think any wrong scripting will cause BSOD or errors in system as Jaclaz complains a lot. They are just softwares that installs some registry entries in software registry and a bunch of files adds into programs folder. If there is BSOD or errors it is because the wrong scripting about microsoft system features and probably about the system hive services part of that feature.

This post has been edited by Kullenen_Ask: 09 September 2011 - 04:29 PM