Search options (Page 10 of 14)

One thing you'll notice is that there are so many variations of HWIDS that it's almost impossible to do it that way.

I stopped doing it that way in version v1.9 looking for specific HWIDS. Which used read each line of the inf and found a matching start of a PCI\VEN, USB\, SCSIAdapter\, etc.

Then I switched to in 2.4 to what the line that holds the HWID would look like. So line that would be like an equals sign, and at least one comma, two quotes or two percent signs. Would not be HKR, HKCR, HKLM, excludefromselect, etc.

cool! I'll check out it's parsing asap!

Yeah I read up on the microsoft website on how they construct inf files. And then just looked at a lot of INF files and looked at how they really do it. For me it was the only to get consistent data without any missing hwids.

IN order to get your vbs to run what do I have to do??

Hey looks good! Did the code help?

Are you working on the quotes in the inf titles?

Overflow do you need help getting that parsing to work?? Do you want the code of FindHWIDs to help in this regard?

That's great news! I'm happy it helped!

Wolfi,

For Mass Storage v8.10 with PCI\VEN_10DE&DEV_07F8&CC_0104 (Class SCSIAdapter - Desc NVIDIA nForce Serial ATA Controller) it's
located at C:\D\M\NV6\nvrd32.inf. Which doesn't help you since it's not the same.

ACPI\NVRAID20\3&267A616A&0 is not found at all. Not even ACPI\NVRAID20 within the mass storage pack.

Their just not in the MassStorage and Chipset. Searching for both based on XP x86.

Could you export your list of hardware using save_hwids.exe found in JakeLD's signature?

Generally a Subsys isn't used unless it's specifically stated in the inf file. You mostly go up to either Dev or CC.

MrGuitar and DragonFyre,

Download the latest MassStorage pack and extract them to a location of your choosing, for instance C:\D\M.

First of all you need to run sysprep with the -bmsd parameter to grab all the windows drivers, from mshdc.inf, pnpscsi.inf, scsi.inf, pciide.inf, etc (grabs HDC, SCSIAdapter and weirdly enough it includes system classes too). This is a REQUIREMENT. Unless you want to run the utility below on those select inf files as well (i don't advise it).

Then run the utility found here http://forum.driverpacks.net/viewtopic.php?id=3018 on the folder C:\D\M. Then choose the option for Sysprep output and filter only for current OS/Architecture. Click Start. This will parse all the HWIDs for classes HDC and SCSIAdapter to your Sysprep.inf files MassStorage section. This way will only produce ONE HWID entry in the sysprep.inf file, even though there may be multiple inf's with the same hwid.

Therefore your less likely to produce errors. It will also only filter for the current OS and Arch type so you won't get bum entries.

Make sure to setup your HAL before restarting and capturing the image as an Advanced Configuration and Power Interface (ACPI) PC. This will allow it to be imaged on a dual core/processor machine as well as a single processor machine. However, you will have to change it later if you want to use it on a dual core machine.

You should also add a folder within the Sysprep folder called $OEM$ with a txt file called cmdlines.txt.

C:\Sysprep (folder)
-- $OEM$ (folder)
---- cmdlines.txt

cmdlines.txt

[Commands]
"C:\Sysprep\Sysprep -clean"

This will clean the system of loading all those extra drivers for hardware not present from every boot up.

Also, I suggest using Vernalex's sysprep Driver Scanner tool to add drivers into the registry http://www.vernalex.com/tools/spdrvscn/index.shtml before running sysprep. I also suggest adding C:\Windows\INF to the list too. This instead of using OemPnPDriversPath to parse drivers for installation.

With the newest chipset and mass storage driverpacks they've split IDE/SATA drivers from chipset into mass storage. So you shouldn't need the chipset pack for this. The only thing left in chipset are

PCI\VEN_8086&DEV_444D&CC_0000="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller
PCI\VEN_8086&DEV_444D&CC_0104="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller
PCI\VEN_8086&DEV_444E&CC_0000="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller
PCI\VEN_8086&DEV_444E&CC_0100="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller
PCI\VEN_8086&DEV_444E&CC_0104="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller
PCI\VEN_8086&DEV_444E&CC_0580="C:\D\C\I5\IaNvStor.inf" ; SCSIAdapter - Intel(R) Turbo Memory Controller

Thanks...

v3.1.7 is out

v3.1.7 @ 2008-09-28 5:42pm EST - Adds scan time, files scanned and hwids found to excel and csv output. Moved scanning of certain parts of the INF to produce a faster scan. Changed during scan the FindHWIDs window now minimizes.
v3.1.6 @ 2008-09-28 4:41pm EST - Fixes CSV output to mimic Excel output. Now exports the INF Description (also still outputs the PNPID description)

Excellent! I hope that this latest version really gives the best understanding of the drivers in the packs. Overflow, have you made any progress on the sysprep parser?

Overflow don't forget that you also need to parse HDC from the Chipset drivers too! For instance Intel IDE drivers.

lol... well I just got back from a boring Crystal Reports XI training. So I was itching/chopping at the bit.