551

(26 replies, posted in Vista / 7 DriverPack Chipset)

Ra wrote:

Please add

ThinkPad Power Management driver

http://support.lenovo.com/en_US/downloa … IGR-4GXPEG

That's already in the Third Party DriverPack "Misc"

Implemented for 12.03 release (in testing)

Implemented for 12.03 release (in testing)

Yes, they are included.
Please try DriverPacks before you post requests.

555

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Here's a great reference from Microsoft regarding loading drivers in an offline image.

Driver Ranking

One of the most common issues in deploying drivers occurs when a driver is successfully imported into the driver store but, after the system is online, Plug and Play finds a higher-ranking driver and installs that driver instead.

The Windows PnP manager ranks the following driver package properties in order of importance:

1. Signing
2. Plug and Play ID match
3. Driver date
4. Driver version
For example, if a device has a better Plug and Play ID match but is unsigned, a signed driver with a compatible ID match takes precedence. In addition, a newer driver can be outranked by an older driver if the older driver has a better Plug and Play ID match or signature.

556

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Well I just tried a win7 64 bit source on my USB drive with the $WinPEDriver$ at the root containing the 64 bit dpms (untouched) and the pre-setup (up to the drive selection) went without a problem at all.  This is on my main tower (mentioned above).
I'll try again later with the 32 bit flavor.

557

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

OK, here's an example breakdown for the dpms 64-bit AHCI Intel drivers. 
Unique HWIDs are in GREEN and duplicated HWIDs are in RED.

x64\All\M\Intel\1\iaAHCI.inf   DriverVer=11/06/2010,10.1.0.1008
PCI\VEN_8086&DEV_2681&CC_0106
PCI\VEN_8086&DEV_27C1&CC_0106
PCI\VEN_8086&DEV_27C5&CC_0106

PCI\VEN_8086&DEV_2821&CC_0106
PCI\VEN_8086&DEV_2829&CC_0106

PCI\VEN_8086&DEV_2922&CC_0106
PCI\VEN_8086&DEV_2929&CC_0106
PCI\VEN_8086&DEV_3A02&CC_0106
PCI\VEN_8086&DEV_3A22&CC_0106
PCI\VEN_8086&DEV_3B29&CC_0106
PCI\VEN_8086&DEV_3B2F&CC_0106
PCI\VEN_8086&DEV_3B22&CC_0106
PCI\VEN_8086&DEV_1C02&CC_0106
PCI\VEN_8086&DEV_1C03&CC_0106

x64\All\M\Intel\2\iaAHCI.inf   DriverVer=10/17/2011,10.8.0.1003
PCI\VEN_8086&DEV_27C1&CC_0106
PCI\VEN_8086&DEV_27C5&CC_0106
PCI\VEN_8086&DEV_2922&CC_0106
PCI\VEN_8086&DEV_2929&CC_0106
PCI\VEN_8086&DEV_3A02&CC_0106
PCI\VEN_8086&DEV_3A22&CC_0106
PCI\VEN_8086&DEV_3B29&CC_0106
PCI\VEN_8086&DEV_3B2F&CC_0106
PCI\VEN_8086&DEV_3B22&CC_0106
PCI\VEN_8086&DEV_1C02&CC_0106
PCI\VEN_8086&DEV_1C03&CC_0106

x64\All\M\Intel\3\iaAHCI.inf   DriverVer=11/29/2011,11.0.0.1032
PCI\VEN_8086&DEV_27C1&CC_0106
PCI\VEN_8086&DEV_27C5&CC_0106
PCI\VEN_8086&DEV_2929&CC_0106
PCI\VEN_8086&DEV_3A02&CC_0106
PCI\VEN_8086&DEV_3A22&CC_0106
PCI\VEN_8086&DEV_3B29&CC_0106
PCI\VEN_8086&DEV_3B2F&CC_0106
PCI\VEN_8086&DEV_3B22&CC_0106
PCI\VEN_8086&DEV_1C02&CC_0106
PCI\VEN_8086&DEV_1C03&CC_0106

