POV-Ray : Newsgroups : povray.bugreports : Failed to start render: Failed to parse INI file Server Time
15 Apr 2024 12:43:21 EDT (-0400)
  Failed to start render: Failed to parse INI file (Message 1 to 7 of 7)  
From: jartim
Subject: Failed to start render: Failed to parse INI file
Date: 26 May 2010 07:30:01
Message: <web.4bfd04c2737e13da2d9cc77a0@news.povray.org>
I have POV 3.7.0.beta.37a.msvc9-sse2.win32 installed on my PC.
Due to our network system, my 'My Documents' folder is mapped to a network
server '\\mcm3kerp\home\jartim'.
When I try to render a scene I get the following error -

Cannot open INI file '\\mcm3kerp\home\jartim\POV-Ray\v3.7\ini\povray.ini'
Failed to start render: Failed to parse INI file.

I can edit the povray ini file from the 'Tools\Edit Master POVRAY.INI' menu, so
I don't think it is not a file security problem.


Post a reply to this message

From: clipka
Subject: Re: Failed to start render: Failed to parse INI file
Date: 26 May 2010 09:36:00
Message: <4bfd23c0$1@news.povray.org>
Am 26.05.2010 13:26, schrieb jartim:
> I have POV 3.7.0.beta.37a.msvc9-sse2.win32 installed on my PC.
> Due to our network system, my 'My Documents' folder is mapped to a network
> server '\\mcm3kerp\home\jartim'.
> When I try to render a scene I get the following error -
>
> Cannot open INI file '\\mcm3kerp\home\jartim\POV-Ray\v3.7\ini\povray.ini'
> Failed to start render: Failed to parse INI file.
>
> I can edit the povray ini file from the 'Tools\Edit Master POVRAY.INI' menu, so
> I don't think it is not a file security problem.

Sounds familiar - I guess it is a variation of known bug FS#107 
(<http://bugs.povray.org/task/107>); a fix for that exists and will be 
included in the next beta release.

Until then you'll probably have to work around by copying the files to a 
local directory and rendering from there.


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Failed to start render: Failed to parse INI file
Date: 26 May 2010 12:44:50
Message: <4bfd5002$1@news.povray.org>
On 26.05.10 15:35, clipka wrote:
> Sounds familiar - I guess it is a variation of known bug FS#107
> (<http://bugs.povray.org/task/107>); a fix for that exists and will be
> included in the next beta release.
>
> Until then you'll probably have to work around by copying the files to a
> local directory and rendering from there.

Actually, mapping the network share to a drive letter is sufficient.

Interesting enough, there are lots of programs out there that cannot deal 
with network share paths in Windows ... so at least we are not alone with 
this (already fixed) bug.

	Thorsten


Post a reply to this message

From: jartim
Subject: Re: Failed to start render: Failed to parse INI file
Date: 1 Jun 2010 04:30:00
Message: <web.4c04c497840c44922d9cc77a0@news.povray.org>
Thorsten Froehlich <tho### [at] trfde> wrote:
> On 26.05.10 15:35, clipka wrote:
> > Sounds familiar - I guess it is a variation of known bug FS#107
> > (<http://bugs.povray.org/task/107>); a fix for that exists and will be
> > included in the next beta release.
> >
> > Until then you'll probably have to work around by copying the files to a
> > local directory and rendering from there.
>
> Actually, mapping the network share to a drive letter is sufficient.
>
> Interesting enough, there are lots of programs out there that cannot deal
> with network share paths in Windows ... so at least we are not alone with
> this (already fixed) bug.
>
>  Thorsten

Thanks for the help, but I still have the problem.
I tried changing the povray.ini location by mapping it to a drive and setting
the POVINI environment variable to point to it - set POVINI =
H:\POV-Ray\v3.7\ini\povray.ini

This still makes no difference, in fact no matter what I set POVINI to point to
I still get the same error! I have tried pointing to local folders on drive C
and remote folders on drive H.


Post a reply to this message

From: Rob
Subject: Re: Failed to start render: Failed to parse INI file
Date: 17 Mar 2024 06:05:00
Message: <web.65f6bf9d840c449247f01b1d796430ab@news.povray.org>
"jartim" <tim### [at] yahoocom> wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
> > On 26.05.10 15:35, clipka wrote:
> > > Sounds familiar - I guess it is a variation of known bug FS#107
> > > (<http://bugs.povray.org/task/107>); a fix for that exists and will be
> > > included in the next beta release.
> > >
> > > Until then you'll probably have to work around by copying the files to a
> > > local directory and rendering from there.
> >
> > Actually, mapping the network share to a drive letter is sufficient.
> >
> > Interesting enough, there are lots of programs out there that cannot deal
> > with network share paths in Windows ... so at least we are not alone with
> > this (already fixed) bug.
> >
> >  Thorsten
>
> Thanks for the help, but I still have the problem.
> I tried changing the povray.ini location by mapping it to a drive and setting
> the POVINI environment variable to point to it - set POVINI =
> H:\POV-Ray\v3.7\ini\povray.ini
>
> This still makes no difference, in fact no matter what I set POVINI to point to
> I still get the same error! I have tried pointing to local folders on drive C
> and remote folders on drive H.

If you have changed directories like I have, you have to change the registry
too, go to the registry editor and go to
'Computer\HKEY_CURRENT_USER\Software\POV-Ray\v3.7\Windows'
There will be 'DocPath' and 'Home', change those to the path of the directory
you have installed it in


Post a reply to this message

From: jr
Subject: Re: Failed to start render: Failed to parse INI file
Date: 17 Mar 2024 11:35:00
Message: <web.65f70d0c840c44921686e436cde94f1@news.povray.org>
"Rob" <nomail@nomail> wrote:
> "jartim" <tim### [at] yahoocom> wrote:
> ...

5038 days.  a record ? :-)


regards, jr.


Post a reply to this message

From: Mr
Subject: Re: Failed to start render: Failed to parse INI file
Date: 18 Mar 2024 04:35:00
Message: <web.65f7fb8d840c449216086ed06830a892@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> "Rob" <nomail@nomail> wrote:
> > "jartim" <tim### [at] yahoocom> wrote:
> > ...
>
> 5038 days.  a record ? :-)
>
>
> regards, jr.

Still, Thanks for constructive feedback it's also good because it keeps
workarounds actualized.


Post a reply to this message

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