Zorba the Geek

What is the point of keeping a topic like this alive long after all the links to the addons have become dead?

Microsoft VC7.8.9.10.11.12 Runtime Libraries It should be possible to integrate these addons into XP using the RVM Integrator and into VISTA+ using the WinNT6.x True Integrator. Registry entries have been included that could block the installation of previous releases of these runtimes by application installers. Two releases are provided with the English release including only the English MFC language resource file. File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Enu.7z (DropBox) File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Enu.7z (Google Drive) File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Enu.7z (4Shared) MD5: cbb6ab1aa56b8e12dec310cc32b080a2 SHA-1: 90fc6c30ca19c3c804951328433abd1932668a4f SHA-256: f582d59c2bdba224c49c929e1af8e3580a2e49472ed4158c65409da8bc943f72 Release date: 23/10/2021 Size: 17 MB File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Int.7z (DropBox) File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Int.7z (Google Drive) File: Microsoft_VC7.9.8.10.11.12_RuntimeLibraries_Addon_Int.7z (4Shared) MD5: e0fb8a49696188e5ec0deb7eead15ada SHA-1: a0d4886f2ab7f12ab054257f85569a519f40d3a5 SHA-256: 20e5fd1495698b86c328216db2d394f1734374e6f738524c04832f0fb833650f Release date: 23/10/2021 Size: 18.6 MB Microsoft Visual C++ 2015 Redistributable (x86) This package can be uninstalled from the Add/Remove Windows Components control panel. Unfortunately it is not possible re-install it due to the long file names Microsoft have used requiring them to be truncated into the 8.3 format on the Windows installation disk. It should be possible to integrate these addons into XP using the RVM Integrator and into VISTA+ using the WinNT6.x True Integrator. File: Microsoft_VC14_Runtime_Libraries_Addon_Eng.7z (DropBox) File: Microsoft_VC14_Runtime_Libraries_Addon_Eng.7z (Google Drive) File: Microsoft_VC14_Runtime_Libraries_Addon_Eng.7z (4Shared) MD5: 5C20835CECB7BEF99D41D159FB74619A SHA-1: B664EBE446244355B240AC9BF575C9AFF9716901 SHA-256: 7F8BFD00DD45C44FAC0DC59995680325EF89F708DC53AEEA8D2F1936F1EEDDC5 Release date: 05/06/2022 Size: 4.43 MB File: Microsoft_VC14_Runtime_Libraries_Addon_Int.7z (DropBox) File: Microsoft_VC14_Runtime_Libraries_Addon_Int.7z (Google Drive) File: Microsoft_VC14_Runtime_Libraries_Addon_Int.7z (4Shared) MD5: 86EAB3C655F48BE082B31977505B09F6 SHA-1: 0D15EE93C3777E8FB8EFD2A86D2EFDC4ECEE00A9 SHA-256: DA838CE8D9D60FB0E188CB3CE60906C4CC99423623B4B0CDE3BA3BB9344D9118 Release date: 05/06/2022 Size: 4.53 MB File: Microsoft_Visual_C++_2015_Minimum_Runtime_Addon.7z (DropBox) File: Microsoft_Visual_C++_2015_Minimum_Runtime_Addon.7z (Google Drive) File: Microsoft_Visual_C++_2015_Minimum_Runtime_Addon.7z (4Shared) MD5: 96B1E43519B36A8EB23B44E7030A62D2 SHA-1: 5D38085758DB64FDDD1652DDD0DF1670085FAB5E SHA-256: BB06608BC86FC9A14FFE56AF85C359EA1F078DFD40A464381A45745D5570E428 Release date: 05/06/2022 Size: 731 KB Microsoft Visual C++ 2015-2019 Redistributable (x86) This package can be uninstalled from the Add/Remove Windows Components control panel. Unfortunately it is not possible re-install it due to the long file names Microsoft have used requiring them to be truncated into the 8.3 format on the Windows installation disk. It should be possible to integrate these addons into XP using the RVM Integrator and into VISTA+ using the WinNT6.x True Integrator. File: Microsoft_VC++_2015-19_Redistributable_Addon_Eng.7z (DropBox) File: Microsoft_VC++_2015-19_Redistributable_Addon_Eng.7z (Google Drive) File: Microsoft_VC++_2015-19_Redistributable_Addon_Eng.7z (4Shared) MD5: 4633B4361B210738AEEE7CCE2B2C803D SHA-1: 69C0D88B1C60DDB0DA6A3D35B4F7B07EAC626441 SHA-256: B11EAA83EC2D379E9D49D6D3830CE59A8618859ADB37F2B33B398DFA43B6A7AE Release date: 05/06/2022 Size: 4.54 MB File: Microsoft_VC++_2015-19_Redistributable_Addon_Int.7z (DropBox) File: Microsoft_VC++_2015-19_Redistributable_Addon_Int.7z (Google Drive) File: Microsoft_VC++_2015-19_Redistributable_Addon_Int.7z (4Shared) MD5: 1663BB442310881DB73697DEB20BFB4F SHA-1: 5EA31B7BAA21B77E5B096399125671F87DE103F4 SHA-256: E33B33C43C91D1A97457EB178661181922CD190FDEC32A03B71E5C44A73AB3B7 Release date: 05/06/2022 Size: 4.63 MB File: Microsoft_Visual_C++_2015-2019_Minimum_Runtime_Addon.7z (DropBox) File: Microsoft_Visual_C++_2015-2019_Minimum_Runtime_Addon.7z (Google Drive) File: Microsoft_Visual_C++_2015-2019_Minimum_Runtime_Addon.7z (4Shared) MD5: F79049B96DE6D2873BAAF54223A0A4E0 SHA-1: 74C1EAABF28BA436545CAD0B909FF2AA11579581 SHA-256: 647AD9A655CC8E50E8639AADD31827E4B2F6BAC31B6B33A05FCADCBD7273349D Release date: 05/06/2022 Size: 799 KB Note: 4Shared is blocked in the UK, so UK residents need to use a VPN server in the United States

The RyanVM forum has been down since early February, so I have decided to provide links to my Windows XP addons and update packs here. I recommend that integration is done with the RyanVM integrator version 1.6.1b2.1 which can be obtained here. It needs to be updated by placing 7za.exe version 16.2 in the plugins\7zip folder, and renaming it 7zdn.exe XPSP3_QFE_UpdatePack for Windows XP Post-SP3 This is my update to the update pack created by user_hidden in 2018 with one extra critical update and some enhancements. File: XPSP3_QFE_UpdatePack_20220212_Home.7z (DropBox) File: XPSP3_QFE_UpdatePack_20220212_Home.7z (Google Drive) File: XPSP3_QFE_UpdatePack_20220212_Home.7z (4Shared) MD5: 95E97EA2FC09D318443AA14E3ED20CE8 SHA-1: 21388005FA71ACA2D254C5AD16D05A148EF31D54 Release date: 12/02/2022 Size: 68.7 MB File: XPSP3_QFE_UpdatePack_20210829_Pro.7z (DropBox) File: XPSP3_QFE_UpdatePack_20210829_Pro.7z (Google Drive) File: XPSP3_QFE_UpdatePack_20210829_Pro.7z (4Shared) MD5: B10F3139428A1517B3CAA45CF5002278 SHA1: 200C708A79E393E9DB39F43E35AC37EED59563C5 Release date: 29/08/2021 Size: 68.5 MB XPSP3_QFE_UpdatePack for Windows XP Post-SP3 Combined (Spanish) File: XPSP3_QFE_UpdatePack_20231213_ES.7z (DropBox) File: XPSP3_QFE_UpdatePack_20231213_ES.7z (Google Drive) File: XPSP3_QFE_UpdatePack_20231213_ES.7z (4Shared) MD5: 16d754c9e434ae181007b561592d6950 SHA-1: 7a6d66f62f4e2093238fb47df45464f07e20ca12 Release date:13/12/2023 Size: 67.2 MB KB931125 - Root Certificate Update (40,0,2195,0) KB2728973 - Revoked Root Certificates (5,0,2195,0) KB952013 - ICCD Smart Card Driver. The ICCD Smart Card Driver is probably superfluous, because Windows XP ships with a ICCD smart card driver usbiccd.sys. Neither driver is installed untill a smart card device is connected to your PC. KB971286 - WinUSB 2.0 driver. The Winusb coinstaller and driver are included but installation occurs when a WCID compatible device is connected. Rather than require a custom INF file for the device the generic hardware ID WINUSB,USB\MS_COMP_WINUSB is used. In the Found New Hardware wizard there will be the message “this wizard helps you install software for: USBDevice”. Select “Install the software automatically”. If you prefer to use the WMTP driver delete the file wcid.inf in the %SystemRoot%\INF directory and it will be installed automatically. KB4500331 - A remote code execution fix for Remote Desktop Services (critical). The ActiveX version of Flash has been removed from these update packs, because no-one watches videos in IE8. The AppMgmt service has been removed from the Home Edition because this is a Pro version only feature, and the necessary files are missing from the home edition. The security tab in the properties of files and folders has been made available in normal mode for the Home Edition. The Windows Management Instrumentation consol has been added to the Home Edition. I have included an attachment with a list of what has been included. XPSP3 QFE POSReady Updates Addon File: XPSP3_QFE_POSReady_Addon_20200820_Pro.7z (DropBox) File: XPSP3_QFE_POSReady_Addon_20200820_Pro.7z (Google Drive) File: XPSP3_QFE_POSReady_Addon_20200820_Pro.7z (4Shared) MD5: E2A808A23B9E2C51CB8E4A343A5E33B1 SHA1: BEE57B936E490CB927CF898EEC9E21B2C80DE061 SHA256: 0EF05A702F0EE17A7AC2A607DD174668E1ADE619EE25CE5FADACDD0E3D843FA3 Release date: 20/08/2020 Size: 26.0 MB File: XPSP3_QFE_POSReady_Addon_20200820_Home.7z (DropBox) File: XPSP3_QFE_POSReady_Addon_20200820_Home.7z (Google Drive) File: XPSP3_QFE_POSReady_Addon_20200820_Home.7z (4Shared) MD5: C4FA2434DF7500B7BC5EBE20D9F90C60 SHA1: 03B5E74EE32CF3A79C66ECE665E86E1F8921B5C2 SHA256: 6653FC9A81A5AA04D49DF9798BEA551FEAC779A49AE2AE5D45D2663D855715E9 Release date: 20/08/2020 Size: 26.0 MB XPSP3 QFE POSReady Updates Addon Combined (Spanish) File: XPSP3_QFE_POSReady_Addon_20240101_ESN.7z (BoxDrop) File: XPSP3_QFE_POSReady_Addon_20240101_ESN.7z (Google Drive) File: XPSP3_QFE_POSReady_Addon_20240101_ESN.7z (4Shared) MD5: 5D9F25C41DB91C97583BDAF65E9F8335 SHA-1: E5F8E43B7BAEF3D75C1309C45EA57C4AA362D60A Build date: 01/01/2024 Size: 34.7 MB Credit must be given to 5ereph for initiating this addon and the time and effort he must have put into it. This addon slipstreams all the POSReady 2009 updates released untill EOL on 09 April 2019 directly into a 32-bit XP SP3 source when used with the XPSP3_QFE_UpdatePack. All files are from the SP3QFE branch. An update to the Adobe Flash Player has not been included because no-one plays videos in Internet Explorer 8. Windows Automatic Update will offer a number of obsolete version of gdiplus and the Cumulative Security Update for ActiveX Killbits for Windows XP (KB2900986) when the integrated source is installed. The gdiplus updates I recorded are as follows: KB4473077, KB4462987, KB4458000, KB4039384, KB4015383, KB3178034, KB3065979, KB3035132, KB3029944, KB3013126, KB2957503, KB2834886, KB2659262, KB4463361, KB4022884, KB2412687. This list is probably not exhaustive. They are installed as side by side assemblies in the WinSxS folder. The integrator cannot handle multiple versions of the same module in the WinSxS folder, so it is only possible to integrate the last POSReady 2009 version of gdiplus. Once integration is complete there will be two versions of gdi plus, one from the uppdate pack, and one from this addon. It seems likely that the last POSReady 2009 version of gdiplus is backwards compatible with programs written for previous versions since 2012. Therefore I recommend that you do not install these older versions of gdiplus and disable Automatic Updates. The XPSP3 QFE POSReady Addon and XPSP3 QFE Update Pack can be integrated into the source using the RVM integrator separately or at the same time. If the are integrated seperately the [Obsolete] section of entries_posready.ini will remove security catalogues and registry entries made by the update pack for updates made obsolete by the addon. If integrated at the same time the [ExtraFilesEdits] section of entries_posready.ini will prevent the update pack from installing the registry entries for updates made obsolete by the addon, and the [Obsolete] section will remove the security catalogues. 5ereph’s original XPSP3 QFE POSReady Updates 20180917 disabled the Jet 4.0 database engine. The registry entries for Jet 4.0 have been restored and msjet40.dll and msjetoledb40.dll have been registered in the ActiveX/COm section of the registry. Updates Included: KB2926765 - MS14-027 - Shell Light-weight Utility Library KB2962872 - MS14-037 - IE6 - BrowseWM Player KB2993254 - MS14-062 - Message Queuing* KB2998579 - MS14-063 - Fast FAT File System Driver KB2991963 - MS14-078 - Japanese Input Method Editor KB3020393 - MS15-002 - Microsoft Telnet Server Helper* KB3021674 - MS15-003 - User Environment Group Policy module KB3004361 - MS15-014 - Windows Security Configuration Editor Engine KB3033889 - MS15-020 - WebBrowser Control module KB3033890 - MS15-057 - WMP 9 KB3124275 - MS16-001 - Internet Explorer 6 - Cumulative KB3124624 - MS16-003 - VBScript Scripting Engine v5.7 KB3109560 - MS16-007 - DirectShow Core KB3121918 - MS16-007 - Advanced Windows 32 Base API KB3126587 - MS16-014 - Database Support for Oracle KB3140709 - MS16-025 - Windows Address Book KB3139914 - MS16-032 - Secondary Logon Service DLL KB3139398 - MS16-033 - USB Mass Storage Class driver KB3149090 - MS16-047 - SAM Server DLL KB3161949 - MS16-077 - Web Proxy Auto Discovery KB3170455 - MS16-087 - Print Spooler KB3185911 - MS16-106 - User API Client KB3183431 - MS16-123 - Distributed File System KB3196718 - MS16-130 - OLE Automation KB4012584 - MS17-013 - Microsoft Color Management Module KB4014652 - CVE-2013-6629 - DirectShow KB4014794 - CVE-2013-6629 - DirectShow KB4019276 - Support for TLS 1.1 and TLS 1.2 KB4025398 - CVE-2017-8557 - System Information Control KB4025409 - CVE-2017-8563 - Lightweight Directory Access Protocol API KB4025497 - CVE-2017-8463 - Shell Browser UI Library KB4026061 - CVE-2017-8588 - Wordpad MFC Application KB4034775 - CVE-2017-0250 - JET 4.0 Database Engine KB4047211 - CVE-2017-11788 - Content Index Utility DLL KB4052303 - CVE-2017-11885 - IP Router Manager KB4056564 - CVE-2018-0886 - TS Single Sign On Security Package KB4056941 - OpenType/Type 1 font driver KB4089082 - CVE-2018-0881 - ActiveX control for streaming video KB4089175 - CVE-2018-0883 - ZiP Compression Library KB4089453 - CVE-2018-0878 - Windows Remote Assistance KB4089694 - CVE-2017-13077 - Wireless Zero Configuration Service KB4091756 - CVE-2018-0967 - WinSNMP v2.0 Manager API KB4101477 - CVE-2018-0824 - COM Services KB4130957 - CVE-2017-11927 - InfoTech Storage System Library KB4291391 - CVE-2018-8304 - Windows DNS Client API KB4457163 - CVE-2018-8468 - Windows Shell Common DLL KB4458001 - CVE-2018-8332 - Embedded OpenType Font Engine and Font Subsetting DLL KB4458318 - CVE-2018-8419 - Kernel CSA Library KB4459091 - CVE-2018-8419 - Cryptographic and TLS/SSL Security Provider KB4462935 - CVE-2018-8333 - Windows NT SMB Minirdr KB4463103 - CVE-2018-8411 - NT Kernel KB4467689 - CVE-2018-8550 - Remote Procedure Call Runtime KB4467770 - Enables TLS 1.1 and TLS 1.2 in WinHTTP KB4470118 - CVE-2018-8544 - Windows Scripting Host KB4486463 - CVE-2019-0621 - NT Kernel & System KB4486465 - CVE-2019-0703 - Server driver KB4486468 - CVE-2019-0821 - Named Pipe FileSystem Driver KB4486536 - CVE-2019-0683 - Microsoft Authentication Package v1.0 KB4486538 - CVE-2019-0683 - Kerberos Security Package KB4487990 - Cumulative Timezone Update KB4489493 - CVE-2019-0755 - Mailslot driver KB4489973 - CVE-2019-0784 - Microsoft Data Access - ActiveX Data Objects KB4489977 - CVE-2019-0617 - Microsoft (R) Red ISAM KB4490228 - CVE-2019-0765 - User Experience Controls Library KB4490501 - CVE-2019-0759 - Windows Spooler KB4491443 - CVE-2019-0856 - MBT Transport driver KB4493341 - CVE-2019-0601 - Hid Parsing Library KB4493563 - CVE-2019-0842 - Object Linking and Embedding. NT Kernel KB4493790 - CVE-2019-0792 - Microsoft XML Core Services 3.0 and 6.0 KB4493793 - CVE-2019-0877 - Microsoft Jet xBASE Isam KB4493794 - CVE-2019-0851 - Microsoft Jet Paradox Isam KB4493795 - CVE-2019-0671 - Microsoft Jet Excel Isam KB4493796 - CVE-2019-0847 - Microsoft Jet Engine Library KB4493797 - CVE-2019-0846 - Microsoft (R) Red ISAM KB4493927 - CVE-2019-0848 - Multi-User Win32 Driver KB4494059 - CVE-2019-0845 - COM Interfaces for Printer Web Pages KB4494528 - Windows Installer KB4495022 - CVE-2019-0802 - Microsoft GDI+ KB4500331 - CVE-2019-0708 - Terminal Server Driver *XP Professional only. Note: 4Shared is blocked in the UK, so UK residents need to use a VPN server in the United States or the Netherlands What is included in XPSP3_QFE_UpdatePack_20210829.rtf

I did some research and discovered that there have been no Spectre and Meltdown kernel patches released for Core2Duo CPUs, so I was out of luck. As for the the POSReady 2009 updates mentioned here I am not convinced that they are intended to resolve the Spectre and Meltdown vulnerabilities. KB4056615 is covered by CVE-2018-0748 whose summary is as follows: KB4056615 has been replaced by KB4463103 which is covered by CVE-2018-8411 whose summary is as follows: and is also covered by CVE-2018-8330 whose summary is as follows: I have KB4463103 included as an update on my system and tests for Spectre and Meltdown mitigation showed that there was nothing. I am completely unprotected.

As we all know the the VPN service providers are phasing out their L2TP servers leaving us XP diehards with OpenVPN whose operation which can be erratic at times. Are there third party IKEV2 clients that we could adapt for connection to these public VPN proxy servers? Here is a list of of VPN clients that we could experiment with: HA Remote StrongSwann The Green Bow Soft Remote by Safenet TauVPN SoftEther The problem is that these VPN clients were intended for enterprise VPN networks and require lots of settings that are not known for the public VPN proxys. The software provided by the VPN providers may do the job, but the PureVPN client software requires .NET 4.5. Your thoughts and experiences on this subject would be appreciated.

I think that this may be caused by incorrect formatting of the yara rules and another definitions update may resolve it. An outdated version of yara-python might also be a cause except that we are using the penultimate version 4.3.0. Version 4.3.1 was released last week.

I have compiled Windows XP compatible builds of psutil-5.6.1 including the modifications I made in my builds of psutil-5.5.1. These include restoring the Return the number of physical CPU cores section using code from version 3.4.2, and removing the condition "#if (_WIN32_WINNT >= 0x0600)" from the Get process IO priority as a Python integer and Set process IO priority sections. You can obtain direct downloads of psutil-5.6.1-cp27-cp27m-win32.whl and psutil-5.6.1-cp38-cp38-win32.whl from my 4Shared account. Also available as direct downloads from my OneDrive account: psutil-5.6.1-cp27-cp27m-win32.whl and psutil-5.6.1-cp38-cp38-win32.whl Included is the modified source code including ntextapi.h for Python 2.7 Incidentally compiling psutil without modifications under Windows 8.1 produces lots of warning messages. Is this normal or is it sloppy programming? _psutil_windows.c ntextapi.h Note: 4Shared is blocked in the UK, so UK residents need to access 4Shared from a VPN server located in the US or Netherlands.

After version 3.4.2 of psutil the section Return the number of physical CPU cores was removed for XP and VISTA because the developers preferred to use GetLogicalProcessorInformationEx rather than XP's GetLogicalProcessorInformation. I have restored the Return the number of physical CPU cores section for XP and VISTA in psutil-5.5.1 I have removed the condition "#if (_WIN32_WINNT >= 0x0600)" from the Get process IO priority as a Python integer and Set process IO priority sections because NtSetInformationProcess and NtQueryInformationProcess are exported from the Windows XP version of ntdll.dll (5.1.2600.7682) You can obtain direct downloads of psutil-5.5.1-cp27-cp27m-win32-mod.whl and psutil-5.5.1-cp38-cp38-win32-mod.whl from my 4Shared account. Also available as direct downloads from my OneDrive account. psutil-5.5.1-cp38-cp38-win32-mod.whl and psutil-5.5.1-cp27-cp27m-win32-mod.whl Included is my modified source code. _psutil_windows.c Note: 4Shared is blocked in the UK, so UK residents need to access 4Shared from a VPN server located in the US or Netherlands.

