Kullenen_Ask

No. that will be enough. There were prepared registry entries and file list this post #45 but hotfile delete files very quick and i do not have backups i think.

Read post #71 You miss to [HKEY_LOCAL_MACHINE\SOFTWARE\Classes] full branch and "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer] full branch" part probably. How to work on that brach explained at deep note that starts with "UPDATE to classes.hiv:"

Yes it is.

I did not had any problem. "Windows pe cannot start because the actual SYSTEMROOT directory (x:windows)" this one corresponds to [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\WinPE] "Version"="3.0" "InstRoot"="X:\\" and "is different from the configured one (X:$windows.~bt\windows)." corresponds to [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion] "SystemRoot"="X:\\Windows" in same manner X:\\ --> X:$windows.~bt X:\\Windows --> X:$windows.~bt\windows can work. i did not test. it will be closer to original.

If you make Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\WinPE] "Version"="3.0" "InstRoot"="X:\\" [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion] "SystemRoot"="X:\\Windows" everything will be OK.

No

i solved. i made package additions under different dism combinations. when i prepared base boot.wim with mouse working, i started to contiune to work on it. i think i made package additions under windows 7 sp0, added files under winpe4.0. Only thing it need to change user to admin after boot as your way or need to invent another way to change user after boot. under system user control panel and explorer not works because of the reason i explained. Other eveything seems fine and no problem.

No problem to start pm. But it is just pretty good to continue from here for everybody read and add to the conversation and say opinions. 1-)For to program a winpe builder first you need to try and use other builders such "makepe3" and "winbuilder" 2-)I prefer a explorer like gui, as winbuilder or the fallowing link GUI 3-)At main menu user will select the source media. Program need to detect the media language. Maybe can read "D:\boot\en-us" and detect it is "en-US" language variable. Also can read version number from selected media and say that not supported service pack version. 4-)There is 2 images at boot.wim first one is not bootable and doesn't have client setup packages. Second one bootable and has extra setup files. Maybe user can select which one to use. Probably it will not change anything but can decrease boot.wim size if the first one used. 5-)Program need to export the selected image to a temporary location as BOOTABLE (imagex /export D:\sources\boot.wim 1 C:\Builder\Wim\boot.wim "WinPE" /boot) 6-)There will be 2 mount directories under "Builder" folder (I used C:\a and C:\b in batch file). They can be "C:\Builder\a" and C:\Builder\b" 7-)Program will mount the "C:\Builder\Wim\boot.wim" to "C:\Builder\a" 8-)Program will mount the "D:\sources\install.wim" selected image (can be image selection menu) to "C:\Builder\b" 9-)Program will load the "C:\Builder\a\Windows\system32\config\ default/software/system" hives to current registry as exploreable with regedit as default/software_00/system_00 10-)Program will load our registry settings. http://hotfile.com/dl/130284818/caaf7b8/registry.rar.html 11-)Program will copy the files we from "C:\Builder\b" mounted install.wim directory to our "C:\Builder\a" winpe directory. It will look also language variable "en-US" and copy related files. http://hotfile.com/dl/130284959/639174b/copyfiles.cmd.html 12-)Program will unload the hives and unmount and commit the winpe wim. Unmount the install.wim This will be our main script and will be customizable as file lists and registry part. I explained the most simple as i can. Also this manual should be the most simple manual to create a winpe 3.0 on the internet. If you can do them let us see what you did and we talk about what we will do more in detail. Also read previous posts.

I just mount the wim, load the hives of winpe and full windows to current registry with loadhive.exe program, i copy and paste the registry stuff from full windows hives to winpe hives. I copy the files from install wim to winpe wim. There is no extra ordinary way. What kind of details you need? I am ready to help.

I think microsoft changed Hard Links and Junctions or another thing. I can not export, add package and commit or change any kind without losing mouse support any of boot.wim 1/2 images. Now i started to think wim gets corrupted after i work on it. Also another thing when i use dism from windows 8 when i commit and save, files stays at the mounted driectory. I use vista imagex (ok very old), window 7 sp1 dism, windows 8 dism. Anybody has such problems? Or anybody can do that without problem, which operating system and dism combinations.? Changes: Packages can add to winpe.wim under windows 7 sp0 with dism. There is no problems I made "file add" operations under WinPE 4.0 mounting with new dism. No more problems. Mouse working. working mouse and internet explorer. Note: Control panel and explorer have very long loading times. I investigated and found the reason. It disappointed me because looks serious. Previous we were deleting (Runas "interactive user") keys from classes for to get control panel items to work without have identity errors under system user. Also same settings was working at administrator account. Now it no longer logons as system user deleting that keys result such a long load times. Not deleting also gives identity error. Changed them to (Runas "nt authority\system") it did not worked also. Need a quick solution. Mount/Unmount, Export (did not select "check" option) with vista imagex did not had any problems on wim this time. Mouse stays. I can continue with it. Will make easier. My first profiling file list, i do not know how much sized. Windows Developer Preview Profiling Some extra services to add to winpe 4.0 . Registry Hive format. Windows Developer Preview Extra Service Additions Note: Be sure to add sys or dll files that the services contains without to have a BSOD

