Dietmar

@Damnation Send me your wished tables, which you want to upload. I upload them to my Registry and make an *.reg file from them. Only risk for you can be, that your XP installation may be destroyed after, when you install this *.reg file. For to overcome this risk, make from an outstanding Windows a copy of your system32 folder and rename this copy to system32rett. When something went wrong, you just choose this system32rett, delete damaged system32, and rename it system32rett to system32 Dietmar

@Damnation Where is limit in the sky, I just succeed to upload a different DSDT without any asl.exe to registry , and indeed THIS new DSDT is loaded from XP SP3 after reboot, and stays there until I delete it by hand from registry.. Dietmar EDIT: This overcomes any signing limits or versions limit of the DSDT. I also "succeed" to upload the DSDT and SSDT from the z690 Asrock Extreme board to the z370 Asrock gaming k6 board a, only mistake I see then is, that suddently the i8700k cpu of the Asrock k6 board has 24 cores^^..

@Damnation Here is the compare of HKLM from XP SP3 without ASL (named ORI) and with ASL. You can see, that asl.exe does a very simple job. Some is there with Cryptographie, which I dont understand. But mostly asl.exe puts the table DSDT in this key [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ACPI\Parameters\DSDT\ALASKA\A_M_I_\01072009] So, any with asl.exe uploaded DSDT and also SSDT comes into ControlSet001\Services\ACPI\Parameters\DSDT ControlSet001\Services\ACPI\Parameters\SSDT Dietmar https://ufile.io/v4btld4z

@Damnation Oh, soso much fun. With a ram boot XP I extract the whole registry HKLM. Editor needs even in ram some time for to open this 52 Mbyte *.reg file. And then I let asl.exe upload its tables and read again whole HKLM out. Before reboot I compare both registries then with Beyond Compare 2 Dietmar

@Damnation I think, even without the asl.exe tool you can add the acpi tables by hand to registry. This I will try now. My only problem in this is, how to translate the Hex *.reg outread from Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\HARDWARE\ACPI\DSDT because this outread contains "," and linebreaks instead of pur hex code Dietmar

@Damnation The asl.exe has a BIG downside: ALWAYS test your dsdt.aml files with another methode before!!! Because when your DSDT or SSDT has an error, asl.exe uploads this fatal table also to the Registry of your XP and makes XP unbootable Dietmar From Microsoft: Using the Microsoft ASL compiler's ACPI-table-load feature During system development, it is useful to have a way to simulate various ACPI BIOS constructs and test them on the development system. The Windows operating system allows certain ACPI tables to be loaded from the Windows registry instead of from the PC's BIOS ROM. Use of this feature requires administrator privileges, and also requires that test signing be enabled on the system. For systems that support UEFI Secure Boot, test signing cannot be enabled, and the compiler's table-load feature cannot be used unless UEFI Secure Boot is disabled or the Windows Debug Policy is installed on the system. To use the table-load feature, the ACPI table to be overloaded must meet the following requirements: The table to be overloaded must already be present in the system's BIOS ROM. For instance, the DSDT can be overloaded; however, if the machine does not have an SSDT, you cannot force an SSDT to be loaded from this registry override mechanism. The table must contain AML code that is normally consumed by the Windows ACPI interpreter (the Acpi.sys driver). The table with the highest version number will be loaded. The table loaded into the registry for testing must have a higher version number than the same table in the BIOS ROM. The table to be loaded must be in compiled (AML) format and loaded into the registry in the correct location, with the correct parameters specified. The mechanism described herein is designed to handle all aspects of loading the table and configuring the registry.

@Damnation I think, the table that you want to upload has to be newer than the table, that is already in use Dietmar

@Damnation This asl.exe Tool is easy to use: 1.) Put asl.exe to the root of your XP, means copy it to C:\ 2.) Copy your compiled Acpi tables also to C:\ for example dsdt.aml . 3.) Type then at command line C:\asl /loadtable dsdt.aml 4.) After reboot, this new dsdt table, which is stored in Registry, is loaded from XP. 5.) For to unload this dsdt table type at commandline C:\asl /loadtable -d dsdt.aml 6.) After next reboot the original dsdt table from Bios is loaded. 7.) For ssdt1 table etc. you do the same, just load one table after the other with asl. 8.) Nothing is changed on your motherboard, because the tables are only stored in Registry of your Hardddisk with XP. 9.) I do not think, that this works for Server 2003, because this one takes its acpi tables always from Bios and not from Registry, so the DSDT upload patcher from @Mov AX, 0xDEAD or the grub2 from you should work Dietmar asl.exe Version 5 https://ufile.io/y8e5iz3r

@Damnation The asl.exe V5 works also. The advantage from this tool is, that under XP SP3 the modified tables are stored in Registry and you dont need to upload them always new Dietmar

@Damnation Can you see a difference in the DSDT tables beween the power cores and the "efficient" cores of the 12900k cpu? The 12900k cpu has 8 Power cores with Hyperthreading, shows 16 "cpus" and 8 efficient cores, so all together 24, which numbers are NOW shown correct in processors Dietmar

@Damnation Waaaoohhh , now we need Tutorial, how to make this Dietmar PS: Power consumption goes down from 44 Watt --> 1.6 Watt. This I like a lot, because in this winter here in germany people will die because no money for HEATING! Asrock Extreme z690 with 12900k cpu before DSDT mod from @Damnation after

@Damnation Yes, this is the board which consumes a lot of power for nothing. The same is true for all the other z690 boards, which I have. But this board is the most XP friendly board and stable. When you have mood for, I am happy when you make a try for to modd the DSDT files and I will report then Dietmar PS: Now we 3 possibilities to upload acpi tables.

@Damnation Here they are, from the Asrock z690 Extreme, which is for me the most most XP friendly board. I use latest iasl from March 2022 and extract under win10 Dietmar https://ufile.io/piqd5ke6

@Damnation Oh, we are all blind as much as possible. I just check the asl.exe Tool V5 from Microsoft. It works also, IF you dump and modify the DSDT files from running XP. If you are as "clever" as me, extract DSDT from Bios, modify it and upload it then, with any of the 3 methods you are forced to flash the Bios with this DSDT or you get always this acpi.sys error. Really crazy, I spend hours and hours with flashing Bios only because of this mistake^^ Dietmar PS: Here is the asl V5 tool. It works, I just test^^ https://ufile.io/rtk8elu3

@Damnation Yessssaaa grub2 works for to upload any DSDT table Dietmar

@Damnation Ok, now the @Mov AX, 0xDEAD DSDT patcher works for me, very first time that I succeed to upload an own DSDT on boottime to XP. Now comes your grub2 for to test Dietmar

@Damnation After crazy experience with the Tutorial from @Mov AX, 0xDEAD I succeed to load my DSDT with his patcher. Crazy, first I need to understand, that his reload.bin is nothing other then the binary file dsdt.aml . And voila, I get the same(!) acpi.sys error as with the grub2 methode. Now I think, after a short comment from @Mov AX, 0xDEAD, that it depends on the dsdt.aml itself. You are not allowed to take it direct from the Bios. Instead of this you have to take it from running XP. Ok, next try and may be that via this way I also get the Microsoft tool asl.exe to work Dietmar

@Damnation Yes, I can see my file dsdt.aml there. But when I boot XP, it gives me the same acpi.sys error. So, this methode seems to work only on AMD boards. I will try the Tutorial from @Mov AX, 0xDEAD Dietmar

@Damnation How do you boot your compi after grub> acpi (hd0,2)/acpi/dsdt.aml And the dsdt.aml is NOT the dsdt.dsl renamed file? I think, that dsdt.aml has to be the binary file which you get after iasl runs over dsdt.dsl. I have no idea what I can do more here with ETB Dietmar

