LOL, I guess I could have included "dummy packs" instead eh? smile

1,527

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

Those are from 2008.  But you're right.  It's pretty depressing that ATI can't even update a driver for current-gen (or even last-gen) OS.

v11.02.13 online

I'll see if I can get the "privilege elevation" code working auto-magically in the next version.

Any response?  I was hoping to get confirmation so I could work this into a release candidate.

1,530

(11 replies, posted in DriverPack Graphics)

OK, nothing noteworthy in there.
So, can you run another test for me? 
Remove all graphcs DriverPacks from your disc.  Install XP.  Once finished, XP will be using the generic default VGA driver.  Make sure you have .NET 2 installed.  Then download and install the 10.2 legacy drivers directly from ATI and tell me if that works.

OK, I've worked in a few improvements to the code.
Now checks for UNC paths and displays error if found.
Added NT6 Method 1 routine (uses xcopy instead of copy).
A few other refinements.  More to come...

Well looking at DriverPack Graphics A it is supported.  Did you try DriverPack Graphics A?
HP only supports Win7 on that notebook.

XP support for new cards is shaky at best.
Please post your HWIDs.

1,534

(10 replies, posted in Software)

OverFlow wrote:

the method(s) mr_smartepants describes is far superior to going to device manager and hitting search... However if you are dead set on doing it that way his recomendations will not work.

the only way to make that work (and it is slow and clunky) is to extract all the drivers to a DVD, then select search removable media.

Isn't that what I said? big_smile LOL, I need coffee.

I tested it on my HD3450 (similar) and had no issue.
If the official drivers have the same problem for you, then either the official drivers are broken (which we can do nothing) or you're doing something wrong.

1,536

(31 replies, posted in DriverPack Sound)

I do not rename any drivers.  Those files are renamed during the .inf install process under the copyfiles header.
I discussed this in one of the bartpe forums, I can't remember where now.
*Edit: Here it is: http://forum.driverpacks.net/viewtopic.php?id=5039

Because your .iso is "locked", the files can't be renamed.  This is one of the reasons the DriverPacks are extracted to the systemdrive, then installed, then cleaned up.

I found a bug when using UNC paths such as \\server\path\to\DriverPacks
http://support.microsoft.com/kb/156276
The fix is altering the registry, but changing the affected key may have unwanted side effects.
Hmmm...

1,538

(10 replies, posted in Software)

You could create a Method-1 SAD disc using DriverPacks BASE.  Method 1 for SAD has the added benefit of having the drivers directly read from the disc.  Method 2 would require extraction to the system drive first.
There are several guides on using SAD in the FAQ.
Here's a few to get you started.
[How to] SAD on USB with pre-extracted drivers?
SAD (Stand Alone Drivers) disc - A DriverPacks Drivers Only CD / DVD guide
An updated version of the SAD utility is here: http://forum.driverpacks.net/viewtopic.php?id=4954 (2nd post).

1,539

(11 replies, posted in DriverPack Graphics)

The nlite settings "log" is at the root of your disc "LAST SESSION.INI"

1,540

(11 replies, posted in DriverPack Graphics)

I'd be interested in seeing your nlite logs (not the serial #).

PCI\VEN_1002&DEV_7240&SUBSYS_0D021002&REV_00\4&D553C31&0&0010: Radeon X1950 CrossFire Edition
PCI\VEN_1002&DEV_7260&SUBSYS_0D031002&REV_00\4&D553C31&0&0110: Radeon X1950 CrossFire Edition Secondary
#-019 Searching for hardware ID(s): pci\ven_1002&dev_7260&subsys_0d031002&rev_00,pci\ven_1002&dev_7260&subsys_0d031002,pci\ven_1002&dev_7260&cc_038000,pci\ven_1002&dev_7260&cc_0380

#I063 Selected driver installs from section [ati2mtag_R580] in "c:\d\g\a\dps_1.inf".
===============

#-019 Searching for hardware ID(s): pci\ven_1002&dev_7240&subsys_0d021002&rev_00,pci\ven_1002&dev_7240&subsys_0d021002,pci\ven_1002&dev_7240&cc_030000,pci\ven_1002&dev_7240&cc_0300

#I063 Selected driver installs from section [ati2mtag_R580] in "c:\windows\inf\oem5.inf".

I'd like to know why XP setup is choosing an unsigned c:\d\g\a\dps_1.inf for one HWID and a generic c:\windows\inf\oem5.inf for the other.  This mis-match can only be bad.
I'll have to dig into DriverPack Graphics C and find out what's going on.
*Edit
Looks like the official legacy 10.2 drivers from ATI are not signed. sad

@Clockman, Please test this pack: http://www.mediafire.com/file/xx0bw67tc … 102nt19.7z

clockman wrote:

Pack 17=4 instances of Unknown Disk (there is no disk in this drive) then BSOD after F3 to quit
Pack 18=4 instances of Unknown Disk (there is no disk in this drive)

That's very odd.  Packs 17 & 18 match \N7 & \N7r.  They SHOULD have worked...but didn't.

I have a sinking feeling that I'll need to merge \N7 and \N7r together.  They share some of the same files, but I have a nagging suspicion that the merge will break something (txtsetup.oem files are different).
Test version coming up!

lordsepid wrote:

when exactly this new build would be released ?

When it's done. wink

Thanks, I'll look into it.  I haven't had that error in the latest test build (uses Catalyst 11.01) so maybe the new version fixed it on it's own. wink
I prefer using the /qb switch because it gives a progress bar during installation.  /qn gives no feedback at all (silent).

That's a fine start!  Once you've verified your pack works on the hardware you have access to, then upload to mediafire (or another file-sharing site) and post a link here for others to try.
Once the majority of hardware has been tested successfully by others, we then make the pack a final version and upload to the main server for broad deployment.  That's how the Third Party DriverPacks work! smile

You are now a Third Party DriverPack developer! 
Welcome to the club.

That set of HWIDs are already supported by the current dpms in folders AM1\ and AM9\
AM1: DriverVer=07/08/2009,5.2.0.57
AM9: DriverVer=03/24/2010, 3.2.1548.37

Check your driver versions and see if they're notably different.  If not, just use our dpms!
Otherwise, let us know what versions you have and I may add them to dpms from the Asus website. big_smile

Ooh, nice!  I'll have to add that to my "to-do" list.
Yes, I'll have to create it's own thread and sticky it.

Do not use the monitors Third Party DriverPack.  It's folder structure does not play nice with the folder path length limit.  You can use it in a SAD disk though with no problems.
Bluetooth also has it's own problems.

1,549

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

That's not a problem, it's meant to give that error.
The winnt.sif OemPnpDriversPath entry has a maximum limit of 4096 characters.  By including all the DriverPacks, the path length limit is exceeded.

We discussed that a while ago.  DriverPacks Finisher pulls in the entire HWID list for the log file only.  When matching .inf files, DriverPacks Finisher only compares HWIDs beginning with PCI; it skips ACPI, HDAUDIO and USB for speed.
It was never a problem before.