I do not understand why there will not be a x86 Winpe (as i understand from the topic you mention) This is x86 im my photos. Hard to believe less than 300Mb for a x64. Probably no x86 support and only a command prompt or pure explorer. It is 530 mb but as i said it has all the files from system32, .net, and assembly folders. I did that because i want to use profilling to decrease size and to find the really used files. But for a winpe such like that is very little because has all files. I have'nt had such small when copied all the files of windows 7 in same manner. I use imagex and dism from versions vista,win7 sp0, win7 sp1, win8. I found that when using commands, version mismatch causes some problems, forgot about that. But i have to use because of resource problems with my pc. Working on Xp. Hımm. I just saw that. Thank you very much for the link. I have not know that there was such Assessment and Deployment Kit (ADK) exist. And it is good that i have subscription now to download it It shows there are packages for WinPE-NetFx4.cab, WinPE-PowerShell3.cab super.

I want a touchable preferably open source builder. But the reason i want that is not for myself. I do not want or care to change the core, Gui, syntax nor i do not know coding. It is just for if the the main programmer decide to retire, other people can continue or a more clever approach (another programmer) can make addons, improve stability, functionality and continue the support time. And do not understand if it is open source why untouchable. There is also a missunderstanding. But not about the meaning of your words. If you compare the inf file of a driver and inf file of the BartPE you can see they are not same kind of stuff. Also what i mean will be a third kind of stuff. It is just Barts way to process its scripts and he gives his scripts the extension inf. We can give .inf or else anything also extention not important, just will be familiar and will be easy to open with notepad. There do not need a inf to reg converter stuff because we do not work with a xp setup routine. My example looks like same as BartPE but it is just an example. I put a complate reg file contents under [RegAdd] There is no inf to reg convertion. Also i forgot to mention copfiles part can be different and should be compatiable with "Optimize_Profile.txt" files as microsoft way. I know a lot of people advise me to use MakePE3. It is most close builder for my needs. Also i tried to support and could not be succed. I explained the reasons in my topic or MakePE3 topics. It is depended to wimb and he can change any/all structure anytime as his needs because he is owner, coder of his work. There is only two options that first to write add ons to MakePE3. If i write a batch it can be useless in one day with an update change of wimb. Other option is to take MakePE3 and call it another name and make it another builder that will result a "rabbit" that will work until "me" support. Will not be universal.

I just downloaded new Windows 8 Developer Preview today. WITHOUT installing it to anywhere i started to work on WinPE works. Until now my previous posts continue to work at WinPE 4.0 (i do not know what they call yet). They are all just a few hours of work and very newly. I can not give much info file list registry etc. stuff. Fresh screenshot. What is new? 1-)There is no need any service. Ux.exe or patch something. Aero is default. I did not see old classic theme. 2-)Assembly folder very small, also at Windows 8.Can result smaller winpe's. 3-)I think directx11 will be need and default. 4-)My mouse not works I do not see cursor. But it is there. 5-)Winpe 4.0 boots always as administrator. I think there is no more System user booting Some needed files for to start explorer it complains missing: d3d11.dll twinapi.dll dcomp.dll d2d1.dll

Of course all of us here for suggestions and ideas. But i am a little confused about all of this stuff. When i look all people says their solutions is different and a new builder, but when a look as a normal user, all uses same gui and same scripts. Somebody should try to explain me what is the difference between Gena, Nuno's http://winbuilder.googlecode.com and Psc nativeEx or others like that. In my side all are same. Only we can say "rabbit" word for theese winbuilder variants and get rid of them. Projects as MakePE3 can not be a rabbit in here. I said a few times that i want to get rid of the API's (i think you call the script systax like that) I do not have problem with the winbuilder GUI. If you can take the project that you gave the link and get it work with scripts as for example this [TargetDirectories] a="Windows\System32" a1="Windows\System32\en-US" b="Windows" b1="Windows\en-US" [CopyFiles] zipfldr.dll=a zipfldr.dll.mui=a1 explorer.exe=b explorer.exe.mui=b1 [CopyWinSXSFolder] x86_microsoft.vc80.crt*.* [CopyWinSXSManifests] x86_microsoft.vc80*.manifest [CopyWinSXSFileMaps] $$_system32_21f9a9c4a2f8b514.cdf-ms [RegAdd] Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\DirectPlay] "Compat1"=dword:00000001 i will not be against to use winbuilder or any of the variants. Just i want is the builder to copy the files under [CopyFiles] to the folders [TargetDirectories] and merge the registry stuff under [RegAdd] to a mounted software.hiv. It should be very easy to code a such program when compared with complex syntax and API's of winbuilder. Everbody easly edit and create scripts.

Check your system.hiv that contains system\controlset\control\product options as "Terminal Server" http://hotfile.com/dl/129714991/552db7e/acb.reg.html

http://technet.microsoft.com/en-us/library/cc766347(WS.10).aspx http://www.windowsfordevices.com/c/a/News/Windows-Embedded-Standard-blog-postings/

My idea also little wheels preferably. One big giant wheel will make fault locating very difficult. Will make it dependent for the inventor. On person should do all. But little wheels more customizable and easy for different people to make small plugins. I do not want anypart of it to be dependent to anybody for it to live long life. Thats why i always say "open source"

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.

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.

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

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.

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

For me not.

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. 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.

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