RyanVM

Don't remove CAT files. And try searching the forums instead of bumping nearly 5 month old threads

That's the idea...

Even a cursory look through that list shows a bunch of redundant hotfixes. You might want to consult with Hulk's sticky at the top of this forum for a list of current hotfixes needed for your install. Or just use my Update Pack

Care to elaborate on what kind of network problems you're having...?

I think what he's trying to say (and I'll be the first to admit that I'm kind of inexperienced in exactly how nLite does things) is that my pack adds a few new languages via an updated intl.inf. Since Update Pack integration and component removal are done at the same time, nLite isn't able to detect those new languages when you run it the first time through since it's working with the original intl.inf on the CD when it's seeing what languages are there. That's why he's saying to integrate Update Packs first and then do component removals. That being said, I'm not completely certain if that's what nLite does. I think nuhi may actually scan the update packs for a newer intl.inf prior to determining which languages exist so it can all be done in one pass. nuhi, care to confirm or deny that?

Well, they're both smaller than 160MB

The only reason I'm interested in Vista is DX10

Correct

If you're looking for a quick and dirty solution, you can always just edit boot.ini and remove the non-working entry from the list.

I'm going to strongly recommend starting with a fresh CD. Nothing changed with respect to those specific files between 2.1.0 and 2.1.1, so if it worked before it should work now. I'm guessing that some other change was made that you haven't told us about (wouldn't be the first time that's happened) or that you're unaware of.

Like T D said, the XP Pro upgrade CD will work like a regular XP install CD, but you'll need your XP Home CD at a point during the install to verify that you're upgrading legitimately.

When you go to burn the image in Nero, make sure the dropdown in the upper left corner of the Burn Compilation window is set to DVD and not CD.BTW, you might be able to get away with overburning if you're only adding an extra 12MB.

Out of curiosity, how many threads does lennierv really need on this topic? I'm counting 4 thus far...

uh, WFM And surely you followed the directions here before assuming it was my pack's fault, right?

That explains it perfectly. In other words, it's got nothing to do with my pack and everything to do with what the OP removed from his source.

1.) Use a newer update pack 2.) Don't remove CAT files when integrating it

MBSA comes up clean for me on a test install with Update Pack 2.1.1 integrated into it.

MBSA checks file versions last time I checked, so it should be coming up clean.

BTW, being punctual means you show up to things on time (Please read my sig before killing me)

http://unattended.msfn.org/unattended.xp/view/web/13/

You should note that removing the EXEs will cause registry entries for the hotfixes to not be written. Normally that's not a huge deal, but IE Cumulative Updates do require certain registry entries for them the show as installed on Windows Update. Therefore, running the INF for 918899 should be considered mandatory.

Actually, there was a decent gap of time between when SP2 was released and the first hotfixes for it started showing up. Also, don't forget that many fixes are being coded and tested many months prior to release. It's not much of a stretch to assume that updates being tested for future release are being included in betas of the SP as well.

Has BtS successfully added this driver to his DP Mass Storage?

See this? [SCSI.Load] percsas = percsas.sys,4Here you're assigning a name to the driver file you're loading (precsas assigned to percsas.sys). Later you assign three descriptions to that same name (percsas). Look at the sections you're modifying way more closely than you apparently have at this point. You'll see that each controller listed in [sCSI.Load] has exactly one description for it in [sCSI]. The only place multiple items can be associated with one name is the device IDs. Get it?