"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3d5b51a6$1@news.povray.org...
>
> Well, given that the source code is available, isn't this guessing game
> redundant?
>


    Have you actually looked at the startup code for WinPOV ? It's quite
complex - the developers are for more likely than any of us, mere mortals
(even a software engineer like me), to be able to quickly find the source of
this bug and fix it - information like this will be helpful to them in
knowing where in the source the bug is likely to reside.
    Having said that, and having thought about it a little, I think this
could be quite a difficult bug to fix - it's probably caused by the fact
that you can pass a number of command line parameters to pov and the
parameters are separated by spaces... though why, then, spaces in the file
name work ok, but spaces in the directory path doesn't, I'm not sure...

--
Pandora/Scott Hill/[::O:M:C::]Scorpion
Software Engineer.
http://www.pandora-software.com

Post a reply to this message

Principially  you are right, Torsten.

In this particular case....

If I 'll go and search mistakes in the POV-Sourcecode,
you'll have to render with watercolor and paper next week :-).

**********************************************


"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5b51a6$1@news.povray.org...
> In article <3d5b3e36@news.povray.org> , Josh Seagoe <rab### [at] junocom>
> wrote:
>
> > Note that this CANNOT be a problem with the shell, as the command line
> > is passed as one string to WinMain, or via GetCommandLine in Windows.
> > The application is responsible for splitting out parameters.  (usually
> > in the C runtime startup code before calling main, so it still may be
> > outside of the POV code)
>
> Well, given that the source code is available, isn't this guessing game
> redundant?
>
>     Thorsten

Post a reply to this message

No i did not.
can I hear out of your message that this would change something ?


"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:3d5b51f6$1@news.povray.org...
> In article <3d5926a8@news.povray.org> , "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
>
> > bin\pvengine.exe "f:\00_rpgm\01_bs\01_projekte\smpov
> > 1\com\ani_woodbox_08132002_172415_87176_1_0x0-160x120a.ini"
>
> Did you try to put "/RENDER" in front of the path in the various possible
> combinations?
>
>     Thorsten

Post a reply to this message

On Tue, 13 Aug 2002 18:59:42 +0200, ABX <abx### [at] babilonorg> wrote:

>On Tue, 13 Aug 2002 18:53:37 +0200, "Theo Gottwald *"
><The### [at] t-onlinede> wrote:
>> Sounds intresting to me.
>> I have win2k.
>
>NT4 Sp6 here.
>
>ABX
I've just tried

pvengine "c:\program files\pov-ray for windows v3.5\insert
menu\images.ini"

on WinXP Pro and got the following in the message window


Calling rendering engine with parameters '"c:\program files\pov-ray
for windows v3.5\insert menu\images.ini"'
Preset INI file is 'C:\PROGRAM FILES\POV-RAY FOR WINDOWS
V3.5\RENDERER\QUICKRES.INI', section is '[320x240, No AA]'.
Rendering using command line '"c:\program files\pov-ray for windows
v3.5\insert menu\images.ini"'.
Persistence of Vision(tm) Ray Tracer Version 3.5 win32 (.icl)
  This is an official version prepared by the POV-Ray Team. See the
   documentation on how to contact the authors or visit us on the
   internet at http://www.povray.org/.
Copyright 1991-2002 POV-Ray Team(tm)
This Windows version by Christopher J. Cason
Possible Command Line Error: Could not open INI file 'c:\program'.
Possible Command Line Error: Could not open INI file 'files\pov-ray'.
Possible Command Line Error: Could not open INI file 'for'.
Possible Command Line Error: Could not open INI file 'windows'.
Possible Command Line Error: Could not open INI file 'v3.5\insert'.
Possible Command Line Error: Could not open INI file
'menu\images.ini'.

<snip>

Post a reply to this message

In article <3d5b56c5$1@news.povray.org> , "Pandora" 
<pan### [at] pandora-softwarecom> wrote:

> Have you actually looked at the startup code for WinPOV ?

