George King

I will rebuild it in few hours, when I’m back on my PC

I have added only few “improvements” to @Mov AX, 0xDEAD latest release. You can see changelog on GitHub.

UpdatePacks https://www.wincert.net/forum/topic/17130-repack-onepiece-xp-post-sp3-aio-international-update-packs-final-v110/ Embedded UpdatePacks https://www.wincert.net/forum/topic/17131-repack-onepiece-xp-embedded-post-sp3-international-true-addon-v102/

Why not use PAE patcher to allow all 8GB?

@reboot12 Your SourceDiskFiles section is not correct according to documentation. https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-sourcedisksfiles-section [SourceDisksFiles] | [SourceDisksFiles.x86] | [SourceDisksFiles.ia64] | (Windows XP and later versions of Windows) [SourceDisksFiles.amd64] | (Windows XP and later versions of Windows) [SourceDisksFiles.arm] | (Windows 8 and later versions of Windows) [SourceDisksFiles.arm64] (Windows 10 version 1709 and later versions of Windows)

[nvme_inst.NTx86.CopyFiles] should be probably [nvme_inst.NTamd64.CopyFiles] is true, then it should work.

@reboot12 There is really newer ported drivers collection here

Maybe it depends on storport version?

@Dietmar I have added mentioned fix to both source trees, here are updated files for XP and 2003 https://www.mediafire.com/file/cboxm3x9ctb9i1u/ACPI_7777.6_x86+x64_5.1+5.2.7z/file

@legacyfan Do you need specific language? I have full repo

@Dietmar Can you please try this latest acpi on Optiplex 780? And if there is still BSOD, can you post logs for @Mov AX, 0xDEAD please? I hope we can get one universal ACPI without needs of swaping with original one.

Here are mentioned files https://www.mediafire.com/file/kfx9dyt90fb856e/acpi_x86_x64_7777.6.7z/file

@Dietmar @Damnation I have compiled 5.2 x86 and x64 too. Let me know if you want to test it too.

@Dietmar @Damnation Here is compiled files with latest changes https://www.mediafire.com/file/ej2amz70wf4lpyl/acpi_x86_5.1.2600.7777.6.7z/file

Hi @Mov AX, 0xDEAD, I have just added your fix to my source tree, I was comparing dat.c in Win2k3 vs XPSP1 and there is difference. 2k3 dat.c have ACPI0004 and XP ACPI0006. Is this difference OK? @Damnation @Dietmar Here is compiled file https://www.mediafire.com/file/ej2amz70wf4lpyl/acpi_x86_5.1.2600.7777.6.7z/file

XP2ESD have added better UEFI support for XP / 2003 x64, but new version (v1.6.3) is still not released to public and it needs to be tested a lot. You can follow @reboot12 tutorial hwo to deploy XP x64 on UEFI manually.

