OK, Instead of putting 50 batch files in your \FMN directory, or making your
        HDD smaller by re-copping your EXE's, we decided on this plan.......

1.      Create a sequential text file called: "1$EXT.PRO" in your \FMN
        directory.

2.      Copy the defaults we have provided you, use your own, or get others,
        but follow these parameters.


Column 1 - 19 inclusive:    Protocol Keyword
                                
                            You must differentiate the keywords
                            for uploading vs downloading, if your
                            commandline parameters are different
                            in each case.

Column 20 - 59 inclusive:   Drive:\Full Path\Executable Filename.Extension

                            Example: C:\protocls\mydrvr.exe


Column 60 and on...         Command line parameters

                            Example: \e port2 /P-12

                            If your program requires passed variables
                            you must use literal strings. For example
                            Port# should be Port2, if your actual Port
                            number is 2.


3.      When using Batch uploads, "uploading a series of filenames,"
        create a file anywhere, but name it with a "LST" extension,
        for example: c:\mydir\files2go.lst

        Then simply copy all the file names you want to upload in a single
        Upload session, into this file, use full path names, if they don't
        reside in the \FMN directory.

        At the Upload file name prompt, within 1$COMM, use your list file
        full path and name, again if not in the current directory, and
        press Enter.

        1$COMM will pass the filenames list file to your external protocol,
        and start the upload.

        You may also specify filenames using wildcard characters. 
        Example: "Myfile??.*"

        Your list file may contain up to 150 entries, but with the power
        of using wildcard characters, you'll have limitless capabilities!


4.      In the 1$EXT.PRO file please use specific key word lines, pending
        different command line options for each protocol.

                           key word              command line

        For example:       DSZ UP SINGLE         port# ha on sz
                           DSZ UP BATCH          port# ha on sz @d:
                           DSZ DWN               port# ha on rz

        This is because the command line parameters will generally be 
        different for a single file upload as opposed to a batch upload.

        Please note that if the filename that you enter into the input
        prompt box, from within 1$COMM at Upload time, has a "LST"
        extension, 1$COMM will not insert a space between the end of
        the command line string and the filename. Otherwise, it always
        adds that space....now you can see the need for separate calls.
        
                                               Examples continue that way -->

DSZ Zmodem FileUp  D:\FMN\DSZ.EXE                          port# ha on sz
DSZ Zmodem ListUp  D:\FMN\DSZ.EXE                          port# ha on sz @d:
DSZ Zmodem Down    D:\FMN\DSZ.EXE                          port# ha on rz

MobyTurbo FileUp   D:\FMN\DSZ.EXE                          port# ha on sz -m
MobyTurbo ListUp   D:\FMN\DSZ.EXE                          port# ha on sz -m @d:
MobyTurbo Down     D:\FMN\DSZ.EXE                          port# ha on rz -mry

DSZ YmdmG FileUp   D:\FMN\DSZ.EXE                          port# ha on sb -g -k
DSZ YmdmG ListUp   D:\FMN\DSZ.EXE                          port# ha on sb -g -k @d:
DSZ YmdmG Down     D:\FMN\DSZ.EXE                          port# ha on rb -g -k

HSLINK             D:\FMN\HSLINK.EXE                       -P#
HSLINK ListUp      D:\FMN\HSLINK.EXE                       -P# @


You may use these examples as actual calls, but make sure you replace the
"#" symbol with your actual com port number. Also correct the drive and
path, if your protocols do not reside in the "D:\FMN" drive and directory.
It may also be a good idea if you used shorter key words to identify the
protocols, our example is more verbose in order to identify the protocol
in the example. Please keep in mind, for the benefit of those not familar
with external protocols, it up to the user to provide the actual protocol,
"program.exe," they are not included in 1$COMM, that's why they are called,
External!
         
Do not put blank lines in the "1$EXT.PRO" file.


"Bob's note"
Note: Switches are case sensitive in both protocols....DSZ must have all
switches in lower case. HS/Link needs the -P upper case. Just pass the
port and these should be fine as defaults.



11.09.93
� Wizard.....
End of Document