 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello all,
I have used POV in the past...a learner if you will, but I am now installed on a
new system, Vista 64, I installed POV for windows 64, opened it, went to run the
very first demo scene just to see how the system does compared to my old system,
and I get a Parse error, " Cannot open output file". POV installed into my
programs on my C drive in the 64 bit programs folder like it should, all
related folders appear to be there too.... not quite sure what the problem
could be, I unrestricted I/O. Anyone have some suggestions? The INI file has
the path as 1=%installedir%\Renderer\Rerun.
Thanks in advanced!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Blayd" <nomail@nomail> wrote in message
news:web.4835e34b9f9519fff51b2e730@news.povray.org...
> Hello all,
> I have used POV in the past...a learner if you will, but I am now
> installed on a
> new system, Vista 64, I installed POV for windows 64, opened it, went to
> run the
> very first demo scene just to see how the system does compared to my old
> system,
> and I get a Parse error, " Cannot open output file". POV installed into my
> programs on my C drive in the 64 bit programs folder like it should, all
> related folders appear to be there too.... not quite sure what the problem
> could be, I unrestricted I/O. Anyone have some suggestions? The INI file
> has
> the path as 1=%installedir%\Renderer\Rerun.
> Thanks in advanced!
>
I don't have Vista, but I think I've read in previous postings that there
are various problems where Vista secures bits and pieces that Windows has
never secured before.
I couldn't find the thread that I was thinking of, but I came across this
one where the last 8 responses could be of interest to you. The key seems to
be not to install it in the default location, which write protects a whole
load of things that stop POV-Ray working:
http://news.povray.org/povray.windows/thread/%3Cweb.462601924b1ad72e11d42ae90%40news.povray.org%3E/?mtop=242839&moff=20
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I couldn't find the thread that I was thinking of, but I came across this
> one where the last 8 responses could be of interest to you. The key seems
> to be not to install it in the default location, which write protects a
> whole load of things that stop POV-Ray working:
>
>
http://news.povray.org/povray.windows/thread/%3Cweb.462601924b1ad72e11d42ae90%40news.povray.org%3E/?mtop=242839&moff=20
I don't have Vista either, but I understand the problem to
be with usage of "ini" extention on files. Vista treats all
ini files in C:\program files as system only files, and
denies read and write access. This doesn't just stop
POV from working, it stops many other applications
from functioning properly. MS wants all programs to
use the registry instead of ini files, disregarding that
programs like POV wish to keep thier ini files editable
as a text file. I would think that to be on the safe side
no programs at all should be installed to C:\program files,
I think this rates right up there with clicking "start" to
access "turn off the computer". With Vista you take
the files from your programs and put them anywhere but
into "program files".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Blayd nous illumina en ce 2008-05-22 17:19 -->
> Hello all,
> I have used POV in the past...a learner if you will, but I am now installed on a
> new system, Vista 64, I installed POV for windows 64, opened it, went to run the
> very first demo scene just to see how the system does compared to my old system,
> and I get a Parse error, " Cannot open output file". POV installed into my
> programs on my C drive in the 64 bit programs folder like it should, all
> related folders appear to be there too.... not quite sure what the problem
> could be, I unrestricted I/O. Anyone have some suggestions? The INI file has
> the path as 1=%installedir%\Renderer\Rerun.
> Thanks in advanced!
>
>
>
On Vista, it _should'nt_ be installed in the programms folder, BUT into a custom
folder somewhere else. That's because the programms folder is "protected" and
you are prevented from writing there most of the time. For example, only
installers are allowed to write and modify any *.ini file.
--
Alain
-------------------------------------------------
I was making love to this girl and she started crying. I said, "Are you
going to hate yourself in the morning?" She said, "No, I hate Myself now."
Rodney Dangerfield
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
