Huh? Beta Test Expired Key?

[mightyt]

OK, so if I want to try this 2.1 "beta" code on a system that I used for my original 15 day trial of 2.0 which since expired, the beta will not run???

And remembering all too well, the only way around this is to reformat and reinstall OS, etc from scratch.

Why doesn't a "new" release install give you a refreshed trial period? I can deal with technical and tweaking issues, but this is probably this biggest annoyance / pain about Sage to me. Sorry, just a bit frustrated.

T.

[Opus4]

I don't know whether Frey will reset the trial period for the final release of 2.1, but this is a release candidate of beta software, not the actual final release, so it doesn't surprise me that the trial period has not been reset. Also, the Beta Software page states that it will only run with a license key, so it probably doesn't run as a trial version at all, even if you had a fresh system.

The 2.0 beta would not run w/o a license either -- there was no trial during that beta period.

- Andy

[mightyt]

Originally Posted by Opus4

I don't know whether Frey will reset the trial period for the final release of 2.1, but this is a release candidate of beta software, not the actual final release, so it doesn't surprise me that the trial period has not been reset. Also, the Beta Software page states that it will only run with a license key, so it probably doesn't run as a trial version at all, even if you had a fresh system.

The 2.0 beta would not run w/o a license either -- there was no trial during that beta period.

- Andy

I understand Andy ... I just "respectfully" disagree with this Frey policy. A new release "should" provide us with a risk free 15 days, beta or final release. I should be able to test this beta or try a new release of software without having to disable my current ability to use the existing version I paid for.

Only one mans opinion ... which I am told could spawn change ...

Thanks, T.

[kny3twalker]

they do not want new user to run a beta if they never used the software before
it could leave a bad taste in their mouth if the beta was not the most stable

I agree with this

new users can use the current release

[mightyt]

Originally Posted by kny3twalker

they do not want new user to run a beta if they never used the software before
it could leave a bad taste in their mouth if the beta was not the most stable

I agree with this

new users can use the current release

OK, I'll bite on the new user thought, then why not let registered users have a seperate key sent to them for beta? This can be done just as simple as they automated your getting your paid for key via email. There is always any way around this to make it easier for users.

Or, the software could be smart enough to allow you to install with an existing key without rendering the old version useless.

Not intending to be a pain, just trying to be open to alternate options.

EDIT: Hmm... I just had another thought that would negate your new user scenario ... If today I am a new user and I lay down my $80 for a Sage license / key, I can, "by policy", then get the beta release. So, if nothing prevents me from doing this I can still have the "bad taste" in my mouth that you mentioned. The only difference is Sage got paid, but the end result was the same. So, I am not sure that holds as much water as I first thought.

In addition, by the looks of the thread "SageTV 2.1 thoughts", this is
another reason you don't want to overlay beta on your functioning Sage because you have to use it's key.

Thanks, T.

[mightyt]

Hence ... My point ... The key does not prevent that from happening

See the newbie with RC ...

http://forums.sage.tv/forums/showpos...67&postcount=1

So, I respectfully hold my position ...

T.

[kny3twalker]

I understand that but it stops trialers from using the beat instead of the full release
most people will at least try the trial before buying
so some experience is better than none

[mightyt]

Maybe so, but I still think my other suggestions above are valid and worthy of consideration without making it open to all or impacting your new user concern.

Unfortunately it was enough to prevent me (and potentially others) from beta testing. So, I'll just have to take pleasure in viewing the new 2.1 feature list and Andy's new manual until the real deal arrives ...

In the mean time ... I'll just continue to enjoy my mlbdude / nielm 2.0 setup and hope that folks like you are able to input enough experience with 2.1 such that it will be a breeze for me.

T.

[nielm]

You cant run a 2.1 client using a 2.0 server, so you will have to install a 2.1 server on your test machine...

In which case, you should be able to use your existing 2.0 server licence on that test machine for testing purposes....

[mightyt]

Originally Posted by nielm

You cant run a 2.1 client using a 2.0 server, so you will have to install a 2.1 server on your test machine...

In which case, you should be able to use your existing 2.0 server licence on that test machine for testing purposes....

With that, can you have two systems on the same network with the same key? If not, that means to test 2.1 you would have to disable your existing functioning Sage environment ...

[nielm]

Servers dont talk to each other: just try it.. Its how I have been beta testing sage2.1

[GrayGh0st]

Originally Posted by mightyt

EDIT: Hmm... I just had another thought that would negate your new user scenario ... If today I am a new user and I lay down my $80 for a Sage license / key, I can, "by policy", then get the beta release. So, if nothing prevents me from doing this I can still have the "bad taste" in my mouth that you mentioned. The only difference is Sage got paid, but the end result was the same. So, I am not sure that holds as much water as I first thought.

Truuueeee. But most people realize that beta versions are buggy, and often, not entirely complete. If a new user, who just paid for sage decides they will test out the beta, then they are accepting this fact. They've probably (I would sincerely hope) used the stable version already as a trial - as was already mentioned - and IF they want to test beta, they would have to accept it with a grain of salt. Or simply revert back to the stable 2.0. I don't, however, know how license keys are affected by all this, as per your initial question...

Justin

[mightyt]

Originally Posted by GrayGh0st

Truuueeee. But most people realize that beta versions are buggy, and often, not entirely complete. If a new user, who just paid for sage decides they will test out the beta, then they are accepting this fact. They've probably (I would sincerely hope) used the stable version already as a trial - as was already mentioned - and IF they want to test beta, they would have to accept it with a grain of salt. Or simply revert back to the stable 2.0. I don't, however, know how license keys are affected by all this, as per your initial question...

Justin

The beta "requires" a license key, thus you have to give up your working 2.0 to test the 2.1.