tomasz86

I tried to do it but the result is standby instead of hibernation. I get 3,6 GB without PAE but I'm just wondering if there is any way to make hibernation possible with PAE on. I even tried to use the older kernel (pre 5.0.2195.49) but it's too old and doesn't work with other system files (bluescreen on boot).

I see So far I haven't seen any other problems connected with merging. I used your script to merge many update.inf files from Win2k updates and everything seems to work fine unless the update.inf itself has different structure (ex. IE/OE updates or WMP updates are different).

I haven't prepared the update.inf yet but I have some information about deduping sections. Generally, all [*.files] sections can be deduped without any problems. [sourceDisksNames] & [sourceDisksFiles] can be also deduped. As for the strings I wrote about a few days ago it's like this: The basic structure: [Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE% HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE% [Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Backup Dir",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed By",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed On",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Service Pack",0x10001,%SERVICE_PACK_NUMBER% HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Valid",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"Flags",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"New File",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"New Link Date",0,"" HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%\File 1\,"Old Link Date",0,"" HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ReleaseType",0,Hotfix HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows 2000\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%" HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE% ; Plugin.ocx HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%","DisplayIcon",0x00020000, "%windir%\System32\msiexec.exe" Without any loss of necessary data it can be reduced to [Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE% HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE% [Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed",0x10001,1 This line HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%","DisplayIcon",0x00020000, "%windir%\System32\msiexec.exe" should be reduced and go to both [save.Reg.For.Uninstall] & [Product.Del.Reg]. Final thing should look like this: [Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE% HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE% HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE% [Product.Del.Reg] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE% [Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed",0x10001,1 Finally, SP%SERVICE_PACK_NUMBER% should be changed to SP5 (all Win2k updates after SP4 are listed as SP5). So if we add ex. KB123456 it should be [Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB123456 HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB123456 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB123456 [Product.Del.Reg] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB123456 [Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB123456,"Installed",0x10001,1 The line HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB123456 in [Product.Del.Reg] is necessary to remove KB123456 from the list of installed updates. On the other hand, HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB123456,"Installed",0x10001,1 is needed to tell Windows Updates that KB123456 is installed. Is is also important to note that the basic structure I put above is also needed but in the case of a merged update it will be related to the name of the merged update, not the updates included in it. I'll give an example. Let's say we merge two updates - KB123456 & KB234567. The merged info should be [Save.Reg.For.Uninstall] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB123456 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB234567 HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB123456 HKLM,SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB234567 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB123456 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB234567 [Product.Del.Reg] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB123456 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB234567 [Product.Add.Reg] HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB123456,"Installed",0x10001,1 HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\KB234567,"Installed",0x10001,1 I hope you understand what I mean. Please tell me if my explanation is unclear or too complicated

Thank you for all your recommendations What I want to do is to repack the installer to M$ update format to make it streamable. Installrite seems to be the most user-friendly Is it 100% reliable?

No, you can't do it English version is available only for kernel v5. The newest Japanese version is v10.

Hello everyone, I am looking for a program which can monitor changes that happen to the OS when you (for example) install an application. To be more exact - I would like to check which files and registry entries get installed/changed when installing Microsoft Visual C++ 2005 Service Pack 1. I need to know exactly which files get updated and which registry entries are added/changed/removed. Is there any program that is able to do such a comparison?

I would recommend getting a PCI SATA controller. I tried a few of these cheap adapters and there was ALWAYS problem with them. Either it was reduced to ATA-33 (as dencorso pointed out) or it was working very unstable (connection lost when copying larger number of files, etc.).

v3 of both IE / OE Mini Rollup 1 & 1.1 is ready. Changes: - improved compatiblity with Windows Updates From now it's fully compatible with WU and the IE / OE updates included in the rollup won't be asked for by WU after you've installed the rollup.

BlackWingCat's installer (not Full Pack ) is a different thing. Apart from DX9c (June 2010) files it installs also a few modified .dlls (there is a detailed description somewhere on the MSFN board) and the main purpose of it is to install DX9 (June2010) in a running system, not slipstream it. It also doesn't contain KB975560 & KB975562 (BlackWingCat included different versions of msyuv.dll and quartz.dll, I guess the XP ones). On the other hand, DX9.0c Full Pack contains only official files coming from M$ and the only purpose of it is slipstreaming. You should use BlackWingCat's installer if you want to install the newest DX9 (Gaming) as my package doesn't contain an installer. DX9.0c Full Pack is only for slipstreaming.

I did a test on a Virtual Machine and no problems occur: shlwapi.dll's version numer is 6.0.2800.2007.

There is v10 available already but only in Japanese I really hope BlackWingCat will eventually make an English version of the newest kernel.

It's for HFSLIP only. I'm sorry

That's what I'm talking about I don't get any errors even if NOT using the BWC kernel.

It won't be an easy task the only suggestion I can give is - use portable installers if available.

HFSLIP uses folder called HFAAO for Addons that come in .CAB format.

My2GirlsDad, It's good to know that everything works now As for MDAC 2.81, it will be included in UR2.1. WMP9 - I'm still now sure whether to include it in UR2.1 or just make a separate package. PROBLEMCHYLD, Interesting... I got no errors when putting scripten.exe in HF (and I didn't slipstream anything else apart from it to be sure that it was scripten.exe to cause that error). Anyway, I always recommend using BlackWingCat's kernel (v5) as it extends Win2k kernel by adding functions from the XP one. Many programs which normally don't work under 2K can be run with no problems when this kernel is installed.

I'll check it Could you try running Dependency Walker on Wordpad.exe and check what files are causing problems (you can post a screen shot).

Molecule, odbc32.dll is caused by the broked header of KB2419632. I posted about it long time ago here You should try using the Global version (v2) which has this problem fixed. Windows2000-KB2419632-v2-x86-Global.exe PROBLEMCHYLD, are there any problems with the above updates (scripten.exe, KB975542, KB981349) when not using the kernel v5?

"Echo is off." still present update.inf

Are you sure it was related to the files from BlackWingCat? I would suspect an HBR to be responsible for this.

Yes I think there are no updates at this moment that CAN'T be installed on Win2k Server. You can even install DX Gaming on it Which files are you particularly talking about? In case of this one I'm sure it works as I'm using it myself on Win2k Advanced Server. My2GirlsDad, You may try putting "scripten.exe" in HF instead of HFSVCPACK_SW1. To summarise: #1. Use the fixed (v2a) version of IE / OE Mini Rollup 1.1. #2. Use the kernel v5 together with DX Full Pack (Gaming). #3. Put "scripten.exe" in HF. Everything should install fine.

2. You have to use this unofficial kernel made by BlackWingCat (and modified by me to make it streamable) when using DX9 Full Pack (June 2010). Windows2000-KB935839-v5a-x86-ENU.exe Just copy it to HF In case of DX9 Full Pack (Standard) there is no need for any patches. EDIT 3. This error is caused by Script 5.7 (scripten.exe). It's not related to anything else. I've just did a test where I used a clean Win2k SP4 & scripten.exe and processed it through HFSLIP - and got this error on the first boot.

After doing some tests: Kelsenellenelvian, nLite direct integration of UR2 is unsupported because UR2 contains a few files which are not present on the original W2K CD (ex. gdiplus.dll). It can be only integrated indirectly. I recommend using HFSLIP in this case. I'll have to add this to the readme. I'm sorry for inconvenience My2GirlsDad, These problems are not caused by UR2. 1. You're right about the IE / OE Mini Rollup 1.1. The header of shlwapi.dll is wrong. The same problem occurs if you try to slipstream WildBill's KB2416400. I prepared a corrected version of IE/OE Mini Rollup 1.1 (v2a) and KB2416400 (v2). By the way, KB2416400 & KB2423089 are already included in IE / OE Mini Rollup 1.1. You shouldn't use both 2. There is something wrong with DX Full Pack. I'll need to check it once again from the beginning. 3. It's caused neither by UR2 nor by IEOEMR1.1. I need to do more tests. I also suggest using the newest UR2 (v2). You could delete the following updates KB911564 KB925398-v2 KB954600 KB974112 KB977816 is also included in UR2 but only for WMP6.4. You're slipstreaming WMP9 so you still should slipstream KB977816 separately (as you're doing now). You also seem to include stuff related to Windows Update. UR2 at this moment is not compatible with it - the updates already included in UR2 will still show in WU. For this reason UR2 (v2) disables Automatic Updates by default. I'll write here again after I find out the causes of #2 & #3.

There is a bug in KB2416400. The header of shlwapi.dll is wrong and the file cannot be copied during text setup after slipstreaming. You can see it in the first screen shot here. I prepared a fixed version (v2). Windows2000-KB2416400-v2-x86-ENU.exe 4.05MB

I uploaded the v2a version of IE / OE Mini Rollup 1.1. Changes: - fixed an error causing Windows text setup to stop when copying shlwapi.dll after slipstreaming the rollup by HFSLIP (the header of shlwapi.dll was wrong) IE / OE Mini Rollup 1 is not affected by this problem.