MCE Standby Tool 0.9.094 on Windows 7

[Cafe.Racer]

Hi,

I think "Run on Away Mode" would do what I wanted, as well.  You know I want to run something that turns the TV and Amp on/off - I think that going into Away Mode would be when the TV and Amp should go off, and coming out of Away Mode should be when they get turned on.  Again, I only need to run a batch file for these two events.

The other possibility, I think, is I notice Monitor On and Monitor Off events in the log - could these be used for the same thing?

[hveijk]

Hello Herman! Hope all is well.

I am fine, thanks.

A little update:

I have fixed not being able to check ForceHCResetOnResume, I need feedback from you people if it still has some function under Windows 7 (it might fix the remote issue some of you are experiencing, I have one positive report so far).

I have improved the general reliability of the blanker.

MST now uses balloon tips to show serious error situations (none when everything is working fine).

The main cause of the sticking in the blanker issue seems to be the system is being kicked in standby while still handling the PBT_APMSUSPEND message.

At the next resume MST will still be handling this message while the new PBT_APMRESUMEAUTOMATIC already is being send. These two will be nested and seriously confuse MST.

Officially an application has to return from PBT_APMSUSPEND in 2 seconds max. In practice this can be longer but Windows 7 seems to be less forgiving than Vista was (or the closing of eHome takes longer under Windows 7).

I have been able to reduce the time eHome needs to close properly. This looks promising but still needs some serious testing.

If things go well I hopefully will be able to drop a new version here sometime next week.

I will add the Away mode run options. I have decided not to add new functionality to be able to fully focus on the Windows 7 compatibility but this one takes very little effort.

Michael, I still want your full log to investigate the blanker issue further. There is a fair chance your issue is caused by not fast enough closing of eHome.

Herman

[Nielson]

Hi Herman,

Here's a piece of my logfile when the Blanker error occurred:

vr 03 jul 2009 00:21:39.986 - ExecutionState: 1
vr 03 jul 2009 00:21:42.015 - ExecutionState: 0
vr 03 jul 2009 00:21:54.178 - ExecutionState: 1
vr 03 jul 2009 00:21:56.206 - ExecutionState: 0
vr 03 jul 2009 00:21:58.542 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 0
vr 03 jul 2009 00:22:09.387 - ExecutionState: 1
vr 03 jul 2009 00:22:10.401 - ExecutionState: 0
vr 03 jul 2009 00:22:12.463 - PBT_APMSUSPEND (Suspend from user interaction)
vr 03 jul 2009 00:22:12.467 - eHome is running, closing by sending terminate signal (Handle=000107DC ProcessId=00001728)
vr 03 jul 2009 00:22:15.471 - Terminate signal send, result=0
vr 03 jul 2009 00:22:31.515 - Close request timed out
vr 03 jul 2009 00:22:31.516 - Unsafe to terminate the eHome process
vr 03 jul 2009 15:51:53.866 - PBT_APMRESUMEAUTOMATIC (Resume for user interaction)
vr 03 jul 2009 15:51:53.867 - PBT_APMRESUMEAUTOMATIC done (0ms)
vr 03 jul 2009 15:51:53.868 - PBT_APMRESUMESUSPEND (Start user interaction)
vr 03 jul 2009 15:51:53.868 - Resuming userinterface
vr 03 jul 2009 15:51:53.869 - eHome ResumeStart()
vr 03 jul 2009 15:51:53.870 - Start at / Move to selected page
vr 03 jul 2009 15:52:07.462 - PBT_APMRESUMESUSPEND done (13588ms)
vr 03 jul 2009 15:52:07.941 - Delaying suspend for 1000 milliseconds.
vr 03 jul 2009 15:52:08.941 - PBT_APMSUSPEND done (55796472ms)
                              ...
