Windows Installer

[uberpixel]

I recently decided to install SageTV 9.1.8 (upgraded from fresh v7 install) on a fresh Windows 10 Pro install. I attempted to copy my old 9.1.7 Wiz.bin from the old WHS 2011 install and found that it didn't work on the new Win10 install with 9.1.8. I believe that since the Wiz.bin came from an older version of v9, the new version was unhappy and caused the Wiz.bin to become corrupt.

Fortunately I still had my old WHS 2011 OS on a cloned drive and simply booted that OS, upgraded from 9.1.7 to 9.1.8 and then copied the resulting Wiz.bin to the new Win10 9.1.8 install with no issues.

Over Thanksgiving weeekend I upgraded my system from WHS 2011 to Windows 10 Pro. The main reason was that Crashplan has decided to discontinue their general consumer cloud service and I wanted to move to Backblaze. Only problem is Backblaze wanted me to pay for an enterprise level of service since I was using WHS 2011... Plus client backup stopped working for me on WHS and there really wasn't any reason to keep using it.

I run this machine for SageTV, Blue Iris and as a general file server with Drivepool for duplication.

Other than that not so small problem with the Wiz.bin, everything went very smoothly. My drivepool moved without incident and I'm now backing up to the cloud with Backblaze. Since I was starting with a fresh OS I decided to update to the latest OpenDCT, HDHomerun Driver, 32 bit Java 1.8, and Comskip Donator version. All smooth sailing.

Not sure if this is a known issue, but I wanted to mention it in case anyone is headed down this same path.

-uberpixel

[jusjoken]

Originally Posted by uberpixel

I recently decided to install SageTV 9.1.8 (upgraded from fresh v7 install) on a fresh Windows 10 Pro install. I attempted to copy my old 9.1.7 Wiz.bin from the old WHS 2011 install and found that it didn't work on the new Win10 install with 9.1.8. I believe that since the Wiz.bin came from an older version of v9, the new version was unhappy and caused the Wiz.bin to become corrupt.

Fortunately I still had my old WHS 2011 OS on a cloned drive and simply booted that OS, upgraded from 9.1.7 to 9.1.8 and then copied the resulting Wiz.bin to the new Win10 9.1.8 install with no issues.

Over Thanksgiving weeekend I upgraded my system from WHS 2011 to Windows 10 Pro. The main reason was that Crashplan has decided to discontinue their general consumer cloud service and I wanted to move to Backblaze. Only problem is Backblaze wanted me to pay for an enterprise level of service since I was using WHS 2011... Plus client backup stopped working for me on WHS and there really wasn't any reason to keep using it.

I run this machine for SageTV, Blue Iris and as a general file server with Drivepool for duplication.

Other than that not so small problem with the Wiz.bin, everything went very smoothly. My drivepool moved without incident and I'm now backing up to the cloud with Backblaze. Since I was starting with a fresh OS I decided to update to the latest OpenDCT, HDHomerun Driver, 32 bit Java 1.8, and Comskip Donator version. All smooth sailing.

Not sure if this is a known issue, but I wanted to mention it in case anyone is headed down this same path.

-uberpixel

I have to think this was coincident and not related to 9.1.7 to 9.1.8 upgrade as no database changes were made.

I am glad it worked out in the end.

k

[uberpixel]

Originally Posted by jusjoken

I have to think this was coincident and not related to 9.1.7 to 9.1.8 upgrade as no database changes were made.

I am glad it worked out in the end.

k

Okay - I thought that the Wiz.bin move was typically pretty robust so it surprised me when it went corrupt. I tried copying it a couple of times to confirm and it would mark it corrupt and start fresh each time.

I recognize that I added enough variables to the process that it's possible something else caused the issue but the fact that it worked after I upgraded my WHS 2011 to 9.1.8 and then copied that Wiz.bin to the Win10 9.18 install had me somewhat convinced that it wasn't just coincidence.

-uberpixel

[wnjj]

Any version can read any older version of wiz.bin just fine so that wasn't what caused the corruption. It also hasn't changed format in over a year. Something else went funny there. Did you start up and the shut down the V9 install before copying the wiz.bin into it? Was the system you copied it from actively running SageTV? Wiz.bin gets written a lot when it's running.

Regardless, it's always been a good idea to have regular backups of wiz.bin. Mine gets backed up weekly.

[TwistedMelon]

Is the current installer supposed to be able to identify an existing Windows SageTV installation and its current folder?

I last installed 9.1.5 over top of 7.x in the summer and it went without a hitch, but I can't remember if I had to point it at the existing folder.

I just launched 9.1.8 installer (Windows 7) and it wanted to install to Program Files x86. I pointed it to the correct folder on the root of the drive and it went through its install without a hiccup.

After relaunching SageTV however, the current version in System Information is still reported as 9.1.5.

[Tiki]

No, the current installer makes no attempt to locate a previous installation. It will install to the default location unless you specify a custom location.

[waylo]

Originally Posted by TwistedMelon

Is the current installer supposed to be able to identify an existing Windows SageTV installation and its current folder?

