I think I kind of figured it out. The sendmessage idea works when the window itself puts the monitor to sleep because the Power Options haven't engaged. Once the Power Options engage (in your case after 1 minute) XP requires an actual mouse or keyboard event to wake it up. I don't think that's exactly right - it's more like we can still wake the monitor up with sendmessage but the Power Options immediately put the monitor to sleep again because there hasn't been any keyboard or mouse input. I did some testing with the sendmessage.exe and that appears to be what's happening. It happens fast enough that you typically won't see the monitor start to wake up before it goes back to sleep.
There are windows API's that cause "real" keyboard/mouse events and they will trigger the Power Options to wake the monitor. I wrote a little exe that moves the mouse 1 pixel right and then 1 pixel left that seems to work fine.
EDIT:
http://home.comcast.net/~twhite644/spid ... seMove.exe Just call the exe with OS\Execute, no parameters, select the "Server Event" checkbox so it executes on the server.
I don't think my exe will really solve your problem though, the monitor will go back to sleep 1 minute later regardless of what you do on you PPC. The problem goes back to Xlobby's mimic functionality. Steven, is performing the mimic entirely in Xlobby which makes perfect sense (ie you click a button on the PPC, it has a Xlobby based id, Steven passes this back to the Xlobby Server instance and executes the events associated with the button id on the server). But because of this the server OS never encounters the actual keyboard inputs (like Enter, or LeftClick) when you click on a button on the PPC.
So I think the only real answer would be for Steven to provide an option with Mimic that sends the appropriate OS calls for keyboard input.
tsw