LightAlpha263

Or, quite literally: https://www.godaddy.com/domains/searchresults.aspx?checkAvail=1&tmskey=&domainToCheck=windows2000tk The same domain plus .com doesn't sound that bad.

Checking in again; is this project dead? I am starting to wonder since it has been about a month since I checked in, and yet no replies. I'll check back again later, just hopefully I may get an answer by asking now.

Hey, I just wanted to check up on things after awhile. Sorry to hear what has happened with the .tk domain, I hope things are resolved soon. In addition, when I recently took a vacation with my old laptop with Windows 2000 plus several modifications including the UUR, it was great, a good way to get a bit away from technology while of course having it in case. Fun fact: My school still had XP PCs until 2013 or so. Now we're all on 7.

I am now aware of it existing, and I see how it basically serves the function of what I desire to make with this package. I will not entirely rule out getting back into finishing this project because I want to make a package that will serve as working to incorporate unofficial packages after Windows 7 becomes unsupported and to allow users to either use the software itself or use it as an update repository. I wish the person making WSUS Offline Update good luck in making his software, but I hope that I will be able to finish mine as well if I soon get back into finishing it.

I apologize for inactivity. I haven't worked on the project in months and there's a bad reason why. Even after saying "Oh I'll use this method to install the updates", I can't figure out the very best way to install all the updates while making it easy to uninstall them all too. I can confirm that the parts of the scripts where the user can select which categories of updates are installed work. The parts that haven't been made is the part where the central script (a batch script) launches each individual update script for each update category. The part where the central script launches these scripts does exist. However, the individual update scripts do not have any code in them other to echo something like "not done". So, why? I already said. I can't figure out how to make the pack easy to install and uninstall. I have two ideas. Either I have an uninstaller which literally uninstalls each update that was added if it was installed, or if I do use DISM to install the update just accept the fact that the updates are non-uninstallable. I'm again sorry for the inactivity on this project and I will get back to it sooner or later, but due to a very busied life, I haven't been able to. Just in case, expect a few more updates coming soon.

Not true. Firefox ESR is a version of Firefox that is older in functionality but receives updates. It is an official version of Firefox, and is meant mainly for businesses who are reliant on software still working while remaining updated. Technically, that also applies to legacy systems such as Win2K Extended Kernel. Download the latest version here: https://www.mozilla.org/en-US/firefox/organizations/all/ I have it on my Windows 2000 laptop, and it works great. I also have it on my main laptop for some reason I don't get.

Great! Did you speed up the site? I have yet to check it out.

I'll have to get the drive from my router, as it is connected as NAS drive via the router (which is slow, and why I'm trying to do the W2K file server thing).

EnableBigLba is set to 0x1. I tried plugging the drive in again, but it still came up as "unreadable" in Disk Management. I'm not sure if I have to use a USB-Y cable, or if one can connect into the drive. Also, as far as I know as of now, the drive isn't a drive-sled that can be easily opened up with the HDD in there. It is the size of a typical drive-sled, and I'm looking now as to if I can maybe use the drive inside as an internal drive if I can remove the drive from the case. UPDATE: There is a way to remove the drive-sled, but this particular drive has a tedious and annoying process as it the drive is very new. I'd rather use USB if I can. What else could be causing the drive not to be recognized?

I have recently set up a file server on Windows 2000 Advanced Server. The machine is an old Dell PowerEdge from around 2003. I installed the OS initially with an official disk. I installed the drivers. I then created an slipstream disk via a (slightly) older version of the HFSLIP2000 full pack. I then 'non-destructive' (I used a slightly different method) reinstalled through that and then installed the latest UUR. All seemed well until took my primary external HDD from my router and plugged it into the server. It installed the device, but it didn't show in "My Computer". I went to Disk Management (diskmgmt.msc) and saw that the driver was "unreadable". I plugged the drive into my Windows 7 Home Premium x64 laptop and the drive worked fine. I then plugged it back into the router and it still worked. The drive did say it was only 'compatible' with versions of Windows 7 and above, though initially I thought it was that since the HDD was 5TB and Windows 2000 isn't compatible with GPT, only MBR, which I converted the drive to earlier on limiting it's space to 2TB but getting it to work with my router (which since we changed routers, it might have worked with GPT, I don't know and I don't wanna risk reconverting). So, is the drive incompatible due to a larger amount of space than Windows 2000 can handle (even with the unofficial updates)? Or is it a problem with the USB ports on the computer (I tried multiple ports, the drive is USB3 but the ports may be USB2 or hopefully not 1)? What else could it be?

The update is good, the slowness can be fixed. Perhaps try redirect links right on the site, for example, http://windows2000.tk/kb941569.html would be a an automatic redirect to http://download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/windows2000-kb941569-x86-enu_5b6495e0873468c8c65fa635992ac3e9cfd7dbd5.exe, the whole point being the redirect link would be much smaller than the direct link. Without tracking the IP/History/Personal info (like automatic redirect links usually do).

I have decided to instead use the DISM application to install updates. I will begin work on the scripts tomorrow, and I'll release a test version of the scripts for security updates only.

Really clever! This will help to archive/preserve hotfixes as I'm sure that MS will prevent older hotfixes from downloading correctly as they remove the files from their servers, but they will definitely shutdown the hotfix download system for Windows XP and earlier first before removing said files.

