Look at the 2 images - 2kquickstart.png 1 & 2 first - then skim the 'read me' and revisit the images, the process of building our release is simple.
One you get the local script part down, test your shortcuts, one to (apup.exe) to download only 'AutoPatcher Updater' & 'AutoPatcher Engine' (don't forget to use 'Options' - 'Remember Selections' - no other releases) / and one shortcut to (apup1006.exe) set to find a local script and run it. Both will have logging. Look at your log file - notice the information written when you run the local script. Btw, this will download 4 files only, don't bother trying to install them, it's simply to test - the test release should be Official when done.
I would like some feedback on the structure of the release, I was thinking that all OS updates (Critical and NonCritical) will go in the main folder but labeled accordingly, and then if we try and add specific categories they would be in their own folder, something like this (also look at how the .apm files are named in the updates folder)...
C:\2kcustom\modules
..............................\Windows 2000 SP4
..............................\Internet Explorer 6
..............................\MDAC 2.8
..............................\.Net Framework
but, if someone goes ahead and mixes this release with another script from autopatcher.com - this could create trouble - remember, we will need to extract the .apm files by hand, I want it to be simple, easy to do, not buiried 2 or 3 folders deep.
The final test script will remove the files and folders from '\windows 2000 sp4' and '2ksp40827.rti', the user will extract a new .rti file (2ksp4xxxx.rti) to the root to make it Official - then the building of the beta script for real. Feedback!!!!!
NOTE: The user will need to remove the old local script, add the new script and edit the shortcut everytime a new script is used - only seconds to do - too much effort? I don't know of another way! I don't think it's smart to use the same name for everything, this can get confusing, the last 4 digits will be all that changes -> 2ksp40827.script / 2ksp40910.script, 2ksp40827.rti / 2ksp40910.rti - a user could always edit out the date when they move the new script in place but this could cause trouble if a mistake is made.
Either way an edit will be needed, simply change the last 4 digits in the shortcut 'Target'. (right-click shortcut - click 'Properties' - 'edit' Target, click 'Apply')
Target: C:\2kcustom\apup1006.exe /log /localscript:C:\2ksp40827.script
...to (what ever the new script date is)
Target: C:\2kcustom\apup1006.exe /log /localscript:C:\2ksp40910.script
Once again, it has taken 5 times longer to write than to do
I'll be busy for a few days, my teacher is moving fast, 86 pages in 2 days yuk. If this sounds too complicated to do please speak up, I have no problem halting the project.
File: 2ksp4files0827.zip
MD5: c82c1b641d4fad8e529db8c3b7e6ce8d
Size: 387410
I've scanned the .zip with Avast and Malwarebytes.













