This mean only one thing. Start reading what users write to you. If you can’t understand, simply use Google and start learning. If it still doesn’t help, sell your PC / laptop and leave this.
I want to add new building option for next version. My goal is to build universal MultiSystem ISO for USB. I will add some kind of new config file MultiAIO.ini where we will define ISO names for merging. I have added some modifications into unreleased XP2ESD v1.6 to be fully compatible with all newer files deployment used in POWIS. 1) XP2ESD 2) Vista 3) 7 4) 8.0 5) 8.1 6) 10 7) 11 At the end of this process we should get one huge install.esd with all Windows versions from XP and newer. This setup will be really universal as Snappy Driver Installer will install all DriverPacks during setup automatically. But some applications are OS limited. I need to create new addition for RunOnceEx - I'm thinking about some kind of change of current TXT files into INI with some OS restriction to avoid uneeded errors during RunOnceEx phase. CCleaner.ini Code: Parameter=/S MinOS= MaxOS= OS Definitions should be Code: XP = 5.1 2003 = 5.2 Vista = 6.0 7 = 6.1 8.0 = 6.2 8.1 = 6.3 10 = 10.0 For example for XP and Vista needs CCleaner 5.64 as it's latest one that run under these OSes. If I create XP / 7 / 10 AIO I will need to have old and new installer. CCleaner564.ini Code: Parameter=/S MinOS=5.1 MaxOS=6.0 CCleaner.ini Code: Parameter=/S MinOS=6.1 MaxOS= What do you think about it?
Why do you insult other users of this forum? Your scripts also not perfect, people are not perfect, the world are not perfect... But you can wrote it because your nickname here is "George King"? Why you don't move your computer to the garbage and stop insult others? The question: was to difficult for you, or? ONE BIG -1 FROM ME! @Tito @ancestor(v) @Yen Please add the "thumbs-down", especially for messages like that.
@wilenty See all him posts with my answers, then you should understand. I was very patient and I really tried it, but he always ignoring our advicing
I like this idea a lot. FWIW, I think all(?) of the possible probable NT version = MS OS pairs would be: 5.0 = 2K 5.1 = XP 5.2 = XP 64, 2003, 2003 R2, Home Server 6.0 = Vista, 2008 6.1 = 7, 2008 R2, Home Server 2011 6.2 = 8, 2012 6.3 = 8.1, 2012 R2 10.0 = 10, 2016, 2019, 2022, 11 I agree that it would be very unlikely that an app compatibility would "skip" an OS, so it would seem to be easiest to do some sort of OS range, ie min--max, such as you suggested. And, coding-wise, I like the idea of using the NT version number. But instead of having to include another file, why not just include the info in the app name, such as: SomeApp_v1.0.0_NT_5.1-10.0_ OtherApp_v1.0.0_Win_10.0-10.0_ AnotherApp_v1.0.0_Win_6.1-6.3_ Having the info in the app name makes it obvious for the user. BUT, regardless of using the app name or a separate file, MS threw you a curve when both Win 10 and Win 11 are called NT 10, or no longer using the NT designation. So apps that are not Win 11 compatible, or Win 11 only, create a problem. You'll either have to come up with some way to differentiate them, or, instead of NT version, you'll need to use the OS "name", such as: SomeApp_v1.0.0_Win_XP-11_ OtherApp_v1.0.0_Win_11-11_ AnotherApp_v1.0.0_Win_7-10_ This might be easier for the normal user to understand anyway. Leading the OS names with _Win_, or _NT_, and bracketing the min and max such as _min-max_ should give your software a relatively easy way to identify them, if they are there. If they are not there, I guess you should assume _Win_XP-11_? You could also indicate "everything up to and including" as _Win_-10_ and "everything starting with and after" as _Win_11-_. Just some other ideas to consider.
Do not forget about Ukrainian language (Note: Change txt extension to inf, because I can't upload inf file due to the MDL restriction)
I understand that a driver pack is needed so that the "boot.wim" can detect the "install.wim or install.esd" Is there a generic driver to avoid putting drivers from different computers?
i ran powis on windows 7 x64 host, with MSE real time protection disabled. when running directly from the .cmd file (admin), errors occur on step 13 and step 14: Code: Drag and drop ISO or extracted Windows Setup location here: E:\Downloads\en_wind ows_7_ultimate_with_sp1_x64_dvd_u_677332.iso [1] Extracting ISO [2] Creating autounattend.xml [3] Adding Unattended files [4] Adding dynamic drivers folder [5] Adding DriverPacks support [5] Adding Setup folder [6] Adding Updates folder [7] Adding Activation support [9] Adding Multi-Unattended support [10] Modifying bootloader [11] Modifying setup launch in boot.wim [12] Applying RunOnceEx icon patch [13] Exporting boot.wim The system cannot find the file specified. [14] Recompressing boot.wim [ERROR] Can't open "E:\Downloads\POWIS_v1.0.3\_output\sources\boot.wim" read-onl y: No such file or directory ERROR: Exiting with error code 47: Failed to open a file. [15] Building ISO OSCDIMG 2.54 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (7500 files in 1550 directories) Scanning source tree complete (7818 files in 1585 directories) Computing directory information complete Image file is 4431872000 bytes (before optimization) Writing 7818 files in 1585 directories to E:\Downloads\POWIS_v1.0.3\POWIS.iso 100% complete Storage optimization saved 1497 files, 80785408 bytes (2% of image) After optimization, image file is 4373407744 bytes Space saved because of embedding, sparseness or optimization = 80785408 Done. Process finished, press any key to exit... when running from cmd prompt (admin) everything is OK (SAME ISO): Code: [1] Extracting ISO [2] Creating autounattend.xml [3] Adding Unattended files [4] Adding dynamic drivers folder [5] Adding DriverPacks support [5] Adding Setup folder [6] Adding Updates folder [7] Adding Activation support [9] Adding Multi-Unattended support [10] Modifying bootloader [11] Modifying setup launch in boot.wim [12] Applying RunOnceEx icon patch [13] Exporting boot.wim [14] Recompressing boot.wim "E:\Downloads\POWIS_v1.0.3\_output\sources\boot.wim" original size: 481786 KiB Using LZX compression with 16 threads Archiving file data: 464 MiB of 464 MiB (100%) done "E:\Downloads\POWIS_v1.0.3\_output\sources\boot.wim" optimized size: 158832 KiB Space saved: 322953 KiB [15] Building ISO OSCDIMG 2.54 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2007. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (7500 files in 1550 directories) Scanning source tree complete (7819 files in 1585 directories) Computing directory information complete Image file is 4594532352 bytes (before optimization) Writing 7819 files in 1585 directories to E:\Downloads\POWIS_v1.0.3\POWIS.iso 100% complete Storage optimization saved 1497 files, 80785408 bytes (2% of image) After optimization, image file is 4536055808 bytes Space saved because of embedding, sparseness or optimization = 80785408 Done. otherwise everything works good (if i run it from cmd prompt)
lol, despite working as is, unlike xp2esd v1.6, this tool is stuck in it’s 1 year old 2021 v1.0.x days, with very old approaches, such as 2021’s approach uses bcd to create winre, meanwhile the new xp2esd powis launcher has recovery environment button and more options, and some others can i ask, why?