3) USB 3.0 driverThe USB controllers on modern motherboards work in XHCI mode. By default Windows XP only supports EHCI controllers and you need a driver for XHCI support. In this archive you will find a USB 3.0 driver ported from Windows 8 to Windows XP. USB drivers must be used with a modified ACPI driver, without the correct ACPI, the USB XHCI driver will not even install.
Advantages:
1) Modification of Microsoft driver.
2) High stability
3) Support for all xHCI USB controllers that Windows 8 only supports
4) Full RAE support (for x86 systems with more than 4GB RAM)
5) PC switch to Standby mode
6) High speed (100 MB/sec read from USB3 flash memory stick, I could see it personally)
Installation:
When installing Windows XP from scratch, you need to integrate USB3_from_Win8 (NEW) + acpi.sys into the distribution using nLite. How to do this was previously posted, read the forum. When replacing the driver in the installed system, first replace ACPI, then use "Device Manager" to update both components: first "USB 3.0 Root Hub" and then "USB 3.0 xHCI Host Controller". Note that the protection of the OS may return old files, keep an eye on this.
First version of universal driver from May 3, 2020:
USB3_from_Win8 (NEW) - "new driver" for ALL chipsets, ported from Win8
USB3_x86_PAEfix (OLD) is "old driver" for new Intel chipsets with correct work in PAE mode (RAM>4GB).
acpi.sys - modified ACPI, put it in c:{WINDOWS\system32\drivers
Download (840 kB) -
https://www.upload.ee/files/12532472/US ... s.zip.htmlNuances:
v2.3.3.XXX = Generation 1 drivers are the most stable versions, I recommend using v2.3.3b14.zip -
https://www.upload.ee/files/12532348/Wi ... 4.zip.htmlv2.3.4.XXX = Generation 2 drivers - newer versions, more complicated to install. You need to manually copy files ntoskrn8.sys and storport.sys, taken from Integrator Files\Patches\Miscellaneous and also files wdf01000.sys and wdfldr.sys, taken from "Kernel-Mode Driver Framework 1.11" to folder c:\WINDOWS\system32\drivers
Get the latest version of the 1st generation universal driver dated June 16, 2020 from Generic USB 3.0 xHCI driver v1.2 taken from "WinXP-IE Optional Patch Integrator v2.3.3b20.zip" -
https://www.upload.ee/files/12532315/Wi ... 0.zip.htmlTake the latest version of the 2nd generation universal driver dated September 9, 2020 from the Microsoft USB 3.0 xHCI driver v2.1 folder of the stable version of the WinXP-IE Optional Patch Integrator v2.3.4 Stable -
https://www.upload.ee/files/12532365/Wi ... e.zip.html4) A set of INF stubs for system and useless devicesSystem devices on the motherboardI am laying out a set of drivers for Intel motherboards, for AMD motherboards you have to build by yourself. This driver is not required, the system will install and work fine without it, just in the "Device Manager" will be a lot of undefined devices with a yellow icon. The set was unpacked from a package downloaded from
https://softreview.ucoz.ru/load/10-1-0-32.
There are a lot of small INF files and the Windows installer will not find the INF file you need if you set the installation to look for the driver in a specified folder. Then how to work with this package?
1) We look through the "Device Manager" ID codes of the required hardware. For example it will be VEN_8086&DEV_34A3. Then use TotalCommander to find line VEN_8086&DEV_34A3 in files "by contents" and find it in IceLakePCH-LPSystem.inf file.
2) Copy it to a separate directory. Open it with Notepad and study the contents, this file also refers to IceLakePCH-LP.cat, which we also copy and put next to it.
3) Then install this driver manually by selecting "Intel(R) SMBus - 34A3" device from the list. Match the ID code with the driver name in the [Strings] section. This section is usually at the bottom of the inf-file.
To not bother with every single device, just
integrate the whole set into the installation distribution. When installing the OS, an in-depth driver search is performed and you won't need to poke at each file individually.
INF Plugin Archive (194 KB) -
https://www.upload.ee/files/11387540/Wi ... _.zip.htmlUseless devicesThe IME driver is basically a technology for remote PC control, in a first approximation a telemetry service, useless to a user. A set of clever words like Identity Protection Technology, Boot Guard, Rapid Start Technology, Smart Connect Technology, Sensor Hub Controller (ISHC), Active Management Technology (AMT), Small Business Advantage (SBA), Wireless Display, PlayReady, Protected Video/Audio Path, again, is nothing more than pushing telemetry under the guise of unusual technologies with pretty names. It's up to you whether you need it or not! Read more on Vinrade -
https://www.win-raid.com/t596f39-Intel- ... Tools.htmlAs a "driver" of IME I recommend to use the empty driver (stub). The driver has no functionality and removes the yellow icon for IME. If you don't have driver installed on your OS, change digits of OS version from 6.1 - it is Win7, to 5.1 - it is Windows XP by editing INF-file. Driver without functionality - it doesn't do anything, it just tells system, that driver is installed and Windows doesn't need driver.
; NULL Driver[Version]
Signature="$WINDOWS NT$"
Class=System
Provider=Intel_Home
DriverVer=07/05/2019,1.2.5.4
[Manufacturer]
Intel_Home=Intel, NTx86, NTamd64
[Intel.NTx86]
"IME x86 (NULL Driver)" = Intel_Inst, PCI\VEN_8086&DEV_A13A
[Intel.NTamd64]
"IME x64 (NULL Driver)" = Intel_Inst, PCI\VEN_8086&DEV_A13A
[Intel_Inst]
; the install section must be empty
[Intel_Inst.Services]
AddService = ,2 ; no value for the service name
The stub driver can be installed on any useless device, like Intel Management Engine and the like. To install, you need to replace VEN_8086&DEV_A13A with your ID codes. "Installed" device will have driver version 1.2.5.4 with date 07/05/2019 and name "IME x86 (NULL Driver)". Everything can be edited with standard Notepad, by entering your values. You will find complete file in archive -
https://www.upload.ee/files/11375292/Nu ... r.zip.htmlThe archive contains hal.dll and intelppm.sys
timer fix for Intel motherboards, which files were taken from hardcore. I didn't find any description of what's being patched. With these files we get up to 1-2% performance boost on Intel CPU and significant speed boost on SATA AHCI controller which increases speed of reading SSD disk up to 20-30%. According to some reviews this fix also removes microlags in 3D games.
5) REALTEK sound card driver.From the official Realtek website, the driver "Realtek HD Audio v5.10.0.7510" from 06.08.2015 has already been removed. Although the site has a driver for Windows XP dated 10.12.2013 and it works on my sound system too (ALC887 chip, motherboard built on Intel H110M chipset), but this one is more recent -
https://www.upload.ee/files/11522597/Re ... _.zip.html.
Unfortunately after the Windows 10 interface cutout, a lot of hardware manufacturers started to remove drivers for old systems. It seems that this is done consciously and deliberately, so that people can not work on the old operating systems, and were forcibly transferred to Win10. On the official sites there are no driver files themselves, no information on what version is the latest. There are a lot of fakes: it says one thing, but in fact the driver for Win10 or another version. After a day of searching, I actually got the latest version of "Realtek HD Audio" drivers for Windows XP - it's version 5.10.0.7514 of 23.08.2016.
The supported chips are ALC880, ALC882, ALC883, ALC885, ALC886, ALC887, ALC888, ALC889, ALC892, ALC899, ALC861VC, ALC861VD, ALC867, ALC900, ALC660, ALC662, ALC663, ALC665, ALC668, ALC670, ALC671, ALC672, ALC676, ALC680, ALC221, ALC231, ALC233, ALC235, ALC255, ALC260, ALC262, ALC267 and others.
Realtek_HD_Audio_v5.10.0.7514 driver from 08/23/2016 for Windows XP (35 MBytes) -
https://www.upload.ee/files/11530218/Re ... 6.zip.htmlWarning, a known bug in the XP driver! If you have reinstalled the driver several times, the driver may stop installing or the sound may disappear with the driver installed. Treatment - in Device Manager -> System Devices -> try to remove Microsoft UAA Bus Driver for High Definition Audio and reboot to redefine the bus.
6) The driver for network cards on REALTEK chipYou can find the driver for network cards with Realtek chips on their website. The driver on Windows XP is fairly new (version 5.836.0125.2018 from 25.01.2018) and supports most modern hardware. Since manufacturers very often remove drivers for older operating systems like Windows XP, I have reposted this driver on the sharing sites.
The driver "Realtek Ethernet PCIe Family Controller.zip" (940 kB)
https://www.upload.ee/files/11794394/Re ... r.zip.htmlhttps://www37.zippyshare.com/v/OcTa8lst/file.html7) Drivers for Intel embedded network cardsMy searches for the driver started with a Z87 chipset motherboard with an Intel(R) Ethernet Connection i217-V on it. As it turned out, there is a driver, but it was not easy to find. The latest driver package published for Windows XP by Intel for its network cards does not include it (version 18.3, I think), in later versions the support for Windows XP is discontinued. A comparative analysis of the latest driver package for Windows XP and the driver package for Windows 7 32-bit showed that if a driver for Windows XP existed, it would be called e1d5132 (meaning e1d5132.inf, e1d5132.sys, etc.). Googled e1d5132.inf - came up with Intel Ethernet Drivers for Microsoft Embedded Operating Systems, then googled Intel Ethernet Drivers for Microsoft Embedded Operating Systems - came up with the Intel Download Center, where you can download this driver package:
PROEmbSw11.exe file, version 11.5, dated 01/09/2013.
File PROEmbSw12.exe, version 12.0, dated 19.12.2014.
Now the files have been removed from the download center, but found on the Internet. Both drivers are in the archive (9 MB) -
https://www.upload.ee/files/12081517/In ... P.zip.htmlIf exactly your network card is not in the driver explicitly, it must be added by replacing the DEV_ID of the neighboring, close in name. Why could not it be laid out so that it could be found humanly (at least with the status of beta or unsupported) - is not clear. More precisely, it is clear - we see Microsoft support in conformation of old convenient operating systems - such as Windows XP.
8) Drivers for Radeon and GeForce graphics cardsThere are complete drivers for Windows XP for video cards up to and including NVidia GTX 960 and AMD Radeon R9 370X. There are no drivers for newer video cards on Windows XP yet. There are modifications for NVidia GTX 1060, but only 2D acceleration works and gaming 3D doesn't work, so I don't lay out such crutches.
NVIDIA graphics card (GeForce iCafe Graphics driver v368.91)Supported cards:
GeForce 900 series: GTX 960, GTX 950
GeForce 700 series: GTX TITAN Z, GTX TITAN Black, GTX TITAN, GTX 780 Ti, GTX 780, GTX 770, GTX 760, GTX 760, GTX 750 Ti, GTX 750, GTX 745, GT 740, GT 730, GT 720
GeForce 600 series: GTX 690, GTX 680, GTX 670, GTX 660 Ti, GTX 660, GTX 650 Ti BOOST, GTX 650 Ti, GTX 650, GTX 645, GT 645, GT 640, GT 630, GT 620, GT 610, 605
GeForce 500 series: GTX 590, GTX 580, GTX 570, GTX 560 Ti, GTX 560 SE, GTX 560, GTX 555, GTX 550 Ti, GT 545, GT 530, GT 520, 510
GeForce 400 series: GTX 480, GTX 470, GTX 465, GTX 460 v2, GTX 460 SE v2, GTX 460 SE, GTX 460, GTS 450, GT 440, GT 430, GT 420, GT 415
http://drivers.softpedia.com/get/GRAPHI ... r-XP.shtmlhttp://cn.download.nvidia.com/Windows/i ... tional.exeThere is information on the net that drivers newer than the 322 version under PAE no longer work, for PCs with more than 4GB RAM. But the test showed that the 368th works fine. Probably the restriction was regarding drivers for Vin7 and not for VinHP.
Support for GTX970/980/980TI/TitanXOfficially the drivers for Windows XP only exist for GTX960, while newer cards are not supported. It turns out that there is a method to adapt driver for GTX970, 980, 980TI and Titan X cards -
https://mattpilz.com/windows-xp-drivers ... i-titan-x/AMD graphics cards (Radeon iCafe driver for Windows XP)Supported cards:
AMD Radeon HD 5000 Series: HD5450 / HD5550 / HD5570 / HD5750 / HD5770 / HD5830 / HD5850 / HD5870
AMD Radeon HD 6000 Series: HD6450 / HD6570 / HD6670 / HD6750 / HD6770 / HD6850 / HD6870 / HD6950 / HD6970
AMD Radeon HD 7000 Series: HD7750 / HD7770 / HD7850 / HD7870 / HD7950 / HD7970 / HD7990
AMD Radeon R9/R7 200 Series: R5 230 / R7 240 / R7 250 / R7 250X / R7 260X / R9 270 / R9 270 1024 SP / R9 270X / R9 280 / R9 280X
AMD Radeon R9/R7 300 Series: R7 360 / R9 370 1024 SP / R9 370X
All AMD Radeon APU Series: HD7480D / HD7540D / HD7560D / HD7660D / HD8370D / HD8470D / HD8570D / HD8670D / R7 series
http://radeon.ru/drivers/amd/xp/icafe-w ... -sep24.exehttps://web.archive.org/web/20180817074 ... ified.aspxThere is only the video driver in the archive, if you need Catalyst Control Center, please install it separately.
Download -
https://www.upload.ee/files/12377846/AM ... 3.zip.htmlIntel graphics cards (embedded in processors)The latest Intel HD Graphics driver for Windows XP and 4th Generation Intel Core processors (Haswell).
Version 14.56.0.5449 dated February 7, 2014 (graphics 01/30/2014, version 6.14.10.5449).
Download -
https://www.upload.ee/files/12236569/Wi ... r.zip.html9) Drivers kit (official drivers for different hardware)DriverPack DrvCeo is one of the best free sets of drivers for different hardware. There is a version for Windows XP as well as for other operating systems. In this set you will not find those modifications for modern PC. These are the usual, official drivers, just assembled into one set DriverPack DrvCeo x86 v1.9.18.0 (December 2019). Don't mindlessly install everything in a row. Use only in case of inoperability of certain hardware. Be critical of this kit and others like it. The author can not test on everything and the existing hardware, so there may be erroneous drivers and confusion with versions. It is better to search for drivers separately by VEN_ID and DEV_ID codes, but if you are lazy then this set is for you.
Download (650 MB) -
https://yadi.sk/d/UjXvo7n1mvgycg or
https://yadi.sk/d/RcnjQRXMerIhmAInstalling any drivers manually (the most detailed instructions):
The majority of users got used to install drivers through the installer - run the e.g. file, press the buttons and it's done. But what to do if the driver does not have an installer? Among the modified drivers 99% go without the installer. I describe in maximum detail the procedure of installation of the driver through the "Device Manager", by pointing at the INF-file manually. As an example, let's install universal AHCI SATA driver from "WinXP-IE Optional Patch Integrator v2.3.3b20.zip".
Methodology:1. Boot as an Administrator user. At the time of driver installation, do not run unnecessary programs. It should use as few resources as possible. You may open this text instruction in Notepad - this will not affect it, but you definitely should not run heavy programs.
2. 2. Unpack the folder with driver "Generic SATA+AHCI driver v1.3" to the folder "Temp" on drive "C". You can set it to any other path, it doesn't matter, just don't forget where you want it to go.
As a result, we will get 3 files:
c:\Temp\Generic SATA+AHCI driver v1.3\storahci.inf - command file for driver installation
c:\Temp\Generic SATA+AHCI driver v1.3\storahci.sys - system file, the driver itself
c:\Temp\Generic SATA+AHCI driver v1.3\Readme.txt - text description
After installing driver successfully, folder with files can be removed, files will be copied to the system and this folder will be useless.
3. Go to Start - Settings - Control Panel, click on System shortcut, go to Hardware tab, click on Device Manager.
4. In "Device Manager" find the category with the device, if the driver was previously installed and you want to update it or the device will be with a yellow icon in the category of other (not defined) devices.
5. 5. In my case SATA AHCI controller had already installed the driver of Fernando modification, so SATA controller is already in the category "SCSI and RAID controllers".
6. Open the category, double-click - go to its properties. Usually properties window has tabs: "General", "Driver", "Details", "Resources", but there may be some additional tabs, like power management
7. Go to the "Driver" tab and click on the "Update" button. The "Hardware Update Wizard" window opens, asking if you want to connect to the Windows Update node. Our driver is on the disk, so Windows Update will not help us anything, although I do not know of cases where it would help. Choose the bottom item "No, not this time", click "Next".
8. A window will open with a choice of "Auto Install" and "Install from Specified Location". We clearly know where our driver is - so we choose the bottom item "Install from Specified Location" and click "Next".
9. A window will open with the choice of the driver search path. You can select "Include next search location" and use the "Browse" button to specify the path c:\Temp\Generic SATA+AHCI driver v1.3, but it is better to do it manually. Sometimes it happens that the driver consists of several INF files and the search can't find the needed one. This often happens with unpacked motherboard drivers, where the directory can contain more than 20 different INF files. Therefore the best option is to click on the INF file "manually", for which we select "Do not search. I will choose the right driver myself" and click "Next".
10. In the window that opens, click "Install from disk". The "Install from Disk" window opens, where you click on the "Browse" button. Normally the default path is to the lisette (drive "A"), but we go to drive "C" to the directory "Temp", then to the directory "Generic SATA+AHCI driver v1.3" and point to the file storahci.inf. Press the "Open" button. The path will be automatically filled in and then press the "OK" button.
11. After that a window with the list of available devices will open. They can be one or more. In our example, this device is called "Standard SATA/AHCI Controller". Well, whatever, most drivers for WinXP do not have a digital signature, it is not considered mandatory for WinXP. Press the "Next" button.
A window will open with the driver installation progress and copying files. If during installation you will get a warning that the driver is not signed, agree that you will use it anyway. If existing files will be replaced, agree to that as well. When the installation is complete, a window will open saying that the installation is complete but that the hardware will not be used by the system until you reboot the computer. Click the "Finish" button at the bottom.
13. Close the "Task Manager" window, the "Change System Settings" dialog box will appear asking you to "Restart your computer now". You can click "Yes" for an immediate reboot, you can click "No" if you need to save any open documents. But do not delay with rebooting, as soon as you close the documents you must restart your PC immediately.
14. After restarting the PC, the new driver should work. You can go to "Device Manager" again and look at the tabs "General", "Driver", "Details", "Resources" to see the information about the installed driver
P.S.: When you install a driver "manually", something can go wrong. For example, you may install a driver that is not compatible with your hardware and the system may stop booting, dropping into BSODs or the installed device may start glitching. In manual mode (by changing VEN_ID and DEV_ID) you can install any driver to any device. Be prepared for such circumstances beforehand!