Windows Installer

[jusjoken]

Version 9.0.14.568 R1.012 fixes an issue that was raised where in a windows client or server you could not display a web site link for a plugin.

The issue itself came from when the "." was removed from the classpath as the 2 jar files used for this feature (jdic.jar and packager.jar) were previously located in the SageTV root and not in the JARs folder. This release will install these in the JARs folder.

Note: jdic.jar and packager.jar may be used for other features I am not aware of but I have tested that moving these has resolved the issue mentioned above.

k

[tbower]

FYI - Observing much improved video/audio playback with this release on Dell Convertible laptop on wireless network connections. It has a smoother recovery to dips in network performance on playback.

[Pelicanjoe]

Originally Posted by tbower

FYI - Observing much improved video/audio playback with this release on Dell Convertible laptop on wireless network connections. It has a smoother recovery to dips in network performance on playback.

Why would that be? I looked on the release log and no changes were made to improve video/audio playback. What version did you upgrade from?

[wayner]

With V9 and Windows is there any reason to install the client version of SageTV when you can just install the server version and then use the command "sagetv.exe -client -connect servername" to run the client version when and if you need?

[Fuzzy]

Originally Posted by wayner

With V9 and Windows is there any reason to install the client version of SageTV when you can just install the server version and then use the command "sagetv.exe -client -connect servername" to run the client version when and if you need?

Yes - if you're never going to run a server on the client machine, than there's no reason to clutter it up or modify the command line, so you just install the client package.

[EnterNoEscape]

Originally Posted by wayner

With V9 and Windows is there any reason to install the client version of SageTV when you can just install the server version and then use the command "sagetv.exe -client -connect servername" to run the client version when and if you need?

Originally Posted by Fuzzy

Yes - if you're never going to run a server on the client machine, than there's no reason to clutter it up or modify the command line, so you just install the client package.

Also if you install the server, you'll end up with a SageTV service that you don't need in your Windows services.

[wnjj]

I took the post to mean the server version is already installed and only IF the client version is needed would you use the command line. The simple answer is yes, it will work fine. The client .exe is nothing more than the server .exe compiled with the command line options for client mode forced on.

[tbower]

It was most likely SageTVPlaceshifterSetup_9.0.13.536_R1.011. The improvements could have been due to some Windows 10 update but, sure seemed like it was the new install of the application. Maybe an uninstall and reinstall of the same version would have given the same results. I love the end result just the same!

[sflamm]

When upgrading to 9.0.14.568 from 9.0.13.536 - simply install over once? (assume it leaves wiz.bin etc alone)

There is a comment in the installer directions:

If upgrading from the same version level - 9.0.4.xxx to 9.0.4.yyy you will need to run the installer a 2nd time and select repair to insure ALL files get installed. Normally we will try to release full point versions when possible.

Assume running twice only required for minor versions of 9.0.14.xxx? Is the requirement to install a second time and repair still true?

[jusjoken]

Originally Posted by sflamm

When upgrading to 9.0.14.568 from 9.0.13.536 - simply install over once? (assume it leaves wiz.bin etc alone)

There is a comment in the installer directions:



Assume running twice only required for minor versions of 9.0.14.xxx? Is the requirement to install a second time and repair still true?

2nd run is only required for minor releases with the same 3rd digits... so 9.0.13.x to 9.0.14.y does not require a 2nd run.

Wiz.bin and properties files are not included in any installer build so will not be overwritten. Sage does create these files on first run if they do not exist or will upgrade the wiz.bin if needed between versions.

k

[mdnttoker]

Installed v9 over v7 over the weekend, and transitioned to SD EPG. Smooth as butter! Thank you everyone!

[jusjoken]

Release on Bintray

Note...9.1.1 has only linux changes but i will likely build a release tomorrow anyway to keep the versions the same.

k

[JREkiwi]

Originally Posted by jusjoken

Note...9.1.1 has only linux changes but i will likely build a release tomorrow anyway to keep the versions the same.

Does the G1GC String deduplication not apply to Windows?

John

[Monedeath]

Originally Posted by JREkiwi

Does the G1GC String deduplication not apply to Windows?

It does, that was in 9.1.0 the only thing in 9.1.1 was a bug fix specific to Linux.

Although the G1GC feature requires Java8 or newer, so depending on which web plugins you're using on Sage you're going to need to decide between those plugins and better heap management.

Note: Java7 is still the minimum requirement, 9.1 will just default to the old behavior if it detects java7.

[wubdich]

Just to get it right: G1GC will be used on Windows if Java 8 is found during setup/install or will G1GC will be used on Windows if Java 8 is found during SageTV startup ?

[EnterNoEscape]

Originally Posted by wubdich

Just to get it right: G1GC will be used on Windows if Java 8 is found during setup/install or will G1GC will be used on Windows if Java 8 is found during SageTV startup ?

The setup has nothing to do with it this time. The Java version detected on SageTV startup is what gets used.

[Monedeath]

Originally Posted by wubdich

Just to get it right: G1GC will be used on Windows if Java 8 is found during setup/install or will G1GC will be used on Windows if Java 8 is found during SageTV startup ?

From my understanding, it's a branch in the code that happens at runtime(when Sage does Garbage collection), so it'll be a matter of whatever version of Java SageTV thinks you're running on. So "at startup of SageTV" is the correct answer here.

[rickgillyon]

Originally Posted by jusjoken

Note...9.1.1 has only linux changes but i will likely build a release tomorrow anyway to keep the versions the same.

The 9.1.1.651 files are there now, but are missing the .exe extensions.

[gordyp]

Originally Posted by rickgillyon

The 9.1.1.651 files are there now, but are missing the .exe extensions.

That might not be all they are missing (the .exe part was easy enough to fix, just add it to the downloaded file name) - I had problems with the server download - I was getting a bunch of Java errors (I suspect the java.jar file was missing) and had to roll back to 9.1.0.648 on the server. The 9.1.1.651 client install seems fine, aside from the missing file extension...

[rickgillyon]

Originally Posted by gordyp

That might not be all they are missing (the .exe part was easy enough to fix, just add it to the downloaded file name) - I had problems with the server download - I was getting a bunch of Java errors (I suspect the java.jar file was missing) and had to roll back to 9.1.0.648 on the server.

9.1.1.651 is working fine here.