Alrighty, so, previously I was parsing the .inf.ORG1 files as well, do you still want that? I've changed it a bit with the next version to only parse true, usable INF files. Also, I've created the ability to export all file information from the SourceDisksFiles section. It grabs root dir, file name, hash, version, modified date.

Quick question... I want to add some functionality to find file versions (through section SourceDisksFiles) for the actual driver (so I can sort of predict the "best" driver for a certain PNPID) but I'm unsure as to what exactly is the most important file for the driver... is it the .sys, .dll, .cat? I might still just allow export of all files with hash and file version though.

I'm also hoping to build a new scanning function to vastly improve, or should vastly improve, scanning time. Right now I'm using the built in functions to scan a single file multiple times (slow), I'm looking to scan one file into an array once (fast) and use that array multiple times instead.

Glad to hear! This version should catch EVERYTHING! haha... I remember posting that only a couple pages into the thread.

29

(109 replies, posted in Universal Imaging)

I don't think you're going to match PCI\VEN_10DE&DEV_0612&SUBSYS_82A81043&REV_A2\4&399D3C6A&0&0008 specifically. You'll probably only get a match off of PCI\VEN_10DE&DEV_0612&SUBSYS_82A81043&REV_A2 or anything between PCI\VEN_10DE&DEV_0612 and PCI\VEN_10DE&DEV_0612&SUBSYS_82A81043&REV_A2.

v3.2p @ 2011-02-28 -
-- Fixed issue with Reading sections bombing when key/value is directly followed by a section

http://db.tt/pSlc7sw

Yeah I got the same error while scanning another set of INF Files... I have to figure out what's going on there...

Anytime smile I'm assuming it's working?

v3.2o @ 2011-02-24 -

-- Fixed issue with Array growing to enormous proporations during reading INF File

-- !! BUGGED and WILL CRASH

v3.2n and previous would bomb on the Realtek WDM HD v2.57 driver that was mentioned earlier; specifically INF's HDALC.inf and HDXLC.INF.

v3.2N is up for downloads

-- Updated scanning for selecting Windows 7/Vista/2008/2008R2 OS's
-- Changed scan progress indication to a scanned to total scan items
-- Fixed issue with Automatically Choosing OS and Arch
-- Removed support for Pre NT Only INF Files

-- !! BUGGED and WILL CRASH

The error is coming from this function
http://www.autoitscript.com/forum/topic … ge__st__20

