Jump to content

RyanVM

Member
  • Posts

    2,756
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by RyanVM

  1. Send me an IM (my info's in my profile) and we'll see if we can figure it out. Odds are it's just a typo.
  2. Thanks both of you No current plans for anything else. I think just supporting this pack and continuing to make installers like .NET 1.1 SP1 will keep me plenty busy
  3. You need to adjust the parameters you send to shutdown.exe. My page has a link to the PsShutdown web page which contains the command switches to use with it. A few are different from the standard shutdown.exe. ...? This pack is supposed to be integrated into your XP CD, not installed on top of a current XP installation . I guess I don't understand what it is you're doing.
  4. Java5 was originally going to be released as version 1.5.0. Sun changed their mind and named it 5.0 for some reason unbeknownst to me (I think they wanted version number parity with some of their products or their competitors' products).
  5. Actually, that's a very good question. And there's a couple of ways to verify that it's installed correctly. First, at the T-12 stage of setup, you'll see a little window pop up with a title of "Updating Registry". That's my pack adding a couple extra registry entries that can't be added from INF files. That'll tell you that the INF executed properly. To verify that the hotfixes are installed, you can do a couple things. First, you can go to Windows Update. If everything is installed OK, only Windows Journal Viewer and Windows Media Player 10 will be on there. Second, you can download the program "qfecheck" from Microsoft (it's also included in the full pack), and it can verify that the hotfixes installed are up to date. Third, you can go into c:\windows\system32\dllcache. In there, you'll see all the files currently protected by Windows File Protection. You'll see tcpip.sys build 5.1.2600.2505 and update.sys buid 5.1.2600.2508 in there (amongst a few others). Those are the hotfixed versions. Fourth, you can go into c:\windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}. There you'll see KB884020.cat, KB885523.cat, KB885626.cat, and scripten.cat. Those cat files were all installed by my INF file.
  6. Correct me if I'm wrong, but isn't there an INF file included with the hotfix, with the neccesary registry changes? There's a few problems with the INF file included. First, there's a crap ton of extraneous garbage in them that isn't necessary. Second, I looked through them before, and frankly I didn't see the entries that were needed in them . I just install the fix in VPC then run ART on it to see the changes. Generally, it's just adding the entries to HKLM\Software\Microsoft\Updates key and HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix key.
  7. Protect some of the other replaced files, like calc.exe, shutdown.exe, etc
  8. Good idea. Consider it done.
  9. Actually, updating for new hotfixes is VERY easy with this method. In fact, the main reason I did it this what is exactly because of that. I'm planning on making upgrade packs when new hotfixes come out so people don't have to download the full 5+MB archive every time. All it'll take is an update HotfixUpdates.inf and of course the newer files (EDIT: Put it this way, it took me about 15 minutes to add KB885523 into it the other day, and the vast majority of that was me having to install the update in VPC to get the registry entries added for it) And yes, [ProductCatalogsToInstall] is vital to the proper installation of the hotfixes . It's that stage that allows the updated files to be protected by WFP (can be confirmed by finding them in dllcache).
  10. Read my profile for contact info. And bootvis has an explicit "optimize" command. You could always check the help file.
  11. B) Isn't that you guys' job?
  12. It doesn't matter which [Files] section you put them in. And I'm using the exact same disk (VLK w/ SP2 slipstreamed) as you. EDIT: yeesh, it's like people think I didn't test this at all EDIT2: You'll be shocked to know that txtsetup.sif has multiple sections with the same name as well. It doesn't matter.
  13. Glad you're a fan of my other packs Do remember to remove the msxml4sp2 installer from your unattended setup now Also, make sure you get the Java Runtime Environment 5 installer from me too!
  14. The only reason I found out was because I was poking through the registry entries and came across entries for 5 that got put in when the DLL got registered
  15. OK, I think you're confused on a couple things. First, understand that new MSXML versions do NOT necessarily make older versions obsolete. By default, XPSP2 comes with both MSXML 2.6 and MSXML 3.0 installed. My pack adds both MSXML 4.0 SP2 and MSXML 5.0, both of which add their own features, but neither of which makes the other obsolete. That being said, you don't need to install MSXML 4.0 SP2 if you use my pack because it's included in it . Hopefully you understand that the entire POINT of this pack is to make it so all of the components included in it do NOT need to be installed seperately. Having MSXML 5.0 already installed when you install Office2003 shouldn't make any difference at all. I wouldn't worry about that.
  16. You could try running bootvis too and see if that helps.
  17. Only needed if you have installed.
  18. Correct, it's actually RaveRod's modded dll. SFCSetting is in the same place as always: ;Disables System File Protection [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "SFCSetting"=dword:ffffff9dAgain, remember that I have it set to zero by default, so WFP will remain active unless that registry entry is changed. It's not on Microsoft's site. It comes with Office2003. Consider it a bonus Yes, with the LZX:21 setting. You're welcome
  19. Oh, I forgot to mention something on the site (I'll update that in a sec). If you're using this with nLite, be sure to uncheck "nLite Post Setup Cleanup" to avoid some potential RunOnceEx issues. I've been reassured by nuhi that it does very little (if anything) at this point, anyway. EDIT: Site's updated.
  20. I've got makecat now. Now to make it work I'll give you some pointers. Expand sysoc.in_, svcpack.in_, and hotfixupdates.in_ to see the magic
  21. Time and space Also, to whomever just PMed me about AutoIT, I accidentally hit the delete button instead of reply (whose idea was it to put those two similar looking buttons right next to each other anyway? ). Please PM me again.
  22. You're the third person in the thread to point that out . I fixed it already and re-uploaded. The main idea behind the Lite pack was for languages other than English. If it can be confirmed that 5.2.3790 is language independent, I'll move it to the Lite pack.
×
×
  • Create New...