WPI Basics

Suggested Folder layout:

With the above folder layout all your config entries should read like:
%wpipath%\Install\Blah.exe

There is a minor bug in WPI right now that adds an extra set of quotes on the reg before and reg after sections! Please remember to delete the set of quotes from the config section as WPI will add in a set on the reg sections.

There is a "cannot open reboot.js" file error that occurs with Microsoft office programs and hotfixes that we cannot overcome. We are try to track down the single hotfix that is causing this...

Basic Things to remember with WPI:

Some apps require extremely odd switches to install silently and register please go here --> MSFN's Applications forum section as most of the switches for these apps can be found there.

Please search the forum when you are having difficulties.

Forced install DOES mean forced it WILL install the app when WPI exits!

There is no longer a "lite" version of WPI but if you are really worried about size it can be GREATLY slimmed down by hand you can slim it from 3 1/2 megs down to @ 600 kb.

We are very open to suggestions and mods of WPI. Without these WPI would not be that app it is today.

Unless you are doing something advanced with WPI please use the install folder to store your apps.

USSF is not a full one stop shop for switches some apps simply are to odd or need advanced methods to install silently (Like auto-it).

WPI is not meant to only be ran during windows installations, you can run it at any time. Also you can optionally make a standalone WPI disk for easy accessibility.

Remember if you are already using a cmdlines.txt to just edit it when adding the contents of the $OEM$ folder.

WPI now supports the calling of several different switches like so:

        WPI.hta options=useroptions_mritter.js config=config_mritter.js check=Work timer=30

        If a path is not specified for the file, it will assume they are in WPIScripts.

        It will still check for:
        WPI.hta Work 30

        NOTE: Paths can be full (starting with a drive letter) or relative to WPI.hta (starting with '.\' or '..\') and must end in '.js'. Spaces are supported only if a path is provided and properly quoted: (config="c:\space in\file path.js").

To upgrade to a newer version of WPI all you need from your old WPI setup is the config.js file that is in the wpiscripts folder. Then you will have to reset all of the options.

FAQ

1. Q: Which file do I edit so I can add my own programs and tweaks?

   A: There is now a configuration wizard that can be accessed from the main WPI interface.

2. Q: How many apps can I install?

   A: Former versions of WPI supported up to 48 app. This has been changed to unlimited.

3. Q: Progs are displayed in name sort order. Some apps are dependent on each other. How can I achieve correct install order ?

   A: Despite the progs are displayed in their names' sort order, they get installed in order of their definition in config.js. You can override this order by setting.

   order[pn]=[number]

   There's a field for it in the configuration wizard. It says 'Installation order'.

4. Q: I'd like to run cleanup.cmd from WPI. How can I achieve this, so that it's executed at the end of all installations ?

   A: Since the release of 5.0 there is now an execute before and after section configured from the options menu.

5. Q: What should the unattended CD's folder layout look like ?

   A: See the example here.

6. Q: How can I make programs dependent on each other ?

   A: With version 2.9.9 this is now possible. The 2 dependent programs shall both have a unique uid.

   The dependent program must also have a reference to its parent. So you'll have to use the deps property.

   Set deps[pn]=['PARENTUID']. For an example, see the relationship between Office and its resource-kit in the the sample-config.

   A program can be dependent of more than one other progs. In this case, the deps property contains more than one entry:
   deps[pn]=['PARENT1','PARENT2',...].
   See the 'Office Primary Interop Assemblies' in the sample-config for details.

   Note: uid and deps ARE case sensitive !

   It's easier with the config wizard: Both apps must have an Unique ID. Program B is dependent of program A.

   
   Click to Enlarge.
   
    
7. Q: How can I change to install by category ?

   A: It's an option in the options wizard.

8. Q: How do I add a free space after an application ?

   A: In your config.js program definition add a <br /> after the program name. Example:

   prog[pn]=['A sample program<br>']

   Do not add more than 1 linebreaks - the rendering would get messed up.

9. Q: What does disableOnDepsNotMet do ?

   A: a06lp wrote a little tutorial. See here.

10. Q: How do exclusions work?

    A: Imagine 2 apps PA and PB with uid=PA and uid=PB if PA should exclude PB and PB should exclude PA then

    excl[PA]=PB and excl[PB]=PA

    if only PA should exclude PB then

    excl[PA]=PB

    if program PC should exclude PA and PB then

    excl[PC]=PA,PB

    it wouldn't make sense to create counter-productive dependencies. PA shouldn't exclude PB if it's dependent on it!!

    deps[PA]=PB and excl[PA]=PB

    or

    deps[PA]=PB and excl[PB]=PA

    the code used above is pseudo code - don't use it in your config. the right syntac would be:

    excl[pn]=['PA'], excl[pn]=['PA','PB']

    in the config wizard you could just use PA,PB - the wizard makes the rest for you.

    DON'T FORGET TO GIVE EACH APPLICATION USED IN DEPS or EXCL A UNIQUE IDENTIFIER (uid)