Error --
Array maximum size exceeded.:
Local $aSection[$nUBound +1][$nUBound +1]
Local $aSection[$nUBound +1][^ ERROR

...

Sorry guys I've  been kinda pre-occupied with life lately. I'll get a new version loaded somewhere... Figure out how to fix that bug.

37

(25 replies, posted in Software)

pferd5, are changes saved back to disk or is this something that's more like a iso boot that just get's stored into ram? Because if that's the case a reboot is obviously going to reset it. Perhaps you should look at boot-land.net and the 911cd.net forums for help on the solutions.

38

(25 replies, posted in Software)

pferd5 wrote:

I will write the error's i found, if i gonna remember my testing szenario wink. last i remeber is, that there was an inf (normal dpinst found) and your programm didn't found and showed the dpinst switches in a big gray dialogwindow. And there was referring an error in line xxxxx (i don't remember).

Try and remember to get the path that it's screwing up on. That'll help me hone in on what is causing the issue.

39

(25 replies, posted in Software)

Devcon has really been replaced by DPinst.exe for driver installations. However, devcon does give some nice information but you can get most of that though WMI.

I'm happy people are trying Drivergeek out. And yes for the most part it's an automated dpinst.exe installer. It's not meant to be the end all be all and some graphics and sound drivers are exceptionally bad at installing via normal means, and automatically.

DriverGeek v0.5 Beta 1

//-- Download --//
http://drop.io/wanderingit -- click DriverGeek for the beta download

//-- Version History --//
v0.5b1 - 2010-04-30 - Beta 1 for public trials

//-- Introduction --//
DriverGeek was designed from the ground up to be an easy and intelligent driver installation tool; replacing the aging tool DriverForge. It will automatically find and install all hardware drivers based on the driver paths that you select. The current version of DriverGeek will run in all supported x86 Windows operating systems (2000/XP/2003/Vista/2008/7 and PE's based on these); an x64 version will be released in the future but has not been compiled yet.

//-- Usage --//
To use the program is simple. Edit the dgconfig.ini file to set your configuration and then run the program to install the drivers. The first time you run the program it will create the dgconfig.ini file with all options. It will then open the ini file for you to edit it. Save the ini file when you are done editing. The ini lives in the same root directory as the program. You can use environment variables in your search paths. To put it into perspective the only option you really need to supply is for the section [Drivers] and a uncompressed drivers path for the option DriverSearchPaths. The settings below can be configured:

[Main]
; Run without prompts and progress even if prompts help, this has not been fully implemented, only for tooltips
; Blank defaults to 0 = No, 1 = Yes

RunSilent=

; Reboot after install completes
; Blank defaults to 0 = No, 1 = Yes

Reboot=

; Show Windows Device Manager during installation, it will close when driver installs have finished
; Blank defaults to 0 = No. 1 = yes

ShowDeviceManager=

; DpInst.exe is used in installing the drivers to the system. If DPInst.exe cannot be found or supplied the
; program will ask if you would like to default to Windows 2000/XP/2003 x86 default driver installation method
; using Rundll32.exe
; The temporary folder for running DPinst.exe from is deleted when the program exits
; Blank defaults to %temp%\drivergeek\bin

DPInstPath=

; Accept Software EULA, you must accept the EULA to run the program
; Blank defaults to 0 = No, 1 = Yes

AcceptEula=


[Drivers]
; Search Paths, multiple paths, or even INF file(s), separated via Pipe symbol
; Environment variables work with this option.

DriverSearchPaths=C:\D|C:\Windows\inf

; The software will automatically append the current programs directory your driver search path
; Blank defaults to 1 = Yes, 0 = No

ScanScriptDir=

; Search drives found, options are:
; ----> ALL, CDROM, Removable, Ramdisk, Fixed, Network (and Unknown, but shouldn't need to be used)
; The option "All" will take the place of needing to enter the rest of the options and will add all drives found
; You can add one or multiple, separating them with a Pipe symbol
; Blank will not search any "drives" for drivers

DriverSearchDrives=CDROM|REMOVABLE|RAMDISK

; Has not been implemented but will allow extraction of compressed drives from the path supplied
; and then extracted and installed from. This feature has not been implemented yet. The extracted drivers
; path will be appended to the DriverSearcPaths option.
; If a compressed drivers path is specified and a extract path is not the program will default
; to extract to %temp%\drivergeek\drivers and will be deleted after drive installation has completed
; If the program cannot extract to any directory extraction will be terminated, if no other driver
; path is specified the program will exit

CompressedDriversPath=
ExtractDriversPath=

Alrighty I found hosting and updated to v3.2m

just pm me your email address and i'll send it to you smile

Chris,

It's main purpose will still be to install drivers; whether it be after imaging, or normal driver installs, or PE environment driver installs. But it's going to be a bit more streamlined, hopefully less configuration settings and stable/faster.

Thanks for the kind words on DF, btw.

Chris,

I'm actually working on a completely new program called DriverGeek which should alleviate some issues I, and others, have always had with DriverForge (namely within PE environments). I'm also working on a new build of FindHWIDS to fix some bugs. It's all coming down the pike but I've been extremely busy lately. We're moving offices to a new building so it's crazy around here.

45

(50 replies, posted in Software)

Actually myself and a German member from msfn.org started DF before WarmSnow. And even then Madboy from MSFN.org developed his first before us, Pro-S Hardware.

I would however, like to see a tool that is modular and works well in all languages and open-source.

46

(6 replies, posted in Universal Imaging)

This is the HAL driver for you or CPU. You don't want to remove it, believe me. Is there a specific reason why?

Btw, are you Vietnamese?

smile I know Jeff-fah-fah... it's cool... thanks again!

Glad the selector is working for you wink

Dude like crazy man... moved our whole data center to a new building... ugh... fun

I'll see about the 3rd party server... nice idea

... someone edited my post... err... odd

The download is down for now... I have to find hosting somewhere for it.

Erik, does the filtering function work for OS type and OS arch?