vr 03 jul 2009 15:52:54.518 - AwakeState: AS_MEDIACENTER
vr 03 jul 2009 15:52:56.546 - ExecutionState: 1
vr 03 jul 2009 15:52:58.575 - ExecutionState: 0
vr 03 jul 2009 15:53:11.753 - ExecutionState: 1
vr 03 jul 2009 15:53:13.783 - ExecutionState: 0
vr 03 jul 2009 15:53:25.951 - ExecutionState: 1
vr 03 jul 2009 15:53:28.999 - ExecutionState: 0
vr 03 jul 2009 15:53:42.180 - ExecutionState: 1
vr 03 jul 2009 15:53:44.205 - ExecutionState: 0
vr 03 jul 2009 15:53:57.383 - ExecutionState: 1
vr 03 jul 2009 15:53:59.421 - ExecutionState: 0
vr 03 jul 2009 15:54:12.601 - ExecutionState: 1
vr 03 jul 2009 15:54:14.629 - ExecutionState: 0
vr 03 jul 2009 15:54:27.810 - ExecutionState: 1
vr 03 jul 2009 15:54:29.837 - ExecutionState: 0
vr 03 jul 2009 15:54:42.002 - ExecutionState: 1
vr 03 jul 2009 15:54:45.049 - ExecutionState: 0
vr 03 jul 2009 15:54:57.218 - ExecutionState: 1
vr 03 jul 2009 15:54:59.245 - ExecutionState: 0
vr 03 jul 2009 15:55:11.404 - User input detected (171851294)
vr 03 jul 2009 15:55:11.412 - ExecutionState: 1
vr 03 jul 2009 15:55:51.003 - ExecutionState: 3
vr 03 jul 2009 15:55:51.004 - SetContinuousThreadExecutionState(ES_SYSTEM_REQUIRED | ES_DISPLAY_REQUIRED)
vr 03 jul 2009 16:07:52.933 - ExecutionState: 1
vr 03 jul 2009 16:07:54.975 - ExecutionState: 3
vr 03 jul 2009 16:07:57.999 - ExecutionState: 1
vr 03 jul 2009 16:07:59.012 - ExecutionState: 3
vr 03 jul 2009 16:08:24.364 - ExecutionState: 1
vr 03 jul 2009 16:08:25.383 - ExecutionState: 3
vr 03 jul 2009 16:09:35.343 - ExecutionState: 1
vr 03 jul 2009 16:09:36.356 - ExecutionState: 3
vr 03 jul 2009 16:33:40.302 - ExecutionState: 1
vr 03 jul 2009 16:33:56.535 - AwakeState: AS_DESKTOP
vr 03 jul 2009 16:33:56.538 - SetContinuousThreadExecutionState(0)
vr 03 jul 2009 16:33:56.538 - SetThreadExecutionState(ES_SYSTEM_REQUIRED)
vr 03 jul 2009 16:33:57.539 - ExecutionState: 0
vr 03 jul 2009 16:34:24.915 - ExecutionState: 1
vr 03 jul 2009 16:34:25.932 - ExecutionState: 0
vr 03 jul 2009 16:35:16.909 - Starting frontend: MCE Standby Tool
vr 03 jul 2009 16:35:16.938 - Initialisation done

Minutes before 16.00u i woke the system with the mce remote. First used Media Center to watch some video's but when i closed the MC shell to do some webbrowsing i noticed the MST Blanker was still active because the screen turned black. Had to kill MST Blanker through taskmanager, but this make my taskbar disappear somehow. After logoff/logon all is well.

Regards,

Niels

[makryger]

Ah, it did not occur to me that something before the wake up could be causing this too.

