NOTE: If there are drivers for other versions of windows, for example Vista or 64 bit drivers, do not install them as it will cause file load errors. If you do select them, nLite will notify you of the problem.
After selecting Textmode Driver you will be at a page listing all the drivers that will be installed. You should click on the Next button and then click on the OK button when it asks if you want to start the process. Your SATA drivers will now be integrated into your Windows files folder. When the process has finished, click on the Next button and then the Finish button.
Windows XP Pro SP2 W SATA Integrated Drivers!
Hi,I just added your drivers in windows xp, made new image with it, setuo bios to ahci and run install. However, on certain stage I saw something like "There are no any HDD at your system". My config is asrock z87 extreme4, i7 4770k - do these drivers work with it?Thx
I recently had to go through all of this again. How familiar are you with DISM? Or do you have your own copy of NTLite?So, I was installing Win 7 SP1 on an NVMe, which requires the incorporation of a Win 7 SP1 hotfix. I found that order matters with my X399 platform on when you incorporate this fix, as if I did so after using the Asrock Win 7 USB 3.0 fix software, it would not allow using DISM to include the hotfix in the image. Because I couldn't do it or verify it, I went old school with a PS2 keyboard, which this MB has that port. If you do not have a PS2 MB or a legacy USB 2.0 port, it will complicate things a bit.1) Get a clean copy of Win 7 SP1.2) Use DISM with the Install.wim to mount the image and to install the hotfix and drivers you want (you can verify after that they are included in the install.wim).2.a) here is Intel's instructional on NVMe hotfix and Windows instructional on commands to incorporate drivers. You can extract the drivers from those sources or AMD's chipset driver from their website. -and-storage.html -us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-imageIt is worth noting that many of the drivers I took from the Chipset and other drivers on the manufacturers page failed to be included in the image, but with DISM, you are told if there was an issue doing so. Also, ignore Intel telling to do the patch program first if using Asrock's utility, as afterwords I could not get DISM to add the hotfix for NVMe for the life of me. ( I used the most recent Win 10 ADK, which may have been the issue instead of using the Win 8 ADK or Win 7 ADK to include the drivers, as an aside; since I had the PS2 keyboard and port, it was one more thing I didn't want to troubleshoot during the effort to install Win 7 SP1 again).3) You can then try to use the Win 7 USB patcher utilities on the install.wim or disk folder you create for Win 7 that you dropped in the modified install.wim file.3) Put a clean Win 10 image on a USB. Then only replace the install.wim on the USB with the Install.wim modified from Win 7. This will install windows 7 without an issue, but if you did not do the NVMe hotfix correctly with DISM, it will error when trying to boot after that. You may want to put in a storage hard drive on the system that is non-nvme with the drivers necessary to load after windows boots so that you can install your LAN or WLAN drivers as needed, as well as containing the All-in-one driver or the chipset driver from AMD so that you can run it. If you didn't get a successful USB 3.0 patch, but have a legacy USB 2 that is recognized or a PS2 port, use keyboard commands to navigate to the folder containing the chipset driver and run it. After running that, your USB 3.0 peripherals should install and start being able to be used on the Win 7 SP1 OS.Hope this helps a little bit! If you need more information, feel free to ask.Edit: To be clear, even if you do not get the USB 3.0 and 3.1 drivers into the Win 7 Install.wim, by copying the install.wim onto a windows 10 USB stick in the sources folder (overwrite the Win 10 install.wim file), you can use the USB 3.0 and 3.1 peripherals to install Win 7 SP1 on the drive. You just will have no ability to setup windows or use those peripherals AFTER the install is done, meaning you have no ability to input anything into the OS, unless you properly included the USB 3.0 and 3.1 drivers into the install.wim image. That is why I mentioned the PS2 or USB 2.0 legacy inputs as a backup. Wanted to clarify that. Also, by copying it onto a Win 10 USB stick, it will install onto an NVMe drive without an issue, but cannot initialize after the install without the hotfix being integrated into the install.wim. You will get error and bootloop if the hotfix is not on the image.Edit 2: Links to different ADKsWindows 10 APK 1803 Build -us/windows-hardware/get-started/adk-install#winADKThis page contains the ADK for builds 1709, 1703, 1607, and Windows 8.1, as well as Insider preview.
Is this still needed? I am currently trying my method above and running into issues installing windows 7 for some reason. Doing hangs and wondering if it is the version of rufus I'm using or what. I've actually installed it twice on an NVMe drive and now just trying to install it on a regular HDD. I keep running into the CLASSPNP.sys driver hang (which can be resolved with the USB drivers), disk.sys hang, and one other driver hang (didn't explore beyond that yet).Once I figure out how to reliably get it to install on my 1950X, I planned on creating a community based image with all of the AMD recent chipset drivers incorporated into the install.wim with it put into a windows 10 iso. Just have to get it working first! LOL. 2ff7e9595c
Comments