Open Source Windows Installer

[Fuzzy]

Originally Posted by jusjoken

I have separated the Windows Installer download location from the Linux location as it can be confusing when versions are not released at the same time.

The first post has been updated with both links....

Windows Files

Linux Files

k

Going along with this, do you think the respective building projects are ready to be rolled into a combined automated build system, so we can get version releases lined up? and released together?

[jusjoken]

Originally Posted by Fuzzy

Going along with this, do you think the respective building projects are ready to be rolled into a combined automated build system, so we can get version releases lined up? and released together?

I don't think they are ready yet but still not sure how we are going to do that. I hope to first create a build script so the Native and Windows Installers can be built from the command line and then we can figure how to add in the rest....so still a ways to go.

k

[Hotliner]

Thanks for all the hard work.. I'm going to give V.9 a whirl this weekend.

Hotliner

[jusjoken]

I have built and uploaded another installer release and I felt it was far enough along to consider this a RC version of the installer.

Windows Files

This version no longer has the Client/Server EXE as forcing elevation as I took a different approach in the registry to resolve previous issues.

The Launch button has been removed from the Install Complete dialog as it could not be made to work if the user changed the install folder from within ProgramFiles (a WIX tool limitation). So I removed it to reduce confusion.

All other issues on my list have been resolved (that I remember ).

Note: if upgrading from 9.0.4.224 to 9.0.4.232 you will need to run the installer a 2nd time and select repair to ensure all files get installed. The installer system does not handle "same version" releases well so the 2nd run is required. This is not needed for upgrades from v7 or 9.0.3.xxx and prior releases.

Please continue to report all issues here.

Thanks
k

[SHS]

Originally Posted by jusjoken

Note: if upgrading from 9.0.4.224 to 9.0.4.232 you will need to run the installer a 2nd time and select repair to ensure all files get installed. The installer system does not handle "same version" releases well so the 2nd run is required. This is not needed for upgrades from v7 or 9.0.3.xxx and prior releases.

Hmm in stead of doing that I think would eazy just to uninstall them and reinstall the new ver

[ThePaladinTech]

Hi - I upgraded to SageTV 9 server using your beta 3 installer. worked great! I installed over the top of my existing 7.19 install.

-but-

Doing the same thing with my sage client it doesn't seem to work somehow? Again I am upgrading over the top of the 7.19 client. The app shows the V9 splash screen, but it shows "connection lost reconnecting" after that. My SD-200 connects fine.

I thought I would need to install over the 7.19 client to retain closed caption.
any advice to get this working?

[jusjoken]

Originally Posted by ThePaladinTech

Doing the same thing with my sage client it doesn't seem to work somehow? Again I am upgrading over the top of the 7.19 client. The app shows the V9 splash screen, but it shows "connection lost reconnecting" after that. My SD-200 connects fine.

I thought I would need to install over the 7.19 client to retain closed caption.
any advice to get this working?

Your approach is correct....to retain CC and MPEG2 decoders install OVER v7.

Did the install complete properly...ie: you get a successful dialog or was an error reported.

If the install was succesful, then I please post the sagetv client logs. If debug is not already on then you need to go into the client properties and set debug = true...start the client until you get the error and then post the log.

k

[jusjoken]

Originally Posted by SHS

Hmm in stead of doing that I think would eazy just to uninstall them and reinstall the new ver

You can certainly do that but I have tested the upgrade and then repair and it works well.

Eventually we will get to a point where we only release full point versions and the smaller builds would only be for testing purposes so most people will not be in this situation.

k

[ThePaladinTech]

shouldn't this post be at least pinned? and maybe pinned and moved to the downloads subforum? Or a new topic that links to the installer downloads be made in the downloads area? as it stands the downloads area *does* have a pinned topic that links to windows executables.

[ThePaladinTech]

Originally Posted by jusjoken

Your approach is correct....to retain CC and MPEG2 decoders install OVER v7.

Did the install complete properly...ie: you get a successful dialog or was an error reported.

If the install was succesful, then I please post the sagetv client logs. If debug is not already on then you need to go into the client properties and set debug = true...start the client until you get the error and then post the log.

k

Yes, install completed. I've done this on a few machines now. (all windows ten if that matters, as smart screen does complain when I run the installer) all with the same results. On one machine I've gone so far as uninstalling the client and java and installing just the open source client. still no worky.

On another machine I've gone and added a line in my sageclient.properties file debug=true. This line didn't exist? Ran the client but didn't find any logs- where should I be looking?

[jusjoken]

Originally Posted by ThePaladinTech

Yes, install completed. I've done this on a few machines now. (all windows ten if that matters, as smart screen does complain when I run the installer) all with the same results. On one machine I've gone so far as uninstalling the client and java and installing just the open source client. still no worky.

On another machine I've gone and added a line in my sageclient.properties file debug=true. This line didn't exist? Ran the client but didn't find any logs- where should I be looking?

