POV-Ray : Newsgroups : povray.beta-test : Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits] Server Time
25 Dec 2024 20:37:26 EST (-0500)
  Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits] (Message 1 to 5 of 5)  
From: RipClaw
Subject: Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits]
Date: 24 Feb 2008 04:30:01
Message: <web.47c138ab4de4c13375ffb0220@news.povray.org>
Hi Folks,

I've been trying to run the 3.7 beta on my machine, but I am yet to be
successful.

This is how I tried to install
1> Install 3.6
2> Download 3.7 beta
3> Overwrite 3.6 \bin files with 3.7 beta

Basically, when I double click pvengine.exe, nothing happens!! It does not say
any error message too.

I used the straceNtX to trace what is happening.
This is what I see
/------------------------------------------------------------------\
IntellectualHeaven (R) System Call Tracer for NT, 2K, XP, 2K3.
Copyright (C) Pankaj Garg. All rights reserved.

Tracing command: ["D:\bin\appz\video\POV-Ray for Windows
v3.6.1.a\bin\pvengine.exe"]
Exception = c0000005, Address = 7c918fea (first-chance!)
Exception = c0000005, Address = 5b006f55 (first-chance!)
Exception = c0000005, Address = 5b006f55 (first-chance!)
Exception = c0000005, Address = 5b006f55 (first-chance!)
Exception = c0000005, Address = 5b006f55 (first-chance!)
...... The same thing a million times ....
\------------------------------------------------------------------/

Povray 3.6.1.a, 3.6.1.c etc work without any problems !!!
The CPUs are dual Athlon MP 2800+  and OS = Windows XP

Am I doing something wrong somewhere or does Povray need dotnet runtime or
something ??


Post a reply to this message

From: Thomas de Groot
Subject: Re: Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits]
Date: 24 Feb 2008 09:51:34
Message: <47c18476$1@news.povray.org>
"RipClaw" <nomail@nomail> schreef in bericht 
news:web.47c138ab4de4c13375ffb0220@news.povray.org...
> Hi Folks,
>
> I've been trying to run the 3.7 beta on my machine, but I am yet to be
> successful.
>
> This is how I tried to install
> 1> Install 3.6
> 2> Download 3.7 beta
> 3> Overwrite 3.6 \bin files with 3.7 beta
>

Don't overwrite 3.6 files!
Just download the beta files into a folder alongside the 3.6 one. The beta 
will automatically look if and where the 3.6 version is residing. just start 
one of the beta exe's.

Thomas


Post a reply to this message

From: Nicolas Alvarez
Subject: Re: Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits]
Date: 24 Feb 2008 10:59:37
Message: <47c19469@news.povray.org>

> does Povray need dotnet runtime or something ??

Hell no!


Post a reply to this message

From: Alain
Subject: Re: Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits]
Date: 24 Feb 2008 13:10:31
Message: <47c1b317$1@news.povray.org>
RipClaw nous apporta ses lumieres en ce 2008/02/24 04:29:
> Hi Folks,
> 
> I've been trying to run the 3.7 beta on my machine, but I am yet to be
> successful.
> 
> This is how I tried to install
> 1> Install 3.6
> 2> Download 3.7 beta
> 3> Overwrite 3.6 \bin files with 3.7 beta
> 

> 
> Am I doing something wrong somewhere or does Povray need dotnet runtime or
> something ??
> 
> 
> 
Something wrong? Yes. You overwrite the 3.6 files.
Create an other folder. It can reside as a subfolder in the bin folder, or be a 
"bin_beta" folder beside the original bin.
Now, start the beta from that new folder. I have a shortcut to the 3.6.1 and one 
to the 3.7beta.

Need some external runtimes libraries? NO! Not at all!

-- 
Alain
-------------------------------------------------
A Bill of Rights is what the people are entitled to against every
government, and what no just government should refuse, or rest on inference.
Thomas Jefferson


Post a reply to this message

From: Chris Cason
Subject: Re: Unable to run Povray 3.7 on WinXP, Dual Athlon MP cpus [Silently exits]
Date: 27 Feb 2008 06:45:22
Message: <47c54d52$1@news.povray.org>
If you still are having problems with this please be sure to let me know. I
don't like it when stuff like this happens ;-(

One thing: if it's still not working, could you please advise if you have a
Logitech webcam installed? I recall a beta-tester in the past had a problem
that appeared identical to this and I tracked it down to a DLL that
Logitech inject into the address space of most Windows processes.

-- Chris


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.