Using the SMTLink Protocol Generation Utility
=============================================            
                                               LSS 5.0(0), August 1996
                                               -----------------------

This document describes the SMTLink  utility  which  can  be  used  to 
generate  specific  combinations  of  the  Smart  kernel  and protocol 
modules.  

1. OVERVIEW
-----------

The SMTLink utility is used to combine the Smart kernel (SMART.EXE), a 
configuration file (SMART.CFG) and a number of protocol modules into a 
single  executable.   The  executable  can  then  be  used  to provide 
particular combinations of protocols  without  the  need  for  a  disk 
containing all the protocol modules themselves.  

SMTLINK is most likely to be of use in two situations. Firstly, in the
case where where an install utility or operating system expects to see 
a monolithic driver (for example, with Windows for Workgroups) .  
Secondly, in remote booting (from LAN Server for example) it may be
necessary to have a monolithic driver.  

For details on the format of the a configuration file (SMART.CFG) see
the Information Files for the Smart II Software (SMART.TXT, etc)  and
the User Documentation.


2. BASIC OPERATION
------------------

SMTLink can be used in two distinct ways:

2.1. SMTLINK <filename.exe> /V
------------------------------
        
The  first  option  will  examine  the .EXE file called "filename" and 
display its contents.  This will show which modules were  linked  with 
the  kernel.   You need to use the /V command-line option.  An example 
is:

SMTLINK SMARTIPX.EXE /V

SMTLink reports that SMARTIPX consists of the kernel (SMART.EXE),  and 
the  LLC,  NetBIOS  and  IPX  protocols.  It also displays the version 
numbers of the components.

To display the components without the version numbers, use /A  instead 
of /V.

2.2. SMTLINK <filename.exe> smart.exe [smart.cfg] <protocols...>
----------------------------------------------------------------

Used in this form SMTLink generates the file "filename.exe" consisting 
of the Smart kernel (SMART.EXE) an optional SMART.CFG  file  and  some 
protocols.   SMTLink  searches for the files it is required to link in 
the current directory if none is specified.

Example: to generate an executable which consists of just the  kernel, 
LLC  and  NetBIOS  modules, use  the  following  (the output is called 
SMTLSP.EXE in this example):

        SMTLINK SMTLSP.EXE SMART.EXE LLC.SMT NETB.SMT

SMTLink reports the modules it has linked together (in this  case  the 
kernel and two protocols: LLC and NetBIOS).

Example: to generate an executable (called SMTIPX.EXE) which  contains 
the IPX protocol and a configuration file, use the following:

        SMTLINK SMTIPX.EXE SMART.EXE SMART.CFG IPX.SMT

SMTLink reports errors if:

* It can't find one of the modules that it  is required  to link.
* If a disk error occurs while it is writing the final .EXE file. 


2.3. Pre-linked drivers
-----------------------

Two pre-linked drivers are provided, SMTNDIS.DOS (along with 
PROTOCOL.INI and OEMSETUP.INF) and SMTNETB.EXE.  SMTNDIS.DOS is a 
pre-linked SMART.EXE, NDIS.SMT and SMTNDIS.CFG, while SMTNETB.EXE is a
pre-linked SMART.EXE, NETB.CFG and SMTNETB.CFG.  
Note that if you need to specify other parameters then put them on the 
SMTNDIS.DOS or SMTNETB.EXE command line or alternatively make a new 
CFG file containing all the required parameters and use SMTLINK.EXE to 
link the new CFG file with SMART.EXE and the required protocol.

                    ****** End of SMTLINK.TXT ******
