RyanVM

ftp://ftp.adobe.com/pub/adobe/reader/win/...70_enu_full.exe EDIT: The good news is that it appears PrintMe was removed from 7.0, so that's one less thing I'll need to do myself

Yeah yeah, yuck it up For what it's worth, I found a download link for 7.0 (from Adobe's FTP server, so it's legit)

PsShutdown gives the same window he was referring to

I don't see a download on Adobe's site for Reader 7.0 yet. And yeesh, if had known it was coming so soon, I doubt I would have bothered making one for 6.0.3.

Acrobat Speedup works by moving files from the "plug_ins" directory to the "optional" directory. My initial thought is that mimicing that behavior within the installer MSI might not work depending on how Acrobat is trained to look for plugins. I probably won't do any acrobat speedup type stuff with my switchless installer. For what it's worth, Acrobat Speedup can be run silently.

Shoot me an IM and I can make you a custom one. Be warned that I'm out of town, though, so I may not respond to my IMs right away (I'm remoting into my desktop back in Philly to get work done)

The executable available for "public" download seems to be a 7-ZIP SFX. Is Asta's "special silent" installer the same thing just packaged in a silent SFX? And, if that's the case, any objections to someone (say, me) taking it upon themselves to make those modifications for their own benefit, Ryan? It's the same core file. The only difference is that the MSI is called with the /qn switch instead of the /qb-! switch. As far as I know, Igor has yet to implement silent extraction into his 7zip SFX module (I emailed him awhile ago about it).

Well, two would be version 1.0.4 of my post-SP2 update pack The other is a file for another board. It's unrelated to MSFN.

Yup, up and working. http://www.ryanvm.net/msfn/faq.html

Yeah, I saw in my FTP logs that you'd gotten it

wow, 63 downloads already

IM me

This key doesn't exist on my system? (XP SP2 NL) That's probably why it isn't showing for Dutch users. I can confirm that the solution keytotime posted works.

6.0.3 switchless is up. http://www.ryanvm.net/msfn/

Yes, that should work. But there's another way which supposedly works that I'm in the process of verifying.

I'm inclined to agree that classic packs should remain. Direct integration is very nice and like keytotime said, it allows users to use it without necessarily having an unattended CD.

Have you actually tested that? My result with that registry entry is that WindowsUpdate still wants to install it.

qchain hasn't been necessary for new hotfixes for over a year now And to expand on what Alanoll said, here's what /integrate does: 1.) Updates the hotfixed files in i386 with the GDR version of the file. The updated file is uncompressed (.dll instead of .dl_). 2.) Copies the cat file for the hotfix exe to svcpack folder within i386 3.) Renames hotfix exe to KBxxxxxx.exe and copies it to svcpack folder in i386 4.) Adds entries to svcpack.inf to install hotfix catalog file and run the hotfix exe during setup So what you end up with is an uncompressed hotfixed file in i386 and a hotfix exe and cab file in the svcpack folder. The advantage is that the updated file is used from the beginning, so vulnerabilities are patched from the beginning. The downside is that the exe must still be run to fully install the hotfix. @ DLF, I can assure that I release updated packs whenever any critical updates are released. No, I don't release new updates for minor updates that most people aren't affected by, but I do for major updates.

Well, all post-SP2 patches do support the /integrate command, which works better than nothing.

Yeah, it's driving me nuts. Oh well, if the workaround works, the renamed blastcln.exe is 40KB extra on the download size - not exactly a big deal for an 11.5MB file. And it adds an extra 7k to the overall size of the CD

danke shoen

That is strange, I have been checking your site regularly and it still shows version 1.03 only. In fact I just checked again before making this post. PS: I changed the '.03' to '.04' in the link "hxxp://www.ryanvm.net/msfn/files/RVMUpdatePack1.03Full.cab" and was able to download the file. My bet is you've got a cached copy either on your end or from your ISP. There are ways to force a reload, but I don't remember them off the top of my head (I think it may be Ctrl+Reload)

I tried nearly every combination of file/registry settings I could think of, but to no avail. And I'm really not tricking WU into thinking it was run, since it was actually run . I'm just fooling Windows setup into running something other than what it thinks it is.

Well, I figured out a way that works. As some of you are aware of, blastcln.exe is already on the XP CD. Also, you can see on a fresh install that at some point during XP setup, blastcln.exe is run. The evidence for that is a log file in c:\windows\debug named blastcln.log. I also noticed when running doomcln.exe that a doomcln.log was also created in the same directory. This got the gears spinning in my head. So I tried renaming doomcln.exe to blastcln.exe and compressed it and put it in i386. And (not) to my surprise, it worked! doomcln.log was present and WindowsUpdate no longer wants to install. So for the next release, that's what I'll be doing unless someone can find a better solution.

Interesting, I just ran a normal test install in VirtualPC with my usual winnt.sif (with Hyperterminal not installed) and qfecheck still reports 873339 as being installed properly. Mind you, there's not a trace of hypertrm.dll on the system. Weird but convenient at the same time (And for those of you who didn't notice, 1.0.4 of my pack is out)