Dietmar

@Dave-H Now your Flex 10 behaves exact as mine. When I show in Device Manager all hidden devices, I see a yellow question mark at partmgr. This device you need, in other case you get Bsod 0x7B. I think, there is a conflict between something, but the behavior, that you describe, happens the same in Safe Mode via F8 or with emergency start with nearly no drivers. Is there a Log file at boot time from XP, that can tell more? May be, that there is also a possibility to use Windbg for to check this, but I dont know how Dietmar PS: Today in the afternoon I make an install from original XP SP3 CD in IDE mode, just naked, only with new acpi.sys V5 and look, if then the install logs tell something more.

@Dave-H For to have sound, you have to deinstall in Device Manager system devices Microsoft UAA High Definition Audio, reinstall it again, after this sound works with Realtek driver Dietmar

@Dave-H I use an own harddisk for XP in the Flex10. This harddisk before I write with Winhex 00 everywhere and prepare it with RMPrebUSB with MBR, ntldr, NTFS and force use of LBA. Then I install XP SP3 from scratch with the new acpi.sys V5 integrated. All works at once and very fast install. The only things that still not work on the Flex 10 under XP SP3 is the 3D graphik, because no driver for it. And also reboot still does not work (I never see this on any other compi), only shutdown works Dietmar PS: I use the Storahci driver from Kai Schtrom.

@Dave-H You need an xp.iso, where the new acpi.sys V5 is integrated permanently, means also in SP3.cab Dietmar

@daniel_k I did the same for my Asrock z370 k6 gaming board. This was crazy hard work, because I cant use the EEpromer for the modded DSDT, because no place on board for to connect the EEpromer. So I have to upload whole new Bios always via Win7. This methode does not work on the Flex10 because of its crazy Insyde Bios. Even the Bios tool reads its Bios out as 3 Mbyte file (means crash, because it is 8MB). On newer Bios, with a size bigger than 16MB, the Bios tool does not work at all. So, now it is MUCH more comfortable to let do nice new acpi.sys all this work. Interesting, on this Flex 10 board I cant install before with original Bios 93cn59ww Bit64 XP SP3, Vista, win7, win8, win10. Only win8.1 I can install before. But now, XP Sp3 with new acpi.sys is the match winner Dietmar EDIT: How do you modd DSDT for Enable IO MWAIT Redirection (fixes CPU C states) ? This I dont have. Can you upload here your original DSDT from Gigabyte together with the modded DSDT?

@Mov AX, 0xDEAD@daniel_k@Dave-H I just test the new acpi.sys V5 free for XP SP3 with connection() patch, which I compiled just now https://ufile.io/mzgeqhbo Waaaooooh, it works on the Flex 10 with newest Bios 93cn59ww Bit64, what a crazy nice work Dietmar

@Mov AX, 0xDEAD Just test for me, if I understand you correct: "fix detect sequence 02 11 (connection as buffer), skip all inside buffer definition and jump" If acpi.sys sees any code in DSDT, that it does not like, via this way it jumps over it. For this, acpi.sys only needs to know, which is the byte code for the unknown >acpi2.0 word (here 02 11) and then it ignores what happens inside this code, jumping to the very first code after (here 02 11) is finished Dietmar PS: So, when the same happens again for another unknown >acpi2.0 word, you only need to do the same patch in parse.c again via its special byte code.

@daniel_k I found this place in parser.c . I only want to know, how it works. Maybe, that my idea is not so bad and this way to jump over unknown words depending on the OS version can be generalized in acpi.sys Dietmar

@daniel_k I dont have one of those USB sticks. But I noticed another strange behavior on any USB device with the new USB3 driver: When you copy a really big amount of data (for example 40 Gbyte) in one step, suddently comes a message, that not enough ram is there, even I have with patch 32 Gigabyte. When you disconnect the stick and connect again, you can copy this 40 Gbyte. But when you try to copy the next 40 Gbyte, exact the same message appears. This is not a big problem, because nearly no "normal" file is about this size, but the problem is real. This never happens, when you make the same transfer with 40Gbyte again and again via 2 Sata disks Dietmar

@Mov AX, 0xDEAD Can you write a pseudocode with words, what you change and how? From your post before I thought, that you make the pointer from amli just to jump to next device, when it meets the acpi5 word connection(), depending on the real OS version. This would be very similar as we did in the very first editing the DSDT in the Gigabyte H110M board via Method (THDH, 1, Serialized) { THDS (ToHexString (Arg0)) } ====> Method (THDH, 1, Serialized) { If ((OSYS >= 0x07D6)) { THDS (ToHexString (Arg0)) } } From my thinking this would be the ideal solution, depending from the OS the words from >acpi2.0 would be just overjumped but now not with editing DSDT, just lets do acpi.sys exact the same Dietmar EDIT: May be, that you can make a compare between the DSDT.raw and DSDT2.raw files from my 2 DSDT examples on the Gigabyte H110M board, what this If ((OSYS >= 0x07D6)) exactly is doing.

