Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
W
wine-winehq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
wine
wine-winehq
Commits
2f38cffa
Commit
2f38cffa
authored
Feb 14, 1999
by
Joseph Pranevich
Committed by
Alexandre Julliard
Feb 14, 1999
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
New examples/documentation for console configuration options.
parent
ebc0e5e0
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
78 additions
and
2 deletions
+78
-2
console
documentation/console
+73
-0
wine.ini
wine.ini
+5
-2
No files found.
documentation/console
View file @
2f38cffa
...
...
@@ -92,3 +92,76 @@ FreeConsole
Is it possible to interrupt win32's FileWrite? I'm not sure.
It may not be possible to interrupt any system calls.
DOS (Generic) Console Support
-----------------------------
I. Command Line Configuration
DOS consoles must be configured either on the command line or in a dot
resource file (.console). A typical configuration consists of a string
of driver keywords separated by plus ('+') signs. To change the
configuration on the command-line, use the -console switch.
For example:
wine -console ncurses+xterm <apllication>
Possible drivers:
tty - Generic text-only support. Supports redirection.
ncurses - Full-screen graphical support with color.
xterm - Load a new window to display the console in. Also
supports resizing windows.
II. Wine.conf Configuration
In the wine.conf file, you can create a section called [console] that
contains configuration options that are respected by the assorted
console drivers.
Current Options:
XtermProg=<program>
Use this program instead of xterm. This eliminates the need for a
recompile.
XtermResolution=<cols>x<rows>
(Example: XtermResolution=80x25)
Start your xterm program with this text resolution. 80x25 is
recommended, a NULL value will mean to use the terminal's default
resolution, determined however your specific terminal figures
that out. Most console-based programs expect eother 80x25 or
80x40 displays.
Note: The default for many terminals is 80x24. One row smaller
than what the console subsystem generally expects.
Note 2: This information is passed on the command-line with the
-g switch.
III. Terminal Types
There are a large number of potential terminals that can be used with
Wine, depending on what you are trying to do. Unfortunately, I am still
looking for the "best" driver combination.
Note that 'slave' is required for use in Wine, currently.
Program | Color? | Resizing? | Slave?
-----------------------------------------
xterm N Y Y
nxterm Y N Y
rxvt Y ? N
(linux console) Y N ?
As X terminals typically use a 24x80 screen resolution rather than the
typical 25x80 one, it is necessary to resize the screen to allow a DOS
program to work full-screen. Soon, I will add an option to the
configuration to set this up at run time. On the fly resizing will
still be disabled however.
wine.ini
View file @
2f38cffa
...
...
@@ -89,4 +89,8 @@ Exclude=WM_SIZE;WM_TIMER;
[programs]
Default
=
Startup
=
\ No newline at end of file
Startup
=
[Console]
;XtermProg=nxterm
;XtermResolution=80x25
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment