DATE: 27/Jan/94

The purpose of this package is to provide Microsoft Visual C++ 1.0 and 1.5
users the complete source code for the Virtual Memory Manager libraries which
were shipped in those versions of Visual C++. The code is identical except
for a fix made to a problem that occurs when allocating memory for the upper
memory blocks (vmphys.c).
These libraries contain several fixes to the libraries which were shipped
with Microsoft C/C++ v7.0.
MASM v6.00B, v6.10A or v6.11 should be used to build these libraries along
with VC++ v1.0 or v1.5.

*Some files included in this package:
readme.txt: This file.
build.bat: Builds VM.LIB.
delobjs.bat: Deletes your object files.
dellibs.bat: Deletes your library files.
strip.bat: Removes the all of the OBJ files from the designated .LIB
file.
xms.rsp: Response file used in strip.bat.
ems.rsp: Response file used in strip.bat.
vm.rsp: Response file used in strip.bat.
vmm.txt: A document that discusses some aspects of the VMM.
legal.txt: Legal stuff.

The SRC directory contains all of the files used in VM.LIB. The
files in it use include files from the VM\H, VM\INC and the
\MSVC\INCLUDE directories.

*Building the libraries:

You must have both Microsoft C/C++, v7.0 or later and MASM 6.0 or
later installed in order to build these libraries.

In order to build VM.LIB, you should make sure your DOS environment
is set up for Visual C++ and MASM.

An example (minimal configuration):

SET PATH=c:\msvc\bin;c:\masm\bin
SET INCLUDE=c:\msvc\include
SET LIB=c:\msvc\lib

You will also have to have a VMDIR environment variable.
If you have installed the libraries under the c:\msvc\source\vm
directory VMDIR would be set like this,


SET VMDIR=C:\MSVC\SOURCE\VM

To build the VM.LIB type,

BUILD {release | debug} ... from the C:\MSVC\SOURCE\VM directory.

VM.LIB will be put into the C:\MSVC\SOURCE\VM\OBJS directory.
NOTE that XMS.LIB and EMS.LIB will also created. These libraries
are included in VM.LIB and may be deleted.

BUILD NOTES: *****************************************************

1) If you find that all of the source files are in your current
working directory, remember to use the '-d' switch when you run
VM.EXE. The -d switch preserves the original directory structure,
relative to your current working directory. This is essential
to building this library.
2) BUILD.BAT will modify your environment. It also sets some
environment variables. You should probably have about 1K reserved
for your environment. If you are low on environment space you may
wish to increase it by modifying the SHELL command in your CONFIG.SYS
file. See your DOS manual for more information regarding the SHELL
command.
3) The compiler options in BUILD.BAT are those that were used on
the shipping versions and are unchanged. There is some aggressive
optimization being done. At this time there are no known problems
with those optimizations. You may wish to use less aggressive
optimizations.


*Linking with VM.LIB

MAKE SURE YOU SAVE YOUR ORIGINAL LIBRARIES!

Method1:

You may wish to link in VM.LIB into your programs, for testing purposes
without removing it from your main library. In order to avoid getting
Multiply Defined Symbols your link line should look like,

LINK TEST.OBJ,,,/noe /nod VM.LIB xLIBCE.LIB {Other libs};
(Note that VM.LIB is first in the listing.)

Method2:

Copy strip.bat and ems.rsp, xms.rsp and vm.rsp into your C:\MSVC\LIB
directory. Copy your original XLIBCX.LIB to another directory
as a precaution.

Type,
STRIP LLIBCE ... This will remove the VM .OBJ's from LLIBCE.LIB

Type,
LIB LLIBCE.LIB +VM.LIB;


Microsoft sincerely hopes that you find these libraries a useful resource.


=========================< Additional Notes >==========================

- Microsoft Product Support Services offers limited customer
support to answer general questions about installing and building
unmodified sources.

- Several compiler warnings may be displayed during a build of the
run-time libraries. All of these warnings have been investigated
and can be ignored.

- We have tested these run-time library sources and found that they
are functionally equivalent to the shipping versions.

Nevertheless, you might find that certain LIBs and OBJs do not
binary-compare with the versions shipping with Visual C++. This is
due to a hardware or software configuration difference, or to using
a pre-production version of the tools for the shipping libraries.


Note:

You ARE NOT authorized to redistribute these library sources. You
may, however, redistribute the compiled binaries with the understanding
that Microsoft Corporation does not warrant or support them in any way.