Changes between Version 1 and Version 2 of BuildingFAT32

Timestamp:

Nov 8, 2016, 4:18:22 PM (8 years ago)

Author:

martini

Comment:

fixed format

BuildingFAT32

@@ -2 +2 @@
 
 = REQUIREMENTS: =
+You require the following software:
 
--the IFS DDK Build Environment 
-
--IBM VAC 3 
-
--OS/2 Toolkit 4.5 (included with OS/2 ACP/MCPs and eCS) 
-
--IBM DDK sources and tools (no longer available at IBM's DDK site) 
-
--IBM C 
-
--the System utilities (including link.exe)
-
--FAT32 source code 
+* The IFS DDK Build Environment 
+* IBM VisualAge for C 3 
+* OS/2 Toolkit 4.5 (included with OS/2 ACP/MCPs and eCS) 
+* IBM DDK sources and tools (no longer available at IBM's DDK site) 
+* IBM C 
+* The System utilities (including link.exe)
+* FAT32 source code 
 
 = COMPILING: =
@@ -21 +16 @@
 To get a build going, you'll need several things; 
 
-You should have VisualAge installed and it's environment variables set. Then set these 3 variables: 
+You should have VisualAge for C installed and it's environment variables set. Then set these 3 variables: 
 
 SET DDK=d:\ddk[[BR]]
@@ -27 +22 @@
 SET IBMC=d:\ibmc[[BR]] 
 
-Correct the paths as neccessary. 
+Correct the paths as necessary. 
 
 Then run the make.cmd script, and if all goes well you should have a fresh build of FAT32.IFS. 
 
-Note: There are many warning when compiling FAT32. Most of them are 'optimizing' warnings or 'unreference variable' warnings. Essentially, these warnings mean that certain functions cannot be optimized and that some vars/const are never referenced. The resulting binaries work however. 
+'''Note:''' There are many warning when compiling FAT32. Most of them are 'optimizing' warnings or 'unreference variable' warnings. Essentially, these warnings mean that certain functions cannot be optimized and that some vars/const are never referenced. The resulting binaries work however.