[Wine] WINE fails in directories with Question Marks in name

Martin Gregorie martin at gregorie.org
Mon Sep 12 19:43:41 CDT 2011

On Mon, 2011-09-12 at 18:31 -0500, stvs wrote:
> Thanks for the suggestion, but that wil fail because it is wine that
> fails when executed from within a directory containing a special
> character.
You said 'There is no way for me to escape the directory's name in the
(scripted) call to wine', which indicates that your problem is an
inability to escale question marks in a non-Windows script. Your example
only confirms this by showing:

cd 'foo?'
wine cmd.exe bar.exe

which nowhere indicates that wine and its app has much idea what
directory its in when it fails. In fact this shows that you're not
running comskip its installation directory. Is this as accurate
illustration of what you're doing? If so, does comskip work better if
you cd to its installation directory and run it from there, e.g.

cd '/Library/Application Support/ETVComskip/comskip'
wine comskip.exe

>  Of course you can escape the character in a shell script, but that
> won't help wine when it attempts to access the directory './foo?'.
I looked at all the logs posted this year. The ones from January are
about an entirely different problem: not a '?' in sight.

There's no indication in your logs that Wine failed to pass an absolute
pathname containing a question mark to comskip - in fact exactly the
opposite is true, since comskip reports the name correctly, though I notice
that path doesn't start with a drive letter. Should it do so? 


More information about the wine-users mailing list