Only once, to install the persistent driver. From then on it runs nicely in user mode.
Here is a screenshot with open HWiNFO.Martin said:According to the screenshot it looks like HWiNFO is not running. The only tool that was found is OpenHardwareMonitor.
Delayed response I know, but I would love to get more information into a backend and visualization tool I've been packaging. I've tried using collectd's JSON plugin but I'm not quite skilled enough in this area to adapt it to the formatting output by the Remote Sensor Monitor web server.Michael Z Freeman said:Looks useful I can probably pull info from the json using CLI in Linux. But does anyone know of a Linux tool/app to display the info graphically ?
"Remote Sensor Monitor.sys" is not part of this package and anything else related to HWiNFO. So you will need to check elsewhere.PaulBags said:Hi, how to remove "Remote Sensor Monitor.sys" injected into process 'System' and why isn't it unloaded when the program exits?
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://machine_local_ip:55555/. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
I wish to introduce Remote Sensor Monitor (a small freeware Windows console application (requires .NET 4.0) that I have been developing over the last week or so) for your feedback / bug reports.
1. Added support for AIDA64 sensor / data reporting
2. Removed external DLL dependency for GPU-Z shared memory access
1. Fixed bug related to certain sensors being reported multiple times in Hyper-V enabled machines
1. Initial public release
Remote Sensor Monitor 220.127.116.11
Copyright (C) 2013 Ganesh T S
Remote Sensor Monitor is a Windows console application designed to present various hardware sensor parameters reported by HWiNFO / GPU-Z / AIDA64 / Open Hardware Monitor as a JSON string and make it available over the network. Enabling GPU-Z, HWiNFO and AIDA64 requires the programs to be running the background. The minimum supported versions are: GPU-Z: 0.7.4, HWiNFO: 4.30, AIDA64: 4.00.2706. Open Hardware Monitor sensors can be reported only if OpenHardwareMonitorLib.dll is present in the same folder as that of the application. Once the web server starts up, the JSON string is available at http://<IP>:<PORT> ; The reported parameters can be filtered / configured via the web interface at http://<IP>:<PORT>/config ; The program requires administrative privileges in order to open and close the applicable port in the firewall when necessary.
Command Line Options:
p, port : (Default: 55555) Port number to use
hwinfo : (Default: 1) Enable (1) / Disable (0) sending out sensor readings from HWiNFO
gpuz : (Default: 1) Enable (1) / Disable (0) sending out sensor readings from GPU-Z
aida64 : (Default: 1) Enable (1) / Disable (0) sending out sensor readings from AIDA64
ohm : (Default: 1) Enable (1) / Disable (0) sending out sensor readings from OpenHardwareMonitor
h, help : Display the help screen.
"Remote Sensor Monitor.exe" [-p=<port_number>] [--hwinfo=<0|1>] [--gpuz=<0|1>] [--aida64=<0|1>] [--ohm=<0|1>]
With the JSON output, it is easy to develop client applications for various purposes. For example, the script hosted here: https://code.google.com/p/sensor-mo...rowse/trunk/RemoteSensorMonitor_Client_CLI.pl : can be used to record various sensor parameters of a remote machine on which this program is running into a CSV file.
The code itself is based heavily on SensorMonHTTP, a open source GPU-Z / sizegenetics-reviewOpen Hardware Monitor C# .NET application that I had developed earlier. It is hosted here: http://code.google.com/p/sensor-mon-http/source/browse/trunk/SensorMonHTTP ; I have added HWiNFO support, thanks to the shared memory details provided by Martin. I would have loved to open source this effort too, but Martin prefers that the shared memory specifications remain private. Therefore, this fork of SensorMonHTTP will have to remain closed-source.
Edit: It would be great is someone could contribute an icon / display graphic for the program.
Hi Is anybody using this tool?
I find that the program will randomly stop and there is no way to know the state of the program.