home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
MCE infrared reciever dies on resume!
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="P.Niem" data-source="post: 268162" data-attributes="member: 64879"><p>My previous HTPC was a AMD 2500+ with a ASUS mother board with VIA chipset. I had the same weird behavior. I search the internet many times and saw that there were many people with the same problem. The problem here might be caused by the VIA chipset. There are some known hardware issues regarding USB in VIA chipset. I've tried almost everything. First solution was to run a batch file at resume that reinitialised the USB devices, but then there was a problem to disconnect. Finally I made a home brew piece of hardware with a 4 contact relay. The MCE remote receiver was connected via this relay with the USB port. As soon as my HTPC woke up from S3. The relay was switched on and disconnected the MCE remote receiver from its USB port. Six seconds later the relay was switched off again and this causes the a reconnection of the MCE remote to its USB port. Windows reacts on it by 2 time the Ding Dong and after that I could use my remote again. Not a very nice solution, but it works. </p><p></p><p>My AMD HTPC wasn't that stable (there were more issues) and finally I decided to buy another mother board with a Intel duo and Intel chipset. Since then I have no trouble at all with USB. This is also a Asus mobo and I haven't got any stand-by issues.</p></blockquote><p></p>
[QUOTE="P.Niem, post: 268162, member: 64879"] My previous HTPC was a AMD 2500+ with a ASUS mother board with VIA chipset. I had the same weird behavior. I search the internet many times and saw that there were many people with the same problem. The problem here might be caused by the VIA chipset. There are some known hardware issues regarding USB in VIA chipset. I've tried almost everything. First solution was to run a batch file at resume that reinitialised the USB devices, but then there was a problem to disconnect. Finally I made a home brew piece of hardware with a 4 contact relay. The MCE remote receiver was connected via this relay with the USB port. As soon as my HTPC woke up from S3. The relay was switched on and disconnected the MCE remote receiver from its USB port. Six seconds later the relay was switched off again and this causes the a reconnection of the MCE remote to its USB port. Windows reacts on it by 2 time the Ding Dong and after that I could use my remote again. Not a very nice solution, but it works. My AMD HTPC wasn't that stable (there were more issues) and finally I decided to buy another mother board with a Intel duo and Intel chipset. Since then I have no trouble at all with USB. This is also a Asus mobo and I haven't got any stand-by issues. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
MCE infrared reciever dies on resume!
Contact us
RSS
Top
Bottom