1256902135MASM615

所属分类:多国语言处理
开发工具:Asm
文件大小:6418KB
下载次数:160
上传日期:2009-11-03 19:55:23
上 传 者beiyitiao
说明:  下载附件中的winrar压缩包,在本机磁盘中解压后修改C:\autoexec.bat 在autoexc.bat中加入以下内容 SET PATH=E:\USER\ZDX\MASM614\BIN E:\USER\ZDX\MASM614\BINR PATH SET LIB=E:\USER\ZDX\MASM614\LIB LIB SET INCLUDE=E:\USER\ZDX\MASM614\INCLUDE INCLUDE SET INIT=E:\USER\ZDX\MASM614\INIT INIT SET HELPFILES=E:\USER\ZDX\MASM614\HELP\*.HLP HELPFILES SET ASMEX=E:\USER\ZDX\MASM614\SAMPLES ASMEX SET TMP=C:\TEMP 注意其中的路径要与你解压后的路径相同 重启机器 编辑,用任何一种文件(源程序)编辑软件都可以,比如ultraedit 编译,在dos窗口下用masm 文件名[.asm]连接,在dos窗口下用mlink(link.exe) 文件名[.obj] 运行,在dos窗口下 文件名[.exe] 当汇编程序中有字符串输出/入时,在windows操作系统的DOS窗口中可能无法正常工作, 这时,可用alt+enter键使dos窗口全屏显示,基本可以解决此问题。
(Download the attachment in the winrar archive, extract the disk in the machine after the change C: \ autoexec.bat Add the following elements in the autoexc.bat SET PATH = E: \ USER \ ZDX \ MASM614 \ BIN E: \ USER \ ZDX \ MASM614 \ BINR PATH SET LIB = E: \ USER \ ZDX \ MASM614 \ LIB LIB SET INCLUDE = E: \ USER \ ZDX \ MASM614 \ INCLUDE INCLUDE SET INIT = E: \ USER \ ZDX \ MASM614 \ INIT INIT SET HELPFILES = E: \ USER \ ZDX \ MASM614 \ HELP \*. HLP HELPFILES SET ASMEX = E: \ USER \ ZDX \ MASM614 \ SAMPLES ASMEX SET TMP = C: \ TEMP Note that the path which should be with you the same path after decompression Reboot Editor, with any kind of files (source code) editing software can be, for example ultraedit Compilation, in the dos windows with the masm file name [. Asm] connection, in the dos windows with mlink (link.exe) filename [. Obj] Run, in the dos window, the file name [. Exe] When the assembler has a string output/Pops, i)

