glentium

@pawan: did you also slipstream IE7 and all IE7 hotfixes in one go? That is exactly what is happening on my end.. I'll try just_laze method of slipstreaming IE7 and the hotfixes on 2 separated steps with nLite..

I use HFSLIP to slipstream updates. then, using nLite, I managed to slipstream IE7 and the 3 hotfixes (928089, 928090, 929969) all in one go. Everything seems to be okay and all IE7 updates are in. The only problem I encountered is after install, I occasionally received "Windows File Protection" dialog boxes...

Tomcat and tommyp will sure take care of that..

thanks booogy, will try that asap...

Tomcat and Super-Magician, from the other thread about this WMP11 problem, it seems you don't have this problem. You don't use OEM versions, do you? Sgt_Strider and XibaD, do you use OEM versions of WindowsXP? The reason I'm asking is because mine is also OEM version and I do have this problem of not having the WMP toolbar for the taskbar, when I slipstream WMP11, but not if I install it via svpack.

Sgt_Strider: If I install just 3.0, then I should be fine for most applications; at least the latest ones right? In principle, yes. But like I said, I only have 1.1 and 2.0, both installed at T-13, but I haven't installed 3.0 cause I don't need it at the moment so I can't say exactly if you won't get into problems... you can always try, my friend.

it depends. they are frameworks that certain applications depend upon. if you use Visual Studio .NET 2003, you need 1.1. Visual Studio Express Editions and Paint.NET requires 2.0. but since 3.0 actually contains 2.0, it's up to you. apps that depend on 2.0 should work with 3.0. personally, i haven't installed 3.0 since it's just 2.0 plus plus and i don't need the plus plus for now.

@Kiki, you posted a link to the same topic Tomcat posted...

bump!

BIG THANKS for the updates! however, I've just downloaded WindowsUpdateAgent to double-check but our MD5 still didn't match... WindowsUpdateAgent20_x86.zip

thanks for the new version, tomcat! btw, in HFSLIP, does including your dotnet30 silent installer product of SNM at SVCPACK makes including KB927977 (msxml6) at HF unnecessary?

S-M, my friend, you might have mixed up this topic, which is entitled "Windows Update Agent not slipstreaming on 2003 server" with the one about "Microsoft Update" here: HFSLIP - Test releases btw, I can both go in without hassle to Windows Update and Microsoft Update in XP and 2003 by just putting in the necessary files listed in the dynamic lists by tomcat, which is why I said in my other post: 'don't fix something that is working'...

I don't think anyone would want to recreate dotnet installers everytime HFSLIP is run! just use this tool once (or when another patch for dotnet is available and support for it is added to SNM) to create the installers and add them to HFSVCPACK folder. although the idea is possible, why add bloat to HFSLIP with this one? I believe creating silent installers is beyond HFSLIP principle. HFSLIP is geared toward (and EXCELLENT for) slipstreaming/integrating/(now 'guirunonceing') hotfixes, updates and much, much, much more, and not for creating silent installers...

using an old but clean CD and the product key from the unattend.txt might work, but I believe the I386 provided is optimize for thinkpads as to drivers (and perhaps, other things as well) are concerned. I tried using it on a hp Desktop and I got some errors as to missing drivers. the recovery discs would be of no value to you as to using HFSLIP is concerned because it only contains compressed recovery image to be restored, as plain Windows XP SP2. All thinkpad customizations and patch/hotfix installations are done during the rest of the recovery process. so, I'm 100% sure the I386 directory on my thinkpad (T60) is clean SP2-slipstreamed source. That is what I used for HFSLIP. It didn't even have a SVCPACK folder. All files in I386 are dated 8/4/2004 except for OEMBIOS.*, unattend.txt and winbios.txt. Is it brand new notebook? Maybe somebody already messed up with your source. To be sure, you might want to print the directory structure of your I386 folder from the command-prompt: type "DIR C:\I386 /S > i386.txt" and post your i386.txt. I will compare it to mine. Now, to be really, really sure, run the Product Recovery from the Recovery Partition to restore it to factory settings. You should then have a clean I386 folder. after that, I suggest making a set of product recovery discs as a precaution (but always use the Recovery Partion not the discs to restore). also a simple folder backup of a freshly restored C: drive.

hmmm.... well then, I guess the only thing that was change in WMP11 is the download page...

@Kiki pardon me for gatecrashing here, but if you have no problem with WU and HFSLIP, I suggest you just leave your current HFSLIP setup as is... i do have a W2K3SP1 HFSLIPed DVD and I have no problem with WU..

may i ask what is your notebook brand? if it's a thinkpad, i might be able to assist you. most notebooks that do not provide recovery discs does have a recovery partition which is accessible by their own software. from that software, you should find it in All Programs, you can create recovery discs yourself...

but then, it wouldn't hurt to download and use the 'latest' release in our install source, i guess..

this is great, thanks Tomcat! btw, I know that dotnet30 is actually dotnet20 plus extras, but for people who want those extras, would you please add support for using the dotnet30 installer instead?

I don't think wpa.dbl matters, activated or not, in a corporate product key because it doesn't require activation... but I'm pretty sure it wouldn't be long before HFSLIP can actually slipstream IE7, and not just integrate it or install it at RunOnce...

IE7 integration is really quite problematic, maybe because of us, HFSLIP users, having different types if Windows XP (Corporate, OEM, Retail, etc, etc, etc... ) and this activation thing. anyways, personally, i have always prefer to install IE7 as the last application in my unattended install (RunOnceEx) then run the updates for IE7 on the next reboot. works flawlessly, so far...

I can't remember having makecab in HFTOOLS ever since, because it is part of Windows (or I could have removed it a long time ago)... for Windows 2000, make sure it is in WINNT\SYSTEM32 folder and copy it over in it if not, as mentioned by this HFSLIP Guide for Windows 2000 under PREREQUISITES section... or you can check out the CMD file itself and you can see that HFSLIP checks for the existence of MAKECAB in the SYSTEM32 folder and not in HFTOOLS...

Sorry for not being able to respond to this sooner. I was kind of busy and also went on vacation. Tried it with both CDBURN.EXE and DVDBURN.EXE in HFTOOLS. As expected, it defaulted to DVDBURN, but learned I don't have to use /Erase switch for DVD+RW media. Anyway, it worked. I didn't test CDBURN.EXE because of not having a chance to slim down my source but I guess, in principle, it should also work. For it's lack of features, like verifying sectors and waiting for media to be inserted on the drive, I prefer not to use DVDBURN, though. So, I tried it with IMGBURN, and, of course, worked... Also, even though, I sometimes fiddle with SOURCESS before making ISO and burning, I personally feel that this feature is necessary because one could always use MAKENOISO in HFANSWER.INI so that SOURCESS could be tweaked a bit, then, in one step, run HFSLIP again using MAKEISO, then BURN, BABY, BURN!

well, i wish the installer window deviates more from the 'RunOnceEx" look. I mean, even though the current version's installer windows is a little different from the "RunOnceEx" one, i just wish it would be more "WPI" look..

hmm, interesting..