tzeentch

Haha, true, don't try this at home Hmm, I was sure I added a msg like "Finished. Cleaning up" or sth. I'll check that. Regarding how many updates downloaded, do you mean the ones that were actually downloaded? eg. apart from the ones that were already there? Yes, I know, Bilou mentioned sth about this as well. I've just ran a test with a VM, I downloaded the hotfixes, integrated them on to the iso, installed, and after installation windows update still had few updates to download. I'll have to check that but after a brief look I think the ones that it offered were the non-critical ones, or whatever you call them. On many lists they are considered 'additional'. It just seems they are not included in mssecure. I'm not sure though why Windows Installer is one of them. To be honest when I started this project I thought MS puts ALL their updates in the mssecure file. It seems it's not entirely the case. I'll definitely see what I can find out about it.

New release is available now!! Thanks to TAiN for the hosting again. The link is still the same - GET IT HERE Briefly, changes in the current version (0.5b1) are: Changes: * moved configuration to a separate file * implemented the command line switches * cleaned up and rearranged the config files * implemented the message printing and logging functions * cleaned up and added messages generated by the program * added a bit more checks to prevent the program from going further if something went wrong * introduced a new bug :O * fixed the above bug :D * implemented the dry run switch * implemented a function counting number of hotfixes to be downloaded * added information about localized updates * updated the README * added -s or --save-list file to save the hotfix list * fixed the query execution * did some tests with Windows 2000 SP4, Windows Server 2003 Gold and with French version of mssecure and everything seems to be all right This is just a brief, see the full ChangeLog in docs/ dir to see the full list of changes. Now be sure to look through the README as lots of things have changed (mainly due to switching to config files). There is an explanation in the README regarding the localized updates. It seems MS only supports few languages if it comes to mssecure. Instructions for those languages are there so if you're interested you can use it. Checked with french version and worked fine. For those who MS doesn't like I may come up with an alternative way to download those hotfixes but it can be less robust. I may have an idea how to do it, just don't know when will I find the time. In the meantime, try it and let me know, I'll try to shoot the bugs first (if any of course).

Have you actually unpacked DEFLTWK.IN_ ? You should copy it to some other location then open command prompt and type: expand DEFLTWK.IN_ DEFLTWK.INF Then look in the DEFLTWK.INF for [system Access] section and the NewAdministratorName entry should be there. If it's not you can add it as: NewAdministratorName = "guru" Obviously change 'guru' to whatever you want admin account to be called. After that you need to pack the DEFLTWK.INF. You'll need makecab for that. Open your cmd prompt again and type: makecab DEFLTWK.INF Now you can copy the newly created DEFLTWK.IN_ to your windows source. The question is: why not simply use nLite for that?

Well, I'm back. I've been working on the script this week and implemented some rather nice changes. I'm still doing some tests because I encountered some rather nasty bugs there but I have totell you that things look pretty good now. I'm running tests with Win 2000 as well as XP and 2003 Server and things seem to go all right. Also I've noticed MS updated their MSSecure yesterday and there seem to be more updates on the list. I'm not sure what way do they work with updating this file Later on I'm gonna have a look at what Bilou mentioned about the number of updates downloaded. Although with the new MSSecure I was getting around 50 updates for XP SP2 but I'll try to compare with some of the lists published on the internet. Anyway, I plan to finish the tests today, pack it all together and hopefully release it today.

Hey, great stuff ricktendo64 !! Well, it seems he's left many people disappointed by disappearing without a word. I must admit I am one of them

Hmm, I admit I haven't checked SP1 throughly. I'll have a look into that. See, I still don't understand what MS means by 'severity' or 'importance'. Last time I checked windows update everything there was 'Critical'. The MSSecure file seems to have a bit more options It's a good idea to add some counters. That migh give some comparison. I'll also add a soft-run option - to show what would be done without actually downloading anything.

Glad to hear that it works!! I've uploaded the bugfix release to TAiN's website. The link is still the same. This one just fixes few of the encountered problems. I hope to release the new version soon as well.

