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

@Damnation Yes, I have compi with Win10. May be, that my problem is, that I tried to do all under XP SP3. Have you tried to make this USB boot stick with Easy2boot + Agfm under XP? Is yes, I am just too blind and need a short Tutorial Dietmar EDIT: XP, WIndows 7, WIndows 8 and early versions of Windows 10 have a problem with USB Flash (thumb) drives. They will only access one partition. Please use Windows 10/11 to create a E2B+agFM UEFI-bootable USB drive. If your USB drive is a USB Fixed Disk (e.g. USB HDD) then you can use any version of Windows. I have a Kingston Workspace 64 GB, which is always shown as USB hardDISK.

@Damnation I prepare an USB stick with fat32 and Grub2. It contains now grubfm.iso grubfmaa64.efi grubfmia32.efi grubfmx64.efi loadfm At commandline grub: ls It shows me (hd0,msdos1) (hd1) (hd1,msdos1) But any try to boot from any it always gives me the message error: you need to load the kernel first Dietmar

@Damnation I never worked with grub2, only grub4dos. Which grub2 you use and can I work with it like with grub4dos Dietmar

@Damnation I see, that the power consumption of your cpu is also after this modd at about 40 Watt. When you succeed that the processor lists shows your cpu correct, will this powerconsumption go down? Can you please send me your modded DSDT and the needed SSDT, all in original and in modded? Then I will make a try with to integrate it permanently in one of my not needed z690 boards via Bios flash with EEPromer Revelprog IS Dietmar PS: I need to flash, because I never succeed to load a DSDT in boottime under XP.

@Damnation If we do not succeed to integrate it in a new acpi.sys for XP, can we put the old processor definition again in each DSDT Dietmar

I found a solution, but it is unclear for me, how the Bios protection can be overcome. The tool, with which I extract the Bios.exe from Dell is called Dell_PFS_Extract.exe You are not allowed to change the name of the origin bios.exe file. And be careful: For me it worked under Win8 and check each file on whole compi, if it is an dell Bios, brrr.. So better to make an own folder and put this bios.exe together with Dell_PFS_Extract.exe there in and give at the start from the program ONLY this folder^^ for to search..

Hi, does anybody know, how to extract the Bios file from Dell Inspiron_Vostro_3481_3581_3584_3781_1180.exe so that it can be read via UEFITOOL thanks a lot Dietmar

@dearleader The "NTLDR" from Reactos is better in finding the correct Arcpath. But it can be only used for Fat32 partition. In my experiments in booting XP from nvme on any old compi, this works Dietmar

@dearleader This means, that nothing is written to your real harddisk during XP install Dietmar EDIT: You need to prepare your HARDDISK with RMPrepUSB, not the USB stick.

@dearleader When the install of XP hangs during boot of XP from CD @Setup is inspecting your computer's hardware configuration, there may be an error with the geometry of your harddisk. Use RMPrepUSB vers 2.1.739 and set there XP (NTLDR), NTFS, Force use of LBA calls Dietmar

Yes, this can happen, when the arcpath is not found for ntoskrnl.exe. This happens also on the z690 chipset for win10 bit 32, same message as you have. This problem happens to me also. This is gone, when you burn your XP.iso to CD and install XP from CD (or DVD) but only via IDE or Sata. The same is true for Win10 bit 32 Dietmar

@dearleader On some compis, XP cant be installed via USB. In this case you need a burned CD (or DVD) with this XP on it and an IDE or Sata CDROM drive, not USB(!) Dietmar

