Hello,

I installed POV-Ray 3.6.0 on Windows XP, and I have the impression that 
it doesn't follow the basic guidelines for multi-user compatibility in 
WinXP, since it keeps trying to write to its installation directory. The 
resulting problems are obvious: users are forced to share their 
settings, and non-Administrators cannot even save them!

Is there a way to correct this that I have overlooked? If not, what is 
the proper way to report it to the POV-Ray developers? (The fix is 
pretty obvious: move the config files to their proper location, inside 
the user profile directory).

Thanks in advance!

-- 
   Lionel Fourquaux

Post a reply to this message

On Fri, 18 Jun 2004 20:31:40 +0200, Lionel Fourquaux
<use### [at] no-spaminvalid> wrote:
> I installed POV-Ray 3.6.0 on Windows XP, and I have the impression that 
> it doesn't follow the basic guidelines for multi-user compatibility in 
> WinXP, since it keeps trying to write to its installation directory. The 
> resulting problems are obvious: users are forced to share their 
> settings, and non-Administrators cannot even save them!

No, users are not forced. See details at,
http://www.povray.org/documentation/view/3.6.0/136/

ABX

Post a reply to this message

ABX wrote:
> No, users are not forced. See details at,
> http://www.povray.org/documentation/view/3.6.0/136/

Thanks. It's a partial solution, however, since the settings cannot be 
changed from the GUI. Moreover, I've been unable to make it work using 
an INI file in POV-Ray's current directory: according to Filemon, it 
doesn't even try to open it.

Post a reply to this message

On Fri, 18 Jun 2004 21:11:32 +0200, Lionel Fourquaux
<use### [at] no-spaminvalid> wrote:
> > No, users are not forced. See details at,
> > http://www.povray.org/documentation/view/3.6.0/136/
>
> Thanks. It's a partial solution, however, since the settings cannot be 
> changed from the GUI.

There is input for typing options below menu.
http://www.povray.org/documentation/view/3.6.0/141/

> Moreover, I've been unable to make it work using 
> an INI file in POV-Ray's current directory: according to Filemon, it 
> doesn't even try to open it.

Do you know how to set current directory for exacutables? It's in properities.
Also you can type pvengine.exe from commandline.

ABX

Post a reply to this message

ABX wrote:
> There is input for typing options below menu.
> http://www.povray.org/documentation/view/3.6.0/141/

Thanks again, but still, it's not very handy.

>>Moreover, I've been unable to make it work using 
>>an INI file in POV-Ray's current directory: according to Filemon, it 
>>doesn't even try to open it.
> 
> 
> Do you know how to set current directory for exacutables? It's in properities.

Precisely in the shortcut properties.  :)

That's what I tried. Either I made a mistake somewhere (the current 
directory, at least, is ok), or it doesn't work.

> Also you can type pvengine.exe from commandline.

I tried that, too. I can see _a lot_ of accesses 
(open/lock/read/unlock/close) to INI files in the installation 
directory, and none in the current directory.

Post a reply to this message

On Fri, 18 Jun 2004 21:45:02 +0200, Lionel Fourquaux
<use### [at] no-spaminvalid> wrote:
> I tried that, too. I can see _a lot_ of accesses 
> (open/lock/read/unlock/close) to INI files in the installation 
> directory, and none in the current directory.

I missed something. IIRC, the current directory, is that where active scene
file of active ini file is located.

ABX

Post a reply to this message

ABX wrote:
> I missed something. IIRC, the current directory, is that where active scene
> file of active ini file is located.

Now, it's my turn to say I don't understand what you mean... For me, the 
"current directory" is a parameter passed when a program is started, 
until the program changes it. E.g. if I type

cd Z:\Foo
pvengine

then the current directory should be Z:\Foo , and it looks like 
pvengine.exe doesn't try to open anything in Z:\Foo , while part 3.3.1 
of the documentation (which you pointed out) seems to say otherwise.

Post a reply to this message