nettaddr requires IPV6 to be installed because it is not installed by default as in VISTA+. In your Local Area Connection Properties install the network protocol Microsoft TCP/IP Version 6. The problem seems to be linked to the line IPV6_LOOPBACK = IPAddress('::1') in C:\Python38\Lib\site-packages\netaddr\ip\__init__.py. Maybe cmalex could help me sort it out. Alternatively I could raise an issue at the LOKI Github site.

The link to alexfree's website where you can obtain the source code is broken, so I have uploaded it to my 4Shared account from where you can download it at the following links File: winxp_python3.6.15-src.zip (4Shared) File: winxp_python3.6.15-src.zip (Google Drive) MD5: 4CAE917675AE7F91F03808F026EA619C SHA-1: 2668E14644007B6A15EF1201E8741353C36CDDFF SHA-256: 0F564388025A843DEFF31AC8AA4CE808369D160D4C417BF0ED53249D04EA38B6 Release date: 26/12/2021 Size: 27.6 MB I have succeeded in compiling it according to the instructions given in readme.txt, and I would be interested in reading about other people's experience of doing the compile. I am mainly concerned about identifying where are the components of this Python 3.6 are located because as far as I can tell they are scattered around both Cygwin and the source folder. Once I identify them I ought to be able to assemble them into a package that can be archived or shared. As far as I can tell this python can be run outside of Cygwin as it is linked to a few Cygwin dlls such as Cygwin1.dll, Cygintl-8dll and Cyggcc_5-1.dll which can be included in the distribution. Note: 4Shared is blocked in the UK. Use VPN servers located in the United States or the Netherlands.

I have compiled Windows XP compatible builds of psutil-5.5.1-cp38-cp38-win32.whl and psutil-5.5.1-cp27-cp27m-win32.whl which you can obtain as direct downloads. I have tested _psutil_windows.cp38-win32.pyd and _psutil_windows.pyd with Dependency Walker and there are no missing imports under XP. I have further tested them by installing them into the Python 3.8.13 supplied by cmalex and then rebuilding Loki, and everything works fine when Loki is run. To create these Windows XP compatible builds of psutil-5.5.1 I first had to delete these lines in setup.py: 111 if sys.getwindowsversion()[0] < 6: 112 msg = "this Windows version is too old (< Windows Vista); " 113 msg += "psutil 3.4.2 is the latest version which supports Windows " 114 msg += "2000, XP and 2003 server" 115 raise RuntimeError(msg) Then I added these lines after line 10 in _psutil_windows.c #define WINVER 0x0501 #define _WIN32_WINNT 0x0501 These #define statements instruct the compiler to select the Windows XP options in the code suitable for the target OS. These XP compatible builds have reduced functionality due to the functions ConvertLengthToIpv4Mask and GetIfEntry2 not being available in iphlpapi.dll version 5.1.2600.5512. GetTickCount64 has been replaced with GetTickCount. The Return NICs addresses section has reduced functionality due to the absence of ConvertLengthToIpv4Mask. The Return path's disk total and free as a Python tuple section has reduced functionality due to the absence of GetIfEntry2. The Return the number of physical CPU cores section was removed for Windows XP and VISTA after version 3.4.2 because they decided to use GetLogicalProcessorInformationEx rather than GetLogicalProcessorInformation. I tried to copy this section of code from version 3.4.2 to version 5.5.1, but naturally compilation failed with lots of undefined variables messages. It could be possible to make Windows XP compatible versions of psutil up to version 5.6.7 if you are prepared to rewrite the code in _psutil_windows.c and possibly elsewhere which I am not qualified to do.

I have successfully compiled an XP compatible version of the latest release from Github which is 0.45 and now it runs perfectly with no error messages. You can try it out by downloading loki-0.45.0-xp.7z from my 4Shared account. You will also require this limited implementation of bcrypt.dll intended for running ffmpeg under Windows XP. It supplies the BCryptGenRandom function required by yara.cp35-win32.pyd. It should be placed somewhere in your path like the System32 folder. Also the Microsoft TCP/IP version 6 network protocol is required by netaddr (I need to work on this). If you want to compile it yourself you need to install the following Python packages: colorama-0.4.6, future-0.18.3, netaddr-0.8.0, psutil-3.4.2, rfc5424-logging-handler-1.43, pywin32-300, wmi-1.5.0, yara-python-4.3.0, and pyinstaller-4.10. There is no distribution of psutil-3.4.2 for Python 3.8. so I have compiled a wheel for psutil-3.4.2 which you can download here. You will require the build of pe-sieve32.exe that does not require the function GetTickCount64 made available by cmalex here. Loki seems to work OK with psutil-3.4.2, but the yara-python developers recommend version =>5.6.7. It is possible to compile psutil-5.5.1 for Windows XP with reduced functionality, because _psutil_windows.c includes options for VISTA+ and XP depending on your operating system. These are typically shown as #if (_WIN32_WINNT >= 0x0600) // Windows Vista and above Lines of code #else // Windows XP Lines of code #endif With a Python 3.8 installation this can only be done with VC14 under VISTA+ which means that the XP only options cannot be implemented. Therefore it ought to be possible to edit _psutil_windows.c to remove the winnt>=6.0 specific code and compile an XP compatible build using VC14. Also it is necessary to delete these lines in setup.py 111 if sys.getwindowsversion()[0] < 6: 112 msg = "this Windows version is too old (< Windows Vista); " 113 msg += "psutil 3.4.2 is the latest version which supports Windows " 114 msg += "2000, XP and 2003 server" 115 raise RuntimeError(msg)

The Stackoverflow post did not provide information for fully modifying PHP 7.3 code to be compatible with Windows XP and POSReady 2009. It merely detailed a change to a single line of code needed to run it with One Core API.

See my next post

cmalex thanks for taking the time to comment on the issues we have raised. I need help compiling LOKi the IOC scanner which requires Python 3.8, but is not supposed to support XP. I know that this should be raised as an issue at the LOKI Github site, but I am afraid they may laugh at me when I tell them I am trying to compile it for XP. After version 0.45 was compiled on a Windows 8.1 machine LOKI ran fine with the following Python modules chosen for compatibility with XP: pyinstaller-4.10. psutils-3.4.2, and pywin32-304 To run it on an XP machine I have to install Microsoft TCP/IP version 6 required by Brotli, and an XP compatible bcrypt.dll required by yara-python. When first run under XP I receive this error message: Linux System - deactivating process memory check ... Traceback (most recent call last): File "loki.py", line 1515, in <module> File "loki.py", line 1490, in main File "lib\helpers.py", line 284, in getHostname AttributeError: module 'os' has no attribute 'uname' After some Googling I remedied this by editing this block of code in Loki-0.45.0\Lib\helpers.py 297 # Computername 298 if os_platform == "linux" or os_platform == "macos": 299 return os.uname()[1] 300 else: 301 return os.environ['COMPUTERNAME'] by changing os.uname() [1] to platform.uname() [1] This resulted in a new error message thus: Traceback (most recent call last): File "loki.py", line 1535, in <module> File "loki.py", line 142, in __init__ File "loki.py", line 1413, in updateLoki File "subprocess.py", line 858, in __init__ File "subprocess.py", line 1311, in _execute_child FileNotFoundError: [WinError 2] The system cannot find the file specified After some Googling I remedied this by altering the following block of code in Python38\Lib\subprocess.py 736 def __init__(self, args, bufsize=-1, executable=None, 737 stdin=None, stdout=None, stderr=None, 738 preexec_fn=None, close_fds=True, 739 shell=False, cwd=None, env=None, universal_newlines=None, 740 startupinfo=None, creationflags=0, 741 restore_signals=True, start_new_session=False, 742 pass_fds=(), *, encoding=None, errors=None, text=None): and changed shell-False to shell=True. This then resulted in another error message thus: Python path configuration: PYTHONHOME = 'D:\DOCUME~1\\LOCALS~1\Temp\_MEI32882' PYTHONPATH = (not set) program name = 'D:\Loki-0.45.0\dist\loki.exe' isolated = 0 environment = 0 user site = 0 import site = 0 sys._base_executable = 'D:\\Loki-0.45.0\\dist\\loki.exe' sys.base_prefix = '' sys.base_exec_prefix = '' sys.executable = 'D:\\Loki-0.45.0\\dist\\loki.exe' sys.prefix = '' sys.exec_prefix = '' sys.path = [ 'D:\\DOCUME~1\\USERPR~1\\LOCALS~1\\Temp\\_MEI32882\\base_library.zip', 'D:\\DOCUME~1\\USERPR~1\\LOCALS~1\\Temp\\_MEI32882\\lib-dynload', 'D:\\DOCUME~1\\USERPR~1\\LOCALS~1\\Temp\\_MEI32882', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized LookupError: unknown encoding: utf-8 At this point I am at my wits end because utf_8.py is present in the Python encodings folder. I am trying to compare the code between version 0.45 and version 0.33 the last XP compatible version looking for clues. This is complicated by the fact that version 0.33 was written for Python 2.7.

