Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1260980" data-attributes="member: 141969">I don't have a specific solution for you, but this area of MP has been problematic for several releases now. This is a very complex area, and I think that it is the case that the developer who knows about this part of MP cannot reproduce the problem on his own system (making it exceedingly difficult to identify the origin of the problem).A possible solution is to upgrade to MP 1.22, as this may solve your problem (MP 1.22 contains some fixes that address this area).As a workaround, remember that you can avoid the problem by exiting to the Windows desktop before you sleep or hibernate your system. Your can define a button on your remote to invoke MP's exit dialogue, and the START button on your remote can start MP from the desktop when your next wake the system. (This is how I use my HTPC.)-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1260980, member: 141969"] I don't have a specific solution for you, but this area of MP has been problematic for several releases now. This is a very complex area, and I think that it is the case that the developer who knows about this part of MP cannot reproduce the problem on his own system (making it [i]exceedingly[/i] difficult to identify the origin of the problem). A possible solution is to upgrade to MP 1.22, as this may solve your problem (MP 1.22 contains some fixes that address this area). As a workaround, remember that you can avoid the problem by exiting to the Windows desktop before you sleep or hibernate your system. Your can define a button on your remote to invoke MP's exit dialogue, and the START button on your remote can start MP from the desktop when your next wake the system. (This is how I use my HTPC.) -- from CyberSimian in the UK [/QUOTE]

Verification