Jakob99

Here it is in the image below.

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.

Does anyone know if .net framework 4.8 works under Vista? If so, how do I get it working.

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.

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

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.

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.

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.

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

Ah. Thanks for sharing this link!

I know this thread is old, but I want to say thank you for linking to these Nvidia Quadro drivers. By adding in my 06EB hardware ID, I was able to get these to install on a Dell Latitude E6400 with 2000. Interestingly enough, the Quadro drivers from Dell's website do mention 2000 in the inf of the XP version, but I don't think I was able to work that one under 2000.

1. Grab a Windows 2000 SP4 disc. 2. You will need a SATA driver otherwise you will get a BSOD. blackwingcat has them somewhere on his blog http://blog.livedoor.jp/blackwingcat/archives/1995283.html but I am unable to remember where I found them (Tip: Use Google Translate to translate his site into your desired language. Once you find what you need, navigate to that page on the untranslated Japanese site and complete the download there. Downloads do not work on Google Site Translations). 3. Integrate using nLite. 4. Install the OS normally. No need to press F5, F6, or F7. 5. After installation, using another computer download these nVidia quadro drivers https://www.nvidia.com/download/driverResults.aspx/25619/en-us If your graphics is Intel, you should have Windows 2000 support from using the Intel graphics on the Dell website for the Latitude E6400. You can grab the Intel graphics here: https://www.dell.com/support/home/en-us/product-support/product/latitude-e6400/drivers Just ensure Windows XP (not the x64 version) is selected. 6. Copy them over to the windows 2000 laptop through a USB drive along with 7zip. 7. Open up the NV4_DISP.INF file in Notepad by extracting the exe installer with 7zip. 8. Use Ctrl+F and search for this line: %NVIDIA_DEV.06E9.01% = Section002, PCI\VEN_10DE&DEV_06E9 Copy it and paste it directly below it. Change E9 to EB so it now reads %NVIDIA_DEV.06EB.01% = Section002, PCI\VEN_10DE&DEV_06EB 9. Save the file and then right click My Computer on the desktop and click on Manage. Point to Device Manager and click on the graphics driver under Other Devices. Click on Reinstall driver. 10. Click Next on the screen that pops up. Deselect everything except for Specify a location. Browse to the aforementioned NV4_DISP.INF anf click Ok. The next popup should have a checkbox for Install one of the other drivers. Check that and click next. On the list that pops up select %NVIDIA_DEV.06EB.01%. Click next to let it install. Restart and you should now have 32bit color!

Hi! I have Windows 2000 installed to a Dell Latitude E6530 with Ivy Bridge, but am having issues with it. 1. I can't seem to get it to install under ACPI mode as attempts to do that result in a non-ACPI complient BIOS BSOD. To bypass this, I had to hit F5 and install under Standard PC. Is there any way to get 2000 to install under ACPI mode? 2. I am also having issues with the USB ports. I have two USB 3 ports and one USB 2 port, but device manager shows an error with the USB 2 drivers meaning I can't use any of the ports (not even the 3.0 ports as 2.0 ports). I have tried a Google search and even one of the topics here to try and fix this issue, but non seemed to work. Any help on getting the ports working would be greatly appreciated (whether it be through the built-in driver or with a generic USB 3 driver someone made for 2000). 3. What is the best way to fully update Windows 2000 to make it compatible with the Extended Kernel/Extended Core and thus @blackwingcat's custom made Sandy Bridge/Ivy Bridge graphics driver? For internet, this has Intel for both wireless and ethernet and both do not have 2000 drivers, and I currently have no way to use something like USB ethernet or USB wireless that is 2000 compatible due to the aforementioned USB issue (though I can use one if we can fix the USB issue). Any help on these issues is greatly appreciated!

Ah, ok. While I don't use much resource intensive stuff, I do have a few Steam games as well as Dolphin that are, so having RAM 8GB or higher is a must. Games like Bloons TD runs fine with 8GB while something like Dolphin requires more than that for most games to run smoothly. Now let's get this topic back on track before we derail it completely.

It's alright. The Dell laptop that I have is insanely fast! It has enough strength to emulate Nintendo GameCube and Nintendo Wii games through Dolphin flawlessly. What was listed on the eBay listing for this laptop was only partially right, and that was the laptop itself and the 320GB HDD. The other stuff it advertised (8GB RAM and Nvidia graphics) was incorrect and I instead got a beast of an Ivy Bridge HD 4000 graphics card and 16GB of RAM. While most instances of the listing being incorrect tends to not be of any benefit to the customer (I.E. They needed what was listed and not what they instead got), in my case, I benefited a whole lot more by getting a really good bang for my buck with this laptop. This and Windows Vista replaced my 2019 Acer Aspire A315-21 as my daily driver OS. Now when I use the latter, I find it is slow, even with a 1TB SSD and 12GB of RAM. Since the former is from 2014 and nearing 10 years, I am likely gonna build a souped up laptop around Christmas/Birthday (about a month out from each other) that can hopefully be just as powerful as this Dell (like have RAM higher than 16GB), As for Haswell, I do have a really good Dell Inspiron 3847 with it. Only has 8GB RAM compared to the laptop's 16GB's, but regardless, it still runs GameCube/Wii games flawlessly in Dolphin when coupled with 8.1 or 10 (7 works but its Bluetooth stack has issues with the Wii Remotes that were only resolved in 8 and later). So, my two powerful computers happen to be Dell's with Intel Ivy Bridge/Haswell, which are literally one generation and year apart (laptop in 2014 and desktop in 2015). EDIT: All the laptop's/desktop's I own can be seen in my signature.

