RyanVM

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.

Then why is it possible to download 2 'different' versions? Why do they warn you not to install one driver instead of the other? God only knows. They've been unified since like driver revision 281 (the infamous Compaq drivers). Check out the forums over at driverheaven.net for more on the matter. You can hack one file (ctcomp.dat) to to allow setup to install on all cards (it's artificially limited to certain cards).

Interesting. I guess that's an idea for future improvements then .

Creative uses a unified driver architecture. They're the same.

Then why is sp1.cab still there afterwards? EDIT: Also, are you using makecab to recompress the cab files? If so, you can increase the compression ratio by using LZX compress. Just put /D CompressionType=LZX into the command line to enable it. It tends to take 15-20% off standard LZ compression and it decompresses faster according to MS.

I don't think SP2 integration works properly. I selected the EXE and it extracted the files, but the directory still shows only the SP1 files. There's no .SP2 in the root or anything. Also, it would be a really cool feature if you did the integrating of SP1.cab and SP2.cab into drivers.cab. That'll shave off a good 20+MB as well.

You need to have the downloaded SP2 exe file.

weird, I was getting that same error message with some beta builds of SP2. I don't know, a clean format/install has made it go away (build 2120's working fine with it)

And it didn't occur to you that we're busy people too and don't have the time to walk you through step by step? Seriously, there's a ton of good info out there, and the MSFN Unattended site has loads of info and code you can copy/paste right on it.

http://unattended.msfn.org/xp/office2003_advanced.htm You're supposed to specify the CD key when creating the MST file.

Just raise the DPI in the display control panel if it really bothers you that much. I personally use a Dell 2001FP (20.1" LCD) which runs at a native resolution of 1600x1200 and wouldn't dream of giving it up. Of course, I had a Hitachi CM772 19" CRT prior to that that I was running at 16x12.

WOW! This looks incredible!

start /wait "%programfiles%\winrar\hotfix.exe"

So that worked in IDE mode? Very curious. Though if that works, you could expand that by using subdirectories for all the different controllers.

Seems logical.

While I can't say if it does or not, it would make logical sense that it automatically compare file versions to be sure that the newest remains.

Definitely a step in the right direction. It would be a nice timesaver if we didn't have to install all the hotfixes one by one during setup (especially as they begin to pile up a year or more after a service pack). Out of curiosity, has anyone tried using the newer update.exe with older service packs? In other words, extract the files from the installer, replace update.exe with the newer one then attempt to integrate. Might be a fun experiment

Last post on page 3. You're making it too complicated.

All the info you need is in the sticky at the top.

There's absolutely no reason to have two identical folders, that's for sure. EDIT: Most importantly, the INF files are identical. Those are what actually allow for a driver to install for a certain piece of hardware.

To further prove the point that the Live/Audigy cards use the same drivers, note that your AU1 and AU2 directories are 100% identical. Look at the inf files to see the supported controllers. Interestingly enough, it appears that all Live cards use the same PnPID and all Audigy cards (including the 2 and 2ZS series) share an ID.

Put quotes around the path to avoid issues with spaces

For what it's worth, DetachedProgram works like charm. The RAR archive self-extracts as soon as GUI setup loads and Windows setup waits to continue until after it's done.

Could you just tell me what the names of those controllers are? At www.tweakers.net there's an overview of the newest drivers. Over there they say 1.84.40 :s ----------------------------------------------------------------------- err... perhaps ".html"???? it's a website with only a javascript in it... EDIT: I've tested it too with FireFox. Seems it opens it _only_ correctly if I open it from HDD... What can I do to fix this? I think you need to declare the MIME type in your server software. Also, run it through the W3C HTML validator to make sure it's up to spec. Also, look at the INF file for the Live/Audigy drivers. That's the relevant file version. Here's what I've got (theoretically anyway ) supported in my collection that I can send you: Creative Soundblaster Live/Audigy Series - 5.12.01.0443 (yay unified drivers) Creative Audigy2 LS - 1.02.027 nVidia nForce APU - 6.14.0431.1 Realtek AC97 Audio - 5.10.00.5530 (there's like eleventy billion different PnPIDs for this) ALi Audio Accelerator - 5.12.01.5260 ALi M5455 Audio Controller - 5.12.01.7005 AMD 8111 Audio Controller - 1.8.6.0 VIA Envy24HF Controller - 5.12.01.3630 Sigmatel Audio Controller - 6.14.01.3901 VIA Vinyl Audio Codec - 6.14.01.4020