What is the advantage over the standard Acronis PE builder? My launcher does this: (1) Display a splash screen (2) Read in serial from text file, recode it to Acronis reg format, add to registry (3) On first launch in PE, copy files needed to start to services to system32\ (snapapi.dll) and system32\drivers (snapman.sys, fltsrv.sys) (4) Start the services (this is why "sc.exe" is needed in your PE (5) Launch Acronis. So using a launcher is just a case of "If it can be done, I want to try it". You don't really NEED a launcher, but in that case you need some type of "Winbuilder" script when building your custom PE (PE fans should know about these already, but there do not seem to be a lot of PE fans here on MDL). Why do I need a "launcher" script? (I like Autohotkey, but it could be other languages) msi file from the full Acronis installer, extract pe.zip from the msi, then extract x86 and 圆4 program files from that (these include VC runtime files, some services files, etc.) As I mentioned before, just around 50-70mb in total needed from the large installer. Which files from Acronis do I use? I could answer later in more detail, but the main idea is to use 7zip in a batch to extract an. (3) Or take a boot.wim from a Windows iso. to extract boot.wim, then some batches to extract a few extra files from a full "install.wim" index (for example "sc,exe" is needed to start the Acronis services, this file has to be taken from an install.wim index, then inserted in boot.wim using Wimlib. (2) From any ESD download, using Wimlib etc. Where do I get them from? (1) ADK PEs, these are the "cleanest", I download these using direct links (no full ADK install needed). Click to expand.Base PE could be any version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |