TechDud wrote:

"I took your advise, and copied/moved the contents of folder [1] into [UF] & [UV] and edited the masstorage.ini to reflect these changes.  However; i was greeted with another BSOD, this time STOP $7E in WDFLDR.SYS."

Actually, the error was a STOP $0000007E {0xC0000005,0xF6D61211,0xF78DA4D4,0xF78DA1D0}.

I wonder if combining the main controller device HWid's with those of the Hub Controller may have caused this issue.

From DriverPack_MassStorage_wnt5_x86-32.ini in DP_MassStorage_wnt5_x86-32_1210.USB3.build6.7z:
...

[UF]

ms_count=4
ms_1_deviceName="FRESCO USB3 Controller"
ms_1_tag="flxhcic"
ms_1_sysFile="flxhcic.sys"
ms_1_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"

ms_2_deviceName="FRESCO USB3 Hub Controller"
ms_2_tag="flxhcih"
ms_2_sysFile="flxhcih.sys"
ms_2_hwids="FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k,w2k3"

; THIS IS NEEDED FOR FRSCO LOGIC AND VIA USB3 DRIVERS

ms_3_deviceName="Microsoft Kernel-Mode Driver Framework 1.9 loader"
ms_3_tag="wdfldr"
ms_3_sysFile="wdfldr.sys"
ms_3_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k,w2k3"

ms_4_deviceName="Microsoft Kernel-Mode Driver Framework 1.9"
ms_4_tag="wdf01000"
ms_4_sysFile="wdf01000.sys"
ms_4_hwids="PCI\VEN_1B73&DEV_1000,PCI\VEN_1B73&DEV_1009,PCI\VEN_1B73&DEV_1100,PCI\VEN_1B73&DEV_1400,FLUSB\ROOT_HUB_FL30,FLUSB\Class_09"
ms_4_isBusExtender=false
ms_4_exc_skipIfOS="w2k,w2k3"

...

[UV]

ms_count=4

ms_1_deviceName="VIA USB3 Controller"
ms_1_tag="xhcdrv"
ms_1_sysFile="xhcdrv.sys"
ms_1_hwids="PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"

ms_2_deviceName="VIA USB3 Hub Controller"
ms_2_tag="Viahub3"
ms_2_sysFile="Viahub3.sys"
ms_2_hwids="USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k,w2k3"

; THIS IS NEEDED FOR FRSCO LOGIC AND VIA USB3 DRIVERS

ms_3_deviceName="Microsoft Kernel-Mode Driver Framework 1.9 loader"
ms_3_tag="wdfldr"
ms_3_sysFile="wdfldr.sys"
ms_3_hwids="PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="w2k,w2k3"

ms_4_deviceName="Microsoft Kernel-Mode Driver Framework 1.9"
ms_4_tag="wdf01000"
ms_4_sysFile="wdf01000.sys"
ms_4_hwids="PCI\VEN_1106&DEV_3432,PCI\VEN_1106&DEV_9201,USB\VIA_ROOT_HUB,VUSB3\CLASS_09,VUSB2\CLASS_09,VUSB1\CLASS_09"
ms_4_isBusExtender=false
ms_4_exc_skipIfOS="w2k,w2k3"

827

(17 replies, posted in Software)

Respectfully, kanmani shanmugam, can you offer evidence of this, as the following quote from you seems at first blush to be patently false.

kanmani shanmugam wrote:

"Unfortunately, you’ll find more unsigned than signed drivers on the market right now."

At least offer up three examples of hardware that cannot work without disabling Driver Signing, and the version of Windows used.  Perhaps this would be of assistance to find properly signed drivers from official channels.  hmm

You may be correct, yet you should offer some proof, not just blanket statements which could mislead people.

Sûnnet Beskerming wrote:

"As with any other system modification and administration tool, system instability, failure or unresponsiveness may be encountered when using Atsiv - so use is at the user's own risk."
http://www.theregister.co.uk/2007/07/30 … iver_tool/

It is good that you do acknowledge this.

kanmani shanmugam wrote:

"Of course, you’re giving up a little extra reliability and security to use this feature — at least in theory."

Another note; your link to Atsiv comes up "404 Not Found" on my system AND the link to article you mentioned on "avantgo.computerworld.com.au" reveals an all-but blank page!

Edit:  I finally got through to Linchpinlabs site you linked to above.  It says that Atsiv was declared to be malware by MS & it's digital signature was revoked on August 3, 2007.

