upgrade form 6 - 7- 9

[jerryb33]

From 6 - 7 went smooth, only had to use the license free progs as it wouldn't accept my license. Used sagetv3 and was using it this way for a week.

From 7 - 9 (9.1.2.662) it went ok as long as I used STV7. SAGETV3 with imports created havoc on the screens. Both on the client and the extenders. The detailed setup menu would write over the top of menu. It wasn't clearing the previous screen. Tried installing again and it did the same. I am using stv 7 for about a week now and getting used to it. (too many steps, but getting used to it).

Problems

I do not get comskip donator to work with 9. Is there a procedure to install this? I can't find anything on this. I have the latest from them but did not install it (don' know where to put it) the older version does not work.

Got SD for a year and set up my 4 OTA tuners (sdepg) all the same channels and my HDPVR for Directv, my computer slowed down to a crawl. I checked performance and the CPU was over 90%. Memory was also high. I had to go out and did not check again (10 hrs) it did quiet down. I put that to SD D/Ling the guide. Now my only concern on this is my Avast anti-virus is kicking in and saying my Private VPN is susceptible. Never ran anything but a plain vanilla computer, I never put this on. Is this part of SD and am I safe.

[graywolf]

For SageTV V6 UI look, install plugin Full UI => SageTV 3

Then in Detailed Setup => Advanced => Set Full UI ; go up 1 directory then into SageTV3 and choose SageTV3.xml

[KarylFStein]

Originally Posted by jerryb33

I do not get comskip donator to work with 9. Is there a procedure to install this? I can't find anything on this. I have the latest from them but did not install it (don' know where to put it) the older version does not work.

Put it wherever you like, (except in the SageTV/comskip folder or wherever the plugin places its version of comskip). Then in SageTV go to Setup > Plugins > Installed Plugins. Find and click on Commercial Detector and select Configure. There you can put the path to your comskip.exe and comskip.ini to use.

[jerryb33]

Originally Posted by jerryb33

Now my only concern on this is my Avast anti-virus is kicking in and saying my Private VPN is susceptible. Never ran anything but a plain vanilla computer, I never put this on. Is this part of SD and am I safe.

I rebooted and it is gone. Don't know where it came from.

[waynedunham]

Originally Posted by jerryb33

I rebooted and it is gone. Don't know where it came from.

I have Avast on my Android phone, but not on any of my PCs. On this machine I have Avira (no SageTV on this machine) and on the SageTV machines (I have two) I just run Microsoft Security Essentials since all those machines do is SageTV.

Anyway, on my phone from time to time (maybe once a month?) it says my internal WiFi on my Lan at the house may be suspicious and prompts me to retest it. Nothing has changed, no changes to the WiFi, nothing new connecting to it. I think it may just be Avast making you recheck every so often.

[jerryb33]

I removed Avast and tried re-install MSE. It hangs up on the definitions again. This a Vista machine. I think that was the reason I stop using it and went to Avast. I will try to look for something else as I do agree that it is creating false hits. I just went to Microsoft and support for the vista ended in April 2017. I guess I didn't remember why I put Avast on it.

[jerryb33]

Originally Posted by KarylFStein

Put it wherever you like, (except in the SageTV/comskip folder or wherever the plugin places its version of comskip). Then in SageTV go to Setup > Plugins > Installed Plugins. Find and click on Commercial Detector and select Configure. There you can put the path to your comskip.exe and comskip.ini to use.

This didn't work for me. The comskip folder in commercial detector is empty. there has to be more to it. After I configured it, the file was nowhere to be found.

[jerryb33]

Everything is up and running. After removing Avast and loading another one, comskip came to life. I will stick with stv 7. I put 9.1.2.622 on but I see 9.1.5.683 is the newest. Is there much difference between them?
Thanks for all the help.

[graywolf]

Originally Posted by jerryb33

Everything is up and running. After removing Avast and loading another one, comskip came to life. I will stick with stv 7. I put 9.1.2.622 on but I see 9.1.5.683 is the newest. Is there much difference between them?
Thanks for all the help.

You can go to the Windows Installer thread and there is a link to the Change Log to review the difference between the versions.

[Mark57]

Originally Posted by jerryb33

Everything is up and running. After removing Avast and loading another one, comskip came to life. I will stick with stv 7. I put 9.1.2.622 on but I see 9.1.5.683 is the newest. Is there much difference between them?
Thanks for all the help.

It's an easy process. I've had to temporarily disable Avast anytime I run these installs. Then I enable after and let it do it's scan.

Note, if you upgrade from a minor version to another minor version 9.x to 9.x, you must run the install a second time and select repair to make sure everything gets registered properly. This has been explained better in other places here. It works.

[jerryb33]

Originally Posted by graywolf

You can go to the Windows Installer thread and there is a link to the Change Log to review the difference between the versions.

Got them thanks

[graywolf]

Originally Posted by Mark57

It's an easy process. I've had to temporarily disable Avast anytime I run these installs. Then I enable after and let it do it's scan.

Note, if you upgrade from a minor version to another minor version 9.x to 9.x, you must run the install a second time and select repair to make sure everything gets registered properly. This has been explained better in other places here. It works.

Actually I think it would be like 9.1.4.x to 9.1.4.y that you need the 2nd run (repair) but if 9.1.4.x to 9.1.5.z you would not

[jusjoken]

Originally Posted by graywolf

Actually I think it would be like 9.1.4.x to 9.1.4.y that you need the 2nd run (repair) but if 9.1.4.x to 9.1.5.z you would not

Correct...and i think we are dropping the 4th level in the version number moving forward so this should not occur.

The other way to need a repair is if the the user has manually updated a file that the install normally handles as it will not overwrite a user modified install file except on a repair which forces this behavior. Of course files not included in the installer like wiz.bin or properties are never affected by the install. Even a repair run.

k