tomasz86

There was also IE for Mac.

I think that first of all you should try to uninstall KDW. There must be something messed up with the registry. WMP10 itself relies on KDW/XP files but doesn't need any additional registry changes at all so you shouldn't worry. Have you tried restoring the browseui.dll to its original state?

Have you installed any "strange" updates or messed with system files? I've experienced this kind of error when browseui.dll (%windir%\system32\browseui.dll) was broken.

Finally I've managed to install the system and it turned out to be much simpler than it seemed to be in the beginning. First of all, I formatted the drive to NTFS using Disk Management. Next I opened WinSetupFromUSB and enabled displaying disk drives in Advanced Options. After that I could select the device I wanted to use. Now I went to txtsetup.sif and added (without changing anything) the wks_id = "Microsoft Windows 2000 Professional" line. Next step was to select the source folder in WinSetupFromUSB and click "GO". I installed the system on my notebook to test if it works and the installation process went "almost" perfectly. I say almost because there is one problem. There's an update which is run from svcpack and it has one prerequisite - it can be only installed during Windows setup. [PreRequisite] Condition = SingleOp, PreReq.SingleOp.InSystemSetup [PreReq.SingleOp.InSystemSetup] EqualOp = CheckReg, HKLM, "SYSTEM\Setup", "SystemSetupInProgress", 0x10001, "==", "1" Display_String = "%NOT_IN_SYSTEM_SETUP%" Now the problem is that it is not installed when using the USB device and there are no problems with it when setup is run from CD or in a VM. To be sure I disabled the condition and it also installed just fine. The other updates which go from svcpack also install without any problems. What's the difference here? Why is "HKLM\SYSTEM\Setup\SystemSetupInProgress" different when run form USB and when run from a CD or ISO in a VM? Apart from that everything seems to install perfectly OK.

I've searched for RunCore but they're too expensive I'll probably go for Samsung 470 64GB and remove the case to make it fit into this notebook.

That was it! It seems that WinSetupFromUSB can't detect USB flash disks properly under Win2k. However, there's another problem when loading drivers in the first stage of the text setup: I searched for it and found this topic. Now, the problem is that my version of Win2k is Advanced Server and what I have in txtsetup.sif is: [Strings] srv_id = "Microsoft Windows 2000 Advanced Server" Should I change it to wks_id = "Windows 2000 Professional" or add it as an additional line? Will it have no negative impact on the system?

I added: OnePiece_Microsoft.NET_Framework_v3.5.30729.3644.4_True_AddOn_ENU_W2K.7z This is modified version of OnePiece's .NET 3.5 True AddOn for XP/2K3. I fixed the dependencies to make it work smoothly in Windows 2000. The files used to fix them come either from BlackWingCat's KDW or directly from Windows XP. You must install OnePiece's .NET 2.0 True AddOn together with one!! When slipstreaming in HFSLIP, both of them should go to HFAAO folder.

Because it's a hotfix by request (HBR)

I've improved the script I use to merge updates and I've been testing a new version of IE6 Mini Rollup I made using it. Why am I posting about it here? I believe the problem related to KB982381 showing up on WU is fixed. It doesn't show up anymore when IE 6 Mini Rollup is installed even though all official & unofficial updates are included in it.

I've tried disk management - the drive is still not detected. HP USB 2.0.6 - also no difference. BUT I've also tried using another drive and this time PEtoUSB worked! However, it's still not recognised by WinSetupFromUSB

PEtoUSB doesn't work. I can format the drive using HP USB and I've already tried it before but the problem is that it's still not detected in WinSetupFromUSB. What system files exactly do these program use when formatting the drive? Format.com? Would replacing the 2K native format.com with the one from XP help?

I reinstalled my system and tried to run RMPREPUSB once again but it's the same as before. It doesn't matter whether it's set to FAT or NTFS. Bootice also doesn't seem to work. Is there any other program I could use to prepare the drive for WinSetupFromUSB?

I added two updates: Windows2000-UU-MSRDP7-x86-ENU.exe <- MS Remote Desktop 7.0 (quite experimental but works) Windows2000-UU-WIC-x86-Global.exe <- Windows Imaging Component (WIC) Both of them rely on DLLs coming from either BlackWingCat's KDW or directly from Windows XP. I'd also like to add one important information. Starting from this moment I'm going to test updates only in a system with (at least) BlackWingCat's kernel v5 installed. They may work without the kernel but don't have to. I'm sorry to say it but I just haven't got the time to test them in a configuration without unofficial kernel installed The kernel is also required for applications written in Visual Studio 2010 so I think using it is just inevitable.

I've removed KB908536. Uxtheme.dll seems to cause problems with .NET Framework based applications. I tried both versions - one from OldCigarette and the other one from BlackWingCat but unfortunately it's always the same. There's an error when trying to launch .NET based programs.

I've experienced this very annoying problem and wonder if there's any fix for it. Basically, after I resume from hibernation and use a USB 2.0/3.0 device, it's detected as Full Speed (1.1) so the transfer is very low. To make it work normally (Hi-Speed) I have to restart Windows. After doing so, it's detected as a Hi-Speed device again. Has anyone else experienced this kind of problem? It is a bug in Windows 2000 or maybe just a problem related only to my configuration?

