RyanVM

Yeah, I'll be repackaging it. The fun part about the 6.0.3 update is that the MSI contains only one actual updated file. Then it updates the plugins through a secondary program called by the installer which unpacks some other files which are in some proprietary format (at least, I can't figure out a way to open them and get the files out of it). That's OK, I have ways of working around that

Well, it was no big loss for you guys anyway. And I think I'll join you. Can I get a Pina Colada with one of those cool curvy straws? B)

French version of that same article. http://support.microsoft.com/kb/824994/fr

Man, I really have to integrate this into my CD sometime to see what all the fuss is about

...so I'm guessing that's a no then... Rats

, you guys crack me up. Yes, I'll be releasing 1.0.4 hopefully tonight with about 8 new hotfixes integrated into it. I pretty much had it ready to go last night, but then 873339 showed up As for my reasons for not liking the /integrate command, it's not the idea in and of itself I don't like. It's the way in which the hotfixes are "integrated" into the CD. It's stupid that the updated files sit in i386 uncompressed (especially because some of the bigger ones get better than 4:1 compression ratios). It's stupid that the hotfix installers must still be run from svcpack.inf even with the files integrated, since that means longer install times and lots of wasted space on the CD. Of course, that's what motivated me to do what I did. My pack requires only 1-2MB of extra space on the XP CD to get the same effect. Needless to say, that's a huge savings when you've got 15 (my current count) hotfixes integrated in. Those installers/uncompressed files add up quick. Not to mention how much time is saved by not running 15 installers during setup! EDIT: And for the record, those who dare me I shall SMITE!

Yes I did. There's a lag in that sometimes.

ooo, an MVP B). I see a lot of them in the MS Beta newsgroups. Welcome aboard

I'm not really sure what's going on. There's two different download pages that say the update is for XP SP2. There's this one and there's this one. Both list XP SP2 as a supported operating system. Now, things would make sense if #2 were larger than #1 (as it contains updates for 4 different operating systems instead of just one), but NOOOOO. #1 (the XP SP2 only one) is LARGER. EDIT: I get it now. I just downloaded #2 and tried running it, only to get this message: --------------------------- KB887797 Setup Error --------------------------- The version of Outlook Express you have installed does not match the update you are trying to install. --------------------------- OK ---------------------------I think #2 saying it supports XP SP2 is a typo.

I still can't get over just how stupid Microsoft's /integrate command is.

http://www.microsoft.com/downloads/ Search for (you ready?) "KB887797" and choose the one whose description says it's for XP SP2. (It should be the first result in the list)

The MSI file can be found in your temp folder when you run the EXE.

I'm not sure I understand exactly what you're asking.

OK, I'm getting really frustrated by this. On all my fresh installs now, Windows Update is prompting me to run the Doomjuice, Mydoom, Zindos removal tool (KB836528). So far, my quest to find a registry key which makes Windows think it was run (similar to the GDI+ Detection Tool) has turned up nothing. The best lead I've had is that the tool makes a RemovalTools registry key and adds an entry for that tool with a value of OK when it's run. However, I've tried manually adding that entry on a fresh install and Windows Update still thinks the tool must be run. Has anybody figured out a way to trick WindowsUpdate???

You can always run the exe with a /? switch to see the available switches... EDIT: At least, I find that's a faster way of finding out rather than waiting for people to reply to you on a forum.

Good find.http://www.microsoft.com/downloads/details...&DisplayLang=en , the fixes keep rolling in Of course, you HAD to post that right as I was testing the other 4 updates integrated into my update pack

wow, I didn't think people were still getting those worms... (must resist urge to make Canadian joke....)

correct (at least for XP SP2)

You generally get that error when there's a mistake in txtsetup.sif. If I were you, I'd start with a fresh CD and re-add Bashrat's pack.

Yeah, it's on their download page but there's no KB article for it yet. Thanks for the headsup. http://www.microsoft.com/downloads/details...&DisplayLang=en

New security updates are out: http://www.microsoft.com/technet/security/...n/MS04-041.mspx http://www.microsoft.com/technet/security/...n/MS04-043.mspx http://www.microsoft.com/technet/security/...n/MS04-044.mspx http://www.microsoft.com/technet/security/...n/MS04-045.mspx The first three affect XP SP2, the 4th doesn't. MS04-42 is for NT4 only.

I'm assuming you've already got an administrative installation point at this point in time. Download StartX and put it in the same folder as the SAV9 AIP (you'll have to do a search to find it - it's finals week for me and I'm not looking for it). (The rest of this is for the most part in the 7zip help file, for future reference...) Create a 7zip archive of the whole thing. You can delete the other files in the directory so you only have a .7z file remaining. In notepad, create a text file with the following information in it and save it as config.txt in UTF-8 (critical!) format.;!@Install@!UTF-8! RunProgram="StartX.exe /WAIT \"msiexec /i sav9.msi /qb-! RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS\"" ;!@InstallEnd@!You can change the MSI parameters however you see fit (say for example you want to use the /qn switch instead or your MSI has a different filename), just maintain the rest of the structure. From the 7zip directory, copy 7zS.sfx to the folder with the .7z file and config.txt in it. Open a command prompt at that location and enter the following command: COPY /B 7zS.sfx + config.txt + sav9.7z sav9.exe(I'm assuming that the archive name is sav9.7z for this example - you'd obviously change that to whatever it really is. Same goes for the final EXE name) You should now have an EXE in the directory ready to go. P.S. - We'll save custom icons and UPX compression of the SFX module for a later date (unless somebody else wants to do it) EDIT: Heck, I'm feeling like such a nice guy tonight (and don't feel like studying anymore) that I'll even include my UPX compressed SFX file with a custom SAV icon for the installer. Just extract the SFX file from the archive and modify the procedure accordingly to take the new filename into account (if you can't figure that part out, I will officially lose all hope for mankind). sav.zip

....I'd imagine you'd customize the exe for a given unattended CD, so it still wouldn't be a problem. Seriously, you're way overanalyzing here.

Then you'd use %systemroot% instead of %systemdrive%\Windows

I just extract to %systemdrive% and use a full directory structure within.