A couple others have done these update lists in the past, and they start out great. Then their interest wanes and they'll just up and disappear with no notice whatsoever.
Basically, what I've been doing is have a Win2K VM that is patched w/ SP4 + UpdateRollup, then run hfnetcheck with the MSSecure.xml file within the VM:
Quote
hfnetchk -o xml2 -x mssecure.xml -vv -f hf.xml
Grep the file for "\<Download URL\>", ie
Quote
<DownloadURL>http://download.microsoft.com/download/5/2/3/5231e3ef-ae49-4ee6-
aa06-f9f226bc9cfb/windows2000-kb828035-x86-enu.exe</DownloadURL>
Of which I can output the last forward-slash piece to a text file, (generally process the text with with gawk in a .cmd batch script) compare vs my HF folder, and have the download links even to fetch the files in question. I may see how an AHK script handles the whole shebang, instead of UnxUtils and .cmd batch.
YMMV, and you need an actual working copy of HFNETCHK which is pretty hard to find these days, I dunno if were even allowed to link to where a copy can be found.
I had given autopatcher a try a few times, to see how it handled just fetching the patches (as it downloads them from MS servers now). While it does a half-decent job with XP, it's a complete fail IRT Win2K. I was looking for a less time intensive way of building an updated central XP location for when I do the odd XP reinstall for family and friends. Since I don't keep up with XP in general. Even with AutoPatcher and a few other methods, every single time I need to build a current XP disk it winds up taking literally days of troubleshooting obscure issues. Especially OEM boxes which don't legally allow you to install a "real version of XP". After the most recent incident, I've pretty much stopped offering my help/time.
This post has been edited by Crash&Burn: 18 August 2009 - 12:00 AM