sorry...the setting is...

debug_logging=true

and please note....it seems windows 10 does not include mpeg2 support so if not installing over v7 then you will need other decoders such as LAV filters

oh...and please post what smartscreen is complaining about...


k

[ThePaladinTech]

Yep - thought that might have been it. I enabled that as well and was unable to find any logs.
-so-
I uninstalled everything (sage and java), deleted all files from c:\program files(x86)\sagetv - there were leftover files.

Installed V9 - it works!

uninstalled v9, deleted the sageTV directory again (again there were leftover files)

installed 7.19 - Ran it, it cannot find a server. Which makes sense as it is now a V9 server. but I cannot register my client license key...

Upgraded to V9 - and *IT WORKS*

So, I'm still confused. happy but confused LOL - Am I missing anything by not having the 7.19 client key registered?

and why does it work now? I had some client plugins installed, could they have been the problem? but AFAIK they are only client plugins that run happily on the server.

I still have two other machines that aren't working. If there is something I can do to help you? let me know, otherwise I am happy to completely uninstall both of them and use the steps that succeed on this machine.
Just kinda baffled as to why it works.

-and- why didn't it ever generate any logs? I looked in the sageTV directory for *.log files and even searched for them on the whole c: drive.

Edit:

oh and the smart screen errors where "windows smart screen has prevented an unknown program from starting" - along with the "sageTvclientxxxx.exe is not commonly downloaded" when I downloaded it.

A thought - I had 'auto connect' enabled in my setups the server string is now "SageTV,V9.0.4,192.168.1.45" - wonder if that has something to do with it?

edit2:
sagetvclient_0.txt *doh* - I will see if I can get some errors on my other machines.

[bryanzim]

If I install the latest RC installer over V9.0.3 then the HD Home Run tuners work; however if I just install the RC installer then the HD home run tuners no longer work with capture device failure so it seems as if this issue is still outstanding.

On another note, if I do an upgrade install then both V9.0.3 and V9.0.4 show up under programs and features instead of just the V9.0.4.

I should have time this weekend to investigate. What do I need to do to produce a log to investigate this issue?

[jusjoken]

Originally Posted by bryanzim

If I install the latest RC installer over V9.0.3 then the HD Home Run tuners work; however if I just install the RC installer then the HD home run tuners no longer work with capture device failure so it seems as if this issue is still outstanding.

For this one I need you to have debug_logging=true in your properties file and then recreate the issue where you get the error and then upload the sagetv_x.txt file to review and see if something leads me to what files are missing.

Originally Posted by bryanzim

On another note, if I do an upgrade install then both V9.0.3 and V9.0.4 show up under programs and features instead of just the V9.0.4.

I should have time this weekend to investigate. What do I need to do to produce a log to investigate this issue?

This second problem is because of the approach I was taking in the early release 0.001/0.002. This will not occur in 0.003 and 1.000 and up.

k

[jusjoken]

Originally Posted by bryanzim

If I install the latest RC installer over V9.0.3 then the HD Home Run tuners work; however if I just install the RC installer then the HD home run tuners no longer work with capture device failure so it seems as if this issue is still outstanding.

On another note, if I do an upgrade install then both V9.0.3 and V9.0.4 show up under programs and features instead of just the V9.0.4.

I should have time this weekend to investigate. What do I need to do to produce a log to investigate this issue?

One other thing to try...it's just a WAG but try copying the following files from an install that worked to the V9 that is not working and see if it solves it. These would be in the SageTV\SageTV folder (the old version had them in SageTV\Common as well but I don't think they are needed there).

msvcp71.dll msvcr71.dll
msvcm80.dll msvcp80.dll msvcr80.dll

If this solves it then we need to figure out if they ALL are needed or if only the 80's or the 71's are needed.

Let me know how it goes.

k

[bryanzim]

I had the CRT libraries installed on the system anyway, so I doubted this would fix it and indeed copying the 8 or 7 CRT's to the SageTV folder had no effect.

I turned on debugging and have attached the log file which shows the capture error. Hopefully it won't be to hard to figure out.

Thanks for all your good work so far.

[jusjoken]

Would you be able to do a v9 install that works and upload the same log after a success with HDHR?

So far I am at a loss? And Jeff says there are no specific file dependencies for HDHR on windows so its not likely a missing file.

k

[bryanzim]

Originally Posted by jusjoken

Would you be able to do a v9 install that works and upload the same log after a success with HDHR?

So far I am at a loss? And Jeff says there are no specific file dependencies for HDHR on windows so its not likely a missing file.

k

Sure here is V9.03.194 which works just fine. Also the latest installer works if I install over this version but not if I uninstall old version and then install RC.

The failure difference is here