Here is some more food for thought concerning drivers, driver signing, & malware:

Quote from Cisco's Cyber Risk Report, July 19–25, 2010

"Microsoft recently collaborated with Verisign to revoke certificates issued to Realtek and JMicron, two hardware companies whose private keys for their driver-signing signatures were apparently compromised. These companies' signatures were used to sign malicious drivers distributed as part of the Stuxnet malware that has recently targeted SCADA systems via USB drives. Realtek and JMicron were issued new certificates to sign future drivers."
...
"IntelliShield Analysis: Some reports, which appear to originate with Sophos' Mike Wood, indicate that signed drivers whose certificates have been revoked will continue to function if they were signed prior to the revocation date. Only drivers signed with a revoked certificate after the revocation date will not load. If this is true, then this action by Microsoft and Verisign will apparently only prevent the malware distributors from further signing additional malware with Realtek and JMicron's compromised private keys. If Wood and others are not correct, then organizations using Realtek and JMicron hardware with signed drivers may soon notice that their hardware is not functioning as expected. "
http://www.cisco.com/web/about/security … -25.html#4

Additional info here --> http://www.securelist.com/en/blog/2236/ … _questions
   & here, all from July, 2010 --> http://blogs.cisco.com/security/stuxnet … _behavior/

Indeed.

Michael Mimoso wrote:

"Oracle Leaves Fix for Java SE Zero Day Until February Patch Update"
http://threatpost.com/en_us/blogs/oracl … ate-101712

"Researcher Develops Patch for Java Zero-Day, Puts Pressure on Oracle to Deliver its Fix"
"A security researcher has submitted to Oracle a patch he said took him 30 minutes to produce that would repair a zero-day vulnerability currently exposed in Java SE. He hopes his actions will spur Oracle to issue an out-of-band patch for the sandbox-escape vulnerability, rather than wait for the February 2013 Critical Patch Update as Oracle earlier said it would."
http://threatpost.com/en_us/blogs/resea … fix-102212  sad

Michael Mimoso wrote:

"Researcher: Fix for UPEK Fingerprint Reader Encryption Woes Falls Short"
http://threatpost.com/en_us/blogs/resea … ort-101112

An update to this story here --> http://threatpost.com/en_us/blogs/deepl … fix-101112


I note that Apple acquired AuthenTec, including UPEK.
http://www.reuters.com/article/2012/07/ … KD20120727

830

(52 replies, posted in Vista / 7 DriverPack Graphics A)

It would seem that the community may need to come to the aid of the moderators here.
Time is increasingly short for both DriverPacks' principals and myself.

Personally, i have realized no financial benefit to assisting the moderators here; it has simply been a community service and an honor at that.  smile

Support your local "driver"-slinger (the Sheriff is out at the moment)!

It would appear that is indeed a NetMOS device (VEN9710).

That company was acquired by India-based MOSchip Semiconductor Tech. in 2001.
A large chunk of IP was sold to Taiwan-based ASIX in 2011.  http://www.asix.com.tw/news.php?op=Asix … ;NewsID=76

It would appear that ASIX has a goodly amount of driver updates for various NetMOS/MOSchip devices.
  Unfortunately yours doesn't appear to be explicitly amongst them.
They don't seem to list even so much as a datasheet for an MCS9834(CV).

Do give this WHQL'ed pack from ASIX a try though, it is for MCS98xx devices and updates drivers originally from 2001 to 2012 including Win8 support:
32bit --> http://www.asix.com.tw/FrootAttach/driv … 0_WHCK.zip
64bit --> http://www.asix.com.tw/FrootAttach/driv … 0_WHCK.zip  hmm

MCS9835(CV) details: http://www.asix.com.tw/products.php?op= … p;PLine=74
"http://asix.com.tw/FrootAttach/Pphoto/PCI_Connectivity_Solutions.jpg"
image quoted from http://asix.com.tw/FrootAttach/Pphoto/P … utions.jpg

If this driver does work, please Request that it be added to DriverPacks Chipset (if i remember correctly).

If this driver fails to work, relay a close-up picture of the controller chip, or just type what it is that is actually written on the chip.  Knowing the name/logo upon it would be helpful, too.  At least this info should allow us to pinpoint the controller chip's specifications, date of manufacture, and hopefully drivers.  If you upload a copy of the drivers you did receive (check the legality of this FIRST in your legal jurisdiction), or point to an existing link online; this could be of assistance too.

