3,451

(9 replies, posted in Feedback and Support - DriverPacks Base)

AHCI is better.

http://en.wikipedia.org/wiki/Advanced_H … _Interface

What's everyone's thoughts on nvidia PhysX drivers?  Needed/not needed?
We can add that functionality to DPBase as a discriminator (like ATICCC/ATICCP) along with adding support for AVIVO by creating dummy .ins files.
Overflow?  This is possible right?

Thanks SamLab for doing all that testing.  From what I can understand of your posts, you recommend 175.19 as the overall best driver.
Thank you for taking the time to do all the testing for us.

SamLab wrote:

Why do you ignore version of the official version of cards for the series 5-9 175.19?

Wow, as odd as it may seem, selecting US at nvidia.com selects the 175.16 version.  Any other language selects 175.19...weird. hmm
Go to www.nvidia.com and see for yourself.  I was toying with 177.41 for these nightly builds.
If 177.41 doesn't work, then we'll revert back to 175.19 since it's the WHQL driver of choice by nvidia themselves.

Sigh. I'll build another one.

806F online now
  Fixed ATICCC installer not silent (oops)

That's odd, since I get the nvidia .inf files from http://www.laptopvideo2go.com/forum/

So the DriverPacks don't work, but the driver from the above website does? hmm
Which version?

SamLab wrote:

Bad sad but I tested 806E and i create new DP with 175.19!

How can you have tested 806E when it finished uploading about two minutes ago? hmm
I haven't even had a chance to update the first post yet...first post updated.

Hi Dan,

Welcome to DriverPacks.net! 
Well the current FAQ was a collaborative effort between myself, Jaak & Helmi.  It was written a while ago, so it is a bit out of date and can use some spiffying up! smile
If you're offering your services to help write a FAQ, by all means do so.  We really could do with a FAQ on SysPrep (I know I could!)

danboid wrote:

I did find a free tool that integrated a number of tools (stuff like ryanvm, nlite etc.) into one, simplifying this whole process yet still giving you the power to tweak and configure your setup. Duno what it was called or if it was any good/ the best.

You might be thinking of AutoImage.

3,458

(4 replies, posted in Software)

Looks nice!

Welcome to DriverPacks.net! smile

SamLab wrote:

I think you add 175.19 to the DP 806D

Nope.  it's 175.16 in there. smile
But 806E is uploading now with 177.41.

The only difference between 806D and 806E is the 175.16->177.41 update.

Well I'm stumped about the 8400/8600 mobile problem. 
The only idea I have is that both abdou and krige are using non-english builds of XP and some of the registry settings in the nvidia .inf are coded for US english builds.
It looks like the drivers are loading, but the device can't start.

I'll try again with the 177.41 build soon.

3,461

(3 replies, posted in Software)

I used it, and it's awesome!

806D online (see first post).

ATI hotfix is in.
Nvidia 175.16 drivers are in (replaces buggy 177 drivers)

To Do:
Add new nvidia 177.41 drivers.

OK, 806D coming up...

Fragbert wrote:

I should need to explain no more...

You're right...hotfix it is then.  Unfortunately, that will break driver signing for some notebooks.
What about AVIVO?  Does anyone use that?  I could add it as a finisher exception.

krige, I'll look a little more deeply into your issue.  I thought for sure this release would fix it. sad

Thanks SamLab for confirming the fixes for me. smile
Fragbert, so you can confirm the problems (and solutions) you're talking about?  I mean REALLY confirm them.  Not just "I have this friend..." confirmation.
If so, then I'll include the hotfix files.

My problem is that I find it very hard to believe that ATI would release their monthly milestone drivers, only to follow up with working drivers as a "hotfix" three months in a row.  hmm
Either ATI is exceedingly stupid, or this hotfix is ONLY intended to fix the problems related to the KB article.

From my perspective, these "hotfix" drivers are beta.  We don't use beta software.
Quote from the KB article:

Note: This driver is provided as is and is not supported by AMD. It has not completed full AMD testing, and is only recommended for users experiencing the particular issue described above.

krige wrote:
mr_smartepants wrote:

Well, 8.6 is built into the latest nightly (8.06C).  Lets see what pops up during testing.

Cool! I am looking forward to test it smile

Your wish is my command...

DP_Graphics_A_wnt5_x86-32_806C (20080622)
<link pulled>
MD5: 75E77F1459C2376E26ACE06ACB9E3529
Size: 72.7 MB

