when did duty-cycle make its appearence in the 3.5 windows interface?

--
#macro G(D,E,F)#local I=array[3]{D,E,F}#local B=0;triangle{#while(
B<3)#while(I[B])A[mod(I[B],10)]+#local I[B]=div(I[B],10);#end<-5,-
2,9>#local B=B+1;#end}#end #local A=array[7]{x,x*2,x*4,y,y*2,y*4,z
}light_source{-x*6-z*9,1}mesh{G(105,10,146)G(105,246,10)G(105,56,
146)G(105,1256,246)G(1256,126,220)G(22156,2216,201)pigment{rgb 1}}//TM

Post a reply to this message

On Mon, 13 May 2002 12:08:41 +0100, "Tom Melly" <tom### [at] tomandlucouk> wrote:
> when did duty-cycle make its appearence in the 3.5 windows interface?

according to http://www.povray.org/binaries/windows/changes.txt
it was Change 1419 inf 3.5.beta.13

ABX

Post a reply to this message

news:bt7vduch0g2o1ipot50lki4dockmkn6rei@4ax.com...
> On Mon, 13 May 2002 12:08:41 +0100, "Tom Melly" <tom### [at] tomandlucouk> wrote:
> > when did duty-cycle make its appearence in the 3.5 windows interface?
>
> according to http://www.povray.org/binaries/windows/changes.txt
> it was Change 1419 inf 3.5.beta.13
>

Silly me - should have thought of checking that. Had anyone run into problems
with laptops and POV, or was it a "better safe than sorry" feature?

Post a reply to this message

On Mon, 13 May 2002 12:08:41 +0100 Tom Melly wrote:

>when did duty-cycle make its appearence in the 3.5 windows interface?

  Tom, you can read Chris Cason's 03-May-2002 post, Message-ID
<3cd37738@news.povray.org>, and followup messages in this group.

-- 
Alan
ako### [at] povrayorg
a k o n g <at> p o v r a y <dot> o r g

Post a reply to this message

"Tom Melly" <tom### [at] tomandlucouk> wrote in message
news:3cdfa149$1@news.povray.org...
> Had anyone run into problems
> with laptops and POV, or was it a "better safe than sorry" feature?

I've been using a DELL notebook exclusively for the past year. I had only
tried using Duty Cycle a couple of times and I think it would need to be
under 50% if my fan (or fans, the Inspiron 8000 has two) failed while I'm
away and unable to shut it down. Thing is, I use a fan control utility to
run the fans, better than the BIOS seems capable of doing by itself, so
overheating isn't a problem anyway.
Without intervention of any kind the temperature goes real high and I could
see Duty Cycle being of good use if no manual fan control was available. I
went with 90% before just to see how it would go but that's too short a
pause, 70 to 80% is probably needed for good overheating prevention. Until I
had the fan control this notebook was blistering hot and DELL had the
setting of the secondary fan at so high a temp it never did turn on. Last
summer, with typically 75 to 80 F indoors, the underside of this notebook
was unbearably hot even without POV running. I had several BSOD's in Windows
possibly from simply running too hot. It was said the second fan could spin
when the CPU reached something like 80 or 90 C, hence the reason a couple
Inspiron owners created fan control utilities and made them freely available
to all. In fact, I only recall of one person in Australia during their
summertime saying they had both fans going at some point. Others supposedly
had melting plastic because the 2nd fan wasn't ever on.

I haven't put Duty Cycle to any ultimate test but I can guess it should
certainly help prevent system lockups for the average notebook/laptop, esp.
the faster CPU's now that they are in the GHz range and I suppose must also
be difficult to cool.

bob h

Post a reply to this message