Hehe, glad to here that. Hopefully I'll have some time this week to implement the config files and make the script more robust. The next thing I'll be looking at is simultaneous downloads I'll post a fix for that there 2mrw B)

dshadow1, THANKS !!! I don't know if you know how much you've just helped me to find this pesky little bug !!! Haha, so simple! You see, I have some things tweaked in cmd interpreter settings so I just take them for granted See the line of output you quoted with the sggrep command from step 4? I take it it's the output when you turn the echo on. See the part where it says !WINUPDL_ProductIDs! ? Well, that should actually be expanded to the numbers separated with '|'. What that means is that the delayed expansion is not on. I have it on all the time via registry that's why I couldn't reproduce that. I'm working on a bigger update at the minute, to include the separate config files, etc, but I'll patch that tomorrow and release it. If you want to check in the meantime there's a super quick fix: instead of starting the prog by dbl clicking or typing winupdl, type: cmd /v:on /c winupdl.cmd Anyway, next release will contain some more error checking to avoid things like that

That is very weird I can't reproduce this bug. I've tried few times but I only get updates for XP (and one for WindowsMedia but it must be marked for XP in mssecure). I'm attaching a script here: winupdl_prep_debug.zip which will save some information that could help me debug that. If you want to try it download it, then unzip to the directory where you have winupdl in. Now you'll have to run it, then run the debug version of script it generates (winupdl-debug.cmd) and after that's finished you have to run it the second time. After that's done you'd have to pack the log and tmp dirs from winupdl directory and send it over so I can have a look. My email is: tzeentch dot gm at googlemail dot com Eh, I don't even want to start about Microsoft and it's practices. I've heard recently that they want to move everything to WSUS (aka Windows Server Update Services) and integrate it with Microsoft Update which means the xml file will become obsolete. I think they already stopped supporting it but they update it because the SMS 2.0 still uses that for updates. Well, we shall see.

Do you mean you run this without any modifications and you end up getting updates for a different product? I'll have to investigate this. On the day that I've released it M$ updated the mssecure file. I don't think it could break something but I'll have a closer look at what have they changed. @Camarade_Tux: That seems a good thing indeed. I'll have a look how it can be done.As for running this to download things for different versions of windows, I thought about doing it this way: separate configuration to a config file add a cmdline switch to select a different config file than the default one you can then have two separate config files say one for XP, one for 2K and run it as: winupdl.cmd --profile 2k.conf and it would dl things according to 2k.conf which could contain a separate download paths, etc. What do you think about that? Also, @sTe: Yes it checks the timestamp of the files and will download only if they changed on the server.

Hello!! Yes that's my mistake, sorry about that. I've tested it on my laptop at home today and got the same result It was actually wget returning status 1 because it couldn't find the wgetrc file You see in the environment it was build I use proxy to connect to the outside world so I have to use wgetrc Anyway, I've identified two more bugs which somehow escaped my attention, and they are gone now as well TAiN, can I email you the fixed version again? I'll have a look around to organize some hosting maybe in the near future Thanks

TAiN, I've emailed the file to you. Let me know if you got it. If not it was probably blocked by some paranoid email server

Hmm, ok, I wanted to attach it here for starters but it seems I can't. I get a msg "... total filespace ... greater than your per post or global limit ...". Weird the file is just 1mb Right ok, I'll just email it to you then, TAiN.

To everyone interested: The program/script is finished. Wow it took some time but considering my recent schedule I'm happy that I could find time to finish it. The package is self contained and you can just unzip it anywhere you want. Now. Most probably you will want to configure some of it's behaviour. Depending on factors like: which version of windows do you want updates for, do you use a proxy to connect to internet, etc. I've included a short readme file so be sure to read it. As for now configuring the script means opening it and changing some variables in the beginning. It is well commented and everything should be easy enough. If you'll think it'll be better, I can modify it to use an external config file. Anyway, grab it, try it, tell me what you think Uh, just one question though. How do I upload the file to MSFN? I can see some storage folders in my control panel but can't seem to find a control to upload it. Or will I just attach it to the post here?