v9 windows 10 configuration issues

[lewispm]

I just tried to edit Sage.properties, but when I stop the service the Sage.properties file disappears. I have been able to edit it before, but I tried it twice, and it immediately renames the file to Sage.properties.autobackup. Do I just edit the last autobackup file?

Speaking of when I was able to edit it before, the v9 FAQ lists the instructions for moving recordings to a new directory as the same method that was used previously, i.e. advanced_video_file_recovery=true. This entry was not listed in my Sage.properties when I tried it a few weeks ago. (Now I can't verify, as the file is deleted, see above.)

I am using win10 from the windows installer.

[Taddeusz]

Originally Posted by lewispm

I just tried to edit Sage.properties, but when I stop the service the Sage.properties file disappears. I have been able to edit it before, but I tried it twice, and it immediately renames the file to Sage.properties.autobackup. Do I just edit the last autobackup file?

Speaking of when I was able to edit it before, the v9 FAQ lists the instructions for moving recordings to a new directory as the same method that was used previously, i.e. advanced_video_file_recovery=true. This entry was not listed in my Sage.properties when I tried it a few weeks ago. (Now I can't verify, as the file is deleted, see above.)

I am using win10 from the windows installer.

You have to stop the SageTV service before editing the sage.properties file. Editing the file while SageTV is running does nothing. The changes go away the next time SageTV syncs the file, which is usually when the service is stopped.

[lewispm]

I can see the file, but when I stop the service to edit sage.properties, thats when the file disappears.

[Taddeusz]

Originally Posted by lewispm

I can see the file, but when I stop the service to edit sage.properties, thats when the file disappears.

What operating system?

[lewispm]

I am using win10 from the windows installer.[/QUOTE]

[Taddeusz]

Originally Posted by lewispm

I am using win10 from the windows installer.

[/QUOTE]

Oh, duh. Sorry, I was still waking up when I replied. You sure the file is actually disappearing? How are you sorting the folder? What do you see if you sort by date from newest to oldest?

I ask this because Windows tends to put newly added files to the bottom of the list. It doesn't necessarily automatically adjust the sort when changes happen.

You might even go to a command prompt and type the following commands assuming you are on 64bit and installed to the default directory, otherwise replace the path with your custom path:

cd "C:\Program Files (x86)\SageTV\SageTV"
dir /od

Personally, I always have my SageTV folder sorted by date with the newest files at the top.

[Tiki]

Originally Posted by Taddeusz

Oh, duh. Sorry, I was still waking up when I replied. You sure the file is actually disappearing? How are you sorting the folder? What do you see if you sort by date from newest to oldest?

I ask this because Windows tends to put newly added files to the bottom of the list. It doesn't necessarily automatically adjust the sort when changes happen.

You might even go to a command prompt and type the following commands assuming you are on 64bit and installed to the default directory, otherwise replace the path with your custom path:

cd "C:\Program Files (x86)\SageTV\SageTV"
dir /od

Personally, I always have my SageTV folder sorted by date with the newest files at the top.

Could this be a UAC thing? UAC was introduced in Windows Vista and one of its features is to prevent programs from directly modifying files in certain locations (including the "Program Files" folder). So, when programs try to write stuff to one of these protected folders, they get re-directed to a user folder somewhere else.

Turning off UAC, or installing Sage to a different location (such as c:\Sage) might get around this.

I know Sage had some issues with this a long time ago. I think I recall that some changes were made in Sage v7 to make it more consistent with the Windows preferred behavior. It's possible that something is different in v9.

Personally, I'm still running Sage v7 and I have it installed in c:\Sage, so I don't see any of these sorts of issues.

[Taddeusz]

Originally Posted by Tiki

Could this be a UAC thing? UAC was introduced in Windows Vista and one of its features is to prevent programs from directly modifying files in certain locations (including the "Program Files" folder). So, when programs try to write stuff to one of these protected folders, they get re-directed to a user folder somewhere else.

Turning off UAC, or installing Sage to a different location (such as c:\Sage) might get around this.

I know Sage had some issues with this a long time ago. I think I recall that some changes were made in Sage v7 to make it more consistent with the Windows preferred behavior. It's possible that something is different in v9.

Personally, I'm still running Sage v7 and I have it installed in c:\Sage, so I don't see any of these sorts of issues.

This was fixed a long time ago. I keep UAC enabled on all my machines, even my SageTV server, and have no issues. The sage.properties file gets written to the correct folder.

[lewispm]

Originally Posted by Taddeusz

How are you sorting the folder? What do you see if you sort by date from newest to oldest?

Thanks Taddeusz, this was the problem. I was watching the folder in file manager when I closed the service, so I saw it disappear.

I left the folder, closed the service, re-entered, and it was where it was supposed to be.

Thanks!