RyanVM

Doesn't matter at all as long as they're in the correct section. You could even make brand new sections for them if you really wanted to. EDIT: In fact, I do exactly what you're asking about.

dosnet.inf is a hell of a lot longer than that. Scroll down a bit. Or you could always do a trusty Ctrl+F to find it.

Directly from the changelog:

How are you trying to install them?

I like to keep my beta testers on their toes BTW, thanks again for your help in getting this out the door.

Short answer: this isn't a democracy, so no Now for the long answer. My directions explicitly say that the pack should be extracted immediately after slipstreaming SP2. The main reason for saying that is exactly what you pointed out. Second, I'm aiming for the widest audience possible with this. The fewer modifications people have to make, the better. Many people are very uncomfortable opening up even two relatively straightforward files for editing, let alone decompressing, editing, and recompressing the files. Not to mention that the more editing people are required to do, the more likely they are to make mistakes. I for one don't like troubleshooting other people when it's a mistake on their end, not mine. So bottom line is that if people follow the directions on my page, they won't have problems However, I can (and probably will) edit the page with directions for those who don't want to extract sysoc.inf and svcpack.inf and would rather edit it themselves. I will not be taking them out of the pack, however.

If you remove them with nLite, then there's no point in going through the hassle of taking them out manually. nLite will still get rid of them like normal.EDIT: Assuming you follow my nLite instructions, anyway. Component removal happens after the pack is extracted.

Just so you guys know, the URL for my installer has changed. It's now: http://www.ryanvm.net/msfn/files/acroread602.exe

I'm hoping by the overall lack of response that 1.0.1 is working better for people

Absolutely. Just download the full pack and extract it to a directory other than i386. You can expand the INF file to see which files belong to those components and delete them. Might I ask why you don't want those files specifically? CalcPlus has the same look and functionality as the original calc.exe, but it has some improved functions. RDC is the same as before, but with an option to automatically reconnect if disconnected. The hacked SFC_OS by default still leaves WFP on. You'd still have to edit the registry if you want WFP turned off. The hacked uxtheme won't impact you at all until you want to use unsigned themes. If you stick to signed themes, there's no difference at all.

Windows File Protection changed it back to the original version. You need overwrite both the one in system32 and dllcache in order for it to stick. (Or just use my pack )

Don't extract flash.oc_ or swflash.in_ from the CAB download. You can just pull makecab.ex_ out of the full pack and replace it with the version in i386. Or just PM me with your email address and I can send it to you. Thanks

Yes, that would be fine. The registry entries for the Hotfix are applied somewhere around the T-39 stage of setup (ain't it cool? B)), so that should be OK. That's what I'm currently working on figuring out. What'll have to be done is to create a digitally signed CAT file that says that the file with that checksum is OK. Easier said than done, but I've got some tools that'll hopefully allow me to accomplish that feat (i'd like to be able to protect some other files in the pack as well which are currently unprotected).

, something like that No, it's not patched for unlimited connections. I actually originally put the patched file in the pack, but later decided to go back to the original for a few reasons which I'll explain to you.First, I want as many files in the pack to be protected by Windows File Protection as possible. The patched version (as you would imagine) has a different checksum from the original, so the security catalog doesn't recognize it as valid and hence won't protect it. Second, most average users will see no benefit from patching the file, and patching the file is (for the average user) something that's irreversible (as opposed to SFC_OS.dll, which can be patched but still have WFP enabled). Those who can actually use the patched file (pretty much if you're using P2P apps) will be able to patch it easily afterwards. Yes, you can patch the file, fix the CRC header with ModifyPE, and makecab the file and replace it on the CD. The only real downside is that it won't be protected by Windows File Protection and the registry entry for the checksum will be incorrect, which might throw off qfecheck (it's very easy to change that, though). EDIT: Also, nLite will still allow you to patch the file. And nuhi's slaving away on an updated version which natively supports this pack as I write this

I have no idea what's going on. Like I said a bit ago, I was able to manually install WinRAR 3.4 just fine. I don't know of anything in my pack which could be causing issues like that. Everything is quite self-contained.

1.0.1 is up. It fixes all the issues that I'm aware of at this point. Download & Instructions: http://www.ryanvm.net/msfn/ Changelog: http://www.ryanvm.net/msfn/changelog.html READ THE DIRECTIONS AND MAKE SURE YOU'VE FOLLOWED THEM TO THE LETTER BEFORE POSTING HERE THAT YOU'RE HAVING PROBLEMS

The cmpnents directory is not needed. Yes, use the .NET installer (not that I'm biased in its favor or anything ) at the RunOnceEx stage. Also, please keep this thread on topic.

Also, I can't reproduce the problems a couple people are having with compression programs. I did a fresh install of XP in VirtualPC. I then copied WinRAR setup and a random RAR file onto the desktop of the virtual machine. As expected, the RAR archive was seen as an unknown file type. I then installed WinRAR. The RAR archive was then recognized as a WinRAR file. I restarted the Virtual Machine and it was still recognized as a WinRAR file and opened just fine when double clicked. Am I missing something?

@Adiel: Very shortly. I just changed things to an 8.3 naming scheme, so I'm testing the ISO quick just to make sure I didn't miss any file calls when I made the change. @codejunkie: Try actually looking at what those entries are that you're posting before you start questioning my judgment. Most are for dllcache, which is just the WFP-protected files. It's completely irrelevant. Some others are for caching that's irrelevant when the files are integrated. Also, there's one for the uninstaller, also unnecessary. Trust me, everything that needs to be added is added. Also @codejunkie: Don't get ahead of me. Some things will be changing in 1.0.1 that will long term make things easier. Part of taht is that the CAT file entries won't be added to dosnet.inf and txtsetup.sif. Read the changelog link I posted earlier.

exactly http://www.ryanvm.net/msfn/changelog.html A sneak peak

Making a changelog website right now as VirtualPC runs in the background

I already posted in the thread that I'd be releasing an updated version today with that fix included. I think it's back a page or two.

I'll look into it, but I don't see what in my pack could be causing that.

Give it a couple days. The EXE was just released yesterday.

I've got an update coming out tomorrow. It'll simplify some installation issues (only needing to add two lines to both dosnet.inf and txtsetup.sif and never needing to add any after that) and adds the KB885894 hotfix to the pack. There will not be an update pack for this release as it's going to be making some changes to the structure of the update. However, the changes made will make it easier for update packs in the future. I'll post more on this tomorrow. Gonna test it out in VirtualPC shortly then go to bed