Finally Upgrading Sage

[acrowe]

Long time no post...

I've been running sage 5.0.4 for the past couple (few?) years. Lots of life stuff happened (2 kids, 4 moves, etc...) so I wasn't able to keep up to date. But I'm now getting a (little) bit more time and Sage is calling my name...

So any gotchas in moving from 504 to the latest release? I'll also be jumping on the newest version of SageMC and I'm sure many other things.

So for any "old timers" who have moved from older versions to the newer ones anything to watch out for? I'll be doing the standard full safe upgrade (backup folder, etc) but wanted to see if there was anything I needed to watch out for.

I'll probably be picking up the new license on Friday and working on it over the weekend.

Thanks in advance!

[GKusnick]

Sounds like you already know about the upgrade fee if your original purchase was before V5. But just to spell it out, you don't need a new full license, just a V6 upgrade license (and you don't even need that if your original purchase was V5).

A couple of things come to mind on the technical end. There's a somewhat lengthy database conversion going from V5 to V6, so be prepared for several (possibly many) minutes of unresponsiveness the first time you fire up V6. People with enormous music libraries (tens of thousands of songs) seem to be hit the hardest by this.

Also V6.3 has UI animations enabled by default. If your machine is old and/or graphically challenged or has outdated graphics drivers, you may see some garbled menus or poor UI performance unless you turn the animations off in Detailed Setup or via the ui/animation/core_enabled property.

[jchiso]

I upgraded a version 4 system to v6 a few months ago and was amazed at how smoothly it went. I have two other v4 systems that I have not upgraded because I prefer the v4 GUI and there does not see a comparable v6 .stv.

[Boolah]

I actually upgraded from v2.2.8 to v6.3.5 this weekend. As GKusnick mentioned, there was approximately a 10-15 minute wait when first starting the new version of Sage while it migrated the DB.

I uninstalled v2.2.8 before I installed v6.3.5, but the uninstall left my wiz.bin, sage.properties and a few other files in the old "Frey Technologies" directory. When I installed the new version of Sage, it installed into the "SageTV" directory rather than the old "Frey Technologies" directory, but the sage.properties file in the new SageTV directory referenced the wiz.bin (and a few other files) in the "Frey Technologies" directory, even though I had copied those files into the SageTV directory. Since I never upgraded to version 5, I don't know if Sage uses the "Frey Technologies" directory or the "SageTV" directory in v5, but you might want to check the references for accuracy in your .properties file before you fire up your new install of Sage for the first time.

Other than that, the upgrade went smoothly.

[mickm]

Planning on moving from v4 to the latest v6.x this evening (HD extender on the way!).

I've just purchased the upgrade license and want to take this opportunity to do a complete format of my server machine.

How does the upgrade license work on a machine that doesn't have any previous SageTV installed on it? I still have my v4 license key.

Thanks,
Mick

[GKusnick]

Originally Posted by mickm

How does the upgrade license work on a machine that doesn't have any previous SageTV installed on it? I still have my v4 license key.

You'll have to enter both keys (the original key and the upgrade key) the first time you run Sage after reinstalling.

[mickm]

Much appreciated! Can begin the formatting now...