tomasz86

Ah, so I guess that we have found the culprit then! Even though you did take some time away from me, it is all right . At least now we know that slipstreaming with HFSLIP2000 works fine under all versions of Windows, and I myself will definitely make use of the HFSLIP2000-info script in my future testing. You kind of motivated me to actually write the script, and for that I am very thankful. I would guess that it is nLite adding those drivers to cause the IE/DX issue. Installing from USB should normally not affect anything, unless you have used some kind of a fancy tool which tampers with the system files. I do not use nLite anymore, but as far as I remember, there is a special instruction on using it after HFSLIP. Please check https://web.archive.org/web/20171220125454/http://www.vorck.com/windows/2ksp5.html, especially "Step 13". "This utility" can be found here: Edit: I just want to say that I have not forgotten about the .NET incomplete installation problem. If you look carefully at the progress bar during the Windows setup process, you can clearly see that the .NET Framework components are being processed extremely quickly. I would say - too quickly. This likely means that the INF files responsible for their installation are simply being skipped there. I will try to troubleshoot the problem, but I may need some time to investigate all the possible causes.

Yeah, so the only difference between the old HFSLIPWU.INF and the new HFSLIPWU.INF is the HFSLIP2000 version number included in one of the strings (1.0.2 vs 1.0.3BETA), which does not matter also. Right now there seem to be basically no differences between your and my copies of the updated Windows 2000 source, but mine installs perfectly here, so I am quite confused. I myself am using Windows 7 (fully updated) as the host OS, and testing the installation in VirtualBox (v5.2.28). Where are you installing your Windows 2000? Is it a real computer, or a virtual machine? I will try to test slipstreaming under Windows 10 (1809), and will also try to find out why that experimental version of HFSLIP2000 fails (because it is the only case where I can reproduce the IE/DX versioning issue). Edit: Slipstreaming under Windows 10 makes no difference for me. The resulting source folder is exactly the same as the one slipstreamed under Windows 7. It installs correctly too.

Thank you. As I mentioned above, the difference between the two SETUPREG.HIVs does not seem to matter though. There is, however, another difference in the two HFSLIP-info files of yours. Could you please upload HFSLIPWU.INF from the i386 folder - both the old and the new one?

I think that we may have a little bit of a mistery here. Your "SETUPREG.HIV" is indeed abnormal. The file has basically its contents doubled, hence it has twice the size of the original. The problem is that even in this state, it does not affect the installation process. I have used the file for my test installation, and there was no difference with the previous one. The installed system was functioning 100% normally, with both IE6 and DX9 present. At the moment, the only way that I can reproduce the IE/DX missing issue is when using that experimental version of HFSLIP2000 from two years ago, but your log file suggests just the standard version of HFSLIP2000, so I am really not sure what may have caused the issue .

Hmm, I expected some significant differences in the slipstreamed files, but in fact almost all of them are exactly the same as in my source, with the exception of "SETUPREG.HIV". Yours is almost double the size of the original, which is quite strange. This file is modified by HFSLIP only in the very beginning of the slipstreaming process when adding support for larger drives to the Windows 2000 installer, and I am suspecting that this may be the host OS (which is Windows 10 in your case) to mess the things up. Even after the modifications, the file size should normally stay roughly the same (as it is in my case). I would like to ask for two things: 1. Could you please share your "SETUPREG.HIV" file for inspection? If possible, both the one from your unmodified Windows 2000 source, and the one after using HFSLIP2000. 2. I have uploaded a new, beta version of HFSLIP2000 to the Archive under https://mega.nz/#F!2lBVBBLI!WqmqhpxuX0qyCY1LiX4-gw!L0omSarK. This one does not use "reg.exe" from the host OS, but rather relies on the one from Windows 2000 to patch "SETUPREG.HIV". This will probably require some time, but if possible could you use this version of HFSLIP2000 to slipstream everything again, and then run "HFSLIP2000-info.cmd" on the newly created source? I would like to compare it with the old one to verify my suspicions.

I like this attitute . I have uploaded the script to the download Archive under https://mega.nz/#F!2lBVBBLI!WqmqhpxuX0qyCY1LiX4-gw!L0omSarK. Please download "HFSLIP2000-info.7z" and unpack it to your Windows source folder. The file structure will look something like this: I386 SUPPORT CDROM_IP.5 CDROM_NT.5 CDROMSP4.TST HFSLIP.LOG HFSLIP2000-info.cmd Then just run "HFSLIP2000-info.cmd" and wait for the results. It may take some time as the script is not optimized (=it is slow), and also right now requires to be run in Windows 7 and above (because of one of the tools used to calculate SHA1). The script will make a list of all files from the i386 folder, including their size, version, and SHA1 checksum. Once the script has finished its job, you will find a new file called "HFSLIP2000-info.txt" next to the script file. Please pack it and upload somewhere for me to see.

