In article <0001HW.BA2D4A770010D86F04AF8FF0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> Does knowing it works fine with preemptive threading turned on help
> any?

Yes, I assumed you had it on for the four tests and then your report would
not have made sense ... if the effect goes away with it being enabled, then
leave it on (also the switch is hidden, it will remain in effect when
restarting POV-Ray).

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Mon, 23 Dec 2002 23:40:17 +1100, Thorsten Froehlich wrote
(in message <3e070434$1@news.povray.org>):

> In article <0001HW.BA2D4A770010D86F04AF8FF0@news.povray.org> , Martin Crisp
> <Spa### [at] tesseractcomau>  wrote:
> 
>> Does knowing it works fine with preemptive threading turned on help
>> any?
> 
> Yes, I assumed you had it on for the four tests and then your report would
> not have made sense ... if the effect goes away with it being enabled, then
> leave it on (also the switch is hidden, it will remain in effect when
> restarting POV-Ray).

Sorry, I just hadn't gotten to that - you seemed unconvinced that I 
was having the problem in the first place.

Thanks for the help. 

Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

In article <1fnn944.1lvwmom1f70r48N%cassio@free.fr> , cassio@free.fr 


> I can't believe you call him mad ! If you start insulting everybody
> that is reporting a bug, then we're not finished yet. Pov-Ray 3.5
> still has problems on Mac OS 9, and I suppose you know it.

No, it is being developed and tested on Mac OS 9.2.2.  And there is a very
big difference between saying a report does not make sense and calling
someone mad!

> Btw, what does internal error -10000 means ? I got it several times
> this morning after switching to preemptive threading as you suggested
> and experiencing slowdowns similar to Martin's symptoms...

See, I frequently get bugreports in the style you are using as well. But how
am I supposed to be able to get the problem without a screenshot if you
forget to mention 90% of the important information?  If you read the error
message carefully you will notice that it nowhere says something about an
"internal error" and even tells you that you are not supposed to know and
that the error number is there for "internal reference", so you just have to
report what it says ;-)

The numbers are regular Mac OS error codes, so this one is
"errAEEventFailed", which simply means that sending an Apple Event, probably
the one to stop the render, failed for some reason.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <0001HW.BA2D4DB700119C0004AF8FF0@news.povray.org> , Martin Crisp
<spa### [at] tesseractcomau>  wrote:

>  [Thorsten: remember that
> weird 'is it pov or is it the mac' bug to do with CDs and macros in
> 3.0?]

Yes, I remember.  It turned out it was a bug in the Finder which would set
some global working directory settings made by the C library.  I think I
recall sending you an email over a year later when Apple had finally fixed
the Finder in a newer Mac OS version...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Tue, 24 Dec 2002 0:01:21 +1100, Thorsten Froehlich wrote
(in message <3e070923$1@news.povray.org>):

> In article <0001HW.BA2D4DB700119C0004AF8FF0@news.povray.org> , Martin Crisp
> <spa### [at] tesseractcomau>  wrote:
> 
>> [Thorsten: remember that
>> weird 'is it pov or is it the mac' bug to do with CDs and macros in
>> 3.0?]
> 
> Yes, I remember.  It turned out it was a bug in the Finder which 
> would set some global working directory settings made by the C 
> library.  I think I recall sending you an email over a year 
> later when Apple had finally fixed the Finder in a newer Mac OS 
> version... 

Yep. Jul 99 (bug reported) vs Jan 01 (email notification of fix).

I don't play CDs while rendering anymore, I got out of the habit 
:-)
Have Fun
Martin
-- 
Kinky:
What I do that you wouldn't
Perverted:
What you do that I wouldn't

Almost always SMASHed

Post a reply to this message

Yes, Same here, 867Mhz dual G4. OS 9.9.2 or OSX 10.2.3, Carbon Lib 1.6. 
And I'm rendering very simple scenes.
John


