linux build

Microsoft C v4/S1.@@@

@@ -1,11 +0,0 @@
-							Machine Menu
-
-Which type of computer are you using?
-
-  I    IBM (TM) Personal Computer
-
-  C    IBM-compatible computer
-
-  N    MS-DOS computer that is not IBM compatible
-
-Press the letter of your selection: 

Microsoft C v4/S10.@@@

@@ -1,17 +0,0 @@
-A common debugging technique is to establish a situation in
-which you know the results your program should produce, then
-see if the program actually produces those results. This
-method is used in the sample session.
-
-During the session, the debugger examines a simple program
-called COUNT. This program counts the letters, words, sentences,
-and other elements in a text file. The program contains a bug
-that will be found and analyzed during the session.
-
-To test the program, a text file called COUNT.TXT is provided.
-The words, sentences, letters, bytes, and other elements in
-COUNT.TXT have been counted by hand, and noted in the file itself.
-During debugging, the numbers in the text file will be compared
-to the numbers counted by the program. Any differences will
-be a clue to help locate the bug.
-

Microsoft C v4/S11.@@@

@@ -1,9 +0,0 @@
-
-The rest of the session may be more helpful if you have a
-printed listing of the source file, COUNT.C, and the file
-to be analyzed, COUNT.TXT. If you have a printer that can
-be accessed through the PRN device, you can now print these
-files. Make sure your printer is properly attached to the
-computer, that the power is on, and that the paper is adjusted.
-
-Do you want to print COUNT.C and COUNT.TXT? (Y/N) 

Microsoft C v4/S12.@@@

@@ -1,23 +0,0 @@
-The debugger will be started with the following command line:
-
-	CVR /W /S /M "/C<COUNT.R" COUNT COUNT.TXT
-
-The elements of the command line are explained below:
-
-  - CVR is the program name of the restricted debugger.
-  - /W is an option that specifies window mode.
-  - /S is an option that specifies screen swapping as the
-    screen-exchange mode.
-  - /M is an option that turns off the mouse if you have one.
-  - "/C<COUNT.R" is an option that specifies that, on start-up,
-    commands will be redirected from COUNT.R to the debugger.
-  - COUNT is the executable file (the .EXE extension is assumed).
-  - COUNT.TXT is the file to be processed by COUNT.EXE.
-
-Your command line may also include the /B, /I, or /D options,
-depending on selections made at previous menus. See the
-CODEVIEW.DOC file for more information on command lines.
-
-The debugger will now be started. Loading and initial processing
-may take a moment . . .
-

Microsoft C v4/S13.@@@

