br14n

I did more work with windows-xp-sp3-x86-enu.ulz. I made a 'wud' script that can be run like 'wud windows-xp-sp3-x86-enu.ulz' to download the files with wget: for f in $(unzip -p $1 | grep url | cut -d'>' -f2 | cut -d'<' -f1); do wget "$f"; done My ~/.wgetrc: timeout=10 tries=inf user-agent= robots=off I think I was short one file because Microsoft names different EXEs the same thing. For example, different versions of .NET are named 'dotnetfx.exe'. wget handles this by appending .1, .2, etc., to the filenames. Maybe WUD is clobbering existing files. The hard part of this thing isn't downloading the files, it's knowing what to download. How are people figuring that out?

WUD 2.40 build 1299 using UL file windows-xp-sp2-x86-enu.ulz 2008-04-08, no proxy. WUD says that the following files are missing: 1 of 131: WindowsXP-KB944338-x86-ENU.exe 25 of 131: IE7-WindowsXP-KB938127-x86-ENU.exe 115 of 131: Windows-KB890830-V1.40.exe Also, WUD reported 3 of 131 files missing, so I would expect to have 128 files in the download directory. Instead, there are 127.