search

xuantl / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Tray icon(s) missing in Windows 7 when logging on too early #269

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Windows 7 Pro x64

When I logon as fast as possible after bootup, the OHM Window appears, but not 
the tray icon and the configured other icons with sensor values.

When I minimize the OHM Main Window, there is no way to access it again.

Btw., Speedfan has exactly the same issue. Both processes are shown in the 
process monitor under the task scheduler from where I can kill and restart them.

It seems this happens when the tasks are started while the desktop is not yet 
visible (I can hear that because Speedfan shortly sets the fan to 100%). If I 
wait long enough before logon, the desktop appears much faster and the 
scheduled tasks start after it is visible and correctly register their icons...

Original issue reported on code.google.com by moritz.f...@gmail.com on 30 Aug 2011 at 9:07

GoogleCodeExporter commented 9 years ago 
I can reproduce this on another machine (fast hardware with SATA3 SSD). Not 
sure how this is best fixed.

Original comment by moel.mich on 15 Jan 2012 at 9:56

GoogleCodeExporter commented 9 years ago 
I start OHM using Task Scheduler and give it a 15 or 30 second delay after user 
logon (depending on machine speed, SSD, etc.).  I suggest creating the tray 
icons after a short delay.

Original comment by steve.hoek on 28 Jan 2012 at 12:23

GoogleCodeExporter commented 9 years ago 
Looks like issue 253:

1. When auto-startup on WinXP startup, sometimes not all values are shown.
I must do a "reset", then all values are o.K.

I think, a little delay on startup can fix it.
For example, is there an option in seconds possible to auto-startup the monitor?

Original comment by microsof...@freenet.de on 2 Feb 2012 at 12:04

GoogleCodeExporter commented 9 years ago 
Used suggestion (comment 2) and give a delay of 15 seconds after logon. OHM now 
works correctly every time logged on.

On WinXP used task scheduler and a little script for delay, because WinXP task 
scheduler allows only minute-steps.

Because I have a SSD (Crucial M4, AHCI-mode), I think OHM is to quick and the 
board / sensors are not ready so fast.

Btw: the SSD reports nothing (only listed). Its a Crucial M4-64GB.

Original comment by microsof...@freenet.de on 19 Feb 2012 at 9:42

GoogleCodeExporter commented 9 years ago 
I have create an alpha version that should fix the problem:

http://openhardwaremonitor.org/files/openhardwaremonitor-v0.4.0.15-alpha.zip

Unfortunately I do no longer have access to a machine where I could reproduce 
the problem myself, so I wait for your feedback.

Btw. also Crucial M4-64GB SSDs should be recognized correctly now.

Original comment by moel.mich on 10 Jul 2012 at 7:38

GoogleCodeExporter commented 9 years ago 
Thanks, I'll testing it and report.

Original comment by microsof...@freenet.de on 11 Jul 2012 at 6:44

GoogleCodeExporter commented 9 years ago 
what test results did you get?

Original comment by moel.mich on 13 Jul 2012 at 10:14

GoogleCodeExporter commented 9 years ago 
The described error no longer occurred in the past three days.
Starts now correctly every logon (about round 20 times).

But its a very short test-time ;-)
The descibed error occurred in the past not every logon.

Crucial M4 reported "Remaining Life = 99%"

Original comment by microsof...@freenet.de on 14 Jul 2012 at 8:07

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r401.

Original comment by moel.mich on 14 Jul 2012 at 7:24

GoogleCodeExporter commented 9 years ago 
Thank you very much for your test. The current implementation now tries to 
create the tray icon for about 8s until it gives up. The original 
implementation never even checked if creating the tray icon failed.

Original comment by moel.mich on 14 Jul 2012 at 7:27

GoogleCodeExporter commented 9 years ago 
Well done, good work - but please look at issue 253 - it's comming back...

Original comment by microsof...@freenet.de on 17 Jul 2012 at 8:21