LINK Help (linker.hlp) (
Table of Contents;
Topic list)
Important Notice
The pages on this site contain documentation for very old MS-DOS software,
purely for historical purposes.
If you're looking for up-to-date documentation, particularly for programming,
you should not rely on the information found here, as it will be woefully
out of date.
NAME Statement
◄Up► ◄Contents► ◄Index► ◄Back►
─────LINK───────────────────────────────────────────────────────────────────
Syntax: NAME [appname] [apptype] [NEWFILES]
Identifies the executable file as an application. NAME can also
specify the name and application type. If NAME is specified, the
LIBRARY statement cannot be used. NAME or LIBRARY must precede all
other statements. If neither is used, the default is NAME.
Arguments can appear in any order. The <appname> specifies the
name of the application as it is known by the operating system.
This name can be any valid filename. If <appname> contains a
space, begins with a nonalphabetic character, or is a reserved
word, enclose <appname> in double quotation marks. The name cannot
exceed 255 characters (not including surrounding quotation marks).
The default is the base name of the executable file.
See: ◄Reserved Words►
The <apptype> specifies the type of application. The type can also
be specified using a form of the LINK /PM option:
<apptype> Meaning LINK Option
WINDOWAPI Default. Windows application to /PM:PM
run in the Windows environment.
WINDOWCOMPAT Character-mode application to run /PM:VIO
in a text window in Windows.
NOTWINDOWCOMPAT Character-mode application that /PM:NOVIO
must run full screen and cannot
run in a text window in Windows.
The NEWFILES keyword sets a bit in the file header to notify the
loader that the application may be using an installable file
system. The synonym LONGNAMES is supported for compatibility.
Example
NAME calendar WINDOWCOMPAT
This example assigns the name 'calendar' to an application that
can run in a text window in PM or Windows.
-♦-