Page 76 of 345
#1126 RE: Windows XP SP3 32bit and modern PC parts by infuscomus 23.07.2019 20:20

@cedar

did you manage to get multiprocessor ACPI PC working? or did you get a BSOD?

#1127 RE: Windows XP SP3 32bit and modern PC parts by diderius6 23.07.2019 20:44

@cedar
Until now we dont have a good acpi.sys for XP 64 bit,
which works on a lot of newer mainboards,
Dietmar

#1128 RE: Windows XP SP3 32bit and modern PC parts by cedar 23.07.2019 21:46

@infuscomus

In safe mode, multiprocessor ACPI PC seems fine. I can install other
drivers. After exiting safe mode. I may or may not be able to
get back to safe mode if XP installed through optical Sata drive.

I remember probably 2 weeks or more ago, I can repeatly go back to
safe mode with multiprocessor ACPI PC. Out side safe mode, BSOD.

I just upated 2003 from SP0 to Sp1, and SP2. Will try if they work later?

Cedar

#1129 RE: Windows XP SP3 32bit and modern PC parts by cedar 23.07.2019 21:49

@diderius6

Any chance to work on XP 64 ACPI?. I realize too XP64 has no
Standard mode!.

Cedar

#1130 RE: Windows XP SP3 32bit and modern PC parts by cedar 23.07.2019 22:36

@infuscomus

Wow. SP2 for 2003 instead of SP0 works. I am in
Multi PC ACPI mode now.

Edit: And it is from swap drive method.
Edit2: Now I can use similar way on XP. Different SPs may make
or break things.
Edit3: Even SP1 works.

Cedar

#1131 RE: Windows XP SP3 32bit and modern PC parts by diderius6 25.07.2019 11:06

I found NEC USB3.0 driver from 10 January 2010 vers. 1.0.19.0.
This driver is really very simple structurated.
With this I make new try using Windbg for XP SP3
Intel chipset 3.0 driver
Dietmar

EDIT: I have now NEC driver USB 3.0 from June 2009 for XP, Vista (means before Win7), vers 1.0.1.0.

#1132 RE: Windows XP SP3 32bit and modern PC parts by canonkong 25.07.2019 11:36

avatar

@diderius6
If you use IDA7.0 to open the *.sys, than press F5, it will converting to C language, maybe some one can use it to recompile.

https://github.com/microsoft/Windows-driver-samples

#1133 RE: Windows XP SP3 32bit and modern PC parts by diderius6 25.07.2019 11:58

@canonkong
This is really a nice feature,
but my Ida Pro is from 2004 :))
Dietmar

PS: Starting from autumn 2009, NEC makes USB 3.0 drivers also for Win2000 and NT4 .

#1134 RE: Windows XP SP3 32bit and modern PC parts by infuscomus 25.07.2019 13:13

@diderius6

can you upload to station-drivers for driver archiving?

If we are lucky, it might even work for windows 98

assuming all function requirements are met by ntkern.vxd

#1135 RE: Windows XP SP3 32bit and modern PC parts by diderius6 25.07.2019 13:41

@infuscomus
Here it is.
The xhci.sys driver is loaded in XP as I can see
but the hub.sys not.
So, the problem with DEV_&VEN_ is gone,
but something is wrong with the hub
Dietmar

#1136 RE: Windows XP SP3 32bit and modern PC parts by canonkong 25.07.2019 13:45

avatar

@diderius6
If the xhci.sys is loaded but the hub.sys not. It meant that the XHCI.sys need to fix somewhere. HUB is follow to XHCI.

#1137 RE: Windows XP SP3 32bit and modern PC parts by infuscomus 25.07.2019 14:06

@diderius6 @canonkong

I noticed with the earlier modified AMD USB 3.0 drivers there was a FileSize error in the sys files



maybe this was causing problems? i fixed them

or maybe its nothing, i dont know

#1138 RE: Windows XP SP3 32bit and modern PC parts by canonkong 25.07.2019 14:28

avatar

@infuscomus
I signed the driver use driving signature tool, it can automatic checksum,so I don't have noticed FileSize error.

#1139 RE: Windows XP SP3 32bit and modern PC parts by diderius6 25.07.2019 14:57

Now I get

usbstor.sys
usbd.sys
xhci.sys
hub3.sys

loaded very early (start 0, Group System Reserved)
but still yellow questionmark for USB 3.0 xhci and no hub3
in device manager
Dietmar

PS: I corrected yesterday the above size error. It does not change anything.

#1140 RE: Windows XP SP3 32bit and modern PC parts by diderius6 25.07.2019 15:40

There is only one small step, to make the very first NEC driver from June 2009 make to work for Intel chipset USB3
It looks like the "IRP_MN_START_DEVICE" failed and this can be the fault of hub3.sys because Child 0000000000.
Dietmar

0: kd> !DevNode 0x8a47f250
DevNode 0x8a47f250 for PDO 0x8a4c1818
Parent 0x8a4bb6e0 Sibling 0x8a47bbb0 Child 0000000000
InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\2&ebb567f&0&A0"
ServiceName is "nusb3xhc"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeStartCompletion (0x306)
StateHistory[06] = DeviceNodeStartCompletion (0x306)
StateHistory[05] = DeviceNodeAwaitingQueuedRemoval (0x30f)
StateHistory[04] = DeviceNodeStartCompletion (0x306)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
StateHistory[09] = Unknown State (0x0)
StateHistory[08] = Unknown State (0x0)
StateHistory[07] = Unknown State (0x0)
Flags (0x00002030) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_PROBLEM
CapabilityFlags (0x00002000) WakeFromD3
Problem = CM_PROB_FAILED_START
Failure Status 0000000000



CM_PROB_FAILED_START


This function is reserved for system use.

The device failed to start.
Error Code 10
Display Message

If the device's hardware key contains a "FailReasonString" value, the value string is displayed as the error message. (A driver or enumerator supplies this registry string value.) If the hardware key does not contain a "FailReasonString" value, the following generic error message is displayed:

"This device cannot start. (Code 10)"

"Try upgrading the device drivers for this device."
Recommended Resolution

Select Update Driver, which starts the Hardware Update wizard.

This error code is set when one of the drivers in the device's driver stack fails IRP_MN_START_DEVICE. If there are many drivers in the stack, it can be difficult to determine the one that failed.

Xobor Forum Software von Xobor
Datenschutz