Jump to content

Zorba the Geek

Member
  • Posts

    41
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by Zorba the Geek

  1. Internet Explorer 8

    These are my updates to the Internet Explorer 8 addons originally released by YumeYao and 5ereph at the RyanVM forum, and which includes the final IE8 security updates for POSReady 2009.  System files are removed in these addons, so I have disabled their entries in sfcfiles.dll so that they are not flagged by the System File Checker.

    YumeYao_IE8_Addon_Nosetuperr_ENU_1.5.44.7z

    MD5: 879324EF89046713DF67CF14265DACB7
    SHA-1: CECD955BFC292F3BE3A471CCEAE60CBE3B67611F
    Size: 14.4 MB
    Build date: 28/06/2022

    No Setuperr Style: Tricks are made to avoid setuperr.log reporting while not modifying syssetup.inf which require syssetup.dll to be patched.

     

    YumeYao_IE8_Addon_Clean_ENU_1.5.44.7z

    MD5: 5510CCD02498F18414BEF698AD3DECBF
    SHA-1: ACE800F0425C980276F1606D6255F25695CDDC67
    Size: 14.4 MB
    Build date: 25/08/2020

    Clean Style: Files are copied directly resulting in setuperr.log items.

  2. Intel SATA Drivers

    File: iaStor_7.8.0.1012_Addon.7z

    MD5: 8EFF9EBBB5B00A6BD208BB92305458B7
    SHA-1: 3D91757110E1A59A9013C5A312EEA09439EAB29D
    Size: 171 KB
    Release date: 26/03/2022
    Driver Date: 29/09/2007

    Supported device instance IDs:

    Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)
    PCI\VEN_8086&DEV_2653&CC_0106

    Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)
    PCI\VEN_8086&DEV_2681&CC_0106

    Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)
    PCI\VEN_8086&DEV_27C1&CC_0106

    Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)
    PCI\VEN_8086&DEV_27C5&CC_0106

    Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)
    PCI\VEN_8086&DEV_2821&CC_0106

    Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)
    PCI\VEN_8086&DEV_2829&CC_0106

    Intel(R) ICH9 SATA AHCI Controller (Desktop/Server/Workstation)
    PCI\VEN_8086&DEV_2922&CC_0106

    Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)
    PCI\VEN_8086&DEV_27C3&CC_0104

    Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)
    PCI\VEN_8086&DEV_27C6&CC_0104

    Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)
    PCI\VEN_8086&DEV_282A&CC_0104

    Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)
    PCI\VEN_8086&DEV_2822&CC_0104

    Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)
    PCI\VEN_8086&DEV_2682&CC_0104

    iaStor_8.9.8.1005_Addon.7z

    MD5: 60D614B78376CBCB08EB554D703A86B1
    SHA-1: D2A0F8F598A57FDB648095188819999AD7A36149
    Size: 182 KB
    Build date: 26/03/2022
    Driver Date: 05/04/2010

    Supported device instance IDs:

    PCI\VEN_8086&DEV_2652&CC_0106 (iaAHCI_ICH6R)
    PCI\VEN_8086&DEV_2653&CC_0106 (iaAHCI_ICH6M)
    PCI\VEN_8086&DEV_2681&CC_0106 (iaAHCI_ESB2)
    PCI\VEN_8086&DEV_27C1&CC_0106 (iaAHCI_ICH7R)
    PCI\VEN_8086&DEV_27C5&CC_0106 (iaAHCI_ICH7M)
    PCI\VEN_8086&DEV_2821&CC_0106 (iaAHCI_ICH8R)
    PCI\VEN_8086&DEV_2824&CC_0106 (iaAHCI_ICH8_1)
    PCI\VEN_8086&DEV_2829&CC_0106 (iaAHCI_ICH8M)
    PCI\VEN_8086&DEV_2922&CC_0106 (iaAHCI_ICH9R)
    PCI\VEN_8086&DEV_2923&CC_0106 (iaAHCI_ICH9_1)
    PCI\VEN_8086&DEV_2929&CC_0106 (iaAHCI_ICH9M)
    PCI\VEN_8086&DEV_3A02&CC_0106 (iaAHCI_ICH10D)
    PCI\VEN_8086&DEV_3A22&CC_0106 (iaAHCI_ICH10R)
    PCI\VEN_8086&DEV_3A03&CC_0106 (iaAHCI_ICH10_1)
    PCI\VEN_8086&DEV_3A23&CC_0106 (iaAHCI_ICH10_2)
    PCI\VEN_8086&DEV_3B29&CC_0106 (iaAHCI_5)
    PCI\VEN_8086&DEV_3B2F&CC_0106 (iaAHCI_5_1)
    PCI\VEN_8086&DEV_3B22&CC_0106 (iaAHCI_5_1_1)
    PCI\VEN_8086&DEV_1C02&CC_0106 (iaAHCI_6_Desktop)
    PCI\VEN_8086&DEV_1C03&CC_0106 (iaAHCI_6_Mobile)
    PCI\VEN_8086&DEV_1D02&CC_0106 (iaAHCI_AC600)
    PCI\VEN_8086&DEV_8D02&CC_0106 (iaAHCI_AC600_1)
    PCI\VEN_8086&DEV_8D62&CC_0106 (iaAHCI_AC600_2)
    PCI\VEN_8086&DEV_1F22&CC_0106 (iaAHCI_AC600_3)
    PCI\VEN_8086&DEV_1F32&CC_0106 (iaAHCI_AC600_4)
    PCI\VEN_8086&DEV_0816&CC_0106 (iaAHCI_SM35)
    PCI\VEN_8086&DEV_0F23&CC_0106 (iaAHCI_BAYTR)
    PCI\VEN_8086&DEV_22A3&CC_0106 (iaAHCI_BAYTR_1)
    PCI\VEN_8086&DEV_5AE3&CC_0106 (iaAHCI_APOL)
    PCI\VEN_8086&DEV_1E02&CC_0106 (iaAHCI_7/C216)
    PCI\VEN_8086&DEV_1E03&CC_0106 (iaAHCI_7_1)
    PCI\VEN_8086&DEV_8C02&CC_0106 (iaAHCI_8/C220)
    PCI\VEN_8086&DEV_8C03&CC_0106 (iaAHCI_8_1)
    PCI\VEN_8086&DEV_9C02&CC_0106 (iaAHCI_8_2)
    PCI\VEN_8086&DEV_9C03&CC_0106 (iaAHCI_8_3)
    PCI\VEN_8086&DEV_8C82&CC_0106 (iaAHCI_9)
    PCI\VEN_8086&DEV_8C83&CC_0106 (iaAHCI_9_1)
    PCI\VEN_8086&DEV_9C82&CC_0106 (iaAHCI_9_2)
    PCI\VEN_8086&DEV_9C83&CC_0106 (iaAHCI_9_3)
    PCI\VEN_8086&DEV_9D03&CC_0106 (iaAHCI_9_D)
    PCI\VEN_8086&DEV_A102&CC_0106 (iaAHCI_100)
    PCI\VEN_8086&DEV_A103&CC_0106 (iaAHCI_100_1)
    PCI\VEN_8086&DEV_A282&CC_0106 (iaAHCI_200)
    PCI\VEN_8086&DEV_9DD3&CC_0106 (iaAHCI_9_DD)
    PCI\VEN_8086&DEV_A352&CC_0106 (iaAHCI_300)
    PCI\VEN_8086&DEV_A353&CC_0106 (iaAHCI_300_1)
    PCI\VEN_8086&DEV_2652&CC_0104 (iaStor_ICH6R)
    PCI\VEN_8086&DEV_2682&CC_0104 (iaStor_ESB2)
    PCI\VEN_8086&DEV_27C3&CC_0104 (iaStor_ICH7R)
    PCI\VEN_8086&DEV_27C6&CC_0104 (iaStor_ICH7M)
    PCI\VEN_8086&DEV_2822&CC_0104 (iaStor_Express_D)
    PCI\VEN_8086&DEV_282A&CC_0104 (iaStor_Express_M)
    PCI\VEN_8086&DEV_2826&CC_0104 (iaStor_C600_D)
    PCI\VEN_8086&DEV_2827&CC_0104 (iaStor_C600_M)
    PCI\VEN_8086&DEV_9D07&CC_0104 (iaStor_9_D)
    PCI\VEN_8086&DEV_A106&CC_0104 (iaStor_100)
    PCI\VEN_8086&DEV_A107&CC_0104 (iaStor_100_1)
    PCI\VEN_8086&DEV_A286&CC_0104 (iaStor_200)
    PCI\VEN_8086&DEV_A28E&CC_0104 (iaStor_200_1)
    PCI\VEN_8086&DEV_9DD7&CC_0104 (iaStor_9_DD)
    PCI\VEN_8086&DEV_A356&CC_0104 (iaStor_300)
    PCI\VEN_8086&DEV_A357&CC_0104 (iaStor_300_1)
    PCI\VEN_8086&DEV_2652&CC_0104 (iaStor_ICH6R)
    PCI\VEN_8086&DEV_2682&CC_0104 (iaStor_ESB2)
    PCI\VEN_8086&DEV_27C3&CC_0104 (iaStor_ICH7R)
    PCI\VEN_8086&DEV_27C6&CC_0104 (iaStor_ICH7M)
    PCI\VEN_8086&DEV_2822&CC_0104 (iaStor_Express_D)
    PCI\VEN_8086&DEV_282A&CC_0104 (iaStor_Express_M)
    PCI\VEN_8086&DEV_2826&CC_0104 (iaStor_C600_D)
    PCI\VEN_8086&DEV_2827&CC_0104 (iaStor_C600_M)
    PCI\VEN_8086&DEV_9D07&CC_0104 (iaStor_9_D)
    PCI\VEN_8086&DEV_A106&CC_0104 (iaStor_100)
    PCI\VEN_8086&DEV_A107&CC_0104 (iaStor_100_1)
    PCI\VEN_8086&DEV_A286&CC_0104 (iaStor_200)
    PCI\VEN_8086&DEV_A28E&CC_0104 (iaStor_200_1)
    PCI\VEN_8086&DEV_9DD7&CC_0104 (iaStor_9_DD)
    PCI\VEN_8086&DEV_A356&CC_0104 (iaStor_300)
    PCI\VEN_8086&DEV_A357&CC_0104 (iaStor_300_1)

    iaStor_10.1.0.1008_Addon.7z

    MD5: 79BFC30418DCEF09A1BBC3F1913A3F78
    SHA-1: 50D20703DD7B41D2805BD575F8F0B35538977D1A
    Size: 191 KB
    Build date: 26/03/2022
    Driver Date:05/11/2010

    Supported device instance IDs:

    PCI\VEN_8086&DEV_2681&CC_0106 (ESB2 SATA AHCI Controller)
    PCI\VEN_8086&DEV_27C1&CC_0106 (ICH7R/DH SATA AHCI Controller)
    PCI\VEN_8086&DEV_27C5&CC_0106 (ICH7M/MDH SATA AHCI Controller)
    PCI\VEN_8086&DEV_2821&CC_0106 (ICH8R/DH/DO SATA AHCI Controller)
    PCI\VEN_8086&DEV_2829&CC_0106 (ICH8M-E/M SATA AHCI Controller)
    PCI\VEN_8086&DEV_2922&CC_0106 (ICH9R/DO/DH SATA AHCI Controller)
    PCI\VEN_8086&DEV_2929&CC_0106 (ICH9M-E/M SATA AHCI Controller)
    PCI\VEN_8086&DEV_3A02&CC_0106 (ICH10D/DO SATA AHCI Controller)
    PCI\VEN_8086&DEV_3A22&CC_0106 (ICH10R SATA AHCI Controller)
    PCI\VEN_8086&DEV_3B29&CC_0106 (5 Series 4 Port SATA AHCI Controller)
    PCI\VEN_8086&DEV_3B2F&CC_0106 (5 Series 6 Port SATA AHCI Controller)
    PCI\VEN_8086&DEV_3B22&CC_0106 (5 Series/3400 Series SATA AHCI Controller)
    PCI\VEN_8086&DEV_1C02&CC_0106 (Desktop/Workstation/Server Express Chipset SATA AHCI Controller)
    PCI\VEN_8086&DEV_1C03&CC_0106 (Mobile Express Chipset SATA AHCI Controller)
    PCI\VEN_8086&DEV_2682&CC_0104 (ESB2 SATA RAID Controller)
    PCI\VEN_8086&DEV_27C3&CC_0104 (ICH7R/DH SATA RAID Controller)
    PCI\VEN_8086&DEV_27C6&CC_0104 (ICH7MDH SATA RAID Controller)
    PCI\VEN_8086&DEV_2822&CC_0104 (Desktop/Workstation/Server Express Chipset SATA RAID Controller)
    PCI\VEN_8086&DEV_282A&CC_0104 (Mobile Express Chipset SATA RAID Controller)

    iaStor_11.2.0.1006_Addon.7z

    MD5: 8FD3137FADF0763F548BEF084939E17D
    SHA-1: A542EC16D8D083E04750FC2E4C830373E9C85C06
    Size: 251 KB
    Build date: 26/03/2022

    Supported device instance IDs:

    PCI\VEN_8086&DEV_2681&CC_0106 (iaAHCI_ESB2)
    PCI\VEN_8086&DEV_27C1&CC_0106 (iaAHCI_ICH7R)
    PCI\VEN_8086&DEV_27C5&CC_0106 (iaAHCI_ICH7M)
    PCI\VEN_8086&DEV_2821&CC_0106 (iaAHCI_ICH8R)
    PCI\VEN_8086&DEV_2824&CC_0106 (iaAHCI_ICH8_1)
    PCI\VEN_8086&DEV_2829&CC_0106 (iaAHCI_ICH8M)
    PCI\VEN_8086&DEV_2922&CC_0106 (iaAHCI_ICH9R)
    PCI\VEN_8086&DEV_2923&CC_0106 (iaAHCI_ICH9_1)
    PCI\VEN_8086&DEV_2929&CC_0106 (iaAHCI_ICH9M)
    PCI\VEN_8086&DEV_3A02&CC_0106 (iaAHCI_ICH10D)
    PCI\VEN_8086&DEV_3A03&CC_0106 (iaAHCI_ICH10_1)
    PCI\VEN_8086&DEV_3A22&CC_0106 (iaAHCI_ICH10R)
    PCI\VEN_8086&DEV_3A23&CC_0106 (iaAHCI_ICH10_2)
    PCI\VEN_8086&DEV_3B29&CC_0106 (iaAHCI_5)
    PCI\VEN_8086&DEV_3B2F&CC_0106 (iaAHCI_5_1)
    PCI\VEN_8086&DEV_3B22&CC_0106 (iaAHCI_5_1_1)
    PCI\VEN_8086&DEV_1C02&CC_0106 (iaAHCI_6_Desktop)
    PCI\VEN_8086&DEV_1C03&CC_0106 (iaAHCI_6_Mobile)
    PCI\VEN_8086&DEV_1D02&CC_0106 (iaAHCI_AC600)
    PCI\VEN_8086&DEV_8D02&CC_0106 (iaAHCI_AC600_1)
    PCI\VEN_8086&DEV_8D62&CC_0106 (iaAHCI_AC600_2)
    PCI\VEN_8086&DEV_1F22&CC_0106 (iaAHCI_AC600_3)
    PCI\VEN_8086&DEV_1F32&CC_0106 (iaAHCI_AC600_4)
    PCI\VEN_8086&DEV_0816&CC_0106 (iaAHCI_SM35)
    PCI\VEN_8086&DEV_0F23&CC_0106 (iaAHCI_BAYTR)
    PCI\VEN_8086&DEV_22A3&CC_0106 (iaAHCI_BAYTR_1)
    PCI\VEN_8086&DEV_5AE3&CC_0106 (iaAHCI_APOL)
    PCI\VEN_8086&DEV_31E3&CC_0106 (iaAHCI_GEML)
    PCI\VEN_8086&DEV_1E02&CC_0106 (iaAHCI_7)
    PCI\VEN_8086&DEV_1E03&CC_0106 (iaAHCI_7_1)
    PCI\VEN_8086&DEV_8C02&CC_0106 (iaAHCI_8)
    PCI\VEN_8086&DEV_8C03&CC_0106 (iaAHCI_8_1)
    PCI\VEN_8086&DEV_9C02&CC_0106 (iaAHCI_8_2)
    PCI\VEN_8086&DEV_9C03&CC_0106 (iaAHCI_8_3)
    PCI\VEN_8086&DEV_8C82&CC_0106 (iaAHCI_9)
    PCI\VEN_8086&DEV_8C83&CC_0106 (iaAHCI_9_1)
    PCI\VEN_8086&DEV_9C82&CC_0106 (iaAHCI_9_2)
    PCI\VEN_8086&DEV_9C83&CC_0106 (iaAHCI_9_3)
    PCI\VEN_8086&DEV_9D03&CC_0106 (iaAHCI_9_D)
    PCI\VEN_8086&DEV_A102&CC_0106 (iaAHCI_100)
    PCI\VEN_8086&DEV_A103&CC_0106 (iaAHCI_100_1)
    PCI\VEN_8086&DEV_A282&CC_0106 (iaAHCI_200)
    PCI\VEN_8086&DEV_9DD3&CC_0106 (iaAHCI_9_DD)
    PCI\VEN_8086&DEV_A352&CC_0106 (iaAHCI_300)
    PCI\VEN_8086&DEV_A353&CC_0106 (iaAHCI_300_1)
    PCI\VEN_8086&DEV_34D3&CC_0106 (iaAHCI_300_2)
    PCI\VEN_8086&DEV_02D3&CC_0106 (iaAHCI_400)
    PCI\VEN_8086&DEV_06D2&CC_0106 (iaAHCI_400_1)
    PCI\VEN_8086&DEV_06D3&CC_0106 (iaAHCI_400_2)
    PCI\VEN_8086&DEV_A382&CC_0106 (iaAHCI_400_3)
    PCI\VEN_8086&DEV_43D2&CC_0106 (iaAHCI_500)
    PCI\VEN_8086&DEV_2682&CC_0104 (iaStor_ESB2
    PCI\VEN_8086&DEV_27C3&CC_0104 (iaStor_ICH7R)
    PCI\VEN_8086&DEV_27C6&CC_0104 (iaStor_ICH7M)
    PCI\VEN_8086&DEV_2822&CC_0104 (iaStor_Express_D)
    PCI\VEN_8086&DEV_282A&CC_0104 (iaStor_Express_M)
    PCI\VEN_8086&DEV_2826&CC_0104 (iaStor_C600_D)
    PCI\VEN_8086&DEV_2827&CC_0104 (iaStor_C600_M)
    PCI\VEN_8086&DEV_9D07&CC_0104 (iaStor_9_D)
    PCI\VEN_8086&DEV_A106&CC_0104 (iaStor_100)
    PCI\VEN_8086&DEV_A107&CC_0104 (iaStor_100_1)
    PCI\VEN_8086&DEV_A286&CC_0104 (iaStor_200)
    PCI\VEN_8086&DEV_A28E&CC_0104 (iaStor_200_1)
    PCI\VEN_8086&DEV_9DD7&CC_0104 (iaStor_9_DD)
    PCI\VEN_8086&DEV_A356&CC_0104 (iaStor_300)
    PCI\VEN_8086&DEV_A357&CC_0104 (iaStor_300_1)
    PCI\VEN_8086&DEV_A35E&CC_0104 (iaStor_300_2)
    PCI\VEN_8086&DEV_34D7&CC_0104 (iaStor_400)
    PCI\VEN_8086&DEV_02D7&CC_0104 (iaStor_400_1)
    PCI\VEN_8086&DEV_06D6&CC_0104 (iaStor_400_2)
    PCI\VEN_8086&DEV_06D7&CC_0104 (iaStor_400_3)
    PCI\VEN_8086&DEV_06DE&CC_0104 (iaStor_400_4)
    PCI\VEN_8086&DEV_A386&CC_0104 (iaStor_400_5)
    PCI\VEN_8086&DEV_43D6&CC_0104 (iaStor_500)
    PCI\VEN_8086&DEV_43DE&CC_0104 (iaStor_500_1)

    iaStor_11.2.0.1006_x64_Addon.7z

    MD5: B1CF9B51F905454728BCD0A443A566C7
    SHA-1: 42DE45E13A393B04662D3A6580CCFBA1604B8110
    Size: 283 KB
    Build date: 10/04/2022

    Supported device instance IDs same as above

  3. Microsoft VC7.8.9.10.11.12 Runtime Libraries

    It should be possible to integrate these addons intp 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[2].7z

    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[2].7z

    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

    MD5: 1aefd853fa491fb6c3262fc5cc31efa6
    SHA-1: 10557b429bf2a5fe68523c0a71cba35e929505dc
    SHA-256: 994e2a443a838b1c50bd1df29b60f6a96e633b8ac7e591c4a7fea5e81d2b8158
    Release date: 05/06/2022
    Size: 4.43 MB

    File:  Microsoft_VC14_Runtime_Libraries_Addon_Int.7z

    MD5: 3e97a9c1517ace5176ce53237ecea35c
    SHA-1: 2693b036638ad34c9a5d247283b7c0f304ffa72d
    SHA-256: 6055a9760c9b657c7ab959c66334e38dc7ea8fda0995ec78298f1391f88319a3
    Release date: 05/06/2022
    Size: 4.53 MB

    File: Microsoft_Visual_C++_2015_Minimum_Runtime_Addon.7z

    MD5: 7bd82b607183f7afe7b31291bc1bbfcf
    SHA-1: 8ef2a6d6e5fa94b2fb0368987803c7c67749d768
    SHA-256: 0b6462bf7853ba00b514328aa3aab187812ef474e67629c7931da0d1e8f2b9e9
    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

    MD5: a1a9d36741d0a058700b1f32617d29ce
    SHA-1: fe9423562ef604e93c20985a24af6b6eb228c021
    SHA-256: 6f7c3fbdc394db9a55d196852ed540a6bc7bc16bef1e3ed652c9b45dbc8d79c8
    Release date: 05/06/2022
    Size: 4.54 MB

    File: Microsoft_VC++_2015-19_Redistributable_Addon_Int.7z

    MD5: 1038c38da6fe12a809fcad4da3895b73
    SHA-1: 8ea637722b64ba2ee2b04631ffdd5f0bd1c28b51
    SHA-256: f2e20fac4d7220bb9fe951aad582ba62f1a78d687440a03980dc8ef4c2afebde
    Release date: 05/06/2022
    Size: 4.63 MB

    File: Microsoft_Visual_C++_2015-2019_Minimum_Runtime_Addon.7z

    MD5: f79049b96de6d2873baaf54223a0a4e0
    SHA-1: 74c1eaabf28ba436545cad0b909ff2aa11579581
    SHA-256: 647ad9a655cc8e50e8639aadd31827e4b2f6bac31b6b33a05fcadcbd7273349d
    Release date: 05/06/2022
    Size: 799 KB

     

     

     

  4. 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 7zdn.exe version 16.2 in the plugins\7zip folder.

    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

    MD5: 95E97EA2FC09D318443AA14E3ED20CE8
    SHA-1: 21388005FA71ACA2D254C5AD16D05A148EF31D54
    Release date: 12/02/2022
    Size: 68.7 MB                                                                                                                                                                                                                                                                 

    File: XPSP3_QFE_UpdatePack_20210829_Pro.7z

    MD5: B10F3139428A1517B3CAA45CF5002278
    SHA1: 200C708A79E393E9DB39F43E35AC37EED59563C5
    Release date: 29/08/2021                                                                                                                                                                       
    Size: 68.5 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.

     

    [Addon] XPSP3 QFE POSReady Updates

    XPSP3_QFE_POSReady_Addon_20200820_5er_Pro.7z

    MD5: CF3083C8A3826CB93D4574D5F1655495
    SHA1: 92CC5268EB0924B4F63A6D3E1C1F87EEDD792A68
    SHA256: 65C0D8239B790678DD8F4640A4FB8EC1DC2C2D9711C7F55A453AEC0414D41328
    Release date: 20/08/2020
    Size: 26.0 MB

     

    XPSP3_QFE_POSReady_Addon_20200820_5er_Home.7z

    MD5: CBFC854A54364C4EFEB73C2596D05996
    SHA1: 8D966AE0CA6E7B4C385695F35FA684BCAEFE2148
    SHA256: 439328A3E2342CB635D6EED8A4D840A0694EAFD132D8AD3277C1D5AB34653955
    Release date: 20/08/2020
    Size: 26.0 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.

                                                                                                                                                  

     

    What is included in XPSP3_QFE_UpdatePack_20210829.rtf

  5. On 4/1/2023 at 7:24 PM, AstroSkipper said:

    All Spectre and Meltdown vulnerabilities depend massively on the CPU architecture of the computer that is to be protected.

    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:

    Quote

    An elevation of privilege vulnerability exists in the way that the Windows Kernel API enforces permissions. An attacker who successfully exploited the vulnerability could impersonate processes, interject cross-process communication, or interrupt system functionality.

    To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.

    The security update addresses the vulnerability by helping to ensure that the Windows Kernel API properly enforces permissions.

    KB4056615 has been replaced by KB4463103 which is covered by CVE-2018-8411 whose summary is as follows:

    Quote

    An elevation of privilege vulnerability exists when NTFS improperly checks access. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

    To exploit the vulnerability, an attacker would first have to log on to the system, and then run a specially crafted application to take control over the affected system.

    The security update addresses the vulnerability by correcting how NTFS checks access.

    and is also covered by CVE-2018-8330 whose summary is as follows:

    Quote

    An information disclosure vulnerability exists when the Windows kernel improperly handles objects in memory. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user’s system.

    To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to execute code or to elevate user rights directly, but it could be used to obtain information that could be used to try to further compromise the affected system.

    The update addresses the vulnerability by correcting how the Windows kernel handles objects in memory.

    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.

    • Like 2
  6. 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.

  7. On 4/27/2023 at 11:58 AM, genieautravail said:

    @Zorba the Geek

    In the results of a scan, an error message is displayed:

    |Traceback (most recent call last):
      File "loki.py", line 544, in get_string_matches
    TypeError: 'yara.StringMatch' object is not subscriptable

    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.

  8. 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.

    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

  9. 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.

    Included is my modified source code.

    _psutil_windows.c

  10. On 4/25/2023 at 4:35 PM, genieautravail said:

    @Zorba the Geek

    Your compiled version of LOKI doesn't works on my computer

    Any idea of what happen ?

    Regards

    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.

  11. 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 winxp_python3.6.15-src.zip.  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.

  12. 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.

    • Like 1
  13. 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)

     

     

  14.  

    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.

  15. On 3/3/2023 at 5:18 PM, cmalex said:

    Greetings.

    Please check lib\site-packages\PIL\_imaging.cp38-win32.pyd for "kernel32.dll" strings.

    If there are any - replace them with "kernelxp.dll"

    Best regards.

    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.

  16. 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

  17. 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.

     

  18. 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%.

  19. On 1/16/2023 at 8:16 AM, FranceBB said:

    Otherwise, you can use different protocols, for instance OpenVPN works just fine on XP, you just have to install the client (or rather an older version of the client). Alternatively, you can go for a different protocol like IPSec Xauth PSK by installing the Shrew Soft VPN Client which still runs on XP.

    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.

  20. 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

     

    • Like 1
  21. 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.

    • Like 1
    • Upvote 1


×
×
  • Create New...