Some Missed Recordings

[grits]

I'm a relative newbie to GBPVR but have been using it for a couple of months and I really am amazed at the functionality. I'm even using EWA. In general no major complaints, however I have on occasion missed some recordings. I figured this was just because my "leftover, off-lease computer" was under-powered and sometimes wasn't up to the task. This post is about some missed recordings Thursday night. This time I was even on the computer and confirmed it was recording "30 Rock" during the broadcast, so I was surprised when I looked for it afterward and couldn't find it. Could someone let me know which logs to post that may let someone decipher the problem? I've looked at a few and they do reference the recording starting. I'd like to know why it didn't get saved.

My configuration is
PIII 850 Mhz PC
Windows XP SP2
Haupauge HVR-1600
Haupauge MediaMVP

Thanks for any help you can give me.
Grits
Oakville, Ontario, Canada

[grits]

Forgot to mention, I'm using GB-PVR v1.2.9

[Carlito]

Probably best just to zip up the whole logs directory and post them. That way you're sure to get the right logs.

[sub]

Yeah do what carlito said. Next time it misses a recording, zip and attach the logs, and let me know what it was supposed to record at what time.

[grits]

OK here you go. The night of April 24 missed all its recordings, including 30 Rock at 8:30 pm, The Office at 9pm, and ER at 10 pm. I can confirm that I visually saw the the GBPVR icon green while it was recording 30 Rock. Checked back the next day and nothing was recorded. I can see in some of the logs that the recording started, but thats as far as I've got.

Thanks again for your help and quick responses.

[sub]

2008-04-23 23:34:03.109 ERROR failed to start Conexant Graph
2008-04-23 23:34:03.109 VERBOSE ERROR_NO_SYSTEM_RESOURCES

GB-PVR had attempted to perform these recordings, but for whatever reason the device refused to start. The most common cause of this specific error would be the device being in use by some other software on the machine. Otherwise it could be some driver bug.