Thank you. The log indeed indicates the official version of HFSLIP 2000, not the experimental one, and is exactly the same as mine from yesterday, which installs correctly here. Something must have gone wrong during the slipstreaming process, but the HFSLIP log, unfortunately, does not include any post-slipstreaming information. What is your host OS, by the way? HFSLIP, of course, always says "Windows Vista", but in reality this covers all Windows versions from Vista to 10. If the HFSLIP log included a full list of files with their version and what not, then it would be a different story, but with such limited information, I am unable to do any more blind troubleshooting. To really be able to investigate more, I would either need to have access to the full i386 folder to check the files myself, or ask you to run a special script that would make a full list of the slipstreamed files with their versions. My question is - would you be willing to run such a script? I am asking since I have to write the script first and do not want to do it for nothing. Another option would be to pack the i386 folder and upload it somewhere, but this would be classified as illegal Windows file sharing by M$, even if done only for troubleshooting purpose . PS To hide the content, you need to manually type [spoiler] [/spoiler] around the content you want to hide. It will show up as a thin line in the preview, but clicking on the line will not do anything at this stage. The content will become hidden only after you submit the post. Sounds complicated? Yes, the new "modern" and shiny forum software is kind of a pain to actually use. Who would have guessed...

Please let me know once you try again. The thing is that that experimental version is/was also called "1.0.2", although the structure of the final log file would be a little different. If you can still find the log file, I would like to have a look at it.

I did some testing and here is what I have found. Everything slipstreams and installs correctly when using the official version of HSFLIP 2000, which at the moment is version 1.0.2, which is also included in the FullPack package. Using my test version of HSLIP 2000 which I talked about sometime 2 years ago (i.e. the one which greatly sped up the integration process) results in a partially broken installation. I am not sure what exactly gets broken, but there is at least this IE and DX problem, and also the installer once asks something about installing unsigned drivers, which should not happen in an untouched, clean installation. I liked to use that version of HFSLIP 2000 for my testing because, well, it is so much faster, but I will not do it anymore. That version is currently available to download at my GitHub, but it is not advertised anywhere else otherwise. The FullPack uses just the standard version of HFSLIP 2000 as well. My question then is - @win32, did you happen to use the experimental version of HFSLIP 2000 by any chance? On the other hand, the problem with .NET is unrelated and I believe it is simply HFSLIP being unable to properly slipstream it. All the files are copied to the system folders correctly, but there is likely an error in the file registration and executing process. I will try to see if there exists any simple fix to this issue. In the worst case, I may simply end up disabling the automatic installation, and leaving only the manual installation through the Add/Remove Programs applet in the Control Panel. Right now I will very likely remove the broken experimental version of HFSLIP 2000 from GitHub, as I have not been working on it any longer. I actually do not want to do any more patchwork on HFSLIP, and I have some other ideas in mind for the future, so for now I will concentrate on bug fixes only.

You are right. I can confirm that something is indeed very wrong. I would actually say that this is a critical bug. I am pulling the FullPack from the download Archive for now. I will have to test whether it is another component butchering the installation, or HFSIP2000 itself. I am very sorry for the situation. I am not using Windows 2000 as my daily OS anymore, and no one had reported these problems before, so I had no clue. I will try to find a solution as soon as possible.

Could you provide more details on the exact problem? Do you end up with IE 5 and DirectX 7 installed instead of the newer versions? Could you post screen shots? I have personally not experienced such a problem. In my new, fresh installation of Windows 2000 using the FullPack I have both IE 6 and DirectX 9 installed correctly. I have conducted a fresh installation using the FullPack and can confirm that the .NET programs indeed do not work correctly. I am guessing that it is HFSLIP unable to correctly integrate the .NET addons. I will try to do more testing and see if the issue is fixable, either in HFSLIP2000 or the .NET addon packages themselves.

Thank you for reporting the problem. I will try to check it myself, but just in case could you give me names of those programs?

Yes, the FullPack contains all the required updates. I have not updated my website for a while, so some of the newest updates for XP POSReady are probably missing. The FullPack also does not contain any unofficial updates, just the official ones. It should still be more than enough though to serve as a basis for a fully updated Windows 2000 system. Judging from the screenshot, you seem to have everything unpacked and ready to go. By "unchanged Windows source" I mean the contents of your clean Windows 2000 CD (or ISO) which have not been modified by programs such as HFSLIP, nLite, or any others. You need to copy all the files from your Windows CD to the SOURCE folder. Then just right click on the "HFSLIP-1.0.2.cmd" and run it as Administrator. Do not use the computer while the script is running.

