Windows Deployment

Program update: drvbckp 0.3

by on Jan.17, 2010, under Uncategorized

About the program: drvbckp is a CLI driver backup tool
Drvbckp is a small .NET 3.5 tool used to backup drivers from a windows computer. It is intended to be used either as a standalone tool or inside scripts to automate driver backup. It can include or exclude Microsoft drivers as they in most situations already are included with the OS.

New version, lots of bugfixes!

SVN log follows:
[ADDED] Escaping of regular expressions to avoid errors
[FIXED] RegExp now picks up the architecture endings on install section
[FIXED] File-specific sourcefolders are now created
[ADDED] If a file isnt found the whole sysdrive will now be searched (as a last resort)
[FIXED] Files with different sourcenames are now saved with the correct names

drvbckp-0.3

If you find it useful, please donate!






1 Comment for this entry

  • Daniel P

    Hi,
    I love your utility, I’ve bee experimenting with other ones, but they are all gui driven and I do prefer CLI.
    For the most part all my drivers where supposedely extracted correctly. But when I try to add these to a new identical system, 2 drivers had slight u=issues with there file structure.
    Basically the drivers in the win7 driverstore use a subdirectory called x86 and amd64, your utility correctly copied these diretories but they were empty, and the files that should have been in these directories where in directory above this.
    Here are the files that were backuped by your utility for this offending device (Validity sensor)

    oem11.inf
    vfs471.cat
    WdfCoInstaller01007.dll
    WinUsbCoinstaller.dll
    and 2 directories X86 and AMD64

    The error is that the 2 files
    WdfCoInstaller01007.dll
    WinUsbCoinstaller.dll
    should have been placed under the x86 directory.
    This is the way the oem11.INF expects it.

    SO this driver will NOT work as is, until the 2 files are moved under the x86

    I had another identical issue with another driver.

    I also know hat there are several drivers that use this type of subdiretory to styore their files.

    It would be really nice if you could fix this.

    Let me know if you need any more info.

    Thanks again for a great utility.

    PS: it wouls also be nice if the INF file could be renamed to their original names rather than just oemxx.inf

    Daniel

247 Trackbacks / Pingbacks for this entry

Leave a Reply

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

Archives

All entries, chronologically...