Latest ported drivers repository builded for XP2ESD as DriverPack. Compatible with XP and 2003. No prereqs needed, every driver is standalone x64 AMD_RAID_6.1.5.00025 AMD_SATA_1.2.001.0337 AMD_SATA_1.2.001.0402 AMD_SD+MMC_1.0.0.0106 AMD_USB3_1.1.0.0145 Generic_AHCI_1.0 Generic_AHCI_6.2.9200.20652 Generic_MSAHCI_6.1.7601.25735 Generic_NVMe_1.3.1014.00 Generic_NVMe_1.5.1200.00 Generic_NVMe_10.4.49.0 Generic_NVMe_6.1.7601.23403 Generic_SD+MMC_6.2.8056.0 Generic_Touchpad_6.2.9200.16384 Generic_UASP_6.1.7600.4002 Generic_UASP_6.2.9200.16384 Generic_USB2_5.2.3790.5203 Generic_USB3x_6.2.9200.21180 Generic_USBMassStorage_5.2.3790.5829 IRST_16.8.3.1003 IRST_18.36.3.1019 RSTe_4.7.0.1119 Samsung_NVMe_3.3.0.2003 TPM_6.1.7600.16385 WinUSB_6.2.9200.16384 x86 AMD_RAID_6.1.5.00025 AMD_SATA_1.2.001.0337 AMD_SATA_1.2.001.0402 AMD_SD+MMC_1.0.0.0106 AMD_USB3_1.1.0.0145 Generic_AHCI_1.0 Generic_AHCI_6.2.9200.20652 Generic_Disk_5.2.3790.4171 Generic_MSAHCI 6.1.7601.25735 Generic_NVMe_1.3.1014.00 Generic_NVMe_1.5.1200.00 Generic_NVMe_10.4.49.0 Generic_NVMe_6.1.7601.23403 Generic_SD+MMC_6.2.8056.0 Generic_Touchpad_6.2.9200.16384 Generic_UASP_6.1.7600.4002 Generic_UASP_6.2.9200.16384 Generic_USB2_5.2.3790.5203 Generic_USB3x_6.2.9200.21180 Generic_USBMassStorage_5.2.3790.5829 IRST_16.8.2.1002 RSTe_4.7.0.1119 Samsung_NVMe_3.3.0.2003 TPM_6.1.7600.16385 WinUSB_6.2.9200.16384 Download https://www.mediafire.com/file/dap6k6n96t27l1a/DP_Ported_DriversCollection_v24.7z/file These files are also signed with custom XP2ESD certificate. If you want to see them as signed, just import certificate into system. Run from CMD these commands reg add "HKLM\SOFTWARE\Microsoft\SystemCertificates\Root\Certificates\2516FF09B7786B05CBB7B96B97690821A13B36AF" /v "Blob" /t REG_BINARY /d "5C0000000100000004000000000800000300000001000000140000002516FF09B7786B05CBB7B96B97690821A13B36AF1900000001000000100000006604E2B4AF8E1E311D7D01577BADCE9C14000000010000001400000001A43F9D5BAEBFE4D86C9D007514AA094103C73A0F000000010000001400000080F75388C42C3A5209BC64307A711CE8E258BFFF04000000010000001000000029A595DC50B71061B554EB3F74A2BCED20000000010000001E0400003082041A30820306A00302010202109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D050030543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D060355040313065850324553443020170D3231313233313232303030305A180F32323231313233313232303030305A30543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534430820122300D06092A864886F70D01010105000382010F003082010A0282010100DC0EAF99F8FD61A19AC1B151DA02347897480373974B34E464C9896298FD513183C31BE742059BF7493A428C0B899F948F432B2EEAE29A617ADE75AEE6D7FBF0055AF5A6944B1AE427551553C05319E2B65301EDC6E7DC03159CDD228129058FFB46EBF26B871B5A1546B158EA8006744BA12DAEAE49BF266ADE97166BCDE424C43E7AE4E951BBFE8F6CA3AAA9A692851B5E5F91409B2071EECE7F5BF2EE372FA40D4DB30FF43062363F8CE499F5960350B49ECFB72559C234A356ABC97F300E7F6389C31A622294707E8143DC219E3A0BBCED4AD5C7A6DE2A44B65587D7FB5E898326C2905D4546EACAFF0A579A8643D99E58410623492DB4535F7502060CB90203010001A381ED3081EA300F0603551D130101FF040530030101FF304F0603551D250448304606082B06010505070303060A2B0601040182370A0305060A2B0601040182370A0306060A2B0601040182370A0307060A2B0601040182370A0308060A2B0601040182370A03093081850603551D01047E307C80106E13AE59A3D4C6AB69BD5A699E28E3F3A15630543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534482109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D0500038201010033C95C0CB8471EB54CB8DA1B176178F8ADA702DB79FAD0447A2B2E2D5C26143198C643E0F7A566B7A6D7B148A0FD72ABD762B7BCF7B46DF55C5BF5905C53CD3CA6DD4E12DA2AFC2E1355A4AD1658DA3D875E0C33C37C680B3D8E7D057F0183A6458D03B16EBC7D4155B26930EAAA0629E4FAC432DE31A848706DD5BB3D66EDC8E3DE5ED2D17F515EB810B1856B906C8714CC72EF8F8A91813EF65CD3224923ADBD4FD08FBE8147C11AF4D9CF047698E870B3F698B490F4C639713DBE31CBE51334783D8EE325CE803438B6E959F5466BA3B178448569864CE3542B7C31E76A81857993CFB3D6C1818C8D357E4A0B19DBE3DDDC8739A02D2A883C89F0923EBA6A" /f reg add "HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\B9B6F07ACD8C0A29597BB2AC1EECF59D046697A7" /v "Blob" /t REG_BINARY /d "030000000100000014000000B9B6F07ACD8C0A29597BB2AC1EECF59D046697A75C00000001000000040000000008000019000000010000001000000027114C6CAC4F2A0B4B6D0B1D3FD888AA140000000100000014000000EC77C51CB1021AD6278248DD8D6D474DF123699A0F00000001000000140000007C2BE80346DA6933211FB3E086D2D373454DEF48040000000100000010000000AA5FE38C7A8D84E83EC756AEAB36705920000000010000001B0400003082041730820303A0030201020210AA944720F0F0E89A4C7925C5BD795FDE300906052B0E03021D050030543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D060355040313065850324553443020170D3231313233313232303030305A180F32323231313233313232303030305A30543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534430820122300D06092A864886F70D01010105000382010F003082010A0282010100F0C27E766F7D27BC2BA2CC1B3E0A6E7434589F51AF1554A37BE1C23939B54E601DB393A14C3A223EFD61A47973E1093C1810BCF0298A2D4603684EA80CB5ED303C7D20094CCFFBE903EFA0CDF9FB29CF3F9CFD04E820494100E8E72C2719ED983202DAA59C2FB1DEC68AECBA724DE40173FEBDF9C8D20918538DDEDD7DEF033B69EB584B547910C69166953EF08E226FE26B02310975929C7862AF41B0739C0463A7356988E13AA396DC87195B1744D10EA59E1449F6DA6A6D536F423C81F325870756FBE54BCB0B1A7F8A0B4E165B730CC5A4A1C464CAF6257EB3575ECC38077A8334BF11C7561AF1A8F16D6A570ACD1343510329F6AAB6EF96741FCE7E58E50203010001A381EA3081E7300C0603551D130101FF04023000304F0603551D250448304606082B06010505070303060A2B0601040182370A0305060A2B0601040182370A0306060A2B0601040182370A0307060A2B0601040182370A0308060A2B0601040182370A03093081850603551D01047E307C80106E13AE59A3D4C6AB69BD5A699E28E3F3A15630543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534482109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D050003820101000307298CCD1B761CAEDAABD7BC51E6528CE75CCB8F99C1092146C0E1589CD900D713F3EF97B18B3B43FADE02403F36EEAE7EAE1DD100F1A005F14F095D55653F35A4A44AAA00837DADB5E985388987D9798331AC8A1AB78CA13F457C110B0A87ACC98D3288E482AA403055D4119066C9384DB0A8646A399202117FFE9098DE5B6E9FCF59DD3D2A1050086C52009D5C80A8D677F1FDE7CF2C9B0F2ED11FE847B9DA132A9D9DCE584CC28CB694DC661CFD8F7C2BDB9ECAAA970D191655C327C819F3AB93D4EADBAF67B8B1CF5C2BC4D50944E9ED46CB6584BAC6E70D7F1FFADC72ACC2CCFECFAF1404902174EE0C6620A619F178238DF70D9EFE09E92500E29A1E" /f

