• Content count

  • Joined

  • Last visited

  • Days Won


tomasz86 last won the day on November 12 2016

tomasz86 had the most liked content!

Community Reputation

60 Excellent

1 Follower

About tomasz86

  • Rank
  • Birthday 05/10/1986

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 2000 Professional
  • Country
  2. Nothing has changed concerning the .tk domain so I have removed the redirection. You can access the site again under
  3. My site may not be working in the next few days. I have received an e-mail from Freenom who is responsible for the .tk domain. It just seems like a generic e-mail they send to everyone whose domain is not accessible at the moment (which is true as I removed the redirection). The important thing though is that they said they would re-check the domain again "in a few days" and cancel it if it is still not working. I do not have much hope as the status is still "suspended" but just in case I have added the redirection again so that everything is correct, at least on my side... Let us see what happens. If there is no further information from them I will just remove the redirection again (so that the Github address will work). If you want to view my site right now, you can always use
  4. My website has been offline for a few days because the domain was apparently suspended with no further explanation. My guess would be that someone did not like all the non-direct links to MS updated that I had to add in the last few months (since the original URLs were no longer working). I am still unsure what to do next as the original domain is probably lost for ever. For the time being you can access my website under
  5. UURollup does install files from newer versions of Windows . I was referring strictly to the original USP 5.1 which was limited to original and unedited files provided by Microsoft. The xpsp4res.dll comes from XP updates released after SP3. However, I would suggest not to use UURollup at this point in time because it is outdated. It is better just to stick to the kernel and core extensions created by BlackWingCat. Both UURollup and the BWC kernel require a fully updated Windows 2000 system though (which basically translates into having all the updates listed on my website installed).
  6. USP 5.1 by Gurgelmeyer is just a compilation of official updates and hotfixes for Windows 2000 released by M$ up to mid-2006. It does not contain any unofficial / modified files or any files from other Windows versions whatsoever.
  7. OnePiece updated his .NET 3.x and 4.x addons so I have updated my package too! You can find the newest version in the Archive. I have also renamed the folder to "dotNETFramework" as MEGA would not recognize a folder with a dot in the beginning of its name. The QFE files are still not included yet. And just a quick reminder for those who may be confused - this combined .NET Framework installer requires the BlackWingCat's kernel (or UURollup but I would not suggest using it now) to work. The newer .NET Frameworks do not work in vanilla Windows 2000.
  8. I have added a new version of the .NET Framework combined installer to the Windows2000\USP5\.NETFramework folder in the Download Archive. The filename is "20161211_NETFX101120303540.7z". This is the next-to-last version since the old versions of .NET Framework went EOL in January this year. The last step will be adding the QFE files for .NET 3.x.
  9. It is included in Windows2000-KB891861-v2.reg.
  10. It was replaced by KB961501 (first reported by acus back in 2012). The info is actually present in the old changelog that is not on the site right now. I still need to reformat it to match the new style and then re-add everything...
  11. The log file is created in the HFSLIP folder each time you run the script. Mine looks like this: The SP4 is included in the FullPack so it should not matter. Using nLite may cause issues though, especially when used after HFSLIP. An ISO file is automatically created when using the FullPack so if possible try to use that to install the system. This way we will see if nLite is the culprit or not. WINNT.SIF is used for automated installation. I have mine set up so that the whole process is 100% automatic. This is especially handy for testing the ISO in VirtualBox. Basic information: Detailed information: Here you can check mine (without the serial key): Be careful! Using this file as it is will remove all existing partitions from the drive! Also, I have used this file for Windows 2000 Server and Windows XP too so not all sections / entries are relevant to 2000 Pro. Those are ignored during the setup process anyway.
  12. As always, thanks a lot for testing and all the kind words. To tell the truth, I have not really tested slipstreaming drivers for a very long time. I have not experienced any issues with the stock ones though. I will need to have a look at your HFSLIP log file. Can you upload it here? Also, is your Windows source modified in any way? Have you used any other tools than HFSLIP to modify it? I always test my HFSLIP packages before uploading with a clean copy of Windows 2000 Professional with SP4 pre-integrated. I only add my WINNT.SIF, run the HFSLIP script and then test the ISO file in VirtualBox.
  13. A big update today! 1. Many new updates added (mostly from XP POSReady but not only). 2. HFSLIP 2000 updated (check the changelog in the ZIP archive). 3. HFSLIP2000-FullPack also updated accordingly with the new updates and the updated HFSLIP 2000 script. Check the changelog on for all the details, and please let me know if you find any issues with the new updates.
  14. I have just updated my website. The Archive now links to Google Drive instead of Dropbox. I have also fixed several broken URLs (thanks @MattRoot1616). Please let me know if there any other issues with the site!
  15. I am not sure if creating a new topic was a good idea because the combined .NET installer is discussed and available only through the main USP 5.2 thread. Anyhow, my guess would be that you have not installed either UURollup or the BlackWingCat's kernel. The .NET Framework 3.5 and 4.0 files require the kernel extension to run. I would suggest to install the newest version of BWC kernel (and other BWC kernel related packages) and then reinstall the .NET package. On a side note, there is also a possibility that not all .NET dependant applications will work, regardless of the kernel, but you should still try first.