Just for the record, the riched20.dll included in the USP 5.1 is old. The newest official version of this file is riched20.dll 5.30.23.1231 from KB953024.

I am sorry but I do not really understand the question . The link seems to only show information of a user who is currently logged in to MEGA. Could you include a screenshot to make the question clearer? Judging by the quoted size alone, I am guessing that you may be asking about the size of my whole Archive which is indeed ~30 GB. Please keep in mind that it includes updates for both Windows 2000 and XP, and also SP3 for Windows Server 2003 which is ~7.5 GB alone.

There were still several APIs missing when I was testing it for the last time a few years ago. I cannot say for now though, with the newest version of the @blackwingcat's kernel. The installation then was partially functional. Some programs requiring it worked fine, some others did not. Of course, the official installer has never worked in Windows 2000, so you need to use my unofficial combined .NET installation package instead.

Download HFSLIP2000-FullPack-2000-ENU.7z and unpack it. Make sure that the path is not too long, so I would suggest something like "d:\hfslip". Run HFSLIP2000-1.0.2.CMD once. Several folders will be created automatically. Copy your unmodified Windows 2000 source to the SOURCE folder. Make sure to unpack everything in case it is an ISO file. Run HFSLIP2000-1.0.2.CMD again. Make sure to use "Run as Administrator" when using newer versions of Windows. Do not use the computer while HFSLIP is processing the files. The reason is that HFSLIP will keep stealing focus when unpacking the updates, so you can actually interrupt the process by mistake when trying to type on the keyboard, etc. An ISO file of the updated Windows source will be created in the HFSLIP folder. You should test it in a virtual machine, e.g. VirtualBox to make sure that it works correctly.

It does seem to work again! Thank you for checking .

@dencorso I was eventually going to update the broken URLs, but the https://hotfixv4.trafficmanager.net seems dead as for today. I am also unable to receive emails for any of the requested hotfixes. Is the MS hotfix hosting infrastructure finally gone?

That is an option, but, judging by the country flag, I suspected that @Radovan might perhaps be using a Czech version of Windows 2000, and the FullPack is available only in English.

It does not exist, hence the "WIP" or "work in progress" tag in the title. Please use my website http://windowsarchives.com/ for the latest list of official updates and hotfixes and use them with HFSLIP2000 to create a fully updated Windows 2000 installation ISO. If this is your first time, make sure to prepare yourself mentally and have a cup of strong coffee as right now there are almost 400 different files to download and categorise into different HFSLIP folders .

I would agree that installing additional components such as WMP 9 or DirectX 9 may not be necessary (and could potentially be omitted if you want a system with smaller footprint). However, the vast majority of updates and hotfixes listed on my website are simply security fixes. They do not add "bloat" to the OS, but rather just replace old/insecure/buggy versions of the already existing files. I personally recommend slipstreaming everything possible just for the sake of simplicity and to avoid any possibility that some system components will be left not updated. If you know what you are doing and want to cherrypick specific components or updates, there is nothing wrong with that. I used to do it in the past, but now I just tend to install the OS as it is, and then disable what I do not need. I did once manage to play with HFSLIP/nLite and shrink my Windows 2000 installation (fully updated, that is) to use very little disk space and less than 20 MB of RAM, but the system was basically only "for show" and not really usable . Yeah, UURollup is based on old versions of BWC kernel/core, and as such it is quite outdated at this point. It does include additional files which are not present in the BWC packages (e.g. new fonts, etc.), but these are not really required for a functional Windows 2000 system.

Please post a link to the specific USB driver. I will try to have to a look at it in my free time. HFSLIP can indeed slipstream drivers, but the documentation is lacking. You will also have to make sure that the driver works in vanilla Windows 2000. If it requires the Extended Kernel, then the whole task will be much more problematic.

K10stat but it is only for older AMD CPUs. You may need something different depending on your CPU family.

Does the app have to be on the Play Store? I personally try to use open source apps whenever possible and/or also lightweight apps. As such, the majority of them come from F-Droid, directly from GitHub / GitLab, and from the Play Store or other sources only if there is no alternative. While it is not always the case, the vast majority of the open source apps are free and also ad-free. For a text editor, I use MiXplorer which is a simple but advanced file manager with text / code editing functionality. It is not available on the Play Store though, so you would have to download it either from XDA or other source like APKMirror. It is also not open source, but I have not been able to find any viable alternative to it. The text editors available on F-Droid are either extremely barebone and/or buggy, and the ones on the Play Store are ridden with ads.