infuscomus

@daniel_k Yes, win8.0 USB3 driver on 8.1 works. It also works on 8.0 after swapping out @Dietmar's patched win8.0 acpi.sys -------- ACPI driver issue is unlikely to ever be fixed for XP though.

@George King It's in wrk2003.c near the bottom of the file. comment out or delete from line 1722 to 1956 are the hex pattern checks that cause the BSODs @Mov AX, 0xDEAD what are you using this hex pattern check for?

@Dietmar have you had any luck booting with my winlogon.exe? also, can you get a Gigabyte B450M DS3H board to test with the 149C controller?

@Mov AX, 0xDEAD I found the place in the win8.0 usbxhci.sys where controller is started - theres a 100ms wait in there that I can increase to 127ms but theres no room for anything larger than that, and it might not achieve anything. I don't see a wait interval on the reset function though. I'm not certain I can inject new code without breaking the driver. The Wind10 driver code is similar but makes use of ExTimer functions // // Controller failed to clear halt in the first 5 ms of aggressive polling by the driver. // Implement a secondary wait period with less frequent polling using high resolution // timers and relinquish the CPU while waiting for the timer event. // timer = ExAllocateTimer(Controller_HighResTimerCompletion, &event, EX_TIMER_HIGH_RESOLUTION);

@Mov AX, 0xDEAD I'd like to try and use the function PoSetPowerState to set the powerstate of the 149c controller to D3 - then wait 1-2ms - then go back to D0. But I'm not sure how to do it, if you know how can you show me?

@Mov AX, 0xDEAD I moved kestallprocessor to DllInitialize like you said, itmade no difference, I'm guessing the controller needs resetting. I mean like check system uptime and to only reset the USB controller if it's within the first minute of uptime or so, so that it doesn't reset the controller every time the driver is called. But I'm a novice at this, so I'm still not sure how to accomplish this.

@Mov AX, 0xDEAD I'm still very much a novice at this, so any help you can provide would be appreciated.

@Mov AX, 0xDEAD Can you show me in C code how to check if the system has just been booted, and if so, tell the xhci controller to reset itself?

@Mov AX, 0xDEAD I gave KeStallExecutionProccessor a try in ntoskrnl extender but without success - PCI_COMMON_CONFIG PciHeader; NTSTATUS DriverEntry ( // Dummy entry PDRIVER_OBJECT DriverObject, PUNICODE_STRING RegistryPath ) { if ((PciHeader.VendorID == 0x1022) && (PciHeader.DeviceID == 0x149C)) { KeStallExecutionProcessor(10000); } return STATUS_SUCCESS; } No change in behaviour.

@Mov AX, 0xDEAD @canonkong The behaviour is different for me, both the controller and the hub are reported by windows as "This device is working correctly." however any devices that are connected to the hub have deviceIDs like USB\VID_0000&PID_0000 USB\VID_000E&PID_0001 Disabling and re-enabling the controller will resolve the issue but it will recur again at next boot.

It fails to start at boot every time consistently. I've been using a 3rd party USB 3.0 PCI-E card as a work around for it at the moment, but I'd like to get my motherboard USB 3.0 ports working at boot if I can.

@Mov AX, 0xDEAD I was looking through the XP HAL source code and saw there are USB related chipset hacks included called HalpStopohciInterrupt HalpStopUhciInterrupt etc.. I looked into the Windows 8.0 HAL and saw there is now a HalpStopXhciInterrupt included too, I know I'm just guessing here but this might be what is needed to fix problematic USB controllers. Do you think you could try and implement this function into the XP HAL source code? P.S I've tested using source code built HAL in XP SP3 and it works just fine, no issues with winlogon.exe or anything as with ntoskrnl.exe

@Dietmar here you go. checkedwinlogon.7z

@Dietmar If I send you a checked build of my winlogon.exe from source, can you try and get passed a c0000021a BSOD with it?

I resolved all the missing exports in the 2k3 kernel and got to "Setup is Starting Windows" in XP SP3 text mode setup, then the VMs CPU halted and it shutdown.

@ExtremeGrief I'm going to start trying that tomorrow, there are still a number of exports missing that I'll need to add back in, and hopefully I won't run into the SESSION5_INITIALIZATION_FAILED BSOD again.

@Dietmar Thanks. @ExtremeGrief No, this is just me experimenting to try and build the ntoskrnl from source code that can successfully boot XP SP3 to desktop. Setup completes, but it fails shortly afterwards.

@Dietmar Had some success compiling winlogon with the server 2003 compiler, let see how this one goes. https://ufile.io/ljjg9x9w

I'm not having much luck compiling winlogon.

@Dietmar Tomorrow I will try to re-compile the decompiled XP winlogon that showed up on 4chan a while back - hopefully that can help get this working. edit: I've also made a new build environment VM - old one got corrupted.

@Dietmar I went and did a full fresh install of XP with my kernel on a vanilla SP3 ISO - I got all the way to the OOBE and after exiting that - BSOD 0xC000021A It seems I have missed something with my kernel - I got close to SP3 compatibility though.

@Dietmar here you go. https://ufile.io/3gzbkrf1 P.S I included HALs too but have not yet tested them.

@Mov AX, 0xDEAD I haven't needed to compile anything else other than the kernel and it works when I swap ntoskrnl/ntkrnlmp/ntkrnlpa/ntkrpamp out on a SP3 ISO at least, but ntoskrnl extender it seems refuses to work with it.

@Mov AX, 0xDEAD I have an OEM SP3 XP ISO where I swapped out the kernel with my compiled version if you want to try it out? This version installs in a VM at least.

@Mov AX, 0xDEAD So do you think the 149C controller is failing because of a missing function in our patched acpi.sys that the windows 8.0 acpi.sys has?