Re: Re: pvconv invocation

> works fine and produces in.qcp.  Maybe you have a different version of pvconv 
> that works better.  I agree, the work-around is ugly.

Ah, it all becomes clear.  I am actually using version 2 of pvconv.exe
that does work correctly.  I used filemon from sysinternals.com to 
try and see if it was opening something stupid, and it doesn't even
try.  This simply looks like a pure coding error in command line argument
parsing.  Using ltrace on Linux I was able to figure out that what
actually happens is it tries to open a zero length filename for
the second file.

I couldn't find any way of working around the problem through command
line arguments.  The argument parsing is terrible - you can put "-v"
anywhere!

Roger


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt