home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dr. CD ROM (Annual Premium Edition)
/
premium.zip
/
premium
/
IBMOS2_1
/
MSVC_OS2.ZIP
/
READ.ME
< prev
Wrap
Text File
|
1993-09-09
|
8KB
|
219 lines
===============================================================
Instructions for Updating the Microsoft Visual C++ Command Line
Tools to Run under OS/2 2.1
===============================================================
September 1, 1993
Phar Lap Software, Inc.
60 Aberdeen Ave.
Cambridge, MA 02138
(617) 661-1510
tech-support@pharlap.com
FAX: (617) 876-2972
BBS: (617) 661-1009 300-9600 Buad, 8 data, No parity, 1 stop
====================================================================
This ZIP file contains a patch which allows the command
line tools of Microsoft Visual C++ 1.0 for Windows to
run in a DOS box of OS/2 2.1. The Visual C++ compiler
is a 16-bit compiler that targets DOS and Windows. The Visual
C++ command line tools include CL, LINK, LIB, and NMAKE.
The patch updates the DOSXNT DOS-Extender of Visual C++ to
make it compatible with OS/2 2.1. DOSXNT is a 32-bit
DOS-Extender which was licensed from Phar Lap Software by
Microsoft to run the Visual C++ command line tools.
Note: This patch only allows the Visual C++ command line
tools to be run in an OS/2 DOS box. The patch does NOT
allow the Visual Workbench to be run under OS/2. Please
see the Question and Answer section of this document
for more information about the Visual Workbench.
To install the patch, you must already have installed
Visual C++ 1.0 on your hard disk. If you haven't already
installed the compiler, do it now before proceeding.
Here are steps for applying the patch to Visual C++:
1. Start a DOS box under OS/2 2.1
2. Create a temporary directory on your disk and
make it the current directory:
MD \OS2FIX
CD \OS2FIX
3. Using PKUNZIP, unpack this zip file in the
temporary directory:
PKUNZIP OS2FIX.ZIP
4. Run the OS2FIX batch file. For its command
line argument give the path to the top-level
directory which contains the Visual C++ compiler.
Example:
OS2FIX C:\MSVC.100
5. The patch will take a few seconds to be applied.
If the patch is successful, the batch file will
print out a message saying it is done. If there
is a problem applying the patch, then OS2FIX will
output a message saying what the problem is.
6. To clean-up, all of the files in the temporary directory
can be deleted and the temporary directory can be
removed:
DEL *.*
CD ..
RMDIR OS2FIX
In order for DOSXNT to run correctly under OS/2, the DPMI
support in OS/2 must be properly configured. In particular, the
"DPMI_DOS_API" DOS setting must be set to "enabled". The default
setting of "auto" will not work properly.
Here is how to set "DPMI_DOS_API" to enabled:
1. From the Command Prompts - Icon View window, double-click with the
right mouse button on the DOS Full Screen icon to bring up the menu.
2. Choose the "Open Settings" selection.
3. Click on the "Sessions" page button.
4. Click on the "DOS Settings" button.
5. At this point, a list of options is displayed. Scroll to
"DPMI_DOS_API" and click on it to change the setting. Select
"enabled" from the Value drop-down list and click on "OK."
6. Scroll to "DPMI_MEMORY_LIMIT" and click on it to change the setting.
This setting specifies the amount of DPMI memory available to the
DOS session. OS/2 2.x supports between 0 and 512 MB of DPMI memory.
The default is 2 MB, which is not sufficient for most DOS-Extender
applications. We use 10 MB; you should choose the appropriate value
for your program. (There is no correlation between the amount of
DPMI memory and the amount of physical memory.)
7. Click on the "Save" button. This brings you back to the DOS Full
Screen Settings window.
8. Close this window to return to the OS/2 desktop.
Once OS/2 has been properly configured we recommend compiling,
linking, and running a simple test program to make sure that
the Visual C++ compiler and the updated DOSXNT have been installed
correctly.
Here are the basics for testing the compiler:
1. Double-click on the DOS Full Screen icon that has been
configured for running DPMI applications.
2. Make sure the PATH, INCLUDE, LIB, and TEMP environment
variables are properly configured for running the
Microsoft C/C++ compiler:
SET PATH=C:\MSVC.100\BIN
SET LIB=C:\MSVC.100\LIB
SET INCLUDE=C:\MSVC.100\INCLUDE
SET TEMP=C:\TEMP
3. Build a simple test program like hello world:
CL HELLO.C
where HELLO.C contains
main()
{
printf("Hello world....\n");
}
4. If the compile and link is successful, run the hello world
program:
HELLO
5. All done!
=====================
Questions and Answers
=====================
1. Why did the original version of DOSXNT.EXE that came with
Visual C++ not run under OS/2?
The original version of DOSXNT.EXE required a Windows
Virtual Device Driver (VxD) in order to run in
Windows enhanced mode. This VxD is named DOSXNT.386.
It provides enhanced memory management features not
found in either the Windows or the OS/2 DPMI servers.
Since OS/2 cannot run Windows VxDs, the original
version of DOSXNT was not compatible with OS/2 2.1.
The newer version of DOSXNT was re-engineered by Phar
Lap Software to not use the VxD, hence it is compatible
with OS/2 2.1.
2. Why can't the Visual Workbench be used under OS/2 2.1?
Since none of the Windows tools included with Microsoft Visual C++
1.0 for Windows have been tested on OS/2, Microsoft therefore
cannot guaruntee their functionality. The Visual Workbench
specifically requires support of enhanced mode Windows
for it's build engine. OS/2 doesn't provide this support and
cannot be used to invoke builds from under OS/2.
3. Will the newer version of DOSXNT run under version 2.0 of
OS/2 in addition to version 2.1 of OS/2?
Maybe, but all testing was done under OS/2 2.1 since it
is the currently shipping version of OS/2. If you are
still running version 2.0 of OS/2 we recommend upgrading
to version 2.1.
4. Why can't I build Presentation Manager applications
which target OS/2 with Visual C++?
The Visual C++ compiler only generates 16-bit code.
The compiler targets 16-bit DOS and 16-bit Windows.
Current generation Presentation Manager applications
require a compiler which generate 32-bit code.
5. Will Visual C++ 1.0 for Windows NT run under OS/2 2.1?
The command-line tools appear to run under OS/2 but have
not been tested. Therefore the support for these tools
is as mentioned in the next question. Additionally the
Windows tools will not run because they are Windows NT
applications which won't run under OS/2.
6. Can I get technical support for Visual C++ when running
under OS/2?
Yes, Microsoft Development Support will provide support
on the usage of the command-line tools but they cannot
address OS/2 specific issues. Since the compiler has not
been extensively tested under OS/2, it is recommended
that if a problem with the tools occurs under OS/2
then it should be duplicated under DOS before calling
Microsoft.
7. What about future versions of Visual C++ and other Microsoft
language products, will they be compatible with OS/2?
This patch provided by Phar Lap Software does not represent
a commitment from Microsoft that future language products will
be able to run under OS/2.