Closed GoogleCodeExporter closed 9 years ago
As far as I know AS SSD tries to open the physical drive with share mode set to
none. That means it tries to get exclusive access to the drive. If other
software (like the Open Hardware Monitor) is accessing the drive as well this
will of course fail. The Open Hardware Monitor opens the physical drive with
share mode set so read / write, so it is prepared to share access to the drive.
The CPUID Hardware Monitor might close the handle to the drive after each
access making it less likely to have an open handle when AS SSD requests
exclusive access. But in theory it could happen there as well. I don't see any
good way to solve this. Closing the handle to a resource you still want to
access just so that other software can claim exclusive access to it doesn't
sound right to me.
I think the main issue here is that AS SSD requires exclusive access. This
might really be needed to get accurate results, that is something I do not
know. But in any case it should produce an error message that clearly says what
failed.
Original comment by moel.mich
on 30 Jun 2013 at 5:20
Original issue reported on code.google.com by
bradfor...@gmail.com
on 21 Mar 2013 at 9:48Attachments: