Change to running as a service

[tomfowler]

Hey guys,

I am running a successful installation on a multi-user computer with me having to log in first all the time to get SageTV running for all the clients to use (I don't usually use the server to watch).

I'd like to change over to running as a service, but when I do I'm having problems with my configuration. It treats it like a brand new installation, and it can't see the HDHomerun channel mapping created with the HDHomerun utility. It seems like the configuration files are user specific. I've tried starting the service as the specific user I am using in standalone mode but I get the same results.

Any ideas? I've tried copying the wiz.bin and sage.properties files to different locations, but no success.

Thanks,

Tom

[Fuzzy]

Sounds like you are running vista or win7, and the config files aren't actually in the SageTV folder. They are most likely stored in UAC's virtualstore (which is user-specific). You'll have to move them back to the sagetv folder to get them visible to all, and either disable UAC, or reinstall Sage in a non-protected folder (I use C:\SageTV).

[tomfowler]

Thanks for the reply. I have an 8 yr old that occasionally uses the computer and I'd rather not completely disable UAC (I've heard it can be good for these types of cases). How do I find those files in my virtualstore and move them to the real location?

[tomfowler]

OK, I found the files in my user virtual store. How do I copy them out to the real SageTV directory without issue?

[Fuzzy]

Honestly, I'd recommend moving the Sage install outside of the program files folder. I've never moved a working install in that way before though, as I've usually just reconfigured from that (copying over the wiz.bin after reinstall/configure).

You should be able to uninstall sage (the configuration files and such will remain), install sagetv in the C:\SageTV folder, then copy the wiz.bin from your program files\sagetv\sagetv folder, and then copy the properties and hdhomerun files from the virtualstore. This will allow sage to function fully, and as expected, without the UAC issues, while still keeping UAC enabled.

If all you are trying to do is get service mode to work, then you SHOULD be able to configure the service to log-on as your username. This will make it use the same virtualstore it is currently using. The only thing that will be different is the UI settings in the sage.properties will not be used (as they start using sageclient.properties).

[tomfowler]

Thanks for the advice. I'll try uninstalling and reinstalling in the new folder.

[null_pointer_us]

Doesn't the sage.properties file store some absolute paths?

You may have to open it in a text editor and change them yourself.

[Fuzzy]

Probably... I've always made it a point to not reuse a properties file though.