Jump to content
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. ×


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

  • Country

    United States

Jakob99 last won the day on October 5 2021

Jakob99 had the most liked content!

About Jakob99

Contact Methods

  • Website URL

Profile Information

  • OS
    Vista Ultimate x64

Recent Profile Visitors

1,556 profile views

Jakob99's Achievements



  1. I know this is old, but since it's my thread, I should be fine. Anywho, I finally figured this out. Not with the Acer Aspire E1-531 (I broke that the week of USA Memorial Day), but with a Dell Latitude E6530 with Ivy Bridge that I acquired 4th of July week. Regardless of what I have, it should work with Sandy Bridge too. If you are interested in running Windows 2000 on Sandy/Ivy Bridge, you can learn how to do so here: http://windowsenthusiasts1.epizy.com/
  2. I found what appears to be Beta source code for the RTL8811CU USB WiFi device. I uploaded this here: https://www.mediafire.com/file/cucirhe1k86z19b/BETA_V9_RTLWlan_1930.16.1213.2016_Source.zip/file Maybe this can be leveraged to create a Windows 2000 compatible driver if modifying the INF won't work. I wonder if @blackwingcat can figure something out either by getting the INF file to work or by utilizing this Beta driver source code.
  3. I'll try that, but I'm not holding out hope. Here's a quote from blackwingcat, which indicates more stuff besides the OS string would need to be modified. "In other words, the following OEM hardware can be used with Win2000 by rewriting INF and erasing ".NTx86". I think "
  4. I did not. I did find this https://blog-livedoor-jp.translate.goog/blackwingcat/archives/2004917.html?_x_tr_sch=http&_x_tr_sl=ja&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=sc where blackwingcat investigated it and said rewriting the INF would work, but so far I have not been able to find any more articles in relation to this. In case the translation link doesn't work: http://blog.livedoor.jp/blackwingcat/archives/2004917.html Just open up Google Translate from the Google page, select Detect Language and paste the link in the first box and then your desired language for the second box. Click the link in the second box to open it up in your language.
  5. Does anyone know how I can get the RTL8811CU or RTL190CT Realtek USB Wi-Fi to work with Windows 2000? The description on Amazon and eBay said it supports 2000 (and 98 for the latter), but I can only find XP and later drivers. Maybe @blackwingcat has some solutions? I'll advanced Google search his site in case there is something already there. Any help is greatly appreciated!
  6. Just to let anyone know who is using a driver updater such as Driver Booster while osver.ini is in the Windows folder. When that file is present in the Windows folder, the driver updater will try to update your Vista drivers to the Windows 7 version. With this, it is better to update after getting Internet driver but before installing Extended Kernel and osver.ini. While you can continue on with the installation, most of the drivers will error out in Device Manager, forcing you to roll back. If your driver updater prompts you to update the drivers to the 7 version, just ignore that and all future updates to that device as it currently will not work. It is thanks to Driver Booster thinking the 7 drivers would work that I ended up with a partially broken Intel Control Panel. Please do note that this white and blue control panel only appears if installing Intel HD 4000 Graphics on Windows 7 and later. Windows Vista and earlier get the black, transparent control panel (called Extreme Graphics) unless you have osver.ini and your driver updater installs the 7 driver.
  7. I have made a more complete version of this guide. While the initial guide is a copy n' paste of what I posted here, there are two more guides which are linked to at the bottom of the initial guide in a See also section. Those guides are essential if you want working USB 2.0 and Intel HD Graphics. Everything you need to download/setup has been linked to from within the guide. If there are any issues with any of the links, please let me know and I will see if archive.org has the file archived and swap that in. Here's where you can find the guides: http://windowsenthusiasts1.epizy.com/Windows2000SandyBridge.html
  8. Alright, so everything that I asked about here has been fixed. 1. blackwingcat has a modded ACPI.sys that you need to integrate into DRIVER.CAB as well as drop it into the folder where DRIVER.CAB is, with it named ACPI.sy_. 2. USB 2.0 ports can be fixed by updating. There are ISO's out there with the updates. Google Windows 2000 Extended Kernel Tutorial and a YouTube Video should have one. 3. blackwingcat's custom made Intel HD Graphics can be made to work by manually updating ACPI MultiProcessor PC within Device Manager under the Computer tab. 4. Rather than post everything I did to get everything working, I will simply link to my website which has everything you need to get a successful Sandy/Ivy Bridge Windows 2000 installation. At the bottom of the page I linked to will be a See also section with two links that take you to the USB 2.0 solution as well as the Intel HD Graphics solution. I hope these tutorials are able to help other lost people out. http://windowsenthusiasts1.epizy.com/Windows2000SandyBridge.html
  9. Interesting. If we can get the 6519 HAL ported over, then maybe it will be easier to get 7 drivers working. Not sure if the HAL has anything to do with driver compatibility, but it may.
  10. That might actually be a good starting point! Compare the hal files and see how we can implement them into Vista's hal. Build 6519 might also be the first 7 build to accept pure 7 drivers, at least I think so as I tried a 7 build earlier than that, and from what I tested, it appeared to not accept the 7 drivers (and this was either on a 2015 HP or a 2019 Acer, I can't remember).
  11. This thread has been branched off from the Extended Kernel thread as to not bog that one down. For discussion about the Extended Kernel, go here: Anyways, it is widely known that installing Windows Vista on Intel Haswell and later causes bugs to appear. These can range from many things such as "The Interactive logon process has failed" error message after the startup orb is shown to several services not starting and requiring a restart, sometimes several, in order to get them working (there is no way to start these manually from within Windows). Also, several other errors may occur within Windows itself. These include User Account Controls not showing up and instead throwing an error (redoing what prompted the UAC will get it to pop up normally) to many other errors. If one takes a look at 6003.20489.vistasp2_ldr_escrow.190320-1700, it will show that the problems that plague Haswell and later are fixed by way of new HAL driver, however, this is only partially true. While I did get less errors in relation to the Haswell+ issues, I still got errors such as the aforementioned user account controls error. So, if we want a chance at even getting these issues fixed once and for all, it will probably be worth it to investigate the HAL.dll as BetaWiki claims a new version of this fixed the issues. Even if we get the issues fixed (which should definitely happen down the road), there is still the issue of getting most drivers (most of which are 7+) working, although after getting Realtek Ethernet working, I ran Driver Booster and it found a fair chunk of driver, including SATA drivers, shockingly. Intel graphics obviously do not work, although you "might" be able to work the XP Haswell drivers.
  12. Yeah. i tried it on my lone Haswell board and didn't get any errors upon starting, but after using it for a little bit, I noticed errors. Instead of derailing this thread, I will create a new thread related to the Haswell and later issues and link to it here once it is up. EDIT: Here it is:
  13. It may be possible with osver.ini, but I think more functions would be needed. If, somehow, it installs with osver.ini, it would be broken. Using that, DriverBooster updated my Intel HD 4000 graphics driver to the Windows 7 one (from 2016 and contains the blue and white Intel control panel used in 7 and later as opposed to blue and black used in Vista and XP), but it was broken so I had to roll it back.
  14. I experienced this too after trying to multi-boot Vista, 7, and 11 on my Dell Latitude E6530. Glad I'm not the only one. At first, I just chalked it up due to the hardware being unsupported and possibly the fact that Windows 11's UEFI may mess up Vista's UEFI I should note booting into Windows 7 worked just fine!

  • Create New...