AnX

For now it is stable in my environment, but I'd like to see a way to get those 2003 drivers to stay put.

Any way to forcefully get the server 2003 drivers to stay in xp? Every time i try to copy them over, no matter what, i cant get em to stay put, they are overwritten by the xp ones. I've flushed the dllcache, modded the .cab files, still no avail.

I'm sorry, but I simply see no use in running Windows XP on this sort of hardware. If anything you're gonna run into tons of compatibility problems. You're better off getting Windows 7 x64, and thereafter running Windows XP in a virtual machine.

I just use malwarebytes under 2000, works great.

Apart from my main rig that runs Windows 10, i have been setting up a second Win2k box with some older hardware. It's a core 2 duo e7500 with a gig of RAM and a 500gig HDD. Runs Win2k SP4 + USP5.1 + BWC's EXTKernel/Core. Runs quite great due to 2000's lightweight nature.

I happen to be the person who owned that machine on the video and ran Vista on it. Yes, by all means, you will need a dedicated card. A GT 610, like I had, is not very expensive and still works for basic tasks.

Grab the latest realtek audio driver for Windows 2000 from the realtek.com.tw website, that should do the trick.

After switching to a GeForce GTX 960, all of my headaches with the Radeon drivers are over. However, with nVidia, the latest 355.xx drivers have a bug with a file called nvwgf2umx.dll on certain games and applications. So I would reccomend sticking to 353.62 until the problem is fixed. Me and 2008WindowsVista have already reported the issue.

This has been discussed for quite a while. While I have gotten MTP drivers to work on Windows 2000, even with WMP10, I can't properly access any of my files. Is there any fix to give me proper MTP support? It won't show up in My Computer, and the Portable Media Devices section of control panel shows me files, however I cannot copy any of them over. If I do: I get this error message. Any solutions?

Thanks for the reply. I have Windows 10 on one drive (the SSD) and Win2k on the other (HDD). I use the bios to switch between booting off the 10 drive or the 2k drive. However, when i run Windows 10 for a long time and boot back into 2k, it no longer boots, and i have to manually reset the 2k drive partition from active to non active to active again in order for it to work. More recently, an install of Avast/Malware Defender seems to have botched up the 2k install more, so I'll have to repair that. For now I'm back on 10.

Windows 10 isn't a bad OS at all. But it seems that if i run it dualbooted with another OS, it simply does not work out so well. Atleast an older one (e.g. Windows 2000). Now you may be thinking that its just "because Win2k is too old" but this is still a problem that can potentially creep up on a newer OS. This does not happen with Windows 7 as the main OS. I will also inform you that Windows 10 is installed as MBR and not GPT.

First of all. Windows 2000, by itself, runs great, starts on every boot, and so forth. But, bring WIndows 10 that's installed on my SSD into the equation, and you get problems. For some reason, whenever WIndows 10 runs and "settles itself", then after you reboot into 2k, you get an inaccesible_boot_device bsod. With Windows XP and later, however, this isn't usually the case. So I want to know what's the issue? Could it be bwc's ahci driver for AMD? Or Windows 10 just not being multiboot friendly enough?

Successfully installed the NVidia GeForce GTX 960 drivers on Windows 2000. I used BWC 347.88, works great.

Update: My 260x botched out on me, and I've purchased the new GTX 960. I will be continuing my endeavor with Windows 2000, and this time we will hopefully have graphics. Lol.

Find an older driver. I use a TP-LINK driver from 2010 on Win2k and my TL-WN722N performs as well on Win2k as it does on newer OSes. I didn't even have to install unofficial updates, the adapter was ready to go as soon as i popped in the driver.

VESA driver unfortunately does not work for me.

I know that you suggest I'd go with nVidia, but for the time being, to run Windows 2000 in proper resolution, I'm requesting a catalyst driver for Windows 2000 just so I can get out of the dreaded 640x480 with 16 colors. Any help?

But I do keep on having this strange problem. Every once in a while, the OS throws an "inaccessible_boot_device" when booting up. It seems to happen when I'm on Windows 10 and run it for a while. Otherwise, it never used to throw a BSOD like that. However, hte problem goes away after a while, and if I only use Windows 2000. That's strange.

Originally, when I used the insider preview, I had tons of problems with the OS. So I decided to wait it out for the RTM. All i can say is that I'm impressed. Unlike Windows 8.1, Windows 10 hasn't given me a problem on my system. It also feels smoother overall to Windows 7, and faster too. Windows 8.1 caused quite a few problems for me. namely one annoying problem where devices would disconnect for no reason. The UI of Windows 8.1 was also not that great. However, Windows 10 comes with a very refreshing UI, that is much more desktop-friendly, and has neat features like multi-desktop. For an RTM release, Windows 10 is also rather stable, which is a great thing. Whether it was on my main machine, in a VM, or on an ASUS laptop I have, Windows 10 has not caused any issues and runs excellent. However, there are a few things that I'd like to change. By default, it would be better off for the Windows Update P2P to be disabled. I have a slow 1Mbps connection, and that can potentially cause problems. Also, the "Modern" applications running in the background would have been better if kept off. Regardless of this, the OS hasn't caused me a single problem yet. Overall, I really like this OS, and I believe it is a step in the right direction.

Alright. Found the solution. it turns out that you need to install this driver before you install UUR. I did that and now everything's fine.

Earlier I was having some snafus with Windows 2000 on this board, but now I've managed to get it sorted out (apart from the graphics, of course). What I did was simply slipstream the AMD AHCI driver from BWC into my Win2k USP5.1 install and began from there. Setup was simple and nothing went wrong. Then i installed the realtek audio, LAN and TP-Link Wireless driver. Then I installed UUR, the AMD SMBus, ASMedia SATAIII, ASMedia USB3, and the HPET driver "fix" that I posted in another thread. The GPU (AMD Radeon R7 260x) has no drivers that could function on Windows 2000. I will be replacing it with an nVidia GeForce GTX 960 (update, replaced with 960) All in all, this is a great motherboard to run Win2k on. My AMD 8 core CPU does run a few degrees warmer (3-5c), but that's been the case with most Win2k installs on multi-cores.

Looks like the problem has crept up again. When I tried to install a driver for the GPU audio, the Reaktek audio quit and i can't get it up anymore. I've tried the previous methods without any success.

Here is a fix for the HPET driver on Win2k. It was made by HP to fix the issue in server 2003, but works great under Windows 2000 too.

I have fixed the audio problem by installing thew BWC extended kernel. Now if only we had VGA...