http://bugs.winehq.org/show_bug.cgi?id=14965
Summary: Wine not passing Windows program arguments correctly Product: Wine Version: 1.1.3 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: yfrwlf@gmail.com
When running, say:
wine C:\Program\ Files\Diablo\ II\Game.exe -direct -txt
OR the Linux variant of the path
The arguments never reach the program. However, when going into the same directory and running it from there:
cd /home/user/.wine/drive_c/Program\ Files/Diablo\ II/
and then running:
wine Game.exe -direct -txt
It works. Even if you try to run it from one directory down, but still "on the Windows drive", by going:
/drive_c/Program Files$ wine \Diablo\ II\Game.exe -direct -txt
OR
/drive_c/Program Files$ Diablo\ II/Game.exe -direct -txt
It still doesn't work. So it's not some strange thing with needing to run wine from the "Windows drive". Running it from within the Windows command line also exhibits the same problem. When running:
C:\Program Files>Diablo II\Game.exe -direct -txt
It doesn't work, but when running
C:\Program Files\Diablo II>Game.exe -direct -txt
It works.
http://bugs.winehq.org/show_bug.cgi?id=14965
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
--- Comment #1 from Vincent Povirk madewokherd@gmail.com 2008-08-23 17:10:31 --- What happens when using cmd.exe on windows?
http://bugs.winehq.org/show_bug.cgi?id=14965
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from James Hawkins truiken@gmail.com 2008-08-24 03:24:09 --- It's the same thing on windows. Invalid.
http://bugs.winehq.org/show_bug.cgi?id=14965
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from James Hawkins truiken@gmail.com 2008-08-24 03:24:17 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=14965
--- Comment #4 from Yfrwlf yfrwlf@gmail.com 2008-08-24 11:14:14 --- (In reply to comment #2)
It's the same thing on windows. Invalid.
That's retarded. Why not fix this Windows bug then in Wine? Surely fixing this couldn't hurt anything?
http://bugs.winehq.org/show_bug.cgi?id=14965
--- Comment #5 from Vincent Povirk madewokherd@gmail.com 2008-08-24 11:23:52 --- It's not a Windows bug. If anything it's a bug in the application that it is sensitive to the working directory. The wine command passes the working directory as-is to the program, like the windows command line, and this is not going to change.
If you want to match the Windows GUI behavior, what Diablo probably expects, methods are provided for that. Use the shortcuts Wine set up when you installed the program (which you can take apart to see how to do the same thing in the command-line) or double-click on the exe file (which runs 'wine start /unix unix-path-of-file').
http://bugs.winehq.org/show_bug.cgi?id=14965
--- Comment #6 from Yfrwlf yfrwlf@gmail.com 2008-08-26 00:55:27 --- Since it's a bug in the program nor in Windows then I guess that's all I needed to know. Thanks. ^^