Dietmar

Into Windows XP Professional SP3 x86 - Integral Edition 2023.11.26\Patch Integrator v4.0.1\Patches\ACPI drivers

Into Windows\system32\drivers or just change it in Ramsey XP acpi folder Dietmar

@SEDANEH Make a try with this acpi.sys Dietmar https://ufile.io/6l9k08lg

But may be it has to look like this Scope (_PR) { Processor (C000, 0x00, 0x00000410, 0x06){ Name (_HID, "ACPI0007") } }

@Mov AX, 0xDEAD Hi, in DSDT I find this Scope (_PR) { Processor (C000, 0x00, 0x00000410, 0x06){} Processor (C001, 0x01, 0x00000410, 0x06){} Processor (C002, 0x02, 0x00000410, 0x06){} Processor (C003, 0x03, 0x00000410, 0x06){} }

I notice, that no Processor entry is in Device Manager. It is an AMD cpu e2-9000e. And maybe no entry for processor in DSDT, so only 1 cpu ist recogniced, without any acpi Dietmar

This will not help. I succeed to boot XP from USB this crazy HP 255 g6. And get 2 entries in Device-Manager: For Standard PC and Acpi Multiprocessor. But only with Standard PC it boots, Bsod 0x7B with Acpi Multiprocessor. So, there must be something in Bios, what disrupted the arcpath to any boot device, when you choose any acpi on this notebook.

On the HP 255 g6 with any XP SP3 ACPI install, the compi seems to loose any contact to the boot device, no matter if Sata or USB. Independend from the underlying boot device driver. And because of this comes the Bsod 0x7B Dietmar

1 3 5 A C F with ramsey Dietmar

@Mark-XP 1.) Edit Hal entry in registry via regedit to this Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000] "ConfigFlags"=dword:00000000 "Legacy"=dword:00000000 "DeviceReported"=dword:00000001 "Service"="\\Driver\\ACPI_HAL" "HardwareID"=hex(7):61,00,63,00,70,00,69,00,61,00,70,00,69,00,63,00,5f,00,6d,\ 00,70,00,00,00,00,00 "CompatibleIDs"=hex(7):44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,49,00,\ 6e,00,74,00,65,00,72,00,6e,00,61,00,6c,00,5c,00,41,00,43,00,50,00,49,00,5f,\ 00,48,00,41,00,4c,00,00,00,44,00,45,00,54,00,45,00,43,00,54,00,45,00,44,00,\ 5c,00,41,00,43,00,50,00,49,00,5f,00,48,00,41,00,4c,00,00,00,00,00 "Capabilities"=dword:00000000 "ClassGUID"="{4D36E966-E325-11CE-BFC1-08002BE10318}" "Class"="Computer" "Driver"="{4D36E966-E325-11CE-BFC1-08002BE10318}\\0000" "Mfg"="(Standardcomputer)" "DeviceDesc"="ACPI-Multiprocessor-PC" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\LogConf] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\Control] "DeviceReported"=dword:00000001

@Damnation My problem is, that the HP 255 g6 shows Bsod 0x7B with acpi, means that the arcpath cant be found to the boot device. So, no information about the reason for this Bsod during debug. But it depends on acpi, because with "Standard PC" setup of XP works. This is such a strange behavior, because I can see my harddisk for a second at XP-Setup, but then compi shuts down Dietmar

@Mov AX, 0xDEAD Do you have an idea, what XP SP3 acpi.sys not likes in this DSDT from HP 255 g6 Dietmar https://ufile.io/6fb5w13l

@Mov AX, 0xDEAD I also test the brandnew acpi.sys from George King. Exact the same behavior. I can make a try to debug this BSOD via Lan from you, Mov AX, 0xDEAD, possible because it has a supported Realtek Lan chip. But this will be hard work, because I have no working XP SP3, so that I can boot from this XP for to fetch the Bsod.

Hi, I bought for few Euro a notebook from 2017, HP 255 g6, Bios F20 e2-9000e AMD cpu with integrated graphik R2. It is very slow. But there is a graphik driver for XP. It looks, as if there is a problem related to acpi.sys. I only can install XP SP3 on the HP 255 g6, Bios F20 e2-9000e AMD cpu with integrated graphik R2, when hitting F7 F8 during setup in TXT mode. This gives the "Standard PC". No acpi at all. This works. If I try to install in normal Acpi Multiprocessor, I can see for a second the harddisk, but then the compi shuts down. Never I have seen this behavior before. Dietmar

@K4sum1 Just read msfn.org/board/topic/183489-windows-xp2003-x32-on-modern-hardware-faq Dietmar

@K4sum1 In assembler it just jumps over the question, if the PM Timer should be used Dietmar

@canonkong Hi, please tell me, how do you reach this. What motherboard you use? Please send me this Bios, nice Dietmar

Hi, now it is written for Win8. I think, some modifications have to be done and then compile for winsevers 2003, as the OFA driver Dietmar

@George King Here is hal.dll modded only with Timerhack for the last XP SP3 version, good luck Dietmar https://ufile.io/kc0jvres

@George King Here it is, hal.dll x86 2003 Timerhack, now uses always the System Clock of the motherboard, 1 byte hack, Dietmar https://ufile.io/i34ue3zv PS: If the compi cries now, that it is not the original file, open it one time with Resource Hacker and store it again.

@George King I was not fast enough, the file was deleted. Please load it up again on https://ufile.io/ Dietmar

@George King Please send me the hal.dll from x86 Win Server, that you want to be patched. The intelppm.sys, that I send to ramsey works always, independend if you use PAE or not. I found therin a second place, where it has to be patched for to put all the power saving states to D1 Dietmar

@gordo999 Here they are again, good luck Dietmar https://ufile.io/3inwz0ye

@UsefulAGKHelper Here they are, good luck Dietmar https://ufile.io/aurp14da

@66cats Just copy and paste acpi.sys into the Setup folder AMD64 before building the XPSP2bit64.iso via Nlite. No need to compress it there. On reboot of install, acpi.sys is changed back to the original version. Just copy acpi.sys one time more into Windows\system32\drivers. If you dont like, that the acpi.sys is changed back to its original one, you have also to put acpi.sys into SP2.cab folder (of XP bit64 SP2) Dietmar