RyanVM

I've been running integrated builds of SP2 since build 2055. The only hotfixes I install are HighMAT support and MSXML 4.0 SP2 (it only comes with 3.0 SP5 as best I can tell), both of which use MSI style installers that have to go during the GUIRunOnce stage. So basically yes, start with a fresh install

Here's more info: http://www.tacktech.com/display.cfm?ttid=312

XIA is the designation for an SP1a-integrated CD.

nuhi, are you on summer vacation by chance? Regardless, I'm happy that you're enjoying making this, because we all win when that's the case! .

Extract them from the zip file and follow the directions here: http://unattended.msfn.org/xp/drivers.htm

OMG I LOVE YOU!

I'm pretty sure they are. Again, most of these security patches are written a month or more before they're actually released so they can go through QA testing, so it's not hard for me to believe that they just go into the SP2 codebase at the same time (since we beta testers are doing their QA for them ).

no

You pretty much hit the nail on the head. What it comes down to is that MS is aware of these issues for quite some time before they release the patch. Patches just have to go through enormous amounts of QA testing before they can be released to the public, even if they've been in the codebase for awhile.

Checkboxes and an install button would be cool. This would be a godsend for those drivers that don't integrate correctly but you don't necessarily want to install on all systems (like Detonator or Catalyst drivers depending on the system).

Not true. RC1 has MS04-011, MS04-012, MS04-013, and MS04-014 integrated into it. No, I can't quote the source as this comes directly from an MS rep in the beta newsgroups and I'd get in trouble for doing so

You need a hacked SFC_OS.dll and then you need to kill windows file protection.

The only way I know of is to delete the partition and recreate it.

My favorite part is how it installs both Windows Messenger and MSN Messenger. And how it installs all the updates to the MS JVM only to remove the JVM later on. Seriously, it seems like the creators put zilch for thought into this.

I think you need to register the control panel as well to get it to appear.

I've had similar problems to this (trying to launch a standard GUI Win32 app from a command prompt) with not very good results. One thing you might try (though start /wait wouldn't quite work correctly with it) is to pack it in a self-extracting RAR archive and call that. You can configure the SFX module to automatically launch the program upon extraction.

I can imagine it would be! But like I was saying, it could be a very simple conditional to only have it do it if those other cabs exist. If not, I can always just use jdeboeck's batch files . Regardless, your work is to be commended! You're providing a HUGE service to everybody on this forum, so many well-deserved kudos to you . And you should be fine with the assumption of everyone using 800x600. At least I hope nobody's installing XP on a system that can't do better than 640x480 .

You can see in the INF files if the CPs are getting installed or not. I'll be testing with the Audigy2 ZS at some point (probably this weekend). I've heard that in the past, people haven't had luck with Creative drivers, though, so we'll see. And the CTComp file was in one of the cab files, so you won't see it unless you extract it with the right tools.

I use the default SFX module and the settings I put in my post to be copied/pasted allow it to work WITHOUT switches.EDIT: And that's not even the right thread. Look at the last post on this page. http://www.msfn.org/board/index.php?showtopic=12566&st=20

LOL, the fun is when you've got like 80 different controllers . I can only imagine how big your winnt.sif OEMPnPDrivers line is EDIT: But yeah, I've actually been thinking about dividing them up similarly to that lately for my own organization sake as well. Back to the thread title, so if you copy all the files (including the OEM file) into that directory and point winnt.sif at it, it works in textmode setup with no extra files added to i386 or changes made to txtsetup.sif?

That's normal. It's because there's some file system overhead when a drive is formatted. Also, remember that most manufacturers use a base 10 (1GB = 1000MB) system while Windows uses a base 2 (1GB = 1024MB) system, so there will be differences as a result of that.

Also, will there be any negative effects from using a different version of SFC_OS.dll than the rest of the files (say I integrate a newer SP2 build than what's currently available to the general public)? It seems to me that there's a potential liability there. Of course, when SP2 goes final, you could simply have RTM, SP1, and SP2 versions of the file and which one gets copied depends on which version of XP is detected.

Nah, what I'm saying could be done through a simple IF statement. The program checks for sp1.cab and sp2.cab and if it finds them, it does expanding/combining/recompressing into driver.cab. If it doesn't see them, it doesn't bother.