--- MiNT/src/purec/puremint.txt	2018/04/24 17:56:11	1.1
+++ MiNT/src/purec/puremint.txt	2018/04/24 17:56:55	1.1.1.2
@@ -1,10 +1,10 @@
-How to compile MiNT 0.96 with PureC
+How to compile MiNT 0.99 with PureC
 
 -----------------------------------
 
 
 
-Julian F. Reschke, 19. Oktober 1992
+Julian F. Reschke, 23. Januar 1993
 
 email: julian@math.uni-muenster.de
 
@@ -22,27 +22,27 @@ version differs in some small details fr
 
 can't use Pure's tos.h, either, because in its latest versions it already 
 
-defines some of MiNT's data structures. You can either leave osbind.h in 
+defines some of MiNT's data structures. You can either copy osbind.h into 
 
-the MiNT source directory, or copy it to your PureC include folder. If you 
+the MiNT source directory or copy it into your PureC include folder. If 
 
-are using the MiNT library, all should work fine without this file.
+you are using the MiNT library, all should work fine without this file.
 
 
 
 This is all what's needed. You can either use the command line versions 
 
-of PureC, or you can use the PureC shell. I am compiling MiNT with GNU 
+of PureC, or you can use the PureC shell (copy mintpure.prj to the source 
 
-make (latest version at atari.archive.umich.edu should work fine) and a 
+directory). I am compiling MiNT with GNU make (latest version at 
 
-self-made 'cc' command, that I've specially written for the PureC command 
+atari.archive.umich.edu should work fine) and a self-made 'cc' command, 
 
-line versions (see makefile.pcc). This tool is still being tested, and 
+that I've specially written for the PureC command line versions (see 
 
-I've not yet decided how to distribute it. If you are interested, write to 
+makefile.pcc). This tool is still being tested, and I've not yet decided 
 
-me.
+how to distribute it. If you are interested, write to me.
 
 
 
@@ -92,15 +92,9 @@ this guarantees nothing:
 
 There's still a conflict in the way PureC saves registers with what MiNT 
 
-file system drivers or device drivers expect. That's why minix.xfs will 
-
-bomb. There are two solutions: change it in the kernel, or change PureC. 
-
-Both are being currently considered. Note that the same problem will 
-
-arise if you try to write drivers with PureC.
-
+file system drivers or device drivers expect. You will have to use PureC 
 
+1.1 to get the correct behaviour.