·DP_Chipset_wnt5_x86-32_1412111.7z - 67.47 MB   48663CCDD3BE4EE4A02F12AA4E2882DF374A2175

·DP_Chipset-Utils_wnt5_x86-32_1410141.7z - 25.99 MB   E8F8133220D290E5E9AA108306F792F04BA02DC3

Todo:  export USB device drivers (not USB controller drivers) to a new DP_Misc_USB & DP_Misc-Utils.

for DriverPacks folder:
·DP_WLAN_wnt5_x86-32_1412241.7z - 21.85 MB   5F9C13EFB3D636A52F8BC64BA3AA5330295A86AE

for 3rd party DriverPacks folder (or side-by side for SAD3 installation):
·DP_WLAN-Utils_wnt5_x86-32_1412191.7z - 214.71 MB   CC07102508848BB6F44EB2DEBC6C6DC64D24F81B

for post-Windows Setup utilizing SAD3:
·DP_WLAN_USB_wnt5_x86-32_1412241.7z - 14.28 MB   EDE096C76530827797844BCB360E5AC203A24F95

DP_AVM_Broadband (now deprecated) has been incorporated into the LAN packs, and Proset v14 & Realtek's utility included in the optional DP_LAN-Utils pack.

·DP_LAN_wnt5_x86-32_1412241.7z - 12.26 MB   A4332B6A35BFBB9044DE1CE94489FDD91CD6D1D7

·DP_LAN-Utils_wnt5_x86-32_1412221.7z - 15.94 MB   0B4E620BA600F948972980C0429DDF71F5416BF8

·DP_LAN_USB_wnt5_x86-32_1412241.7z - 6.29 MB   A4618C199CD4374466C905830E075BF27EBD682F

That [AM7] section is very much like that from the official release, and what i based the [AM] part on.
Are you experiencing issues installing on a RAID system?

At least the w2k3 driver (amd_sata.sys/amd_xata.sys) has been restricted in [AM].  It was modded for XP, but XP doesn't have Storport.sys so that was a no-go.

We have had some years to find fault with the official release, and it has been difficult to do.
It took years for anyone to recognize that as anomolous, for instance.
The previous DriverPacks Team is to be thanked here & now.  Thank you!

The DAAMiT (AMD/ATi) drivers are a real mixed bag of mixed HWID types that do not cooperate well.
Add to that the fact that they made a regular habit of reusing HWIDs for differing product & you too might be heard to exclaim something similar.  yikes
Right click on the executables, and discover who appears to have really wrote them in the Version tab.

It would appear that those proposed modifications are in err.
  The related .Inf installs SCSI\ProcessorATI_____ with a null driver.
    Perhaps the "ahciT3r" section need be simply removed.
      Is there a better solution?

Good eye, Outbreaker!

Maybe that section would be better if modified the following way.