I think what you mean is that _imaging.cp38-win32.pyd should be opened with CFFExplorer and the import directory edited so that the module named KERNEL32.DLL is renamed to kernelXP.dll. I assume that kernelXP.dll supplied in the External folder of your distribution should be placed in the same folder as _imaging.cp38-win32.pyd. The missing imports InitializeConditionVariable, InitializeCriticalSectionEx, SleepConditionVariableCS and WakeConditionVariable from kernel32.dll are actually supplied by kerneXP.dll so this might work. I wonder if we can rely modules from the Xompie project like kernelXP.dll to allow the use of up to date Python modules with C extensions incompatible with XP as long as they supply the required functions to be imported.

I want to thank cmalex for all the effort he must have made in producing this backported build of Python 3.8.13. I have succeeded in compiling an XP compatible yt-dlp which is very fortunate because I doubt if there are any other video downloaders currently being developed that support XP. My problem with installing psutils was caused by my use of an unsuitable copy of pyconfig.h which lacked the line #define NT_THREADS. I used the pyconfig.h from version 3.4 which seemed to work. I am including it as an attachment. I have revised my package of this backported Python 3.8.13 in a number of ways and you can download it from my 4Shared account here. The SHA1 hash is bfe13847982d0d75f48b750f8bd700decd72ac87.Here is a list of changes to the package: I have included the pyconfig.h file from the MSI installer of Python 3.8.13, and changed the following lines /* set the version macros for the windows headers */ /* Python 3.5+ requires Windows Vista or greater */ #define Py_WINVER 0x0600 /* _WIN32_WINNT_VISTA */ #define Py_NTDDI NTDDI_VISTA to this /* set the version macros for the windows headers */ /* Python 3.4+ requires Windows XP or greater */ #define Py_WINVER 0x0501 /* _WIN32_WINNT_WINXP */ #define Py_NTDDI NTDDI_WINXP There is still the line #define PYTHONPATH L".\\DLLs;.\\lib" which may need revising because there is no DLLs folder in this distribution. I have copied the contents of Python.zip to the .\Lib folder because pyinstaller seems to have a problem reading the contents of archives. Now it works like a charm. I have updated batch files that install and uninstall Python to the a folder named Python38 in the root of the system drive. i am not clever enough to make an interactive batch file allowing you to choose the name and location of the Python folder. Maybe later. My batch file installs shortcuts for the Python console, the IDLE interactive envirironment, the Python help file, and the pydoc server. The Python path variables are set in the Environment registry key, and a PYTHONPATH value is created under the same key. It might be possible to install pip and setuptools with the bundled wheels using python -m ensurepip --default-pip but I have included get-pip.py to enable the download and install of the latest pip, setuptools and wheel/ pyconfig.h

Hi folks! I recently compiled yt-dlp version 2023.02.17 using the version of Python 3.8.13 backported for Windows XP by cmalex available here on a Windows 8.1 PC so that I could use the latest bug free Pyinstaller. It seems to be a roaring success with impressively fast downloads. I have made it available as a direct download from my 4Shared account here. Please try it and provide feedback here. We are lucky in that yt-dlp and it's Python dependencies do not include C extensions incompatible with XP. I hope I have the same luck when I attempt to make an XP build of Streamlink.

Fifteen years later and I may need to patch setupapi.dll version 5.1.2600.5603, but the hex sequence 8BFF558BEC occurs in multiple locations. Possibly my successful patch for syssetup.dll may enable me to modify layout.inf.

The outlook for VPN anonymity using Windows XP is looking grim because XP only supports PPTP and L2TP IPSec protocols. L2TP is being phased out by VPN providers and PPTP is no longer considered secure. I was beginning to despair because PureVPN have reduced L2TP to four locations in the world, and usually it is impossible to connect to the UK servers, while I remember that their OpenVPN service was terrible. However, PureVPN have appeared to revamp their OpenVPN servers, and they now provide an excellent service with this protocol. I can rely on connections to the UK servers, except at weekends when occasionally a connection attempt fails,and I can play streaming 720p video without problems. So far I have not experienced dropped connections using their OpenVPN servers. A big plus for XP users is that the PureVPN servers will accept connections from PCs with the OpenVPN version 2.3.18 client installed. If you do use this version of the OpenVPN client remember to uncheck the TAP Windows driver when installing it, because it installs a version for VISTA. There is a separate XP compatible installer for TAP Windows version 9.9.2. If at sometime PureVPN demands a later version of the OpenVPN client then we have the option of using a custom XP build of version 2.5.4 which you can obtain from here. Another plus for XP diehards provided by PureVPN is that you do not need to use their app if you need port forwarding. Port forwarding is activated in the members area after paying a fee. If I need a kill switch I use the VPNWatcher app. Also I must say I have had no problem with the OpenVPN client hogging CPU time. I am using a Core2Duo 2.59 Ghz CPU and System Explorer showed that while playing streaming 720p video openvpn.exe had an average CPU load of 0.84% declining to 0.17%.

