I'm having some problems setting the I/O permissions under pov 3.5 for
windows using XP Pro.  I've read section devoted to it in the documentation
and have set my permissions according to what/where I'd like Pov to write:

PVENGINE.INI=
[Permitted Input Paths]
1=%INSTALLDIR%
2=F:\WINDOWS\Fonts
3=F:\Documents and Settings\jgentry\My Documents\povfiles
4=F:\Documents and Settings\jgentry\My Documents\povfiles\include

[Permitted Output Paths]
1=%INSTALLDIR%\Renderer\ReRun
2=%INSTALLDIR%\Insert Menu
3=F:\Documents and Settings\jgentry\My Documents\povfiles

POVRAY.INI=
Library_Path=F:\Program Files\POV-Ray for Windows v3.5\INCLUDE
Library_Path=F:\WINDOWS\Fonts
Library_Path=F:\Documents and Settings\jgentry\My Documents\povfiles
Library_Path=F:\Documents and Settings\jgentry\My Documents\povfiles\include
;
;
+FN
+OF:\Documents and Settings\jgentry\My Documents\povfiles\

--

I've never run into these problems under Linux and I'm wondering what I'm
doing wrong as far as setting my permissions.

--

Here is the error I get when trying to render a scene with these
permissions:

I/O restriction prohibits write access to 'F:\' for 'Documents.png'.

Press OK to grant.... etc.

--

It seems that Pov is not reading past the spaces in the path names.  If this
is so, how do I fix this?

Have I misinterpreted something in the documentation and have not set my
permissions correctly?

Help would be most appreciated.

Post a reply to this message

In article <3e26e82f@news.povray.org> , "earthdog" 
<ear### [at] NOSPAMevil3dnet> wrote:

> +OF:\Documents and Settings\jgentry\My Documents\povfiles\

> I/O restriction prohibits write access to 'F:\' for 'Documents.png'.

These two lines give a clue:  You should look at the output options POV-Ray
shows where it actually wants to write the file to.  Given that the file
name POV-Ray want to write is "Documents", it suggests the missing quotation
marks around the output file specification are the cause.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3e2704c6@news.povray.org...
> In article <3e26e82f@news.povray.org> , "earthdog"
> <ear### [at] NOSPAMevil3dnet> wrote:
>
> > +OF:\Documents and Settings\jgentry\My Documents\povfiles\
>
> > I/O restriction prohibits write access to 'F:\' for 'Documents.png'.
>
> These two lines give a clue:  You should look at the output options
POV-Ray
> shows where it actually wants to write the file to.  Given that the file
> name POV-Ray want to write is "Documents", it suggests the missing
quotation
> marks around the output file specification are the cause.

This is interesting. It's apparently not something that can be done. I went
to check on this since I couldn't remember setting the output to a directory
(folder) having a space in the name. It didn't work for me either. I tried a
more ordinary, non-system folder. Used quotes too, in the pvengine.ini and
command line.

I was going to reply here only to say it might be something to do with
Windows having the My Documents located on a drive other than C: is Windows
itself is on C: and not F:.

That Documents.png is taken from the F:\Documents and Settings pathname,
since only that is valid, dropping the rest.

I really thought I had output renders to such folders before so I'm a little
surprised to see it can't be done. Well, I can't prove it can't be, what I
mean is that I've also tried it now and find the same thing happening.

Was that capability left out? I saw that Chris Cason is away for now and he
might have been the person to answer this Windows question.

Post a reply to this message

In article <3e2727b1@news.povray.org> , "hughes, b." <omn### [at] charternet>
wrote:

> This is interesting. It's apparently not something that can be done.

Of course it can, and is the only way in fact.  What problem are you seeing
when putting quotes around the path?

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3e273be4@news.povray.org...
>
> Of course it can, and is the only way in fact.  What problem are you
seeing
> when putting quotes around the path?

This message is shown when using +O"c:\image files\test.png" in the P.-R.
for W. (XP) command line field. Just to check other ways I put quotes around
only the 'image files' part too with same result.


Possible Command Line Error:  File name or path parameter expected for
switch 'o', found 'c:\image'.
Command Line Error: Problem with command line or INI file.


And I also tried it with double backslashes. Same, except then it is
c:\\image for the output path and file name.

I'm out of ideas.

Post a reply to this message

Thorsten,

Right after replying I thought I should also check the INI way of doing this
too, just in case that also didn't work.  And it's okay, no problem with
using simply Output_File_Name=C:\image files\ without quotes or double
backslashes, as usual.

Same goes for the Documents and Settings path, just to be 100% certain. As
long as it is done through a INI all is fine. So there must be something
inoperative with the command line and paths with spaces. And not only the
path but also the file name itself cannot have a space in it either.

But now I wonder if it is only since this version of POV I have (IYKWIM). Or
if platform universatility has always kept it like this. My memory is
totally lacking here, I just know I use spaces a lot these days, and since I
use the command line switches enough too I would have noticed it before (or
so I think).

Bob

Post a reply to this message

In article <3e274fa4@news.povray.org> , "hughes, b." <omn### [at] charternet>
wrote:

> Right after replying I thought I should also check the INI way of doing this
> too, just in case that also didn't work.  And it's okay, no problem with
> using simply Output_File_Name=C:\image files\ without quotes or double
> backslashes, as usual.

This is in no way officially supported in POV-Ray also it has indeed always
worked.  Quotes are mandatory when specifying paths with spaces in POV-Ray
3.5 and in previous versions there was no official support for spaces in
paths or filenames.  That said, it does indeed still work for INI files, and
only INI files, but it simply cannot work for the command line because there
is no way of knowing where a command line option starts and a path ends if
the path contains spaces.

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3e2749e6$1@news.povray.org> , "hughes, b." 
<omn### [at] charternet> wrote:

> Possible Command Line Error:  File name or path parameter expected for
> switch 'o', found 'c:\image'.
> Command Line Error: Problem with command line or INI file.
>
>
> And I also tried it with double backslashes. Same, except then it is
> c:\\image for the output path and file name.
>
> I'm out of ideas.

Report it in p.windows.


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message