How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My Documents"?

I'm setting it up on an office machine that has a morning user, but that will be
free for rendering use at night.

I don't want ANYTHING POV-Ray related in "My Documents" (I also don't wish to
set up multiple users.) Once I get it to read POVRAY.ini, I can easily do the
rest with "Library_Path".

It's an XP Pro system in case that matters.

Thanks in advance for all replies.

Best Regards,

Mike C.

Post a reply to this message

Mike the Elder wrote:
> How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My Documents"?
> 
> I'm setting it up on an office machine that has a morning user, but that will be
> free for rendering use at night.
> 
> I don't want ANYTHING POV-Ray related in "My Documents" (I also don't wish to
> set up multiple users.) Once I get it to read POVRAY.ini, I can easily do the
> rest with "Library_Path".
> 
> It's an XP Pro system in case that matters.
> 
> Thanks in advance for all replies.
> 
> Best Regards,
> 
> Mike C.
> 
  I don't know about XP or what version of POV you have. The big 
question is the povray.ini got in "My Documents". I have Win version of 
POV 3.6 and Win98 and the povray.ini is in the renderer folder. I had to 
look it up I haven't use it in a long time. I got several of those ini 
files all over the place. My version of POV has a big INI button you 
push that lets you do what ya need to with the ini files.
Have Fun!

Post a reply to this message

"Mike the Elder" <nomail@nomail> wrote:
> How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My Documents"?...

I have exactly the same question - the installer of POV-ray 3.7 (and perhaps
3.6.2 as well, I'm not sure) puts every "user editable" files into "My
Document". It seems that the %INSTALLDIR% variable is now automatically set to
c:\my documents\povray. How is it possible to override? Although during the
installation there is an option to install the program itself wherever the user
wants to, there's no possibility to change the default place of other files.

Post a reply to this message

"Mike the Elder" <nomail@nomail> wrote:
> How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My Documents"?
>
> I'm setting it up on an office machine that has a morning user, but that will be
> free for rendering use at night.
>
> I don't want ANYTHING POV-Ray related in "My Documents" (I also don't wish to
> set up multiple users.) Once I get it to read POVRAY.ini, I can easily do the
> rest with "Library_Path".
>
> It's an XP Pro system in case that matters.
>
> Thanks in advance for all replies.
>
> Best Regards,
>
> Mike C.

Chris Cason would know, but it /is/ irritating to say the least. I do miss the
good ol' days when everything was in the application directory.

It's ironic to me that INI files (INItialization files) used to be stored in
their application directory and would determine the initialization of various
app settings, and now they're scattered all around the hard disk and mapped to
some crazy registry keys in multiple places and for multiple users, so the app
has to look up the keys that tell it how to find the files that tell it how to
initialize its settings... /sigh

Post a reply to this message

On 09-Mar-11 17:10, Robert McGregor wrote:
> "Mike the Elder"<nomail@nomail>  wrote:
>> How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My Documents"?
>>
>> I'm setting it up on an office machine that has a morning user, but that will be
>> free for rendering use at night.
>>
>> I don't want ANYTHING POV-Ray related in "My Documents" (I also don't wish to
>> set up multiple users.) Once I get it to read POVRAY.ini, I can easily do the
>> rest with "Library_Path".
>>
>> It's an XP Pro system in case that matters.
>>
>> Thanks in advance for all replies.
>>
>> Best Regards,
>>
>> Mike C.
>
> Chris Cason would know, but it /is/ irritating to say the least. I do miss the
> good ol' days when everything was in the application directory.
>
> It's ironic to me that INI files (INItialization files) used to be stored in
> their application directory and would determine the initialization of various
> app settings, and now they're scattered all around the hard disk and mapped to
> some crazy registry keys in multiple places and for multiple users, so the app
> has to look up the keys that tell it how to find the files that tell it how to
> initialize its settings... /sigh
>
>
>
>
Security. Ever since Vista, the user has to have Administrative privileges to write to
the "Program Files" directory, so 
any file that might get updated during runtime has to be in a directory that the user
has write privileges for (i.e. the 
"\Documents and Settings\<username>" directory where the "My Documents" directory
resides"). It is easiest to assume 
that the user _doesn't_ have Administrative privileges to simplify the installation
process. Mr. C can elaborate.

Post a reply to this message

On 3/10/2011 12:28 PM, Tim Riley wrote:
> On 09-Mar-11 17:10, Robert McGregor wrote:
>> "Mike the Elder"<nomail@nomail> wrote:
>>> How do I tell POV-Pay to look for POVRAY.ini somewhere BESIDES "My
>>> Documents"?
>>>
>>> I'm setting it up on an office machine that has a morning user, but
>>> that will be
>>> free for rendering use at night.
>>>
>>> I don't want ANYTHING POV-Ray related in "My Documents" (I also don't
>>> wish to
>>> set up multiple users.) Once I get it to read POVRAY.ini, I can
>>> easily do the
>>> rest with "Library_Path".
>>>
>>> It's an XP Pro system in case that matters.
>>>
>>> Thanks in advance for all replies.
>>>
>>> Best Regards,
>>>
>>> Mike C.
>>
>> Chris Cason would know, but it /is/ irritating to say the least. I do
>> miss the
>> good ol' days when everything was in the application directory.
>>
>> It's ironic to me that INI files (INItialization files) used to be
>> stored in
>> their application directory and would determine the initialization of
>> various
>> app settings, and now they're scattered all around the hard disk and
>> mapped to
>> some crazy registry keys in multiple places and for multiple users, so
>> the app
>> has to look up the keys that tell it how to find the files that tell
>> it how to
>> initialize its settings... /sigh
>>
>>
>>
>>
> Security. Ever since Vista, the user has to have Administrative
> privileges to write to the "Program Files" directory, so any file that
> might get updated during runtime has to be in a directory that the user
> has write privileges for (i.e. the "\Documents and Settings\<username>"
> directory where the "My Documents" directory resides"). It is easiest to
> assume that the user _doesn't_ have Administrative privileges to
> simplify the installation process. Mr. C can elaborate.
Yeah, but then you get the "Oh, you can find an obscure setting to 
change this location, but I won't move/copy the files in the old one for 
you, so everything 100% completely breaks, the moment you actually do 
that! Isn't that so helpful!!?", issue. :p

Post a reply to this message