PCI\VEN_8086&DEV_1E02&CC_0106
PCI\VEN_8086&DEV_1E03&CC_0106

Now you would think that the logical action would be to remove folder \2 because it's duplicated between folders \1 & \3, BUT...not all the HWIDs in folder \2 are duplicated in the newer folder \3. 
My motherboard has PCI\VEN_8086&DEV_2922&CC_0106 which isn't supported by the newer folder \3.  So my best match is folder \2.  I wouldn't want to be stuck with the older driver if I didn't need to be and I'm not the only one that feels that way.

The 32-bit dpms is similar.

So if you can prove that one folder ON IT'S OWN fails, then we can remove it from the pack.  One of the great things about the DriverPacks is that they are modular and you can add/delete/modify each one to suit your needs.
Looking at the IaStor drivers it's probably perfectly safe to remove the v10.8.0.1003 iastor.inf (and sundry) because it's a 100% duplicate with v11.0.0.1032
I'm sure that more testing is in order though.

*Edit
Oh, and editing the .inf will break driver signing and the Windows setup will use ANY other matching driver as long as it's signed.  That's one of the quirks with driver signing is that setup will always default to a signed driver over any other driver.

*Edit 2
I'll try to confirm your bug on my system using your methods.

558

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Hmm, I'll have to take a closer look at the packs contents.

Ah, I see what the download problem is now.  You need to run IE as an administrator for the catalog.update.microsoft.com site to work.  That's just dumb! 
Rule #1 for safe internet browsing is "Never run ANY browser as an admin".

Anyway, got the downloads.  They'll be in the next RC.

Those links aren't working anymore.  The download site keeps crashing.

561

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Sorry, I got confused.  I was looking at the 64-bit pack which is different than the 32-bit.
Yes, your HWID matches all the above drivers in the folders you mentioned.
What happens is the system will scan the available drivers, then select whichever meets all the below criteria (in this order):
1) Digitally signed
2) Matches the exact HWID
3) Newer than the others
4) Matches a partial HWID

So the only way for you to fix your particular problem is you know for certain that a newer driver doesn't work is to remove that driver from the pack (or don't integrate it).

562

(15 replies, posted in Windows 7 Discussion)

marshalkerry57 wrote:

What  is the extra advantages between windows 2 and windows 7?

5 ?

Oh, and spamming the forums gets you banned quick around these parts.

563

(3 replies, posted in Installation Platforms)

No.  XP-64 will never have support at DriverPacks.net.
http://forum.driverpacks.net/viewtopic.php?id=2651

You CAN install XP-32 though and it will be very happy on your laptop (Acer may not support the downgrade though). 
Win7-64 will be 500% better than XP and probably be fully supported by Acer as well.

564

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

That's an interesting problem and it's one that nobody else has reported.
I'm not certain that there is a problem with dpms itself or the method that you're using them.  So I'll leave the thread here (we might move it to "Universal Imaging" later if it's appropriate).

Your HWID is supported in \All\M\Intel\3\iastor.inf but not folder 4.  So that particular error related to folder 4 is very odd.

In practice, the "RAID" BIOS option should not be enabled unless you actually are running a RAID array.  AHCI is the best option for single drives.

We need to look into this a little deeper, hopefully cdob or one of our other imaging pros will stop by for a chat.

The "OEM Preinstall" option in nlite is in the "Unattended" settings under the "General" tab.  It's not really intended for driver use but enables the use of the $OEM$ folder hierarchy.  Ugh, I feel dirty now for having to open nlite.

566

(4 replies, posted in Software)

This thread is a spam-magnet. sad

567

(1 replies, posted in 3rd Party Vista / 7 DriverPacks)

Most of these are already in DriverPack Chipset 12.02

568

(3 replies, posted in Software)

