Jump to content











Photo
* * * * * 1 votes

DriverGrabber 2.0 - One Click Driver Backup!!

now works in winpe!!!

  • Please log in to reply
42 replies to this topic

#26 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 14 June 2012 - 11:39 PM

Glad to hear it was successful! I hope to hear many more successful tests by other members as well! I really think this is turning out to be a vital tool. It will go great with my PC Data backup utility I am working on as well. :)

#27 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 18 June 2012 - 06:34 PM

Updated!

Beta 5:
Fixed - A few bugs in the code causing DriverGrabber to fail finding the correct path to grab some driver files.
Changed - DriverSearch is now set to Off by default. If anyone has issues with backups I suggest they try to turn DriveSearch on and then post their log on the forum so I can make sure their drivers are properly backed up in a future release of DriverGrabber. We are still in Beta... and I'd like to have DriverGrabber functioning as well as I can without the need for DriveSearch.

#28 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 09 July 2012 - 05:33 PM

Beta 6 is online now as well!
I will also be releasing my Data Backup utility (With Drivers backup) soon as well. Just a few more changes and it will be ready for a public release.
It's a great Utility for backing up needed Data from a computer before reinstalling the system and works in both a live system and a Preinstallation Environment like BartPE or LiveXP.
  • wimb likes this

#29 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 09 July 2012 - 06:57 PM

Beta 7 Online!!!
  • wimb likes this

#30 Atari800XL

Atari800XL

    Member

  • Members
  • 71 posts
  •  
    Netherlands

Posted 09 July 2012 - 07:25 PM

Thanks for the new versions. Looking forward to the Data Backup tool as well...

#31 saddlejib

saddlejib

    Frequent Member

  • Advanced user
  • 270 posts
  •  
    United Kingdom

Posted 10 July 2012 - 11:38 PM

Latest version does'nt appear to work for me, deleted zip Beta5 and expanded folder plus grabbed drivers from 5 (which had worked) and tried new version got only one set of drivers. Which was "H:DriverGrabber 2.0Drivers?Win7SystemATK0110 ACPI UTILITY. Have I missed something?

#32 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 11 July 2012 - 05:42 AM

Can you post your log and any oem*.inf files that may be failing? Not sure what the ? in your path is from?

#33 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4131 posts

Posted 11 July 2012 - 07:25 AM

A would go with a gui.

#34 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 11 July 2012 - 04:31 PM

I plan to add a GUI option in the future. But it's mainly meant to be a one click backup solution. Which would have no need for a GUI. Although it shouldn't be too difficult for me to allow an option in the DriverGrabber.ini to enable a GUI.

#35 ericgl

ericgl

    Frequent Member

  • Expert
  • 314 posts
  •  
    Israel

Posted 11 July 2012 - 08:47 PM

Yep, I also support the idea of a GUI with a big BACKUP MY DRIVERS button and (optional) path to where the app should look for them.

#36 smallhagrid

smallhagrid

    Newbie

  • Members
  • 27 posts
  • Location:Vermont
  • Interests:Everything ?
  •  
    United States

Posted 14 July 2012 - 09:43 PM

The download at:
http://integrator.si...p?addons&id=242


Failed for me - tried it 3 times and could not get the file...

#37 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 15 July 2012 - 08:53 PM

Not sure why it is not working for you. It is working.

But here is another link:
http://professorcpu....Grabber 2.0.zip

#38 smallhagrid

smallhagrid

    Newbie

  • Members
  • 27 posts
  • Location:Vermont
  • Interests:Everything ?
  •  
    United States

Posted 17 July 2012 - 06:22 PM

Thanks, same result:

Not sure why it is not working for you. It is working.
But here is another link:
http://professorcpu....Grabber 2.0.zip

Apparently it is NOD32's fault for objecting to the file-type:
Posted Image
I paused NOD32, and got it OK, but when un-paused the message above comes on and blocks file access.
BooHoo.

#39 smallhagrid

smallhagrid

    Newbie

  • Members
  • 27 posts
  • Location:Vermont
  • Interests:Everything ?
  •  
    United States

Posted 17 July 2012 - 06:23 PM

Thanks, same result:

Not sure why it is not working for you. It is working.
But here is another link:
http://professorcpu....Grabber 2.0.zip

Apparently it is NOD32's fault for objecting to the file-type:
Posted Image
I paused NOD32, and got it OK, but when un-paused the message above comes on and blocks file access.
BooHoo.

#40 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 18 July 2012 - 05:07 AM

Yeah... I really like nod32... but I won't buy it because it tends to flag anything written in autoit. I think it is lazy on antivirus makers to flag anything just because of the language it's written in. :( If you don't mind... you can contace eset on my behalf and request that they not flag DriverGrabber.

Thanks,
Glad you figured out the issue with downloading it.

#41 cammn

cammn
  • Members
  • 4 posts
  •  
    United States

Posted 01 August 2012 - 05:12 PM

Siginet, Great work and glad to see this done in AutoIt. As a sys admin, I've learned to love the language.

You are real close to something I've wanted for awhile. The ability to load the host network drivers if PE doesn't have them. There are 3rd party drivers, and wireless drivers not available in PE.

Here's the scenario i crave.
-Boot to PE (I have a custom build for my environment)
-Check for network cards
-If no network card found LOCATE DRIVER from host system (DriverGrabber)
-Load new driver
-If successful, launch a remote support session (I'm using LogMeIn but could be a UltraVNC one-click session)
-This allows remote support for crashed systems and I could just add the PE to the Windows F8 boot menu to load the PE image I've built.

The fact you have PE support is wonderful. I would already know the SOURCE Windows folder of the host (C:\ or D:\ if there's a system reserve partition) but I need to pass that to DriverGrabber. Maybe another parameter stating that I only want to back up "Network Adapters" even if it is a Microsoft driver, there isn't much for wireless drivers in PE.

So, what would it take to add a couple more parameters to the .INI file?
SOURCE=D:\Windows
DriverType="Network Adapters"

Again, thank you for your support in the community.

#42 Siginet

Siginet

    Frequent Member

  • .script developer
  • 154 posts
  •  
    United States

Posted 26 August 2012 - 10:41 PM

Siginet, Great work and glad to see this done in AutoIt. As a sys admin, I've learned to love the language.

You are real close to something I've wanted for awhile. The ability to load the host network drivers if PE doesn't have them. There are 3rd party drivers, and wireless drivers not available in PE.

Here's the scenario i crave.
-Boot to PE (I have a custom build for my environment)
-Check for network cards
-If no network card found LOCATE DRIVER from host system (DriverGrabber)
-Load new driver
-If successful, launch a remote support session (I'm using LogMeIn but could be a UltraVNC one-click session)
-This allows remote support for crashed systems and I could just add the PE to the Windows F8 boot menu to load the PE image I've built.

The fact you have PE support is wonderful. I would already know the SOURCE Windows folder of the host (C: or D: if there's a system reserve partition) but I need to pass that to DriverGrabber. Maybe another parameter stating that I only want to back up "Network Adapters" even if it is a Microsoft driver, there isn't much for wireless drivers in PE.

So, what would it take to add a couple more parameters to the .INI file?
SOURCE=D:Windows
DriverType="Network Adapters"

Again, thank you for your support in the community.

Glad you like it. :) I will be adding many new options for the DriverGrabber.ini as well as command line switches in the near future. ;)

#43 wazer

wazer
  • Members
  • 1 posts
  •  
    Denmark

Posted 19 August 2014 - 05:58 PM

Glad you like it. :) I will be adding many new options for the DriverGrabber.ini as well as command line switches in the near future. ;)

 

Are you still updating this?

 

Is it possible to save the respective driver/files in the subs where they belong instead of grabbing all drivers/files in root for the respective driver folder name?

 

When using WinToolkit it will complain about missing drivers when trying to intergrate drivers to the windows iso because it's looking for subs strings, i then have to search manually for those files in windows and look what sub folders they are in and then create and add files there before it will accept them.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users