POV-Ray : Newsgroups : povray.windows : Windows beta 39 available Server Time
3 Mar 2024 14:38:30 EST (-0500)
  Windows beta 39 available (Message 1 to 6 of 6)  
From: Chris Cason
Subject: Windows beta 39 available
Date: 16 Sep 2010 01:29:56
Message: <4c91ab54@news.povray.org>
The beta page (http://www.povray.org/beta/) now has available beta 39 of
POV-Ray for Windows. See the above link for the full list of new features
and changes. Source and Linux code will be updated as time permits.

-- Chris


Post a reply to this message

From: andreas post
Subject: Re: Windows beta 39 available
Date: 6 Oct 2010 02:10:01
Message: <web.4cac123c30543542fa5d16fc0@news.povray.org>
Hi Chris,

when will be the final version of POV-Ray v3.7 be released?
Will it be compiled with InstallShield 12?

I'm asking because, also v39 beta of v3.7 does not solve the multi-user
installation problem of POV-Ray if installed under 64bit Windows.

Warm regards, Andreas

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> The beta page (http://www.povray.org/beta/) now has available beta 39 of
> POV-Ray for Windows. See the above link for the full list of new features
> and changes. Source and Linux code will be updated as time permits.
>
> -- Chris


Post a reply to this message

From: Chris Cason
Subject: Re: Windows beta 39 available
Date: 6 Oct 2010 02:22:15
Message: <4cac1597@news.povray.org>
On 6/10/2010 17:07, andreas.post wrote:
> when will be the final version of POV-Ray v3.7 be released?

I am hoping to make it final in January 2011.

> Will it be compiled with InstallShield 12?

Not if I can help it. I have a very strong dislike for the way Acresso (or
Flexera or whatever they are calling themselves this week) treated us after
IS stopped working (they implied the software was being used illegally,
despite having been paid a significant sum of money for it). It took me
almost two weeks to get it re-enabled. As a result I now consider
dependence on IS to be a risk to the project, but have yet to find the time
to re-write the installer using another tool.

> I'm asking because, also v39 beta of v3.7 does not solve the multi-user
> installation problem of POV-Ray if installed under 64bit Windows.

If you mean that it doesn't provide multi-user advertised files, this is a
known issue. I have to decide what approach to take - an advertised MSI or
coding support into POV to clone the user-editable files upon first run.
The advertised module is the proper way to do it, but I am not sure I will
be able to find the time.

-- Chris


Post a reply to this message

From: andreas post
Subject: Re: Windows beta 39 available
Date: 13 Oct 2010 16:50:01
Message: <web.4cb61ad030543542b5dafe00@news.povray.org>
Hi Chris,

I understand your 'headache' regarding using InstallShield!

> If you mean that it doesn't provide multi-user advertised files, this is a
> known issue.

Yes, when I try to install (logined as administrator), installation fails due to
missing admin-/write-rights (because I can not run the *.msi-package by
right-click and selecting 'run as administrator'). Then I used an environment
either by starting file-explorer TotalCommander or cmd.exe by using right-click
and choosing 'run as administrator'. In this case installation does not fail,
but created links in startmenu does not work resp. are not global
(user-independent).

The general problem raised because there is a CAD-software (to design kitchen
furniture) which uses POV-Ray. In this software, the path to "pvengine64.exe"
has to be administrated global (user-independent).

If POV-Ray is installed in path "C:\program files\POV_Ray\" then the setting
"C:\program files\POV_Ray\bin\pvengine64.exe" leads to error messages when a
single user tries to use POV-Ray functionality.

In other case I installed POV-Ray v3.6.2 using the recommended path
("C:\Users\<<user-name>>\AppData\Roaming\..."). But the setting
"C:\Users\%USERNAME%\AppData\Roaming\...\bin\pvengine64.exe" or
"C:\Users\"%USERNAME%"\AppData\Roaming\...\bin\pvengine64.exe" does not work in
this software. Nevertheless the call of
"C:\Users\%USERNAME%\AppData\Roaming\...\bin\pvengine64.exe" in cmd.exe (or
TotalCommander) works fine (POV-Ray starts without error-messages).

Either I have to wait and check, what will offer final version of POV-Ray v3.7
or I have to convince Ruediger (the developer of the CAD-software) to fix the
path-setting behaviour in order to accept path-settings including environment
variables (%USERNAME%).

Warm regards, Andreas


Post a reply to this message

From: Alain
Subject: Re: Windows beta 39 available
Date: 14 Oct 2010 12:42:50
Message: <4cb7330a@news.povray.org>


> Either I have to wait and check, what will offer final version of POV-Ray v3.7
> or I have to convince Ruediger (the developer of the CAD-software) to fix the
> path-setting behaviour in order to accept path-settings including environment
> variables (%USERNAME%).
>
> Warm regards, Andreas
>
>

Here, the problem is prety obvious:
Ruediger deliberately chose to ignore the current windows 
specifications, leading to broken functionality. It's thus THER job to 
correct the problem.


Alain


Post a reply to this message

From: Christian Froeschlin
Subject: Re: Windows beta 39 available
Date: 14 Oct 2010 17:56:10
Message: <4cb77c7a@news.povray.org>
andreas.post wrote:

> If POV-Ray is installed in path "C:\program files\POV_Ray\" then the setting
> "C:\program files\POV_Ray\bin\pvengine64.exe" leads to error messages when a
> single user tries to use POV-Ray functionality.

I'm not sure this is enough but have you tried copying
the folder <installinguser>\My Documents\POV-Ray folder to
the folder <user>\My Documents\POV-Ray folder for each user
manually?


Post a reply to this message

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