Search options (Page 9 of 14)

Yes exactly...

You can use vernalex's sysprep driver importer to create a list of drivers and install post sysprep

You'll want to have the exe in the same folder as this batch script

@ECHO OFF
ECHO Setting Driver Signing Policy to OFF
START WatchDriverSigningPolicy.exe
ECHO Importing Drivers to Registry
START /WAIT spdrvscn /p c:\D /e inf /d %windir%\inf /a /s /q
ECHO Starting Driver Manager
START devmgmt.msc
ECHO Starting Install of Hardware
START /WAIT RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers
taskkill /f /im WatchDriverSigningPolicy.exe
taskkill /f /im mmc.exe

v3.2d @ 2009-02-26 -
-- Fixed issue with timers displaying properly.
-- Speeds up exporting via Excel by hiding Excel
-- Adds ClassGUID to outputs Excel and CSV
-- Change GUI background to white
-- Scanning process no longer minimizes main window and adds Tooltip processing. Processing staying in main window and updates Statusbar area.
-- Fixes issue with _INIReadSectionEx to skip commented out lines (or should, I did test )
-- Fixes issue with adding any HWID filters. You must use the Pipe symbol on all filter seperations. Updated the help functions to coincide with changes.

I guess I'm wrong about just version in some cases!

Quoted from http://www.microsoft.com/whdc/winlogo/d … WinUp.mspx

"Detection - DriverVer.
All drivers must have the DriverVer directive present in the INF. Only the date portion is required for Windows Update detection matching.
The INF file [Install] sections must key off the most specific Plug and Play IDs only. Plug and Play IDs must be specific as per WHQL INF file requirements for PCI devices. Information about the INF Requirements for PCI Devices is available at http://www.microsoft.com/whdc/system/bus/PCI/infreq.mspx."

More INF Resources:
http://www.microsoft.com/whdc/archive/w2inf.mspx
http://www.osronline.com/ddkx/install/c … f_4l47.htm
http://www.microsoft.com/whdc/connect/pci/infreq.mspx

Is anyone familiar with Regular Expression??

Always happy to oblige more work for you oh master of thy graphics!

After some testing I see what's happening. I think it's the INIReadSection that's doing it.

It's not so much that after PCI\VEN_XXX_DEV_XXX_SUBSYS_XXX that it won't pick up but it stops after a certain amount of read data! It is just a coincidence that it stopped there...

And I quote "Only the first 32767 chars are taken in account in an section due to Win9x compatibility." I can't wait till it's bye bye 9x compatibility!

I'll see what I can find in regards to expanding it so I can get the rest of the data!

...

I found a UDF that will allow reading of all the values. I'll be testing tonight!

As Jeff and I discussed in IM we definitely see the human aspect to never go away with this. Mainly because there are so many variables. However, I do think that giving weight to a driver is a good idea. Something that gives certain drivers precedence and scale. So something to the affect of "driver a is top priority to install, but only if the system is hp coded, else use this driver here". Something like that. However, that's a TON of work.

Or do we only rely on specific manufacturers releases for hardware? Not relying on OEM releases, but the manufacturer release if we can help it? Like Broadcom drivers being released by Broadcom or HP, choose broadcom. That way it's a broader scale. Same thing we do for the likes of intel, nvidia, ati, adaptec.

For driver installation, if my research is correct, I believe the only thing that Windows DLL install method and the Microsoft Driver Installer Framework only work off of version release number, I don't think they even look at the date. So if the version is greater than the driver will be updated. But with the MS driver installer framework you can force a lower version driver to be applied.

Also, do we want to apply more weight (ie. install first) to more generic drivers. Like a hwid for PCI\VEN_XXX instead ahead of PCI\VEN_XXX_DEV_XXX ?

And I said I'd leave System out of the mass storage drivers scan

Hi Babasera you're actually in the wrong sub section if your looking for actual drivers. But you would want to get that information from the manufacturers site.

You can't set autologon previous to running Sysprep and have it work after. It won't translate to the "new" machine. Although you can autologon with a local account with the sysprep.inf settings.

Not exactly. Mysysprep only helps with getting the proper HAL working on the machine. Nothing to do with BSODs because of incorrect mass storage drivers.

v3.2 is out!

v3.2 @ 2008-10-26 11:48pm EST - Created a function to scan for variables within the INF. Reducing bad data (hopefully eliminated). Scan speed is about the same.
v3.1.9.1 @ 2008-10-23 2:19pm EST - Scan time has also been reduced about 20%.
v3.1.9 @ 2008-10-23 11:49pm EST - Fixed flawed logic with strings. Hopefully rebuilding soon with a better way of handling strings. Though this version fixes some missed converting of strings into hwids.
v3.1.8 @ 2008-10-22 6:28pm EST - Adds install as an option (with DPinst.exe 32bit english only, copyright Microsoft), installing only hardware found on machine. Improves on scanning speed. Fixes some strings issue.

Yeah that's why I wrote mine in autoit.