[Release] DriverGrabber v0.5

[Siginet]

This small exe will grab all 3rd party drivers from your system and stick them into a "Drivers" directory in the same directory as the exe.

Very simple to use... ;) Not even a newbie can screw this up... (I hope). ;)

Just download the exe... and double click it! :eek:

Sit back untill the icon in the bottom right goes away. Yep you're done now. :D

Now post back here and let me know if it worked out for you.


You can download DriverGrabber Here:
Rate & Download DriverGrabber v0.5.1 at BetaNews.com (http://fileforum.betanews.com/detail/DriverGrabber/1170699160/1)
Download DriverGrabber v0.5.1 (http://www.siginetsoftware.com/forum/downloads.php?do=cat&id=2)



Change Log:
0.5 Beta
1. Now it builds a log file. In the log it shows all drivers that are skipped and what the provider is. It shows all drivers that were grabbed and the provider. It lists all files that were copied for each driver. It will log any directory creation errors.
2. There is now a DriverGrabber.ini file that you can specify a string to look for in each Provider you wish to skip and you can specify a String to skip if it is found in the drivers name. By default the drivergrabber.ini will have the info in it to have all microsoft drivers skipped:

[Provider]
Microsoft=Skip

[Name]
Microsoft Corporation=Skip
3. DriverGrabber will now detect if the system is x86 or x64 and use the correct devcon.exe needed for the system. So it should work fine with x64.

0.4 Beta:
1. Fixed some path bugs. Some drivers where not backed up because drivergrabber could not create a directory for the driver if they had certain symbols in their name. Thanks for your help pandera13!
2. I also put an error check when the new directory is made according to the drivers name. Now if the directory can not be created then a msgbox will pop up stating the directory name that it failed to create. If you get this error message please post it here so I can add a check for the symbol that is messing up the directory creation.
3. The Splash window now apears at the top of your desktop and not in the center. It also can now be moved around and placed wherever you want.
4. The splash window would flash like crazy whenever it went to the next step... so I fixed this so that it doesn't flash and it is much nicer to look at.

0.3 Beta:
1. Fixed grabbing of cat files. It should now correctly grab the cat files (as long as they exist... remember some drivers may not have had the cat files installed. If your cat file is not grabbed please search your harddrive for it or if your drivers inf file is named oem7.inf or simular search for oem7.cat etc...)
2. DriverGrabber should scan for drivers better now. So those of you who had missing drivers... please try the new version and post back here.
3. Splash window now shows progress.
4. Added Siginet copyright info.

0.2 Beta:
1. Should now grab needed cat files.
2. Better checking for Microsoft drivers so that it skips backing them up.


P.S. I just got news that it also works in Vista!!!

Edit: I got rid of the hide feature I was using to share the drivergrabber.exe because some people were having problems getting the file. So I attached the drivergrabber file to the post for all members to download.

[Zacam]

3 tests. 3 successes in an average of 17 seconds of operation.

First Test: Operation XPSP2 with RVM 2.1.0 and drivers on cd (MSFN method), returned exactly what was installed plus the Alchohol virtual drive.

Second Test: Virgin SP2 install with virgin Vendor drivers. Same results.

Third Test: RVM'd source without drivers on cd, virgin vendor drivers. Again, same results.

[ricktendo64]

Siginet can you maybe enable the backing up of .cat files

This is what B?shrat said about them:
They make or break WHQL signing... ;)

Not necessary, but good to have them.

[Siginet]

OK... I'll have to look into where the cats are saved and how to tell which cat goes to which driver.

[Siginet]

Updated to 0.2 Beta.

[IcemanND]

Nice work so far.

Though it did not grab any of the CAT files and it skipped a device that it shouldn't have:
Intel(R) PRO Wireless 2200BG Network Connection

I also don't recall that these are part of the windows installation, but they were not found either.
Mobile Intel(R) 915GM PM Express PCI Express Root Port - 2591
Mobile Intel(R) 915GM PM GMS 910GML Express Processor to DRAM Controller - 2590

It also grabbed a couple extra file with the ALPS Touchpad and Conextant modem drivers, but every app of this type seems to grab an extra file here and there so it's not a big deal.

Not sure why it skipped the Intel drivers but let me know if I can help.


And this may help you figure out why it didn't get the wireless driver, it also did not get the VMware net drivers, cisco vpn adapter driver, and deterministic network enhancer miniprot driver. none of which I care about but they all fall under the network adapter category.

Thanks for the work. Keep it up

[Siginet]

Thanks for the info. Could you please post the inf files for me? on the ones that did not get grabbed properly. I need to see those infs to understand why they weren't grabbed.

[ricktendo64]

It skips some of my Device Drivers also

[IcemanND]

I'll post the inf's later tomorrow. Not at that machine anymore. And I can test it on a few more machines and let you know the results.

[ricktendo64]

It wont grab my Sampsung Monitor or my S3G built in Graphics
Here are the .inf files http://www.mytempdir.com/843153

[Siginet]

It skips some of my Device Drivers also

BTW: Chek out eggsters version of---> DP Base Driver Pack Creator (http://s8.createphpbb.com/jybesystems/viewtopic.php?t=9&sid=14e504ed19d275c7786757f0b9979032&mforum=jybesystems), its got a 7zipper
Maybe you two can get together combine your brain power and make one killer app.

I think he cheated a little :P

http://img99.imageshack.us/img99/135/dpblq1.jpg

LOL. well the plan in the end is to make it 7zip to a driverpack. I really wish eggster would have contacted me first. I haven't added 7zip support yet because it isn't fully functioning at grabbing the drivers. Also...eggster... no offence but you should give credit where credit is due. I spent some time coding the drivergrabber file and it isn't very cool to say you created it.

[Siginet]

I'll post the inf's later tomorrow. Not at that machine anymore. And I can test it on a few more machines and let you know the results.

Hmmm... weird because it should grab them. It is only supposed to skip those that are provided by microsoft. It checks the provider=
and it checks the name of the driver for any instance of "Microsoft Corporation".

[Siginet]

Ok... I updated drivergrabber.exe we are now at 0.3 Beta. ;)

[IcemanND]

0.3 beta got the CAT, still skips the Intel drivers.


I zipped the two critical inf's from Intel like I said before I don't care about thecisco vpn, deterministic network miniport driver or the VMware drivers, they all have to be reinstalled with their respective installers to work right anyway.

http://www.mytempdir.com/843838

[ricktendo64]

Awesome Siginet, it Rocks!, I Love the new Icon and Splash Screen :twisted:

And it got my .cats

[Siginet]

0.3 beta got the CAT, still skips the Intel drivers.


I zipped the two critical inf's from Intel like I said before I don't care about thecisco vpn, deterministic network miniport driver or the VMware drivers, they all have to be reinstalled with their respective installers to work right anyway.

http://www.mytempdir.com/843838

I'm not sure why it doesn't grab those 2 intel drivers. All I can think is devcon does not recognise them.

[IcemanND]

if I do DEVCON FIND =Net
it returns the wireless adapter


PCI\VEN_14E4&DEV_1677&SUBSYS_01861028&REV_01\4&2959CBDC&0&00E0: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_4220&SUBSYS_27218086&REV_05\4&2FA23535&0&18F0: Intel(R) PRO/Wireless 2200BG Network Connection
ROOT\DNI_DNEMP\0000 : Intel(R) PRO/Wireless 2200BG Network Connection - Deterministic Network Enhancer Miniport
ROOT\DNI_DNEMP\0001 : Broadcom NetXtreme 57xx Gigabit Controller - Deterministic Network Enhancer Miniport
ROOT\DNI_DNEMP\0002 : WAN Miniport (IP) - Deterministic Network Enhancer Miniport
ROOT\DNI_DNEMP\0003 : Cisco Systems VPN Adapter - Deterministic Network Enhancer Miniport
ROOT\MS_PSCHEDMP\0001 : Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport
ROOT\MS_PSCHEDMP\0002 : Intel(R) PRO/Wireless 2200BG Network Connection - Packet Scheduler Miniport
ROOT\MS_PSCHEDMP\0003 : Cisco Systems VPN Adapter - Packet Scheduler Miniport
ROOT\MS_PSCHEDMP\0004 : WAN Miniport (Network Monitor) - Packet Scheduler Miniport
ROOT\MS_PTIMINIPORT\0000 : Direct Parallel
ROOT\NET\0000 : Cisco Systems VPN Adapter
ROOT\VMWARE\0000 : VMware Virtual Ethernet Adapter for VMnet1
ROOT\VMWARE\0001 : VMware Virtual Ethernet Adapter for VMnet8

Same type of thing with devcon driverfiles =net

How are you using Devcon to find the devices? Or is it stopping with the first device in the class, my broadcom NIC in this case?

Let me know how I can help.

[Siginet]

basically I run:
devcon classes

to return all of the classes.

Then on each class shown I run devcon driverfiles =$class

I'll have to see if for some reason drivergrabber is not parseing the log files correctly.

Can you perform a
devcon driverfiles =net > C:\net.log
for me and post the log here so I can take a look at it?

thanks.

[IcemanND]

PCI\VEN_14E4&DEV_1677&SUBSYS_01861028&REV_01\4&2959CBDC&0&00E0
Name: Broadcom NetXtreme 57xx Gigabit Controller
Driver installed from c:\windows\inf\oem5.inf [BCM5750A1DMOBILE.XpInst]. 1 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\b57xp32.sys
PCI\VEN_8086&DEV_4220&SUBSYS_27218086&REV_05\4&2FA23535&0&18F0
Name: Intel(R) PRO/Wireless 2200BG Network Connection
Driver installed from c:\windows\inf\oem6.inf [Install_DELLMPCI3A_BG_XP]. 3 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\w29n51.sys
C:\WINDOWS\system32\w29NCPA.dll
C:\WINDOWS\system32\w29mlres.dll
ROOT\DNI_DNEMP\0000
Name: Intel(R) PRO/Wireless 2200BG Network Connection - Deterministic Network Enhancer Miniport
Driver installed from c:\windows\inf\oem16.inf [DneMP.ndi.NT]. No files used by driver.
ROOT\DNI_DNEMP\0001
Name: Broadcom NetXtreme 57xx Gigabit Controller - Deterministic Network Enhancer Miniport
Driver installed from c:\windows\inf\oem16.inf [DneMP.ndi.NT]. No files used by driver.
ROOT\DNI_DNEMP\0002
Name: WAN Miniport (IP) - Deterministic Network Enhancer Miniport
Driver installed from c:\windows\inf\oem16.inf [DneMP.ndi.NT]. No files used by driver.
ROOT\DNI_DNEMP\0003
Name: Cisco Systems VPN Adapter - Deterministic Network Enhancer Miniport
Driver installed from c:\windows\inf\oem16.inf [DneMP.ndi.NT]. No files used by driver.
ROOT\DNI_DNEMP\0004
Name: WAN Miniport (Network Monitor) - Deterministic Network Enhancer Miniport
Driver installed from c:\windows\inf\oem16.inf [DneMP.ndi.NT]. No files used by driver.
ROOT\MS_L2TPMINIPORT\0000
Name: WAN Miniport (L2TP)
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-L2tp]. No files used by driver.
ROOT\MS_NDISWANBH\0000
Name: WAN Miniport (Network Monitor)
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-Bh]. No files used by driver.
ROOT\MS_NDISWANIP\0000
Name: WAN Miniport (IP)
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-Ip]. No files used by driver.
ROOT\MS_PPPOEMINIPORT\0000
Name: WAN Miniport (PPPOE)
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-Pppoe]. No files used by driver.
ROOT\MS_PPTPMINIPORT\0000
Name: WAN Miniport (PPTP)
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-Pptp]. No files used by driver.
ROOT\MS_PSCHEDMP\0000
Name: WAN Miniport (IP) - Packet Scheduler Miniport
Driver installed from c:\windows\inf\netpsa.inf [PSchedMP.ndi]. No files used by driver.
ROOT\MS_PSCHEDMP\0001
Name: Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport
Driver installed from c:\windows\inf\netpsa.inf [PSchedMP.ndi]. No files used by driver.
ROOT\MS_PSCHEDMP\0002
Name: Intel(R) PRO/Wireless 2200BG Network Connection - Packet Scheduler Miniport
Driver installed from c:\windows\inf\netpsa.inf [PSchedMP.ndi]. No files used by driver.
ROOT\MS_PSCHEDMP\0003
Name: Cisco Systems VPN Adapter - Packet Scheduler Miniport
Driver installed from c:\windows\inf\netpsa.inf [PSchedMP.ndi]. No files used by driver.
ROOT\MS_PSCHEDMP\0004
Name: WAN Miniport (Network Monitor) - Packet Scheduler Miniport
Driver installed from c:\windows\inf\netpsa.inf [PSchedMP.ndi]. No files used by driver.
ROOT\MS_PTIMINIPORT\0000
Name: Direct Parallel
Driver installed from c:\windows\inf\netrasa.inf [Ndi-Mp-Pti]. No files used by driver.
ROOT\NET\0000
Name: Cisco Systems VPN Adapter
Driver installed from c:\windows\inf\oem17.inf [Cisco.ndi]. 1 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\CVirtA.sys
ROOT\VMWARE\0000
Name: VMware Virtual Ethernet Adapter for VMnet1
Driver installed from c:\windows\inf\oem21.inf [VMnetAdapter1.Install]. 3 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\vmnet.sys
C:\WINDOWS\system32\DRIVERS\vmnetadapter.sys
C:\WINDOWS\system32\vnetinst.dll
ROOT\VMWARE\0001
Name: VMware Virtual Ethernet Adapter for VMnet8
Driver installed from c:\windows\inf\oem21.inf [VMnetAdapter8.Install]. 3 file(s) used by driver:
C:\WINDOWS\system32\DRIVERS\vmnet.sys
C:\WINDOWS\system32\DRIVERS\vmnetadapter.sys
C:\WINDOWS\system32\vnetinst.dll
21 matching device(s) found.

[IcemanND]

Any further developments?

[Siginet]

Not latley. Sorry I have been really busy latley.
Not sure why there is an issue with grabbing your drivers though. :(

I'm thinking that it will just be one of those things that we will live with for a while until we can narrow down the error.

I think soon I will make a driverpacker program based on drivergrabber. But that will have to wait until I have more time. ;)

[lynx]

Is there a way to use the Driver_Packer program not during an install, but while in Windows?

Say you get in a PC that is missing three drivers. Is there a way to run the program to install them automaticly, without having to look them up on the net and manually installing them?

[pandera13]

Anyone know of a program similar to this that will run silently and update a network directory by chance? Basically I am wanting to run the program on all of our workstations to grab each unique driver from our workstations.

I want to create a customized driverpack from list. I am looking into a way to script DevCon to updatea DB based on unique PNPID, but limited scripting knowledge and time itself is a killer.

If you run from a network either unc or mapped drive you get an autoit error
For$c=1 to $myclasses[0]
For $c=1 to $myclasses^Error
Error Subscript used with non-Array variable


By the way, this util is awesome, very ice job

Thanks for any info in advance

[Siginet]

does your mapped drive have write access?

[pandera13]

Yeah, it seems it may only be an issue with my production box. Tested on three other systems and seems to work ok.

[pandera13]

The issue with the Intel Drivers is the Name itself. DriverGrabber can not create the directory because of invalid characters. / \ * < > " and | are all invalid characters in directory names.

So doing a replace function in the name string turns
Intel(R) PRO/Wireless 2200BG Network Connection
into
Intel(R) PROWireless 2200BG Network Connection
and allows the directory to be created correctly.

Hopefully that helps out in the next version.

[Siginet]

Thanks a lot for the tip! :D I will fix this in the next version. ;)

[dbsignet]

When I run DriverGrabber 0.3, My RAID drivers are not in the Drivers folder from where DriverGrabber 0.3 is run. my drivers are:
A:\txtsetup.oem
A:\disk 1
A:\Win_XP\hpt3xx.cat
A:\Win_XP\hpt3xx.inf
A:\Win_XP\hpt3xx.sys
A:\Win_XP\hptpro.sys
Thanks, Donald

[Siginet]

pandera13 has given me some good tips and came up with some good solutions for a lot of the reasons some drivers are not backed up. As soon as I get some spare time I will begin working on v0.4.

[pandera13]

Have to ask the obvious question, but where did you run DriverGrabber from? The driver also has to be installed on the current system for DriverGrabber to work correctly.

Also, did you search the driver directory created by DriverGrabber for the file hptpro.sys by chance? Since this is a raid driver, it may be located under SCSIAdapter

[dbsignet]

I ran DriverGrabber from My Downloads Folder and from C;|>, still got the same results.

[pandera13]

Did you search the drivers directory for hptpro.sys by chance?

Also have to ask, but are you trying to grab the drivers from the floppy disc itself?

You can try running "devcon find =scsiadapter" from a command prompt and see if it lists any raid devices.

You will of course have to download devcon.exe if you do not have it.

[dbsignet]

Did you search the drivers directory for hptpro.sys by chance?
No, it wasn't in there-- I searched by MS Search for "hptpro.sys".

Also have to ask, but are you trying to grab the drivers from the floppy disc itself?

No. Used the Unarchived contents in: C:\Documents and Settings\Donald\My Documents\Jeff Stuff\hp_drv\Win_XP\hptpro.sys

You can try running "devcon find =scsiadapter" from a command prompt and see if it lists any raid devices.

You will of course have to download devcon.exe if you do not have it.

Where is 'devcon.exe' ? I searched on Signet and came up blank; no devcon.exe.

-- Thanks, Donald

[pandera13]

I think Devcon is a part of the Windows XP resource kit.

Do you have the device actually installed on the machine you are running DriverGrabber from? If the driver is not installed, then DriverGrabber will not be able to copy the needed files to the driver directory.

You can try a Nlite if you need to integrate drivers. It will parse a subdirectory of drivers and allow you to pick and choose which drivers to integrate. http://www.nliteos.com

[elbrute]

Driver Grabber 0.3 Beta
Ran it, and this is what I got;

Display\empty

hdc\VIA Bus Master IDE Controller\oem2.inf, viaide.sys, viamini.cat

Monitor\Dell P991\oem12.inf, DELLMON0.cat, P991.icm

Net\D-Link DFE-530TX+ PCI Adapter\oem10.inf, DLKRTS.sys, NETDLKR5.cat

SCSIAdapter\Win2000 Promise Ultra100 (tm) IDE Controller (PDC20265)\oem7.inf, Ultra.sys

Didn't pick up my nVidia geforce2 gts 30.82 drivers.
Didn't pick up my Creative PCI16 drivers.
Missed the Ultra.cat file. Was in the C;\WINNT\OemDir\
I updated the Promise drivers about a year after the initial install,
maybe that shuffled things up a bit.
Probably missing some chipset drivers too.
Like cpu to agp, cup to pci, ect.
Keep it up. This looks to be a good program.

elbrute

[Floppy]

@Siginet
:D Very good!

Iam using the BTS driverpacks....would it be possible to alter the DriverGrabber.exe so it saves the driver's in "BTS driverpacks" mode. :?:

Hope you understand what I mean, my English is not to good. :roll:


EDIT
Sorry, just read your post over at DriverPacks.net Forum. You are working at it right now. Did not mean to nag!!

[komsboy_more]

thank you ................................

[Silyn]

Nice ^^
Can't wait to try it xD

[Siginet]

New version released! :D I fixed some path bugs which caused some drivers not to get backed up. I also modified a few other small things here and there. ;)

Please let me know if you still have issues when backing up your drivers.

Thanks for the help pandera13!

[Siginet]

It works in Vista too! :D

[baldboy]

i want it so much

[the_guy]

For some reason I can't get at the hidden content even though I clicked the Thanks icon.

the_guy

[ProfessorCPU]

For some reason I can't get at the hidden content even though I clicked the Thanks icon.

the_guy
Really? Have you tried to refresh the page? anyone else having an issue?

I'll pm the info to you if you still have an issue. The only reason I added the hide hack is so I can keep track of how many people are interested in using it. When I see a lot of people are interested then I know that it is a program that is worth my time to keep coding. :D

Obviously the DriverGrabber tools is much more popular than I thought. :D

[racerx]

works great! thanks:D

[krismark]

:) Love it:p

[tiby]

good job
thanks.

[Kumo]

nice!

I try it now

[samuraj1000]

gooooood stuff :D

[shane]

Thank you!

[ric]

tnx for this

[nas75019]

THANKS A LOT !

Very good soft

[dr4g0n]

This is good soft!
Many fucking thanks!

[cbuk2k]

Just a not to say thanks

[alwayscamp]

thanks alot

[Kevin523]

Thanks for a wonderful program. I find it very useful!

[jarod]

Thank you for this

[brittosa]

thanks! just begining to get tired of MyDrivers.:)

[Drm]

I 'm not sure, that 'Thanks' button works as it should...

[rolandt52]

Cool tool. But I do not see the "Thank you" icon at all.

[tryme2k]

thanks for the dl.

[emily]

thanks you for sharing

[pandera13]

I lost my job due to a lay off so won't be able to play around with the new code for a few. Looks like you have added some nince featues and the fact that it supports Vista rocks.

Nice job man,

Jerry

[kelaniz]

That is the coolest utility I've ever seen in my life. Can't beat those things you didn't know you needed until ya find 'em. Thanks very much for creating it.

[mickk]

Hi guys

Been looking for a program like this for a long time but it doesn't seem to work for me i run the file but it doesn't get anything. i copied the file to the root of c and it will not even create a drivers folder. I tried searching for it but the only folder it finds is the driver folder from system32. I'm using Windows XP SP2

[ProfessorCPU]

Hmmm... that is the first post I have heard of with this proble. Does it give you any errors whatsoever?

Maybe you got a bad download of it? Try re-downloading it and see if that clears your problem. It should create the Drivers folder in the same place that it is run from.

Keep me posted.

[pup]

AutoIT Error

Line 0 (File "C:\Windows\Desktop\DriverGrabber\DriverGrabber.exe"):
For $UD11F21D03DFA2CE2 = 1 To $UD11F21D03D5A2BE2[0]
For $UD11F21D03DFA2CE2 = 1 To $UD11F21D03D5A2BE2^ ERROR
Error: Subscript used with non-Array variable.

Error starting program

The DEV.EXE file is linked to missing export SETUPAPI.DLL:CM_Free_Log_Conf_Handle.

[Siginet]

hmmm...
DriverGrabber.ex e
There is a space in the name... is that a typo?

Are you trying to use this on Windows 9x? I doubt if it will work in a 9x environment because:

You can use DevCon with Microsoft Windows 2000, Windows XP, and Windows Server 2003. You cannot use DevCon with Windows 95, Windows 98, or Windows Millennium Edition.

devcon is the main file used inside of DriverGrabber to get the driver info from the computer. :(

For the next version of drivergrabber I am going to be testing another alternative to get drivers as well. But I am not sure if it will work or not. I would like to have drivergrabber work on win9x systems because as a computer tech... you still may have the need to backup drivers on 9x. Actually I think backing up drivers on 9x would be great because finding drivers for 9x systems can be a pain... I know. :(

Thanks for posting.

[mickk]

when i run drivergrabber it looks like its working the window appears and it just runs thew a list of devices saying processing an after a couple seconds it disappears and cannot find out if it generated or anything. anyway i was trying to do this when on a system with a critical system error was reported in windows. I got the system reinstalled and windows found all the drivers anyway. when i get home i will try it again on the system now it is fresh

[ccolijn]

I used it in winxp 64, it looks like it's working but i can't find the result. Where are the driver put?

Chris Colijn

[Siginet]

when i run drivergrabber it looks like its working the window appears and it just runs thew a list of devices saying processing an after a couple seconds it disappears and cannot find out if it generated or anything. anyway i was trying to do this when on a system with a critical system error was reported in windows. I got the system reinstalled and windows found all the drivers anyway. when i get home i will try it again on the system now it is fresh

That may be why it had no output. Because there were no third party drivers installed. :) It recognized only microsoft drivers... and it skips microsoft drivers.

@ccolijn I think drivergrabber v0.4 may not work on an x64 OS. :(
But I am going to try to add support for it in the next version. Actually I think I have allready made support for x64... but I am not ready to release v0.5 yet. If you are interested PM me and I will let you test what I have so far to see if it works in an x64 environment. ;)

[mcube]

I could not get the DriverGrabber 0.4 to work (this is the first version I have tried). Attached is the error I got. Could it be because I am not booting off C:? My Boot Drive is E:

[koszopal]

ok like in begining this tread didnt find my wireless drivers :(
device name is "Intel(R) PRO/Wireless 2200BG Network Connection"
koszopal
:(
ps devcon driverfiles =net
...
PCI\VEN_8086&DEV_4220&SUBSYS_27128086&REV_05\4&39A85202&0&10F0
Name: Intel(R) PRO/Wireless 2200BG Network Connection
No driver information available for device
.....
but i found thet in device manager that he uses w22n51.sys
and this file is with .inf in
c:\<windir>\system32\ReinstallBackups\<nr>\DriverFiles\w22n51.inf

[Siginet]

It should find it now. Unless it is a microsoft driver. Can you post the inf file for it?

[Siginet]

Ok this is what I have added to v0.5 so far.

1. Now it builds a log file. In the log it shows all drivers that are skipped and what the provider is. It shows all drivers that were grabbed and the provider. It lists all files that were copied for each driver. It will log any directory creation errors.

2. There is now a DriverGrabber.ini file that you can specify a string to look for in each Provider you wish to skip and you can specify a String to skip if it is found in the drivers name. By default the drivergrabber.ini will have the info in it to have all microsoft drivers skipped:

[Provider]
Microsoft=Skip

[Name]
Microsoft Corporation=Skip

3. DriverGrabber will now detect if the system is x86 or x64 and use the correct devcon.exe needed for the system. So it should work fine with x64.

I plan on releasing v0.5 soon. Are there any other ideas that I should consider adding?


Here is a DriverGrabber.log that was created when I ran DriverGrabber.exe v0.5 on my laptop:
*Note: I had LogMeIn added as a String to skip in the [Provider] section of my DriverGrabber.ini.

;- Log Started 02/08/2007 - 04:12:41
;- WIN_XP Service Pack 2 X86 System Found.
;- Computer name is: HOME-LAPTOP

[Logged Errors]

[Grabbed Drivers]
NVIDIA GeForce Go 6150=NVIDIA
NVIDIA nForce 430410 Serial ATA Controller=NVIDIA Corporation
Ricoh Memory Stick Host Controller=Ricoh Company
Ricoh MMC Host Controller=Ricoh Company
Ricoh xD-Picture Card Host Controller=Ricoh Company
Conexant High Definition Audio=Conexant
HDAUDIO Soft Data Fax Modem with SmartCP=CXT
Synaptics PS2 Port TouchPad=Synaptics
Broadcom 802.11bg WLAN=Broadcom
AMD Turion(tm) 64 X2 Mobile Technology TL-50=Advanced Micro Devices
HP Quick Launch Buttons=Hewlett-Packard

[Skipped Drivers]
Standard OpenHCD USB Host Controller=Microsoft
Standard Enhanced PCI to USB Host Controller=Microsoft
USB Root Hub=Microsoft
HL-DT-ST DVDRAM GSA-4084N=Microsoft
RI5396A XMB368K SCSI CdRom Device=Microsoft
ACPI Multiprocessor PC=Microsoft
HTS541080G9SA00=Microsoft
LogMeIn Mirror Driver=LogMeIn, Inc.
Standard Dual Channel PCI IDE Controller=Microsoft
Primary IDE Channel=Microsoft
Secondary IDE Channel=Microsoft
Standard 101102-Key or Microsoft Natural PS2 Keyboard=Microsoft
HID Keyboard Device=Microsoft
Audio Codecs=Microsoft
Legacy Audio Drivers=Microsoft
Media Control Devices=Microsoft
Legacy Video Capture Devices=Microsoft
Video Codecs=Microsoft
Microsoft Kernel System Audio Device=Microsoft
Microsoft Kernel Wave Audio Mixer=Microsoft
Microsoft WINMM WDM Audio Compatibility Driver=Microsoft
Plug and Play Monitor=Microsoft
WAN Miniport (L2TP)=Microsoft
ACPI Fixed Feature Button=Microsoft
OHCI Compliant IEEE 1394 Host Controller=Microsoft
Generic volume=Microsoft
Microsoft AC Adapter=Microsoft
Microsoft ACPI-Compliant Control Method Battery=Microsoft
SDA Standard Compliant SD Host Controller=Microsoft

[NVIDIA GeForce Go 6150]
c:\windows\inf\oem9.inf=Grabbed
C:\WINDOWS\system32\DRIVERS\nv4_mini.sys=Grabbed
C:\WINDOWS\system32\nv4_disp.dll=Grabbed
C:\WINDOWS\system32\nvsvc32.exe=Grabbed
C:\WINDOWS\system32\nvapi.dll=Grabbed
C:\WINDOWS\system32\nvoglnt.dll=Grabbed
C:\WINDOWS\system32\nvcpl.dll=Grabbed
C:\WINDOWS\system32\nvmctray.dll=Grabbed
C:\WINDOWS\system32\nvwddi.dll=Grabbed
C:\WINDOWS\help\nvcpl.hlp=Grabbed
C:\WINDOWS\help\nvwcplen.hlp=Grabbed
C:\WINDOWS\system32\nvcod.dll=Grabbed
C:\WINDOWS\system32\nvcodins.dll=Grabbed

[NVIDIA nForce 430410 Serial ATA Controller]
c:\windows\inf\oem22.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem22.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\nvata.sys=Grabbed
C:\WINDOWS\system32\idecoi.dll=Grabbed
C:\WINDOWS\system32\idecoiins.dll=Grabbed
C:\WINDOWS\system32\NVCOI.DLL=Grabbed

[Ricoh Memory Stick Host Controller]
c:\windows\inf\oem13.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem13.cat=Grabbed
C:\WINDOWS\system32\snymsico.dll=Grabbed
C:\WINDOWS\system32\DRIVERS\rimsptsk.sys=Grabbed

[Ricoh MMC Host Controller]
c:\windows\inf\oem14.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem14.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\rimmptsk.sys=Grabbed

[Ricoh xD-Picture Card Host Controller]
c:\windows\inf\oem12.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem12.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\rixdptsk.sys=Grabbed
C:\WINDOWS\system32\rixdicon.dll=Grabbed

[Conexant High Definition Audio]
c:\windows\inf\oem26.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.cat=Grabbed
C:\WINDOWS\system32\ksuser.dll=Grabbed
C:\WINDOWS\system32\ksproxy.ax=Grabbed
C:\WINDOWS\system32\drivers\ks.sys=Grabbed
C:\WINDOWS\system32\drivers\drmk.sys=Grabbed
C:\WINDOWS\system32\drivers\portcls.sys=Grabbed
C:\WINDOWS\system32\drivers\stream.sys=Grabbed
C:\WINDOWS\system32\wdmaud.drv=Grabbed
C:\WINDOWS\system32\drivers\CHDAud.sys=Grabbed
C:\WINDOWS\system32\CHdAudprop.dll=Grabbed
C:\WINDOWS\system32\CHdAudPropres.dll=Grabbed
C:\WINDOWS\system32\CHDAudPropShortcut.exe=Grabbed
C:\Program Files\CONEXANT\CNXT_HDAUDIO\HXFSetup.exe=Grabbed
C:\WINDOWS\system32\UCI32105.dll=Grabbed

[HDAUDIO Soft Data Fax Modem with SmartCP]
c:\windows\inf\oem25.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem25.cat=Grabbed
C:\WINDOWS\SYSTEM32\DRIVERS\HSF_CNXT.sys=Grabbed
C:\WINDOWS\SYSTEM32\DRIVERS\HSFHWAZL.sys=Grabbed
C:\WINDOWS\SYSTEM32\DRIVERS\HSF_DPV.sys=Grabbed
C:\WINDOWS\SYSTEM32\DRIVERS\mdmxsdk.sys=Grabbed
C:\WINDOWS\SYSTEM32\DRIVERS\HSFProf.cty=Grabbed
C:\WINDOWS\system32\mdmxsdk.dll=Grabbed
C:\Program Files\CONEXANT\CNXT_MODEM_PCI_VEN_14F1&DEV_5045_at8ven5m\HXFSetup.exe=Grabbed
C:\WINDOWS\system32\uci32108.dll=Grabbed

[Synaptics PS2 Port TouchPad]
c:\windows\inf\oem23.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem23.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\i8042prt.sys=Grabbed
C:\WINDOWS\system32\DRIVERS\mouclass.sys=Grabbed
C:\WINDOWS\system32\DRIVERS\SynTP.sys=Grabbed
C:\WINDOWS\system32\SynTPAPI.dll=Grabbed
C:\WINDOWS\system32\SynTPFcs.dll=Grabbed
C:\WINDOWS\system32\SynCOM.dll=Grabbed
C:\WINDOWS\system32\SynCtrl.dll=Grabbed
C:\Program Files\Synaptics\SynTP\SynTPLpr.exe=Grabbed
C:\Program Files\Synaptics\SynTP\SynTPCpl.dll=Grabbed
C:\Program Files\Synaptics\SynTP\SynCntxt.rtf=Grabbed
C:\Program Files\Synaptics\SynTP\SynZMetr.exe=Grabbed
C:\Program Files\Synaptics\SynTP\SynMood.exe=Grabbed
C:\Program Files\Synaptics\SynTP\SynTPEnh.exe=Grabbed
C:\Program Files\Synaptics\SynTP\SynTPEnh.ini=Grabbed
C:\Program Files\Synaptics\SynTP\SynTPCOM.dll=Grabbed
C:\Program Files\Synaptics\SynTP\Tutorial.exe=Grabbed
C:\Program Files\Synaptics\SynTP\InstNT.exe=Grabbed
C:\Program Files\Synaptics\SynTP\SynISDLL.dll=Grabbed
C:\Program Files\Synaptics\SynTP\SynUnst.ini=Grabbed
C:\WINDOWS\system32\SynTPCo2.dll=Grabbed

[Broadcom 802.11bg WLAN]
c:\windows\inf\oem27.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem27.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\BCMWL5.SYS=Grabbed

[AMD Turion(tm) 64 X2 Mobile Technology TL-50]
c:\windows\inf\oem1.inf=Grabbed
C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem1.cat=Grabbed
C:\WINDOWS\system32\DRIVERS\AmdK8.sys=Grabbed


[HP Quick Launch Buttons]
c:\windows\inf\oem24.inf=Grabbed

[koszopal]

when can i try version 0.5 ?
koszopal
PS here is link to this inf http://media3.filewind.com/g.php?filepath=5820

[ProfessorCPU]

v0.5 has been uploaded to the download link for a couple days now. ;)

[koszopal]

tryed but seems to notfinding my wireless too
koszopal

[ProfessorCPU]

And your log?

All I can think is the driver for that does not follow the guidlines of any other driver. If devcon is recognising it as no driver files then that would seem to be a driver that isn't a normal type of driver?

[mielus_e]

Hi there,

Nice program, like it very much.
The only thing that seems te be missing is grabbing printer drivers.

I grabbed with this drivergrabber.ini file:
[Provider]

[Name]

So it should grab all drivers, but I don't see any printers
Can grabbing printer drivers be done? Or does it need to be implemented first?

Thanks,

Mielus

[Siginet]

If your printer is not on then it will not grab the driver. If it is on it will get the drivers from your printer.

[iiyama]

Thanks for this but once ran where do you find the drivers to save to disk etc?

[ProfessorCPU]

If there are any third party drivers on the system they will be saved to a Drivers directory in the same area ad the drivergrabber.exe

If you do not have any Driver directory then your system is only using Microsoft drivers which means if you were to reinstall more than likely all of your drivers would be installed by default from Windows.

You can look in the log file to see all of the drivers that were skipped. You should not see any drivers that were grabbed if you don't have a new drivers folder. As you will see in the log each skipped driver will probably = Microsoft and that is why it is skipped. If for some reason you want to backup microsoft drivers just delete the microsoft entries in drivergrabber.ini and re reun the drivergrabber.exe. But most people do not need the microsoft drivers whatsoever. ;)

[iiyama]

Thanks found that. So the grabbed drivers do I just click on any exe folders to reinstall?

[ProfessorCPU]

No the grabbed drivers are for use in a windows install disk or you can use device manager to browse to the folder and install the driver. In a later version of drivergrabber I may include compiled exes.

[mediapla]

Possible to use it with the VISTA OS ?

[ProfessorCPU]

Possible to use it with the VISTA OS ?
I have been told it works fin in Vista. :)

I don't know if it works fine in an x64 environment or not? It should work on an x64 environment because I added x64 support... but I don't have a current x64 installation of windows to test it on yet. I just purchased Vista Ultimate x64... so I'll be installing it soon so I can test it and also update all of my other programs to function in a Vista/x64 environment. ;)

[mediapla]

Great tool to make XP DriverPacks and Recovery CDs. Tried it out today in our store with our first Vista PC(X86/32bit) but it doesnd create driver folders. Dev.exe is running, i see a short cmd window - that all, only a ini file is created

[ProfessorCPU]

Hmmm... that's odd. You shouldn't see a cmd window either. It doesn't create a log file? The ini file should have came with drivergrabber.exe I'd check your md5 hash and see if it matches.

[mediapla]

Hi, it runs fine now !!! Im a little bit new in Vista, must try something to learn. Now I have switch off the "User Account Control" - in control panel - and it runs !!! Thank you for that little prog

[Gambit]

I just ran the util on a Dell Latitude D620 with an Extreme Gigabit Broadcom NIC and a Wifi nic also by Broadcom and it didn't return either in the Drivers\Net folder. Only item it returned was the BT PAN by Toshiba. Is there any info I can provide to assist with future detection of these two NICs?

[Siginet]

Please Post the log file.

[spirou38]

Hi Siginet,

Does your nice utility copy or move the drivers ? So, can I remove the directory after saving it ?

Best regards and many thanks :)

Pascal

[rkillcrazy]

Hi Siginet,

Does your nice utility copy or move the drivers ? So, can I remove the directory after saving it ?

Best regards and many thanks :)

Pascal

I build & repair PCs all the time - it's my job. That said, I highly doubt this app MOVES the drivers. If that were the case, your OS would challenge you for driver disks every time you booted up after running this app.

[Siginet]

It copies the drivers to a folder called "DRIVERS" where drivergrabber.exe is executed. ;)

[sjgoossen]

I'm trying to run this on Vista Ultimate 64 (sjg member of admin, UAC is off) by keep getting the following message. Dev.exe appears to be a 32 bit file from 2002....



---------------------------
cmd.exe - Machine Type Mismatch
---------------------------
The image file C:\Users\sjg\AppData\Local\Temp\DGBR\dev.exe is valid, but is for a machine type other than the current machine.
---------------------------
OK
---------------------------

[Siginet]

Hmmm... could you post the log file for me?
Thx

[sjgoossen]

.... sorry bout that, was going to with the first post...


----
;- Log Started 04/11/2007 - 13:37:09
;- WIN_VISTA X64 System Found.
;- Computer name is: HUMMER
;- X64 Devcon being used.

[Logged Errors]

[Grabbed Drivers]

[Skipped Drivers]


---------

[alhaddar]

thank DriverGrabber v0.5.1

[Overkill]

Works great! Thanks for coding this thing!

I have a few suggestions for this tool that would help make it much more functional :) (for me at least)
let me know what you think

1) for when a set of drivers already exists:

* check files to be backed up against existing files
* if they are all the same then skip the "grab"
* if they are not all the same, then ask if user wants to use the newer drivers, keep older drivers, or auto-rename the driver that's being backed up.
* a "save this response" checkbox that writes a value to the ini file

2) give the user the option of using a different directory than drivers via ini file with ability to use relative (to drivergrabber.exe) and absolute paths.

3) add a command line switch for choosing the ini (I have a few different offices that have different driver sets...would be nice to write my own little launcher for it that can back up to a variable location. I don't want accidentally overwrite audio drivers for office A with those for office B; I'd rather keep the two in different folders without having to rename "drivers" all the time.

4) prevent user from launching two instances of the app at the same time.

5) have the task show up in the task bar =)

thanks
overkill

[Siginet]

All of your requests are planned for a future release. I am actually thinking of having DriverGrabber look into the ini file for a custom location to place the files. By default it will save to the Drivers folder but in the next release I will have it backup to the Driver\ComputerName folder. Which will work much better on a network.

I will have drivergrabber check if a ComputerName directory allready exists. If it exists it will prompt the user.

as with all of my tools... I plan on adding unattended switches to DriverGrabber to help admins perform these tasks much simpler. ;)

I am very pleased with DriverGrabber. It has proven to be a very useful tool.

The biggest thing I want to figure out is how to make it backup drivers of hardware that is not currently in use... like Printers/Scanners and so on. So that when a tech has the computer brought into their shop they can backup all needed drivers... even the ones that are not in use. But that task may not be a simple as it sounds.

I didn't realize I allowed multiple instances of the tool to run. Thanks for pointing that out.

I don't think I'll check if a file allready exists though... because I'd rather it just overwrite files. If I check each file then I would have a prompt pop up too often... and I hate Driver Backup programs that do that.

[Overkill]

Yay! I'm useful! :P

As far as my check each file suggestion...let me clarify with an example:

1) DG compares files A1, B1...Z1 with A2, B2...Z2
2) If A-Z #1 match A-Z #2, user is asked "Files exist and are a match, overwrite anyway?" Yes/No + Always use this answer
--If yes, DG deletes ALL existing files, thus removing any "orphan" files, then copies the new ones
3) If A-Y #1 match A-Y #2, but Z1 != Z2, or if A-Z #1 != A-Z #2, then user is prompted with "Files exist, but do not match. What do you want to do?" Overwrite/Keep/Save to new folder + always use this answer
--If overwrite, DG acts the same as yes in step 2

*Also, another thought...if I've got a driver backup CD, and I want to do a manual install...I don't want to have the subcategories...just device names. I'm not going to have a hard drive called "ATI Radeon All-In-Wonder x1900" :P

Ideally, it'd be:
\Drivers\Mynetwork\Biohazard\leethardwarezorz!!!11 one1! for my house and
\Drivers\GodIHateWorkingHere\butitsgoodmoney\lameh ardwareatleetprices for work :)

--> forgive my "humor", i'm bored :)

[rootw0rm]

I'm trying to run this on Vista Ultimate 64 (sjg member of admin, UAC is off) by keep getting the following message. Dev.exe appears to be a 32 bit file from 2002....



---------------------------
cmd.exe - Machine Type Mismatch
---------------------------
The image file C:\Users\sjg\AppData\Local\Temp\DGBR\dev.exe is valid, but is for a machine type other than the current machine.
---------------------------
OK
---------------------------

i get the same error on XP64 R2. here's my log:


;- Log Started 07/27/2007 - 23:39:22
;- WIN_XP Service Pack 2 X64 System Found.
;- Computer name is: TURBO64
;- X64 Devcon being used.

[Logged Errors]

[Grabbed Drivers]

[Skipped Drivers]

[seranor]

Thank you very much for this tiny cool tool. I've been searching a long time for a tool that enables me to save my drivers for an installed machine in only one step. You did it, thank you.

One thing i see is that chipset drivers (on my machine with nforce2 it is the nvnetbus) not included. This may leads to a problem on a new installation because you'll need the chipset drivers to be installed first.

Regards

Seranor

[kd6aaj]

Thanks for the wonderful program.

kd6aaj

[Siginet]

Your welcome. :) I will do further development on it when I get some time.

[ENU_user]

im getting all the chipsets integrated ,Raid ,Ethernet adapter and sound (digital audio) drivers
but the graphics port driver.
as for the display card ,a detection added to this as well can be great.

cheers

[semiono]

Thanks!
Where is a some tool to grab directly into a distribution of nvidia and any drivers packages? :rolleyes:

Howto I can rebuild the 169.21_forceware_winxp_64bit_english_whql.exe
if I sit now on XP 32bit before? :\

Need rebuild *.inf and remove shared content differently of GeForce6600
Need It be lite!
:cool:

******
Ok! I try firstly install XP64 and grab it after...
Sorry for lame english )

[alphagg]

my computer has 2 windows xp os on it and sadly drivergrabber will not back up any drivers on my system any suggestions

[Siginet]

Probably no third party drivers are installed. All of the drivers on the system must be microsoft drivers... or your drivers are not installed properly?

[Kim]

I successfully started from CD by using a small batch file to copy the files to Desktop. Here's a couple of simple commands:


echo. The next line copies, and creates, the -drivers- folder on Desktop
xcopy "%cdrom%\MyDriver\Portable" "%userprofile%\Desktop\-DRIVERS-" /h /I /k /q /y >NUL
echo. The next line runs the program
CALL "%userprofile%\Desktop\-Drivers-\DriverGrabber.exe"
echo. the next line removes all files except the found drivers
DEL "%userprofile%\Desktop\-Drivers-\*.*" /Q /f

Actually there are a lot more commads in the batch file, like wait, and title, and these type of echos ÜÛß that put borders around echoed name

Just wondering if anyone successfully worked out an easier way to run it from CD
Actually ideally I wish the program could just do it itself, but it doesn't.

I'm very happy with it, it beats all the others (that require installs)
So thanks for an excellent tiny program
Any updates, is the programmer still alive?

Edit:

Actually Siginet is ofcourse, I suppose my question is really, any updates forthcoming ?
And is my little batch file ok, or not?

[Siginet]

Nice batch. :) Yes I plan on updating in the future. Just been busy on the rvm integrator and studys. ;) But I have definatly not finished drivergrabber. :)

[Kim]

Thank-you for the reply.

As mentioned, I like the standalone and %cdrom% access; and also the simplicity and smallness of the program.

I for one have used it many times, it definately surpasses or other larger programs out there. I have also used it on many different systems without fault, over the years.

I have attached my entire folder, that can be used to burn directly to CD or DVD
If this attachment (zip format) causes any legal issue, or you do not wish others to use the tool in such a way, please remove it. It's just that it took me 3 Hrs to get it looking right (even though it's simple batch)

I'll check back from time to time for any updates.

Thanks again

[ENU_user]

siginet i was thinking maybe you can make predefined folder names mainly for raid drivers so its easier to find for Automation
you can also enumerate the folders by their significants so the setup finds the important ones faster ....

00_Raid
01_chipset
02_display

but mainly for RAID as it is needed for some SATA %HOMEDRIVE% the others can use Method 2 ;)

[seranor]

As rootw0rm formerly said, DriverGrabber doesn't work in XP64, the error message is exactly the same.

When will this be fixed?

Want to give Vista x64 a chance, but not without backing up my xp64 drivers before ;-)

Right at the moment I found the correct devcon.exe (the shipped one is for IA64 only and NOT for AMD64!).

It is part of the DDK (Device Driver Kit) and can be downloaded from here: http://download.microsoft.com/download/9/0/f/90f019ac-8243-48d3-91cf-81fc4093ecfd/1830_usa_ddk.iso
It resides under /tools/devcon/amd64.

So only further action is to replace the old devcon.exe with the one within this DKK (amd64\devcon.exe) or in addition to the exisiting devcon.exe and rebuild it, should work then :-)

Regards

Seranor

[Kim]

That file (ISO) is 236Meg !


So only further action is to replace the old devcon.exe with the one within this DKK

Can't we just get the latest devcon.exe posted.? How big is that one?

From 1st Post:

3. DriverGrabber will now detect if the system is x86 or x64 and use the correct devcon.exe needed for the system. So it should work fine with x64.
.
So is this working or not?

[seranor]

Can't we just get the latest devcon.exe posted.? How big is that one?


I uploaded it here (http://www.fileden.com/files/2007/3/29/936366/devcon.png)

Just download and rename it then to an executable.


So is this working or not?

Initial it will work only for x86 and IA64 systems with the current used devcon.exe within DriverGrabber. The author of DriverGrabber has to add the new one for support of amd64 systems.

Seranor

Carpe Noctem! :)

[Afgan]

Hi, just to let you know that the new version of driver grabber errors on my vista 64 bit system and wont run at all.
Error message is: "The image file C:\users\user\appdata\local\temp\DGBR\Dev.exe is valid, but is for a machine type other than the current machine"
can you please shed some light on this problem for me.;)

[Siginet]

Yeah it is a known issue. I just haven't had a chance to work on drivergrabber in a long time.

Hopefully I will have time to work on it in the near future.

If you know anyone who wants to help develope the program please have them contact me. :)

[seranor]

I also have not that much time to spend many hours into a development, but if you wish I'll try to help to at last this bug.

Regards

Seranor

[impact1600]

hello i'm a newbie i couldn't figure out how this forum thing works any tips would be appreciated,

COULD someone help, I've been trying to make a WINDOWS MEDIA FORMAT RUNTIME 11 add-on but have been unsuccessful, also tried doing a google search for one but i keep getting WINDOWS MEDIA PLAYER 11 hits, also is there anyway to add registry key entries as an add-on that way my programs could be preconfigured before install. if anyone who would care to take the time you could email me at joshdum@yahoo.com. thanks

[groovydad]

Just to say thank you for this neat tool. I'm definitely a newbie and even I was unable to mess it up.

[Siginet]

Your very welcome. :) Enjoy!

[commander_keen]

Works pretty good, but seems to miss some drivers?

This is what it finds concerning graphics and chipset:

http://img20.imageshack.us/img20/6061/driverbackuperror.png


DriverBackup on the other hands lists several more drivers for the nForce2 chipset:

http://img5.imageshack.us/img5/6061/driverbackuperror.png

But that software has an error which makes it not even complete it's task, no matter what driver I want to backup.
My hope is now DriverGrabber can be tweaked a bit to get the missing drivers because it at least works :-)

[Siginet]

I do want to update drivergrabber in the future. It is a simple program I created a long time ago that deserves an upgrade. When I get some time in the future I will update it. ;) Or if someone is interested in helping develope it please let me know. ;)

[YodaDaCoda]

I do want to update drivergrabber in the future. It is a simple program I created a long time ago that deserves an upgrade. When I get some time in the future I will update it. ;) Or if someone is interested in helping develope it please let me know. ;)

Seranor uploaded the AMD64 version of the devcon.exe. Perhaps you could simply replace the version that is currently in your program and release as a new version for those of us running AMD64 architecture? I for one am very keen to try this app - sounds like it's going to save me hours or driver problems in the future.


I uploaded it here

fileden (dot) com/files/2007/3/29/936366/devcon.png

Just download and rename it then to an executable.

(url shown in plaintext due to me not having 3+ posts)

[YodaDaCoda]

@Siginet: Depending on the language and whether or not the IDE is avaliable, I could give a shot at some development.

[Kim]

Still waiting :(

The DriverGrabber still works though, but it would be nice to upgrade it, especially with Win7 being released
Anyway, If this project is dead, I'd just like to say that DriverGrabber was the best in the world (at one stage) I'd say I've used it a thousand times.

Well done for such an excellent (very) small program, created a long time ago
It could still be the best in the world again, with a little more support.
Its all up to Siginet :)

[Siginet]

Thanks Kim. I really appreciate that. I do want to continue development. I'd like to someday have it scan the registry to gather all of the needed driver info instead of using devcon. I hads messed around with the idea a long time ago and was having a lot of advances. But then my home life had gotten so busy. All of my programs have been neglected latley. :(

I need to find my src code. I have had a lot of bad luck with computers latley. lol

Had a HD Crash recently. A nasty virus in one of my computers. A MB crash on my main computer. I have moved so many harddrives around and disconneccted some hds I'm not sure which is which anymore. when I find the source code I'll get going on it and gladdly have YodaDaCoda help or any others if they are interested.

[Chumbo]

Is this tool supposed to work under Windows 7 64bit editions? Thank you.

I tried it in Windows 7 Ultimate 64bit and it comes up with the following error: "The image file %temp%\SYSTEM\DGBR\dev.exe is valid, but is for a machine type other than the current machine." The message is in a dialog with an OK button which when clicked closes the app.

I put in "%temp%" but in the dialog it actually shows the temp path.

[YodaDaCoda]

This app does not work properly on x64 machines. Instructions to make it work below.

1. Download the x64 devcon.exe from the link below. It has been uploaded to an image sharing server, so you will need to change the extension from .png to .exe, also rename it from devcon to dev.

fileden.com/files/2007/3/29/936366/devcon.png


1. Download and run the app, let it fail. Take note of the location of the file that fails.

3. Open the location it tells you of the app that fails and replace the dev.exe there with the one you downloaded.

4. Set the properties of the dev.exe to read-only. This will prevent the program from overwriting your dev.exe (which works) with its dev.exe (which won't work).
To set it to read-only, right click > properties > check the 'read only' box.

5. Run the program. :)

[fah_q_2007]

What operating systems is this compatible with?

[mr_smartepants]

It was designed for use on nt5-based systems (XP, 2003 server, etc) but it's been reported to work with Vista. Your mileage may vary.

[user_hidden]

i have used this utility on XP many times and it is an awesome tool.
cannot give any other OS input on its useage.