The ending of suitable VPN protocols for XP would kill the operating system stone dead unless I could somehow figure out how to make a SSL tunnel to a shell account or get a SOCKS5 proxy. The performance of OpenVPN provided by PureVPN was terrible which I assumed was inherent in the protocol, but lately their OpenVPN servers have provided an excellent service,and you can still use version 2.3.18 of OpenVPN. Once they drop support for 2.3.18 there is no reason to despair because someone has made a custom XP build of version 2.5.4 which you can obtain here. Isn't it funny how whenever crucial software support for XP is dropped someone comes to the rescue with their custom build? I am really interested in third party VPN clients like SoftEther and Shrew Soft, but having installed the latter years ago I discovered that it is intended for enterprise VPNs and requires lots of settings that are not available for public VPNs. The Microsoft VPN clients only require the host name and pre shared key. We should continue this discussion about VPNs with a new topic.

Syssetup.inf is digitally signed in Windows XP, so syssetup.dll has to be patched so as to check for M$ Digital Signature on the syssetup.inf file, flagging it as "Always Valid" so that it can be modified. Here are the entries I made for a RVM integrator addon: File name File version Offset BeforeHexCode AfterHexCode I386\SYSSETUP.DLL|5.1.2600.2530|210500| 73 | 72 ;SP2 I386\SYSSETUP.DLL|5.1.2600.2659|211108| 73 | 72 ;KB894871 - SP2QFE I386\SYSSETUP.DLL|5.1.2600.5512|211753| 73 | 72 ;KB936929 - SP3 To remove syssetup.dll from SFC monitoring I patch sfcfiles.dll thus: File name File version Offset BeforeHexCode AfterHexCode I386\sfcfiles.dll|5.1.2600.5512|218048| 250073 | 5C0000 :syssetup.dll I386\sfcfiles.dll|5.1.2600.5512|522176| 250073 | 5C0000 :syssetup.dll I386\sfcfiles.dll|5.1.2600.5512|843936| 250073 | 5C0000 :syssetup.dll I386\sfcfiles.dll|5.1.2600.5512|1180888| 250073 | 5C0000 :syssetup.dll I386\sfcfiles.dll|5.1.2600.5512|1494120| 250073 | 5C0000 :syssetup.dll Sfcfiles.dll is also subject to SFC momitoring so it has to be patched thus: File name File version Offset BeforeHexCode AfterHexCode I386\sfcfiles.dll|5.1.2600.5512|15024 | 250073 | 5C0000 ;sfcfiles.dll I386\sfcfiles.dll|5.1.2600.5512|307384 | 250073 | 5C0000 ;sfcfiles.dll I386\sfcfiles.dll|5.1.2600.5512|629144 | 250073 | 5C0000 ;sfcfiles.dll I386\sfcfiles.dll|5.1.2600.5512|966096 | 250073 | 5C0000 ;sfcfiles.dll I386\sfcfiles.dll|5.1.2600.5512|1291096| 250073 | 5C0000 ;sfcfiles.dll

The end of security updates for XP is not really a big deal. I am using the Atlantis Word Processor, OE Classic, and MyPal which are firmly committed to 32 bit XP compatibility for the time being, so the only thing that could force me to change to Linux is developments in codecs making media unplayable using DirectShow decoders. These do not appear to be in development anymore, so the latest DS decoder I have is the MPC-BE video decoder released in 2016. Also my VPN provider is gradually dropping support for L2TP, and I have not figured out how to make IKEV2 work under XP, which is a worrying development.

I have cracked it! Regular updates for NOD32 Antivirus version 8.0.319 provided by an unofficial update server. Unfortunately the forum rules about circumventing license restrictions prevents me from providing details about how it can be done. However, I hope I can give you some idea of how I did it without being specific and getting myself banned. I found a Youtube video that provided a link in the description for a patch that enables a dialogue box in the update settings in which you can specify a server. The person who uploaded the video had his account terminated after a few days thanks to the vigilance of ESET. I logged the changes made by the patch, and noted that no files are over-written or patched, and only the registry was changed. From this log I made a registry file. After NOD32 AV is installed in the usual way, a well known activation patch is applied in safe mode along with the registry file. Then you enter the address of the server in in the update settings, and update in the usual way. I have yet to see if automatic updates still work. You should note that obtaining virus definitions from an unofficial update server is a risky thing to do, as AstroSkipper has made clear. There could be a legitimate reason for the existence of these unofficial update servers, or they could be run by Russian crooks. Who knows? Later I will demonstrate using the ESET Endpoint antivirus for offline updates if there is nothing involved that could get me banned.

I have decided to remove the information I posted here about unofficial update servers for two reasons. Firstly, these sites could be run by crooks who want to include malware with the virus definitions. Secondly, ESET are hyper vigilant about stamping out methods for obtaining their products without paying for them, so these sites could be shut down. If you have discovered other such sites, or Facebook users who offer regular virus definition packages I advice you not to post links to them here.