Dietmar

@Damnation Geekbench 2.4 bit32 is nice. Or you can just use the tip from @Mov AX, 0xDEAD and take 7zip bit32 time compress for a large folder, full with different files Dietmar

@Damnation Do you make some Benchmark tests with the old acpi.sys and the new one on XP SP3? How is power consumption now on your board Dietmar

@Mov AX, 0xDEAD I found out, what happens. The old acpi.sys and also after my Bios Mod, XP SP3 uses only the 8 power cpu cores with 16 threads. But the new acpi.sys for XP SP3 makes use of the 8+8 cores with 24 threads! And the Win10 version, bit 64 version 1803 also uses only the 8 power cores Dietmar

@Mov AX, 0xDEAD I cant install Win7 SP1 , win8.1 , win10 all bit 32 versions on the Asrock Extreme z690 board. Just now I remembered my tries from before on that board, also without success. So I tried an already installed win7 SP1, win8.1 32 bit. Both crash and on repair mode no input is possible at all Dietmar PS: I check other benchmarks under XP SP3 also. Now with this new acpi.sys, they are all about 30% faster than with old acpi.sys or modded Bios. EDIT: So I use win10 bit64 on the Asrock z690 Extreme board with 12900k cpu. Results: Cinebench 11.5 bit32 XP SP3 43 points win10 29 points win10 22H2 39 points with 24 cores with 7 zip compress of whole system32 folder (1.3 Gbyte) on Optane drive XP SP3 46 sec Win10 68 sec bit32 7zip, 69 sec bit64 7zip 72sec Windows 10 22H2 with 24 cores(!) geekbench2.4 XP SP3 37428 Win10 31900 Interesting is also the power consumption: Under win10 bit64 it also reaches 250 Watt with prime95 and with zero load 29 Watt. This is about double as with my modded Bios under XP, thanks to @Damnation. 2000000! with Mathematica 5.0 on this nice XP SP3 on Optane 905P 27 sec. 2000000! with Mathematica 5.0 on i920 cpu, XP SP3 needs 62 sec on my daily compi, also nice.

@Mov AX, 0xDEAD @George King @Damnation Waaoooh, this acpi.sys counts the cpu's correct!!! I have never seen an 12900k running faster. Power consumption is now 25 Watt with zero loading. And with Benchmark it reaches 250 Watt. But this is the by far best benchmark result for Geekbench 2 until now for XP Dietmar PS: With my modded Bios, this cpu is not so fast, 36% less but also less Watt. @Mov AX, 0xDEAD Any idea, why this happens?

@Mov AX, 0xDEAD @George King @Damnation I make some more tests with the new acpi.sys. First I notice, that the DSDT in Bios 9.04 and 10.04 for the Asrock z690 Extreme board are exact the same. Then I modd this 10.04 Bios the way I did before, for to get the old processor definition. After reboot, I get with the new acpi.sys Bsod 0xA5 (0x11, 0x08, xxx, yyy), know acpi crash because of error in _AMLILoadDDB() . Ok, quick dirty hack in the new acpi.sys with IDAPro with 90 90 to go over this Bsod. Now, compi starts with new acpi.sys, showing the correct 24 cores for the 12900k cpu (8+8). But now comes the most crazy: The speed of the cpu now again only 100%, as before. Power consumption nearly zero with 0% load and maximum <200 Watt via Prime95. This means: Even not all is correct with the new acpi.sys, the processor definition there in gives a jump in cpu power + 36%(!) under XP. I checked this with different benchmarks Dietmar This new acpi.sys https://ufile.io/d82p7icl

@Mov AX, 0xDEAD @George King @Damnation The new acpi.sys with new processor definition works on my Asrock z690 Extreme board with 12900k cpu. But it shows not correct the numbers of cores and cpu's in Device Manager. Core Temp shows 16 cores and 32 threads, CPU-Z shows correct 8+8 cores. With my modified Bios, XP gives Bsod with this acpi.sys. So I flash the original brandnew Bios 10.4 from Asrock Webside for this board Dietmar PS: It looks, as if processors are counted double: This cpu has 24 threads, Device Manager shows 48. Power consumption is now 25 Watt with 0% load of each core. Those 25 Watt are much higher than it was with my modded Bios. EDIT: But the most interesting is: ALL benchmarks show an increase from 100% => 136% (!!!). So i think, those different benchmarks are real. In this case, power consumption reaches 250 Watt. My cooler Dark Rock Pro4 can handle this just at its limit, temperature on all cores go up to 91 degrees Celsius, without any throtteling. The cpu Benchmarks show an unbelievable +36%(!) increase.

