View Single Post
Old August 15th, 2008, 04:52 AM   #26 (permalink)
adrenaln
1 Farad - Avg. Capacity
adrenaln's CarPC Specs
 
Join Date: Apr 2008
Location: NSW, Australia
Vehicle: 2006 Ford BF XR6 Turbo
Posts: 23
adrenaln is on a distinguished road
Hi everyone,

To give you a bit more background on the issue, I was the user that did some testing and narrowed it down for Scott and the team.
I am(was, I'm not doing much at the moment...) an SOE developer and had 8 hardware types (all intel) at my disposal for testing.

I can confirm that:
1:The problem exists in XP SP1/2/3. (I dont have a pre SP1 edition to test with)
2:The problem is hardware independent. (Intel and virtual machines anyway)
3:The problem exists not only in centrafuse but any app developed in .NET using the SystemEvents.PowerModeChanged class.
4:The problem cannot be solved simply by emulating keyboard presses and mouse movements, I have tried both, it requires user interaction at a low level.

Those that dont have the problem either have a mouse/trackball of some sort or are simply not hibernating. (if you have a system that is touch screen only and does not display the symptoms, I would be interested to know)
Possible resolutions are
1: Get microsoft to acknowledge and hotfix the issue (considering 99.999% of their market are using mice, I'm not even going to bother)
2: A software solution via centrafuse (I did email a possible solution to Scott, however the solution is more a hack than a fix and I probably wouldnt like it in my production software either)
3: Build a virtual mouse driver that is installed into windows that moves the pointer 1pt to the left and then 1pt to the right every say 5 seconds. I'd do it myself, however I am no good with coding drivers. But maybe someone out there in the community is capable?

My 2c, please let me know if I can help in any way.
adrenaln is offline   Reply With Quote