PPeti66x

I can confirm the ntdll.dll bug in hungarian and czech versions. Microsoft added a new message (ID: 0x8020000B) in Feb 2016, but forgot to update the localized resources. All following messages are shifted by 1 except the last one (which is also a new message). So most of the messages are messed up.

My question is: how to filter out updates with SSE/SSE2 requirement. For Windows Installer (executing one MSI file, e.g. office 2002 installer) and gdiplus.dll (executing Foxit Reader) was easy. The problem is, that untested files with SSE/SSE2 requirement may produce problems later, when some application trying to use it on old systems.

Because some people had problems with the new XP updates on non-SSE-2 CPUs, I made a big test and installed WinXP SP3 and all updates (up to October 10, 2018 from catalog update) on my old 200 MHz Pentium-1 computer (P5 architecture with MMX support). .NET Framework 2.0 SP2 was installed, but not updated nor tested. Windows Media Player was not updated to v10 or v11 and Windows Search 4.0 was not installed. The results are: - Everything installed fine - System booted up correctly - Some updates failed to work due to SSE-2 requirement: kb4340937 (august, 2018) - msi.dll (and may be msihnd.dll and msiexec.exe) kb4343674 (august, 2018) - gdiplus.dll only kb4458000 (september, 2018) - gdiplus.dll only kb4462987 (october, 2018) - gdiplus.dll only So the new gdiplus.dll and Windows Installer updates should be skipped on non-SSE-2 CPUs. But not all installed files are executed by the system by default, so SSE(2) requirement of some of the other files is unknown. e.g. msvidc.dll, t2embed.dll, mf3216.dll, msxml3.dll, msxml6.dll, mrx*, MS JET files should be tested. MS JET seems to be compiled with MSVC12 (which is very uncommon for Windows XP files) - and most of (may be all) MSVC12 compiled applications I used required SSE-2. ================= A different thing: I installed the Windows XP SP3 on the Dell M4800 notebook (Haswell, Q87 chipset). Everything works fine (except VGA in CPU - if dedicated VGA is installed, it is always used by XP, but this is by design), but I can not use sleep/stanydby - it is prohibited by "Microsoft ACPI-Compilant System" driver (HWID: ACPI_HAL\PNP0C08). Device state mappings: S0-D0, S1-Unspec., S2-Unspec, S3-D2, S4-D3, S5-D3 (so the supported sleep states: S0, S4, S5). Is possible to solve this problem (e.g. by remapping S3 to D3)?

AMD R9 280x (3GB VRAM) works fine on XP SP3 (but some - mostly unused - features are not supported)

Hi! OS is Windows XP SP2 (english) hdaudres.dll = KB888111 patched at offset 110h; original: 00,00; new: 64,86 npdsplay.dll = KB911564 patched at offset 160h; original: 00,00,00; new: 61,8F,06 Date difference is because at patching nLite sets the current date. I made the date set back, but +1 minute compared to original. Tripredacus: I'm sorry.

nLite always patches some files: syssetup.dll (to disable checking of signed INF files) sfcfiles.dll (to disable checking of (potentially) patched files, eg. syssetup.dll, tcpip.sys, uxtheme.dll,...) hdaudres.dll - why? npdsplay.dll - why? Can anyone tell my, why these files are patched? (I included these 2 files in original and in patched form in one zip file.)