@Damnation I just test, gives the same netio.sys Bsod as before Dietmar

@Damnation Nice idea, but for this you have to change the link from ntoskrnl.exe to ntoskrn8.sys I think in the 3 files from Win7 ndis/netio/msrpc.sys Dietmar

@Dave-H Yes, I test for myself. I modd my DSDT via the ideas from older Bios for the Flex10 and this works. This depends not on the cpu. But you can also wait few days, because @Mov AX, 0xDEAD promised to make a new fix for exact this problem. This is the only way without a risk, because nothing in Bios will be changed, only in acpi.sys for XP SP3 Dietmar

@Mov AX, 0xDEAD Yepp, this is the way, that I modd my DSDT for the Flex 10. This means editing of DSDT. How can acpi.sys been told to ignore the connection () ? By the way, how is sense for such a acpi5 word connection () in DSDT, when acpi.sys does not work at all with the GPIO pins Dietmar

May be this is interesting about the use of connection() in acpi5 Dietmar https://uefi.org/specs/ACPI/6.4/05_ACPI_Software_Programming_Model/ACPI_Software_Programming_Model.html#gpio-signaled-acpi-events

I also found Debug version of Win8.1 . Download finished in about 5 hours, brrr.. Dietmar https://windowstan.com/win/windows-8-1-debug-checked-build

@daniel_k I am faster^^ Here is acpi.sys Debug from Win8 bit32 Dietmar https://ufile.io/zaglqzt1

@Dave-H When you find a Bios for the Flex 10, version 93cn25ww.exe, 93cn27ww.exe, 93cn28ww.exe and maybe also 93cn50ww.exe you can flash it without risk (nearly) via win8.1 (or win10, I have not tested). At once all will work under XP SP3 Dietmar PS: And maybe, that @Mov AX, 0xDEAD find a solution, how to exclude in DSDT acpi5 words. Win10 and Win8.1 can live without acpi5 words in DSDT, I tested.

I found this DSDT word "connection" in ACPIspec50.pdf from December 6, 2011 for the very first time. Now it is clear, why xp, vista, win7 and (win8) dont like this Acpi5 word "connection" in DSDT. Connection (GMOD), // Re-Use an existing connection (defined elsewhere) Connection ( ConnectionResource // NameString | ResourceMacroTerm ) Dietmar

@Mov AX, 0xDEAD Yepp, I see the strange symbols in output from Windbg. ba15058a: Device(GPO0)OSNotifyCreate: 8A4282C8 (GPO0) = 00000103 ba150592: { ba150592: Name(_ADR,Zero) ba150598: Name(_HID,"INT33FC") ba1505a6: Name(_CID,"INT33FC") ba1505b4: Name(_DDN,"ValleyView2 General Purpose Input/Output (GPIO) controller") ba1505f5: Name(_UID,One) ba1505fb: Method(_CRS,0x8) ba150627: Method(_STA,0x0) ba1506d1: Name(AVBL,Zero) ba1506d7: Method(_REG,0x2) ba1506ea: OperationRegion(GPOP,0x1,GPBS=0x500,0x50) ba1506f7: Field(GPOP,0x1) ba1506ff: { ba150702: Offset(0x28), ba150704: ,21, ba150709: BTD3,1, ba15070c: Offset(0x48), ba15070e: ,30, ba150713: SHD3,1 ba150713: } ba150713: OperationRegion(GPO2,0x8,Zero,0xc) ba15071d: Field(GPO2,0x1) ba150725: { ba15072a: & ,35, ba15072f: Π,1, ba150732: AccessAs(0x0,0x2), ba150734: ,0, ba150736: ,0, ba150738: ,0, ba15073d: ,0, ba150743: #,15, ba150748: \_SB,46AMLI_ERROR(c0000035): Object already exist CreateNameSpaceObject: object already exist - \_SB Do you have an idea, how to exclude or fake Connection ( in acpi.sys Dietmar

@Mov AX, 0xDEAD GpioIo ( appears also in working DSDT. But Connection ( can be seen only in DSDT which gives DDB Bsod Dietmar

@Mov AX, 0xDEAD Here it is. This is the *.raw DSDT with DDB Bsod Dietmar https://ufile.io/gix4287k

I just check working DSDT against DDB DSDT This device does not appear in working DSDT Dietmar OperationRegion (GPO2, GeneralPurposeIo, Zero, 0x0C) Field (GPO2, ByteAcc, NoLock, Preserve) { Connection ( GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly, "\\_SB.GPO0", 0x00, ResourceConsumer, , ) { // Pin list 0x005F } ), SHS3, 1 }

Here is DSDT from the Flex10, Bios 93cn59ww with Whitelist killed Dietmar https://ufile.io/f8t55pnh

@Damnation @Mov AX, 0xDEAD @daniel_k @George King @Dave-H Here is the longer version Dietmar otto2DDBFlex10.7z