Actually, I've been here since 2015, but am still sort of new to the advanced Vista/Extended Kernel scene. Luckily I have a good mobo for Windows Vista, a really good mobo in fact (I can score a 5.6 on Vista WEI and a 6.4 on 7 WEI. Never tried 8's WEI). In fact, I am using it right now. It is a Dell Latitude E6530 with Intel Ivy Bridge Core i5 HD 4000 graphics and 16GB of Ram. Have this set up in a UEFI dual-boot with Windows 7 on a 4TB SSD (Previously, not knowing how to get Vista working under UEFI mode was my reason for not using it right away after getting the 4TB). Hopefully, the Haswell issues can get sorted out in the future. I was shocked out how many of the components inside this Dell Inspiron 3847 still had drivers for Vista (HDD and several others), but I guess I shouldn't be too surprised since I cracked open the Intel Graphics Dell hosts on their support page for this model (which are interestingly branded as Intel HD 4000) and it includes entries for some Ivy Bridge models in addition to Haswell, which suggests some variants of this desktop shipped with Ivy Bridge before its discontinuation. Had mine came with that instead of Haswell, it would have been a whole lot easier to get XP/Vista working on it, although I'd have to hunt for the drivers since Dell obviously does not host XP/Vista drivers for the few Ivy Bridge models (and that reason being the fact these machines were quickly fitted with Haswell upon the Ivy Bridge discontinuation in 2015) they may have made (I have theorized that if a graphics driver from the computer manufacturers website contains multiple processor generations, it's because the computer was manufactured with those processors during its lifecycle (for example, the Acer Aspire E1-531 was manufactured with Sandy Bridge and then later Ivy Bridge, although if you look at the graphics Acer has for 8.1, it lists Haswell processors in addition to Ivy Bridge, suggesting a few late models were made with Haswell even though there is no Windows 10 drivers page)).

Interesting. I thought someone said this bug persisted into the RTM Windows 7 that was only patched through an update? I guess I must be mistaken. Regardless, I wonder if Win32 could backport whatever Microsoft fixed in that build to fix the "Black Screen of Death" in Windows Vista. I also hope @win32 sees what we have posted here and can look into it (Sorry for all the tags Win32. Just trying to draw your attention here). This problem and graphics are the main reason I as well as several other people do not use Vista full time on Haswell (and shockingly, at least for my Haswell desktop, still has loads of drivers for Vista. Broadwell and later will not feature much or anything at all).

That's what I started to think too. Maybe this could solve issues of non-complient ACPI BIOS BSOD's on certain newer hardware when trying to install Vista as well. But regardless, I think @win32 may have something up his sleeve in regards to this idea or even something else entirely.

I do not recommend UEFI multi-booting Windows Vista, 7, and 11. I tried so last night and while 7 and 11 loaded up just fine, Vista Blue screened with 0x01E. Keep in mind I was doing this on Ivy Bridge with a Windows 10 ISO that had 11's Install.wim. I suspect it might have something to do with 11's UEFI files. Regardless, I reinstalled the Vista and 7 dual-boot I had and am fine (this also allowed me to use a different extended kernel compatible/Vista ISO that actually had nothing broken or missing). So, let this be your warning to not multi-boot Vista and 11 with UEFI unless you know of a way to make it work without a 0x01E BSOD when booting into Vista. I should clarify that BIOS (MBR) multi-boot works just fine. I currently have a multi-boot of Vista, 7, 8.1, and 11 on an Acer Aspire A315-21 and nothing is wrong with it so far.

1. I meant Service Pack 1. I mistyped. 2. No bugs on Haswell? Interesting. I thought Windows 7 RTM was plagued with the same bug that Vista is currently plagued with that was fixed in a later update.

Yeah, the thread he linked to above, which I made, should work, although I did run into an issue with my AMD Radeon R4 Stoney Ridge graphics card. I got 7 installed under UEFI mode on my Acer Aspire A315-21, but I could not change the resolution, and when I tried to install the graphics driver, I got an error 43 upon restart. Legacy BIOS works just fine. Please let me know either in this thread or in my thread above what your experiences are, especially when it comes to the graphics driver. EDIT: Ivy Bridge and Sandy Bridge will work just fine (I have an Ivy Bridge UEFI dual-boot setup with Vista and 7, trying to do 11 too). Not sure about Haswell, but I see no issues as long as you use an up to date Windows 7 SP2 ISO (No vanilla RTM Windows 7 ISO as that will cause the Haswell bug to occur until you update the OS).

Installing KB4493471 will fix it somewhat, however, on occasion I still get a "Login initialization process has failed" message, but it isn't often. I would say that the bugs aren't fully fixed, but are greatly reduced.

Then why does it list them as if they were installed? If they aren't installed, I'd expect them to show up under the Other Devices as USB storage devices or something similar with a yellow ! point rather than under the USB devices with no !.

Sorry for double post, but I used Driver Booster to install drivers, and it appeared to install Intel USB 3.0 drivers. I thought Intel didn't support USB 3.0 with Vista, even on Ivy Bridge. This is on Dell Inspiron 3847 with Haswell.

That's what I get too.