Connecting capture Filters.(@device:sw:{FD0A5AF4-B41D-11D2-9C95-00C04F7971E0}\Silicondust HDHomeRun Tuner 10011099-0), 'Silicondust HDHomeRun Tuner 10011099-0' 0
Fri 3/4 17:16:11.796 [MainMsg@b1772] try connect BDA tuner 'Silicondust HDHomeRun Tuner 10011070-0' (@device:sw:{71985F48-1CA1-11D3-9CC8-00C04F7971E0}\Silicondust HDHomeRun Tuner 10011070-0) to ATSC
Fri 3/4 17:16:11.796 [MainMsg@b1772] checking mfr vendor, '' '' (class:0, 0)
Fri 3/4 17:16:11.797 [MainMsg@b1772] Can't connect Network Provider to Tuner Filter (ATSC)
Fri 3/4 17:16:11.993 [PooledThread@15b9be5] MediaFile verification deleting segment this=MediaFile[id=6329694 A[6270179,3895843,"News4 at 5",19578@0304.17:00,60,T] mask=TV host=HT-PC encodedBy=Silicondust HDHomeRun Tuner 10011099-0 WRCDT format=MPEG2-PS 0:00:00 0 kbps [] F:\Videos\News4at5-6270179-0.mpg, Seg0[Fri 3/4 17:15:00.975-Fri 3/4 17:16:11.789], Seg1[Fri 3/4 17:16:11.790-Wed 12/31 19:00:00.000]] segfile=F:\Videos\News4at5-6270179-0.mpg
Fri 3/4 17:16:12.048 [MainMsg@b1772] try connect BDA tuner 'Silicondust HDHomeRun Tuner 10011070-1' (@device:sw:{71985F48-1CA1-11D3-9CC8-00C04F7971E0}\Silicondust HDHomeRun Tuner 10011070-1) to ATSC
Fri 3/4 17:16:12.048 [MainMsg@b1772] checking mfr vendor, '' '' (class:0, 0)
Fri 3/4 17:16:12.049 [MainMsg@b1772] Filters medium not found on filters, filter1:'' filter2:''.
Fri 3/4 17:16:12.049 [MainMsg@b1772] Tuner not sharing the same device with Capture, try next one. (ATSC) state:1 loc1:Silicondust HDHomeRun Tuner 10011070-1 loc2:Silicondust HDHomeRun Tuner 10011099-0.
Fri 3/4 17:16:12.049 [MainMsg@b1772] Didn't find TS pin in BDA tuner (ATSC).
Fri 3/4 17:16:12.049 [MainMsg@b1772] Capture filter input pin mediatype clsid ({71985F41-1CA1-11D3-9CC8-00C04F7971E0}).
Fri 3/4 17:16:12.049 [MainMsg@b1772] Can't connect Tuner to Capture Filter (ATSC).
Fri 3/4 17:16:12.299 [MainMsg@b1772] try connect BDA tuner 'Silicondust HDHomeRun Tuner 10011099-0' (@device:sw:{71985F48-1CA1-11D3-9CC8-00C04F7971E0}\Silicondust HDHomeRun Tuner 10011099-0) to ATSC
Fri 3/4 17:16:12.299 [MainMsg@b1772] checking mfr vendor, '' '' (class:0, 0)
Fri 3/4 17:16:12.299 [MainMsg@b1772] Filters medium not found on filters, filter1:'' filter2:''.
Fri 3/4 17:16:12.299 [MainMsg@b1772] Drop DBA network tuner (Source Fileter) (redundant filter).
Fri 3/4 17:16:12.300 [MainMsg@b1772] Failed to connect Splitter Filter to tuner Filter hr=0x80004005 3e0e4294 380b252c
Fri 3/4 17:16:12.300 [MainMsg@b1772] Force directly connect Splitter Filter to Capture Filter hr=0x80040204 0x3e0e4294-0x380b252c (pin:0x3a6bac9c-0x16b9eb4)
Fri 3/4 17:16:12.300 [MainMsg@b1772] Exception from line: 2609
Fri 3/4 17:16:12.300 [MainMsg@b1772] Built:sage.EncodingException: ERROR (-2,0x80040204): There was a problem using a SageTV component. Please re-install the SageTV application.

[wayner]

I just upgraded from 9.0.4.224 to 9.0.4.232 and I am having issues with JVM size.

I did the install and then the second repair install.

It now appears that the JVM size is 779. I had increased it to 1024 and the registry key still shows 1024.

Any ideas on how to fix?

[jusjoken]

Originally Posted by wayner

I just upgraded from 9.0.4.224 to 9.0.4.232 and I am having issues with JVM size.

I did the install and then the second repair install.

It now appears that the JVM size is 779. I had increased it to 1024 and the registry key still shows 1024.

Any ideas on how to fix?

A few thoughts....check the Sage exe's and ensure they are in fact 9.0.4.232

Check the permissions on the Frey entry in the registry...it should indicate permissions for "everyone" if the installer set it properly.

Try manually running the Sage exe as an administrator and see if that resolves it and let me know.

k