Latest available version https://www.mediafire.com/file/dljs87jh26n0y1x/acpi+7777.5+-+2022.05.13.7z/file

You can also try XP2ESD, all 24 languages ISO images are supported as input.

Use patch from @daniel_k for Windows XP SP3 x86 in any language. https://forums.mydigitallife.net/threads/drivers-and-tools-to-run-windows-xp-on-newer-hardware.81607/ For Windows Server 2003 SP2 x86 or newer use PatchPAE3 https://github.com/evgen-b/PatchPAE3

I have solved it in XP2ESD v1.6.1. Now Windows XP SP2 x64 images created by XP2ESD have same OOBE as x86 XP.

@Dietmar Can you debug current ACPI on problematic Dell Optiplex 780 as we discussed before? It would be great if it can be easily fixed. I know we can use untouched ACPI from SP3 on this machine, but to get one universal ACPI it would be great to report it here and @Mov AX, 0xDEAD can review it.

As you already have XP2ESD, you can grab them from there. XP2ESD\apps\ntfs2btrfs contains ntfs2btrfs-xp.exe. In architecture dependent folders are standalone files that works inside Windows 7 WinPE. Quibble is in XP2ESD\apps\Quibble, it's same as can be found on GitHub. BTRFS driver that have no missing exports under XP is v1.7.7, can be downloaded from GitHub. I have already requested from @CaptainKirk1966 new compilation of BTRFS driver and NTFS2BTRFS. Let's see if he can do that again. Otherwise it can be probably done in VisualStudio 2019 with XP targeting, but I have never tried it. With current Quibble + BTRFS driver v1.7.7 + ntfs2btrfs from XP2ESD it could be done probably. Of course newer files should be better.

