http://bugs.winehq.com/show_bug.cgi?id=205
fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fgouget@codeweavers.com
tony_lambregts@telusplanet.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED
------- Additional Comments From fgouget@codeweavers.com 2001-05-04 19:16 ------- You may have already seen this on the newsgroup but here goes anyway:
This is because wcmd links to the winelauncher instead of wine. Of course with the CodeWeavers package there's a little twists since (AFAIK), wine is in fact winelauncher and wine.bin is what one would normally call wine. So there are a couple of workarounds. * find wcmd, it should be a symlink to /opt/wine/bin/wine, if so then delete wcmd and recreate it as a symlink to /opt/wine/bin/wine.bin * or type the following to start wcmd (use an alias, a script...) WINEPRELOAD=/usr/bin/wcmd.so /opt/wine/bin/wine.bin
winelauncher still needs to be fixed to deal with console applications correctly.
------- Additional Comments From fgouget@codeweavers.com 2001-05-13 13:38 ------- I sent a patch to wine-patches that fixes this problem. The bug was that winelauncher was starting the Windows application in the background in order to be able to both capture its output and get its return code. But starting the application in the background prevented it from getting to stdin. Depending on the application this either blocked it indefinitely, or got it to enter an infinite loop like wcmd. With the patch, we still achieve the above but the application is started in the foreground, allowing it to interact with the console normally. I tested it with wcmd and others and it works just fine.
------- Additional Comments From tony_lambregts@telusplanet.net 2002-07-23 08:27 ------- Marking as verified
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://bugs.winehq.com/show_bug.cgi?id=205. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.