Backup throws error because of deleted driver file

[GoogleCodeExporter]

Hi,

we are having the issue that our backup program "BackupExec" throws an error, 
that it skipped a driver file.

During our research we found that the driver file created by 
openhardwaremonitor-lib is missing. As the driver is still registered, but the 
file is deleted, the backup program throws an error.

Why do you delete the driver file after opening the driver?
http://code.google.com/p/open-hardware-monitor/source/browse/trunk/Hardware/Ring
0.cs#187

Regards,
Kim Schneider

Original issue reported on code.google.com by kitsschn...@gmail.com on 22 Jan 2013 at 10:01

[GoogleCodeExporter]

The driver file is needed only temporary while loading the driver. Depending on 
the situation it might also get extracted to some temporary files folder. Other 
similar software like CPU-Z or CoreTemp handles things similarly (as far as I 
know).

Is there any document from Microsoft that states driver files have to remain in 
place while the drivers are still loaded? For example, a native dll can't be 
deleted while still in use. If deleting isn't against any guidelines from 
Microsoft, then this would be more of an error of BackupExec than Open Hardware 
Monitor.

Original comment by moel.mich on 27 Jan 2013 at 4:57

• Changed state: NeedsInfo

[GoogleCodeExporter]

The problem lies (probably here).

The System references in the registry to this path (and the file does not exist 
anymore).

The backup software correctly looks up for this path but no file is present.

We fixed it now by not deleting the driver, but i think this should be fixed, 
because this seems not correct to me to reference for a file that can be 
deleted.

I attached an screen to make it clear.

Original comment by worldbeh...@gmail.com on 18 Feb 2013 at 8:13

Attachments:

• registryWinRing0.png