Re: [REQ] I need to integrated my ahci driver into winxp disc
We cannot really assume to much, or take decisive action, as we have no further feedback yet.
There is also a possibility, if they are still installing from USB/CD-DVD that the USB bus is not always available.
After all, there are reports of USB Keyboards/Mice disconnecting/reconnecting periodically.
The proper HWID needs be established, too. We could still be "chasing our tails" over a hardware issue.
"Yes, if keys are required, then setupreg.hiv is a possibility.
IOHSATA is a scsiport.sys child driver.
Nvgts.sys is another one. This one requires PnpInterface settings."
I noticed previously that there seemed to be at least a few intel drivers that didn't include what appears to be a safe-mode Pnp setting. Actually, in the current DP_MassStorage, only four .Inf's contain the following entry:
[pnpsafe_pci_addreg]
Those are "I\RAIDSRC.inf, I4\iaAHCI.inf, iaStorA.inf, & iaStorS.inf.
Only I\iSSetup.INF & RAIDSRC.inf contain the following key:
"Parameters\PnpInterface"
from iSSetup.txtsetup.oem:
; This section specifies values to be set in the registry for
; particular component options. Required values in the services\xxx
; key are created automatically -- use this section to specify additional
; keys to be created in services\xxx and values in services\xxx and
; services\xxx\yyy.
;
; This section must be filled out for storage controllers that
; are PNP adapters like PCI and ISA PNP adapters. Failure to do this
; can cause the driver failure to load. Must also add the section
; [HardwareIds.scsi.ID] to identify the supported ID's.
;
; <key_name> is relative to the services node for this device.
; If it is empty, then it refers to the services node.
; If specified, the key is created first.
; <value_name> specifies the value to be set within the key
; <value_type> is a string like REG_DWORD. See below.
; <value> specifies the actual value; its format depends on <value_type>
;
;[Config.IntelSCSI]
;value = parameters\PnpInterface,0,REG_DWORD,1
;value = parameters\PnpInterface,1,REG_DWORD,1
from RAIDSRC.inf
[pnpsafe_pci_addreg]
HKR,"Parameters\PnpInterface","5",0x00010001,0x00000001
HKR,"Parameters\Device","NumberOfRequests",0x00010001,0x000000A0
HKLM,"System\CurrentControlSet\Services\Disk","TimeOutValue",0x00010001,0x0000003c
HKLM,"System\CurrentControlSet\Control\Session Manager\Memory Management","SystemPages",0x00010001,0xffffffff
ICP vortex Computersysteme GmbH
*PCI\VEN_8086&DEV_0600.DeviceDesc="RAID Controller"
*PCI\VEN_8086&DEV_0601.DeviceDesc="RAID Controller"
I found the txtsetup.oem's for the RAIDSRC drivers (DriverVer=06/23/2003, 5.3.0.13)
here --> http://www.intel.com/support/motherboar … 007017.htm
the txtsetup.oem says:
[Config.raidsrc]
value = "", Tag, REG_DWORD, 20
Here is the reg additions in I4\txtsetup.oem:
"[Config.iaStorA]
value = Parameters\PnpInterface,5,REG_DWORD,1
value = Parameters,BusType,REG_DWORD,8
value = Parameters\Device,EnableQueryAccessAlignment,REG_DWORD,1
#
[Config.iaStorS]
value = Parameters\PnpInterface,5,REG_DWORD,1
value = Parameters,BusType,REG_DWORD,A
value = Parameters\Device,EnableQueryAccessAlignment,REG_DWORD,1
#
[Config.iaAHCI]
value = Parameters\PnpInterface,5,REG_DWORD,1
value = Parameters,BusType,REG_DWORD,B
value = Parameters\Device,EnableQueryAccessAlignment,REG_DWORD,1 "
; iaStorA.inf
iaStorA_C600 = "Intel(R) C600 Series Chipset SATA RAID Controller"
#
; iaAHCI.inf
iaStorA_AC600 = "Intel(R) C600 Series Chipset SATA AHCI Controller"
#
; iaStorS.inf
iaStorS_C600 = "Intel(R) C600 Series Chipset SAS RAID Controller"
iaStorS_SATA0 = "Intel(R) C600 Series Chipset SAS RAID (SATA mode) Controller"
I have not yet searched the *.oem files, as there is no loaded "oem" iFilter for that extension; d'oh.
Moving to Explorer++ ... or hacking registry to add to txt,inf.ini,etc ([s]if[/s] is possible).
Edit:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.oem]
@="oem_auto_file"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.oem\PersistentHandler]
@="{5e941d80-bf96-11cd-b579-08002b30bfeb}"I\iSSetup-txtsetup.oem has PnP stuff commented-out. Other than that, it's just I4\txtsetup.oem which was mentioned above. I mention these for comparison, no matter what the result of testing on iohsata.inf in either release candidate.
"[Config.IOHSATA]
value = Parameters\PnpInterface,5,REG_DWORD,1
value = Parameters\Device,MaximumSGList,REG_DWORD,32
value = Parameters\Device,NumberOfRequests,REG_DWORD,64"
from the iohsata.inf:
[IOHSATA_Addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001
HKR, "Parameters\Device", "MaximumSGList", 0x00010001, 0x00000020
HKR, "Parameters\Device", "NumberOfRequests", 0x00010001, 0x40
HKLM,"System\CurrentControlSet\Services\Disk","TimeOutValue",0x00010001,0x00000014
HKR, "Parameters\Device", "DriverParameters", 0x00000000, "ForceResetOnResume=0;ForcePowerStateTransition=0;EnableActivityLED=0;FlushCacheThreshold=50;ForceRemovable=0;BlowHPA=0;SetModeTimeoutOnResume=30"
one key that the aforementioned have in common is similar to:
value = Parameters\PnpInterface,5,REG_DWORD,1one key that RAIDSRC.inf & iohsata.oem/inf have in common are similar to:
value = Parameters\Device,NumberOfRequests,REG_DWORD,64Last edited by TechDud (2013-01-31 16:38:09)
MemTest86+ Video Memory Stress Test D-P-C Driver Latency Tester (Win7-max)