Changed:
A1\
  Added BartPE code to .ini per Overflow request
  Updated to Catalyst 8.6, DriverVer 06/02/2008, 8.501.0.0000
  Removed old WDM directory, supported by G_B\A5\WDM
  Added GART & SMBus driver to AVS directory
  Added HDAudio driver (for HDMI enabled cards)
  Changed DPFinisher .ini to include exception for GART installer
N1\
  Added BartPE code to .ini per Overflow request
  Updated to version 177.35, 06/09/2008 (WHQL)
  (Officially supports the new 200 series cards, but inf modified to support all cards)

The nvidia additions really need testing since I'm using the newer 177.35 drivers which are only WHQL for the newer 200 series cards.  Technically, the majority of their other cards are only supported by the older 175 series drivers. 
Let the testing commence!
smile

Well, 8.6 is built into the latest nightly (8.06C).  Lets see what pops up during testing.

I'll be rebuilding all three graphics DriverPacks (A, B, C).  G_A will be first since it's the most often used one.  G_C will be next because it's been neglected.  G_B will be last.
I'll be rewriting some of the code in mobility.inf with fixes for the HD2400 series cards.  I also just got back from my trip yesterday, so I'll be spending time with my family.
You can expect updated DriverPacks hopefully by the end of the month.

No, that's OK.  I use mobility modder too, I'll do a file comparison to see how they fixed it.

BTW, just got back from my trip.  smile
Game on!

OK, got it.  Researching now...
As I thought, mobility.inf...

PCI\VEN_1002&DEV_9581&SUBSYS_15621043&REV_00\4&1FF24851&0&0008: ATI MOBILITY RADEON HD 2600
<snip>
2008-06-11 09:20:54 : <FLTR>     1. tagFiles (ALL tagFiles must be found)
2008-06-11 09:20:54 : <FLTR>         Found tagfile "C:\ATICCP.ins" (1/3).
2008-06-11 09:20:54 : <FLTR>         Found tagfile "C:\D\G\A1\ATICCP.exe" (2/3).
2008-06-11 09:20:54 : <FLTR>         Found tagfile "C:\WINDOWS\system32\atidemgx.dll" (3/3).
2008-06-11 09:20:54 : <FLTR>     4. +infFiles (ANY +infFiles must be matched)
2008-06-11 09:20:54 : <FLTR>         Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2008-06-11 09:20:54 : <FLTR>         Checking .inf file "C:\D\G\A1\A_Hotfix.inf". 
<snip, no matches>
2008-06-11 09:20:55 : <FLTR>         Checking .inf file "C:\D\G\A1\CX_59746.inf".
<snip, no matches>
2008-06-11 09:20:56 : <FLTR>         Checking .inf file "C:\D\G\A1\CX_59749.inf".
<snip, no matches>
2008-06-11 09:20:56 : <FLTR>         Checking .inf file "C:\D\G\A1\mobility.inf".
2008-06-11 09:20:56 : <FLTR>         Matched +infFile"C:\D\G\A1\mobility.inf" through the HWID "PCI\VEN_1002&DEV_9581" (original HWID: "PCI\VEN_1002&DEV_9581&SUBSYS_15621043&REV_00").
2008-06-11 09:20:56 : <FLTR>     => All requirements for exception [A1] have been met!

The driver is loading, or at least part of it, otherwise the HWID would be detected as generic as "VGA Display Adapter" or something bland.

I suspect a bad line of code (or registry entry) in mobility.inf for that chipset.
I'll do what I can, but I'm living in a tent for the next two weeks.

krige wrote:

It was too big to copy and paste it here in a message, so I put it here:
http://www.mediafire.com/?icvrigsxbu1

That website is blocked from my location. 
You can split it into two separate posts.   

If my gut instinct is correct, I'll have to rewrite the mobility.inf again. sad
I hope I'm wrong.

%SystemRoot%\DPsFnshr.log

The HWIDs are inside the finisher log.

3,473

(12 replies, posted in DriverPack Graphics)

Coolbits is neither installed or supported by DriverPacks.net.  Enabling this tweak during the unattended portion would certainly cause problems.
Once the unattended install and DPfinisher is complete, you can certainly install the Coolbits utility & tweak (supported by nvidia) to your hearts' content! smile

Can you post your DPsFnshr.log?
I need to see how the finisher handles the exceptions.  And I need the HWID.

Wow, that's an old card!  I think it's still supported in the G_C DP though.  I don't have a copy here to browse.