文件列表:
MASM615\BIN\CREF.DOC (10169, 1992-01-27)
MASM615\BIN\CREF.EXE (66560, 1993-09-02)
MASM615\BIN\DOSXNT.386 (9343, 1993-06-16)
MASM615\BIN\DOSXNT.EXE (393942, 1993-06-16)
MASM615\BIN\H2INC.ERR (21880, 1995-09-19)
MASM615\BIN\H2INC.EXE (249344, 1995-09-19)
MASM615\BIN\HELPMAKE.EXE (55585, 1991-12-30)
MASM615\BIN\MASM.EXE (49152, 2000-12-30)
MASM615\BIN\MASMREF.DOC (264704, 2000-02-23)
MASM615\BIN\ML.ERR (9687, 2000-03-16)
MASM615\BIN\ML.EXE (385072, 2003-02-04)
MASM615\BIN\NMAKE.EXE (45568, 1993-08-18)
MASM615\BIN\NMAKER.EXE (86809, 1992-03-10)
MASM615\BIN\PATCH.EXE (76981, 1995-09-19)
MASM615\BIN\PATCH.RTD (2709, 1999-04-06)
MASM615\BIN\PATCH.RTP (642114, 1999-04-06)
MASM615\BIN\QH.EXE (70065, 1992-07-09)
MASM615\BIN\QH.ICO (1086, 1992-01-15)
MASM615\BIN\WIN.INC (144586, 1997-10-14)
MASM615\BIN (0, 2006-08-07)
MASM615\BINR\BSCMAKE.EXE (123296, 1992-03-07)
MASM615\BINR\BSCMAKEV.EXE (127520, 1992-03-07)
MASM615\BINR\CURRENT.STS (4817, 2001-04-13)
MASM615\BINR\CV.EXE (468512, 1992-07-16)
MASM615\BINR\CV.ICO (1086, 1992-01-15)
MASM615\BINR\CVPACK.EXE (127520, 1992-07-07)
MASM615\BINR\CVW.EXE (63488, 1992-03-19)
MASM615\BINR\CVW1.386 (5194, 1992-03-19)
MASM615\BINR\CVW4.EXE (410112, 1992-07-16)
MASM615\BINR\DMW0.DLL (45856, 1992-07-17)
MASM615\BINR\EED1CXX.DLL (105722, 1992-07-16)
MASM615\BINR\EEW0CXX.DLL (105073, 1992-07-16)
MASM615\BINR\EMD1D1.DLL (69322, 1992-07-16)
MASM615\BINR\EMD1W0.DLL (74028, 1992-07-17)
MASM615\BINR\EMM386.EXE (110174, 1992-03-10)
MASM615\BINR\EMW0W0.DLL (74432, 1992-07-16)
MASM615\BINR\EXEHDR.EXE (39377, 1992-02-03)
MASM615\BINR\EXP.EXE (18757, 1992-01-21)
MASM615\BINR\HIMEM.SYS (13824, 1992-03-05)
MASM615\BINR\IMPLIB.EXE (42581, 1992-06-26)
... ...

README.TXT File Release Notes for the Microsoft(R) MASM Professional Development System, Version 6.14 (C) Copyright 1997, Microsoft Corporation. All rights reserved. This document contains release notes for the Microsoft MASM Professional Development System, version 6.14. The information in this document and in the Microsoft Advisor (on-line help) is more up-to-date than that in the manuals. The printed documentation for MASM 6.11 has not changed from MASM 6.10. MASM 6.14 is being released as a patch for users of MASM 6.11. The MASM 6.11 installation disks provide several important files that include new or updated information for this release. They are: README.TXT =====> Contains patch installation instructions, documentation errata, system requirements, information and tips on using MASM 6.1x, and known assembler bugs. CV.TXT =========> Contains release notes for Microsoft CodeView(TM). ERRMSG.TXT =====> Contains updated information on 32-bit Linker errors, ML error messages, and Microsoft DOSXNT MS-DOS Extender error messages. SAMPLES.TXT ====> Contains information about MASM samples for MS-DOS and Microsoft Windows 3.1. NTSAMPLE.TXT ===> Contains information about MASM samples for Microsoft Windows NT. SUPPORT.TXT ====> Contains updated Microsoft Product Support policies. Information on new processor instructions can be found in the following locations: Intel(R) Pentium(R) ====> In PENTIUM.TXT installed with MASM 6.11 Intel(R) MMX(TM) ====> On the World Wide Web at http://www.intel.com/drg/mmx/manuals/prm/prm.htm AMD(R) 3D Technology ====> On the World Wide Web at http://www.amd.com/swdev/swdev.html Intel(R) Internet Streaming SIMD Extensions ====> On the World Wide Web at http://developer.intel.com/design/PentiumIII/manuals/ ======================< README.TXT Table of Contents >===================== Part 1: Patch Installation -------------------------- Part 2: Documentation Errata ---------------------------- Part 3: System Requirements --------------------------- Part 4: Tips for Using MASM 6.1x -------------------------------- - ALIAS directive - Assembling Files Generated by Compiler - Building 32-Bit Applications - 32-Bit Linking - GROUP Directive and Flat-Model Programming - Structure Packing Issues for Mixed Language Programming - /WIN32 Switch for H2INC - CD-ROM Not a Valid Target - CMP Instruction Encoding - Debugging MASM Applications under Visual C++, 32-Bit Edition, or Fortran PowerStation, 32-Bit Edition - INVOKE Command - Multi-File Assembly with MASM.EXE - NMAKE and NMAKER - Response Files - SAMPLES.TXT and NTSAMPLE.TXT - Using MASM 6.x Structures - Visual C++ 1.0/Fortran PowerStation 1.0 Compatibility - Working with MASM 5.1 Code - Working With Microsoft BASIC Far Strings - .FPO directive new to MASM 6.11a Part 5: Known Assembler Bugs ---------------------------- - Expression Order in High-Level Conditionals - Hexadecimal Constants - Initializing Nested Structures - Span-Dependent Expressions used in Macros - Span-Dependent Equates in Macros and EXTERNDEF ABS - Span-Dependent Text Equates - STRUCT and RECORD Initialization Part 6: What Has Been Fixed in 6.11d? ------------------------------------- Part 7: What Has Been Fixed in 6.12? ------------------------------------- Part 8: What Has Been Fixed in 6.14? --------------------------------------- Part 9: What Has Been Added up to 6.14? --------------------------------------- ====================< Part 1: Patch Installation >========================= 1. Make backup copies of the files affected by the patch. These files are all in the MASM bin directory (for example, C:\MASM611\BIN). The following files will be affected: ML.EXE ML.ERR H2INC.EXE H2INC.ERR WIN.INC 2. Change to your MASM 6.11 root directory. For example: C: CD \MASM611 3. Copy the patch files to your MASM 6.11 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. Copy H2INC.EXE and H2INC.ERR from the patch diskette to your \masm611\bin directory. 6. Copy WIN.INC from the patch diskette to your \masm611\include directory. 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 6.11, 6.11a, or 6.11d. If, after checking these possibilities, you still have problems, please contact Microsoft Product Support. ====================< Part 2: Documentation Errata >======================= Environment and Tools, Page xxiii: Microsoft Support Services ------------------------------------------------------------- Microsoft Support Services information has been updated. See SUPPORT.TXT, in the directory in which you installed MASM, for the most current Microsoft support information and policies. Environment and Tools, Page 582: LIB Command Line Sample -------------------------------------------------------- The following example, as it appears on page 582, is incorrect: LIB FIRST +SECOND, , THIRD It should instead read: LIB THIRD +FIRST +SECOND Environment and Tools, Page ***9, 651: _syscall and __syscall ------------------------------------------------------------ The H2INC documentation on pages ***9 and 651 lists _syscall and __syscall as C keywords recognized by H2INC. These are not recognized, and should be removed. Environment and Tools, Page 819: Error Message A2156 ---------------------------------------------------- The value range given for the first parameter of the PAGE directive is incorrect; "...either 0 or a value in the range of 10-255" should read "...either 0 or a value in the range of 14-255." Reference, Page 12: ML Command-line Options /Cu and /Cx ------------------------------------------------------- /Cu is not the default command-line option, but is indicated as such in the MASM 6.10 Reference. Instead, /Cx should be indicated as the default. Reference, Page ***: LEA is no longer optimized ---------------------------------------------- The MASM 6.10 Reference indicates that the LEA instruction is encoded as a MOV when the source operand is a direct memory address. In response to programmer requests, MASM 6.1x no longer performs this optimization automatically. The optimization can be performed by using the OPATTR operator, as shown in the following macro: MOVLEA MACRO Dest, Symbol IF (OPATTR(Symbol)) AND 08h MOV Dest, OFFSET Symbol ELSE LEA Dest, Symbol ENDIF ENDM Programmer's Guide, Page 156: Using an Emulator Library ------------------------------------------------------- The sample code demonstrating floating-point instructions served by an emulator contains the directive .STARTUP. This directive should be removed. Programmer's Guide, Page 202: User-Defined Epilogues & Prologues ---------------------------------------------------------------- The documentation for user-defined epilogue and prologue code reads "Your macro function must return the parmbytes parameter." It should read "...the localbytes parameter." Programmer's Guide, Page 323: The C++/MASM Interface ---------------------------------------------------- The second sentence in the third paragraph reads: "The linkage specification applies only to called routines, not to external variables." It should read "The linkage specification applies to called routines and external variables." The last sentence in the same paragraph should be removed. Help for Runtime Error R6921 ---------------------------- The on-line help for runtime error R6921 reads "...Possibly the CONFIG.SYS file contained a line such as DEVICE=C:\OS\MM386.EXE..." The file name should read "C:\DOS\EMM386.EXE". =================< Part 3: MASM 6.14 System Requirements >================= The following are system requirements for Microsoft MASM 6.14: - Personal computer using a 386 or higher processor running Windows 95, Windows ***, or Windows NT version 3.51 or later. - 4 MB of available memory. - Hard disk with 10 MB available space. - One 3.5" high-density (1.44 MB) disk drive (3.5" low-density (720K) or 5.25" high-density (1.2 MB) disks available separately with coupon enclosed). To target Windows 3.1, you need one of the following: - Microsoft Windows Software Development Kit (SDK) 3.1. - Microsoft Visual C++ Development System, Standard or Professional Edition. To target Windows NT, you need one of the following: - Microsoft Windows NT Software Development Kit (SDK). - Microsoft Visual C++ Development System, 32-Bit Edition. ====================< Part 4: Tips for Using MASM 6.1x >=================== ALIAS directive --------------- The ALIAS directive is not included in the printed documentation for MASM 6.10. The ALIAS directive can be used for creating libraries that allow the linker (LINK) to map an old function to a new function. Syntax: ALIAS = where alias is the alternate or alias name, and actual-name is the actual name of the function or procedure. The angle brackets are required. Assembling Files Generated by Compilers --------------------------------------- Many compilers support assembly-language output. If you experience difficulty assembling the output of such compilers, you may need to assemble using the /Zm option. In some cases (for instance, if the compiler inserts nondelimited comments or page numbers) it may be necessary to edit the assembly-language output by hand. Building 32-bit Applications ---------------------------- Following are a number of items you should keep in mind when building 32-bit applications with MASM 6.1x. Examples of how to create 32-bit applications can be found in the \SAMPLES\NTSAMPLE subdirectory of the directory in which you installed MASM. 32-bit Linking -------------- When you are creating a 32-bit application, you must link separately with a 32-bit linker. To prepare your object files for 32-bit linking, assemble using the following switches: - /c (assembles without linking) - /coff (causes object files to be created in Windows NT- compatible common object file format) After assembling, link with your 32-bit linker. Refer to the documentation included with your particular 32-bit linker for specific information and instructions. In addition, the sample Windows NT applications in \SAMPLES\NTSAMPLE demonstrate the use of /c, /coff, and a 32-bit linker. GROUP Directive and Flat-Model Programming ------------------------------------------ The GROUP directive has no effect when used in 32-bit flat-model programming. It is recommended that you not use the GROUP directive when programming in flat model. Using the GROUP directive with /coff will result in an error. Structure Packing Issues for Mixed Language Programming ------------------------------------------------------- Microsoft MASM uses /Zp1 as it's default setting for structure packing; this means that structures are not packed. Other languages may use other default settings for packing. For example, Microsoft C/C++ compilers prior to Visual C++ 32-bit edition use /Zp2; Visual C++ 32-bit edition uses /Zp8 as the default. Modules built using different structure packing may not be able to share structure data items, so care must be taken when using structures in mixed language programs. The packing size is a maximum, not a fixed, packing value. This means that a member must have a size equal to or larger than the packing limit before any packing is done. /WIN32 Switch for H2INC ----------------------- Use the /WIN32 switch with H2INC to convert C header files to NT-compatible MASM include files. When you use the /WIN32 switch, C int data types are converted to the 4-byte assembler equivalent DWORD (signed int data types are converted to SDWORD). Without the /WIN32 switch, H2INC converts int data types to 2-byte WORD (and signed int data types to SWORD). CD-ROM Not a Valid Target ------------------------- A CD-ROM drive is not a valid installation target for MASM 6.11. Setup may incorrectly list a CD-ROM drive on the target drive list. CMP Instruction Encoding ------------------------ MASM 6.1x uses a different encoding for the CMP , instruction than MASM 6.0 did. There is no difference in length or processor timing. Debugging MASM Applications under Visual C++, 32-bit Edition, or Fortran PowerStation, 32-bit Edition ------------------------------------------------------------- When debugging a pure MASM application under the 32-bit editions of Visual C++ or Fortran PowerStation, you must link in the library file (.LIB) provided with these high-level languages (LIBC.LIB in Visual C++, LIBF.LIB with Fortran PowerStation). If you do not use the .LIB file included in the high-level language, you will receive an "Access Violation" error message when you attempt to run a MASM application in either the 32-bit Visual C++ or 32-bit Fortran PowerStation integrated development environment. INVOKE Command -------------- The MASM 6.x INVOKE command does not support transferring control between 16-bit and 32-bit code segments. When the assembler encounters an INVOKE command in a 16-bit segment, it assumes that the procedure being invoked is also in a 16-bit segment; if the assembler encounters an INVOKE in a 32-bit segment, it assumes that the invoked procedure is also in a 32-bit segment. To avoid this problem, push the necessary parameters on the stack and make the appropriate call instead of using INVOKE. Multi-File Assembly with MASM.EXE --------------------------------- When assembling multiple files with MASM.EXE, you must terminate the command-line with a semi-colon or a comma (for example, MASM *.asm;). Failure to do this may cause the program to appear to hang if you are running Microsoft Windows NT. If this does occur, you can terminate the program with Ctrl+C. NMAKE and NMAKER ---------------- MASM 6.11 includes two versions of the NMAKE project management utility. NMAKER.EXE is a real-mode version of the utility. NMAKE.EXE is a driver program which first loads the MS-DOS extender DOSXNT into memory, and then runs NMAKER.EXE. Using the NMAKE.EXE driver will result in faster build times. Some development tools from other manufacturers may be incompatible with NMAKE.EXE. If you encounter incompatibilities, use NMAKER.EXE instead. Response Files -------------- Information on response files is not included in the MASM 6.10 manuals; however, this information can be found in "ML Command Line Options" in On-line help. SAMPLES.TXT and NTSAMPLE.TXT ---------------------------- SAMPLES.TXT contains information about the MASM samples for MS-DOS/Windows; NTSAMPLE.TXT contains information about the samples given for MASM for Windows NT. Both files include information about additional tools you may need to build some of the samples. If you choose to install the sample code during the setup process, both SAMPLES.TXT and NTSAMPLE.TXT are included. SAMPLES.TXT can be found in the \MASM611\SAMPLES subdirectory; NTSAMPLE.TXT can be found in the \MASM611\SAMPLES\NTSAMPLE subdirectory. Using MASM 6.x Structures ------------------------- MASM 6.x supports a more powerful syntax for structure definition and usage than previous versions of MASM. This more powerful syntax is enabled by default. To use the older syntax, issue the OPTION OLDSTRUCTS directive (see Appendix A of the MASM Programmer's Guide for more information). Note: use of nested structures requires the new MASM 6.x syntax. If you use nested structures, the OPTION OLDSTRUCTS directive will be ignored for the structure which is nested. Visual C++ 1.0/Fortran PowerStation 1.0 Compatibility ----------------------------------------------------- There are specific steps you must take to use MASM 6.1x with Microsoft Visual C++ 1.0 or Microsoft Fortran PowerStation 1.0. If you wish to do mixed language programming with these products, it is recommended that: - You install Visual C++/Fortran PowerStation and MASM 6.1x in separate sub-directories. - You place \MSVC\BIN or \F32\BIN (your Visual C++ or Fortran PowerStation sub-directory) first on your path statement before \MASM611\BIN (your MASM 6.11 sub-directory). - You use NMAKE.EXE from MASM 6.11. You can do this using various methods, such as moving or renaming NMAKE.EXE installed in \MSVC or \F32 thus causing the system to continue searching your path and use the NMAKE.EXE in \MASM611. Optionally, for MASM 6.1x/Visual C++ mixed programming, you may use NMAKER.EXE which is installed with both products. When using the LINK utility included with Visual C++ 1.0, you may encounter one or both of the following warnings: LINK : warning L4017: ... ...

近期下载者

相关文件


收藏者