docu update
Andreas Mohr
andi at rhlx01.fht-esslingen.de
Sat Feb 23 10:32:32 CST 2002
Hi all,
- stress the fact that wineinstall is in Wine *source*
- add missing ttydrv/x11drv section to wine.conf.man
- make sure that we also load shdocvw as builtin in sample config file
(to be justified later)
- add sample AppDefaults section to sample config file
- winecheck update
- more verbose crash message
--
Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany
-------------- next part --------------
Determining best CVS host...
Using CVSROOT :pserver:cvs at rhlx01.fht-esslingen.de:/home/wine
Index: README
===================================================================
RCS file: /home/wine/wine/README,v
retrieving revision 1.31
diff -u -r1.31 README
--- README 2 Feb 2002 18:03:55 -0000 1.31
+++ README 23 Feb 2002 14:31:12 -0000
@@ -14,14 +14,14 @@
2. QUICK START
Whenever you compile from source, it is recommended to use the Wine
-Installer to build and install Wine. From the top-level Wine
-directory (which contains this file), run:
+Installer to build and install Wine. From the top-level directory
+of the Wine source (which contains this file), run:
./tools/wineinstall
Run programs as "wine [options] program". For more information and
problem resolution, read the rest of this file, the Wine man page,
-the files in the documentation directory in the Wine source
+the files in the documentation directory of the Wine source
(see "DOCUMENTATION"), and especially the wealth of information
found at http://www.winehq.com.
@@ -38,7 +38,7 @@
Although Linux version 2.0.x will mostly work, certain features
(specifically LDT sharing) required for properly supporting Win32
threads were not implemented until kernel version 2.2. If you get
- consistent thread-related crashes, you may want to upgrade to 2.2.
+ consistent thread-related crashes, you may want to upgrade to at least 2.2.
Also, some bugs were fixed and additional features were added
late in the Linux 2.0.x series, so if you have a very old Linux kernel,
you may want to upgrade to at least the latest 2.0.x release.
@@ -63,7 +63,10 @@
File systems info:
Wine should run on most file systems. However, Wine will fail to start
if umsdos is used for the /tmp directory. A few compatibility problems have
- also been reported using files accessed through Samba.
+ also been reported using files accessed through Samba. Also, as NTFS
+ can only be used safely with readonly access for now, we recommend against
+ using NTFS, as Windows programs need write access almost everywhere.
+ In case of NTFS files, copy over to a writable location.
Wine requires kernel-level threads to run. Currently, only Linux
version 2.0 or later, FreeBSD-current or FreeBSD 3.0 or later,
@@ -128,7 +131,7 @@
before installing.
If you want to read the documentation supplied with the Wine source,
-then see the "DOCUMENTATION" section.
+see the "DOCUMENTATION" section.
Wine requires a configuration file named named "config" in your
~/.wine directory. The format of this file is explained in the config file
@@ -137,16 +140,22 @@
which has to be adapted and copied to the location mentioned above.
Don't forget to add vital registry entries by applying winedefault.reg
-with programs/regapi/. See documentation/ for details.
+with programs/regapi/. See documentation/ directory for details.
See http://www.winehq.com/support.shtml for further configuration hints.
+In case of library loading errors
+(e.g. "Error while loading shared libraries: libntdll.so"), make sure
+to add the library path to /etc/ld.so.conf and run ldconfig as root.
+
In order to verify the correctness of the environment you need for
-Wine to run successfully, run "./tools/winecheck | less". You'll get
-a percentage score indicating "Wine configuration correctness".
+Wine to run successfully, you may run "./tools/winecheck | less".
+You'll get a percentage score indicating "Wine configuration correctness".
As this program is alpha, it doesn't run a truly thorough test yet, though,
so it should be taken as a first verification step only.
+See wine.conf man page on how to switch to text mode only support if desired.
+
6. RUNNING PROGRAMS
When invoking Wine, you may specify the entire path to the executable,
@@ -166,9 +175,10 @@
Wine is not yet complete, so several programs may crash. Provided you set up
winedbg correctly according to documentation/debugger.sgml, you will be dropped
-into a debugger so that you can investigate and fix the problem. For more
-information on how to do this, please read the file documentation/debugging.
-If you post a bug report, please read the file documentation/bugreports to
+into a debugger so that you can investigate and fix the problem.
+For more information on how to do this, please read the file
+documentation/debugging.sgml.
+If you post a bug report, please read the file documentation/bugs.sgml to
see what information is required.
You should backup all your important files that you give Wine access
@@ -205,7 +215,7 @@
Usenet: The best place to get help or to report bugs is the Usenet newsgroup
comp.emulators.ms-windows.wine. Please read the file
- documentation/bugreports to see what information should be included
+ documentation/bugs.sgml to see what information should be included
in a bug report.
Please browse old messages on http://groups.google.com/ to check
Index: documentation/debugger.sgml
===================================================================
RCS file: /home/wine/wine/documentation/debugger.sgml,v
retrieving revision 1.9
diff -u -r1.9 debugger.sgml
--- documentation/debugger.sgml 12 Jan 2002 21:15:36 -0000 1.9
+++ documentation/debugger.sgml 23 Feb 2002 14:31:13 -0000
@@ -1010,7 +1010,8 @@
<note>
<title>Note 2</title>
<para>
- <command>wineinstall</command> sets up this correctly.
+ <command>wineinstall</command> (available in Wine source)
+ sets up this correctly.
However, due to some limitation of the registry installed,
if a previous Wine installation exists, it's safer to
remove the whole
Index: documentation/installing.sgml
===================================================================
RCS file: /home/wine/wine/documentation/installing.sgml,v
retrieving revision 1.4
diff -u -r1.4 installing.sgml
--- documentation/installing.sgml 26 Sep 2001 23:02:31 -0000 1.4
+++ documentation/installing.sgml 23 Feb 2002 14:31:13 -0000
@@ -52,7 +52,7 @@
<para>
While the users are of course free to set up everything
- themselves, the Wine team will make the automated Wine
+ themselves, the Wine team will make the automated Wine source
installation script, <filename>tools/wineinstall</filename>,
do everything we find necessary to do; running the
conventional <userinput>configure && make depend && make && make
Index: documentation/registry.sgml
===================================================================
RCS file: /home/wine/wine/documentation/registry.sgml,v
retrieving revision 1.4
diff -u -r1.4 registry.sgml
--- documentation/registry.sgml 26 Dec 2001 20:40:48 -0000 1.4
+++ documentation/registry.sgml 23 Feb 2002 14:31:13 -0000
@@ -206,7 +206,7 @@
</screen>
<para>
Note that the <filename>tools/wineinstall</filename> script
- already does all of this for you, if you install Wine as root.
+ already does all of this for you, if you install Wine source as root.
If you then install Windows applications while logged in as
root, all your users will automatically be able to use them.
While the application setup will be taken from the global
@@ -235,12 +235,11 @@
install applications are distributed in a file called
<filename>winedefault.reg</filename>. It is automatically
installed for you if you use the
- <filename>tools/wineinstall</filename> script, but if you want
- to install it manually, you can do so by using the
- <command>regapi</command> tool. You can find more information
- about this in the
- <filename>documentation/no-windows</filename> document in the
- Wine distribution.
+ <filename>tools/wineinstall</filename> script in the Wine source,
+ but if you want to install it manually, you can do so by using the
+ <command>regapi</command> tool to be found in the
+ <filename>programs/regapi/</filename>
+ directory in Wine source.
</para>
</sect2>
Index: documentation/wine.conf.man
===================================================================
RCS file: /home/wine/wine/documentation/wine.conf.man,v
retrieving revision 1.1
diff -u -r1.1 wine.conf.man
--- documentation/wine.conf.man 14 Feb 2002 19:47:31 -0000 1.1
+++ documentation/wine.conf.man 23 Feb 2002 14:31:14 -0000
@@ -145,6 +145,14 @@
Used to specify the path which will be used to find executables and
dlls. Make sure to double the backslashes.
.PP
+.I format: """GraphicsDriver""=""<x11drv|ttydrv>"""
+.br
+default: "x11drv"
+.br
+Tells Wine which graphics driver to use. Normally you'd want to use
+x11drv (for X11). In case you want to run programs as text console/TTY only
+without having Wine rely on X11 support, then use ttydrv.
+.PP
.B [DllOverrides]
.br
.I format: """modulename""=""native,so,builtin"""
Index: documentation/samples/config
===================================================================
RCS file: /home/wine/wine/documentation/samples/config,v
retrieving revision 1.18
diff -u -r1.18 config
--- documentation/samples/config 31 Jan 2002 21:48:59 -0000 1.18
+++ documentation/samples/config 23 Feb 2002 14:31:14 -0000
@@ -81,6 +81,7 @@
"shell32" = "builtin, native"
"shfolder" = "builtin, native"
"shlwapi" = "builtin, native"
+"shdocvw" = "builtin, native"
"lzexpand" = "builtin, native"
"lz32" = "builtin, native"
"comctl32" = "builtin, native"
@@ -239,5 +240,20 @@
"Drivers" = "wineoss.drv"
"WaveMapper" = "msacm.drv"
"MidiMapper" = "midimap.drv"
+
+;; sample AppDefaults entries
+;[AppDefaults\\iexplore.exe\\DllOverrides]
+;"shlwapi" = "native"
+;"rpcrt4" = "native"
+;"ole32" = "native"
+;"shdocvw" = "native"
+;"wininet" = "native"
+;"shfolder" = "native"
+;"shell32" = "native"
+;"shell" = "native"
+;"comctl32" = "native"
+;
+;[AppDefaults\\setup.exe\\x11drv]
+;"Desktop" = "800x600"
# </wineconf>
Index: tools/winecheck
===================================================================
RCS file: /home/wine/wine/tools/winecheck,v
retrieving revision 1.5
diff -u -r1.5 winecheck
--- tools/winecheck 6 Nov 2001 22:22:53 -0000 1.5
+++ tools/winecheck 23 Feb 2002 14:31:14 -0000
@@ -592,7 +592,7 @@
}
else
{
- Do_PrintResult($is_critical, "entry \"Default Taskbar\" not found", "Windows registry does not seem to be added to Wine, as this typical Windows registry entry does not exist in Wine's registry. This can affect many newer programs. Original registry entries won't be available with a no-windows install, of course, so you'll have to live with that.");
+ Do_PrintResult($is_critical, "entry \"Default Taskbar\" not found", "Windows registry does not seem to be added to Wine, as this typical Windows registry entry does not exist in Wine's registry. This can affect many newer programs. A complete original Windows registry entry set will *not* be available with a no-windows install, of course, so you'll have to live with that.");
}
@entries = ();
}
Index: win32/except.c
===================================================================
RCS file: /home/wine/wine/win32/except.c,v
retrieving revision 1.50
diff -u -r1.50 except.c
--- win32/except.c 30 Nov 2001 18:46:55 -0000 1.50
+++ win32/except.c 23 Feb 2002 14:31:14 -0000
@@ -201,8 +201,7 @@
DWORD format_size;
BOOL ret = FALSE;
- MESSAGE("wine: Unhandled exception, starting debugger...\n");
-
+ MESSAGE("Wine: Unhandled exception/crash occurred -> trying to start debugger as configured in registry file...\n");
if (!RegOpenKeyA(HKEY_LOCAL_MACHINE,
"Software\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug", &hDbgConf)) {
DWORD type;
More information about the wine-patches
mailing list