Dec 072017
 
This is a patch to MASM 6.1 to create 6.1a. This fixes problems when trying to run MASM from the same directory as MS Visual C++ and a few other things. It allows MASM to use the latest DOSXNT DOS extender.
File 61PATCH.ZIP from The Programmer’s Corner in
Category Assembly Language
This is a patch to MASM 6.1 to create 6.1a. This fixes problems when trying to run MASM from the same directory as MS Visual C++ and a few other things. It allows MASM to use the latest DOSXNT DOS extender.
File Name File Size Zip Size Zip Type
PATCH.EXE 76981 44224 deflated
PATCH.RTD 2553 628 deflated
PATCH.RTP 139107 133245 deflated
README.TXT 6750 2345 deflated
TPCREAD.ME 199 165 deflated

Download File 61PATCH.ZIP Here

Contents of the README.TXT file



MASM 6.1a PATCH Instructions

(C) Copyright 1993 Microsoft Corporation. All rights reserved.

Several problems in the original Microsoft Macro Assembler (MASM)
version 6.10 release have been fixed. This document describes the
fixes and explains how to install them on your computer.


=============================< CONTENTS >=============================

This file has the following sections:


Part 1: Installation Instructions

Part 2: What Has Been Fixed?

Part 3: Using The New Files


=====================< INSTALLATION INSTRUCTIONS >====================


1. Make backup copies of the files affected by the patch. These
files are all in the MASM bin directory (for example,
C:\MASM61\BIN). The following files will be affected:

CVTOMF.EXE
DOSXNT.EXE
MASM.EXE
ML.EXE
NMAKE.EXE
PWBC.XXT
PWBUTILS.MXT

NOTE: PWBC.XXT may have been renamed to PWBC.MXT. If so, rename
the file to PWBC.XXT before running the patch program, and then
rename it back to PWBC.MXT when done. The patch program will not
update the file unless it is named PWBC.XXT.


2. Change to your MASM 6.10 root directory. For example:

C:
CD \MASM61

3. Copy the patch files to your MASM 6.10 root directory. The patch
files are:

PATCH.EXE
PATCH.RTD
PATCH.RTP

4. Run the patch program by typing:

PATCH

The patch program indicates its actions as it runs. When the
patch has been successfully completed, you can delete the patch
files.

5. In addition to modifying existing files, the patch program creates
several new files. To use the new files, see the "Using the New
Files" section in this document.

6. If you use Microsoft Visual C++ and PWB, you may need to re-select
linker options in PWB. See "Compatibility problems..." in the
"What Has Been Fixed" section in this document.


If you have trouble:
-----------------------

If you have problems installing this patch:

- Check to be sure that you have all three patch files:
PATCH.EXE, PATCH.RTP, and PATCH.RTD.

- Make sure you have the correct version of the files to be updated.
This patch will only patch files from MASM v6.10.

If, after checking these possibilities, you still have problems,
please contact Microsoft Product Support.


=======================< WHAT HAS BEEN FIXED? >=======================


Compatibility problems with Microsoft Visual C++
----------------------------------------------------

- MASM 6.10 cannot be installed in the same directory as Microsoft
Visual C++, because of DOS extender conflicts. MASM 6.1a uses the
same version of the DOS extender as Visual C++, eliminating this
problem.

NOTE: Microsoft Visual C++ contains newer versions of some
utilities. To use the newer utilities, ensure that Visual C++
comes before MASM on the path.

- The MASM 6.10 PWB extensions use /NOF as an abbreviation for the
"Translate Intrasegment Far Calls" linker option. /NOF is not a
legal option for the Visual C++ linker. To make PWB change /NOF
to /NOFA:
1. Open the desired project.
2. From the Options menu, choose Link Options.
3. Select Additional Debug Options or Additional Release Options.
4. Choose OK to close the Additional Options dialog box.
5. Choose OK to close the Link Options dialog box.


Inability to run MASM from a read-only network drive
-------------------------------------------------------

- MASM now correctly uses the TMP environment variable to create
swap files for virtual memory. If you are running MASM from a
read-only network drive, ensure the TMP variable is set to a
drive and directory for which you have write permission.


Other Fixes
---------------

- Errors when assembling a very large number of files using ML *.ASM
have been fixed.

- Added compact memory model Windows DLL library (CNOCRTDW.LIB).

- Added virtual memory browser database utility (BSCMAKEV.EXE).

- Added PWB 2.1 extension for Microsoft Profiler (PWBPROF.XXT).



========================< USING THE NEW FILES >========================


This patch includes new files which were not part of the original
MASM 6.10 release. The files are as follows:

BSCMAKEV.EXE
CNOCRTDW.LIB
PWBPROF.XXT

This section explains how to use these new files.

NOTE: The patch program attempts to install these files in the correct
directories. If the patch program cannot locate the correct directory
for a file, the file will be placed in the MASM root directory. It
may then be necessary to move the file to a different directory to use
it, as described below.


BSCMAKEV.EXE
---------------

BSCMAKEV is a version of the BSCMAKE browser database utility which
uses virtual memory. BSCMAKEV is slower than BSCMAKE, but it can
handle larger databases.

To use BSCMAKEV, make sure BSCMAKEV.EXE and BSCMAKE.EXE are in the
same directory. BSCMAKE will automatically invoke BSCMAKEV when
required.


CNOCRTDW.LIB
--------------

CNOCRTDW.LIB is the compact memory model version of the Windows DLL
startup code. Because Windows DLLs rarely use the compact model,
this file is not typically needed.

To use CNOCRTDW.LIB, make sure it is in the MASM libraries directory
(for example, C:\MASM61\LIB). For more information on writing
Windows DLLs, refer to Chapter 10 of the Programmer's Guide.


PWBPROF.XXT
-------------

PWBPROF.XXT enables the use of the Microsoft Source Profiler version
1.0 with PWB. The PWB extension originally supplied with version 1.0
of the Profiler is not compatible with the current version of PWB.

To use the Profiler with PWB, rename this file to PWBPROF.MXT and
make sure it is in the same directory as PWB (for example,
C:\MASM61\BIN). The extension will automatically be loaded when PWB
is run. (To load the extension manually, refer to the instructions
on using PWB in the Environment and Tools book).


 December 7, 2017  Add comments

Leave a Reply