HAHAHAHA!!!!!
Excuse me for laughing, but that's what I've been stressing over for the
last month!  Want quick answers?  Backtrack through the previous post and
look for all the posts addressed to me.  You'll find out how to set it up
both as an internal and external protocol.  Personally, I liked David's way
of setting it up as a function key the best.
However, I do need to tell you that I think there is a big difference
between the way QModem Test Drive and QModem Pro sets up the .BEW files. 
That is the file that tells HSLINK what to upload while receiving files. 
Everyone here kept telling me over and over what to use with Qmodem Pro, but 
it didn't seem to work with the test drive version.  The problem is
QMODEM.BEW doesn't provide the directory location of each file you tag (very 
improtant with HSLINK), it just provides the name of the file itself and the 
directory location on a different line.  HSLINK rejects this.
I finally solved the problem by finding a separate HSLINK file tagging
program called HSLTAG.  I've seen another around called HSLSHELL.  If you
can find these, get em.  I set up the program so that F8 loads up HSLTAG so
I can make a list of the files I want to upload.  Then I can Esc out of it
and hit F9 to start up HSLINK.  Read the previous posts to me for more info
on how to do this.
The command line I use in the HSLINK.BAT file is:
   HSLINK -Uc:\r @send.lst
c:\r - directory I want to receive the files I am downloading
@send.lst - text file which contains a list of all the files I want to
            upload.  Like I said, HSLTAG creates this file.  I had problems
            using the QMODEM.BEW file the Qmodem TD program creates.
Good luck!  Everyone else here was so helpful to me, I figured I'm obligated 
to return the favor.
--- Renegade v10-05 Exp
---------------