 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Seeing as POV 3.5 now owns the .pov file association,
I figured that I would put shorcuts to the 3.1 pvengine,
the 3.5 pvengine and to megapov.exe into the SendTo
Folder and then be able to send a .pov file to start any
of these programs with a right click and SendTo in the
drop down menu.
It works in that the desired POV program opens but I
get an error and the file does not get loaded.
For MegaPOV and POV 3.1, I get:
INI file error. Bad option syntax or error opening .INI/.DEF file '//'
and in POV 3.5:
Possible Command Line Error: Could not open INI file '//'
Is there something I can alter or add in the Target: or Start in:
dialog space in the shortcut properties box that will allow the file
to be loaded ?
Or ... does someone have a better idea of how to send the
target .pov file to the POV program I want to run ?
TIA
--
Y
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Y wrote in message <3b9d835c@news.povray.org>...
>
>Or ... does someone have a better idea of how to send the
>target .pov file to the POV program I want to run ?
I'd just create file associations for all versions of POV. The names of the
menu options may vary depending on your version of Windows, but the
procedure for Win98 is as follows:
(Warning: Try to keep the various "Edit"s straight :-)
1) Open a folder, and select "Folder Options" from the "View" menu.
2) Click on the "File Types" tab
3) Scroll down to "POV-Ray scene file"
4) Select it, and hit the "Edit" button.
5) Select the "Edit" item in the "Actions" list box, and hit the "Edit"
button.
6) Select the text in "Application used to perform action", and copy it to
the clipboard
7) Hit the "Cancel" button
8) Click the "New" button
9) Type the name of the action (i.e. "Open with MegaPOV") in the "Action"
text box
10) Paste the text you copied in step (6) into the "Application used to
perform action" box
11) Edit that text to include the file and path of the version of POV you
want to use
12) Hit the "OK" button
13) Repeat steps 8-12 for other versions of POV.
14) Hit the "Close" button
15) Hit the "Close" button
--
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If you really want to use short cuts in your SendTo folder try adding "
/edit" to the end of the file name in the target box of the shortcut
properties, (make sure there is a space between the path and the /edit)
you can also do the same with " /render"
-tgq
"Mark Wagner" <mar### [at] gte net> wrote in message
news:3b9d9db2$1@news.povray.org...
>
> Y wrote in message <3b9d835c@news.povray.org>...
> >
> >Or ... does someone have a better idea of how to send the
> >target .pov file to the POV program I want to run ?
>
>
> I'd just create file associations for all versions of POV. The names of
the
> menu options may vary depending on your version of Windows, but the
> procedure for Win98 is as follows:
> (Warning: Try to keep the various "Edit"s straight :-)
>
> 1) Open a folder, and select "Folder Options" from the "View" menu.
> 2) Click on the "File Types" tab
> 3) Scroll down to "POV-Ray scene file"
> 4) Select it, and hit the "Edit" button.
> 5) Select the "Edit" item in the "Actions" list box, and hit the "Edit"
> button.
> 6) Select the text in "Application used to perform action", and copy it to
> the clipboard
> 7) Hit the "Cancel" button
> 8) Click the "New" button
> 9) Type the name of the action (i.e. "Open with MegaPOV") in the "Action"
> text box
> 10) Paste the text you copied in step (6) into the "Application used to
> perform action" box
> 11) Edit that text to include the file and path of the version of POV you
> want to use
> 12) Hit the "OK" button
> 13) Repeat steps 8-12 for other versions of POV.
> 14) Hit the "Close" button
> 15) Hit the "Close" button
>
> --
> Mark
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
: If you really want to use short cuts in your SendTo folder try adding "
: /edit" to the end of the file name in the target box of the shortcut
: properties, (make sure there is a space between the path and the /edit)
: you can also do the same with " /render"
:
: -tgq
:
That didn't seem to work ... if I add it within the " ", I get a windows
message that the path is invalid. If I add it just after the target " "
(with a space ;), the POV prog launches but I receive the same error:
INI file error. Bad option syntax or error opening .INI/.DEF file '//'
Also tried entering that into the "Start with" box but it is not accepted.
Somehow, I still need a way to pass on the same info that is passed
when double-clicking on the .pov ... thru the association.
Obviously, I don't have a clue as to what I'm doing. ;)
I don't understand Mark's advice on creating additional file associations
for each version. How can the .pov file have more than one ?
This is not a big deal ... I can always start the version I wish and then
load in the .pov file I wish to run ... I just thought it would be a simple
and useful way to send a .pov file to whichever version I needed.
And ... it *should* be ;)
Thanks anyway guys for your input ...
--
Y
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
sorry, no quotes either
like this:
"C:\blahblah...wherever megapov is\megapov.exe" /EDIT
at least I was able to get it to work
-tgq
"Y" <out### [at] huntelnet> wrote in message
news:3b9e2f62$1@news.povray.org...
> : If you really want to use short cuts in your SendTo folder try adding "
> : /edit" to the end of the file name in the target box of the shortcut
> : properties, (make sure there is a space between the path and the /edit)
> : you can also do the same with " /render"
> :
> : -tgq
> :
> That didn't seem to work ... if I add it within the " ", I get a windows
> message that the path is invalid. If I add it just after the target " "
> (with a space ;), the POV prog launches but I receive the same error:
>
> INI file error. Bad option syntax or error opening .INI/.DEF file '//'
>
> Also tried entering that into the "Start with" box but it is not accepted.
>
> Somehow, I still need a way to pass on the same info that is passed
> when double-clicking on the .pov ... thru the association.
>
> Obviously, I don't have a clue as to what I'm doing. ;)
>
> I don't understand Mark's advice on creating additional file associations
> for each version. How can the .pov file have more than one ?
>
> This is not a big deal ... I can always start the version I wish and then
> load in the .pov file I wish to run ... I just thought it would be a
simple
> and useful way to send a .pov file to whichever version I needed.
> And ... it *should* be ;)
>
> Thanks anyway guys for your input ...
> --
> Y
>
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Y" <out### [at] huntelnet> wrote in message news:3b9e2f62$1@news.povray.org...
>
> I don't understand Mark's advice on creating additional file associations
> for each version. How can the .pov file have more than one ?
>
One is the default (i.e. the behaviour you get when you just dbl-click on the
file). The other options you get when you right-click on the file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tom Melly" wrote
: >
: > I don't understand Mark's advice on creating additional file associations
: > for each version. How can the .pov file have more than one ?
: >
:
: One is the default (i.e. the behaviour you get when you just dbl-click on the
: file). The other options you get when you right-click on the file.
:
Aha!!! . . . will give it a shot ... thanks Mark and Tom.
--
Y
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
: sorry, no quotes either
:
: like this:
: "C:\blahblah...wherever megapov is\megapov.exe" /EDIT
:
: at least I was able to get it to work
:
: -tgq
:
Yes ... I understood that ... and did it just as you described ...
*except* I didn't use upper case on the *edit*. Will do again.
Thanks
--
Y
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
: : sorry, no quotes either
: :
: : like this:
: : "C:\blahblah...wherever megapov is\megapov.exe" /EDIT
: :
: : at least I was able to get it to work
: :
: : -tgq
: :
: Yes ... I understood that ... and did it just as you described ...
: *except* I didn't use upper case on the *edit*. Will do again.
: Thanks
: --
: Y
Still the same error message.
This is what I have in my properties target box:
"G:\Programs\POV-Ray for Windows v3.1\bin\pvengine.exe" /EDIT
Seems to be as you directed ... ???
I'll try the additional associations.
Thanks
--
Y
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3b9e4cec@news.povray.org>, out### [at] huntelnet says...
> : : sorry, no quotes either
> : :
> : : like this:
> : : "C:\blahblah...wherever megapov is\megapov.exe" /EDIT
> : :
> : : at least I was able to get it to work
> : :
> : : -tgq
> : :
> : Yes ... I understood that ... and did it just as you described ...
> : *except* I didn't use upper case on the *edit*. Will do again.
> : Thanks
> : --
> : Y
>
> Still the same error message.
> This is what I have in my properties target box:
>
> "G:\Programs\POV-Ray for Windows v3.1\bin\pvengine.exe" /EDIT
>
> Seems to be as you directed ... ???
> I'll try the additional associations.
> Thanks
> --
> Y
>
Did the part that you copied to the clipboard have the FULL dir name?
In my system it uses the 8.3 type of name, for example:
C:\PROGRAM FILES\POV-Ray for Windows v3.5\bin\pvengine.exe /EDIT "%1"
becomes:
C:\PROGRA~1\POV-RA~1.5\bin\pvengine.exe /EDIT "%1"
Perhaps that might be the problem?
--
Regards,
Sander
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