Here is a log of some time before the event, and then an automatic resume.
The first entry is me starting the computer on my own.
Entry at 23:37:03.149 is me turning off the computer.
Entry at 07:22:31.952 is an automatic task (record)
I turned on the TV at around 07:56:18.848, there was a black screen.
I moved the mouse around, which is where the User input was detected, and the desktop restored
(I have blanker turned off for now, until this problem can be solved, otherwise it forces me to restart MST)
(There have been times where eHome did not close fast enough. That's why I increased the "delaying suspend" time to 3 s.)



                               ...
Sat 04 Jul 2009 23:34:03.170 - PBT_APMRESUMEAUTOMATIC (Resume for user interaction)
Sat 04 Jul 2009 23:34:06.431 - Executing: C:\Users\HomeTheater\tvon.cmd Flags: 07h
Sat 04 Jul 2009 23:34:06.774 - ExitCode = 0
Sat 04 Jul 2009 23:34:06.774 - PBT_APMRESUMEAUTOMATIC done (3603ms)
Sat 04 Jul 2009 23:34:06.774 - PBT_APMRESUMESUSPEND (Start user interaction)
Sat 04 Jul 2009 23:34:06.774 - Resuming userinterface
Sat 04 Jul 2009 23:34:06.774 - Executing: C:\Users\HomeTheater\tvon.cmd Flags: 07h
Sat 04 Jul 2009 23:34:06.930 - ExitCode = 0
Sat 04 Jul 2009 23:34:06.930 - eHome ResumeStart()
Sat 04 Jul 2009 23:34:06.930 - Start at / Move to selected page
Sat 04 Jul 2009 23:34:07.928 - PBT_APMRESUMESUSPEND done (1155ms)
Sat 04 Jul 2009 23:34:08.537 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 1
Sat 04 Jul 2009 23:34:09.551 - User input detected (3379855)
Sat 04 Jul 2009 23:35:03.355 - AwakeState: AS_MEDIACENTER
Sat 04 Jul 2009 23:37:03.017 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 0
Sat 04 Jul 2009 23:37:03.149 - PBT_APMSUSPEND (Suspend from user interaction)
Sat 04 Jul 2009 23:37:03.149 - eHome is running, closing by sending terminate signal (Handle=00050210 ProcessId=00000F20)
Sat 04 Jul 2009 23:37:03.299 - Terminate signal send, result=0
Sat 04 Jul 2009 23:37:03.666 - Close request successfully finished (515ms)
Sat 04 Jul 2009 23:37:03.682 - Executing: C:\Users\HomeTheater\tvoff.cmd Flags: 07h
Sat 04 Jul 2009 23:37:03.807 - ExitCode = 0
Sat 04 Jul 2009 23:37:03.807 - Delaying suspend for 3000 milliseconds.
Sat 04 Jul 2009 23:37:06.818 - PBT_APMSUSPEND done (3682ms)
                               ...
Sun 05 Jul 2009 07:22:31.952 - PBT_APMRESUMEAUTOMATIC (Resume for automatic task)
Sun 05 Jul 2009 07:22:31.952 - PBT_APMRESUMEAUTOMATIC done (0ms)
Sun 05 Jul 2009 07:22:42.108 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 1
Sun 05 Jul 2009 07:23:32.552 - AwakeState: AS_NON_USER
Sun 05 Jul 2009 07:28:04.059 - Number of active recordings: 1
Sun 05 Jul 2009 07:32:33.378 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 0
Sun 05 Jul 2009 07:56:18.848 - User input detected (33510605)
Sun 05 Jul 2009 07:56:18.864 - PBT_POWERSETTINGCHANGE - MONITOR_POWER_ON: 1

[hveijk]

Nielson

This is clearly a case of eHome not being shut down fast enough.

Code:

vr 03 jul 2009 00:22:31.515 - Close request timed out

The next version will probably improve the situation and likely solve this issue completely.

makryger

This seems to be a different situation.
It looks like your remote (driver) doesn't do its job properly.

Are you by any chance running S4 as sleep state?
What type of remote are you using?
Does this also happen when you wake the system by the power-button?

[RikP]

Hi Herman,

I also experience the remote not working after a suspend (S3).
Please find attached my log...

The strange thing is that i have 10 usb devices before the suspend and also 10 usb devices after the suspend.
But when starting the IRTRANS application after the suspend it give an error that it can't find the device.

Any idea when you will get the new version out?

[makryger]

Nielson

This is clearly a case of eHome not being shut down fast enough.

Code:

vr 03 jul 2009 00:22:31.515 - Close request timed out

The next version will probably improve the situation and likely solve this issue completely.

makryger

This seems to be a different situation.
It looks like your remote (driver) doesn't do its job properly.

Are you by any chance running S4 as sleep state?
What type of remote are you using?
Does this also happen when you wake the system by the power-button?

You may be right about the driver issue. It's a gyration RF remote. I'm not running S4, just S3. When I press the power button first, the system gets its command correctly. The remote just does not seem to elicit a resume suspend command after waking automatically, even though the mouse and buttons are being pressed.

Maybe I can setup an AutoHotKey code that sends its own button press when I click a certain button on the remote. Maybe that will bypass the driver issue...

[hveijk]

Any idea when you will get the new version out?

Yes, right now!

Here it is: mst09097.exe

It includes all changes as described a few postings back, including the AwayMode run keys.

Herman

(A new version is released here.)

[RikP]

Hey heveijk,

Perfect my remote is working now after a suspend
But when i come back from a suspend my tuner can't be found, mediacenter sais it is in use by another program or not responding. (i have a floppydtv tuner).

I did a workaround now by letting MST not stop and start mediacenter ehome. I think something goes wrong there.

But i am very happy with the remote functionality! Thanks!

[makryger]

Hey Herman, after some more testing, it looks like its not just that remote, its other (wired) devices too. It's not like the keyboard and mouse aren't working, windows just isn't sending the resumesuspend command.

[RikP]

Hey Herman,

I've been doing some testing and it seems the problem is with the ehrecvr.exe process. When I close this and restart MCE it will work perfect.
So is it possible with this new version the process isn't handled correct?

Rik

[Cafe.Racer]

Hi,

AwayMode run keys work well - thank you very much.  My screen remains blank (No Signal) after running my Resume Script.  I will have to play with HDMIOn, I think.

I did end up with several instances of eHome running, somehow, though, and I've had a couple of lock-ups when closing eHome.  I'll testing and report back.

[hveijk]

@ Cafe.Racer, RikP

I am able to reproduce the FloppyDTV issue, I guess I am closing eHome a little too rough in version 0.9.097.

This should be fixed in this version: mst09098.exe

EDIT: A newer version can be found here

It might need a little fine-tuning. I would  like to have some logs of a couple of days from different setups (Windows XP, Vista, 7) to do soo.

@ makryger

What build are you using?

Btw. I recently noticed you the guy from My Channel Logos for 7MC!
Great Job!  I did not get a chance to try it yet, but I will probably get back to you about it.

[makryger]

@ makryger

What build are you using?

Btw. I recently noticed you the guy from My Channel Logos for 7MC!
Great Job!  I did not get a chance to try it yet, but I will probably get back to you about it.

I'm currently using build 7232, however the resumefromsuspend issue has been occurring since build 7100, both 32bit and 64bit. (worked fine in 7000.) I'm beginning to think more and more that there's something faulty about my entire setup. I've switched out motherboards and power supply-neither have fixed the issue. I'm probably going to buy some motherboard-approved Ram to replace the crucial ballistix ram I have in it right now... apparently those sticks get bad ratings anyways.

Yep, when I'm not trying to troubleshoot my own machine, I work on My Channel Logos. I think there are some dutch logos floating around the internet made for MCL.

[RikP]

Hi Herman,

Jusy tried the new version and i still have the same problem.
After a suspend i get the message the tuner is busy or not available.

When i close down the mediacenter application there are still some ehome processes running. When manually killing them and restarting the mediacenter application it is working agein.

Please find attached the log.

Regards,
Rik

ps. Makryger: here are the dutch logos
http://www.degroeneknop.nl/forum/index.php/topic,5245.msg30273.html#msg30273

ps 2. Edited message because in my hurry i did it in dutch