Yep, to get back on topic, my major point was that if he is using
"/drive_c" I think it should be preceded by "/.wine" because wine wont
have a clue of what /drive_c is unless he's calling wine from the
/.wine path.<br>
<br>
/discuss<br>
<br><br><div><span class="gmail_quote">On 10/5/05, <b class="gmail_sendername">Holly Bostick</b> <<a href="mailto:motub@planet.nl">motub@planet.nl</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
phil lemelin schreef:<br>><br>> On 10/5/05, Holly Bostick <<a href="mailto:motub@planet.nl">motub@planet.nl</a>> wrote:<br>><br>>> phil lemelin schreef:<br>>><br>>>> On 10/4/05, <a href="mailto:G4BBH@winlink.org">
G4BBH@winlink.org</a> <<a href="mailto:G4BBH@winlink.org">G4BBH@winlink.org</a>> wrote:<br>>>><br>>>>> I have three problems with wine. Wine set up a pseudo windows<br>>>>> directory system under my home directory/wine. My application
<br>>>>> resides in the created 'Program Files' directory and a<br>>>>> necessary file placed in the windows/system directory.<br>>>>><br>>>>> 1. If I click on the exe and run with wine it works without
<br>>>>> error. However I seem unable to set up a path to the exe as in<br>>>>> 'wine "drive_c/Program Files/Airmail/Airmail3.exe"' as the<br>>>>> executive can never be found. I tried all sorts of path
<br>>>>> combinations and failed.<br>>>>><br>>>> For the point #1 Did you tried without the "" and the path would<br>>>> more look like $HOME/.wine/drive_c/blablabla<br>
>>><br>>><br>>> Phil, the quotation marks are necessary because the path contains a<br>>> space (C:\Program Files), and Linux considers a space the end of<br>>> the command unless it is either escaped (C:\\Program\ Files; the
<br>>> extra "\" being an escape character to tell a Linux application<br>>> --which Wine is--that the character following the \ should be<br>>> considered part of the command. This is why the first forward slash
<br>>> is escaped as well as the space, so that Linux can recognize it,<br>>> otherwise Wine would read the path as C:Program Files), or enclosed<br>>> in quotes (single or double), which tell a Linux application to use
<br>>> the quoted command or path 'as is'.<br>>><br>>><br>>><br>> Well, i'm starting all my apps with this command when working from<br>> the console :<br>><br>> $ wine $HOME/.wine/drive_c/Program\ Files/WordView/WORDVIEW.EXE
<br>><br> Right; you've escaped the space between "Program" and "Files", so Wine<br> can pass an understandable (valid) path to Windows.<br>><br>> So far I didnt' had any problem It's true that in some script I also
<br>> use something like<br>><br>> $ wine "c:\\Program Files\\WordView\\WORDVIEW.EXE" "/tmp/tempdoc.doc"<br>><br>Right, because you've escaped the first forward slashes, so that Wine<br>recognizes that a forward slash is meant to be used 'as is', but because
<br>you have not also escaped the space between "Program" and "Files", the<br>quotation marks are needed for the space to be recognized, (although<br>I'm surprised that doesn't cause a problem with the escaped slashes,
<br>since they would then be doubled. But maybe Windows doesn't care about<br>that, I don't know. I can see how that's possible, since the Windows<br>command line is deliberately stupid and will take just about anything so
<br>that users don't have to be precise in telling it what to do). And of<br>course, the path to the doc is in quotes because it's a UNIX path (with<br>backslashes that Windows doesn't recognize, but Wine does), so on the
<br>whole I can see how this works.<br><br>Myself, I don't put stuff in C:\\Program\ Files anyway, because typing<br>that whole path would make me insane-- especially with the necessity to<br>escape everything-- and plus I trained myself not to use it when I was
<br>using Windows, since the C:\\ drive had to be reformatted far too often<br>for me to put up with my applications and data being lost every time it<br>did. And now, using Wine, that habit enables me to control space on my
<br>partitions better, since all my Windows applications are not in /home<br>but on a dedicated partition (linked to d:), so I can always easily see<br>how much space said applications are taking up.<br><br>But that's just me, and off-topic from the actual problem, which is
<br>likely unrelated to the escaping of the path to the application in any case.<br><br>Holly<br></blockquote></div><br><br clear="all"><br>-- <br>Philippe-Alexandre Lemelin