Dale Walsh wrote:
> Martin Crisp wrote:
> 
>> Anyone?
>>
>> I've only just downloaded it (a day or so ago), but am finding it 
>> slows down enormously (under 9.2.2 on a G4 @ 400MHz - I don't have X 
>> at all - looks to freeze, but hasn't, quite) soon after it starts 
>> rendering. [Reading the threads back to August sometime hasn't shed 
>> much light :-(]
>>
>> Maybe another question should be asked first:
>> is anyone not having lockups/slowdowns under 9.2.2?
>> [Base extensions vs all+a few 3rd party seems to make no difference]
>> TIA
> 
> 
> 
> Add me to the list, the render queue stays open and I have to quit to 
> get it to stop.  I see a lot of people have this problem but I see no 
> answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?
> 
> 
>

Post a reply to this message

rThorsten Froehlich <tho### [at] trfde> wrote:

> In article <1fnn944.1lvwmom1f70r48N%cassio@free.fr> , cassio@free.fr 

> 
> > I can't believe you call him mad ! If you start insulting everybody
> > that is reporting a bug, then we're not finished yet. Pov-Ray 3.5
> > still has problems on Mac OS 9, and I suppose you know it.
> 
> No, it is being developed and tested on Mac OS 9.2.2.  And there is a very
> big difference between saying a report does not make sense and calling
> someone mad!
> 
> > Btw, what does internal error -10000 means ? I got it several times
> > this morning after switching to preemptive threading as you suggested
> > and experiencing slowdowns similar to Martin's symptoms...
> 
> See, I frequently get bugreports in the style you are using as well. But how
> am I supposed to be able to get the problem without a screenshot if you
> forget to mention 90% of the important information?  If you read the error
> message carefully you will notice that it nowhere says something about an
> "internal error" and even tells you that you are not supposed to know and
> that the error number is there for "internal reference", so you just have to
> report what it says ;-)
> 
> The numbers are regular Mac OS error codes, so this one is
> "errAEEventFailed", which simply means that sending an Apple Event, probably
> the one to stop the render, failed for some reason.
> 
>     Thorsten
> 
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trfde
> 
> Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Tue, 24 Dec 2002 2:46:09 +1100, John Dribus wrote
(in message <3E0### [at] earthlinknet>):

[top-post moved]

> Dale Walsh wrote:

[snip me]

>> 
>> Add me to the list, the render queue stays open and I have to quit to 
>> get it to stop.  I see a lot of people have this problem but I see no 
>> answers?  G4, OS 9.2.2, Carbon Lib 1.6; all the same systems?

> Yes, Same here, 867Mhz dual G4. OS 9.9.2 or OSX 10.2.3, Carbon Lib 1.6. 
> And I'm rendering very simple scenes.
> John

Thorsten's advice cured my symptoms:
<paste>
> If you really want, you can force the rendering into the background using
> this hidden option:
> 
> You can control if preemptive threading or cooperative threading is used.
> By default cooperative threading will be used.  In order to change this
> setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
> Now hold down the "option" key* and switch back to the General pane.  Now
> you should see another checkbox:  The checkbox for preemptive threading
> which will only take effect after you restart POV-Ray!
</paste>

Have Fun
Martin
-- 
aa #(2^8)*(2^3-2^0)
[...]Et sepultus resurrexit; certum est, quia impossibile.
-- Tertullian

Almost always SMASHed

PGP Key (ID 0xED55A6D0) Fingerprint:
A7C7 F865 B317 ABBB B10E  D8AC F4AD 347D ED55 A6D0

Post a reply to this message

Thorsten Froehlich wrote:

>
> If you really want, you can force the rendering into the background using
> this hidden option:
>
> You can control if preemptive threading or cooperative threading is used.
> By default cooperative threading will be used.  In order to change this
> setting go the the POV-Ray preferences dialog.  Switch to the Editor pane.
> Now hold down the "option" key* and switch back to the General pane.  Now
> you should see another checkbox:  The checkbox for preemptive threading
> which will only take effect after you restart POV-Ray!

This tip solved a lot of the problems I've had. Finally I can use 3.5 on my
laptop. Thank you! :-)

Tom

Post a reply to this message

In article <0001HW.BA2B9D9300039FDC0F42B1F0@news.povray.org> , Martin Crisp
<Spa### [at] tesseractcomau>  wrote:

> Anyone?

Get the POV-Ray 3.5.1 Public Release Candidate 1 (expires March 25th) from
<http://mac.povray.org/download/macosx102.html>

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message