Reconstructing drivers from the system folders

[GoogleCodeExporter]

i want to suggest that your snappy when its start and detect drivers , 
if driver is not in drivers pack , snappy must copy it to its drivers by the 
meaning of adding it to its drivers folder 
thanks im Dr.Lecter from Kick-ass site

Original issue reported on code.google.com by MooT.Fa...@gmail.com on 19 Sep 2014 at 1:13

[GoogleCodeExporter]

sorry correction : 
if the driver is installed but not in drivers pack snappy must add it to his 
own drivers.

Original comment by MooT.Fa...@gmail.com on 19 Sep 2014 at 1:14

[GoogleCodeExporter]

It's not trivial to restore the original driver that way. There're applications 
for backing drivers up but I have no plans to implement this functionality.

In many cases it's impossible to restore the original driver anyway because it 
might be missing an installer or other files. The original driver might have 
been compatible with many versions of OS but when it's installed, it's being 
stripped so that it has only files relevant to the current OS.

You can tick the "Unknown" checkbox in the "Absent in driverpacks" panel to see 
which drivers might be missing in driverpacks. Users are advised to report that 
so SamLab will be able to include the missing driver in updated driverpacks.

Original comment by BadPointer0 on 19 Sep 2014 at 5:27

• Changed title: Reconstructing drivers from the system folders

[GoogleCodeExporter]

Expired

Original comment by BadPointer0 on 27 Jan 2015 at 8:58

• Changed state: Invalid