SageTV for Windows 9.2.1

[sundansx]

I got a bintray notice about a new SageTV for windows release, 9.2.1, but I don't see any release notes anywhere of what changed. the github page seems out of date on notes as well. Anyone?
https://bintray.com/opensagetv/saget...Windows/9.2.1#
thanks.

[wnjj]

Originally Posted by sundansx

I got a bintray notice about a new SageTV for windows release, 9.2.1, but I don't see any release notes anywhere of what changed. the github page seems out of date on notes as well. Anyone?
https://bintray.com/opensagetv/saget...Windows/9.2.1#
thanks.

I’m going to guess that it includes the 2 patches I made here https://forums.sagetv.com/forums/sho...&postcount=467 along with other cleanup. The changelog will likely be updated soon.

[jusjoken]

And the files are not there yet as I am still working on the upload.

Once the upload is complete then I will also update the release post with the details...soon/soon!

k

[Ghildebr]

Will this be an upgrade to the beta or will it be best to uninstall it first?

[jusjoken]

Originally Posted by Ghildebr

Will this be an upgrade to the beta or will it be best to uninstall it first?

You can perform an upgrade from the BETA to this release...no issue with that.

k

[Ghildebr]

[jusjoken]

Originally Posted by Ghildebr

I should mention as I believe you had a manual FIX file from wnjj. You may have to run the 9.2.1 installer twice and select Repair the 2nd time so it forces an overwrite of the manually changed files....but otherwise should work fine.

k

[Tiki]

Was a fix ever found to allow the USBUIRT to work properly with 64-bit Sage when running in service mode (so it could be used as both a blaster and receiver at the same time)?

[Ghildebr]

Originally Posted by jusjoken

I should mention as I believe you had a manual FIX file from wnjj. You may have to run the 9.2.1 installer twice and select Repair the 2nd time so it forces an overwrite of the manually changed files....but otherwise should work fine.

k

I did run the installer twice with a repair the second time. I am however getting the two attached errors when installing the x64 client on a 64 bit version of Windows 10. I am running the install as a local administrator with the "right click and run as administrator" when executing the executable. I selected "Ignore" on both popups and so far do not see anything abnormal.
Gary

[Ghildebr]

As a followup here are my registry settings on the client.

AlwaysSwapForAC3Filter = 1
EnableSageTVStreamDemux = 0

[jusjoken]

Originally Posted by Ghildebr

I did run the installer twice with a repair the second time. I am however getting the two attached errors when installing the x64 client on a 64 bit version of Windows 10. I am running the install as a local administrator with the "right click and run as administrator" when executing the executable. I selected "Ignore" on both popups and so far do not see anything abnormal.
Gary

Although this is a know issue i cannot make it happen on any of my test machines including Win 10. My guess is it occurs if those keys were previously manually added by a user so the installer has issues on accessing the key...is this true in your case?

k

[jusjoken]

Originally Posted by Tiki

Was a fix ever found to allow the USBUIRT to work properly with 64-bit Sage when running in service mode (so it could be used as both a blaster and receiver at the same time)?

Not that I am aware of so it is not included yet.

k

[Ghildebr]

Originally Posted by jusjoken

Although this is a know issue i cannot make it happen on any of my test machines including Win 10. My guess is it occurs if those keys were previously manually added by a user so the installer has issues on accessing the key...is this true in your case?

k

Its strange that both the "Everyone" and the "System" group have permission to both Folders in Regedit. I would think that "TrustedInstaller" should have permission there somewhere. I do beleive that I added these settings somewhere in the x64 troubleshooting\testing stages. Regardless the Everyone group having Full Control should of been good enough to keep the popup from occurring.

[jusjoken]

Originally Posted by Ghildebr

Its strange that both the "Everyone" and the "System" group have permission to both Folders in Regedit. I would think that "TrustedInstaller" should have permission there somewhere. I do beleive that I added these settings somewhere in the x64 troubleshooting\testing stages. Regardless the Everyone group having Full Control should of been good enough to keep the popup from occurring.

Agreed...I just cannot replicate and get this error...hopefully not too many run into it or i find time to test more.

k

[wnjj]

Originally Posted by Tiki

Was a fix ever found to allow the USBUIRT to work properly with 64-bit Sage when running in service mode (so it could be used as both a blaster and receiver at the same time)?

According to JustFred, it worked just fine (https://forums.sagetv.com/forums/sho...&postcount=404). I don’t know what system level things could possibly be affecting your setup. It seems unlikely to be the old Vista permission issue since that would never work for JustFred. Also, when I wrote Jon the second time he didn’t respond so I don’t know what else can even be done. I’ll look when I get some time in case there is some lower level debug code I could add to shed some light.

In the meantime, if 64-bit is important enough, run in application mode. I have for over 10 years without issue or missed recordings.

[waylo]

Originally Posted by jusjoken

Although this is a know issue i cannot make it happen on any of my test machines including Win 10. My guess is it occurs if those keys were previously manually added by a user so the installer has issues on accessing the key...is this true in your case?

k

I had the same errors pop up with my client x86 install, on Win7x64. The server upgrade x86 install did not have this issue. So far it doesn't seem like any functionality is affected though.

[jusjoken]

Originally Posted by waylo

I had the same errors pop up with my client x86 install, on Win7x64. The server upgrade x86 install did not have this issue. So far it doesn't seem like any functionality is affected though.

Good info..,do you know if those settings existed previously?

[Telecore]

For those of us wanting to use the 64 bit Windows Installer to duplicate our 32 bit setup (copy wiz.bin and sage.properties), what is the best way to migrate or copy the plugins from the 32 bit install to the 64 bit install? (Several plugins are indicating that they are "failed")

[jusjoken]

Originally Posted by Telecore

For those of us wanting to use the 64 bit Windows Installer to duplicate our 32 bit setup (copy wiz.bin and sage.properties), what is the best way to migrate or copy the plugins from the 32 bit install to the 64 bit install? (Several plugins are indicated that they are "failed")

The best way is don't do it...install them clean.

Second approach would be install into the x86 location but then the x86 will not function.

You could attempt to copy all the jars and plugins folders manually but you run the risk of missing something or a plugin that has settings somewhere that is path specific.

No easy button IMHO.

k

[Telecore]

There is something weird going on - I am trying to uninstall all of the plugins that were present due to copying wiz.bin/sage.properties from the 32 bit Sage folder - sometimes after uninstalling plugins and restarting SageTV, plugins that were uninstalled are re-appearing as installed, then disappearing after some re-starts and re-appearing later. Any ideas on this? Is there a way to globally delete all plug-ins?

UPDATE: Never mind - I eventually was able to uninstall all plug-ins, but some took multiple attempts to do so. Not sure why.