No, the only thing I added was rdbss.sys It's different in case of 2479628 & 2079403 where changes are related strictly to the registry. Of course you can use both 980232 & 2511455. It's just (in my opinion) that the fewer updates, the better

I've found one more mistake on britols' page and this one I'd call critical. 2511455 is said to supersede 980232 but it does not because there's no rdbss.sys in it. If you slipstream 2511455 and don't include 980232 at the same time, you'll get a BSOD during Windows setup. I prepared a fixed version where I added the rdbss.sys from 980232: Windows2000-UU-KBz2511455-v2-x86-Global.exe

I've just tested it but still no difference unfortunately

WildBill, I've been having some problems with my computer and don't have access to my 2K system at the moment I'll try to test your patch as soon as possible.

Hmm, I can't say anything about Safari because I use Opera & IE only (and sometimes Firefox) but I'll check WMP10 on my system and see if there are any problems with it. Recently I've checked WMP11 to see if it's possible to run it in 2K but there seem to be a lot of dependencies which cannot (at this moment) be fixed by wrappers.

KB2479628 isn't an IE-specific update per se. It was just that initially there were problems when it was installed in an IE5 system. That's why separate versions were created and bristols still keeps them on his page. Starting from 2479628-v8 there are no problems regardless whether you use IE5 or IE6. Only if you happen to use IE6+FDV fileset, you must use HFSLIP 1.7.10 beta J v5 or newer to get this update slipstreamed correctly. Actually it may cause problems (in some cases) if you have both newer and superseded updates in HF folder. As for newer files, there are no problems because HFSLIP always slipstreams only the newest ones (=newest by their date, not version) but it may be problematic when both updates change the same registry entries. In such a case the newer one must be processed after the older. That's why I add the "z" after KB in KB2* to ensure that they are listed after the older ones starting with KB8* or KB9*. I used to keep both superseded official updates and newer unofficial ones in my HF folder but recently I've removed all the superseded ones to prevent any potential errors from happening. Actually I have two separate HFSLIP folders now - one with official updates only and the other one with unofficial ones included (and superseded official updates removed). Thanks to that I can easily check and compare them anytime I want.

OnePiece's True AddOns should work perfectly. I've tested them here and no problems so far.

Unfortunately there's no difference with c5i billtodd, 2286198 does supersede 967715. If you look at the file version of Shell32.dll, you'll see that the one from 967715 is 5.0.3900.7155 and the one from 2286198 is 5.0.3900.7158. Basically newer versions are based on older ones so the changes done to Shell32.dll by 967715 are also present in 2286198. Now, file version is not everything. There are also changes done to the registry. If you check update.inf files of both of these updates it'll be clear that they both add the same things to the registry. However, you do have the point here because indeed there are two mistakes on bristols' page. 1. 967715 is superseded by 2286198. <- Correct. 2286198 is said to be superseded by 2479628 so 2479628 should supersede both 967715 & 2286198. <- False Actually the current version of 2479628 does not supersede 2286198. The shell32.dll file is newer but the registry changes added in both 967715 & 2286198 are not present in 2479628! I prepared a corrected version of it. Windows2000-UU-KBz2479628-v9-x86-ENU.exe Now it really supersedes 967715 & 2286198. 2. 2079403 is said to supersede 955069. In reality it does not. The problem is the same as above - the registry changes done by 955069 are not present in 2079403. Here is a fixed version: Windows2000-UU-KBz2079403-v2-x86-Global.exe I prepared also an another additional update: MS10-005: Vulnerability in Microsoft Paint could allow remote code execution Windows2000-UU-KB978706-v2-x86-ENU.exe Windows2000-UU-KB978706-v2-x86-PLK.exe mspaint.exe 5.1.2600.5918 I have decided to add -UU- for "Unofficial Updates" and "-HBR-" for hotfixes (by request) to filenames from now on so it should be much easier to know what kind of an update it is. I hope everything is clear now EDIT I've changed the filename of KB978706 to KB978706-v2 in order to distinguish it from the original KB978706. You must not use both official KB978706 and unofficial KB978706-v2 when slipstreaming in HFSLIP because the newer paint.exe won't be copied in such a case.

Caspean, If you want direct integration (Yumeyao's addons are switchless installers) you should try True AddOns made by OnePiece: NET 1.1 NET 2.0, 3.0 & 3.5 NET 4.0 These are integrated directly into Windows' source and are installed before T-13. If you create HFAAO and put them there, HFSLIP will automatically unpack and slipstream them. Yumeyao's ones bprobably won't work from HFAAO (as far as I know).

At this moment it's not SSD, just normal 2.5' 250 GB SATA drive. I connected it in order to test the adapter whether it works or not. Capacity limit shouldn't be a problem in case of SSD because if I buy one, it'll be a small one (<=64GB). This notebook (Samsung SENS Q10) was made around 2002 and there's been no BIOS updates released at all.