The title explains things well enough.

I am just wondering about one thing at the moment, and that is *which
time zone* is the POV expiration targetd for, and what time of day or
night in that time zone? I had assumed that POV would base expiration
time upon the local time of my computer, but perhaps not. At any rate,
the replacement version of POV isn't on the web site at the moment,
and I'm eager to finish something that I had started earlier today,
back when my copy of POV 3.5 still worked.

later,
Glen

Post a reply to this message

> I am just wondering about one thing at the moment, and that is *which
> time zone* is the POV expiration targetd for, and what time of day or
> night in that time zone? I had assumed that POV would base expiration
> time upon the local time of my computer, but perhaps not. At any rate,
> the replacement version of POV isn't on the web site at the moment,
> and I'm eager to finish something that I had started earlier today,
> back when my copy of POV 3.5 still worked.

Sorry, we have a hitch and won't be releasing RC3 for at least another 8
hours. Please just set your clock back, re-start POV, then set it forward
again.

-- Chris

Post a reply to this message

On Mon, 29 Apr 2002 13:58:41 +1000, "Chris Cason"
<new### [at] deletethispovrayorg> wrote:

>Sorry, we have a hitch and won't be releasing RC3 for at least another 8
>hours. Please just set your clock back, re-start POV, then set it forward
>again.
>
>-- Chris

Thanks for the suggestion, Chris. I wish you the best of luck in
resolving whatever "hitch" you might have ran into.

Post a reply to this message

As I think expiration is a good idea at beta and RC versions, but:

- expiration time should be at least two or three weeks, not one
- expriration window should be passed by an Ok button, then
    expired Pov should be used normally for some extended period

I've the same headache, because I've to finish my theses in three weeks and
I'm forced to download a 9M install each week.
No comment.

- Vic -

Post a reply to this message

"Vic" <let### [at] fwhu> wrote in message news:3cccd9ef@news.povray.org...

> I'm forced to download a 9M install each week.

Who is forcing you to do this ? Does he/she have a large stick or similar
physical inducement ?

Whoever they are, I'd like to have a strong talk with them. No-one should
be allowed to force you to download beta-quality software that you don't
want.

-- Chris

Post a reply to this message

Youre a funny guy Chris ;-) Seriously though, I think it would be a good
idea to be able to bypass the beta expiration window, after the user has
been warned.

George



> - expriration window should be passed by an Ok button, then
    expired Pov should be used normally for some extended period

"Chris Cason" <new### [at] deletethispovrayorg> wrote in message
news:3cccdb60@news.povray.org...
> "Vic" <let### [at] fwhu> wrote in message news:3cccd9ef@news.povray.org...
>
> > I'm forced to download a 9M install each week.
>
> Who is forcing you to do this ? Does he/she have a large stick or similar
> physical inducement ?
>
> Whoever they are, I'd like to have a strong talk with them. No-one should
> be allowed to force you to download beta-quality software that you don't
> want.
>
> -- Chris
>
>
>

Post a reply to this message

"George Pantazopoulos" <the### [at] attbicom> wrote in message
news:3cccdd60$1@news.povray.org...
> Youre a funny guy Chris ;-) Seriously though, I think it would be a good
> idea to be able to bypass the beta expiration window, after the user has
> been warned.

These betas aren't supposed to even exist after expiring though. What other
solution is there? By putting a message saying turn your PC's clock back?
Seems a bit ridiculous, especially since the arguable point here is that
this is only a beta. There shouldn't be any serious activity considered with
a beta program other than testing. I'm probably echoing that sentiment and
all this has probably been said before.

bob h

Post a reply to this message

On Mon, 29 Apr 2002 01:26:32 -0500, "bob h" <omn### [at] charternet> wrote:
> There shouldn't be any serious activity considered with
> a beta program other than testing.

I agree with You however not everyone has resources for just testing when
crash appear in the middle of one day long render (developing short example
script could take months). It is good to test 3.5 with "real" productions.
Just user should be prepared and have alternate solution in case beta expire
or crash. Betatesting is not for dummies ;-)

ABX

Post a reply to this message

"Vic" <let### [at] fwhu> wrote in message news:3cccd9ef@news.povray.org...
> As I think expiration is a good idea at beta and RC versions, but:
>
> - expiration time should be at least two or three weeks, not one
> - expriration window should be passed by an Ok button, then
>     expired Pov should be used normally for some extended period
>
> I've the same headache, because I've to finish my theses in three weeks and
> I'm forced to download a 9M install each week.
> No comment.
>

You could just d/l the VC++ compile - much smaller (.exe only, so don't delete
your old installation).

Post a reply to this message

"bob h" <omn### [at] charternet> wrote in message
news:3ccce7a8@news.povray.org...
> "George Pantazopoulos" <the### [at] attbicom> wrote in message

> There shouldn't be any serious activity considered with
> a beta program other than testing.

Define "serious", define "shouldn't" ;)

Post a reply to this message