Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



tomasz86

Member
  • Content count

    2,722
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    5

tomasz86 last won the day on December 11

tomasz86 had the most liked content!

Community Reputation

73 Excellent

About tomasz86

  • Rank
    windowsarchives.com
  • Birthday 05/10/1986

Contact Methods

  • Website URL
    http://windowsarchives.com

Profile Information

  • OS
    Windows 2000 Professional
  • Country
  1. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    Oops, I meant the FullPack not being mentioned on the site. The HFSLIP2000 script itself is, of course, the core component of the whole Updates List project . I have actually been moving / rewriting the whole HFSLIP how-to to my site for the last few weeks, and hope to finish it soon.
  2. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    But UURollup was just a compilation of BlackWingCat's files plus several other XP/2003 files, fonts, etc. Hence the name "Unofficial Updates Rollup". It was never a replacement for the whole HFSLIP updates list! I think you may be thinking of the unofficial Update Rollup 2 which was indeed a compilation of the official M$ updates and hotfixes released between 2005-2010. The problem is that the package ended up buggy and there was no easy way to rebuild it as I had added all the updates manually, one by one. It was also not multilanguage and thus, all in all, inferior to the standard HFSLIP procedure of slipstreaming all the single updates. I may indeed have to add such an explanatory note about the obsolete updates to prevent further confusion though. As I said above, UURollup in its core was basically a compilation of the BlackWingCat's Extended Core and Kernel. It has no real advantage to the original packages, especially now, as the Extended Kernel has received a lot of updates in the meantime.
  3. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    I do not recommend using UURollup anymore. It is old and outdated now. The BlackWingCat's extended Core and extended Kernel are the modern solution for extending Windows 2000's capabilities. Mixing UURollup with them may work but I would not do it. UURollup will install old versions of the BlackWingCat's files, so you can never be sure what the result will be. Nevertheless, you can still find the old UURollup files in the depths of my Download Archive, if you really want to . As for the other (official) updates, I recommend following my Updates Lists under http://windowsarchives.com/updates/. The only way to use all of them though is to slipstream everything with HFSLIP2000 and then install the OS from scratch. After that you can just install the BlackWingCat's packages manually. Well, I must somewhat agree with what you are saying (although reluctantly ). Especially in the beginning, I used to start a lot of small projects that ended up being scattered here and there (and thus difficult to manage). In my defence though, I can say that since around 2014 I have been trying to keep everything as concentrated and concised as possible. Correct me if I am wrong, but during the last 3 years the only major "reorganizations" were the forced domain change (which naturally broke all the old links) and the move to MEGA as the main file hosting (caused by the lack of space on Google Drive). I did discontinue and remove many old files with time because, well, most of them were just that, i.e. old, outdated, and obsolete. At the moment there are really only two places where I am active, which are http://windowsarchives.com for all information and updates, and this very thread for other news and discussion. The only two unofficial projects that are still alive and not mentioned on my website are the combined .NET Framework installer (too experimental) and the HFSLIP2000 FullPack package (somewhat risky...). I am also aware that there is lack of proper how-to and I have been working on it. It is a one-man job though, so please understand . I am always open to feedback and suggestions on how to improve the current state of things.
  4. Integrate Unoffcial ExKernel?

    Well, but that was UURollup. I had to do a lot of manual editing in order to make everything work like that. The BWC kernel uses a customised installer, so first of all everything has to be repacked. Next, there are many registry entries that HFSLIP will simply not add automatically, so the files have to be edited specifically with HFSLIP in mind (which I did then). In addition, everything has to be re-checked each time there is an update to the kernel. That is why I said "theoretically". There are, of course, many benefits of slipstreaming the kernel, such as the ability to slipstream new AHCI/RAID drivers or direct .NET Framework 3.5/4.0 integration, but all in all it was just too much hassle . I think that the only reliable way of integration would be to create some kind of a script/program that would repack the kernel automatically so that it could be added to HFSLIP directly. An alternate method would be to make HFSLIP itself support the kernel out of the box. HFSLIP even now has hardcoded many specific updates that are processed separately, such as the Update Rollup 1 or the USP 5.1 so it is indeed possible. Everything would require a lot of time and testing though.
  5. Integrate Unoffcial ExKernel?

    If you mean the @blackwingcat's Extended Kernel, then there is no official way to integrate it directly to the Windows 2000 source. You could theoretically use HFSLIP but you would first have to repack and modify the whole package to make it compatible with it.
  6. Steam on Windows 2000

    Just for the record, technically you are not skipping the Update Rollup 1 because the rollup is already integrated in the USP 5. Update Rollup 1 basically provides a baseline for all the updates released later. It should not cause any such issues in normal circumstances.
  7. List of Working Web Browsers on Windows 2000 & NT4

    From what I found out a few years ago (cannot quote any sources, unfortunately), Google Chrome was originally supposed to support Windows 2000 and above but ended up supporting only Windows XP and later. This is why Windows 2000 was and still may be mentioned in some places in the code (like in case of such errors). The browser itself has never worked in vanilla Windows 2000.
  8. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    I have finally pushed a small update to my site and the Updates List for Windows 2000. I have added the IPv6 update mentioned by @Anixx and have also removed one old update that I found out to be obsolete. I have also been doing a lot of internal testings to check what files are exactly added by each update / hotfix in order to list them on the site later. I have also been working on the HFSLIP 2000 script a lot. I was actually motivated by the @bphlpt's comments and have started to rewrite many parts of the code. It takes time though so do not expect any quick updates in this field in the near future. You can follow the progress on GitHub.
  9. Windows XP - Deepest Impressions

    Just for the record, I do use all the different versions of Windows, starting from Windows 2000 to Windows 10 . When it comes to the NT 5.x line, I have always preferred Windows 2000 to Windows XP. Windows 2003 also is/was cool, but being a server OS it was unavailable to normal users. I had also experienced some weirds quircks when trying to install printers in it (that otherwise worked fine in 2000/XP). As for the NT 6.x line, I like Windows 7 but have also always liked Windows 8 (especially on a tablet / hybrid device). I rather dislike Windows 10 for three reasons: 1) constant feature updates resulting in buggy and unstable experience, 2) privacy issues, and 3) the overall "dark" look. At the moment the last one is actually the most important for me as both the bugs are liveable with and the privacy related settings can mostly be blocked. However, the overall theme and especially the black taskbar right in my face from the very beginning is something that I just cannot bare with. The only way I feel comfortable in Windows 10 is to use my custom high contrast theme that makes the OS look similar to Windows Classic (but many programs have issues with high contrast themes, unfortunately). I still do not understand why it is so difficult for M$ to let the users change the OS colours as you could in all versions of Windows up to 7 (Windows 8 had this problem too but at least the overall look was light, not dark).
  10. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    To Windows 2000? That is unfortunately not possible Unless new development has taken place in the last few months which I do not know about, the maximum you can get is IE6 SP1 with several IE6 SP3 files (already included in my updates list) and WMP10, but the later requires the BWC kernel and is itself non-slipstreamable.
  11. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    I will think about although the Archive at this point is still not static, i.e. I have been adding files to it (new updates, XP updates, etc.) and removing others. I do submit the site to the Wayback Machine manually each time I have done a major update so they should have already archived most of the files listed there.
  12. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    While I did manage to find the original direct URLs to the MSI files, they are useless, as they have not been archived by the Wayback Machine. The files themselves are indeed available to download from other sources, but I doubt that it will be possible to find all the language versions, so at this point I am kind of skeptical about including it. Not yet. The changes are still in the testing phase. What I have managed to do though is to upload the whole HFSLIP2000 script to GitHub! https://github.com/tomasz1986/HFSLIP2000 I have re-done all changes one by one, starting from the original HFSLIP, so that everything is properly documented. They may not be 100% in sync with the currently available HFSLIP2000 script as in the process I have found better / more proper ways to do certain things, but they should still be identical in terms of functionality. What took the longest in the original HFSLIP was unpacking and processing of the type 1 (HF1) updates. I was thinking about how to speed things up and came up with a solution where all the updates are unpacked simultaneously first and only processed later. The only disadvantages are that the unpacked updates require more disk space than when they are unpacked one by one, and that the CPU may be bogged down for a few seconds until the unpacking is finished. The speed benefits are instantly visible though. The specific commit is https://github.com/tomasz1986/HFSLIP2000/commit/b7d6a062085105a957491eb80144ff12cf88a3f6 so feel free to have a look if you are interested. Due to importance of the changes, the upcoming version of HFSLIP 2000 will be called 1.1.0. I am all for it . I have always worried that everything would be lost if something happened to me or the files. It is always nice to have multiple backups. Once M$ finally removes everything from their servers, I doubt there will be any other place to download them (in the whole Internet).
  13. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    Unfortunately it is not compatible with Windows 2000. Firstly, the installer and the executable themselves are blocked from running in the OS. Secondly, although the executable does run when forced to start in XP compatibility mode, the UI is somewhat broken. Specifically, the default theme is broken and, what is more important, the drop-down menus do not display correctly and you have to use a keyboard to navigate through them. In this state I would be against adding it. On a side note, there might have been no visible changes on my site, but I have in fact been working on several improvements lately. I realised that the majority of the KB Article URLs were no longer working, so I have changed all of them to go through the Wayback Machine. Even though some of them do still function, I have decided that it would be too much work to keep checking them individually whether a particular link is still working or not. It may be slower to get to the sites, but at least all of them should be accessible now. I am also working on listing files installed by each update, as I removed the old, inaccurate list some time ago. This time I am not even looking at the information provided by M$. I am checking everything myself with HFSLIP which is time consuming because each update has to be checked separately in order to know for sure what it changes. The lists of files provided by HFSLIP for each slipstreamed update is useless as the updates processed later may (and often do) replace the previously slipstreamed files. In the process I have actually managed to speed HFSLIP up by ~30% (from 17 to 11 minutes) by changing the slipstream related code.
  14. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    No problem . There are some other packages in that archive which you will likely not find anywhere else (like WIC). I should probably tidy it up a little bit to remove everything obsolete and leave only the stuff that is still viable. For now I have just removed all old daily and weekly releases of the .NET Framework and UURollup so that only last three are left. The other reason to do so was to free some space up. That is why I am also thinking of using 7-Zip to pack all the official updates by folder (so that the folder "180410" becomes "180410.7z") so that you would be downloading all language versions of each update in one package. This would also help preserve the original time stamps just in case something goes wrong and their get modified / reset. From my calculation it would be possible to gain around 2.5 GB this way, despite the fact that the original packages themselves are already packed with SFXCAB. These are still only plans so everyone interested please let me know if you have any objections.
  15. Unofficial SP 5.2 for Microsoft Windows 2000 (WIP)

    On the website, no. There was a package in the Download Archive but I removed all unofficial packages from there during the last cleanup as for now I just want to keep the Archive synchronized as much as possible with the site content only. Also, there are too many outdated files there that are simply dangerous to use for people who have no idea what is what. However, I have just reuploaded the files to a different folder in MEGA which you can access under https://mega.nz/#F!SlACALYL!9eek__QpDtB4CIqLR_hUDQ. I am not going to put this link on the site, but maybe I will add it to the first post in this thread later. You can find there the latest compilation of the combined .NET Framework installer. It covers all versions from 1.0 to 4.0 and can be installed like any other Windows update. The installer is from December last year so it may be missing a few security fixes. Of course, it requires the BWC kernel, both to install and to work later. For the record, the XP addon can actually be installed manually (from a command line) but it itself is not compatible with Windows 2000. That is why in my combined installer I had to modify several parts of the installation process to make it compatible with the OS.
×