Miscellaneous discussion (SetupS)

Discussion in 'Discussion' started by Trouba, Jul 6, 2011.

  1. Trouba

    Trouba Administrator Staff Member

    I had this idea that might be performed by a script or otherwise by SetupS itself. When making a LastOS type image (including ssWPI and apps) usually the OS will be one arch, like x64 only. But when including ppApps (mainly) a lot of space may be taken up by the fact those apps are dual-arch (ppApp.7z archives are larger). Would it be possible (and simple) to create a script or feature of SetupS that automatically re-creates those ppApps into a desired architecture, like x64 only? It could leave the _x64 subfolder normally included in dual-arch ppApps, but it would just omit the _x86 (for example) folder and the .app file shortcuts, etc.
     
  2. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

  3. Trouba

    Trouba Administrator Staff Member

    No, I meant perform the action on the app itself (.apz or open folder) to reduce the size of the ppApp.7z archive (take out the _x86 or _x64 folders and adjust the x64/x86 entries in reg files and cmd's and shortcuts in .app file, etc.).
     
  4. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

    Ah, okay. Essentially you want to split up the (already pre-made) dual-arch packages into 2 arch-specific (one x86 and one x64) .apz's, right?

    If so, yeah, I think a simple cmd/bat script could be made to do that -- possibly incorporated into ssEditor ;)
     
    Trouba likes this.
  5. Trouba

    Trouba Administrator Staff Member

    Yeah, I think that would be great. I normally only make the dual-arch ppApps whenever possible, but then for OS images or certain purposes it would be best to only have the one arch there for size reduction (I think Glenn would like that too for his releases). I had been keeping the apps in the image I was making up to date (that 3 month old folder, hehe -- I keep putting the install off) and was remaking some of the apps into single arch from the original dual-arch ones I made.
     
  6. LiveFreeDead

    LiveFreeDead Administrator

    I agree, this feature would be handy, then we can still whip up a dual arch to share to the repo, but not have to duplicate the work to make single arch packages for our own personal installs.
     
  7. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

    So it turns out Windows 10 wasn't the problem (and neither was SetupS). It was PartitionWizard all along. Because it was an x86 app on an x64 OSArch, SetupS was automatically registering the serial number under "WOW6432Node" -- as it is supposed to -- but PartitionWizard wasn't "seeing" it there. All was needed to fix it was to add some OSArch gates to the reg-file. Or alternatively change the assembly order such that the registry info gets entered before SetupS finds out it's an x86 app.

    Or just make the damn thing a ppApp. LOL
     
    Trouba and bphlpt like this.
  8. Trouba

    Trouba Administrator Staff Member

    "Or alternatively change the assembly order" <-- I had actually thought of that but didn't test it.
     
    The Freezer likes this.
  9. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

    I did test it, but unfortunately was unable to come up with anything workable. The OSArch-gated reg-file seemed to work the best and was the simplest to implement, IMO. The ppApp version uses the same OSArch-gated reg-file as the ssApp -- otherwise, the ppApp would register at both the WOW6432Node location and the proper one.
     
  10. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

    Turns out %ProcessKill% and %WaitForIt% were non-effective all along -- because Process Assembly would pause and wait for an installer to finish, they'd never really get the chance to actually do anything.

    The new components should allow a gateway for some of the more powerfull AutoIt functions of Windows unattended manipulation such as clicking buttons, selecting options, even sending keystrokes.

    Later I'll update the help-file with usage explaination & and examples of the new components.

    For those curious, here's a SetupS .app-file demonstrating a little what they can do. It'll open Notepad, type something, then closes it without saving it (the latest SetupS is required, of course):
     

    Attached Files:

    Trouba likes this.
  11. LiveFreeDead

    LiveFreeDead Administrator

    Well %F@c#Me% that does add some more functionality, I always used WaitForIt.exe in my experiments, so never really looked into the inline version to see how you made it "check during execution", so if it was waiting for the app to finish before it knew to look for the apps window to close it (which then waited for 15 seconds before continuing), I imagine it wouldn't work too well at all before :)
     
    The Freezer likes this.
  12. The Freezer

    The Freezer Lead Developer for SetupS Staff Member

    I forgot to add to the change-log that I've added the AutoIt Window Information tool to ssEditor (Ctrl+I). Look for it in the menubar under Tools. Should be really handy for getting those Control-ID triad's for %ClickMe%. ;)

    I've also added Windows Task Manager (Ctrl+T) to ssEditor's tool menu. Will be useful for both %ProcessKill% and %WaitForIt%
     
  13. Trouba

    Trouba Administrator Staff Member

    You're going to have to make a video, Freezer, with Barry White voice, and explain it all :D But seriously, I may need some examples as to how to use those features.
     
    The Freezer likes this.

Share This Page