- update for 1.3.pre1

bochs/README

@@ -1,6 +1,6 @@
 Bochs x86 Pentium Emulator
-Upated: Tue Jun 12 13:54:43 EDT 2001
-Version: 1.2.1
+Upated: Sat Nov 17 20:38:18  2001
+Version: 1.3.pre1
 
 WHAT IS BOCHS?
 
@@ -32,70 +32,18 @@ snapshot which is updated nightly.  The releases contain the most
 stable code, but if you want the very newest features try the
 CVS version instead. 
 
-COMPILING BOCHS FROM SOURCES
-
-All releases are gzip'd tar files.  That means the whole Bochs source
-code directory has been consolidated into one file using the Unix
-command 'tar', then compressed to save space with GNU 'gzip'.  To
-extract the source code, you'll need both 'tar' and 'gzip/gunzip'.
-All files are contained within one subdirectory named 'bochs-[VERSION]'. 
-
-cd /path/parent-directory
-gzip -dc bochs-[VERSION].tar.gz | tar -xvf -
-cd bochs-[VERSION]
-
-Before compiling, you'll need to run the configure script, which
-will configure source code to run on your system, and with your
-chosen options.  There are many options to 'configure', and you
-probably don't need any of them.  If you run BeOS, specify
-'--with-beos' to configure.  To see a complete list: 
-
-unix-> ./configure --help
-
-For more complete documentation of options available to configure,
-look at docs-html/configure.html in your browser.
-
-If configure cannot guess your compiler and compiler arguments,
-you will also need to set environment variables to tell configure
-what compiler and options to use.  The relevant environment variables 
-are CC and CXX (C and C++ compiler), CFLAGS and CXXFLAGS (options
-for the C and C++ compiler).
-
-Now run configure, be it manually or by way of a script file. 
-
-unix-> ./configure
--or-
-unix-> ./.conf.x86
-
-If the configure script bombs, check 'config.log'. Specifically,
-look for errors returned by the compiler.  You may have options
-incompatible with your compiler.  See the link on setting the
-environment variables above. 
-
-Assuming at this point all went well with the configure command,
-edit the file 'config.h', which was generated by ./configure.  Look
-for the USER CONFIGURABLE OPTIONS section.  Each parameter available
-for editing is documented.  Generally the defaults are fine for
-typical users.  Please read about each parameter and edit carefully.
-NOTE: This file is generated, and will be deleted if you run 'make
-dist-clean'. 
-
-You may now compile the source. 
-
-unix-> make
-
 WHERE ARE THE DOCS?
 
-You have a local copy of the Bochs documentation in docs-html that
-came out of the TAR file.  (Point your browser to
-docs-html/index.html.)  These same docs are also on the web at
-http://bochs.sourceforge.net/docs-html.  If you followed the compile
-directions above, the next step is "Setting up the environment
-before running" under Compile/Install.
+The Bochs documentation has been overhauled, and it is now
+distributed in a separate package called bochsdoc-VERSION.tar.gz.
+A copy is also online at 
+  http://bochs.sf.net/doc/docbook/alldocs.html
+For now, the old documentation can still be found at
+  http://bochs.sf.net/docs-html
 
 WHERE CAN I GET MORE INFORMATION?  HOW DO I REPORT PROBLEMS?
 
-Both the docs-html and the Bochs website have instructions on how 
+Both the documentation and the Bochs website have instructions on how 
 to join the bochs-developers mailing list, which is the primary
 forum for discussion of Bochs.  The main page of the website also
 has links to bug reports and feature requests.  You can browse and
@@ -124,9 +72,9 @@ bochs-developers list to avoid several people working on the same
 thing without realizing it.
 
 If you are a Bochs user, not a hardware/C++ guru, there are still
-many ways you could help out.  We have a group of people working on
-making win32 binary releases, and building up a set of useful tools
-to include in those releases.  Others are writing documentation or
-cleaning up the existing documentation.  Others are testing out
-Bochs on every imaginable operating system and writing about how
-they did it.
+many ways you could help out.  For example:
+  - improving win32 binary releases
+  - building up a set of useful tools to include in those releases
+  - writing/cleaning up documentation
+  - testing out Bochs on every imaginable operating system and 
+    reporting how it goes.