2 mitchjs:
two logs are in attached file. carmess.log is created on CarPC based on intel GLY motherboard. UsualPC_Messages.log is created on my notebook. There are some my comments in log files.
carmess.log has many mouse events. I think it is because of touch screen drivers.
You'll see strange messages (wm_user+10) on the log such as:
"message:0x040A [User-defined:WM_USER+10] wParam:00000011 lParam:00000006"
These messages i sent to RR to define time of the incoming messages. wParam is system minutes and lParam is system seconds.
Windows on intel GLY motherboard sends WM_POWERBROADCAST only after user moved mouse, pressed any key, or did any other user event.
Other PCs sends WM_POWERBROADCAST immediatelly after PC was ready to work.
This is not i bug of RR. I think, it is because of bad (via?) drivers...
My CarPC hybernates itself as Stealth915's one.
Quote:
I did a quick test today and can confirm that the computer hibernates by itself after about 5 minutes if I don't touch the screen while it is hanging
It occurs regardless of RR presence in memory. More precisely, PC is not hangs. It doesn't sleep, but it doesn't wake up fully. Winamp can play music on my PC on such conditions. As i understend, RR waits for WM_POWERBROADCAST so it doesn't repaint itself.
Two month ago i wrote a small program. It had to mute sound before hybernate and unmute it after waking up (i wanted to remove loud BUH from speakers). Program worked normally on home PC, but didn't work on CarPC. I added messages logging and did recognize strange behaviour of windows.
ps. sorry for my bad english.
Linear Mode
