RyanVM

Where could one get more info on that? Do you use them at the T13 mark or just the GuiUnattended part?

I replaced two files.

As far as I know, nLite is still having problems with other languages. I'd say it's best to just wait for awhile until nuhi has a chance to sort it all out.

If the hotfixes are in the correct directories, just run the batch file and it will do the rest.

MSXML went from 5.04MB to 1.79MB EDIT: Uh oh. I'm getting an error 2902 when trying to install. I think it's because the digital signature on the MSI is bad. Any idea how to correct it?

I'd say that unless you start getting complaints from MS (and they have at least one representative who posts on this board), don't worry about it

Exactly my thought

Really? I was considering starting a Monitor DriverPack... :s How come monitor drivers won't be installed? Is there any way to do this? Dunno. They compress nicely, though. Went from 25MB to 1.89 as a solid RAR archive. Also, let me tell you that they are a royal b***h to collect.

How do I extract the files from the MSI file so I can change/delete them? Basically, I want to delete the unneeded SDK files and add an updated msxml4.dll from a hotfix. Is there a way I can get access to the CAB contained within the MSI file?

I put together monitor INFs for about 10 manufacturers (over 2000 files), but I hear that monitor drivers won't install during the driver installation stage, so it's moot.

Only problem with that (moreso with sound drivers than mass storage controllers) is that there's a large variety of sound cards out there which get used in home systems.

2126 was a leaked beta build

It's generally recommended you follow a numbering pattern similar to that outlined on the page you linked to in your post. I personally go by the following convention for my personal CD: 000_chipset 001_lan 002_graphics 003_sound 004_tvtuner 005_usb 006_storage 007_monitor etc... This method is recommended (though not necessarily necessary). It's what MS does when they do their testing and supposedly the numerical order eliminates some problems they have had before.

Thanks

I've got space. I know it's possible - the guys over at radeon2.ru have done it in the past.

If you only have one main partition, this is simply a matter of WinXP setup not overwriting the boot sector. In Windows, open boot.ini (it's a hidden file on the c:\ drive) and remove the line referring to Windows 2000. Be aware that boot.ini may be read-only and you might have to change that attribute prior to editing.

If this is true, this would be a better ways, because I know of some companies (and my school) who use PIDs with -640- or something else in the middle and this would be a better way of blocking unlicensed users! lol! Your school is unlicensed? Tut, tut... lol Maybe you could use that to you're advantage.. Chris! No, they're not unlicensed... PIDs aren't only the middle three digits (ie. -640-)... They consist of most numbers, and some of the PIDs with specific numbers including -640- were already blocked in SP1... This doesn't mean that all copies of Windows XP with -640- were blocked... Well.. I think 640's are being blocked in sp2.. Because there pirated. Well thats what i've been told! Chris. Incorrect. You've got the situation reversed.

I think OOBE plays a part in activation which is where the potential legal issues might arise. However, for those of us with Volume License versions, it's irrelevant.

You should do that with the Catalyst drivers next

Where's the registration info for that download? It seems like it's the full version yet it's free?

BAD CRUSHER, BAD! (I'll spare you the shameless self-promo )

OK, I managed to create the admin point and slipstream the update. Now I've got a Win and Program Files folder in that directory. I don't see how I actually install .NET from this admin point at this point. I tried copying those folders with netfx.msi over to a VirtualPC install, but it still want netfx1.cab (which it seems it shouldn't need anymore). I copied that over and it gave another error when installing.

I'm trying to use WinInstall LE to slim down the MSXML 4.0 SP2 install package by removing the SDK portion. However, I've noticed that the MSI's file size doesn't change even after removing the offending sections (the file count in the MSI does decrease like it's supposed to). It's like the references to the file are removed but not the files themselves.

I'm trying to integrate the .NET Framework hotfix (KB824629) into the .NET Framework install. I can extract the MSP from the hotfix download, but I can't get it to update into netfx.msi. Anybody out there tried it? Got it to work? Any ideas/suggestions?

Your path right now is pointing to the original location of the files. When you run Windows setup, that's NOT where those files are copied to. Any files in the $OEM$\$1 directory are copied to C:\ during setup. Therefore, your path should be c:\Install\hotfixes.cmd (or better yet, %systemdrive%\Install\hotfixes.cmd).