@Damnation I think, that I did all, as you describe. From the Webside, I fetch the original Bios 3.2 for the Asrock z370 k6 gaming board, and extract from it its original DSDT with UEFITool. This Dsdt is different from my on this PC, because I make my DSDT by hand XP and USB3 friendly. Then I boot with the Kingston USB stick in legacy mode (not UEFI). Before I make on the second partition of this stick a folder named acpi and put into it the original bin version of dsdt.aml. Then I type grub> acpi (hd0,2)/acpi/dsdt.aml check about missing spaces etc. Crazy, even I choose the german keyboard, now it becomes English keyboard. Ok. On first boot I got error because of acpi.sys. Then I choose my brandnew modded acpi.sys with hack against all A5 03 and A5 011 Bosods. This time I get Bsod 0x7b, so something does not work with this tool. This remembers me a lot at the Microsoft asl.exe tool. With that tool, the behavior was exact the same as now with this E2B tool Dietmar PS: I think, I have to use the DSDT load methode from @Mov AX, 0xDEAD, even the Tutorial for that is a little bit crazy. EDIT: I load its own dsdt.aml from which I know to 100% that it works. And E2B gives again acpi.sys error, so for sure this does not work for me.

@Damnation With acpidump -b I get only DSDT FACP etc. tables but not any ssdt. When I use Rw Everything and make a check between te generates DSDT.bin and the DSDT.raw which I fetch direct from my Bios, I get 34 differences, which should be forbidden in any case or XP changes its DSDT after loading from Bios. So my question is, HOW to get all the acpi tables, with which my XP is actually working? And which role plays RW Everything, does it give the actual all Acpitables, which XP is working with or does it make a copy from Bios? Copy from Bios should be impossible for RWEverything, because in this case my both binary files for DSDT should be identic Dietmar

@Damnation And next question: With which tool and with which version of Windows you read the DSDT files out? And with which version of Iasl you make back again a working dsdt.aml from them Dietmar

@Damnation When you write this at commandline grub> acpi (hd0,2)/acpi/dsdt.aml grub> acpi (hd0,2)/acpi/ssdt2.aml grub> acpi (hd0,2)/acpi/ssdt3.aml grub> acpi (hd0,2)/acpi/ssdt6.aml and then boot XP and it worked where are those files stored? Do you make a 2. partition on your harddisk and into a folder named acpi you put them all? And is (hd0) your harddisk, from where windows starts? This may depend on the kind of the USB stick and/or at which place in Bios the boot place for the harddisk is Dietmar

@Damnation Even my System fullfilles everything, that is written on the E2B homepage for XP install, it hangs after install at the step when looking for Internet for to download the missing files, telling "ok" and then hangs exact at the check for the second partition, even it is there. Ok, for this moment I give up setup during XP. With Win10 I get error 4 at the end, what ever this mean. When I restart from this USB stick, the Live menu with Agfm is shown to me at second place from the menu. Ok, when I click on it, I get this screen. How to come to the commandline, where you put commands for use of external DSDT and SSDTs in? Dietmar EDIT: I found, just hitting F5 and then choose grub console. Then I get this picture, ist it the same as yours?

@Damnation To prepare this USB stick under XP should work, according to this: Updating under Windows XP/7/8 If you don’t have a Windows 10 system you can run the Install_agFM.exe utility (see eBook #4 for download) After you have made the E2B drive using Make_E2B.exe (make a two-partition USB drive), you then run Install agFM.exe which performs the following actions: 1. Asks the user for the USB drive number – DO NOT ENTER THE WRONG DRIVE NUMBER! 2. Deletes the second partition on the chosen drive 3. Creates a new FAT32 second partition using the remaining space (Z:) 4. Re-orders the first and second partition so that partition 2 is now accessible as drive Z: 5. Downloads the currently released of agFM and extracts the files to the second partition 6. Re-orders the first and second partitions back to their original order 7. Re-assigns a drive letter to partition 1