|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have installed the POV-Ray newest version and I did this with administrator
user account. But I have my own account and when POV is started with it I get a
message error that warning me about some files not found (*.ini, ...). So I have
observed that files are into a sub folder (povray) in "My Documents" folder from
Admin account and was necessary to copy than to "My Documents" folder from my
account in order to make POV work rightly.
(Now) Is this a correct way to use POV with a machine with multi users?
TIA
p.s. sorry my bad english.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I have installed the POV-Ray newest version and I did this with administrator
> user account. But I have my own account and when POV is started with it I get a
> message error that warning me about some files not found (*.ini, ...). So I have
> observed that files are into a sub folder (povray) in "My Documents" folder from
> Admin account and was necessary to copy than to "My Documents" folder from my
> account in order to make POV work rightly.
>
> (Now) Is this a correct way to use POV with a machine with multi users?
>
> TIA
> p.s. sorry my bad english.
>
>
If you want to use POV-Ray with multiple acounts, I suggest installing
in a custom folder. That folder must NOT be "programm files", especialy
if you are on Windows Vista.
Alain
Post a reply to this message
|
|
| |
| |
|
|
From: Christian Froeschlin
Subject: Re: POV files in MyDocuments folder.
Date: 29 Jun 2009 18:10:57
Message: <4a493bf1@news.povray.org>
|
|
|
| |
| |
|
|
Micheus wrote:
> (Now) Is this a correct way to use POV with a machine with multi users?
Yes, at least for 3.7b. The installer doesn't yet have
full support for multi-user installations (which would
require to initialize the documents for each user when he
first starts the program, as many apps do). I didn't yet
try 3.6.2 if that also uses the new install mechanism.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <aze### [at] qwertyorg> wrote:
> If you want to use POV-Ray with multiple acounts, I suggest installing
> in a custom folder. That folder must NOT be "programm files", especialy
> if you are on Windows Vista.
Huh? Why's that?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christian Froeschlin <chr### [at] chrfrde> wrote:
> Yes, at least for 3.7b. The installer doesn't yet have
> full support for multi-user installations (which would
> require to initialize the documents for each user when he
> first starts the program, as many apps do). I didn't yet
> try 3.6.2 if that also uses the new install mechanism.
Christian, I think that Yes. This version is using a "msiexec" application
diferent of previos version (if I remember), although it has not been mentioned
in the "changes.txt" file.
The main programs and help are installed at any path that I want (suggested is:
<programfiles>\POV-Ray for Windows v3.62\). But, I see the others installed
files at this folders ...
\ini
\include
\Insert Menu
\scenes (POV samples - input. We can discard them)
...... like a part of the POV-Ray - not personal files - without them no user can
run POV (full).
(Maybe) Custom settings could be placed at user folders and configured like
alternative path - as used at this part of "pvengine.ini" file:
[Permitted Input Paths]
1=%INSTALLDIR%
2=%PROFILEDIR%
3=%FONTDIR%
Bye
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi there.
I've just made a clean installation of the version v3.7R6 and the problem still
is present.
Ok, I already know that 3.7 installer does not multi-user (Christian Froeschlin
told me this before), but this time, I installed the files in the same base
folder I used for 3.6 (that is working) - no privileges issue.
In the installer I have set the POV-Ray core destination to:
C:\Users\Micheus\AppData\Roaming\POV-Ray\v3.7 RC6
instead of:
C:\Program Files\POV-Ray\v3.7 RC6 (default and with privileges required)
....and the folder for Include and sample scene file, I used:
C:\Users\Micheus\Documents\POV-Ray\v3.7
instead of
C:\Users\Administrador\Documents\POV-Ray\v3.7
That is the screenshot of the message I'm getting:
http://img12.imageshack.us/img12/2601/povray37r6.png
and I still get it even I have edited the POVRAY.ini and set the library path
route (as is suggested there):
Library_Path="C:\Users\Micheus\Documents\POV-Ray\v3.7\include"
.... and yes, I read this part:
"... e.g. Windows, unless this feature is
turned off via the configuration file) will automatically append
standard locations like those mentioned above to the library
path list after reading this file ..."
but, if that comment is related to the variable in the General session of
PVENGINE.ini:
[General]
AutoAppendPaths=1 (I think that '0' would turn it off)
then I can say that the version 3.7 doesn't installed/created it (at least, yet
- the only one that search engine found was the one in v3.6 folder)
In such file (talking about what I saw in that one for v3.6), the %PROFILEDIR%
seems to be used as reference. I can check in my prompt that is:
> USERPROFILE=C:\Users\Micheus
and it's not enough that I copy that one - it doesn't work.
I also try look for any register definition, but it seems to not exist (that is
good - less restriction/dependence).
ah! I tried fix the things by using the /INSTALL parameter in the command line,
but what my surprise when it was looking for an [hard coded] path "Renderer"
that doesn't exists too:
http://img27.imageshack.us/img27/5084/povray37r6install.png
I really think that something can be done in the code in order to avoid this
issue.
I count with your comprehension.
Thanks
Micheus
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/12/2012 01:11, Micheus wrote:
> ah! I tried fix the things by using the /INSTALL parameter in the command line,
> but what my surprise when it was looking for an [hard coded] path "Renderer"
> that doesn't exists too:
> http://img27.imageshack.us/img27/5084/povray37r6install.png
>
> I really think that something can be done in the code in order to avoid this
> issue.
Thanks for this report, the issue with /INSTALL has been fixed. I
can't replicate the issue with using a non-standard documents path at
the moment, though it's possible that my codebase has an unrelated fix
that has rectified your problem.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |