RyanVM

I think the top of my site sums up pretty efficiently why integrating the fixes (specifically by my method) is superior to other hotfix installation methods. While some of these points are specific advantages over the /integrate method, some are generic to just integrating hotfixes into the CD in general.

I have a good rule of thumb for situations like these (which is generally valid) - if you have to ask, you already know the answer to the question.

So, uh, scroll down the forum list a bit further before posting next time. http://www.msfn.org/board/index.php?showforum=111

My .NET installer has nothing to do with my Update Pack. They're two seperate things. But like I said before, you can always just manually integrate KB886903 into your .NET installer (not your XP install CD) if you're so worried about it.

100 is used by any files which are replaced by SP2, not just files in sp2.cab. http://gosh.msfnhosting.com/txtsetup.htm

Unless it's serepack.inf, of course

Wow, much easier than sysoc.inf. Why exactly were you opposed to it again?

I think it's pretty well established that nobody will be fixing the download link since this is an obsolete integration method. There are superior ways to do this already.

You can use a program such as Advanced Registry Tracer to take a snapshot of the registry before and after such a change, you know. It's probably a lot faster than waiting for someone to post the answer on the off chance anybody knows.

What are you trying to change in txtsetup.sif? Do yourself a favor and look at an XP Gold txtsetup.sif and an XP SP2 txtsetup.sif. Wanna know what you'll see? The entries for the files found in driver.cab (and sp2.cab) are the same in both versions. The only way Windows setup knows which cab the latest versions are in is with drvindex.inf. So, please explain to me what isn't "clean" about my methodology? I'm really curious to know since it's the same one I use with the RyanVM Integrator which has worked fine for everybody who's used it.

, I can tell you're new here Suit yourself, there's plenty of information out there for how to integrate it yourself if you feel so inclined. Otherwise, 20,000+ downloads can't be wrong . Plus you could always try it in a VM if you think my work is shoddy.

You know, I make a nice switchless installer for .NET 1.1 which includes the KB886903 update http://www.ryanvm.net/msfn/

It's been done before. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=350675

He said publicly that he was leaving once upon a time

OK, that had to be an act. I refuse to believe people are out there which are actually that bats*** insane.

You, sir, are an id***.

You don't need to remove the HP software http://support.microsoft.com/kb/918165

Care to share the solution for the rest of us?

LMAO..... Ryan's humour is so dry it would have to rain for a week to make it damp....

wow, two posts in a row saying exactly what I said in the first reply to this thread. Good work gentlemen

No, they're saying that while it's only available for XP SP2 now, it'll be available for those other OSes as well when it goes final.

Try a clean CD with no nLite and see what happens.

The problem is that the MS has silently updated KB904942. The last official one for download came out in February, featuring build 2784 of wdigest.dll. It was updated this week on MU/WU to build 2874, but no new download has been made available from MS' site.

You using any hacked files or anything?

http://www.sysinternals.com/Utilities/PsShutdown.html