ms_4_deviceName="AMD AHCI Compatible SB6xx"
ms_4_tag="ahciT3"
ms_4_sysFile="ahciT3.sys"
ms_4_hwids="SCSI\ProcessorATI_____,PCI\VEN_1002&DEV_4380&SUBSYS_73891462,PCI\VEN_1002&DEV_4380&SUBSYS_738A1462,PCI\VEN_1002&DEV_4380&SUBSYS_0E0C105B,PCI\VEN_1002&DEV_4380&SUBSYS_0E0D105B,PCI\VEN_1002&DEV_4380&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4380&SUBSYS_42CD1462,PCI\VEN_1002&DEV_4380&SUBSYS_42D71462,PCI\VEN_1002&DEV_4380&SUBSYS_3FB71462,PCI\VEN_1002&DEV_4380&SUBSYS_3FD51462,PCI\VEN_1002&DEV_4380&SUBSYS_E9021631,PCI\VEN_1002&DEV_4380&SUBSYS_E9011631,PCI\VEN_1002&DEV_4380&SUBSYS_12FF103C,PCI\VEN_1002&DEV_4380&SUBSYS_73781462,PCI\VEN_1002&DEV_4380&SUBSYS_73771462,PCI\VEN_1002&DEV_4380&SUBSYS_500117F2,PCI\VEN_1002&DEV_4380&SUBSYS_2412147B,PCI\VEN_1002&DEV_4380&SUBSYS_2411147B,PCI\VEN_1002&DEV_4380&SUBSYS_240F147B,PCI\VEN_1002&DEV_4380&SUBSYS_240E147B,PCI\VEN_1002&DEV_4380&SUBSYS_2410147B,PCI\VEN_1002&DEV_4380&SUBSYS_240D147B,PCI\VEN_1002&DEV_4380&SUBSYS_B0031490,PCI\VEN_1002&DEV_4380&SUBSYS_B0021490,PCI\VEN_1002&DEV_4380&SUBSYS_B04A144D,PCI\VEN_1002&DEV_4380&SUBSYS_0E0A105B,PCI\VEN_1002&DEV_4380&SUBSYS_E0361631,PCI\VEN_1002&DEV_4380&SUBSYS_303117AA,PCI\VEN_1002&DEV_4380&SUBSYS_303217AA,PCI\VEN_1002&DEV_4380&SUBSYS_0C8D105B,PCI\VEN_1002&DEV_4380&SUBSYS_82881043,PCI\VEN_1002&DEV_4380&SUBSYS_01FA1028,PCI\VEN_1002&DEV_4380&SUBSYS_02061028,PCI\VEN_1002&DEV_4380&SUBSYS_73251462,PCI\VEN_1002&DEV_4380&SUBSYS_73241462,PCI\VEN_1002&DEV_4380&SUBSYS_110A1734,PCI\VEN_1002&DEV_4380&SUBSYS_02041028,PCI\VEN_1002&DEV_4380&SUBSYS_01231025,PCI\VEN_1002&DEV_4380&SUBSYS_01241025,PCI\VEN_1002&DEV_4380&SUBSYS_602A1509,PCI\VEN_1002&DEV_4380&SUBSYS_602B1509,PCI\VEN_1002&DEV_4380&SUBSYS_80121854,PCI\VEN_1002&DEV_4380&SUBSYS_80131854,PCI\VEN_1002&DEV_4380&SUBSYS_2C311509,PCI\VEN_1002&DEV_4380&SUBSYS_595016F3,PCI\VEN_1002&DEV_4380&SUBSYS_595216F3,PCI\VEN_1002&DEV_4380&SUBSYS_500017F2,PCI\VEN_1002&DEV_4380&SUBSYS_60101695,PCI\VEN_1002&DEV_4380&SUBSYS_73281462,PCI\VEN_1002&DEV_4380&SUBSYS_73291462,PCI\VEN_1002&DEV_4380&SUBSYS_14F21043,PCI\VEN_1002&DEV_4380&SUBSYS_2A52103C,PCI\VEN_1002&DEV_4380&SUBSYS_2A51103C,PCI\VEN_1002&DEV_4380&SUBSYS_13E810CF,PCI\VEN_1002&DEV_4380&SUBSYS_30C2103C,PCI\VEN_1002&DEV_4380&SUBSYS_2A4E103C,PCI\VEN_1002&DEV_4380&SUBSYS_01FC1028,PCI\VEN_1002&DEV_4380&SUBSYS_01FD1028,PCI\VEN_1002&DEV_4380&SUBSYS_604C107B,PCI\VEN_1002&DEV_4380&SUBSYS_10D11734,PCI\VEN_1002&DEV_4380&SUBSYS_600F1695,PCI\VEN_1002&DEV_4380&SUBSYS_600E1695,PCI\VEN_1002&DEV_4380&SUBSYS_21231019,PCI\VEN_1002&DEV_4380&SUBSYS_21241019,PCI\VEN_1002&DEV_4380&SUBSYS_43811019,PCI\VEN_1002&DEV_4380&SUBSYS_43821019,PCI\VEN_1002&DEV_4380&SUBSYS_100415BD,PCI\VEN_1002&DEV_4380&SUBSYS_100515BD,PCI\VEN_1002&DEV_4380&SUBSYS_0611A0A0,PCI\VEN_1002&DEV_4380&SUBSYS_0614A0A0,PCI\VEN_1002&DEV_4380&SUBSYS_21341019,PCI\VEN_1002&DEV_4380&SUBSYS_21351019,PCI\VEN_1002&DEV_4380&SUBSYS_21361019,PCI\VEN_1002&DEV_4380&SUBSYS_21811019,PCI\VEN_1002&DEV_4380&SUBSYS_21821019,PCI\VEN_1002&DEV_4380&SUBSYS_21411019,PCI\VEN_1002&DEV_4380&SUBSYS_21421019,PCI\VEN_1002&DEV_4380&SUBSYS_72431462,PCI\VEN_1002&DEV_4380&SUBSYS_72441462,PCI\VEN_1002&DEV_4380&SUBSYS_71741462,PCI\VEN_1002&DEV_4380&SUBSYS_71751462,PCI\VEN_1002&DEV_4380&SUBSYS_D6028086,PCI\VEN_1002&DEV_4380&SUBSYS_43811849,PCI\VEN_1002&DEV_4380&SUBSYS_43821849,PCI\VEN_1002&DEV_4380&SUBSYS_82311043,PCI\VEN_1002&DEV_4380&SUBSYS_82321043,PCI\VEN_1002&DEV_4380&SUBSYS_240E174B,PCI\VEN_1002&DEV_4380&SUBSYS_2410174B,PCI\VEN_1002&DEV_4380&SUBSYS_240D174B,PCI\VEN_1002&DEV_4380&SUBSYS_2A4F103C"
ms_4_isBusExtender=false
ms_4_exc_disableIfOS="w2k"

Of course, the beginning of that section would need to be modified to ms_count=8, and all paragraphs following the modification (ms_6 through ms_9) renumbered.

l1c50x86v3.cab - 62.58 KB   9021E99388F32C82ECF00D6B899B7E6B05072EB4
   reference:  http://blog.livedoor.jp/blackwingcat/ar … 79824.html

It will, as requested earlier by ... you!

Coming with the new Chipset pack will be improvised null-drivers for Intel USB 3.0 & Thunderbolt controllers.

dp_TB:

; ********************************************************************************
; ********************************************************************************
; **           FileName: LxLpUSB3.inf                                           **
; **           Abstract: Intel(R) USB3 devices                                  **
; **        Last Update: December 14, 2012 (Version 9.4.0 Build 1012)           **
; ********************************************************************************
; ********************************************************************************


[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
; CatalogFile=LxLpUSB3.cat
DriverVer=12/11/2014, 9.4.0.1012

[SourceDisksNames]

[SourceDisksFiles]

[ControlFlags]
ExcludeFromSelect=*

[PackageInfo]
Name=Chipset
Condition=Provider(Microsoft)||InstalledDriverName(Chipset)||Provider()

[Manufacturer]
%INTEL%=INTEL,NT.5.1,NT.6.1

[INTEL]
%TbtBusDrv.DeviceDesc1566% = NO_DRV,	PCI\VEN_8086&DEV_1566&CC_0880
%TbtBusDrv.DeviceDesc1568% = NO_DRV,	PCI\VEN_8086&DEV_1568&CC_0880
%TbtBusDrv.DeviceDesc156A% = NO_DRV,	PCI\VEN_8086&DEV_156A&CC_0880
%TbtBusDrv.DeviceDesc156C% = NO_DRV,	PCI\VEN_8086&DEV_156C&CC_0880
%TbtBusDrv.DeviceDesc157D% = NO_DRV,	PCI\VEN_8086&DEV_157D&CC_0880

[INTEL.NT.5.1]
%TbtBusDrv.DeviceDesc1566% = NO_DRV,	PCI\VEN_8086&DEV_1566&CC_0880
%TbtBusDrv.DeviceDesc1568% = NO_DRV,	PCI\VEN_8086&DEV_1568&CC_0880
%TbtBusDrv.DeviceDesc156A% = NO_DRV,	PCI\VEN_8086&DEV_156A&CC_0880
%TbtBusDrv.DeviceDesc156C% = NO_DRV,	PCI\VEN_8086&DEV_156C&CC_0880
%TbtBusDrv.DeviceDesc157D% = NO_DRV,	PCI\VEN_8086&DEV_157D&CC_0880

[INTEL.NT.6.1]


[NO_DRV]
Include=machine.inf
Needs=NO_DRV

[NO_DRV.Services]
Include=machine.inf
Needs=NO_DRV.Services

[Strings]
INTEL="Intel"
TbtBusDrv.DeviceDesc1566 = "Thunderbolt(TM) Controller - 1566"
TbtBusDrv.DeviceDesc1568 = "Thunderbolt(TM) Controller - 1568"
TbtBusDrv.DeviceDesc156A = "Thunderbolt(TM) Controller - 156A"
TbtBusDrv.DeviceDesc156C = "Thunderbolt(TM) Controller - 156C"
TbtBusDrv.DeviceDesc157D = "Thunderbolt(TM) Controller - 157D"
REG_DWORD =0x00010001


; Copyright (c) 2003-2012 Intel Corporation
; 
; ********************************************************************************
; Intel is making no claims of usability, efficacy or warranty.
; ********************************************************************************
; Information in this document is provided in connection with Intel products. No
; license, express or implied, by estoppel or otherwise, to any intellectual
; property rights is granted by this document. Intel assumes no liability
; whatsoever, and Intel disclaims any express or implied warranty, relating to
; sale and/or use of Intel products including liability or warranties relating to
; fitness for a particular purpose, merchantability, or infringement of any
; patent, copyright or other intellectual property right. Intel products are not
; intended for use in medical, life saving, or life sustaining applications.
; ********************************************************************************
; Intel Corporation disclaims all warranties and liabilities for the use of this
; document and the information contained herein, and assumes no responsibility for
; any errors which may appear in this document, nor does Intel make a commitment
; to update the information contained herein. Intel reserves the right to make
; changes to this document at any time, without notice.
; ********************************************************************************
; ********************************************************************************
; 
; * Third-party brands and names are the property of their respective owners.

dp_USB3:

; ********************************************************************************
; ********************************************************************************
; **           FileName: LxLpUSB3.inf                                           **
; **           Abstract: Intel(R) USB3 devices                                  **
; **        Last Update: December 14, 2012 (Version 9.4.0 Build 1012)           **
; ********************************************************************************
; ********************************************************************************


[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
; CatalogFile=LxLpUSB3.cat
DriverVer=12/11/2014, 9.4.0.1012

[SourceDisksNames]

[SourceDisksFiles]

[ControlFlags]
ExcludeFromSelect=*

[PackageInfo]
Name=Chipset
Condition=Provider(Microsoft)||InstalledDriverName(Chipset)||Provider()

[Manufacturer]
%INTEL%=INTEL,NT.5.1,NT.6.1

[INTEL]
%PCI\VEN_8086&DEV_0F35.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_0F35
%PCI\VEN_8086&DEV_8CB1.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_8CB1
%PCI\VEN_8086&DEV_8D31.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_8D31
%PCI\VEN_8086&DEV_9CB1.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_9CB1
%PCI\VEN_8086&DEV_A12F.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_A12F

[INTEL.NT.5.1]
%PCI\VEN_8086&DEV_0F35.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_0F35
%PCI\VEN_8086&DEV_8CB1.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_8CB1
%PCI\VEN_8086&DEV_8D31.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_8D31
%PCI\VEN_8086&DEV_9CB1.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_9CB1
%PCI\VEN_8086&DEV_A12F.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_A12F

[INTEL.NT.6.1]


[NO_DRV]
Include=machine.inf
Needs=NO_DRV

[NO_DRV.Services]
Include=machine.inf
Needs=NO_DRV.Services

[Strings]
INTEL="Intel"
PCI\VEN_8086&DEV_0F35.DeviceDesc="Intel(R) Atom(R) Processor Z36xxx/Z37xxx Series USB xHCI - 0F35"
PCI\VEN_8086&DEV_8CB1.DeviceDesc="Intel(R) 9 Series USB eXtensible Host Controller - 8CB1"
PCI\VEN_8086&DEV_8D31.DeviceDesc="Intel(R) C610/X99 Series USB eXtensible Host Controller - 8D31"
PCI\VEN_8086&DEV_9CB1.DeviceDesc="Intel(R) 9 Series USB eXtensible Host Controller - 9CB1"
PCI\VEN_8086&DEV_A12F.DeviceDesc="Intel(R) Sunrise Point-H USB eXtensible Host Controller - A12F"
REG_DWORD =0x00010001


; Copyright (c) 2003-2012 Intel Corporation
; 
; ********************************************************************************
; Intel is making no claims of usability, efficacy or warranty.
; ********************************************************************************
; Information in this document is provided in connection with Intel products. No
; license, express or implied, by estoppel or otherwise, to any intellectual
; property rights is granted by this document. Intel assumes no liability
; whatsoever, and Intel disclaims any express or implied warranty, relating to
; sale and/or use of Intel products including liability or warranties relating to
; fitness for a particular purpose, merchantability, or infringement of any
; patent, copyright or other intellectual property right. Intel products are not
; intended for use in medical, life saving, or life sustaining applications.
; ********************************************************************************
; Intel Corporation disclaims all warranties and liabilities for the use of this
; document and the information contained herein, and assumes no responsibility for
; any errors which may appear in this document, nor does Intel make a commitment
; to update the information contained herein. Intel reserves the right to make
; changes to this document at any time, without notice.
; ********************************************************************************
; ********************************************************************************
; 
; * Third-party brands and names are the property of their respective owners.

I pulled it, because it's incomplete.  I noticed by file-size after it was posted & said to myself "that ain't right".

Changed exception handling to be by HWID instead of by .Inf HWID detection.     smile

DP_Modem_wnt5_x86-32_1411291.7z - 31.65 MB   4A0E8D2456F1A68F5AD4B66CA0932A59B7888DF3

Updates for BlackWingCat:

·asahciaw2k.cab - 48.26 KB   6C8643CCA6290C5BE42770E7111E5F480DEC62DE
   reference:  http://www.msfn.org/board/topic/159005- … dows-2000/
·iata89dw2k.cab - 226.28 KB   5A1F071DE6F096F114411DD232732D90CC909580
   reference:  http://blog.livedoor.jp/blackwingcat/ar … 06720.html

Can somebody relay these to him, please?
They are as of yet untested.

It has been a while, but this should now finally be fixed in the latest DP_MassStorage pack.
http://forum.driverpacks.net/viewtopic. … 381#p58381

It turns out that IOHSATA doesn't seem to function under XP, but rather Server 2003.

for DriverPacks folder:
·DP_MassStorage_wnt5_x86-32_1412115.7z - 10.5 MB   E5A37351D713E42A7520D13494E8C8E9835B2EC9

for 3rd party DriverPacks folder:
·DP_MassStorage-Utils_wnt5_x86-32_1411021.7z - 573.02 KB   E04A6E90E2A7315D583069ECBA119FAC1DD47BBC

The MS pack should extend AHCI coverage for the following:

*PNP0600.DeviceDesc                         = "Intel AHCI Controller"
PCI\VEN_8086&DEV_2681&CC_0106.DeviceDesc    = "Intel(R) 631xESB/632xESB SATA AHCI Controller - 2681"
PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc    = "Intel(R) 82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA AHCI Controller - 2821"
PCI\VEN_8086&DEV_2824&CC_0106.DeviceDesc    = "Intel(R) 82801HB (ICH8) 4 port SATA AHCI Controller - 2824"
PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc    = "Intel(R) 82801HM/HEM (ICH8M/ICH8M-E) Mobile SATA AHCI Controller - 2829"
PCI\VEN_8086&DEV_2922&CC_0106.DeviceDesc    = "Intel(R) 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller - 2922"
PCI\VEN_8086&DEV_2923&CC_0106.DeviceDesc    = "Intel(R) 82801IB (ICH9) Mobile 4 Port SATA AHCI Controller - 2923"
PCI\VEN_8086&DEV_3A03&CC_0106.DeviceDesc    = "Intel(R) ICH10 Mobile 4 port SATA AHCI Controller - 3A03"
PCI\VEN_8086&DEV_3A23&CC_0106.DeviceDesc    = "Intel(R) ICH10 Mobile 4 port SATA AHCI Controller - 3A23"
PCI\VEN_8086&DEV_3B23&CC_0106.DeviceDesc    = "Intel(R) 5 Series/3400 Series Mobile 4 port SATA AHCI Controller - 3B23"
; added (Jan 15,2014) for testing thanks to Fernando
PCI\VEN_8086&DEV_0816&CC_0106.DeviceDesc    = "Intel(R) SM35 Express Chipset SATA AHCI Controller - 0816"
PCI\VEN_8086&DEV_1F22&CC_0106.DeviceDesc    = "Intel(R) C600+/C220+ Series SATA AHCI Controller - 1F22" ; avotachi (below)
PCI\VEN_8086&DEV_2323&CC_0106.DeviceDesc    = "Intel(R) DH89xxCC Series Mobile 4 port SATA AHCI Controller - 2323"
PCI\VEN_8086&DEV_8C02&CC_0106.DeviceDesc    = "Intel(R) 8 Series/C220 Chipset Family 6-port SATA AHCI Controller - 8C02"
PCI\VEN_8086&DEV_8C03&CC_0106.DeviceDesc    = "Intel(R) 8 Series/C220 Chipset Mobile 6-port SATA AHCI Controller - 8C03"
PCI\VEN_8086&DEV_8D02&CC_0106.DeviceDesc    = "Intel(R) C610/X99 Series chipset 6-Port SATA AHCI Controller - 8D02"
PCI\VEN_8086&DEV_9C02&CC_0106.DeviceDesc    = "Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller - 9C02"
PCI\VEN_8086&DEV_9C03&CC_0106.DeviceDesc    = "Intel(R) 8 Series Chipset Mobile SATA AHCI Controller - 9C03"
; added (Mar 29,2014) for testing
PCI\VEN_8086&DEV_8C82&CC_0106.DeviceDesc    = "Intel(R) 9 Series SATA AHCI Controller - 8C82"
PCI\VEN_8086&DEV_8C83&CC_0106.DeviceDesc    = "Intel(R) 9 Series Mobile SATA AHCI Controller - 8C83"
; added (Nov 19,2014) for testing Based on Vista AHCI .Inf files (intel chipset v9.4.4.1006)
;   avotahci.inf
PCI\VEN_8086&DEV_1F23&CC_0106.DeviceDesc    = "Intel(R) Atom(TM) processor C2000 product Mobile AHCI SATA 2 Controller - 1F23"
PCI\VEN_8086&DEV_1F32&CC_0106.DeviceDesc    = "Intel(R) Atom(TM) processor C2000 product family AHCI SATA 3 Controller - 1F32"
PCI\VEN_8086&DEV_1F33&CC_0106.DeviceDesc    = "Intel(R) Atom(TM) processor C2000 product Mobile AHCI SATA 3 Controller - 1F33"
;   Tcrkahci.inf (alt for driver in LS\), VLV2AHCI.inf, Wellahci.inf
PCI\VEN_8086&DEV_880B&CC_0106.DeviceDesc    = "Intel(R) Platform Controller Hub EG20T Mobile SATA AHCI Controller - 880B"
PCI\VEN_8086&DEV_0F23&CC_0106.DeviceDesc    = "Intel(R) Pentium(R)/Celeron(R) processor N/J-series Mobile AHCI Controller - 0F23"
PCI\VEN_8086&DEV_8D62&CC_0106.DeviceDesc    = "Intel(R) C610/X99 Series chipset sSATA AHCI Controller - 8D62"
;   PCI ID Project pci.ids (2014.12.10) from http://pci-ids.ucw.cz/
PCI\VEN_8086&DEV_0F22&CC_0106.DeviceDesc    = "Intel(R) Pentium(R)/Celeron(R) processor N/J-series AHCI Controller - 0F22"
PCI\VEN_8086&DEV_23A3&CC_0106.DeviceDesc    = "Intel(R) Coleto Creek Mobile 4-Port SATA AHCI Controller - 23A3"
PCI\VEN_8086&DEV_9C83&CC_0106.DeviceDesc    = "Intel(R) Wildcat Point-LP Mobile SATA AHCI Controller - 9C83"
PCI\VEN_8086&DEV_A103&CC_0106.DeviceDesc    = "Intel(R) Sunrise Point-H SATA AHCI Controller - A103"
;   From iaAHCI.inf to ensure BartPE/UBCD4Win multiple concurrant driver revision support
PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc    = "Intel(R) ICH7R/DH SATA AHCI Controller"
PCI\VEN_8086&DEV_27C5&CC_0106.DeviceDesc    = "Intel(R) ICH7M/MDH SATA AHCI Controller"
PCI\VEN_8086&DEV_2929&CC_0106.DeviceDesc    = "Intel(R) ICH9M-E/M SATA AHCI Controller"
PCI\VEN_8086&DEV_3A02&CC_0106.DeviceDesc    = "Intel(R) ICH10D/DO SATA AHCI Controller"
PCI\VEN_8086&DEV_3A22&CC_0106.DeviceDesc    = "Intel(R) ICH10R SATA AHCI Controller"
PCI\VEN_8086&DEV_3B29&CC_0106.DeviceDesc    = "Intel(R) 5 Series 4 Port SATA AHCI Controller"
PCI\VEN_8086&DEV_3B2F&CC_0106.DeviceDesc    = "Intel(R) 5 Series 6 Port SATA AHCI Controller"
PCI\VEN_8086&DEV_3B22&CC_0106.DeviceDesc    = "Intel(R) 5 Series/3400 Series SATA AHCI Controller"
PCI\VEN_8086&DEV_1C02&CC_0106.DeviceDesc    = "Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1C03&CC_0106.DeviceDesc    = "Intel(R) Mobile Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1E02&CC_0106.DeviceDesc    = "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_1E03&CC_0106.DeviceDesc    = "Intel(R) 7 Series Chipset Family SATA AHCI Controller"

Maybe somebody with a "Intel(R) Sunrise Point-H SATA AHCI Controller - A103" is willing to give it a try?  hmm
  I pulled the HWID from the PCI ID Project pci.ids (2014.12.10)  http://pci-ids.ucw.cz/

Also, a new driver (..\I\dps_IDER_pciide.inf) has been improvised to ensure Intel IDE-R connected drives have Write Caching disabled.  Complimentary drivers have been made to utilize IntelIDE for the regular SATA Controllers, where support doesn't exist from Intel.

For PCI\VEN_8086&DEV_880B&CC_0106, it would appear the Lapis Semiconductor driver that was handling that HWID cannot seem to function on XP, as it was released.  iaStor.sys is now used instead for XP.

updatum ...

·DP_Chipset_wnt5_x86-32_1412111.7z - 67.47 MB   48663CCDD3BE4EE4A02F12AA4E2882DF374A2175

edit:  WHPPSS!  That pack isn't complete without the Utils. package.
         An older until-now unreleased pack will have to do until some moves are completed.

DP_Chipset_wnt5_x86-32_1409121.7z - 94.73 MB   CCD0DE521AB8793BDBDEEE2ABB5F3C070503F134

... correction:  [I4] ; RSTe 3.2.0.1126 for 8086:1D02:0106 is what exists in the official release, yet is disabled for 2k & XP because that is a StorPort-dependant driver which is not included in OS's less than 2k3.

That more closely aligns with recommendations from Asus (the VAR?), but with a caveat.  a 2k3 license seems minimum to support.  Not XP, unfortunately.     hmm

"The latest official one DP_MassStorage_wnt5_x86-32_1209 does not support the ASUS P9X79 chipset."

The official release included RSTe v3.1 for that HWID, so including it in testing is certainly a valid methodology, as OverFlow correctly states.

Please try a fresh integration with those two [Nightlies], for an independant assesment of our progress, if you agree.  The delay until one can get their hands on real hardware gives us a unique opportunity to fine tune the packs before that usage.

  Am thinking that since the driver included in MS_v1411031 (RST v10.5.2) is only utilized for very few HWID's, that it might benefit from having it's driver signing broken, and the executable renamed, so that it is at least possible to coincide with RST v11.2 for those other HWIDs ...

SP2 is a good recommendation.  That should be noted somewhere in the MassStorage changelog ... 

Am thinking it could be a driver conflict.
Intel RST v10.5.2 might not have liked CD only on the (6Gps - blue???) connectors, for one.  The other connectors probably use v11.2. It seems possible that if any other AHCI port was active there would be a conflict over the file "iaStor.sys", and bloop.

Wlan is a bit of a mess, when it comes to PE support.  I need a couple of days just with that pack alone, and some direction on USB-RNDIS drivers within (the upcoming DP_WLAN_USB) to get things ironed out.

If knoks, or anybody else could test integrate and post the DPs_BASE log, it would help ensure that at least LAN is good to go.  Have worked hard lately on that LAN pack.  (AVM_Broadband to be integrated into DP_LAN_USB)

  How could the MassStorage integration be confirmed?  Would that be via the resulting MassStorage.inf?

Seems funny that we have talked this much about PE, yet until now nobody has mentioned HwPnP.

Updated to finally take care of an old, old request.

v1412061
Added:
 -TT\ (MPEVirtual.inf) CityCom GmbH Virtual MPE Decoder Adapter  {DriverVer=01/16/2012,2.0.1.2}
      (Saa7146n.inf) TechnoTrend TT-DVBsat PCI (SAA7146n)  {DriverVer=04/21/2009,1.7.0.6}
      (ttBudget2.inf) added Security Catalog ttbudget2.cat
      (ttBudget4100.inf) TechnoTrend budget S2_4100 (BDA)  {DriverVer = 02/07/2011,1.0.0.1}
      (ttBudget4500.inf) TechnoTrend TT-budget CT2-4500 CI (BDA)  {DriverVer=02/20/2014,4.0.0.4}
      (ttConnect4600.inf) TechnoTrend TT-connect S2-4600 (BDA)  {DriverVer = 07/21/2013,5.1.8.3}
      (ttConnect4650.inf) TechnoTrend TT-connect CT2-4650 CI (BDA)  {DriverVer=02/20/2014,4.1.0.4}
      (TTHybrid.inf) TechnoTrend TT-budget T-3000/B3ATSC  {DriverVer=08/28/2005,1.0.0.14}
      (ttPremiumHD.inf) TechnoTrend TT-premium S2-6400 Twin HD  {DriverVer = 09/07/2011,1.0.6.1}
      (ttTVStick4400.inf) TechnoTrend TT-TVStick CT2-4400 (BDA)  {DriverVer=07/26/2014,4.3.0.0}
      (ttusb2bda.inf) TechnoTrend DVB USB 2.0 BDA Devices (TTUSB2BDA)  {DriverVer=05/24/2012,1.0.3.9}
      (ttusbir.inf) TechnoTrend USB Infrared Device  {DriverVer =04/21/2009,1.8.0.0}
 -TT\5\ (ndislpu2.inf) TechnoTrend DVB USB2.0 series (Network)  {DriverVer = 11/08/2004,1.9.0.1}
        (ttusb2ts.inf) TechnoTrend DVB USB 2.0 Device  {DriverVer=11/30/2005,1.5.4.2}
 -TT\6\ (Ttbdgeon.inf) TechnoTrend PCI DVB Budget Adapter (EON)  {DriverVer = 12/06/2005,2.5.0.5}
        (ttndsbda.inf) TechnoTrend Virtual BDA DVB Network Adapter  {DriverVer = 06/18/2008,2.0.0.3}
        (ttusb2bda.inf) TechnoTrend DVB USB 2.0 BDA Device  {DriverVer = 10/17/2008,1.0.3.4}
        (ttusbir.inf) TechnoTrend USB Infrared Device (w2k)  {DriverVer = 01/24/2005,1.7.0.0}
Moved & Updated:
 -H\0\1\ to TT\1\ (ttdvbusb.inf) TechnoTrend DVB USB series to {DriverVer = 05/23/2005,1.8.6.9} & (ndisloop.inf)
 -H\0\2\ to TT\2\ (ttbdgpci.inf) TechnoTrend DVB PCI budget Adapter to {DriverVer = 02/03/2006,2.5.1.0}
 -H\0\3\ to TT\3\ (ttloophe.inf) TechnoTrend Virtual DVB-S/-C/-T Network Adapter
 -H\0\4\ to TT\4\ (ttndistb.inf) TechnoTrend Virtual STB-S/-C/-T Network Adapter
Removed:
 -H\0\, TT\3\Saa7146n.* (updated in TT\)
 -TT\tthybrid.cat (older than driver files, sha1 hashes not matching)
 - .Inf references excluding misc invalid .cat files, vista or x64 files, where driver is non-WHQL
 - USB\VID_04B4&PID_8613 (FX2 hardware, virgin EEPROM) references preventing conflict, by commenting out HWID
     in K\5\modload2.inf, TH\8\UDST7020Bda.inf, TT\5\ttusb2ts.inf, TT\6\ttusb2bda.inf

DP_TVcard_wnt5_x86-32_1412061.7z - 64.78 MB   96E8BCA53FB11CB5B13DA50E735E44060ED634F0     smile

Thank you for the reply.

knoks wrote:

"I boot BartPE from a internal CD-ROM drive which is connected to a internal SATA port."

Noted.

First, you need to decide what packs to use.

Note that DriverPack CPU 1005 is obsolete, and DriverPack LAN-RIS 1011 is only for network installs.  Attempting to integrate two MassStorage packs is probably not a good idea.

I would recommend using only DP_MassStorage_wnt5_x86-32_1411031.7z &  DP_LAN_wnt5_x86-32_1411251.7z.

Start from scratch with a fresh source, and integrate a new PE disc.
When you are able, try the disc with the ROM drive plugged into any of the blue ports, then any of the grey ports.  Please not the HWID, and let us know what worked, and what didn't.
If you have a second SATA Rom drive, try two simultaneously plugged into blue and grey, if you like.

for DriverPacks folder:
DP_LAN_wnt5_x86-32_1411251.7z - 10.65 MB   77F7CC78213AD08048F524601C6B08D26CAFF4CF

for 3rd party DriverPacks folder, or SAD3 installation:
DP_LAN_USB_wnt5_x86-32_1411251.7z - 3.6 MB   D0A8390227944F18F2EA9A157BCD1AF2D6303218

for 3rd party DriverPacks folder, or side-by-side with DP_LAN for SAD3 installation:
DP_LAN-Utils_wnt5_x86-32_1410231.7z - 312.1 KB   020C233E109EA74779295486AF10E933B2484532

Oh, BartPE.  It helps when i read with understanding ...   (Bluescreen @boot)

Please post your DPs_BASE log within code tags, and HWIDs with all SATA ports enabled as AHCI/Hotplug.
  Any additional information concerning how the image was created would be appreciated.
    Is this booted via USB or disc?
      Which module caused the fault?  Is that listed as iaStor.sys, perhaps?

By the way, welcome to the Forum!  smile

72

(50 replies, posted in Software)

Not a hijack, this is the right place to ask.
  Am i correct that SDI can leverage DriverPacks.net DriverPacks?

edit:  If not, i would humbly request the choice of driver packs, or direction as to where to place them.  Thank you.

nlinecomputers wrote:

@BadPointer:

"I have SPI version 02 R142.    It is prompting me to update driverpacks.  15 of them and the index.   When I try and do so, nothing happens.   The logs imply that this is done via bittorrent?   If that is so it is likely that my router will be blocking that.

What ports do I need to open on my router to get this to properly update.   I can't find any information that discusses that."

     quoted from previous post

I might have some ideas and questions ...


Do you experience the bluescreen before or after initial partitioning?

Are you using an Advanced Format Drive?  If so, try installing on a previous generation SATA drive.

Have you installed a TPM module?

You should not need the ASUS support DVD for XP installation.

Disconnect the internet for XP setup duration.  Turn off Secure Boot (if available).  Set USB 3.0 to compatibility mode, or disable them (Legacy USB3.0 Support [Enabled] ???).  Don't use them for USB 3.0 install (there is no NT5/Vista Intel USB 3.0 driver).  Use USB 2.0 instead, if so.  Turn off Fast Boot.  Turn off HotPlug.  Disable unused SATA ports.  Ensure your CD/DVD/BR and HDD use the same color connectors.  Those settings here in this paragraph are probably the source of the bluescreen, by the way.

What are the HWID's for the other SATA ports??? 
  I see PCI\VEN_8086&DEV_1C02&CC_0106 listed in the Manual.
Use the HWID's tool linked in my signature (lspci -nn from linuxMint Terminal as an alternative)

Disable TPU & EPU.  Disable Turbo Mode &/or TurboV.

It might be helpful to note that DPs_BASE must be the last step in building your image.  If not, try integrating MassStorage, Chipset, LAN [Nightlies] on virgin media and give that a shot.

If you have created USB media for installation, please indicate the utility used, and make a disc instead for testing (Imgburn?).  Disc installation is the primary method of installation supported here, yet am willing to discuss alternatives.

If those ideas fail, try the blue SATA connectors, instead of the grey ones.  The ASMedia controller should not interfere with installation, but if you have reached this point without success then disable them.


When you do find a winning combination, shutdown XP after install, then reverse some of the settings above, then startup Windows - rinse & repeat, until you find an optimal combination.  Then reinstall XP from scratch to confirm.


Do let me know here what specifically works, so that changes can be made.
  I will credit your username in the changelogs.
  Thank you for your participation!   smile

Added:
-I\w\ IDT High Definition Audio CODEC  {DriverVer=05/06/2008,5.10.5927.2}

for DriverPacks folder:
DP_Sound_A_wnt5_x86-32_1410141.7z - 287.64 MB   D7824792AF366A02669E847031CC9389260968A3   smile

v1410141
Added
-Ap\ Apple Bluetooth, Broadcom Bluetooth, Bluetooth Keyboard, Bluetooth Wireless Mouse, Bluetooth Wireless Trackpad
	from Boot Camp Driver Updates v2.1, 3.1, 3.2


v1408131
Updated Changelog with KB951376-v2-x86 integration recommendation
 & DriverPack.net Topic link

 
v1408122
Modified
-MS\MSbt.inf
  added HWID's from MS\rtusb1.inf
Moved
-Ra\rtusb1.inf to MS\ (then archived)


v1408121
Modified
-DriverPack_Bluetooth_MS-Misc_wnt5_x86-32.ini
  to prevent DP_Finisher from an infinite loop "hang" detecting %SystemRoot%\Inf\bth.inf HWID's
-MS\MSbt.inf
  commented-out MS HWID's already contained in xp-native bth.inf


v1408061
Added
-A\ ATMEL bluetooth PCMCIA
-Bx\ (bltn_2F7E.inf) Billionton Bluetooth CF Card  {DriverVer=01/11/2002, 4.0.6}
     (bltn_13AE.INF) Billionton Bluetooth PCMCIA Card  {DriverVer=01/11/2002, 4.0.6}
     (OX16C95x.INF) Billionton Bluetooth PCMCIA Card  {DriverVer=01/11/2002, 4.0.6}
        - all 3 drivers from ENUBT-C1_Driver.zip
     (brcmusb.inf) Broadcom Blutonium  {DriverVer=17/11/2002,3.3.6.0}
-Nx\ National Semiconductor Sweden AB BlueCard PCMCIA
-Ra\ RaLink RT3290(LE) Series Bluetooth Stack  {DriverVer = 12/06/2011,1.08.08.00 / 11/23/2011, 1.1.2.0000} from wla.2.4S_BT.zip
-S\ Socket Communications Inc Bluetooth CF Card  {DriverVer = 03/23/2004, 1.0.3.7}
-T\ (tosbtsd2.inf) Toshiba Bluetooth SD Card/SD-I/O Host Controller  {DriverVer=04/07/2003, 2.0.0.030407}
    (tosdbt.inf) SDA Standard SD Bluetooth Card  {DriverVer=07/01/2007, 5.0.1901.0}
    (tostrans.inf) Toshiba Bluetooth Transport  {DriverVer=07/01/2003, 2.0.0.030701}
-W\ WavePlus Bluetooth PCMCIA Card
Renamed
 -N\ to Nx\


v1407111 - TechDud
Added
-MS\ MS Bluetooth Stack (HWID's from Win7 bth.inf)  {DriverVer = 07/11/2014,1.0.0.0}
   Added Registry settings from Vista bth.inf in MSBT.reg and added exception in DriverPack_Bluetooth_MS-Misc_wnt5_x86-32.ini
-RT\ Realtek Bluetooth  {DriverVer = 10/28/2006,5.0.0.0} from BT_XPWin7-8-8-1_VER100002_VER3787787.zip
Copied from DP_Bluetooth_wnt6-x86_1407062 (thanks to josywong):
 -Bx\ BlackBerry Bluetooth Device (Null-Driver) & Bluegiga Bluetooth Low Energy RS-232 Emulation
 -Cx\ CSR Casira Bluetooth Module & CONWISE Technology Bluetooth Radio
 -Dx\ D-Link DBT-122 Bluetooth 2.0 USB Device
 -H\ HP Bluetooth PC Card Mouse
 -N\ Nokia Reaction Bluetooth Headset
 -O\ Omron Bluetooth Peripheral Device (Null-Driver)
 -R\ Razer Inc. HID peripherals (incl Wiz. - .NET4 req.)
 -RT\ Realtek Bluetooth 2.0+EDR Model 3.2

for 3rd party DriverPacks folder:
DP_Bluetooth_MS-Misc_wnt5_x86-32_1410141.7z - 14.82 MB   B184B8D63526B799D4B195D6BB9261BEE224E7ED


Deprecated: obsolete = delete
DP_Bluetooth_wnt5_x86-32
     - superseded by DP_Bluetooth_MS-Misc_wnt5_x86-32_1xxxxxx.7z