I am using Povray version 3.7.0.msvc10.win64 in Windows 7 Pro SP1 64-bit.

I tried rendering a LDraw model and got this error:


Preset INI file is 'D:\GOOGLE DRIVE\WORKING\POVRAY\QUICKRES.INI', 
section is '[1600x1200, AA 0.3, Alpha]'.
Preset source file is 'D:\Google 
Drive\Working\Povray\LDraw\web_androbot.pov'.
-
Cannot open INI file 
'C:\Users\Mike-7PRO\Documents\POV-Ray\v3.7\ini\povray.ini'.
Failed to start render: Failed to parse INI file



Notably, povray.ini is missing from that location. Not sure what to do 
next to get it working. Thanks.


Mike

Post a reply to this message

I think this has to do with the user account I used to install the program.

How do I install povray on Windows 7 so that my non-admin account can 
use it? If I try to install as a regular user, then I can't install into 
Program Files. If I install as an admin, then all the support files get 
placed in the admin's Documents directory, and I am locked out.

Help!

Post a reply to this message

Am 04.02.2015 um 13:25 schrieb Mike Horvath:
> I think this has to do with the user account I used to install the program.
>
> How do I install povray on Windows 7 so that my non-admin account can
> use it? If I try to install as a regular user, then I can't install into
> Program Files. If I install as an admin, then all the support files get
> placed in the admin's Documents directory, and I am locked out.
>
> Help!

Have a look at this:

http://wiki.povray.org/content/Documentation:Windows_Section_3#The_.2FINSTALL_and_.2FQINSTALL_switches

I've never had a closer look at this option, so I must leave it up to 
you to figure out the details, but it's designed for exactly the 
situation you're describing.

Post a reply to this message

On 2/4/2015 11:09 AM, clipka wrote:
> Am 04.02.2015 um 13:25 schrieb Mike Horvath:
>> I think this has to do with the user account I used to install the
>> program.
>>
>> How do I install povray on Windows 7 so that my non-admin account can
>> use it? If I try to install as a regular user, then I can't install into
>> Program Files. If I install as an admin, then all the support files get
>> placed in the admin's Documents directory, and I am locked out.
>>
>> Help!
>
> Have a look at this:
>
>
http://wiki.povray.org/content/Documentation:Windows_Section_3#The_.2FINSTALL_and_.2FQINSTALL_switches
>
>
> I've never had a closer look at this option, so I must leave it up to
> you to figure out the details, but it's designed for exactly the
> situation you're describing.
>


This is a bad situation, period. Using the default Windows installer as 
a regular user is not some edge case that should need special configuration.


Mike

Post a reply to this message

Am 05.02.2015 um 04:10 schrieb Mike Horvath:
> On 2/4/2015 11:09 AM, clipka wrote:
>> Am 04.02.2015 um 13:25 schrieb Mike Horvath:
>>> How do I install povray on Windows 7 so that my non-admin account can
>>> use it? If I try to install as a regular user, then I can't install into
>>> Program Files. If I install as an admin, then all the support files get
>>> placed in the admin's Documents directory, and I am locked out.

> This is a bad situation, period. Using the default Windows installer as
> a regular user is not some edge case that should need special
> configuration.

Using the default Windows installer as a regular user with admin rights 
works perfectly.

Using the default Windows installer as a regular user /without/ admin 
rights does the perfectly right thing, namely installing the program for 
the user only. There is no way whatsoever to install into Program Files 
in such a case.


It's the case of using the default Windows installer as an /admin/ to 
install POV-Ray for other users that's bonkers to some degree.


The official way to do this would be for the installer to "advertise" a 
kind of 2nd-level installer, which would then be run the first time a 
user starts POV-Ray. However, this is a feature not supported by the 
install system we're using.

The unofficial way to do this would be for POV-Ray itself to 
automatically check whether it has been installed for the current user, 
and if that's not the case automatically do this 2nd level installation. 
However, this is a feature requiring extra work and testing.


At the end of the day it is a matter of priorities. You might like to 
hear that we already have plans for this somwhere in the drawer, and 
your post might make us reconsider its priority, but don't hold your breath.

Post a reply to this message