Click above to get retro games delivered to your door ever month!

 VERBOSE output
------------------------------------------------------------------------------
 The VERBOSE command is often useful in problem determination.
 Through the use of the VERBOSE command you can see the exact order in which
 Blinker is processing modules from both object and library files, and the
 modules which make up the final executable. If Blinker cannot complete a
 link due to an error, the VERBOSE command is also useful in determining
 which module is causing the problem - usually the last module listed.
 The use of the Blinker command VERBOSE 1 (list files as processed) in a
 sample link script generated the following output listing while Blinker was
 executing:

 File : TEST.OBJ
 File : CLIPPER.LIB
 File : EXTEND.LIB
 File : TERMINAL.LIB
 File : DBFNTX.LIB
 .
 .
 .
 File : TEST.OBJ
 File : CLIPPER.LIB
 File : EXTEND.LIB
 File : TERMINAL.LIB
 File : DBFNTX.LIB

 The use of VERBOSE 2 (list files and modules as processed) yielded the
 following, which will form the basis for our discussion:

 TEST.OBJ(TEST)
 CLIPPER.LIB(CRT0)
 CLIPPER.LIB(CRT0DAT)
 CLIPPER.LIB(CRT0FP)
 CLIPPER.LIB(CRT0MSG)
    .
    .
    .
 EXTEND.LIB(GETE)
 EXTEND.LIB(DISKSPAC)
 EXTEND.LIB(_DIR)
 EXTEND.LIB(COPYFILE)
    .
    .
    .
 DBFNTX.LIB(DTX0)
 DBFNTX.LIB(DTXDYN)
 Resolving external references
 Building map table

 *****  Pass 2  *****

 TEST.OBJ(TEST)
 CLIPPER.LIB(CRT0)
 CLIPPER.LIB(CRT0DAT)
 CLIPPER.LIB(CRT0FP)
    .
    .
    .
 EXTEND.LIB(_TBROWSE)
 EXTEND.LIB(_TBRDB)
 TERMINAL.LIB(BEEP)
 TERMINAL.LIB(DISPIBM)
 TERMINAL.LIB(KBDIBM)
 DBFNTX.LIB(NET)
 DBFNTX.LIB(DTX1)
 DBFNTX.LIB(DTX0)
 DBFNTX.LIB(DTXDYN)

 Clearing output buffers

 If verbose is specified without a parameter then VERBOSE 2 is assumed.

 Pass 1 listing

 The first part of the Verbose output lists all the modules which are
 processed by Blinker as they are encountered. The term module generally
 refers to an object file, whether that object file be specified in a FILE
 command or exists within a library which is specified in a LIBRARY or SEARCH
 command.

 The originating object file or library is listed first, followed by the
 module name in parentheses. These modules are not necessarily included in
 the generated executable file, but are processed due to the manner in which
 they were specified in the link script file.

 Typically the module name is the base file name of the original source file
 without the drive, path and extension. Sometimes the names may not be
 relocated often due to compile time options or renaming the file after
 compilation.

 Module names which are displayed during pass one of the link process are as
 follows:

 . all modules specified in a FILE command.
 . those modules extracted from a library to resolve an external
   reference.
 . all modules within a SEARCHed library.

 Pass 2 listing

 During the second pass, once Blinker has determined precisely which modules
 will be included in the final executable, only those modules actually
 included will be listed.

 Often this list is used in conjunction with the list of duplicated modules
 generated by the BLINKER MESSAGE DUPLICATE command to identify the modules
 within the .EXE which had duplicates at link time.