I have updated my fork of NTOSKRNL_Emu by @Mov AX, 0xDEAD repository on GitHub to v12, I hope it can work without issues. https://github.com/GeorgeK1ng/NTOSKRNL_Emu ChangeLog v11 changes 1) Added Windows 7 ntoskrnl.exe v6.1.7601.25920 (win7sp1_ldr_escrow.220316-1740) exports x64 EtwSetInformation FsRtlPrepareToReuseEcp FsRtlRegisterUncProviderEx2 IoEnumerateRegisteredFiltersListEx IoRegisterFsRegistrationChangeMountAwareEx KeConnectInterruptForHal KeFlushCurrentTbImmediately PsDereferenceKernelStack PsReferenceKernelStack RtlIsSandboxedToken SeGetLogonSessionToken x86 EtwSetInformation FsRtlPrepareToReuseEcp FsRtlRegisterUncProviderEx2 IoEnumerateRegisteredFiltersListEx IoRegisterFsRegistrationChangeMountAwareEx KeConnectInterruptForHal KiMcaExceptionHandlerWrapper PsDereferenceKernelStack PsReferenceKernelStack RtlIsSandboxedToken SeGetLogonSessionToken 2) Added Windows Vista ntoskrnl.exe v6.0.6003.21442 (vistasp2_ldr_escrow.220307-1719) exports x64 FsRtlInitializeExtraCreateParameter FsRtlInitializeExtraCreateParameterList FsRtlPrepareToReuseEcp FsRtlRegisterUncProviderEx2 IoRegisterFsRegistrationChangeMountAware KeConnectInterruptForHal KeFlushCurrentTbImmediately PsDereferenceKernelStack PsReferenceKernelStack RtlIsSandboxedToken x86 FsRtlInitializeExtraCreateParameter FsRtlInitializeExtraCreateParameterList FsRtlPrepareToReuseEcp FsRtlRegisterUncProviderEx2 IoRegisterFsRegistrationChangeMountAware KeConnectInterruptForHal KiMcaExceptionHandlerWrapper PsDereferenceKernelStack PsReferenceKernelStack RtlIsSandboxedToken 3) Added IoSynchronousCallDriver by Mov AX, 0xDEAD, https://msfn.org/board/topic/181615-ntoskrnl-emu_extender-for-windows-xp2003/?do=findComment&comment=1221893 4) Added blank stubs (to fix missing imports) to allow porting Windows 8.0 Build 8056 Generic SD+MMC driver run under XP - 7. Proper code needs to be added, but currently driver starts and work without issues PoFxRegisterDevice PoFxUnregisterDevice PoFxSetComponentLatency PoFxSetComponentResidency PoFxStartDevicePowerManagement PoFxCompleteIdleState PoFxCompleteIdleCondition PoFxReportDevicePoweredOn PoFxCompleteDevicePowerNotRequired PoFxActivateComponent PoFxIdleComponent 5) Added changes from pappyN4 repository, https://github.com/pappyN4/NTOSKRNL_Emu Added RtlInitAnsiStringEx, RtlInitUnicodeStringEx. Updated Readme v12 changes 1) Added memcmp to be able to port AMD RCRAID driver. Source code comes from https://stackoverflow.com/questions/5017659/implementing-memcmp 2) Added MmMapIoSpaceEx which return MmMapIoSpace, according to MS documentation it should work https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-mmmapiospaceex https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-mmmapiospace 3) Added RtlDowncaseUnicodeChar

No issue on WinRAR 6.01