TSM RDME, Studia, Assembler
[ Pobierz całość w formacie PDF ]/***************************************************************************/TSM_RDME.TXTTURBO ASSEMBLERWelcome to Borland Turbo Assembler and Tools 5.0-----------------------------------------------------------------TABLE OF CONTENTS-----------------1. Installation2. New Features3. Assembling and Linking with TASM 5.04. TASM utilities5. Important Informationa) Object File Formatb) Out of Memory and MAKESWAPc) Make under Windows NTd) Creating 16-bit import libraries from .DEF filese) Resource compilers: 32-bit command-line versions----------------1. Installation----------------For details on installing Turbo Assembler and Tools 5.0, see the fileTSM_INST.TXT----------------2. New Features----------------New TASM 5.0 features:- Enhanced MASM compatibility- TASM32.EXE Thunk Compiler compatibility for Windows 95 flat thunking.New Turbo Debugger 5.0 features:- Dual monitor support under Win95 (TDW: -do, TD32: -vd)- Debugger support for new C++ language constructs (bool, namespaces, etc.)- 16-bit debugging support under Windows NT with TDW.EXE----------------------------------------3. Assembling and linking with TASM 5.0----------------------------------------The TASM 5.0 package includes three different assemblers:TASM.EXE 16-bit real-mode assemblerTASMX.EXE 16-bit protected-mode assemblerTASM32.EXE 32-bit protected-mode assemblerAll three assemblers are capable of producing both 16- and 32-bitobject files, depending on the directives contained in your assemblersource files. If you produce a 16-bit object file, then you must usethe 16-bit linker (TLINK.EXE) to link your application. If you producea 32-bit object file, then you must use the 32-bit linker (TLINK32.EXE)to link your application.TASM.EXE is a real-mode assembler, meaning that it is capable of usingonly the lower 640K of memory addressable by DOS. If you're assemblinglarger applications, use either TASMX.EXE or TASM32.EXE. Both of theseassemblers use the DPMI server to take advantage of extended memory.The biggest difference between the three assemblers is the type ofdebug information they produce when you assemble your source files withthe /zi command-line option. Both TASM.EXE and TASMX.EXE produceonly 16-bit debug information. TASM32.EXE produces only 32-bit debuginformation. If you plan to use Turbo Debugger to debug your assemblerapplication, then you must assemble 16-bit files with either TASM.EXEor TASMX.EXE. To produce 32-bit debug information, then you must assembleyour files with TASM32.EXE.-----------------4. TASM utilities-----------------TASM 5.0 ships with several debuggers and utilities to help you create anddebug your assembly language programs. For more information on TurboDebugger and the tools provided with TASM, refer to the text files locatedin the DOC subdirectory located under your main TASM directory.-------------------------5. Important Information-------------------------a) Object File Format------------------------Turbo Assembler generates object modules (.OBJ files) which conform to theIntel OMF (Object Module Format) specification. In addition, the providedtools (such as TLINK32 and TLIB) and libraries accept only this format;there is no support in the linker or librarian for COFF object modulesproduced by Microsoft C tools.b) Out of Memory and MAKESWAP--------------------------------If you get "Out of Memory" errors from DOS when running the command-linetools, create a swap file with the MAKESWAP utility. (Note that thisapplies to DOS only, not to DOS boxes opened under Windows.) MAKESWAPtakes the size of the file to create in KBytes, for example:MAKESWAP 12000will create a 12MB swap file in the current directory called EDPMI.SWP foruse by Borland command line tools. To enable the swap file, use theDPMI32 environment variable by issuing the following command at the DOSprompt:set DPMI32=SWAPFILE <location of swap file>\EDPMI.SWPc) Make under Windows NT---------------------------If you encounter difficulties running MAKE under Windows NT, try runningMAKER instead.d) Creating 16-bit import libraries from .DEF files------------------------------------------------------Use the /o IMPLIB switch when you are creating 16-bit import librariesfrom .DEF files. This prevents IMPLIB from generating extensions forimport entry module names.e) Resource compilers: 32-bit command-line versions------------------------------------------------------The 32-bit command-line resource compilers (br*.exe) that ship with TASM5.0 do not run under 16-bit environments of DOS or Windows 3.1; you mustrun these 32-bit tools from the DOS boxes in Windows 95 or Windows NT. Ifdo not have access to Win95 or NT, you must use the 16-bit resourcecompilers (such as the ones shipped with TASM 4.0 or Borland C++ 4.5) tocompile resources from the command line./********************************* END OF FILE ****************************/ [ Pobierz całość w formacie PDF ]