FindHWIDS v3.2s - The INF Searching, Hardware ID Exporter (Page 5 of 15)

v3.1 out with change log on first post.

Just curious of anyones thoughts on using System class for sysprep.inf imports. Currently FindHWIDS imports SCSIAdapter, HDC and System just the same as sysprep -bmsd does for machine.inf, mshdc.inf, scsi.inf, and pnpscsi.inf (inf's that I know of). But I'm curious if I should just use SCSIAdapter and HDC for the additions and leave off the System class.

My system currently pulls this (with filtering for hardware on) for the latest/nightlies - So I'd get rid of every one of them except PCI\VEN_8086&DEV_266F

PCI\VEN_8086&DEV_2580="C:\D\C\I1\915.inf" ; System - Intel(R) 915G/P/GV/GL/PL/910GE/GL Processor to I/O Controller - 2580
PCI\VEN_8086&DEV_244E="C:\D\C\I1\ich4core.inf" ; System - Intel(R) 82801DB PCI Bridge - 244E
PCI\VEN_8086&DEV_2640="C:\D\C\I1\ich6core.inf" ; System - Intel(R) 82801FB LPC Interface Controller - 2640
PCI\VEN_8086&DEV_2660="C:\D\C\I1\ich6core.inf" ; System - Intel(R) 82801FB/FBM PCI Express Root Port - 2660
PCI\VEN_8086&DEV_2662="C:\D\C\I1\ich6core.inf" ; System - Intel(R) 82801FB/FBM PCI Express Root Port - 2662
PCI\VEN_8086&DEV_266F="C:\D\C\I1\ich6ide.inf" ; hdc - Intel(R) 82801FB/FBM Ultra ATA Storage Controllers - 266F

Btw, I could always add functionality to the program to NOT add certain hwids and/or classes.

Last edited by stamandster (2008-09-24 07:26:33)

I guess the answer is yes a big leave the System class OUT! I can take the hint

I could always write a function in the tool to parse TO a Driverpacks mass storage ini file for you. That way it'll grab everything and then you can just crop what you don't want in the ini file. No missing hwids. How do you determine if the INF gets these:

ms_X_isBusExtender - Think I found it in the inf LoadOrderGroup = System Bus Extender
ms_X_exc_disableIfOS
ms_X_exc_replaceIfOS
ms_X_exc_skipIfOS

These below seem to be mandatory:

ms_count=X changes when there are more than one .inf/.sys files present in the folder ?
ms_X_deviceName is self explanatory - if this is wrong at all does it screw things up ?
ms_X_tag is the service ?
ms_X_sysFile is the .sys file associated with the inf file ?
ms_X_hwids are the hwids associated with that inf file ?

Each section looks like a folder name. It looks like it only parses 32bit Windows 2000, XP and 2003 hwids. However, there are Vista/2008 sections in many of the drivers, especially Intel.

An aside, I noticed that ms_1_exc_skipIfOS="w2k,wxp" for "elxstor". That's good because it's certainly a screwy driver in xp. Also, I'll be in training till thursday so no updates on the software at least until Friday. I'll still be on the forums though.

I think that's it for now. Thank you for your thoughts on the matter Jeff!

Oh, and what is M1, M2 and M3 and SAD? You can pm me about this if you don't feel it necessary to bung the thread up with un-pertinent information.

Last edited by stamandster (2008-09-24 12:12:37)

I see... so there's not real rhyme or reason except through trial and error. You guys haven't found any links of why this happens??

Well the reason I asked was because I created my tool to not only work with Driverpacks but any set of drivers. The driverpacks were my inspiration, most definitely. I can create a separate tool or function to parse the mass storage ini and input that data instead of an inf file scan type that would normally have to be done for regular no driverpacks drivers.

So in it's most basic form it will do an INIReadSectionNames to an array and for each array it'll read the ms_count and then read each ms_X_hwids as X is the count number.  The string will be stringsplit by comma. It'll grab the from rootdir together with the section name for the folder location. A dash will signify a subfolder, which a stringreplace can be used. However, I don't know how you choose the inf name. Is that from ms_1_tag with just an .inf added on? I'd probably throw a if fileexists to check if the person actually has that file for no errors.

Also, why do you split W2k3 and XP? From what I've found the drivers make no delineation between XP and 2003. However they do between 2000 and XP/2003 and Vista/2008. 2000 is only NT.5.0. XP can be either NT.5.1 (release), NT.5.2 (sp1 and later) and 2003 can be NT.5.2 only. No extension tells it that it can be used on all machines 98 and later. The architecture split is .nt for all 2000 and later machines. .ntx86 for all x86 machines 2000 and later. .ntamd64 for x64 machines XP/2003 and later and .ntia64 for Itanium machines XP/2003 and later. NT.6.0 is for Vista/2008 drivers, they are hal independent.

However, exclude from select can also exclude certain things from certain OS versions and processor arch types, too. So it might be wise to look into that as well.

Last edited by stamandster (2008-09-24 13:38:14)

Yeah I need my hair. I appreciate you doing this for us. This'll keep things nice and sane!

I just hope my program doesn't leave blind spots or at least lessens them.

And I'm definitely on board.

Just pm me your AIM im

Based on my experience coding OfflineSysPrep etc. for injection of drivers into an offline xp/2003 system, my opinion is that this would be the way to go as it guarantees the generation of unique driver names, hwids, etc.

Regards,
Galapo.

Last edited by Galapo (2008-09-25 09:30:52)

I agree an off line sysprep of some sort IS the way to go, ultimately. However, for those that can't do a PE type pre-boot I think the only way to not get a BSOD is to use the mass storage packs ini file to parse drivers from. Jeff is working on this utility. And I'll probably add something to my utility as well.

The process though for offline sysprep is to boot a PE environment, install drivers into the PE environment so you can see the drive, then inject the drivers into sysprep.ini based on the current hardware and the OS type that was imaged.

Because of my limited use of PE I don't know how to edit the layed down images registry nor the PE registry. But, alas, I'm getting off topic.

v3.1.3 is out and adds MD5 checking!

Last edited by stamandster (2008-09-27 02:42:46)

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

Lord isn't that the truth!

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I am a hard core individual... (you may have felt some of that energy)

I would not in good concience slipstream a mass storage controler without first slipstreaming the chipset driver that is its foundation... Others may do this and have success with it... not good enough for me. Do it right or Don't do it... chipset must be included and precede mass "anything less would be uncivilized"

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.