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
f71ae47f
Commit
f71ae47f
authored
Dec 16, 2002
by
Andreas Mohr
Committed by
Alexandre Julliard
Dec 16, 2002
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
- spelling corrections
- properly document how to set the DOS PATH
parent
dc85dc0a
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
38 additions
and
27 deletions
+38
-27
configuring.sgml
documentation/configuring.sgml
+21
-21
getting.sgml
documentation/getting.sgml
+4
-4
introduction.sgml
documentation/introduction.sgml
+2
-2
running.sgml
documentation/running.sgml
+11
-0
No files found.
documentation/configuring.sgml
View file @
f71ae47f
...
...
@@ -339,7 +339,7 @@ And here is a setup for Drive A, a generic floppy drive:
</para>
</sect3>
<sect3>
<sect3
id="config-wine"
>
<title>The [wine] Section </title>
<para>
The [wine] section of the configuration file contains all kinds
...
...
@@ -411,7 +411,7 @@ And here is a setup for Drive A, a generic floppy drive:
at all.
Using these things are pretty alpha, so you might want to
watch out. Some people might find it useful, however. If
you're not planning
on working
on printing via windows printer
you're not planning
to work
on printing via windows printer
drivers, don't even add this to your wine config file
(It probably isn't already in it).
Check out the [spooler] and [parallelports] sections too.
...
...
@@ -529,9 +529,9 @@ And here is a setup for Drive A, a generic floppy drive:
<term>builtin</term>
<listitem><para>
The most common form of DLL loading. This is
what you will use if the DLL is
error-prone in
native form (KERNEL for example), you don't have
the native DLL, or you just want to be
what you will use if the DLL is
to system-specific
or error-prone in native form (KERNEL for example),
you don't have
the native DLL, or you just want to be
Microsoft-free.
</para></listitem>
</varlistentry>
...
...
@@ -742,7 +742,7 @@ OPTIONAL:
<para>
The [serialports] section tells wine what serial ports it
is allowed to use.
<programlisting>"ComX" = "/dev/
cua
Y"</programlisting>
<programlisting>"ComX" = "/dev/
ttyS
Y"</programlisting>
</para>
<para>
Replace <literal>X</literal> with the number of the COM
...
...
@@ -753,7 +753,7 @@ OPTIONAL:
(<medialabel>/dev/modem</medialabel> is acceptable). It is
not always necessary to define any COM ports (An optional
setting). Here is an example:
<programlisting>"Com1" = "/dev/
cua
0"</programlisting>
<programlisting>"Com1" = "/dev/
ttyS
0"</programlisting>
</para>
<para>
Use as many of these as you like in the section to define
...
...
@@ -771,7 +771,7 @@ OPTIONAL:
0-3 (<literal>Y</literal> is usually the value in windows
minus 1, just like for COM ports). You don't always need
to define a parallel port (AKA, it's optional). As with
the other section, LptX can equal
any device (Maybe
the other section, LptX can equal any device (Maybe
<medialabel>/dev/printer</medialabel>). Here is an
example: <programlisting>"Lpt1" = "/dev/lp0"</programlisting>
</para>
...
...
@@ -815,7 +815,7 @@ OPTIONAL:
[Debug] is used to include or exclude debug messages, and to
output them to a file. The latter is rarely used. THESE
ARE ALL OPTIONAL AND YOU PROBABLY DON'T NEED TO ADD OR
REMOVE ANYTHING IN THIS SECTION TO YOUR CONFIG.
(In extreme
REMOVE ANYTHING IN THIS SECTION TO YOUR CONFIG. (In extreme
cases you may want to use these options to manage the amount
of information generated by the <parameter>--debugmsg +relay
</parameter> option.)
...
...
@@ -894,7 +894,7 @@ OPTIONAL:
<para>
[WinMM] is used to define which multimedia drivers have to be loaded. Since
those drivers may depend on the multimedia interfaces available on your system
(OSS, A
lsa
... to name a few), it's needed to be able to configure which driver
(OSS, A
LSA
... to name a few), it's needed to be able to configure which driver
has to be loaded.
</para>
...
...
@@ -952,7 +952,7 @@ OPTIONAL:
If this option is set to "Y" or missing, Wine will set the
NetBIOS name to the Unix host name of your computer, if
necessary truncated to 31 characters. The Unix hostname is the output
of the shell command <command>hostname</command>, up to
and
not
of the shell command <command>hostname</command>, up to
but
not
including the first dot ('.'). Among other things, this means that
Windows programs running under Wine cannot change the NetBIOS computer name.
</para>
...
...
@@ -961,7 +961,7 @@ OPTIONAL:
to set the NetBIOS name. Only if the registry entry doesn't exist (usually
only during the first wine startup) it will use the Unix hostname as
usual. Windows applications can change the NetBIOS name. The change
will be effective after a "
R
eboot", i.e. after restarting Wine.
will be effective after a "
r
eboot", i.e. after restarting Wine.
</para>
</listitem>
</varlistentry>
...
...
@@ -983,11 +983,11 @@ OPTIONAL:
The three parts of the section name are separated by two backslashes.
</para>
<para>
Currently wine supports o
nly overwriting the sections
[DllOverrides], [x11drv], [version] and [dsound]
.
Currently wine supports o
verriding selected settings within
the sections [DllOverrides], [x11drv], [version] and [dsound] only
.
</para>
<para>
Here is an example that over
writ
es the normal settings for a
Here is an example that over
rid
es the normal settings for a
program:
<programlisting>
;; default settings
...
...
@@ -1042,8 +1042,8 @@ OPTIONAL:
<ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>,
try the newsgroup
<systemitem>comp.emulators.ms-windows.wine</systemitem>,
or the IRC
net
channel <systemitem>#WineHQ</systemitem> found on
irc.
stealth.net:6668,
or connected servers.
or the IRC channel <systemitem>#WineHQ</systemitem> found on
irc.
openprojects.net,
or connected servers.
Make sure that you have looked over this document thoroughly,
and have also read:
</para>
...
...
@@ -1078,7 +1078,7 @@ OPTIONAL:
<para>
Most Wine users run Wine under the windowing system known as
X11. During most of Wine's history, this was the only display
driver available, but in recent years, parts of Wine ha
s
been
driver available, but in recent years, parts of Wine ha
ve
been
reorganized to allow for other display drivers (although the
only alternative currently available is Patrik Stridvall's
ncurses-based ttydrv, which he claims works for displaying
...
...
@@ -1119,10 +1119,10 @@ OPTIONAL:
title bars, and system menus will be managed by your
window manager. This lets these applications integrate
better with the rest of your desktop, but may not
always work perfectly
. (A
rewrite of this mode of
always work perfectly
(a
rewrite of this mode of
operation, to make it more robust and less patchy, is
currently being done, though, and it's planned to be
finished before the Wine 1.0 release
.)
finished before the Wine 1.0 release
).
</para>
</listitem>
</varlistentry>
...
...
@@ -1130,7 +1130,7 @@ OPTIONAL:
<term>Unmanaged/Normal</term>
<listitem>
<para>
Window
-manager-
independent (any running
Window
manager
independent (any running
window manager is ignored completely). Window
decorations (title bars, borders, etc) are drawn by
Wine to look and feel like the real Windows. This is
...
...
documentation/getting.sgml
View file @
f71ae47f
...
...
@@ -21,7 +21,7 @@
Often a package will only work on the distribution it's
compiled for. We'll cover
<link linkend="getting-dist-debian">Debian</link>,
<link linkend="getting-dist-redhat">Red
h
at</link>, and
<link linkend="getting-dist-redhat">Red
H
at</link>, and
<link linkend="getting-dist-other">other</link> distributions.
</para>
<para>
...
...
@@ -109,10 +109,10 @@ Password:
</sect1>
<sect1 id="getting-dist-redhat">
<title>Getting Wine for a Red
h
at System</title>
<title>Getting Wine for a Red
H
at System</title>
<para>
Red
h
at/RPM users can use <ulink url="http://rpmfind.net/linux/RPM/">
Red
H
at/RPM users can use <ulink url="http://rpmfind.net/linux/RPM/">
rpmfind.net</ulink> to track down available Wine RPM binaries.
<ulink url="http://rpmfind.net/linux/RPM/WByName.html"> This
page</ulink> contains a list of all rpmfind packages that start with
...
...
@@ -144,7 +144,7 @@ Password:
<para>
The first place you should look if your system isn't Debian or
Red
h
at is the <ulink
Red
H
at is the <ulink
url="http://www.winehq.com/download/">WineHQ Download
Page</ulink>. This page lists many assorted archives of
binary (precompiled) Wine files.
...
...
documentation/introduction.sgml
View file @
f71ae47f
...
...
@@ -115,7 +115,7 @@
<ulink url="http://bugs.winehq.com/">Wine's Bugzilla</ulink> to
let us know how this document can be improved. Remember, Open
Source is "free as in free speech, not as in free beer": it can
only work in the case of very active involvement
by
its users !
only work in the case of very active involvement
of
its users !
</para>
</sect2>
</sect1>
...
...
@@ -166,7 +166,7 @@
<para>
<literallayout>A computer ;-)</literallayout>
<literallayout> Wine: only PCs >= i386 are supported at the moment.</literallayout>
<literallayout> Winelib:
other platforms may b
e supported, but can be tricky.</literallayout>
<literallayout> Winelib:
selected other platforms ar
e supported, but can be tricky.</literallayout>
</para>
</listitem>
<listitem>
...
...
documentation/running.sgml
View file @
f71ae47f
...
...
@@ -296,6 +296,17 @@ winspool</><entry>wnet</><entry>x11</>
place the setting into /etc/profile, or also ~/.bashrc in the case of
bash.
</para>
<para>
Note however that there is an exception to the rule:
If you want to change the PATH environment variable, then of
course you can't modify it that way, since this will alter the
Unix PATH environment setting. Instead, you should set the
WINEPATH environment variable. An alternative way to
indicate the content of the DOS PATH environment variable would
be to change the "path" setting in the wine config file's <link
linkend="config-wine">[wine]</link> section.
</para>
</sect1>
</chapter>
...
...
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