@Damnation And this (I think the same) for the new builded free version for ntoskrn8.sys Dietmar *** Fatal System Error: 0x000000d1 (0x0A050007,0x00000002,0x00000000,0xB9A6E9F7) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target at (Thu Jul 28 10:53:14.796 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {a050007, 2, 0, b9a6e9f7} *** ERROR: Symbol file could not be found. Defaulted to export symbols for e1d6232.sys - *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 Probably caused by : NETIO.SYS ( NETIO!NmrpIsEqualNpiId+8 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 8052b724 cc int 3 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0a050007, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: b9a6e9f7, address which referenced memory Debugging Details: ------------------ *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 READ_ADDRESS: 0a050007 CURRENT_IRQL: 2 FAULTING_IP: NETIO!NmrpIsEqualNpiId+8 b9a6e9f7 8b10 mov edx,dword ptr [eax] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: ba5535f8 -- (.trap 0xffffffffba5535f8) ErrCode = 00000000 eax=0a050007 ebx=0a050003 ecx=b9b2d6f0 edx=6d665346 esi=b9b2d6f0 edi=00000000 eip=b9a6e9f7 esp=ba55366c ebp=ba55366c iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 NETIO!NmrpIsEqualNpiId+0x8: b9a6e9f7 8b10 mov edx,dword ptr [eax] ds:0023:0a050007=???????? Resetting default scope LOCK_ADDRESS: 8055b560 -- (!locks 8055b560) Resource @ nt!IopDeviceTreeLock (0x8055b560) Shared 1 owning threads Threads: 8bbaf620-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8055b560 Thread Count : 1 Thread address: 0x8bbaf620 Thread wait : 0x161 LAST_CONTROL_TRANSFER: from 804f8e95 to 8052b724 STACK_TEXT: ba5531ac 804f8e95 00000003 ba553508 00000000 nt!RtlpBreakWithStatusInstruction ba5531f8 804f9a80 00000003 0a050007 b9a6e9f7 nt!KiBugCheckDebugBreak+0x19 ba5535d8 8054483c 0000000a 0a050007 00000002 nt!KeBugCheck2+0x574 ba5535d8 b9a6e9f7 0000000a 0a050007 00000002 nt!KiTrap0E+0x180 ba55366c b9a6ee81 0a050007 b9b2d6f0 89b38850 NETIO!NmrpIsEqualNpiId+0x8 ba553684 b9a6ed5d 8bb85208 00000001 b9b2f008 NETIO!NmrpFindOrAddRegisteredNpiId+0x22 ba5536f0 b9a6ec91 89b38850 ba553728 ba553724 NETIO!NmrpRegisterModuleAndGetBindableCandidates+0x33 ba553718 b9a6ef72 00000002 b9b2e018 00000000 NETIO!NmrpRegisterModule+0x3c ba553740 b9b0bf2f b9b0c6db 00000000 b9b2f008 NETIO!NmrRegisterProvider+0x4b ba553764 b9b0c6db 00060000 8052e8fc ba55378c NDIS!ndisStartNsiProvider+0x4b ba553780 b9b08db9 b9861000 89b38e08 00060014 NDIS!ndisInitializeNsi+0x50 ba553798 b98102a3 89b38e08 89b37000 00000000 NDIS!NdisMRegisterMiniportDriver+0x51 WARNING: Stack unwind information not available. Following frames may be wrong. ba553814 805813af 89b38e08 89b37000 00000000 e1d6232!DriverEntry+0x20f ba5538e4 8058f557 800003f4 00000000 ba553900 nt!IopLoadDriver+0x66d ba553928 805e7b7f e159dad8 00000001 800003f4 nt!PipCallDriverAddDeviceQueryRoutine+0x235 ba553974 805e7f76 e159dabc 00000001 ba5539f0 nt!RtlpCallQueryRegistryRoutine+0x37d ba5539fc 80590ddf 00000001 00000084 ba553a24 nt!RtlQueryRegistryValues+0x368 ba553ad0 8059229c 00000000 00000001 ba553d5c nt!PipCallDriverAddDevice+0x261 ba553d2c 805927a6 8bbd3dd8 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4 ba553d54 804f6a32 00000003 8055b5c0 8056485c nt!PiProcessStartSystemDevices+0x3a ba553d7c 80538921 00000000 00000000 8bbaf620 nt!PipDeviceActionWorker+0x170 ba553dac 805cffee 00000000 00000000 00000000 nt!ExpWorkerThread+0xef ba553ddc 8054623e 80538832 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!NmrpIsEqualNpiId+8 b9a6e9f7 8b10 mov edx,dword ptr [eax] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: NETIO!NmrpIsEqualNpiId+8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 5b48ef86 IMAGE_VERSION: 6.1.7601.24208 FAILURE_BUCKET_ID: 0xD1_NETIO!NmrpIsEqualNpiId+8 BUCKET_ID: 0xD1_NETIO!NmrpIsEqualNpiId+8 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xd1_netio!nmrpisequalnpiid+8 FAILURE_ID_HASH: {1d7ea187-17c8-1608-8471-24546162eb85} Followup: MachineOwner --------- 1: kd> lm start end module name 80062000 80072a80 pci (deferred) 80100000 8012a000 KDSTUB (deferred) 804d7000 806e5000 nt (pdb symbols) C:\Programme\Windows Kits\8.1\Debuggers\x86\sym\ntkrpamp.pdb\270E083F57714738A1895FE542CFB8DE1\ntkrpamp.pdb 806e5000 80705d80 hal (deferred) 80706000 8072e000 kdcom (deferred) b980d000 b987a000 e1d6232 (export symbols) e1d6232.sys b987a000 b98a2000 HDAudBus (deferred) b99bc000 b99bfd80 serenum (deferred) b9a44000 b9a5de80 Mup (deferred) b9a5e000 b9a9d000 NETIO (pdb symbols) C:\Programme\Windows Kits\8.1\Debuggers\x86\sym\netio.pdb\5BBB5169EEB04D0BB707BFA122C6C9442\netio.pdb b9a9d000 b9ac8000 msrpc (deferred) b9ac8000 b9aece80 ntoskrn8 (deferred) b9aed000 b9ba5000 NDIS (pdb symbols) C:\Programme\Windows Kits\8.1\Debuggers\x86\sym\ndis.pdb\B69DA90026554DB7963D1422C84157172\ndis.pdb b9ba5000 b9c31d00 Ntfs (deferred) b9c32000 b9c48b80 KSecDD (deferred) b9c49000 b9c5af00 sr (deferred) b9c5b000 b9c7ab00 fltMgr (deferred) b9c7b000 b9f30000 iaStor (deferred) b9f30000 b9f55700 dmio (deferred) b9f56000 b9f74880 ftdisk (deferred) b9f75000 b9fa7000 ACPI (deferred) ba0a8000 ba0b1180 isapnp (deferred) ba0b8000 ba0c2700 MountMgr (deferred) ba0c8000 ba0d3000 PartMgr (deferred) ba0d8000 ba0e4c80 VolSnap (deferred) ba0e8000 ba0f8000 disk (deferred) ba0f8000 ba104180 CLASSPNP (deferred) ba118000 ba124d00 i8042prt (deferred) ba128000 ba137c00 serial (deferred) ba328000 ba32e800 firadisk (deferred) ba388000 ba38e000 kbdclass (deferred) ba398000 ba39da00 mouclass (deferred) ba4b8000 ba4bb000 BOOTVID (deferred) ba5a8000 ba5a9100 WMILIB (deferred) ba5aa000 ba5ab700 dmload (deferred)

@Damnation I see an endless running bar. Windbg tells this for the checked ntoskrn8.sys version for ndis 6 *** Fatal System Error: 0x000000d1 (0x02030005,0x00000002,0x00000000,0xB9A6E9F7) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target at (Thu Jul 28 10:39:19.687 2022 (UTC + 2:00)), ptr64 FALSE Loading Kernel Symbols .................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2030005, 2, 0, b9a6e9f7} *** ERROR: Symbol file could not be found. Defaulted to export symbols for e1d6232.sys - *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 Probably caused by : NETIO.SYS ( NETIO!NmrpIsEqualNpiId+8 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 8052b724 cc int 3 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 02030005, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: b9a6e9f7, address which referenced memory Debugging Details: ------------------ *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 *** No owner thread found for resource 8055b4e0 READ_ADDRESS: 02030005 CURRENT_IRQL: 2 FAULTING_IP: NETIO!NmrpIsEqualNpiId+8 b9a6e9f7 8b10 mov edx,dword ptr [eax] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: ba5535f8 -- (.trap 0xffffffffba5535f8) ErrCode = 00000000 eax=02030005 ebx=02030001 ecx=b9b2d6f0 edx=49577050 esi=b9b2d6f0 edi=00000000 eip=b9a6e9f7 esp=ba55366c ebp=ba55366c iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 NETIO!NmrpIsEqualNpiId+0x8: b9a6e9f7 8b10 mov edx,dword ptr [eax] ds:0023:02030005=???????? Resetting default scope LOCK_ADDRESS: 8055b560 -- (!locks 8055b560) Resource @ nt!IopDeviceTreeLock (0x8055b560) Shared 1 owning threads Threads: 8bbaf620-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8055b560 Thread Count : 1 Thread address: 0x8bbaf620 Thread wait : 0x152 LAST_CONTROL_TRANSFER: from 804f8e95 to 8052b724 STACK_TEXT: ba5531ac 804f8e95 00000003 ba553508 00000000 nt!RtlpBreakWithStatusInstruction ba5531f8 804f9a80 00000003 02030005 b9a6e9f7 nt!KiBugCheckDebugBreak+0x19 ba5535d8 8054483c 0000000a 02030005 00000002 nt!KeBugCheck2+0x574 ba5535d8 b9a6e9f7 0000000a 02030005 00000002 nt!KiTrap0E+0x180 ba55366c b9a6ee81 02030005 b9b2d6f0 89b39f30 NETIO!NmrpIsEqualNpiId+0x8 ba553684 b9a6ed5d 8bb8e730 00000001 b9b2f008 NETIO!NmrpFindOrAddRegisteredNpiId+0x22 ba5536f0 b9a6ec91 89b39f30 ba553728 ba553724 NETIO!NmrpRegisterModuleAndGetBindableCandidates+0x33 ba553718 b9a6ef72 00000002 b9b2e018 00000000 NETIO!NmrpRegisterModule+0x3c ba553740 b9b0bf2f b9b0c6db 00000000 b9b2f008 NETIO!NmrRegisterProvider+0x4b ba553764 b9b0c6db 00060000 8052e8fc ba55378c NDIS!ndisStartNsiProvider+0x4b ba553780 b9b08db9 b9861000 89b3ac80 00060014 NDIS!ndisInitializeNsi+0x50 ba553798 b98102a3 89b3ac80 89b36000 00000000 NDIS!NdisMRegisterMiniportDriver+0x51 WARNING: Stack unwind information not available. Following frames may be wrong. ba553814 805813af 89b3ac80 89b36000 00000000 e1d6232!DriverEntry+0x20f ba5538e4 8058f557 8000042c 00000000 ba553900 nt!IopLoadDriver+0x66d ba553928 805e7b7f e10141f0 00000001 8000042c nt!PipCallDriverAddDeviceQueryRoutine+0x235 ba553974 805e7f76 e10141d4 00000001 ba5539f0 nt!RtlpCallQueryRegistryRoutine+0x37d ba5539fc 80590ddf 00000001 00000084 ba553a24 nt!RtlQueryRegistryValues+0x368 ba553ad0 8059229c 00000000 00000001 ba553d5c nt!PipCallDriverAddDevice+0x261 ba553d2c 805927a6 8bb8e990 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4 ba553d54 804f6a32 00000003 8055b5c0 8056485c nt!PiProcessStartSystemDevices+0x3a ba553d7c 80538921 00000000 00000000 8bbaf620 nt!PipDeviceActionWorker+0x170 ba553dac 805cffee 00000000 00000000 00000000 nt!ExpWorkerThread+0xef ba553ddc 8054623e 80538832 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: NETIO!NmrpIsEqualNpiId+8 b9a6e9f7 8b10 mov edx,dword ptr [eax] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: NETIO!NmrpIsEqualNpiId+8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETIO IMAGE_NAME: NETIO.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 5b48ef86 IMAGE_VERSION: 6.1.7601.24208 FAILURE_BUCKET_ID: 0xD1_NETIO!NmrpIsEqualNpiId+8 BUCKET_ID: 0xD1_NETIO!NmrpIsEqualNpiId+8 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xd1_netio!nmrpisequalnpiid+8 FAILURE_ID_HASH: {1d7ea187-17c8-1608-8471-24546162eb85} Followup: MachineOwner ---------

@daniel_k When I am interested in a hardware and what can be done with it, I often bought in past this device. Now no money here at the moment, so no buying Dietmar

@mockingbird I only want the Original Intel X540-T2, because this is the only one with big passive cooler and keeps working a life long Dietmar

@mockingbird @Damnation X540-T2 works with 10Gb under XP SP3. Green LED means 2x10Gb working, ultrafast, my router cant compare with, Intel 82599 is X520 also driver for XP SP3 and also 10Gb Dietmar PS: Blackwingcat make them also work under win2000.

@mockingbird I have 10 Gb connection under XP SP3 Dietmar

@Damnation I have no idea, how to integrate all the needed functions, even we have no C-code for them Dietmar

@Damnation No money for this :)) Dietmar

@Damnation Until now, yes. @Mov AX, 0xDEAD told the same Dietmar