@ragnargd Motherboard needs to have in Bios CSM enable possibility. Today I found a board from MSI pro b660m-p ddr4 which has CSM in its Bios, but you cant enable it. So, until now no possibility to install XP SP3, win7 32bit, win8 32bit there. I think, all the Microsoft OSs with bit32 need CSM. No graphik driver for >geforce 980 under XP. No lan driver for Intel >i218 and for Realtek only Lan with 1Gb. Sound works for Realtek until 1200 with driver R2.74. This limits you can overcome with PCIe Slot cards, only CSM has to be there. There is a program called Quibble for to overcome this. For me, it does not work. For Sata, until now always Kai Schtroms Sata driver works. The from @Mov AX, 0xDEAD modded Microsoft driver for USB3 from Win8 works on about 80% from boards. This nice USB driver works also on boards with win7 or win8. Nvme 1.3 from Kai or the modded Microsoft 8 nvme driver from @daniel_k work everywhere. The acpi.sys for XP SP3 drivers work on about 99% of all boards, on more boards than win7 or win8 and even win10(!) support. Until now I have no motherboard, where XP not works Dietmar

@we3fan Yepp, I tested a lot of different xp.iso CDs, all work Dietmar

I found this https://github.com/jeremitu/PatchPae2 and https://ufile.io/su0lnnvh Has somebody tested it, if it is stable Dietmar

Hi, I just test win7 SP1, win8.1 on the Gigabyte z690 UD DDR4 board, both bit32 versions. In win7 SP1 I have to change the acpi.sys against my modded version, because it shows Acpi A5 BSOD during install. The for XP modded USB3 driver works there. But compi is slow. A check shows, that only 790 MB ram are free, the same for win8.1. Any idea, for to get more ram Dietmar

@Computer511212 You can take your original XP CD, name it to the *.iso from Ramsey in the folder and integrate all the needed driver. This is a fantastic possibility of the Ramsey XP Patch Integrator Dietmar PS: Later you update it with all the Posready Updates using this: https://legacyupdate.net/

@Damnation I also cant find the DSDT table in this Bios from ASRock QC6000M . May be, that you can extract it on running compi via RWEverything or acpidump -b Dietmar PS: Do you find a speed compare of the cpu? Interesting board.

@Damnation In win98 you can disable any acpi with the setup /P i switch. Interesting board, for all its devices there are XP SP3 driver, sound, lan .. And Bios is from 2020. I just check, if there are Acpi2.0 orders in their DSDT Dietmar

And here is the same tested Bios Mod for XP for to show processors in Device Manager and bring power consumption down as max as possible and no more "1000" unknown devices there, for the MSI z690-A Pro board. Procedure is the same: Copy only MSI.ROM (BIG letters) to an fresh with Fat32 formatted USB stick and put it into the MSI board, very left down, and press the Flash botton, left direct next Dietmar Biosflash is always a risk. So no garantie. For me it works. https://ufile.io/qr41nwzc You can easy go back to original Bios from webside, copy for this the original Bios to the USB stick and rename the original Bios there to MSI.ROM .

Hi, look for Ramsey XP Dietmar

You can easy go back to your original Bios: Just copy the Original Bios from Webside on the with Fat32 formatted USB stick, rename it and repeat the procedure. The name of the Bios file on this USB stick depends on manufacturer: It is creative.rom for Asrock GIGABYTE.bin for Gigabyte (letters big size and small for bin) MSI.ROM for MSI . I just check this with reading out its new build DSDT, works Dietmar

I found the reason for the Dxdiag.exe crash on z690 boards under XP. It is the LED device under Hid conforme devices in Device Manager. Just disable this (not the USB Hid), and crash is gone Dietmar

I did the same Bios Mod (last version F20b from Gigabyte Webside) for the Gigabyte Z690 UD DDR4 board, for to enable the old processor definition thanks to @Damnation , which shows normal Processor in Device Manager and brings power consumption under XP down as much as possible. All the "Unknown Devices" are gone. You have only to copy the Biosfile GIGABYTE.bin to an fresh with Fat32 formatted USB stick. Put this stick in USB port left side, most up with name Bios written on this port. Compi is shut down, but power is connected. Press Qflash_Plus botton (on board). The orange LED on the board begins to blink, and on your USB stick also. Whole process laasts about 5 min. Dont shut power off as long as the LED is blinking!!! At the end, all LEDs are out. Restart compi, voila you see Bios version F20b, which also works for 13900k etc. Dietmar EDIT: Now no crash because of USB on this board Gigabyte Z690 UD DDR4 when running dxdiag.exe . Before, this Bios even do not recognice a CD-Rom device. Now it does. Gigabyte repairs a lot in their faulty Bios. Now this is also a nice z690 board for XP. The Asrock z690 Extreme board still crashes with dxdiag.exe . Biosflash is always a risk. So no garantie. For me it works. BiosMod for Gigabyte Z690 UD DDR4 https://ufile.io/zpe0ndhy

@Damnation The methode does not work so easy on every compi, when you modd DSDT and SSDT1. But this nice methode from you seems to work everywhere, to modd only DSDT. You can see, what I did when you compare with Beyond Compare both *.dsl files. The numbers of processors is here in DSDT always 64, this I check before Dietmar PS: I dont need to do any other with the Asrock z690 Extreme board for to flash this modded Bios. Dont use this Bios on any other board! As told on Website, disable before EVERYTHING about Security in BIOS Setup. On Asus boards you have to put back its crazy cap, here no cap.

@Mov AX, 0xDEAD Yesssa, I did it! Was crazy much afraid, that I kill my Asrock Z690 Extreme board with this action. I download the newest Bios 9.04 for this board from Asrock Webside, supports also 13900k cpu. With UEFITOOL I extract its DSDT and modd it via the Methode from @Damnation and delete in DSDT also all the 64 "007" devices for "new" cpu definition. Only DSDT is modded. With iasl I make new dsdt.aml from it, all under XP SP3. This I put DSDT back via UEFITOOL into the Bios 9.04 file from Webside. This board has Bios Flashback. So no need for EEpromer. But this Bios Flashback Methode has a bad side effect: On my Asus Apex z370 I "succeed" to kill its Bios chip with wrong Biosfile and "Flashback". There I can repair this with desoldering Bios chip and using EEpromer and new Bios chip. On the Asrock Extreme z690 it is mechanical nearly impossible with Clip to go direct to the Bioschip, you have to solder it also. But this time everything was ok. I put the modded Biosfile named creative.rom on a fresh with Fat32 formatted USB Stick, put this USB Stick into the special slot down next to sound connector, 3 sec press Bios Flashback. And then programming laaasts about 2 min. Blinking red LED on USB stick and green from board. Lightning on stick and LED from board went off and then crossing fingers: board starts, shows Bios 9.04. This methode from @Damnation works on z690 boards for to go away from "1000" unknown devices in Device Manager under XP. The power consumption of the cpu goes down after this methode to nearly zero. And the processor is now shown correct, nice Dietmar PS: This are the files. https://ufile.io/0avd1xjh Very easy to use: As told on Website, disable before EVERYTHING about Security in BIOS Setup. Copy only creative.rom to an with Fat32 formatted USB stick, put it in Flashback port of the Asrock Z690 Extreme board and press "Flashback". No garantie, for me it works.

Yeppp, for to understand, if I am right, I make a complete new readout of the DSDT file with acpidump - b under Win10 on the Asrock z690 Extreme board. And then I compare the DSDT from just now and from 2 months ago. ONLY the time stamp is different. Ok, then I integrate with asl.exe the new modded DSDT into the registry of this board. And voila, works. Crazy, that time can make the difference for XP SP3 boot between a working DSDT and Bsod Dietmar From just now

I succeed to build an XP SP3, which can boot via freeldr or ntldr on any compi, meaning from IDE, any Sata, any USB any nvme device. I build this XP on my Asrock z370 k6 board. Then I test it for nvme boot on the Asrock z690 Extreme board. Boots, everything works as wished. But now comes a crazy thing: When I apply the DSDT patch (thanks to @Damnation) for to use the old processor definition on the Asrock z690 board, suddently compi showes BSOD. Hm, I check the DSDT patch, everything is ok with this patch. This can only mean one thing: After now about 2 months, the compi rejected the same static DSDT patch in registry, which works before. Now I understand, why @Mov AX, 0xDEAD asks for to upload always the modded DSDT fresh to ram, because there must be something crazy like a clock, which compares timestamp in loaded DSDT with actual time Dietmar

@jaclaz It is not enough to do the same copy methode with whole folder "config" in system32. Still the message "Hive not found" appears in this case. And the Win Defrag, contig.exe and Wincontig make a very bad job: When you later make a test with for example contig.exe you see, that a lot of files are still fragmented(!). But via my copy method of system32, you see only one block and ALL files there in are contigous. On the Reactos side they mentioned, that they also noticed this problem with "Hive not found" as a very strange thing, that happens also in Reactos Setup. They think, that the entries in freeldr.ini are not exact the same as in Hive system. This I thought before also. But you can set in freeldr.ini what ever you want, still the message "Hive not found" remains. Newer versions of freeldr.sys cant boot via NTFS. It was very funny, how I come to this special Debug version of freeldr.sys. On Twitter a guy from Reactos team told, that he makes a try with NTFS. I think, that he can do this only because of the leaked SP1 Source files. And then I look in nightly builds for this Author. Not on any other places is noticed, that this freeldr.sys can boot XP. I tested also freeldr.sys around this special build. No NTFS boot Dietmar

@jaclaz What helps for working freeldr boot is, to copy the whole folder system32 to another harddisk with enough free space. Than delete the folder system32 on that XP, FROM where it is taken. Run "Defrag" on this xp, which has now no folder system32. Copy the folder system32 back to its original place. So, it has to do something with, how the files in system32 are sitting to each other or that one of the bootfiles is fragmented but until now, we do not found out, which file this is. With a lot of work, you can make an XP with only the bootfiles, one by one, for to understand this problem. freeldr has this problem, ntldr not Dietmar