RyanVM

Well, you need to actually register the CAT files too. Normally it would be handled by the INFs.

I currently use batch files, but I've been meaning to switch over to RunOnceEx at some point.

(You're talking to the guy who maintains the XP SP2 Update Pack). Yes, CAT files are what Windows uses to verify file authenticity. And upon verifying them, it protects them with WFP. And yes, a CAT file does exist for WMP9 - SP2.cat, and layout.inf, and sfcfiles.dll, etc.

You might want to hold onto the CAT files so that WFP will protect the files still.

OK, I see the problem. It's being caused by WhoLockMe. It'll be out of the next release until I can figure out what's going on and a way to fix it. Thanks for finding the problem. EDIT: New release should be out next Tuesday, for the record (Mcirosoft patch day). EDIT2: To fix the problem for now, open up a command prompt and run the following command: regsvr32 /u WhoLockMe.dll

You can put it in any of the 3 sections. It doesn't matter. You could make a new [sourceDisksFiles] section if you really wanted.

First off, you don't need to shout at us. Second, this should be what you need: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Start_ShowMyComputer"=dword:00000002

, gosh has been gone for 6 months now. Good luck getting a response.

Size and time.

Not to be rude, but I've searched through this thread and I don't know/see which reg entry you mean. Maybe you could repost?Sorry, that was on my other forum:http://www.ryanvm.net/forum/viewtopic.php?p=415#415 No, it doesn't matter when you apply it. I have no clue. I personally don't even use it. From what I've been told, though, is that you'll notice when you use P2P programs like eDonkey.

I actually almost did include it, but ended up removing it prior to the initial release. My reasoning is that I don't want to include hacked files the user has no control over. With SFC_OS.dll, WFP still remains enabled unless they change the registry entry to disable it. For uxtheme.dll, the user won't notice a difference with everyday usage, only if they're using unsigned themes. However, users have no choice with tcpip.sys but to accept whatever changes it provides and no option for the default behavior. And what version of XP do you think I'm using? Finally, the checksum of this modified file is 5c381. If you want QFECheck to report KB884020 as properly installed, edit the registry entry (which I gave in an earlier post in this thread) with that value. For those coming to this thread looking for a quick download, this is a cab compressed (ready to put in the i386 folder of the XP CD) hacked version of tcpip.sys build 5.1.2600.2505 allowing for up to 100 simultaneous connections. It was made on a US English system, but as SiMoNsAyS said in his first post, it shouldn't matter since the file is language independent. http://www.ryanvm.net/msfn/files/msfnforum/tcpip.sy_ (171KB)

Gotcha. So will that show up in Windows Update? Or just be mentioned in QFECheck? Just QFECheck. Windows Update only checks for the presence of the registry entries, not the validity of the files described by them. Neither . SiMoNsAyS' version is from the original RTM version of the file (build 2180), and I've heard that hacking it for unlimited connections causes problems. Hold on a sec and I'll post a build 2505 version that's hacked for 100 connections and ready to be copied into i386.

So I should run the tool, and copy "tcpip.sy_" from: where? then put it in the i386. then itll work fine, and won't interfere with your pack at all? You can just download the hacked tcpip.sy_ from this thread. It's pre-compressed and ready to be put directly in i386. No, it won't interfere. QFECheck works by examining the file versions and checksum information provided to it by the registry entries all hotfixes create upon their installation. It verifies that they're the same or newer as the versions specified. If you included a modified version of tcpip.sys, the file will have a different checksum than the original. As a result, QFECheck will report that KB884020 isn't installed properly.

It'll work fine, just put the hacked tcpip.sy_ in i386 after you extract the cab archive. Also, take note of the fact that QFECheck will complain that KB884020 isn't installed properly since the checksum of the file will be different. I've already had one guy on my forums bitching about it, and I don't need a second.

No, it's cab compressed. Extract tcpip.sys from it with a program like WinRAR. Also, you'd need to overwrite both the copy in system32 and dllcache. I'd personally recommend you just use lvllord's patch which takes care of all it automatically. www.lvllord.de

If you're in the cmdlines.txt stage, you can use this: SET CDROM=%CD:~0,2%Otherwise, this will work in any stage: for %%i in (C: D: E: F: G: H: I: J:) do if exist %%i\win51ip.SP2 set CDROM=%%i

I'm filing a bug report with Sun right now. Hopefully we can get this resolved.

Short of emailing Sun and asking them what's going on, I don't know. You'd think using the Reboot=ReallySuppress switch would keep it from restarting, but even that doesn't work for some reason.

Believe it or not, but I have directions on my site! Try reading them. http://www.ryanvm.net/msfn/updatepack.html

You can always use the Lite pack as well if you don't want any frills. And like Smeeeprig, please take questions like that to my forums to keep discussion in one place instead of many.

for some reasons, i can't download a full package from the above web site. I receive "cannot find server" error. another site host this file??? thanks I'm sending you a private message.

Now that it happens with people using a standard administrative install point (the foundation of my installers too), at least we know that it's not a problem specific to what I'm doing. This is striking more and more as a bug with Sun's installer.

All I know is that my batch file called by GuiRunOnce runs the Java EXE and doesn't restart. I can't tell you why, only that it does.

Yes I could change that. I don't think it needs to be "fixed" since it's an intended feature, though However, I must say that Sun's administrative install point is unlike any other AIP I've ever seen, and it's been a bugger to figure out so far. The files are stored zip files and decompressed during setup. Also, registry entries are imported by a mechanism I don't yet understand (it's not the usual way).

www.genmay.net www.ryanvm.net/forum www.msfn.org/board