 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I posted these 2 questions in the new user area and I just spotted this
windows area. I think these questions belong here.
Ok... My old PC died a few weeks ago and I'm now up and running with Vista
on a Core 2 Duo. I had read that was the best processor for POV-Ray.
Anyways... I'm still getting stuff up and running and just hit my first
POV-Ray issue. I was about to start work on a short animation and to that
end I wanted to edit the resolution INI file. I click on tools, then click
on Edit resolution INI file, and up comes Notepad. I make a few changes as
normal and try to save the changes and all I get is a cannot create the
file error message. It simply says "Make sure that the path and file name
are correct." They are and I'm pretty sure this in a Windows Vista issue
with all its new security. I've now tried opening the file with several
other editor's and I've even now tried to edit the file in DOS mode all
with no luck.
I'm sure there has to be a simple solution to this but for the life of me I
can't figure it out at the moment.
Ok... now I'm really pulling my hair out. I just tried to get around the
INI file problem by putting in all the setting on the commend line.
POV-Ray works fine when I pick one of the options from the INI file and
don't use any command line options. However, I'm now trying to get this
command line to work:
+H800 +W800 +FN +A -J +KFI1 +KFF36 +KI0 +KF1 +KC
And every time I click the run button I get a POV-Ray not responding
message.
Help,
Carl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Carl wrote:
> normal and try to save the changes
What directory are you trying to save the changed file into? The same
directory (or a subdirectory) under the program's executable?
Don't do that. You're not supposed to store data for a multi-user
program into the place the system-wide executables are stored.
That's just my guess, mind, based on the fact that Vista is putting in
stronger support to keep you from doing things like that, and actually
moving files you write into the Programs directory into the user's home
directory "transparently". Very confusing, but necessary when programs
refuse to follow the rules.
--
Darren New / San Diego, CA, USA (PST)
His kernel fu is strong.
He studied at the Shao Linux Temple.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Carl" <car### [at] semisouth com> wrote:
> I posted these 2 questions in the new user area and I just spotted this
> windows area. I think these questions belong here.
>
> Ok... My old PC died a few weeks ago and I'm now up and running with Vista
> on a Core 2 Duo. I had read that was the best processor for POV-Ray.
> Anyways... I'm still getting stuff up and running and just hit my first
> POV-Ray issue. I was about to start work on a short animation and to that
> end I wanted to edit the resolution INI file. I click on tools, then click
> on Edit resolution INI file, and up comes Notepad. I make a few changes as
> normal and try to save the changes and all I get is a cannot create the
> file error message. It simply says "Make sure that the path and file name
> are correct." They are and I'm pretty sure this in a Windows Vista issue
> with all its new security. I've now tried opening the file with several
> other editor's and I've even now tried to edit the file in DOS mode all
> with no luck.
>
> I'm sure there has to be a simple solution to this but for the life of me I
> can't figure it out at the moment.
>
> Ok... now I'm really pulling my hair out. I just tried to get around the
> INI file problem by putting in all the setting on the commend line.
> POV-Ray works fine when I pick one of the options from the INI file and
> don't use any command line options. However, I'm now trying to get this
> command line to work:
>
> +H800 +W800 +FN +A -J +KFI1 +KFF36 +KI0 +KF1 +KC
>
> And every time I click the run button I get a POV-Ray not responding
> message.
>
> Help,
> Carl
I agree. It's very maddening. I think what I ended up doing is saving to
some other directory and then copying the file over to the correct POV-Ray
directory. IIRC, the file can't have the .ini extension or Vista will
block you when you try to copy. I think I saved it with a .txt extension
and then changed it back to .ini once it was copied. Kinda frustrating,
yes. I avoid that machine most of the time now for a variety of reasons.
Charles
PS Other than editing .ini's I haven't had any other issues with POV-Ray on
Vista.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> What directory are you trying to save the changed file into? The same
> directory (or a subdirectory) under the program's executable?
Here is the exact error screen:
http://www.wwwmwww.com/images/VistaError.png
The path is C:PROGRAM FILESPOV-RAY FOR WINDOWS V3.6rendererquickres.ini
Is that the same path that the program executable is in? It's the directory
POV-Ray put the file in when I installed it. I've never had to change it
before.
Darren New <dne### [at] sanrrcom> wrote:
> Don't do that. You're not supposed to store data for a multi-user
> program into the place the system-wide executables are stored.
I'm the only family member that is using POV-Ray and at the moment at least
I'm not using any multi-user features of Vista. Everyone sees the same
desktop, etc. Should I create user accounts for each family member?
Darren New <dne### [at] sanrrcom> wrote:
> That's just my guess, mind, based on the fact that Vista is putting in
> stronger support to keep you from doing things like that, and actually
> moving files you write into the Programs directory into the user's home
> directory "transparently". Very confusing, but necessary when programs
> refuse to follow the rules.
Can that also explain why the command line doesn't work?
http://www.wwwmwww.com/images/VistaError2.png
Note the words (Not Responding) in the header. If the command line it blank
all runs fine though I don't quite get the image I want.
Thanks,
Carl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Charles C" <nomail@nomail> wrote:
> I agree. It's very maddening. I think what I ended up doing is saving to
> some other directory and then copying the file over to the correct POV-Ray
> directory. IIRC, the file can't have the .ini extension or Vista will
> block you when you try to copy. I think I saved it with a .txt extension
> and then changed it back to .ini once it was copied. Kinda frustrating,
> yes. I avoid that machine most of the time now for a variety of reasons.
>
> Charles
>
> PS Other than editing .ini's I haven't had any other issues with POV-Ray on
> Vista.
I'll try some of that tonight. At the moment I'm pretty sure the INI file
thing is a normal Vista issue but I'm even more worried about the command
line stuff not working. The next step may be to uninstall POV-Ray and
start over.
Carl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Carl nous apporta ses lumieres en ce 18-04-2007 15:41:
> "Charles C" <nomail@nomail> wrote:
>> I agree. It's very maddening. I think what I ended up doing is saving to
>> some other directory and then copying the file over to the correct POV-Ray
>> directory. IIRC, the file can't have the .ini extension or Vista will
>> block you when you try to copy. I think I saved it with a .txt extension
>> and then changed it back to .ini once it was copied. Kinda frustrating,
>> yes. I avoid that machine most of the time now for a variety of reasons.
>> Charles
>> PS Other than editing .ini's I haven't had any other issues with POV-Ray on
>> Vista.
> I'll try some of that tonight. At the moment I'm pretty sure the INI file
> thing is a normal Vista issue but I'm even more worried about the command
> line stuff not working. The next step may be to uninstall POV-Ray and
> start over.
> Carl
In that case, you may try installing to a custom location instead of the default
one. I don't know if it will make any change, but worth a try.
--
Alain
-------------------------------------------------
Experience hath shewn, that even under the best forms of government those
entrusted with power have, in time, and by slow operations, perverted it
into tyranny.
Thomas Jefferson
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <ele### [at] netscapenet> wrote:
> In that case, you may try installing to a custom location instead of the default
> one. I don't know if it will make any change, but worth a try.
Well I haven't resorted to re-installing POV-Ray yet but I am making some
headway. If I open notepad by right clicking and selecting "run as
administrator" I can edit and save the INI file. However I still can't
make an animation. If I select one of the normal options POV-Ray runs and
does make an image. Like this:
http://www.wwwmwww.com/images/VistaError3.png
As soon as I select the animation option I entered I just get this:
http://www.wwwmwww.com/images/VistaError4.png
The INI file contains what you see commented out in the sky.pov file. I've
even now right clicked on POV-Ray itself and ran it as an administrator but
it makes no difference.
Arg...
Any other ideas,
Carl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Carl wrote:
> Is that the same path that the program executable is in?
You shouldn't be storing any modifiable configuration information under
C:\Program Files. That's for, you know, program files. ;-)
> I'm the only family member that is using POV-Ray and at the moment at least
> I'm not using any multi-user features of Vista.
You are. You just don't know it.
> Everyone sees the same
> desktop, etc. Should I create user accounts for each family member?
I don't know that's relevant to the problem you're seeing here.
> Can that also explain why the command line doesn't work?
I don't know what that sentence means. Which "command line"? You mean
invoking POV-Ray's render engine with command-line arguments? I don't
know. I would doubt it, somehow, unless perhaps it's trying to write
into the program-files directory as it renders or something.
Just be aware that Vista is different from previous versions in that
respect, because no matter how hard Microsoft tried to get people to
treat it as a secure multi-user platform, they refused for various
reasons. :-)
--
Darren New / San Diego, CA, USA (PST)
His kernel fu is strong.
He studied at the Shao Linux Temple.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Carl wrote:
> Any other ideas,
Where are you telling it to write the resulting image files?
--
Darren New / San Diego, CA, USA (PST)
His kernel fu is strong.
He studied at the Shao Linux Temple.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> Where are you telling it to write the resulting image files?
Well I assume the animation files would be save the same place the still
images are placed. That is the location of the ".pov" file itself. As
seen here:
http://www.wwwmwww.com/images/VistaError3.png
that is J:logo which is a directory on my jump drive.
After some most testing last night the following command line does work:
+H800 +W800 +FN +A -J
So I assume its something with the animation parameters that is locking it
up.
The main reason I got a Core Duo was to speed up POV-Ray and now it doesn't
want to cooperate.
I'll do some more testing with changing some of the animation parameters one
at a time tonight and I suspose I can always render just one frame at a time
but I've just never had these problems with POV-Ray before.
Help,
Carl
P.S. Why don't back slashes show up in these posts? For example I typed
one between J: and logo above.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
