RyanVM

Well, I hit a big snag on the MSI version. I think adding that file screwed up some checksums or something because the install fails (error code 2606 IIRC) with the newer DLL added in (of course, I also realized now that there's a manifest file I should be updating as well). All I know for sure is that there appears to be a lot more stuff being added to the registry by the MSI installer (nothing that can't be exported, though ) that the INF file doesn't say anything about. Whether or not they're necessary is an entirely different matter, though.

Just download the latest detonator drivers, open them in WinRAR or Winzip and extract the files to your drivers folder and reference them in winnt.sif.

Go to the link I gave you. You'd be amazed how much info it has

http://unattended.msfn.org/xp/applications/netframework.htm

Actually, it's for the Indeo codec.

Exactly

Remove any references to KB826939 for one thing - it's a patch for SP1 that isn't needed for SP2. Second, am I reading this correctly? Are you simply running SP2 setup during Windows setup, or did you actually slipstream SP2 into the CD?

And the post I quoted said Microsoft had a right to keep people from pirating their software. Nobody's saying they aren't as that's not what this thread is about.

there's no endquote on it

There's a forum right below this one dedicated to unattended switches, try posting there. Also, you might check this site, which has some of the info you want.

I'm playing with WinInstall LE right now hacking the MSI file. I added the new msxml4.dll file to it successfully. I'm trying to remove the SDK from the MSI to save some space, though, and while it shows as removed, the file size of the MSI doesn't change at all. Just for kicks, I tried removing all the files from the MSI file and it still shows the same size after saving (5.04MB). I'm half beginning to think I might as well just create a new MSI from scratch with all the right files. Meh, we'll see

The switches exist to tell a program to run a certain way when they're called. What switches to use and what the switches do varies on a program by program basis. In the example you gave, /s almost certainly tells that program to run silently, meaning it runs with no user interaction at all. Switches don't work by automating keystrokes (hitting the next button), but by telling the program not to ask in the first place! The MSFN unattended site has a list of many commonly-installed programs and the switches required to make them run silently. If a program you want to install isn't there, search this forum to see if someone else has posted it or figured it out already.

, as it stands now this won't be an issue with SP2 since for some reason that file doesn't exist on the slipstreamed CD (even though txtsetup.sif is looking for it)

Wanna have a go at it?

Are you using Joliet or straight up ISO9660 for the file names? Mine show up normally using Joliet.

That's not the matter of discussion in this thread. EDIT: To clarify, this thread is about a BUG that requires activation on Volume License copies of WinXP with legitimate VLKs, not MS blocking people from installing SP2 on pirated copies in the first place.

I'm also going to take a look at msxml4.msi tonight in WinInstall LE and see what other registry entries and such are being made during that installation.

Now that's timing

Also, how does one go about using the CAB redistributable MS lets you download? It's just a CAB file with 3 dll files and an inf in it. EDIT: I extracted the contents of the CAB file, added the updated msxml4.dll (the only updated file in the 832414 hotfix), changed the INF with the newer file version (4.20.9821 instead of 4.20.9818), and repacked the CAB archive. You can download it here: http://msfn.ryanvm.net/msxml4.cab (515KB) Please tell me how to integrate this into the XP install CD if you figure it out. EDIT2: For reference sake, here's the page where you can download the original: http://www.microsoft.com/downloads/details...&DisplayLang=en

Just so you know, SP2 comes with MSXML 3.0 SP5 (but no MSXML 4.0 of any revision as best I can tell). Also, does anyone have a non-MSI MSXML 4.0 SP2 installer that can be run during the cmdlines.txt part of setup?

Does the ISO work correctly in VirtualPC? If so, then you've probably got a bad burn. If not, try re-integrating SP2. And given that NFTS.sys and FAT32.sys are what allow the OS to read the filesystem, I doubt you'll have any luck copying files over later.

Why are you leaving update rollup 1 in there? SP2 postdates all of those files. Delete them all. Yes, DX9b is included with SP2 (and the recently leaked build 2126 appears to have 9.0c integrated into it).

Well, I'm glad I wasted half a day downloading drivers for 10 different manufacturers and extracting them all . On a side note, it really irks me when a bunch of manufacturers make separate zip files for all their monitors rather than one large zip file with all of them included.

I've had no issues integrating SP2 onto the VLK CDs with builds 2055, 2080, and 2096. I've always used the "standard" method of extracting then running update.exe -S:"path". The only issue I've had was with build 2120 with its activation issues that will supposedly be resolved in the next release.

Yes