Help! Upgrade questions and thoughts (great recovery tip too)

[PaulModz]

I’ve been using SageTV on 3 networked machines for well over a year with zero problems. I haven’t upgraded in 6 months, but I’m thinking about installing 2.2.8 (from 2.0.20), mainly to avoid being left behind with an antiquated release.

On the other hand, if it ain’t broke, don’t fix it! I don't think there are there any new features compelling enough to justify the risk, did I miss anything big? Should I just wait for 3.0? SageTV doesn't exist in a vacuum, and all the issues I'm facing are related to the state of other software components. I searched but couldn’t find solid answers to the following:

1. Is there an officially recommended version of the Hauppauge PVR-250 drivers for the latest release? Will the one I'm currently using NEED to be replaced? I’ve seen dozens of posts about this in the last year or two, so maybe the FAQ would be a good place to mention this, given the proliferation of Hauppauge drivers.

2. Does SageTV 2.2.8 have any problems with SP2 aside from firewall issues?

3. I’m using Media Player 9, and 10 actually broke my version (2.0.20) of Sage. Is moving to 10 forbidden, optional or required for 2.2.8?

4. Is DirectX 9.0c required, or will 9.0b work?

A tip for all you die-hard tweakers out there: I STRONGLY recommend picking up a drive imaging tool, specifically DriveImage 7 or the new Ghost 9. (Ghost 9 == DriveImage 8, Symantec bought PowerQuest) They both use Volume Shadowing which allows you to backup your C Drive without leaving Windows, though you do need to reboot to restore your boot drive.

Earlier today, just to see where I stood, I installed everything on Windows Update (tons of hotfixes, SP2, Media Player 10, DirectX 9c) which of course didn’t work. It even broke Girder somehow. After fooling with it for a half hour, I booted from the Ghost CD, restored the image I took beforehand, and was back to normal is 5 minutes (no chance I’ll miss Lost tonight!)

[stanger89]

Originally Posted by PaulModz

I’ve been using SageTV on 3 networked machines for well over a year with zero problems. I haven’t upgraded in 6 months, but I’m thinking about installing 2.2.8 (from 2.0.20), mainly to avoid being left behind with an antiquated release.

On the other hand, if it ain’t broke, don’t fix it! I don't think there are there any new features compelling enough to justify the risk, did I miss anything big? Should I just wait for 3.0? SageTV doesn't exist in a vacuum, and all the issues I'm facing are related to the state of other software components. I searched but couldn’t find solid answers to the following:

1. Is there an officially recommended version of the Hauppauge PVR-250 drivers for the latest release? Will the one I'm currently using NEED to be replaced? I’ve seen dozens of posts about this in the last year or two, so maybe the FAQ would be a good place to mention this, given the proliferation of Hauppauge drivers.

I haven't touched my drivers in a very long time. AFAIK, there's nothing in Sage forcing a specific version, so whatever you have should be fine. Othewise I think the recommendation is the latest official Hauppauge ones. But as you said, if it ain't broke...

2. Does SageTV 2.2.8 have any problems with SP2 aside from firewall issues?

It better not, I've been running both since they were available.

3. I’m using Media Player 9, and 10 actually broke my version (2.0.20) of Sage. Is moving to 10 forbidden, optional or required for 2.2.8?

It's definitely not required AFIAK, and I don't think it's forbidden.

4. Is DirectX 9.0c required, or will 9.0b work?

DX9c is require if you want to use 3D Accelleration and/or VMR9 (it comes with SP2 anyway).

A tip for all you die-hard tweakers out there: I STRONGLY recommend picking up a drive imaging tool, specifically DriveImage 7 or the new Ghost 9. (Ghost 9 == DriveImage 8, Symantec bought PowerQuest) They both use Volume Shadowing which allows you to backup your C Drive without leaving Windows, though you do need to reboot to restore your boot drive.

Symantec - for screwing up DI.

http://www.acronis.com

Very good advice though