1. Create the project folder:
...Download 'apupxxx.zip' and extract to drive 'C'. Rename 'c:\apup' to 'c:\win2k'.
...apup131.zip...MD5 Hash: 4381A7CEB003F02D598B8647FEE89D87
or
...Create a new empty folder - 'c:\win2k'. Now, 'copy' (not 'move') from an existing AutoPatcher release 1 file and 1 folder -> '\apup_bin' folder and 'apup.exe' to 'c:\win2k'. This is essentially the same as extracting the contents of the .zip file.
You should have 'c:\win2k' with one sub folder and apup.exe. Now, create the needed shortcut to apup.exe that will find the win2k release list (not the main release.list file).
2. Create a shortcut to apup.exe:
...Right-click apup.exe - scroll to 'Create Shortcut' - left-click once, 'Shortcut to apup.exe' should appear.
...Right-click 'Shortcut to apup.exe' - scroll to 'Properties' - using my example you should see
-> Target: C:\win2k\apup.exe
-> Start in: C:\win2k
We need to edit the Target so it will run apup.exe with logging and locate the win2k release list. 'Copy' the following line and replace the Target link... Note: Make sure to change the path to match the folder name and location of your project if it differs from my example.
C:\win2k\apup.exe /log /listfile:http://www.autopatcher.com/releases/english/win2kcustom/win2kcustom.list
Note: If your folder is 'G:\dumbmike' edit the link accordingly, then 'copy'.
G:\dumbmike\apup.exe /log /listfile:http://www.autopatcher.com/releases/english/win2kcustom/win2kcustom.list
...Click 'Apply' - click 'OK' to save shortcut changes.
...Rename 'Shortcut to apup.exe' to something meaningful and short - 'apupwin2k' - whatever you like. If you highlight the shortcut, 'F2' to rename, or 'right-click' and 'Rename'. You will want to run APUP from this shortcut for this project.
3. Test the shortcut:
Double-click the link you created above, if you did everything correctly you should see a list of 3 scripts - AutoPatcher Updater (apup.exe files), AutoPatcher Engine (autopatcher.exe files), and the Windows 2000 script (the Project). Go ahead and check all 3 scripts, let APUP download the needed files to complete the 'base' folder structure. Look at the apup.log file - what's with all the garbage - this is the expected error when a script is not available. Run APUP again, this time uncheck the Windows 2000 script, click 'Finish', the log should be pretty clean now.
Note: If you see the main release list (not the 3 script list) close APUP and recheck the Target, the issue is usually an extra space or the wrong path in the link.
Note: You can fire up AutoPatcher, you will get a warning (no compatible items found) but you can see if autopatcher.exe is 'Official' - upper right corner in white. This might be a good time to create a shortcut to autopather.exe and bypass the 2 EULAs.
3a. Create a shortcut to autopatcher.exe:
Follow the steps above, right-click the executable, edit the Target, but this time we want this as the Target.
->
C:\win2k\autopatcher.exe /nolicense
-> or if your path is 'G:\dumbmike' -
G:\dumbmike\autopatcher.exe /nolicense
Click 'Apply' - click 'OK' - test the link.
4. Wait for an updated script:
We now need to get a script going
1
