Problem with Command line option in RC3 (Message 1 to 6 of 6)
From: MAJ Veld
Subject: Problem with Command line option in RC3
Date: 3 May 2002 03:29:29
Message: <3cd23c59$1@news.povray.org>
Since RC3 I'm having a problem using the +o=d:\temp\ directive for
sending my output to this directory. (This directory exists, so this
might not be the source of all trouble...)
Setting Output_File_Name=D:\temp\ in the POVRAY.INI file also doesn't
help.
The output is written automatically to the directory where the input
file is. Is this a bug and are more people experiencing this problem?
Martijn Veld
A rather unexperienced POVRAY-fan.
From: Ari-Matti Leppanen
Subject: Re: Problem with Command line option in RC3
Date: 3 May 2002 05:22:10
Message: <3cd256c2$1@news.povray.org>
"MAJ Veld" <MAJ### [at] hotmailcom> wrote in message
news:3cd23c59$1@news.povray.org...
: Since RC3 I'm having a problem using the +o=d:\temp\ directive for
sending
: my output to this directory.
: Setting Output_File_Name=D:\temp\ in the POVRAY.INI file also doesn't
help.
Confirmed with RC3.icl in WinXP
Ari-Matti
From: MAJ Veld
Subject: Re: Problem with Command line option in RC3
Date: 3 May 2002 06:09:20
Message: <3cd261d0$1@news.povray.org>
Hello,
Confirmed with RC3.icl in WinXP
>> Well I'm using Windows 98 (4.10.2222A) (I should have mentioned it in my
first message) and I am experiencing this problem. So maybe it isn't a
problem in WinXP only.
Martijn Veld
My system: P II 333, 128 MB RAM
From: Ari-Matti Leppanen
Subject: Re: Problem with Command line option in RC3
Date: 3 May 2002 07:57:44
Message: <3cd27b38$1@news.povray.org>
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3cd273d2$1@news.povray.org...
: What error message do you get?
None. The previous versions always asked at the first run, if writing to
another directory was to be allowed. Now even turning I/O restrictions
off doesn't help.
In the Message dialog under Output Options it says "Output file:
what_ever.bmp" while with the previous rc it says "Output file:
d:\images\what_ever.bmp" with the same ini-file.
Ari-Matti