@@ -1,16 +0,0 @@
-The program `PI' calculates the value of pi to whatever
-precision you specify on the command line. Unlike other
-sample programs on the demonstration disk, `PI.EXE' was
-compiled from two source modules: `PI.C' and `MATH.C'.
-
-The session opens the debugger with `PI' as the program to
-be debugged. The number 60 is passed as a parameter so that
-`PI' will calculate pi to 60 decimal places.
-
-To quit, enter `Q' or select Quit from the File menu. For
-on-line help, press F1 or select Help from the View menu.
-Other than that, you're on your own. Good luck!
-
-The debugger will now be started. Loading and initial
-processing may take a moment . . .
-

Microsoft C v4/S14.@@@

@@ -1,12 +0,0 @@
-
-If your computer is not IBM compatible, you will not be able
-to run the sample session. You can still use the CodeView (TM)
-debugger in sequential mode, as described in the CODEVIEW.DOC
-file, which summarizes the CodeView commands and options. 
-
-If you have a printer that can be accessed through the PRN
-device, you can print CODEVIEW.DOC now. Make sure your printer
-is properly attached to the computer, that the power is on,
-and that the paper is adjusted.
-
-Do you want to print CODEVIEW.DOC? (Y/N) 

Microsoft C v4/S2.@@@

@@ -1,21 +0,0 @@
-
-A few IBM-compatible computers require the /D CodeView
-option. The following are known to require this option:
-
-     Tandy 1000            AT&T 6300 Plus 
-
-Computers that work without /D include the following:
-
-     Compaq                Eagle           
-     HP Vectra             TI Business Professional
-     AT&T 6300             Zenith (except model 100)
-     Tandy 1200 or 3000    NCR PC
-
-If your computer is not mentioned, try the session first
-without /D. If you have trouble, try again with /D. If you
-still have trouble, your computer isn't compatible. 
-
-If you use the /D option, the CONTROL-C and CONTROL-BREAK
-keys cannot be used to break out of the sample session.
-
-Do you want to try the /D option? (Y/N) 

Microsoft C v4/S3.@@@

@@ -1,11 +0,0 @@
-							Equipment Menu
-
-Which type of display adapter and monitor are you using?
-
-  M    Monochrome monitor and monochrome adapter
-
-  B    Black-and-white monitor and graphics adapter
-
-  C    Color monitor and graphics adapter
-
-Press the letter of your selection: 

Microsoft C v4/S4.@@@

@@ -1,21 +0,0 @@
-Welcome to the CodeView (TM) debugger.
-
-Now the world-class Microsoft (R) C Compiler comes with a
-world-class debugger. During this session, you'll see it
-in action. You can learn how to use it and try it on your
-own. By that time, we think you'll be ready to buy it.
-
-The CodeView demonstration disk is freely copyable. You may
-give the disk to friends, upload it to electronic bulletin
-boards, or distribute it through computer clubs. Read the
-CODEVIEW.DOC file for more information about distribution
-and use of the demonstration disk.
-
-The debugger on this disk (CVR.EXE) is a restricted version
-that can only be used with the three sample programs. The
-unrestricted version (CV.EXE) comes with Version 4.0 of the
-Microsoft C Compiler.
-
-     Copyright (C) Microsoft Corporation 1986
-                All rights reserved
-

Microsoft C v4/S5.@@@

@@ -1,20 +0,0 @@
-							Demonstration Menu
-
-Which demonstration do you want to see?
-
-     D  Demonstrates CodeView features. This selection uses
-        a graphics program and requires a graphics adapter.
-
-     P  Prints the documentation file, CODEVIEW.DOC.
-
-     T  Teaches you about CodeView debugging. During this
-        session, a sample program is automatically examined
-        and debugged. The session demonstrates and explains
-        most CodeView commands.
-
-     E  Enables you to experiment by examining a program that
-        calculates the value of pi.
-
-     Q  Quits the sample session.
-
-Press the letter of your selection: 

Microsoft C v4/S6.@@@

@@ -1,8 +0,0 @@
-The documentation file, CODEVIEW.DOC, summarizes the
-CodeView commands and options. If you have a printer
-that can be accessed through the PRN device, you can
-print this file. Make sure your printer is properly
-attached to the computer, that the power is on, and
-that the paper is adjusted.
-
-Do you want to print CODEVIEW.DOC now? (Y/N) 

Microsoft C v4/S7.@@@

@@ -1,8 +0,0 @@
-If you have a mouse, you can probably use it with the
-CodeView debugger. However, the debugger is not guaranteed
-to work correctly if your computer is not completely IBM
-compatible or if your mouse is not a Microsoft Mouse. A
-few non-IBM machines will not run the debugger at all with
-a mouse.
-
-Do you want to try using the mouse? (Y/N) 

Microsoft C v4/S8.@@@

@@ -1,13 +0,0 @@
-
-Powerful, flexible, easy to use--the Microsoft CodeView
-debugger does what you want a debugger to do. And it lets
-you work the way you want to work.
-
-You can debug at the source or assembly level. Commands
-can be entered with menus, function keys, a mouse, or
-command lines. Multiple windows display all the information
-you need when you need it. Debugging graphics programs is
-a snap with the CodeView debugger.
-
-But don't take our word for it. See for yourself.
-

Microsoft C v4/S9.@@@

@@ -1,17 +0,0 @@
-The CodeView debugger is a powerful tool for serious debugging.
-This session uses a practical example to introduce you to
-CodeView commands. Each step in the debugging process is
-explained as it is performed. The session is quite detailed
-and takes 20 to 30 minutes.
-
-You control the pace. The session periodically pauses and asks
-you to press the SPACEBAR. Although keystrokes and commands
-are discussed on the screen, you should NOT try to type them.
-The session does this automatically. Just press the SPACEBAR.
-
-You can quit the session after the debugger is started by first 
-pressing CONTROL-C or CONTROL-BREAK, then pressing the SPACEBAR. 
-The word `break' will appear, followed by the CodeView prompt 
-(the greater-than symbol). At the prompt, enter `Q' for Quit. 
-The debugger will terminate.
-

Microsoft C v4/m.bat

@@ -9,7 +9,7 @@ ntvdm -r:. cl /Ox /DDOSTIME /AS /Gs /Ze -I inc -I inc\sys -L lib %1.c
 if %ERRORLEVEL% NEQ 0 goto alldone
 
 rem use "ntvdm link /help" to get command-line arguments
-ntvdm -r:. -e:lib=lib -h -t link %1,,%1,slibfp
+ntvdm -r:. -e:lib=lib -h link %1,,%1,slibfp
 if %ERRORLEVEL% NEQ 0 goto alldone
 
 ntvdm -r:. -p %1

Microsoft C v4/m.sh

@@ -0,0 +1,15 @@
+str=$(tr '[a-z]' '[A-Z]' <<< $1)
+
+rm $str.COD 2>/dev/null
+rm $str.MAP 2>/dev/null
+rm $str.OBJ 2>/dev/null
+rm $str.EXE 2>/dev/null
+
+ntvdm -u -r:. -h cl /Ox /DDOSTIME /AS /Gs /Ze -I inc -I inc\\sys -L lib $str.c
+ntvdm -u -r:. -e:lib=lib -h link $str,,$str,slibfp
+
+rm $str.COD 2>/dev/null
+rm $str.MAP 2>/dev/null
+rm $str.OBJ 2>/dev/null
+
+ntvdm -r:. -c -p $str