I last installed 9.1.5 over top of 7.x in the summer and it went without a hitch, but I can't remember if I had to point it at the existing folder.

I just launched 9.1.8 installer (Windows 7) and it wanted to install to Program Files x86. I pointed it to the correct folder on the root of the drive and it went through its install without a hiccup.

After relaunching SageTV however, the current version in System Information is still reported as 9.1.5.

With Tiki's info above, @TwistedMelon, are you sure you were running the latest executable? Or the old shortcut which would link to the same old version installed?

[TwistedMelon]

Originally Posted by waylo

With Tiki's info above, @TwistedMelon, are you sure you were running the latest executable? Or the old shortcut which would link to the same old version installed?

I'm positive I was opening the only Sage binary in the install/working folder. Checking the version on that file from Explorer shows 9.1.5.

Installer downloaded from link in the OP bintray: https://bintray.com/opensagetv/saget...rWindows/9.1.8

Running the installer a second (or subsequent) time offers to repair or uninstall. Repair takes only a second and seems to make no difference.

As far as I can tell, the 9.1.8 installer hasn't done anything to any file - it's updated the registry because it knows it was previously run, but I can't find any evidence of any file updates anywhere.

EDIT:

I just ran again and chose UNINSTALL. When complete, nothing had changed, I still had al my files and shortcuts. Re-ran the installer again and this time the 9.1.5 files were overwritten with 9.1.8

[Pelicanjoe]

Try running the file as administrator, make sure your sage tv service is stopped. I've had issues with the install and these 2 steps seem to fix it.

[darrylc]

Trying a new install in a Windows 10 Pro and running into some trouble. During the install I can see the followings -

Unable to register the following:
STVEVRPrstr.dll
Mpeg2Dump.ax
MpegAudioEncoder2.ax
MpegDemux.ax
MpegMux.ax
MusicVisFilter.ax
SageTVFileSRC.ax
StrmDeMux.ax
TSSplitter.ax

Reading this thread convinced me to press ignore thinking that these were not fatal errors because of the loss of decoders in Windows 10; however, when I try to start SageTV I get the following error:

"The application was unable to start correctly"

I tried repairing the install. Any ideas on how I should proceed?

[Tiki]

Originally Posted by darrylc

Trying a new install in a Windows 10 Pro and running into some trouble. During the install I can see the followings -

Unable to register the following:
STVEVRPrstr.dll
Mpeg2Dump.ax
MpegAudioEncoder2.ax
MpegDemux.ax
MpegMux.ax
MusicVisFilter.ax
SageTVFileSRC.ax
StrmDeMux.ax
TSSplitter.ax

Reading this thread convinced me to press ignore thinking that these were not fatal errors because of the loss of decoders in Windows 10; however, when I try to start SageTV I get the following error:

"The application was unable to start correctly"

I tried repairing the install. Any ideas on how I should proceed?

When you ran the installer did you just double-click it, or did you right-click and choose “run as administrator “? Many programs fail to install correctly if you don’t choose to run as administrator (even if you are logged in with an administrator account already).

[darrylc]

Thanks for the idea. I ran as an admin but had the same result and then I noticed that the MS c++ 2015 runtime wasn't installed. Did that manually and then Sage started normally.: clap:

[jusjoken]

Downloads now available....check my signature below.....

[tvmaster2]

Originally Posted by jusjoken

Downloads now available....check my signature below.....

Thanks. What are the updates / differences, etc.?

[KryptoNyte]

Here's a link directly to the change-log;

https://github.com/google/sagetv/blo...r/CHANGELOG.md

[wnjj]

This is the file modification time issue that was fixed.

https://forums.sagetv.com/forums/showthread.php?t=65445

[Eternal]

Originally Posted by TwistedMelon

I'm positive I was opening the only Sage binary in the install/working folder. Checking the version on that file from Explorer shows 9.1.5.

Installer downloaded from link in the OP bintray: https://bintray.com/opensagetv/saget...rWindows/9.1.8

Running the installer a second (or subsequent) time offers to repair or uninstall. Repair takes only a second and seems to make no difference.

As far as I can tell, the 9.1.8 installer hasn't done anything to any file - it's updated the registry because it knows it was previously run, but I can't find any evidence of any file updates anywhere.

EDIT:

I just ran again and chose UNINSTALL. When complete, nothing had changed, I still had al my files and shortcuts. Re-ran the installer again and this time the 9.1.5 files were overwritten with 9.1.8

I mentioned this a while ago.
running the install over an existing install doesn't do anything

[jusjoken]

Originally Posted by Eternal

I mentioned this a while ago.
running the install over an existing install doesn't do anything

What previous version were you using?

Also check the folder location of the previous and new version as the installer does not "find" your previous version... if you dont use the default location then you need to change it also on an upgrade.

k

[Eternal]

default location

ive upgraded every version from the previous version; none of them installs the new files at all unless you uninstall the existing version first

[jusjoken]

Originally Posted by Eternal

default location

ive upgraded every version from the previous version; none of them installs the new files at all unless you uninstall the existing version first

What OS version? I will try to replicate but with over 800 downloads of the latest version it odd no one else is reporting this.

k