[TOOL] POWIS - Powerful Windows Setup v1.0.3

Discussion in 'Windows 7' started by George King, May 24, 2021.

  1. maargueb

    maargueb MDL Member

    Jun 9, 2019
    123
    11
    10
    In the setup file SEUP , do I add winrar silent install or normal installer
     
  2. George King

    George King MDL Addicted

    Aug 5, 2009
    838
    764
    30
    #82 George King, Jul 27, 2021
    Last edited by a moderator: Aug 7, 2021
    (OP)
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. George King

    George King MDL Addicted

    Aug 5, 2009
    838
    764
    30
    #83 George King, Jul 30, 2021
    Last edited: Jul 31, 2021
    (OP)
    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?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. (\_/)^(\_/)

    (\_/)^(\_/) MDL Member

    May 31, 2020
    1,168
    1,012
    60
    :worthy:
     
  5. wilenty

    wilenty MDL Member

    Jan 15, 2014
    235
    428
    10
    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.
     
  6. George King

    George King MDL Addicted

    Aug 5, 2009
    838
    764
    30
    @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
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. sleonov97

    sleonov97 MDL Novice

    Aug 9, 2021
    32
    1
    0
    I want to make All-in-One image of Windows 7
    How to make it?
     
  8. alexxf

    alexxf MDL Addicted

    Feb 9, 2008
    778
    527
    30
  9. George King

    George King MDL Addicted

    Aug 5, 2009
    838
    764
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. bphlpt

    bphlpt MDL Novice

    Aug 2, 2010
    44
    17
    0
    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. :)