How to Use an Unofficial Script?
yoggydog
08 Oct 2011
I tried the Search function to no avail, I cannot seem to figure out how to use a local .script file with AutoPatcher. This is in regards to the one that Mazabuka posted for Win2K. I'm sorry if this has been posted before but I truly could not locate a tutorial on how to do this. Thanks.
ViroMan
08 Oct 2011
any file that says .script at the end is for APUP you can make apup use local scripts but, that post is rather old and so are its scripts.
Anyways... the commands to make APUP use a local script is "/localscript:<FileName>" Take out the quotes and the <FileName> obviously.
AutoPatcher will automatically load all all APM files that it is capable of reading.
Anyways... the commands to make APUP use a local script is "/localscript:<FileName>" Take out the quotes and the <FileName> obviously.
AutoPatcher will automatically load all all APM files that it is capable of reading.
_def_x_
08 Oct 2011
I feel bad, I forgot about Mazabuka going to all the trouble and the script never really got tested. I also noticed he left it for me to have a look at, by the time he uploaded it I had already left the project.
Have a look at the only docs available, search for 'localscript', look at the script and pay close attention to what files go where. Here's the docs...
... http://www.autopatch...st&attach_id=51
Here's a script run locally... apup.exe /log /localscript:C:\apup\win2k.script
Hopefully this is pretty easy to follow. apup.exe is running with logging enabled. localscript is looking for the script, in this case I named it win2k.script, in the apup root directory. You want logging so you can check the errors. Keep the script as short as possible, 2k.script would work. Locate the apup directory in a short path - C:\apup.
Run APUP, and expect many errors with a beta script - check after each run.
It would be nice if someone could get this script updated and Official, at least once, since Mazabuka went to all the trouble. yoggydog, I can try to help you but only via IRC, it is so much easier talking in real time, and like Viroman said, that script is once again outdated and many lines of code will likely need commenting out until you get the updated information. I think I still have the rti tool so the release could get signed, just not likely uploaded to the ftp - your call Yoggydog
Have a look at the only docs available, search for 'localscript', look at the script and pay close attention to what files go where. Here's the docs...
... http://www.autopatch...st&attach_id=51
Here's a script run locally... apup.exe /log /localscript:C:\apup\win2k.script
Hopefully this is pretty easy to follow. apup.exe is running with logging enabled. localscript is looking for the script, in this case I named it win2k.script, in the apup root directory. You want logging so you can check the errors. Keep the script as short as possible, 2k.script would work. Locate the apup directory in a short path - C:\apup.
Run APUP, and expect many errors with a beta script - check after each run.
It would be nice if someone could get this script updated and Official, at least once, since Mazabuka went to all the trouble. yoggydog, I can try to help you but only via IRC, it is so much easier talking in real time, and like Viroman said, that script is once again outdated and many lines of code will likely need commenting out until you get the updated information. I think I still have the rti tool so the release could get signed, just not likely uploaded to the ftp - your call Yoggydog
Mazabuka
11 Oct 2011
gUiTaR_mIkE, on 08 October 2011 - 07:11 PM, said:
I feel bad, I forgot about Mazabuka going to all the trouble and the script never really got tested. I also noticed he left it for me to have a look at, by the time he uploaded it I had already left the project.
Have a look at the only docs available, search for 'localscript', look at the script and pay close attention to what files go where. Here's the docs...
... http://www.autopatch...st&attach_id=51
Here's a script run locally... apup.exe /log /localscript:C:\apup\win2k.script
Hopefully this is pretty easy to follow. apup.exe is running with logging enabled. localscript is looking for the script, in this case I named it win2k.script, in the apup root directory. You want logging so you can check the errors. Keep the script as short as possible, 2k.script would work. Locate the apup directory in a short path - C:\apup.
Run APUP, and expect many errors with a beta script - check after each run.
It would be nice if someone could get this script updated and Official, at least once, since Mazabuka went to all the trouble. yoggydog, I can try to help you but only via IRC, it is so much easier talking in real time, and like Viroman said, that script is once again outdated and many lines of code will likely need commenting out until you get the updated information. I think I still have the rti tool so the release could get signed, just not likely uploaded to the ftp - your call Yoggydog
Have a look at the only docs available, search for 'localscript', look at the script and pay close attention to what files go where. Here's the docs...
... http://www.autopatch...st&attach_id=51
Here's a script run locally... apup.exe /log /localscript:C:\apup\win2k.script
Hopefully this is pretty easy to follow. apup.exe is running with logging enabled. localscript is looking for the script, in this case I named it win2k.script, in the apup root directory. You want logging so you can check the errors. Keep the script as short as possible, 2k.script would work. Locate the apup directory in a short path - C:\apup.
Run APUP, and expect many errors with a beta script - check after each run.
It would be nice if someone could get this script updated and Official, at least once, since Mazabuka went to all the trouble. yoggydog, I can try to help you but only via IRC, it is so much easier talking in real time, and like Viroman said, that script is once again outdated and many lines of code will likely need commenting out until you get the updated information. I think I still have the rti tool so the release could get signed, just not likely uploaded to the ftp - your call Yoggydog
Mazabuka
11 Oct 2011
Since w2k is no longer supported by Microsoft, the script is unlikely to be significantly out of date, if at all. The script does, however, need to be tested to confirm that it downloads correctly and places the downloaded files in the correct folders.
I'd be more than willing to fix all reported errors found in the download script.
In addition to adding the patches that ware missing from the last official version of the download script, I've also fixed all the APM files that did not function correctly on my machine. So I would expect very few problems with the APM files ... but then again, no two w2k machines are configured the same way!
Two of the APM files are out date, being the ones for the Root Certs and MRT - so these two will definitely result in errors if you try to download them from Microsoft.
Is there anybody that can make the RTI tool available to me, as well as explaining how to use it?
How do we go about getting the script made official ones the bugs have been ironed out?
I'd be more than willing to fix all reported errors found in the download script.
In addition to adding the patches that ware missing from the last official version of the download script, I've also fixed all the APM files that did not function correctly on my machine. So I would expect very few problems with the APM files ... but then again, no two w2k machines are configured the same way!
Two of the APM files are out date, being the ones for the Root Certs and MRT - so these two will definitely result in errors if you try to download them from Microsoft.
Is there anybody that can make the RTI tool available to me, as well as explaining how to use it?
How do we go about getting the script made official ones the bugs have been ironed out?
ViroMan
12 Oct 2011
The RTI tool can only be use by trusted script managers. Its a tool that can be used to sign any script. It could be used maliciously to fool others into thinking a bad script is officially supported by the AutoPatcher Team.
Now im not saying your one of those people but, if you work with us a little while longer im sure you will eventually get access to it. Until then any one of the current script managers can sign it for you.
also... I think you can modify the apms you made to remove root certs and MRT domenico's common module takes care of them.
Now im not saying your one of those people but, if you work with us a little while longer im sure you will eventually get access to it. Until then any one of the current script managers can sign it for you.
also... I think you can modify the apms you made to remove root certs and MRT domenico's common module takes care of them.
_def_x_
20 Oct 2011
Mazabuka said:
In addition to adding the patches that ware missing from the last official version of the download script, I've also fixed all the APM files that did not function correctly on my machine.
WRONG
[DetectionRegistry] RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB973346\Filelist KeyName=Type KeyValue=Update
RIGHT
[DetectionRegistry] RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB973346 KeyName=Type KeyValue=Update
Removing \Filelist will allow both detections (reg or file) to function if needed.
Also, if anyone talks with Frank they should encourage him to update IPB to the latest, there have been 2 (I believe) updates, it's now v3.2.3. Major issues were addressed.
ViroMan
20 Oct 2011
I see him online everyday all day. I think he just leaves that computer on. No telling when he will get messages if you send him one.
_def_x_
20 Oct 2011
ViroMan said:
No telling when he will get messages if you send him one.
