Wineconsole
From Wine-Wiki
Contents |
[edit] Introduction
When running text based software, wineconsole is similar to wine command wcmd with a few important differences:
The later one runs a console which is fully compatible to that on Windows and some programs rely on that. Wineconsole is only the "terminal emulation window". [..] It also has the advantage that the wine debugging output (FIXME/ERR) don't clutter the output. [Wine Archive Link]
According to the wine user guide, Wine has three ways for running a console program :
- bare streams
- wineconsole with user backend
- wineconsole with curses backend
"bare streams" means that no extra support of wine is provided to map between the unix console access and the Windows console access. This works well if your software is text based with no special requriements. The Wine program Wineconsole provides good support for full screen CUI applications (including but not limited to color support, mouse support. With the curses backend, X11 does not need to be running but with the limitation that it will produce strange behavior if two (or more) Windows consoles are used on the same Un*x terminal.
Further Reading
[edit] Forum Comments about Wineconsole
[Jun-Jul 06]A user noted: wineconsole by itself doesn't seem to do anything, and using --help didn't work (and there seems to be no man page). Running
wineconsole wcmd.exe'
started a command prompt in the activating terminal just like wcmd.exe normally does, except the console output is forced to 80x25 output with no back buffer (Windows' cmd.exe can have a configurable-sized back-buffer and can be resized), and the error/fixme/trace's from the apps run from it are displayed improperly (I suppose because they end lines with \n, and in wineconsole's console it needs \r\n).
J. Hawkins: try 'wineconsole --backend=user wcmd.exe'. Works great for me. wine archive
A poster noted [May 06]: "wine telnet.exe" on the command line however silently terminates, as the call to GetConsoleScreenBufferInfo returns an empty LPCONSOLE_SCREEN_BUFFER_INFO structure. Shouldn't wine start up some wineconsole in that circumstances as XP does?
R. Shearman: The trouble is that it is already started within a console, it's just that the console isn't compatible. Most people prefer their console apps to start inside the Unix console, since that is what they expect from them. I'm afraid it's a matter of starting the program with wineconsole manually if you want the extra compatibility.
U. Bonnes: If I understand the wine loader right, and didn't overlook something in the relay log, the initial wine process doesn't start the first process by a CreateProcess call. So no chance to fiddle withe the flags.
E. Pouch: that's why we use wineconsole. wine doesn't create any console, wineconsole does. wine archive
D. Kegel [Mar 06]: Last year, I poked at using msys under wine:
http://www.winehq.com/hypermail/wine-devel/2004/04/0149.html but didn't follow up on the hint that wineconsole would help. Finally got around to it. Sure enough, you can run msys's sh.exe in a wineconsole! It's ugly and can't seem to run configure scripts yet, but it does run simple shell scripts and interactive commands like cd, pwd, and ls. Sort of.
