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,773
  • Donations

    $0.00 
  • Joined

  • Days Won

    1

tomasz86 last won the day on July 28 2019

tomasz86 had the most liked content!

Community Reputation

97 Excellent

About tomasz86

  • Rank
    twilczynski.com/windows

Contact Methods

  • Website URL
    https://twilczynski.com/windows

Profile Information

  • OS
    Windows 2000 Professional
  • Country

Flags

  • Country Flag

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you for investigating the issue. I am actually located in South Korea right now, and the site is not working here. It does work in Tor Browser with the exit node set to Poland though. It also used to work from Korea before January 2020 with no issues. I understand that there was a problem with the ad serving, but this sounds like a very radical approach, which will likely block many users and other legitimate visitors from accessing the website . I am not sure what the "specific IP ranges" are, but when it comes to my home connection, I am using a dynamic IP from one of the largest Internet providers here, with more than 4 million registered users. The site also does not work on my mobile connection, which is from a different company, with 18 million users. All this means a very large number of people potentially impacted by the blockade, without even thinking about all the other countries affected.
  2. I cannot tell for sure, as I had only been visiting MSFN quite irregularly in the recent times, but the board was definitely still working in December 2019, because that is when I posted for the last time in https://msfn.org/board/topic/156521-unofficial-sp-52-for-microsoft-windows-2000-wip/?do=findComment&comment=1175170. I also remember reading the following post by win32 on January 28, but I do not remember whether I actually visited the forum or just received an e-mail notification and read it there. I delete all my browser history, so I cannot say any specific dates, but from my memory, I was definitely trying to visit the site two or three times sometime around February and March, and it was already not working. I just thought that the site was down all together though. Just for the record, this is what I see when trying to open MSFN from a regular browser: Ping also fails: Pinging msfn.org [151.106.17.234] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 151.106.17.234: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
  3. I am sorry for any inconveniences. In the future, I do plan to host everything on my own server (in addition to third party hostings like MEGA, etc.) just to make sure that all the data will remain always accessible .
  4. MSFN is also inaccessible from where I live. I initially thought that the website and forum were down. I have tested with my home network and also a mobile network. It does not work in both cases. Have you perhaps introduced some kind of new filters (e.g. to fight spam), which as a result block traffic from certain areas? I am writing this post using Tor Browser.
  5. Yes, the USP 5.1 installs buggy USB drivers from one of the hotfixes. Check for details. That is one of the reasons why I do not recommend using it, and rather slipstream/integrate everything separately, excluding the problematic files.
  6. Just a quick update, as I decided not to pay for the "windowsarchives.com" domain any more, and it has recently expired. The reason is that I have other things, unrelated to Windows, which I also want to share, so I would rather use and pay for just one single domain under my own name, and keep all the other things in their respective subfolders. I am sorry for the inconvenience and I hope you will understand . Anyhow, the Windows Archives website is, of course, not dead, and from now on will be available under https://twilczynski.com/windows.
  7. No, but I do not think that it is necessary. It seems to only be applicable to Windows 2000 RTM and SP1. I cannot find any specific information on the M$ website, but this site explains it well. I did manage to find an archived link to the original package, just in case: https://web.archive.org/web/20120430103429/http://www.microsoft.com/en-us/download/details.aspx?id=15667
  8. @Tommy, I am not sure when you used my packages before, but according to the changelog on my website, I removed the unofficial updates from the updates lists in 2014 . I do not remember exactly when I removed them from my FullPack, but I would guess that it was around that time too (maybe a little bit later, but still ~4 years ago). I decided not to include them, as I wanted to focus mainly on providing a stable base with all the official updates integrated, and leave the unofficial modifications to the more skilled people (who were @WildBill and @blackwingcat at the time). As for the USP 5.1, it is not included because it installs buggy USB 1.1 drivers, and also is English-only while I want to eventually provide my packages in all languages supported by Windows 2000. Also, while I do not have the hard data right now, judging from my testing in the past, I am almost 100% sure that all the updates and hotfixes included in the USP 5.1 (excluding the buggy ones) are covered by my updates list. As you said, DX 10 or even any unofficial drivers would require to have the unofficial kernel / core installed in the first place, thus I am not including any of them. While there are a few unofficial packages listed on my website, they are mainly just repackaged versions of official system components, such as the .NET Framework addons, or the additional system fonts, both of which work in stock Windows 2000. Unless I decide to include the unofficial kernel / core, or any other modified files on my website, I do not plan to include any such unofficial packages for now. If I ever change my mind, they would become a separate list, as I want to keep the main updates list stock.
  9. You can find the old Global version in https://mega.nz/#F!SlACALYL!9eek__QpDtB4CIqLR_hUDQ. Please keep in mind that it is very old, and also does not offer most of the benefits of the BWC kernel (or even the last UURollup for ENU), since most of the core system files are language specific.
  10. Unfortunately I do not have the skills to do it. In case of Windows XP, M$ has released a new version of the file termdd.sys. The file itself is OS specific, so it is impossible to use the XP file in Windows 2000. The file in our OS would have to be reverse engineered and patched accordingly to the XP file.
  11. Make sure that your drivers, and especially the graphics driver, support PAE. I do not know for now, but in the past in my testing only the NVIDIA drivers worked, while both AMD and Intel drivers did not.
  12. I asked the same question regarding Windows 2000 a few years ago, but there has been no definite answer.
  13. While true, I still think that this is a good option to do for the greater good. Right now, the links are accessible only to those logged in on the MSFN forum. If the forum goes down or something happens to the file, they may be lost forever. I myself have gathered all the POSReady updates with their respective links available in the MS Catalog from 2010 to now, but have not managed to archive the older links yet. In case of many Windows 2000 (and older) updates, some of them did actually "vanish", and we have no access to the files any more. Only the broken URLs remain. This is especially true for updates for the less popular language versions of Windows.
  14. I think that it may be beneficial to create a new topic with all the links listed directly in the post instead of a text file. This way they could be indexed by search engines, and also hopefully grabbed by the Wayback Machine while they are still functional.
  15. 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.
×
×
  • Create New...