docu patch

Tue Jun 26 20:04:08 CDT 2001

Hi all,

the README was quite outdated again.
Also updated DEVELOPERS-HINTS slightly.

Andreas Mohr
-------------- next part --------------
Determining best CVS host...
Using CVSROOT :pserver:cvs at rhlx01.fht-esslingen.de:/home/wine
Index: DEVELOPERS-HINTS
===================================================================
RCS file: /home/wine/wine/DEVELOPERS-HINTS,v
retrieving revision 1.9
diff -u -r1.9 DEVELOPERS-HINTS

--- DEVELOPERS-HINTS	2001/01/10 23:59:25	1.9
+++ DEVELOPERS-HINTS	2001/06/26 23:02:00
@@ -23,6 +23,7 @@
 
 GDI:
 
+	console/		- handling of text consoles
 	graphics/		- graphics drivers
 		x11drv/		- X11 display driver
 		win16drv/	-> see below 
@@ -58,7 +59,7 @@
 		msnet/
 		msvcrt/		- C runtime library
 		msvideo/	- 16 bit video manager
-		ole32/		- 32 bit OLE 2.0 librairies
+		ole32/		- 32 bit OLE 2.0 libraries
 		oleaut32/	- 32 bit OLE 2.0 automation
 		olecli/		- 16 bit OLE client
 		oledlg/		- OLE 2.0 user interface support
@@ -86,12 +87,13 @@
 
 Miscellaneous:
 
-	misc/			- shell, registry, winsock, etc.
+	misc/			- misc. wine management, registry, etc.
 	ipc/			- SysV IPC based interprocess communication
-	win32/			- misc Win32 functions
         ole/			- OLE code 
-		nls/		- National Language Support 
+	nls/			- National Language Support 
 				  configuration files
+	unicode/		- Unicode (character) support
+	win32/			- misc Win32 functions
 
 Tools:
 ------
Index: README
===================================================================
RCS file: /home/wine/wine/README,v
retrieving revision 1.23
diff -u -r1.23 README
--- README	2001/04/09 18:32:16	1.23
+++ README	2001/06/26 23:02:00
@@ -3,9 +3,10 @@
 Wine is a program which allows running Microsoft Windows programs
 (including DOS, Windows 3.x and Win32 executables) on Unix.  It
 consists of a program loader which loads and executes a Microsoft
-Windows binary, and a library that implements Windows API calls using
-their Unix or X11 equivalents. The library may also be used for
-porting Win32 code into native Unix executables.
+Windows binary, and a library (called WineLib) that implements
+Windows API calls using their Unix or X11 equivalents.
+The library may also be used for porting Win32 code
+into native Unix executables.
 
 Wine is free software, and its license (contained in the file LICENSE)
 is BSD style.  Basically, you can do anything with it except claim
@@ -20,8 +21,9 @@
 ./tools/wineinstall
 
 Run programs as "wine [options] program".  For more information and
-problem resolution, read the rest of this file, the Wine manpage,
-and the files in the documentation directory in the Wine source.
+problem resolution, read the rest of this file, the Wine man page,
+the files in the documentation directory in the Wine source, and
+especially the wealth of information found at http://www.winehq.com.
 
 3. REQUIREMENTS
 
@@ -44,7 +46,7 @@
   On FreeBSD, you may want to apply an LDT sharing patch too
   (unless you are tracking -current where it finally has
   been committed just recently), and there also is a small sigtrap
-  fix thats needed for wine's debugger. (Actually now that its using
+  fix that's needed for wine's debugger. (Actually now that it's using
   ptrace() by default it may no longer make a difference but it still
   doesn't hurt...) And if you're running a system from the -stable
   branch older than Nov 15 1999, like a 3.3-RELEASE, then you also
@@ -136,13 +138,15 @@
 configuring wine by using the --prefix or --sysconfdir options to
 ./configure. You can also override the global configuration file with
 a file named "config" in your ~/.wine directory.
+NOTE: support for global config file /usr/local/etc/wine.conf has been
+removed. For now, use ~/.wine/config instead.
 
+
 The format of this file is explained in the man page. The file
 documentation/samples/config contains an example configuration file
-which has to be adapted and copied to one of the two locations
-mentioned above.
+which has to be adapted and copied to the location mentioned above.
 
-See http://www.winehq.com/config.html for further configuration hints.
+See http://www.winehq.com/support.shtml for further configuration hints.
 
 In order to verify the correctness of the environment you need for
 Wine to run successfully, run "./tools/winecheck | less".  You'll get
@@ -181,12 +185,20 @@
 
 7. GETTING MORE INFORMATION
 
+Most of the available documentation (> 60%) is available online
+at http://www.winehq.com. Read it !
+A lot of user questions would get resolved by simple RTFM instead of
+blindly asking for help. We do have rich troubleshooting content at WineHQ
+to solve very many seemingly fatal errors.
+
+Miscellaneous items:
 DOCU:	grep -i "SearchString" `find documentation/`|more
 
 FAQ:	The Wine FAQ is located at http://www.winehq.com/FAQ
 
 WWW:	A great deal of information about Wine is available from WineHQ at
-	http://www.winehq.com/, especially various user guides.
+	http://www.winehq.com/ : various user guides, application database,
+	bug tracking, ...
         Untested patches against the current release
 	are available on the wine-patches mailing list; see 
 	http://www.winehq.com/dev.shtml#ml for more information.
@@ -194,24 +206,23 @@
 HOWTO:	The Wine HOWTO is available at
 	http://www.westfalen.de/witch/wine-HOWTO.txt .
 
-Usenet:	Please browse old messages on http://www.dejanews.com/ to check whether 
-	your problem is already fixed before posting a bug report to the 
-	newsgroup. 
+Usenet:	Please browse old messages on http://groups.google.com/ to check
+	whether your problem is already fixed before posting a bug report
+	to the newsgroup. 
 
 	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 
 	in a bug report.
 
-IRC:	Online help is available at channel #WineHQ on IRCnet.
+IRC:	Online help is available at channel #WineHQ on irc.openprojects.net.
 
 CVS:	The current Wine development tree is available through CVS.
 	Go to http://www.winehq.com/dev.shtml for more information.
 
 If you add something, or fix a bug, please send a patch ('diff -u'
-format preferred) to julliard at winehq.com or to the
-wine-patches at winehq.com mailing list for inclusion in the next
-release.
+format preferred) to julliard at winehq.com or to the wine-patches at winehq.com
+mailing list for inclusion in the next release.
 
 --
 Alexandre Julliard
