Recording Service Not Working

[hasso]

I think this problem has been mentioned elsewhere, but wasn't able to locate the thread. Basically I have found that when restarting the PC the only way I could get the recording service to work (i.e. record shows, clicking on the icon in the task bar for getting the tuner status display, etc) was to go into task manager and end any/all GBPVR.exe instances I found. Once I did this, then the recording service became 'responsive' and I could restart GBPVR.exe without issues. If I did not do this I also found that the configuration panel would also freeze as well when clicking on 'OK'. I would assume that this was due to it trying to restart an unresponsive recording service.

This problem has been there for awhile, but since I usually let the PC hibernate where this problem doesn't exist, I haven't mentioned it earlier.

Anything I can do to find/fix the problem?

[sub]

Reproduce the problem, then zip and attach the logs and I'll take a look.

[hasso]

I think I've solved the problem. I've got the PVR350 and the PVR500MCE. Originally, when starting up the PC, ir.exe connected to the PVR500MCE (which does not have a remote input) instead of the PVR350 for which I do have the remote control. So I wrote a start-up script that stops the recording service, stops ir.exe, stops the PVR500MCE, restarts ir.exe (which then finds the PVR350), restart the PVR500MCE, restart the recording service.

It looks like this startup script was trying to stop the recording service while it was in the middle of starting up. This probably caused the recording service not to stop/restart properly. This was not an issue when I only had two recording devices. Now that it has four the recording service takes longer to startup. I put in a 'wait' time of 30 seconds in the startup script before stopping the recording service and now it looks like it stops and restarts without issues... and the configuration window also works without freezing.

In the script I stop the recording service before disabling the PVR500MCE, just to be 'safe'. Do I really need to stop the recording service before disabling and reenabling devices? I would assume I'd have an issue if the device was being used by the recording service?

[sub]

In the script I stop the recording service before disabling the PVR500MCE, just to be 'safe'. Do I really need to stop the recording service before disabling and reenabling devices? I would assume I'd have an issue if the device was being used by the recording service?

I obviously dont test this sort of thing, but I can imagine it being pretty messy if the recording service starts recording before you do this restart.

[gEd]

from http://www.hauppauge.co.uk/board/showthread.php?t=7347

The remote type is set in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Hauppauge\IR

IRPort and I2Ctype:

Nova-t-USB2
IRPort = 0x34
I2Ctype = 0x1a

Nova-t PCI
IRPort = 0x00
I2Ctype = 0x00

Perhaps you could contact Hauppauge tech support and see if they can provide you with the IRPort and I2Ctype for the 350 and 500 respectively.

I used the above info to pin ir.exe to my Nova-T 500 instead of the USB2.

[hasso]

Yeah.. I did do a search on various other forums to find alternate solutions, but it does look like the only consistent way to get ir.exe to associate with the 350 instead of a 500MCE is to go through the disabling/enabling process.

There were some messages saying to change I2Ctype to decimal 19, but there was no confirmation that this actually works. May give it a go as it would be nice to get rid of the script.