Open GoogleCodeExporter opened 9 years ago
I run OHM and Speedfan concurrently without any problem.
(WinXP Pro (both 32 and 64 bit versions). This has been the case with several
different Gigabyte and MSI AM3 motherboards)
I have access to all data, features, reporting, graphing, alarms (supported
only on Speedfan), etc the same as when I run either program by itself.
The reported data when running simultaneously also remain SELF-consistent with
the data each reports when each program is running by itself (in other words,
OHM running while Speedfan is running, reports the same data values OHM does
when Speedfan is not running)
Original comment by transgen...@gmail.com
on 12 Sep 2011 at 5:56
I guess I can't edit my prior comment...
I'm currently running
OHM 0.3.2beta
Speedfan 4.44
Original comment by transgen...@gmail.com
on 12 Sep 2011 at 5:59
Yes, Speedfan and the Open Hardware Monitor can both run at the same time
without problems. The problem here is, that the serial port interface of the
T-Balancer can be accessed only from one software at a time. At the moment you
would have to start Speedfan, then the T-Balancer software and the Open
Hardware Monitor last. In this case the Open Hardware Monitor would just not
monitor the T-Balancer (as its already in use by another software), but beside
that you could read everything on the Open Hardware Monitor.
Of course it would be better to reimplement the software fan control for the
T-Balancer directly in the Open Hardware Monitor. In that case you could drop
Speedfan and the T-Balancer software.
Original comment by moel.mich
on 13 Sep 2011 at 8:43
Thank you for the reply. That does indeed sound like heaven to have the one
tidy app for all.
I have now managed to implement this and run all three to monitor temps with
OHM.
I did have some trouble before though. It was interrupting communication
between speedfan and Tban somehow and fan speeds were increasing etc.
It seems ok at present.
Is the OHM only build for BigNG something you have in the pipeline?
Original comment by DGHPlumb...@gmail.com
on 6 Oct 2011 at 7:16
Original issue reported on code.google.com by
DGHPlumb...@gmail.com
on 16 Aug 2011 at 7:31