tomasz86

You should ask Symantec about it. I think it may be related to the fact that these updates replace system files and modify many system related registry keys. Also they use exactly the same structure as M$ official updates but the difference between them is that M$ updates are digitally signed while mine are not. The two are completely different. Unofficial Updates Rollup (UURollup) = a rollup of unofficial updates Update Rollup 2 = a rollup of official updates & hotfixes They are complementary. EDIT By the way, which files exactly are reported as malware?? Out of curiosity I've just scanned the newest update created today through Virustotal and this is the result: https://www.virustotal.com/file/94d8a389ab82e44c0a99949469058adc1f826d9181dcf88840aa304bf1296d5f/analysis/1336600967/

Clonezilla is good for backing up whole partitions or drives. You run it as LiveCD (or from USB media) and it's pretty simple to use.

@bphlpt I've been trying to reduce the number of packages as much as possible but it's not easy and USP 5.2 is still far far away. @submix8c HFSLIP can't integrate OnePiece's Update Pack. Before I'd thought it could but I tried some time ago and errors occured during the integration process. It's too complicated for HFSLIP. On the other hand nLite won't integrate directly updates that add new files to the Windows source, ex. UURollup.

You can transfer your Windows from the laptop to the PC but it's a very unrecommended option, especially if they use different SATA controllers. On the other hand, my own system has already survived three mainboard changes so... I must say that yes, it's possible I'd recommend slipstreaming though. It's pretty simple in your case. I'm assuming you want to have ALL updates and hotfixes (both official and unofficial) and ALL other components like Silverlight, .NET Framework, etc. This is the simplest way to have EVERYTHING slipstreamed: 1) Download HFSLIP with all tools listed there. 2) Copy the "i386" folder and the three files "CDROM_IP.5", "CDROM_NT.5" & "CDROMSP4.TST" from your W2K Pro SP4 CD to HFSLIP's "SOURCE" folder. 3) Put the following files in your HFSLIP folders: - Windows2000-UpdateRollup2-BETA-x86-ENU.exe (HF) - Windows2000-UURollup-v9b-x86-ENU.exe (HF) - all IE6/OE6 unofficial updates (green background) and HBRs (yellow background) listed here (folders differ) - DirectX 9.0c Full Pack (skip the "KB935839-v5a" mentioned there) and 2631813 (both to HF) - all MDAC 2.8 unofficial updates listed here and MDAC281-KB983838-x86-ENU.exe (all to HF) - all WMP unofficial updates listed here (HF) - "UPHClean-Setup.msi" & "rootsupd.exe" from the Other Programs table (folders differ) 4) In the HFSVCPACK_SW1 folder put: Windows2000-KB829884-x86-Global.exe Windows2000-KB896414-x86-ENU.EXE Windows2000-XP-2003-MSRDP52-x86-ENU.exe Windows2000-UU-KBz2603381-x86-Global.exe Windows2000-UU-KB914783-KB974266-x86-ENU.exe Windows Powershell 1.0 (Windows2000-UU-KB926139-v2-x86-ENU.exe) 5) Create a folder called "HFAAO" and put all addons listed here in it. Use short filenames for .NET Framework, ex. "NETFX40.cab" for .NET Framework 4.0, etc. 6) Run HFSLIP and wait until it's finished. 7) Run nLite and use it to integrate OnePiece's Update pack. You may also want to disable Windows File Protection (SFC) because unofficial updates break it anyway. 8) Create an ISO with nLite and burn it. 9) Install Windows 2000 from the CD. I hope I've not missed anything

http://www.ryanvm.net/forum/viewtopic.php?p=123564#123564

Unfortunately there's no such a package available (at least not yet ). If you want to have a fully updated system and you can't use Windows Update then the best way to do it is to slipstream everything into your source before installation. If you decide the use unofficial updates then the easiest way to slipstream all of them is to use UURollup (see the link in my signature). In case of the official ones you need to download them one by one... The current list of W2K updates is available here. If you don't feel like downloading ~300 updates then you can use Onepiece's Windows 2000 postSP4 Update Pack. It's very comprehensive but doesn't contain any unofficial updates and lacks most of the HBRs (hotfixes by request; the ones with yellow background present on the updates list mentioned above).

@BlackWingCat There is a problem with your kernel32.dll and .NET Framework 4.0. After "installing" .NET 4.0 when trying to run a program which requires it, ex. this one you get: 1. Your kernel32.dll 5.0.2195.71xx (all versions): 2. WildBill's kernel32.dll 5.0.2195.7154. The program runs normally.

Does safe mode work? You should check the registry key mentioned here.

Well, I ran exactly the same benchmark (CrystalDiskMark) using exactly the same drive (Samsung 470) on two different controllers. The difference in results is huge :/

I've uploaded UURollup-v9b. The only change is that I modified file version of syssetup.dll from 5.0.2195.6611 to 5.0.2195.6612 to distinguish it from the official one. I've also added KB950305-KB977225. It contains some Universal Printer drivers. It must be slipstreamed through svcpack (HFSVCPACK_SW1 folder in HFSLIP) because it adds a few files which are originally not present in W2K's driver.cab, therefore they won't be correctly slipstreamed if you use the HF folder. It replaces the previous 950305 which actually also should be slipstreamed from _SW1.

UURollup-v9a (ENU) is ready. Mfc100.dll and mfc100u.dll had wrong checksum and that was the reason to prevent the installer from working when they were slipstreamed. I used a script to fix dependencies and "modifype.exe" to correct checksum but something went wrong and it the end the checksum wasn't changed. I'm sorry about that. Everything should be fine now

UURollup-v9 (ENU) is ready. I overlooked a dependency issue with MS VC++ 2010 libraries in the last version. They worked OK with BWC kernel but don't with WB kernel so I had to fix them and add the BWC's kernelXP.dll to the package.

This guide lacks the most important aspect of a Service Pack, i.e. how to make the new files and registry entries integrate when using the /integrate switch. Adding new files to all these [*.Files] sections will only make them install in a running system but for the /integrate switch you've got different sections like [servicePack.Files] and similar. You also must add the new registry entries to all the hive*.inf files and also modify (as already mentioned by zulebg) dosnet.inf and txtsetup.sif. I hope I'll manage to write such a guide myself later on.

@SearanoX You already said in the other topic that you were using UURollup but I forgot to mention that this .NET Framework 4.0 also requires the newest version of it, i.e.UURollup-v8 (ENU).

I've already "ported" .NET Framework 4.0 some time ago... but it's available only as a true addon. You can find it here. Even though it's an addon you can still install it manually: 1) Unpack the CAB file. 2) Copy the five DLL files to %systemroot%\system32. 2) Unpack "netfx40.in_" to "netfx40.inf" 3) Right click on it and choose "Install". 4) Choose the "NETFX40.cab" as source. 5) Installation will begin. I must say that it's not perfect and not all applications will work but you may try to run this tiny tool to see if .NET 4.0 is properly installed or not. By the way, the ~5 MB mentioned above was not about the size after the installation but was related to the size of the USP5.2's installer itself, like 345 MB instead of 350 MB

I have bad news. BlackWingCat's kernel32.dll breaks .NET Framework 4.0. Applications requiring it either display an error on run or just do nothing when clicked on. It's true that .NET 4.0 doesn't work perfectly in Win2000 but some programs do run and it would be kind of undesired to stick to BWC's kernel32.dll at cost of .NET 4.0 compatiblity. What I found out is that WildBill's kernel32.dll works fine so I decided to switch to this kernel32.dll once again. I'm sorry for inconveniece If anyone's interested you can check .NET Framework 4.0 using this tiny applicatoin. If it runs then everything is OK. If it doesn't run then you're probably using BWC kernel32.dll (or no unofficial kernel at all). Anyway, I have uploaded UURollup-v8 with WB kernel32.dll (5.0.2195.7154) and also uxtheme.dll removed because it's not supported by this kernel32.dll. I've used a small "trick" here so you can even safely install it over the last version and kernel32.dll will still be replaced even though the one from BWC has higher version, and uxtheme.dll will be automatically deleted too. I've also removed the .NET Framework addon and added two separate addons instead, one for .NET Framework 3.5 (2.0, 3.0 & 3.5 included) and one for .NET Framwork 4.0. If you need .NET Framework 1.1 or 1.0 you should just use OnePiece's addons

The problem may have something to do with this line: 13.015: DoInstallation:CreateProgressDialog failed but there's no detailed information so it's just guessing. I've quickly searched for it in the Internet and someone wrote that creating a new user account and installing it from there worked.

Is the situation same in safe mode?

Awesome list I don't know how it works in case of Vista/7 but if you use ntldr you can just use the bcdedit.exe to set {ntldr} as default and then you can easily choose between the two without waiting & rebooting. I've tested it with Windows 2000 & 8 using the same boot partition and it's way better then waiting for Win8 boot loader to bring up the menu (it's pretty slow...) & rebooting in order to boot the older Windows. There is no need to wait for reboot if you want to boot Win8 when ntldr is set as default.

As usually I was a little bit overoptimistic about it Yes, everything I want related to these duplicates can probably be done but it's quite complicated. I'm not sure if spending hours on it just to reduce the size by ~5 MB is worth it. I've been analysing Windows Server 2003 SP2's update.inf where such things are present (one folder for two editions, etc.). The file is just a horror The biggest problem is that the only existing "official" INF documentation somewhat related to those update.inf files is this very old one and many of the newer features are just not described anywhere so it's kind of a trial and error guessing game. I think I shall focus on integrating the actual updates because that's what I know how to do and can do pretty easily

I managed to overcome the installer limitations mentioned above The installer used in USP 5.1 was just too old! I replaced it with a new version which seems to support more functions. It should be possible to get rid of all unnecessary duplicates now.

No problem. For now I'll keep using beta7 since it does the job well. Thanks for your interest anyway

I did buy the device (Nook Touch) and love it. It's great and definitely worth the 100$ it costs. Even without rooting is still does the job very well. It does feel more like real paper and doesn't exhaust your eyes like any LCD screen does. The important thing is that it's colour changes depending on the type of light, i.e. it's different under sunlight, lamp, etc. I like it the most when placed under an incandescent light bulb

Well, except for the issues I reported last time, everything seems to work fine with the previous version. Of course I couldn't try all options but at least creating a W2K installation works perfectly fine and I also used it to prepare a Win7/8 installation (everything was done under Windows 2000 as a host). No problems occured. I just use the system's "format.com" to format the USB flash disk before using WinSetupFromUSB instead of Bootice / RMPrepUSB. By the way, not only USB drives but all drives seem to be detected as SCSI. I've got both SAS & SATA devices connected but all of them are listed as SCSI in the log file.

You may want to check the log file in the Windows folder. It will be called "svcpack.log".