Recording failure "...failed to lock a signal"

[Graham]

But when I right click the tray symbol and choose restart recording service, it works. Is there a command line option for the restart recording service?

Right click the Start menu "Start" and "Stop" recording service items and select Properties. This will show the commands used to start and stop the recording service. Plus, I suspect that the commands will need to run as Administrator.

Do you know about using Administrative Tools --> Task Scheduler to run a task when the computer wakes up? This may help ... http://www.sevenforums.com/tutorials/675...html?ltr=T

Good Luck.

[Stargrove1]

Right click the Start menu "Start" and "Stop" recording service items and select Properties. This will show the commands used to start and stop the recording service. Plus, I suspect that the commands will need to run as Administrator.

Do you know about using Administrative Tools --> Task Scheduler to run a task when the computer wakes up? This may help ... http://www.sevenforums.com/tutorials/675...html?ltr=T

Good Luck.

I already tried a script from the command with the following content:

"C:\Program Files\NPVR\NPVRServiceControl.exe"
"C:\Program Files\NPVR\NPVRServiceControl.exe" start

But then two dialog boxes appear telling me "Stopped" and "Started". In addition, after the restart, I receive a message that NPVR could not communicate with the recording service.

[Stargrove1]

From you description, it sounds like a driver bug.

You could try this patch though. It will terminate NDigitalHost.exe when it detects the machine waking, forcing it to relaunch it next time it's required..

I replaced the NDigitalHost, rebooted the system and scheduled a recording (auslandjournal). But no change, still not recording. I attached the logs

Do you mean the driver of the DVB-C card is the problem? Does NPVR connect in different way than GBPVR did?

[sub]

Do you mean the driver of the DVB-C card is the problem?

Yes. It sounds like the device doesnt function first time after waking from standby. Other devices don't do this, otherwise we'd see lots of posts about it.

Does NPVR connect in different way than GBPVR did?

They're different apps, and they do things a slightly different way. It could easily be exercising a different part of the device's drivers, or the driver doesn't like something about the sequence which NextPVR does things.

This device may have been behaving exactly the same way in GBPVR - you might have been saved in the past by logic in GBPVR that would do a one-off check of a recording size about 30 seconds into a record, and if it was zero bytes, it'd restart it.

[Stargrove1]

I already tested the drivers which came with the card, as well as the latest from the internet.

Does that mean I have to purchase another type of card to get NPVR running?

[sub]

I'm sure you'd be able to hobble together some work around. Maybe look into creating a wakeup.bat that uses devcon.exe to restart the driver. I'm no batch file expert though, so dont ask me exactly what that batch file would look like. Google will turn up plenty of info about devcon.exe though.

[Stargrove1]

I'm sure you'd be able to hobble together some work around. Maybe look into creating a wakeup.bat that uses devcon.exe to restart the driver. I'm no batch file expert though, so dont ask me exactly what that batch file would look like. Google will turn up plenty of info about devcon.exe though.

I tried to use devcon to restart the driver, but afterwards NextPVR wasn't able to connect to the recording service.
I bought a new DVB-C from from different company and now it works properly again.

Thanks to everybody who helped to find a solution and thanks to sub for the information with the driver!