TV-Server Version: 1.0.2
MediaPortal Version: 1.0.2
MediaPortal Skin: X-Factor
Windows Version: Vista 64
1. TV Card: Fire-DTV DVB-C X 2
Hello!
I have a HTPC running MediaPortal 1.0.2.
I have both client and server on the same computer.
As I am running 4TheRecord I am not using the PowerScheduler plugin. I am using the windows Power settings.
This has been working perfect for mounths. The computer have entered sleep after 10 minutes of inactivity.
However that is not the case any more. When MediaPortal client open the computer never sleeps.
First I thought that it was MovingPictures that caused it. But that was not the case. I have tried to disable every plugin I am using. Turned off the watch of the music char directory and so on. I have set the log level to debug. There is nothing in the log during a long time, ie the computer should enter sleep. If I close the MediaPortal client the computer always goes to sleep.
I do not know what causes this behaviour or why it suddenly have started.
I am not really sure when this has started, befor 1.0.2 or not or before doing the last windows update.
How to trace the cause?
/Erik
MediaPortal Version: 1.0.2
MediaPortal Skin: X-Factor
Windows Version: Vista 64
1. TV Card: Fire-DTV DVB-C X 2
Hello!
I have a HTPC running MediaPortal 1.0.2.
I have both client and server on the same computer.
As I am running 4TheRecord I am not using the PowerScheduler plugin. I am using the windows Power settings.
This has been working perfect for mounths. The computer have entered sleep after 10 minutes of inactivity.
However that is not the case any more. When MediaPortal client open the computer never sleeps.
First I thought that it was MovingPictures that caused it. But that was not the case. I have tried to disable every plugin I am using. Turned off the watch of the music char directory and so on. I have set the log level to debug. There is nothing in the log during a long time, ie the computer should enter sleep. If I close the MediaPortal client the computer always goes to sleep.
I do not know what causes this behaviour or why it suddenly have started.
I am not really sure when this has started, befor 1.0.2 or not or before doing the last windows update.
How to trace the cause?
/Erik