Yes it is complex and looking at the code will be a bit more difficult.
However, I usually use a debugger to track such bugs.  Then it is really
easy.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <3d5b6c53$1@news.povray.org> , "Theo Gottwald *" 
<The### [at] t-onlinede> wrote:

> can I hear out of your message that this would change something ?

Yes, of course.  Under WinDOS 2000 this works just fine...

pvengine /RENDER "c:\Programme\POV-Ray for Windows\ini\test.ini"

    Thorsten

Post a reply to this message

On Tue, 13 Aug 2002 17:58:21 +0200, ABX <abx### [at] babilonorg> wrote:

>On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
><The### [at] t-onlinede> wrote:
>> Hmmm. If there is no sollution to give the full path to POV, I guess I have
>> to restrict the proggy to a "non whitespace path".
>
>I have just tested as
>  pvengin.exe "abx test.ini"
>and it worked fine. No idea what could be wrong in your situation.
>
>ABX

I've just had a look at the source code and I can see why it's not
working for myself or Theo - what I can't understand is why it works
for ABX. The source code doesn't seem to be different for W2k/XP and
NT4. The only thing I can think of is to ask ABX whether he has
test.ini as well as "abx test.ini" in his folder?

Cheers,

Scott

Post a reply to this message

Thorsten said, that the /RENDER switch will solve the problem.

--Theo


"Scott Moore" <sdm### [at] zoomcouk> schrieb im Newsbeitrag
news:9e5nlucq0g1ep9ncg9nsea3j7n86p56h58@4ax.com...
> On Tue, 13 Aug 2002 17:58:21 +0200, ABX <abx### [at] babilonorg> wrote:
>
> >On Tue, 13 Aug 2002 17:51:15 +0200, "Theo Gottwald *"
> ><The### [at] t-onlinede> wrote:
> >> Hmmm. If there is no sollution to give the full path to POV, I guess I
have
> >> to restrict the proggy to a "non whitespace path".
> >
> >I have just tested as
> >  pvengin.exe "abx test.ini"
> >and it worked fine. No idea what could be wrong in your situation.
> >
> >ABX
>
> I've just had a look at the source code and I can see why it's not
> working for myself or Theo - what I can't understand is why it works
> for ABX. The source code doesn't seem to be different for W2k/XP and
> NT4. The only thing I can think of is to ask ABX whether he has
> test.ini as well as "abx test.ini" in his folder?
>
> Cheers,
>
> Scott

Post a reply to this message

On Thu, 15 Aug 2002 14:38:39 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:

>Thorsten said, that the /RENDER switch will solve the problem.
>
>--Theo
>

Yes, I saw his post but the documentation (5.1.2) says

You may specify additional INI files on the command-line by simply
typing the file name on the command line. For example:

  POVRAY MYOPTS.INI


Does this mean the docs need to be updated to mention that spaces in
the filename aren't allowed?

(BTW. As I'm mentioning the docs, do all platforms build the source to
pvengine or povray? On Windows the .exe is pvengine - but the docs, as
shown above, suggest it's povray.exe - do the docs need updating for
this also?)

Cheers,

Scott

Post a reply to this message

In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore 
<sdm### [at] zoomcouk>  wrote:

> Does this mean the docs need to be updated to mention that spaces in
> the filename aren't allowed?
>
> (BTW. As I'm mentioning the docs, do all platforms build the source to
> pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> shown above, suggest it's povray.exe - do the docs need updating for
> this also?)

The documentation is clear that it is about the command-line version of
POV-Ray, not the GUI versions and it does refer you to the GUI version
documentation for specifics of those versions.  Where?  Well, in the
introduction of the command-line options in section 5 in case you missed it.

If you don't read the documentation carefully and get burned that is not a
bug in POV-Ray but in your method of reading the documentation.  The
suggested way to read it is from section 1 to the last section.  It is not
recommended to use it for reference purposes only.  That way you _will_ miss
very important details!

    Thorsten

Post a reply to this message