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. ×

Jakob99

Member
  • Posts

    169
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    $0.00 
  • Country

    United States

Everything posted by Jakob99

  1. Cool! Will have to try this. Haven't been on the 2000 side of the multi-boot in a while and have been in 7 for the past couple of weeks.
  2. 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/
  3. 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.
  4. 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 "
  5. 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.
  6. 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!
  7. 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.
  8. 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
  9. 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
  10. 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.
  11. 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).
  12. 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.
  13. 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:
  14. 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.
  15. 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!
  16. I'm trying to run Bloons TD 6 Steam version. What is weird is that the game worked in the past with the Kernel and without .net framework 4.8 (it would prompt me to install it, but I could still run it), but now doesn't. I uninstalled it and tried to reinstall it, but it throws an error. I should note that the game and steam are in my osver.ini file (otherwise it will tell me there is no connection). I should note that Bloons TD 5, also from Steam works, but this game was released when Steam still supported Vista.
  17. Does anyone know if .net framework 4.8 works under Vista? If so, how do I get it working.
  18. Are we getting closer to Windows 7 driver support? I used your osver.ini file to change the version over to 6.1 (7601: Service Pack 1) and opened the AMD Radeon R4 graphics installer. It complained about difxapi.dll missing so I copied that over from a 7 install into System32. I got the installer to open, but it told me that my operating system is not supported (even though I spoofed the version to be 6.1 7601). Installing through Have Disk produces a code 39. I did however get Elantech Touchpad drivers working under Vista. The version I have is 11.6.2.1 and unless they still support Vista, I got a Windows 7+ driver working. Installing Qualcomm Atheros QCA9335 or whatever the Qualcomm driver the Acer Aspire A315-21 uses does not appear to work. Using Have Disk tells me it is unsupported.
  19. osver.ini can be a pickle to work with. I used it and upon restart, the theme was a mashup of Aero and Windows Classic, explorer windows were slow to open, and a slew of other things happened. Once I was able to move the file out of C:\Windows and to the desktop and restarted, I was fine. Here's the contents of my file if I did anything wrong. [C:\Users\Jakob\Downloads\Firefox Setup 94.0.exe] Enabled=1 FirefoxFix=1 [global] Win7SuperVerFix=1 FirefoxFix=1 MajorVersion=6 MinorVersion=1 BuildNumber=6003 ;CSDVersion= PlatformID=0
  20. Unless I configured it incorrectly, it did not. Launching the AMD installer threw an error complaining that it could not find a dll. Using Have Disk to install it caused a Code 39.
  21. I got the new October 2021 update up and running on my main Vista rig, and it works like a charm so far! No errors and Windows 7's Wordpad works like a charm! Also, for those who do not know/remember where Wordpad is stored, it is stored here: C:\Program Files\Windows NT\Accessories. Also note it is also stored at C:\Program Files (x86)\Windows NT\Accessories though you don't have to do anything with these files. If you open this wordpad, you get the classic wordpad, while opening the one in Program Files nets you the 7 wordpad as long as you have the files copied over. Also, any progress on Win7+ drivers? Perhaps if we can lend a hand, we can narrow down the issues that currently prevent Win7+ drivers from working and get them one step closer to working. I also believe a modified ACPI.SYS a la blackwingcat's Windows 2000 one might be needed for hardware if people get the "This BIOS is not ACPI compliant" 0x0A5 BSOD when attempting to install Vista on newer hardware. This obviously has to be slipstreamed into the install media, but not with vLite. Instead, you will have to extract the ISO with 7zip, search for the original ACPI.SYS and swap it with the new one (if it reads ACPI.SY_, drag the file to MakeCab in System32 and it will spit out a new ACPI.SY_ wherever the .SYS file was dragged from) and then if it is like 2000, there will be a DRIVERS.CAB that will have to be extracted, the new ACPI.SYS moved in with the rest of the files, the cab rebuilt with Administrator Command Prompt, and then put back into the appropriate folder in the installation media. EDIT: I swapped out the wordpad files within the Program Files (x86) folder with the Windows 7 fwordpad files from that same folder, but I got an errod stating GetGestureInfo could not be found in the dynamic link library USER32.dll. This is not important for Windows 7's wordpad to function as the files for that is within the Program Files folder, and I have it working successfully.
  22. Does anyone know how to get Windows XP drivers working on Windows 2000? I have heard from several people, blackwingcat included that these should work with the Extended Kernel and Extended Core, but I have had no luck getting any of them to work on my Dell Latitude E6530, even blackwingcat's custom made Intel HD 4000 graphics driver (If I run setup.exe, I get The procedure entry point GetSystemWow64DirectoryW could not be located in the dynamic link library KERNEL32.dl. If I use Device Manager to install the .inf, I get a code 31 upon restart). Does anyone know how to get the Intel HD 4000 graphics driver working along with other Windows XP drivers? To set it up, I used the tutorial embedded below along with the ISO he provided in the description (I did not do anything with the second link below the ISO, which just takes me to a place to integrate all the updates, which appears to not be needed with his Windows 2000 2011 ISO) to setup Windows 2000 as well as the Extended Kernel and Extended Core. Thanks in advanced for your help! I should also note that I got USB working on this machine, so I can do a USB wi-fi/ethernet dongle if needed to further update the machine.
  23. This guide will teach you how to install Windows 2000 to Intel Sandy Bridge or later platforms with working ACPI and SATA drivers. Here's what you will need: A separate laptop with 7 or later (Not sure about 7, but I do know 8.1 and later will for sure work). nlite: https://www.nliteos.com/download/nLite-1.4.9.3.setup.exe IMGBURN or your favorite CD/DVD image burning software. SATA drivers: http://win2k.org/cgi-bin/dl.cgi?file=iata76_cd2ka.zip Modded ACPI.SYS: http://win2k.org/cgi-bin/dl.cgi?file=acpi.cab Latest 64bit Linux burned to USB with Rufus in Legacy mode. Run as administrator command prompt (Open start menu, type CMD, right click, and click Run as Administrator) MakeCab.exe (in the C:\Windows\System32 directory). Cabarc.exe: https://www.mediafire.com/file/07aylmvglqm6k5h/cabarc.exe/file Windows 2000 ISO extracted to folder named Windows 2000 on the Desktop using 7zip A USB separate from the Linux USB with blackwingcat's modded ACPI.SYS stored on it (more on why this is necessary later). 1. Setup nlite, your favorite DVD burning software (such as IMGBURN), and 7zip (if you don't already have it). 2. Download the SATA driver and ACPI.CAB files linked to above and move the cab files to the desktop. Also download the Cabarc file I linked to above and place that on the desktop as well. Also locate MakeCab.exe as well. This is in the C:\Windows\System32 directory already so no installation is needed. 3. Next, we have to extract the SATA and ACPI cab files. Run this command (If you put the files where I told you to, you can just simply copy and paste this command, changing YourUserNameHere with your Windows account name) in an Administrator command prompt (Make sure you create a folder named iata76_cd2kh on the desktop): expand -F:* \Users\YourUserNameHere\Desktop\iata76_cd2kh.cab \Users\YourUserNameHere\Desktop\iata76_cd2kh (for the SATA) expand -F:* \Users\YourUserNameHere\Desktop\acpi.cab \Users\YourUserNameHere\Desktop\ (for ACPI). Once the commands complete, the SATA drivers should be in the aforementioned folder and the ACPI.SYS file should be on the desktop. 4. Navigate to MakeCab.exe and drag acpi.sys to it. This will create acpi.sy_. Rename it to ACPI.SY_. 5. If you haven't already, extract your Windows 2000 ISO to a folder on the desktop named Windows 2000. 6. Navigate to the i386 directory and find the original ACPI.SY_ file. Delete this and copy the modded ACPI.SY_ in. Next up, find the DRIVER.CAB file and move it to the desktop. Create a folder named DRIVER and then using an admin command prompt, run this command to extract the files: expand -F:* \Users\YourUserNameHere\Desktop\DRIVER.CAB \Users\YourUserNameHere\Desktop\DRIVER. Open up the DRIVER folder and find ACPI.SYS and delete it. Move blackwingcat's acpi.sys in and rename it to ACPI.SYS. Also delete the original DRIVER.CAB file from the desktop 7. In the command prompt, run this command: cd C:\Users\YourUserNameHere\Desktop\DRIVER. This will change the directory to the DRIVER folder. Once done, run this command: dir /b > ..\filelist.txt. It will create a file named filelist.txt on the desktop. 8. Next up, run this command: ..\cabarc.exe -m LZX:21 -p -r -i 65349 N ..\DRIVER.CAB @..\filelist.txt. This will rebuild DRIVER.CAB. Once it is done, you can move it back into the i386 folder. 9. Now, open up nlite and point it to the Windows 2000 folder on the desktop. On the options screen, select Drivers and Bootable ISO. On the next screen, select Insert and Multiple Driver Folder. Chose the iata76_cd2kh folder. Once it shows a list of drivers, select all of them. Let it integrate them. Once done, have it make a bootable ISO. Give it a name and then select Make Bootable ISO. Give it the same name again and save the ISO to the desktop. 10. Once done, open your DVD burner and burn it to a DVD. 11. Load up your computer and install Windows normally (Do not press F5, F6, or F7). After the second phase of setup is complete, insert the Linux USB and remove the Windows 2000 CD. Press F12 or whatever the hotkey is to boot into the USB. Select Try Ubuntu from the USB. Load it up. On the other computer, if you haven't already, copy blackwingcat's ACPI.SYS to a separate USB, Insert that into the other computer once done there. Navigate to your Windows 2000 hard drive and navigate to WinNT\System32\Drivers folder. Look for acpi.sys and delete it. Load up the other USB in a separate window and move in blackwingcat's ACPI.SYS to the folder. Also search for USBhub20.sys and delete it. Use Unbuntu's restart command, remove both USB's, press enter, and let it load Windows 2000. The last setup stuff it has to do will complete and you will be at your desktop in no time. I hope this helps you guys out! Credit to mswin.bat, Vruh 2, and lambdacore over at Betawiki Discord and also to @blackwingcat for helping me out here! This would not have been possible without their help (with rebuilding the cab file and the custom made sata and acpi driver). EDIT: 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

×
×
  • Create New...