As per my recent post on the GBPVR forum a (recent) total WinXP re-install has thrown up a problem I just cannot seem to troubleshoot. I've been using GBPVR since mid-2005, with a USB-UIRT.
Almost invariably, after the PC has been on for some time and running 24/7, GBPVR loses the ability to send IR channel changes i.e. No "red IR light" can be seen at the USBIRT.
GBPVR sends the codes OK, but the USBUIT either isn't getting the signals or not sending them. A simple restart of GBPVR (not WinXP, just GBPVR) fixes this immediately. The author of GBPVR cannot see the reason for it, as the codes are sent.
Is there a log or something from USBUIRT which would tell me if the USB-UIRT is getting the attempts to change channel?
Any ideas as to how to start troubleshooting this?
Cheers
Kristian
[EDIT]The problem appears to have afflicted "a few" other users before ?
There seems to be a few posts on GBPVR about a similar issue, with GBPVR eitehr holding on or USBUIRT not letting go. The GBPVR author added a switch <RecycleUSBUIRT>true</RecycleUSBUIRT> to his config.xml a while back, but it would appears that he believes this to be a USBUIRT issue from the posts. I'm not looking at pointing figures at whose issue it is, I'd just really like it fixed
The GBPVR Posts are these:
http://forums.gbpvr.com/showthread.php? ... cleUSBUIRT (GBPVR loses ability to send IR Channel Changes?)
http://forums.gbpvr.com/showthread.php? ... cleUSBUIRT (Very high CPU Load - cause by USB-UIRT driver?)
http://forums.gbpvr.com/showthread.php? ... cleUSBUIRT (gbpvr eats cpu cycles)
http://forums.gbpvr.com/showthread.php? ... cleUSBUIRT (GBPVR/USBUIRT Not Sending "Enter" after first channel change)