There are two ways to have the AMarqueed executable be run when
an AMarquee client connects to your computer:  resident, and
non-resident.  If the AMarqueed executable is not resident, a
new copy of its binary code will be loaded into memory for 
each connection that is accepted.  If, on the other hand, it 
has been made resident, then only one copy of the AMarqueed
executable will ever be loaded into memory, no matter how many
simultaneous connections there are.  Obviously, making AMarqueed
resident will save memory in most situations.

There are two things you have to do to make AMarqueed run 
resident.  The first is to make sure the line

resident amitcp:serv/AMarqueed

has been executed before your first AMarquee connection is
accepted.  This can be done in your user-startup file, or
in your amitcp:bin/startnet file, or anywhere else, as long
as it is done somewhere.  You may need to change the path
above to accurately reflect the location of the AMarqueed
executable on your system. (The included Installer script puts
this command in your user-startup file)

The second thing to do is modify AMarquee's line in the InetD
configuration so that no file path is specified.  This is 
necessary because specififying a file path will cause the
executable to be loaded from that path rather than re-used
from memory.  Thus, you should edit the file (amitcp or inet):db/inet.conf
(or the Databases/InetD window in Miami) to contain this line:

AMarquee stream tcp nowait root AMarqueed

(note that the amitcp:serv/ prefix in the last field has been
 deleted!)
 
You can check to see if the residenting is working by 
accepting several AMarquee connections, and then typing 
"resident" at a shell prompt.  You should see AMarqueed listed,
with a usage count of greater than 0.