POV-Ray : Newsgroups : povray.windows : "cannot open output file." : Re: "cannot open output file." Server Time
17 May 2024 04:03:26 EDT (-0400)
  Re: "cannot open output file."  
From: jm57
Date: 14 Apr 2010 13:00:01
Message: <web.4bc5f36a8295f690d1e7b1580@news.povray.org>
Alain <aze### [at] qwertyorg> wrote:

> > I am having the same problem.  When I attempt to run POV-Ray from the command
> > line the input file will open, but not the output file.
> >
> > It seems that the output file's name is being incorrectly parsed.  For example,
> > if I call pvengine.exe from "C:/Program Files/POV-Ray/bin" and my file to be
> > rendered is specified as "C:/user/file.pov", then the Messages tab shows the
> > output file name as "C:/Program Files/POV-Ray/bin/C:/user/file.pov" which cannot
> > be opened.
> >
> > Is there any way to change the output file naming?
> >
> > A related issue - I would like to store my INI file in a non-default directory.
> > I can see the path under Menu>  Renderer>  Edit Settings/Renderer but cannot
> > edit the path name.
> >
> > Any assistance would be greatly appreciated!
> > JM
> >
> >
> >
> > "Blayd"<nomail@nomail>  wrote:
> >> Hello all,
> >> Not a new user, but its been quite awhile and still a very noob learner.
> >> I just installed POV for windows 64, opened it and tried to run the first
> >> opening scenes just to see the differences in this new system as compared to my
> >> older one. I got a Parse error message saying, " Cannot open output file" I
> >> looked at the messages tab and it reads " Cannot open output file C:\Program
> >> Files\Povray For Windows v3.6\Renderer\Rerun\Current.ini to write rerun
> >> information." I looked in the rerun folder and theres no "current.ini" Should
> >> there be? Is this the problem? System is Vista 64 Home Premium SP1.
> >> Thanks in advance for any help and glad to be back!
> >
> >
> >
>
> Adding to what clipka said.
>
> Are you on Vista or Windows 7?
> If so, you can't write to ...\programm files\
> You should place your generated files in C:\user\...
>
>
> Alain


@clipka - One backslash was interpreted as an "escaper" character but a double
backslash worked perfectly.  Thanks!

@Alain - I'm using Windows XP but I made sure to avoid Program Files just in
case.


Post a reply to this message

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