X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=README.win32;fp=README.win32;h=0000000000000000000000000000000000000000;hb=da79766c5b4c4bae50ddc7bd81b610d3a45c5899;hp=2a094daa8a679fee46e67cf0bcd89a6fb92b2196;hpb=224b4e6d27a3af235500d9d8028ddbd3a60af7ed;p=debian%2Fcpmtools

diff --git a/README.win32 b/README.win32
deleted file mode 100644
index 2a094da..0000000
--- a/README.win32
+++ /dev/null
@@ -1,27 +0,0 @@
-Compiling on Win32 systems:
-
-  It's best to do this using mingw32 and standard configure commands. The 
-makefiles for Microsoft C and Borland C are pretty outdated and don't 
-understand LibDsk. 
-
-For Microsoft C++ (eg: Visual C++ 6.0):
-
-* Run the VCVARS32 command to set up the command-line compiler.
-* Build the CPMTOOLS programs with NMAKE /F MAKEFILE.MSC
-
-For Borland C++ 5.x:
-
-* Use Makefile.bcc
-
-  I have not found a working Curses library for Win32, so fsed.cpm has not
-been touched. 
-
-  Under Windows 95/98, if a program name has more than one dot, you have to
-add the ".exe" extension to the command. So you should use "fsck.cpm.exe" 
-rather than just "fsck.cpm".
-
-  If you have appropriate rights, the CPMTOOLS should be able to access
-the floppy drive by using "A:" or "B:" as the name of the disc image. 
-"mkfs.cpm" and "fsed.cpm" don't have this capability.
-
-John Elliott, 18 June 2000