At the end of this, if neither the reseller, nor the OEM, nor the chip manufacturer can supply working drivers, i would return it too, as mr_smartepants suggests.  Linux support may be lacking, too!  yikes

832

(5 replies, posted in Windows 8 Discussion)

Quote: "Windows Media Center Offered for Free to Windows 8 Users for a Limited Time"
..."“If your PC is running Windows 8 Pro and you'd like to get Windows 8 Media Center Pack so you can watch and record live TV with Windows Media Center, you can take advantage of the following special offer: for a limited time, get Windows 8 Media Center Pack for free,” Microsoft says on its website."
[http://windows.microsoft.com/en-US/wind … ture-packs big_smile]"

The campaign will debut tomorrow on October 26 and will run through January 31, 2013. Only one key will be sent for each email address, Microsoft explained."

Quoted from here --> http://news.softpedia.com/news/Windows- … 2130.shtml
including quotes from the above address

intel xHCI USB 3.0 Host Controller/Hub

updated to {DriverVer=10/16/2012, 1.0.6.245} WHQL'ed for Win7 (x86 & x64)
here --> http://downloadmirror.intel.com/21129/e … Driver.zip  big_smile

I tried that.  Actually, i just wanted to verify that this pack wouldn't cause problems for non-USB3.0 installs.  The first try using the "new USB3 masstorage driver pack" above garnered a STOP $50 BSOD in WDFLDR.SYS.

I took your advise, and copied/moved the contents of folder [1] into [UF] & [UV] and edited the masstorage.ini to reflect these changes.  However; i was greeted with another BSOD, this time STOP $7E in WDFLDR.SYS.

I don't know how that was possible, so i ditched the Fresco Logic & ViaArena USB 3.0 drivers for testing.

Now i can install XP on non-USB3.0 hardware again!  smile


Unofficially updated Damnation's USB 3.0 MassStorage 'mod
    here --> http://www.mediafire.com/file/lxsv7favg … fficial.7z

v12.10.b09 unofficial ChangeLog
Added
-UA\ AMD USB3 xHCI Host Controller/Hub v1.1.0.0118
-UAS\ ASmedia USB3 xHCI controller/hub v1.16.2.0
-UE\ Etron USB3 xHCI controller/hub v1.00.0000.0115
-UN\ early NEC USB3 xHCI controller/hub v1.0.20.0
-UR\ NEC-Renesas uPD720200(a) series USB3 xHCI controller/hub v2.1.36.0
-UR1\ NEC-Renesas uPD720201, 2 series USB3 xHCI controller/hub v3.0.23.0
-UT\ TexasInstruments USB3 xHCI controller/hub v1.12.25.0

PS:  Chipset looked like it could use an update to it's USB 3.0 drivers to reflect changes in DP_MS
     here --> http://www.mediafire.com/file/wvi7a09xu … fficial.7z  big_smile

v12.10.b01 unofficial ChangeLog
Updated
- U\A AMD USB3 xHCI Host Controller/Hub to 07/06/2012, 1.1.0.0118
- U\AS ASMedia USB3 xHCI Host Controller/Hub to 08/20/2012, 1.16.2.0
- U\E Etron USB3 xHCI Host Controller/Hub to 07/20/2012, 1.00.0000.0115
- U\RE Renesas Electronics uPD720200(a) series USB3 xHCI Host Controller/Hub to 05/10/2012, 2.1.36.0
- U\RE Renesas Electronics uPD720201, 2 series USB3 xHCI Host Controller/Hub to 08/21/2012, 3.0.23.0
- U\T TI USB3 xHCI Host Controller/Hub to 07/05/2012, 1.12.25.0
- U\V ViaLabs USB3 xHCI Host Controller/Hub to 05/30/2012, 6.1.7600.3105

note:  the updated AMD USB 3.0 driver (including USB Filter driver - updated) was sourced from
           here --> http://www2.ati.com/drivers/12-10_xp32-64_sb.exe

In the DP_MS 'mod, i would have liked to combine folders as in Chipset.  How do i accomplish this in MS.ini?

NEC/Renesas uPD720201/uPD720202 xHCI USB 3.0 Host Controller/Hub

updated to {DriverVer=08/21/2012, 3.0.23.0} WHQL'ed for XP & xp64
here --> http://am.renesas.com/media/products/to … -setup.exe  big_smile
readme --> http://ftp.computerbase.de/dl-862/jIFij … 0.23.0.txt
install guide --> http://ftp.computerbase.de/dl-862/QL3e_ … 11114).pdf

Reference --> http://am.renesas.com/products/tools/in … /index.jsp  smile


Edit:  Note that Renesas is offering a warning concerning counterfeit chips.  No word yet concerning which chips are most at risk, nor on how to definitively identify them.

Renesas wrote:

"Precautions against counterfeit semiconductor chips

November 14, 2011

Renesas has recently confirmed some counterfeit chips that have very similar appearances to the company's products. These counterfeits are exquisitely made so it is very difficult to discriminate them by appearance. For instance, we discovered counterfeits in which mold surface, marks, or the packages had close resemblances to that of Renesas' genuine products.

Some of these counterfeits have very poor quality and functionality, and may cause breakdowns or malfunctions if used in your systems or applications.

The counterfeits have not been distributed through Renesas' official sales channels and we would like our customers to purchase Renesas products through our official sales channels. Please note that Renesas holds no responsibilities for any malfunctions or damages caused by using counterfeit products."
http://www.renesas.com/press/notices/no … 11114.html

Edit: 

NEC/Renesas uPD720200(A) xHCI USB 3.0 Host Controller/Hub

updated to {DriverVer=05/10/2012, 2.1.36.0} WHQL'ed for XP & xp64
is also available here --> ftp://15.192.40.12/ftp1/pub/softpaq/sp5 … p54511.exe  big_smile

NEC/Renesas uPD720201/uPD720202 xHCI USB 3.0 Host Controller/Hub

updated to {DriverVer=08/21/2012, 3.0.23.0} WHQL'ed for NT6 (x86 & x64)
here --> http://am.renesas.com/media/products/to … -setup.exe  big_smile
readme --> http://ftp.computerbase.de/dl-862/jIFij … 0.23.0.txt
install guide --> http://ftp.computerbase.de/dl-862/QL3e_ … 11114).pdf

Reference --> http://am.renesas.com/products/tools/in … /index.jsp  smile


Edit:  Note that Renesas is offering a warning concerning counterfeit chips.  No word yet concerning which chips are most at risk, nor on how to definitively identify them.

Renesas wrote:

"Precautions against counterfeit semiconductor chips

November 14, 2011

Renesas has recently confirmed some counterfeit chips that have very similar appearances to the company's products. These counterfeits are exquisitely made so it is very difficult to discriminate them by appearance. For instance, we discovered counterfeits in which mold surface, marks, or the packages had close resemblances to that of Renesas' genuine products.

Some of these counterfeits have very poor quality and functionality, and may cause breakdowns or malfunctions if used in your systems or applications.

The counterfeits have not been distributed through Renesas' official sales channels and we would like our customers to purchase Renesas products through our official sales channels. Please note that Renesas holds no responsibilities for any malfunctions or damages caused by using counterfeit products."
http://www.renesas.com/press/notices/no … 11114.html

Edit: 

NEC/Renesas uPD720200(A) xHCI USB 3.0 Host Controller/Hub

updated to {DriverVer=05/10/2012, 2.1.36.0} WHQL'ed for XP & xp64
is also available here --> ftp://15.192.40.12/ftp1/pub/softpaq/sp5 … p54511.exe  big_smile

Prolific Technology PL2303, PL2304 series USB-to-Serial Comm Port

updated to {DriverVer=07/26/2012, 2.1.35.211} WHQL'ed for 2000, XP, & xp64
here --> http://www.prolific.com.tw/admin/Techno … fileID=232  big_smile

uncorked here --> http://www.mediafire.com/file/kz6gm7bnd … .36.247.7z  smile

Prolific Technology PL2303, PL2304 series USB-to-Serial Comm Port

updated to {DriverVer=07/26/2012, 3.4.36.247} WHQL'ed for Vista, 7, & 8 (x86 & x64)
here --> http://www.prolific.com.tw/admin/Techno … fileID=232  big_smile

unobfuscated here --> http://www.mediafire.com/file/kz6gm7bnd … .36.247.7z  smile

ASMEDIA 104x series xHCI USB3.0 Host Controller/Hub

updated to {DriverVer=08/20/2012, 1.16.2.0} WHQL'ed for 2000, XP, & xp64
here --> http://www.foxconnchannel.com/driverdow … USB3.0.zip  big_smile

ASMEDIA 104x series xHCI USB3.0 Host Controller/Hub

updated to {DriverVer=08/20/2012, 1.16.2.0} WHQL'ed for Vista, 7, 8, & Server2k8 (x86 & x64)
here --> http://www.foxconnchannel.com/driverdow … USB3.0.zip  big_smile

841

(5 replies, posted in Windows 8 Discussion)

lenovo's "Accidental Damage Protection" sounds to be potentially the best feature of all.  smile

"Microsoft's biggest desire is to get you using Windows 8, and fast."

..."The Windows 8 eagle has landed, which means that Microsoft's $39.99 in-place upgrade is now available. They've made it extremely easy to upgrade your computer from a Windows 7, Vista, or XP computer to Windows 8. Here's how it's done. "
http://howto.cnet.com/8301-11310_39-575 … windows-8/

To balance this so i don't sound like a spammer for MS, i am reminded of "Murphy" & PT Barnum (waiting for SP1).  :^o

Avira's clueless.  No false positive either, BTW.  wink

I miss the sha1 check-summing; any chance it could be available as an option in a future version
(user-supplied .dll; perhaps call it a plugin)?

C'est la vie.

None of the files provided in 'renesas drivers.zip' match the XP drivers extracted.


  For the lenovo package "8ay210ww.exe", i used the venerable LegRoom's  Universal Extractor mod by Gora v1.6.1.64 to extract the folder "{app}\driver\Files\x86_XP".
  Use the station-drivers.com package (& Acresso_v16 extraction instructions; as below) to confirm, if you wish.


As for the other driver, "uPD720201V30200.zip" contains the file "Setup-30200.exe".

This file, like the Etron packages, and other Acresso (now Flexera; formerly Macrovision Software Business Unit - a spinoff from Macrovision Corp. which had acquired InstallShield; do not confuse Acresso Soft. with Agresso Soft.) v16 installers, are not properly extracted by the current mod of Universal Extractor.

"Setup-30200.exe /b"C:\temp"" works in Command Prompt,
just navigate to your %temp% folder (most likely not the same as "C:\temp", that is where the .msi is duplicated) for the full output before cancelling the installer.  Do it with the internet temporarily disabled to prevent this installer (et al) from possibly "calling home" as other installers seemingly do (ie:  Avira, Ccleaner, Flash Player, Java, etc, etc, etc, etc, ...).
Then you are able to properly extract the contents of "rusb3drv.msi" with Universal Extractor, using the "MSI Administrative Installer".  big_smile

After checking the packages sourced from lenovo, lycom & sunix versus those @ station-drivers.com, all hashes match for both controller series.  Is it possible that you extracted the wrong driver?

There are two relevant folders in the installer.  "driver\Files\x86" & "driver\Files\x86_xp".  Instructions for extraction for .exe's same as Etron USB3 installer here.

If that is no help, how about v3.0.16.0 for the uPD720201, 2 series from a more widely-known source?  hmm
http://downloadcenter.samsung.com/conte … 0.16.0.ZIP

on the Promise PDC20378 front, i have found original driver links for this chip.
  here -->  http://www.asus.com/Motherboards/Intel_ … /#download
and duplicated here -->  http://www.tyan.com/archive/support/htm … pport.html  big_smile
   (noted for anecdotal reasons)
PBFSTTX2K.inf is {DriverVer=08/06/2003, 1.00.1.37} WHQL'ed for 2k, XP, xp64 & 2k3

They are contained in DP_MassStorage_wnt5_x86-32_1209\D\M\P\
WHQL has been broken for the .Inf to add "&CC_0104", denoting RAID.
I see in the same folder a batch file named "UnDo.cmd"

UnDo.cmd wrote:

"DEL /F /Q PBULSATA.inf
REN PBULSATA.inf.ORG1 PBULSATA.inf
DEL /F /Q PBULSATA.inf.ORG*
DEL /F /Q %0"

The signature may be from Microsoft, yet the embedded certificate is only signed using RSA (1024bit), which is obsolete (iirc).
  reference --> http://forum.driverpacks.net/viewtopic. … 251#p49251

Does it recognize any drives (set up as-SATA or RAID in BIOS) if you integrate with driver-signing disabled?

I note that the obsolete certificate may have been upgraded to RSA (2048bit) in v1.0.1.39
http://www.rioworks.com/Server/Download … romise.zip  big_smile
  This is from this download page --> http://www.rioworks.com/server/Product/ … View=HDAMB
  {DriverVer=10/11/2005, 1.00.1.39} probably WHQL'ed (despite the .cat file date) for Win 2k, XP, xp64, & 2k3!

These drivers do not appear to be in any of the MassStorage packs; it is possible that they work for NT6 too!

candles wrote:

"The PSU is more than sufficient - when I built the box"

How old is the power supply?  Also, please clarify what you mean by "more than sufficient"?

Another thing i noticed; "2012-10-02 10:32:02 : <INIT>     Detected DriverPack CPU 1005!"
You can remove this pack from the list of those packs that you are integrating, as this pack is obsolete.
     see:  http://forum.driverpacks.net/viewtopic. … 384#p49384

"QSC        = "yes""

Please clear the DP_BASE's cache before doing your next integration.  smile


PS:  Aluminum Electrolytic capacitors can fail without showing any physical outward sign.
       You may not have spared any expense with that box, yet can you say the same for the P/S manufacturer (or the production manager, for that matter)?  I do not ask this to denigrate any particular brand.

steve from virginia wrote:

"Technological advancement is the essence of ‘ruinous competition’. "
http://www.economic-undertow.com/2012/1 … t-grinder/

  I truly wish that i could loan you my $30 IR thermometer.  You might be amazed to see how hot it gets around the CPU after several minutes running memtest.  I have a couple of similar ASUS boards with an 865P chipset that regularly get up to 85°C with a 3.0 GHz chip!  This is no guarantee that you will see the same results, just circumstantial evidence that you might.
  As capacitors are temperature-sensitive (as well as ripple-current sensitive - that's related to the P/S), if i do the math on a set of Uni-ChemiCon KZE series (Japanese); they should last 8000 hours (333 days) at that temperature (as long as Ripple-Current remains below it's maximum rating).  The math is much different for "Solid" electrolyte capacitors; they last much longer (this is one reason why they are more-widely used today).  Of course, once again, this is no guarantee that you are experiencing cap failure, just more circumstantial evidence.  Intermittent faults can be a symptom.  http://www.badcaps.net/pages.php?vid=5

   see also:   http://www.capacitorlab.com/basic/
                  http://www.capacitorlab.com/visible-failures/index.htm
                  http://www.capacitorlab.com/failure-modes/index.htm
                  http://www.motherboardpoint.com/asus-p4 … 51989.html
                  http://www.pcreview.co.uk/forums/black- … 41866.html

PPS:  Did you try removing (or renaming) the MegaINTL.INF file & repacking with 7-zip for a test integration?  I am assuming that you are indeed using a different machine to do the integrations.  yikes

PPPS:  Use anti-static measures to handle this board & USB pins (esp. FP header), as ICH5/ICH5R may be more sensitive to it.  If any of your front-USB connectors have damage, disconnect them to ensure your mobo is preserved.  The risk is "ICH5R latch-up".  I haven't experienced this myself, just 865 North-Bridges "shorting" out, just not as dramatically.

I noticed all the various packs that DP_Base is attempting to integrate for you (and all-but succeeding, too!).
That can't be good.

Two different versions of the 3rd-Party HID pack are integrated into your source.  Add to that the Monitor pack is all-but-useless, buggy, obsolete and potentially harmful to your monitor (some .inf's from LG, et al, have incorrect timings, iirc).

Surely, a more streamlined set of packs would be helpful also.

Does anyone have any comments on the usage of files from asustreiber.de?
  This does appear to be ASUS; confirmation would be groovy.

D'oh!  I neglected to mention the AMD USB 3.0 drivers as i didn't notice them until now.

From DP_Chipset_wnt5_x86-32_1209.7z:
D\C\U\A\amdhub30.inf
D\C\U\A\amdxhc.inf
D\C\U\A\USBFilter.inf

Sorry, there were still updates for the NEC\Renesas chips (see the "Edit:")
     here --> http://forum.driverpacks.net/viewtopic. … 583#p48583

"The latest driver for the uPD720200(a) series is 2.1.36.0"
...
"The latest driver for the uPD720201, 2 series is 3.0.20.0"

Indeed, i do understand why you passed over v3.5.73.0 for Fresco.  Do you have any comment on asustreiber.de - is it really ASUS?

Also wondering if you could remove the link to StationDrivers in the Etron folder, please.

Forgive me if i seem too much of a PITA; it's for our audience, though; including:
http://driverpacks.net/well-known-users  smile