RyanVM

enbel, you realize this thread is no longer active, right?

You using my pack?

I find it very hard to believe that anything about the DirectX runtimes are localized outside of the installers. If I'm wrong, feel free to say so, but my bet is the DLLs are the exact same regardless of language.

QFT

Not to mention that MS doesn't always use a standard installation method for their hotfixes. Some use MSIs contained within the normal-looking hotfix installer, for example.

http://www.utorrent.com/

I bought them out. You all have 24 hours.

If you downloaded them from Windows/Microsoft Update, the extracted hotfixes can be found in %systemroot%\SoftwareDistribution\Download and they can be installed by running update.exe in the update sub-dir for each hotfix. NOTE: There are a few useless files that get extracted to each hotfix' directory, but you can just ignore them if you're not sure which ones they are.

WPI can let you do that, though it does so post-install

You've already got a bunch of examples of how to do that in this thread

Good to know

boooggy, does that mean that those using my pack with your wmp11 addons haven't been having problems?

Here's the MS KB article explaining the difference between QFE and GDR. http://support.microsoft.com/default.aspx?...kb;en-us;824994 I'm certainly not opposed to you basically "decompiling" my pack if you're interested. It's pretty straightforward actually. The main things you'd want to look over are RVMUpPck.inf (which contains all of the registry entries and DLL registrations) and entries.ini, which tells the Integrator what to add/modify in txtsetup.sif, dosnet.inf, etc. The stuff in entries.ini can be done by hand, but you might as well make use of the tools available to do the hard work for you .

That was the point I made earlier . It needs to run them from svcpack.inf in order for the registry entries and QFE versions of the files to be installed on the system. And all hotfixes from the last 2-3 years have had so-called qchain functionality built into them. Install order makes no difference whatsoever. But I can't say it any more clearly than this - there is NO officially Microsoft-sanctioned way for directly integrating fixes into the XP install source. Do you think my pack would be so popular if there were?

Those are standard strings...

TRY NOT SHOUTING IN THREAD TITLES more people might read your thread that way

http://gosh.msfn.org/Files/DirIds.txt 0x00000001 is what you want. For example: HKCR,"%MyComputer%\shell\services\command",,1,25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33 ,00,32,0,5c,00,6d,00,6d,00,63,00,2e,00,65,00,78,00,65,00,20,00,2f,00,73,00,20,00,25,00,53,00,79,00,7 3,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00 ,32,00,5c,00,73,00,65,00,72,00,76,00,69,00,63,00,65,00,73,00,2e,00,6d,00,73,00,63,00,20,00,2f,00,73, 00,00,00Notice I used 1 instead of 0x00000001 for shorthand as the above link says you can. EDIT: I don't know why IPB is screwing with the text formatting in the codebox, but you can copy/paste the correct code from the message edit box if you pretend like you're going to quote my post.

You can't use F6 for mass storage drivers if OEMPreinstall is set to Yes in winnt.sif. Either live without that entry or directly integrate your driver into the install CD.

http://msdn.microsoft.com/library/default....b9d8dbb.xml.asp Start reading.

/integrate still requires the hotfixes to be installed from svcpack.inf

...did that guy seriously just copy and paste the entire makecab documentation from the MS CAB SDK and try to pass it off as his own work?

Compare the given file versions. All that info is available in either the KB or Technet article for a given fix.

Look familiar?

I think you're talking to the wrong guy, but you make a good point

I don't know what to tell you. This is what I'm seeing: