* Add sensor 1 back for NVMe.
Adjust name of standard temperature sensor for NVMe.
* Update LibreHardwareMonitorLib/Hardware/Storage/StorageDevice.cs
* Update LibreHardwareMonitorLib/Hardware/Storage/StorageDevice.cs
* Update StorageDevice.cs
---------
Co-authored-by: PhyxionNL <7643972+PhyxionNL@users.noreply.github.com>
- add temperature sensors for high/low/critical limits
- change thermal sensor index to 0
- adjust sensor indices accordingly
Storage:
- add Free Space sensor
- add Total Space sensor
- change temperature sensors indices to start from 0
- remove temperature sensor 1 as the non numbered sensor is the same
* Replace Storage implementation with CrystalDiskInfo based implementation.
* Formatting.
* Code review.
* Code review.
* Increase space for attribute name in report.
* Implement dynamic disk handling for usage sensor.
Disable unused warnings.
* Further cleanup in NativeMethods.txt and referenced.
* Minor refactoring for #1699
* Implemented storage update interval for the UI
* Revert "Implemented storage update interval for the UI"
This reverts commit 977ff2f5518d420e35cadad17054f4e69c260df1.
* Revert "Minor refactoring for #1699"
This reverts commit 923f6d6f636a2a10ff44b8c23f84e8985ccbf667.
* Made update interval configurable for storage devices
* Changed label text m to min for consistency
* Revised 8e6c669 as requested
* ATA Update interval defaults to 1s in the UI
* Simplified storage update interval menu
WMI queries do not have a timeout by default and can subsequently hang.
This commit adds timeouts to avoid these hangs.
On timeout, `Get` will throw a `ManagementException` that has an error
code of `ManagementStatus.Timedout`. In the case of abstract storage,
this exception will be silently swallowed and the statistics from WMI
not updated until the next update interval, which seems appropriate.
The storage group, on the other hand, a timeout there would cause an
initialization exception which would be propagated up to the caller
(which seems ok as something must be terribly wrong for that WMI query
to fail).
The code was also updated to call dispose for all the WMI objects. I
don't see this causing a behavior difference, but I found it better to
be safe than sorry.
The timeouts were chosen to be a compromise between returning in a
reasonable timeframe and allowing WMI, which can be terribly slow, to
return the query.
There is no entry for `CopyMemory` exported from kernel32.dll as it is
omitted from the following output:
```
dumpbin /exports C:\Windows\System32\kernel32.dll
```
The name we're looking for is `RtlCopyMemory`. This does not affect
traditional .NET framework users as `CopyMemory` was special cased prior
to .NET core
([source](https://github.com/dotnet/runtime/issues/12496#issuecomment-483442084))
The incorrect entry point will cause an `EntryPointNotFoundException`
for NET core users (ref:
https://github.com/nickbabcock/OhmGraphite/issues/214)
There were a couple other entries in kernel32 that are missing:
- CreateFile
- LoadLibrary
Both functions appear to have a `CreateFileA` and `LoadLibraryA`
variant, but I do not know if those are appropriate.
push-0x57df