bzip2-0.1pl2bzip2-0.1pl2

2 files changed, 24 insertions, 18 deletions

diff --git a/README b/README
index d77830f..d58bb49 100644
--- a/README
+++ b/README
@@ -8,7 +8,7 @@ GREETINGS!
    for details, see the file LICENSE.  Pointers to the algorithms used
    are in ALGORITHMS.  Instructions for use are in bzip2.1.preformatted.
 
-   Please read this file carefully.
+   Please read all of this file carefully.
 
 
 
@@ -223,7 +223,15 @@ DISCLAIMER:
    I very much hope the opposite is true.  bzip2 has been carefully
    constructed and extensively tested.
 
-End of nasty legalities.
+
+PATENTS:
+
+   To the best of my knowledge, bzip2 does not use any patented
+   algorithms.  However, I do not have the resources available to
+   carry out a full patent search.  Therefore I cannot give any
+   guarantee of the above statement.
+
+End of legalities.
 
 
 I hope you find bzip2 useful.  Feel free to contact me at
@@ -240,4 +248,6 @@ Manchester, UK
 25 August 1996 (version 0.21)
 
 Guildford, Surrey, UK
-7 August 1997 (bzip2, version 0.0)
\ No newline at end of file
+7 August 1997 (bzip2, version 0.1)
+29 August 1997 (bzip2, version 0.1pl2)
+
diff --git a/README.DOS b/README.DOS
index d522b81..048de8c 100644
--- a/README.DOS
+++ b/README.DOS
@@ -1,20 +1,16 @@
 

-Windows 95 & Windows NT users:

+As of today (3 March 1998) I've removed the 

+Win95/NT executables from this distribution, sorry.

 

-1.  There's a pre-built executable, bzip2.exe, which

-    should work.  You don't need to compile anything.

-    You can run the `test.bat' batch file to check

-    the executable is working ok, if you want.

+You can still get an executable from 

+http://www.muraroa.demon.co.uk, or (as a last

+resort) by mailing me at jseward@acm.org.

 

-2.  The control-C signal catcher seems pretty dodgy

-    under Windows, at least for the executable supplied.

-    When it catches a control-C, bzip2 tries to delete

-    its output file, so you don't get left with a half-

-    baked file.  But this sometimes seems to fail

-    under Windows.  Caveat Emptor!  I think I am doing

-    something not-quite-right in the signal catching.

-    Windows-&-C gurus got any suggestions?

+The reason for this change of packaging is that it

+makes it easier for me to fix problems with specific

+executables if they are not included in the main

+distribution.

 

-    Control-C handling all seems to work fine under Unix.

+J

 

-7 Aug 97

+