Run R5000-HD as a Service?

[3car]

I'm running SageTV v6.2.10, and have it configured to run as a Windows service with automatic restart. Then if my system reboots unexpectedly (power outage, Windows update etc.), SageTV will be running even though I haven't logged in.

But if my objective is to ensure recordings still take place even though I'm not logged in, don't I also need the R5000-HD program running as a Windows service? How do I do that? Is there any concern about the relatively startup timing of these 2 apps?

Thanks in advance.

[GTwannabe]

Originally Posted by 3car

I'm running SageTV v6.2.10, and have it configured to run as a Windows service with automatic restart. Then if my system reboots unexpectedly (power outage, Windows update etc.), SageTV will be running even though I haven't logged in.

But if my objective is to ensure recordings still take place even though I'm not logged in, don't I also need the R5000-HD program running as a Windows service? How do I do that? Is there any concern about the relatively startup timing of these 2 apps?

Thanks in advance.

You can either create the service yourself in the registry, or use a 3rd party tool like FireDaemon to do it for you. You want to add the DependsOnService key to the SageTV service and point it to the service that must be started first. Note that Sage removes and reinstalls the service every time you upgrade, so you need to recreate this key every time.

[GKusnick]

I don't think the startup order matters all that much. If the R5000 app starts first, it will wait for a connection from Sage. If Sage starts first, I believe it periodically retries the network encoder connection until it connects.

That's my recollection anyway. I'm not at my R5000 box right now to verify.

[3car]

OK, thanks. I'm not too inclined to buy a program (FireDaemon) for one-time use. Does anyone know of a good resource describing how to configure it yourself? I searched the web a bit and the best I could come up with is old instructions from Microsoft for Windows NT/2000.

It would be nice if Nextcom offered this for the R5000-HD (like Sage does), or at least some help for those who want to do it themselves. I wonder if it will cause any problems?

[BobPhoenix]

Originally Posted by 3car

OK, thanks. I'm not too inclined to buy a program (FireDaemon) for one-time use. Does anyone know of a good resource describing how to configure it yourself? I searched the web a bit and the best I could come up with is old instructions from Microsoft for Windows NT/2000.

It would be nice if Nextcom offered this for the R5000-HD (like Sage does), or at least some help for those who want to do it themselves. I wonder if it will cause any problems?

These instructions look good for SrvAny (what you probably already found at Microsoft) but might be better than those at Microsoft - they have pictures anyway. And yes SrvAny works with XP/2003 as well as NT and 2000 - I've used it myself before on XP.

[HawgGuy]

Originally Posted by BobPhoenix

These instructions look good for SrvAny (what you probably already found at Microsoft) but might be better than those at Microsoft - they have pictures anyway. And yes SrvAny works with XP/2003 as well as NT and 2000 - I've used it myself before on XP.

I think These instructions are more specific to Windows XP.

But I still couldn't get things working right. I'm interested in running the r5000 app as a service as well.

[BobPhoenix]

Originally Posted by HawgGuy

I think These instructions are more specific to Windows XP.

But I still couldn't get things working right. I'm interested in running the r5000 app as a service as well.

Can't help with R5000 don't have one yet and I can't say that I've tried your method above but it does look allot easier! I don't remember what I needed it for but I'm not using it now.

[GKusnick]

I haven't ever tried running it as a service, but I have to wonder what would happen to the R5000 UI if you did try it, given that services generally don't have access to the Windows desktop.

You could try checking the "Allow service to interact with desktop" checkbox, but that requires the service to run as LocalSystem, with no access to network resources. And I'm still not sure what will happen if the service tries to create its UI before anybody logs in to the desktop.