It is great update! I think the direct-link catalog updates are great! The site is a bit slowed down, but it can be fixed. Also, the load times aren't that bad.

I have decided what I will do. The installer will be via .msu for ease of uninstallation. It will be an installer script. I will begin writing it soon.

Welp, of course. However, if you extract the .cab files inside the .msu, can anyone merge them? Also, here's a guide to installing updates via DISM: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows. It installs .cab and .msu files, but part of this guide involves extracting the .msu file and installing via the .cab inside the .msu. If there's no way of merging these .cab files, then I'll go back to simply creating an installer script. I will decide by Tuesday.

More or less. I was looking into it the other way, as the installer itself being the rollup, but I have found ways to merge .msu files together. If these ways prove to work, then: 1. There will be a universal .msu for security with updates added to it when needed etc. 2. The installer will use wusa.exe to install each .msu. 3. The last update will be separate from the combined updates, and have a different switch to warn the user of an eminent restart. If anyone can tell me of ways to merge .msu files (so I have less searching of the internet to do), then feel welcome to tell me about it.

Hm. What I had in mind involved the older logos (which are owned by MS). Never mind, I like the update and it's great. Don't worry since the ideas I was gonna suggest are ones involving the MS ones.

I have downloaded all 64 bit updates for Windows 7 via WHDownloader. I realize there are folders for everything, but: 1. In the "Windows7-x64\Extra\WithoutKB3125574\#Security" folder, there's 103 updates, rather than the 16 in the Security Folder. 2. In the "Windows7-x64\Extra\WithoutKB3125574\#Hotfix" folder, there's 290 updates, rather than 11 in the Hotfix folder. 3. So on. I'm going to make a good assumption via the text files I've read to believe that the updates in the regular Security, Hotfix, so on folders are what you install after either: A. The convenience rollup. B. The updates in the "Extra\WithoutKB3125574" folder. If I go with B, then assume I move all the contents of the "#Security" into the "Security" folder (I'm assuming you get the point) and move the "Security" folder to the place where I have the update rollup. I hope this is correct, but I'd just like to make sure.

I'll download the updates today with WHDownloader under the assumption that it will download ALL of the updates. The previous method is not too intuitive (with my schedule) and with this last post, I'm hoping that all of the updates are going to be downloaded. I hope WHDownloader will do the trick, because I am fully relying on it now

I actually have a better idea. If I could divide the workload among several people (I download security updates, someone downloads hotfixes, so on), I could actually have the updates ready in a faster amount of time due to much of my limited free-time being spent not downloading updates but organizing them and getting the installer to install them. Anyone who would like to apply for this, PM me. -Be 100% sure you've downloaded ALL the updates for your given category. -Name the update based on its KB number when downloading and whether or not it is 32 or 64 bit. Format: KBXXXXXXX_x32, KBXXXXXXX_x64 -Divide the updates into 32-bit and 64-bit folders. -Upload a zip file of the updates (with the two folders inside) to any file-hosting service and PM me the link. -Windows 7 is still a supported OS, and so it still receives updates from Microsoft. In the zip file, include the date of the most recent update you have downloaded so I can keep downloading such updates. If you'd like to continue providing update, that would be great. If you want to, just keep updating the zip file and I'll check monthly for any updates inside it. By no means does anyone have to do this, I'm fine continuing downloading the updates by myself. It'd just be very convenient for the project. In other news: I'll keep with the catalog method for Windows security updates. I'll try to see if WHDownloader can do other kinds of updates.

The new site is great! 1. While I do think the site needed an icon update, it could've been a bit more retro yet modern. For example, a transparent box with a Windows XP logo on top of it. However, I'm fine with the new icons. They're good. 2. Try to use archive.org more than the update catalog, as we're aware of a 'site upgrade' for the catalog. I'm curious as to if someone wrote an extended kernel for Windows 2000 that emulates Windows 7, and then installed the Windows 10 free upgrade update. That'd be funny.

Alright, I'll see if WHDownloader can do the trick. I'll determine the method again this weekend.

I'll check that out, thanks! I have already tried this out, and you're not lying! My planned method of downloading the updates goes like this: 1. Go into Windows Update (on Windows 7) and checking the "Installed Updates" section. 2. Go to my Windows 2000 computer with IE6 on the Microsoft Update Catalog and typing in the KB number of that update. 3. Click "Add" for both the 32 and 64 bit versions of the update. 5. When I have to go, keep track of the last I update I downloaded in a text document and download all the updates. 6. Repeat until all updates have been downloaded. One might ask: why not download all the updates at once? I answer: after exiting IE6 because of the inevitbility that I'll have to be somewhere else, the updates aren't saved. By downloading like this, I can keep better track of the updates (such as knowing what was the last update I downloaded) and not lose a ton of updates that would've otherwise been downloaded. I will consider the WHDownloader if the method above doesn't seem to work good, since I have tested it.

So I guess I'll download the updates via a netbook on Windows 2000 (with IE6). When I was looking at the catalog, I had it with Windows 7 and IE11. If it is a joke (which I'd not be surprised), very funny joke. Funny story: Adding HTTPS sites under the trusted sites in Internet Options on IE6 loads HTTPS sites, making IE6 very fast and reliable. (Partially no joke )