You didn't tell us what OS you're trying to install or what DriverPacks versions you tried.
The HWIDs are an important piece of the puzzle but not all.

If you're using XP, the camera is supported in DP_WebCam_wnt5_x86-32_1107\D\3\W\B1\BisonCam.inf

If you're using Win7, then it's possible that the Vista driver may work but we don't have it in our packs yet.
Try this link:
http://support.asus.com/Download.aspx?S … 3&s=41
Then select "Vista" as your OS, then click the "Camera" link and download Version  V6.32.00.004

569

(8 replies, posted in 3rd Party Vista / 7 DriverPacks)

@Brent I fixed your link (forums don't like spaces in urls) but the FTP doesn't accept "deep linking".
You need to click here: ftp://94.31.243.65/
Then burrow down the folders as above.

570

(12 replies, posted in DriverPack Mass Storage)

Are you sure the drive is OK?  Because it's SATA, you can connect it natively to another PC for testing (I prefer SpinRite).
Once you're sure the drive itself is OK, check the BIOS to make sure the SATA ports are not in "legacy" or "IDE" mode but the preferred "AHCI" mode.
PCI\VEN_8086&DEV_27C0&CC_0101
This HWID indicates that you have it in "legacy" mode and no textmode drivers are needed.  Once you change the mode to "AHCI" or "RAID", the HWID should change to PCI\VEN_8086&DEV_27C*&CC_0104 or PCI\VEN_8086&DEV_27C*&CC_0106

I really hate how Broadcom splits their version numbers so it's possible to have a lower number version number with a current date.  Stupid!
Implemented for DriverPack WLAN 12.02r2

12.02r2
- Added - (All) Broadcom\3 Broadcom BCM43xx 802.11a/b/g/n Network Adapter (from HP sp56154) DriverVer=10/26/2011, 5.100.82.112

Implemented for DriverPack WLAN 12.02r2

12.02r2
- Update - (Vista) Atheros\3 Atheros AR500*/AR92** Family Wireless Network Adapter DriverVer = 12/23/2011,9.2.0.470
- Update - (Win7) Atheros\3 Atheros AR500*/AR92** Family Wireless Network Adapter DriverVer = 12/23/2011,9.2.0.470

The drivers you link to are older than the ones that were finalized in dpms 11.11 (and future test packs).
Can you replace the files in the d\m\as\ folder with the ones from the download and confirm the modified pack works?
(let me know if you need me to repackage a test pack for you)

No need to edit the pack .ini.
If it works, I'll revert the drivers to the older ones.

574

(4 replies, posted in Other)

That's great if you have available space.  SAD2 works that way too.  We call it "Method 1".  Though Method 1 still copies the files to the target system.
From the readme.txt

What goes where?

NT5\x86\
-Method-1: Use DriverPacks BASE to create a Method-1 SAD disc selecting the packs you want to include.  By default, the folder "DriverPacks.net" will be created in C:\.
Copy the contents of that DriverPacks.net folder to this folder so that the folder heirarchy looks like this: \NT5\x86\D\.

NT6\x64\
-Method-1: Extract the contents of all DriverPacks to the NT6\x64\D\ folder so that the folder heirarchy looks like this: \NT6\x64\D\*.  Method 1 will fail if the \NT6\x64\ folder contains any .7z DriverPacks.


NT6\x86\
-Method-1: Extract the contents of all DriverPacks to the NT6\x86\D\ folder so that the folder heirarchy looks like this: \NT6\x86\D\*.  Method 1 will fail if the \NT6\x86\ folder contains any .7z DriverPacks.

Hmmm, I wonder if it'll run directly from the USB drive without copying to the target system first.  <goes off to play with code...>

575

(3 replies, posted in Software)

Welcome to DriverPacks.
First, read the FAQ.
Then read the "Read BEFORE you post." link in my signature.
We need you to provide your DPs_BASE.log and HWID list (use the HWID tool in my signature).
We can't help you unless you provide enough info.