Scott and Ric,
	I knew when I started this mini-editorial that I should have gone to the
time-bank first, but if you'll excuse me for having a two-part explantion, I'll
try to help. For one thing Scott, if you're using BOYAN v4.0, you might want to
obtain the 2nd part of that program -BOYAN40B.ZIP, which is available on the
Express Lane BBS 757-2667. I don't have that particular file myself, as I
originally downloaded BOYAN40A.ZIP from Data Pulse BBS and part b wasn't
available at that time. I'll try to up it here if I get the chance though.
Anyway, if my memory serves me, the configuration screen in Boyan requires a
minimum of 105K to the DOS shell in order to perform Zmodem transfers. Whether
there are additional memory allocations necessary for running BImodem, I don't
know, but I do know that Boyan uses as much available memory as it finds for
the scrollback buffer! Just where it draws the line for DOS shell needs and the
scrollback buffer I don't know, but if RAM is not a problem, try raising the
value for the DOS shell and check the scrollback buffer allocation if you can.
	If RAM is a problem for you then I suggest a terrific little Comm-Program
called COMMO v4.53 or v4.54 (both of which are available right here on Star
Factory). COMMO runs DSZ, MPt (and Puma) AutoDownload effortlessly, with a
capability for placing files in a default download directory (say B:\ or
C:\download\ if you are a registered user (if not, there are workarounds to
that as well). COMMO has powerful Macro language, an online help database and
most, if not all the features you normally only find in much larger packages.
	I run BImodem from the DOS shell of COMM v4.53 after compiling the        
transfer list while offline. BImodem v1.24 allows you to do this with the
BiList and BiMark programs that are included. (These are additional programs
that are not found in v1.20). To use BiList and BiMark; have a copy of the BBS
allfiles list on disk with (or in the same directory as) all of your BImodem
files. Then enter BiMenu and select Mark Files for Download from Capture List.
Enter the name of the filelist.ext that you'll be picking files from and scroll
through the list which will be displayed in a window. Press enter to select
files and continue picking files to complete your list of files to download.
Exit BiMark and decide which files to upload. Put them on disk with (or in the
same dir as) all of your BImodem files, which should be your current dir to 
avoid confusion.
	 Now you have to enter BiMenu again and select Transfer List Maintenance.
Once there, you should see the files that you had marked with BiMark in the top
half of the window. In the bottom half of the window, the first field (entry)
has only two choices, simply U or D. Type U and press enter. In the second 
field, Source File, type the drive, path and name of the file that you are
uploading (assuming that you have entered - N, to the entry in BiConfig (under
the heading General Options) Item #2 - Allow file names only (no paths), and
further, within BiConfig (under the heading Filenames and Paths) Item #4 -
Directory or list of Directories files are sent from [that you have specified
the directory(s) here]. Alternatively, you could have answered - Y, to the
entry in BiConfig (under the heading General Options) Item #2 - Allow file
names only (no paths) - and you would simply have only to enter the file name.
This works fine for floppy disk users. Keep it simple, upload from and download
to the current directory. For hard disk users, the choice is yours; the extra
overhead of having to copy files into the BImodem directory and either manually
deleting them when done transferring, or choosing delete source file when done
(from BiConfig, under the heading Upload Defaults, Item #4 - Y). As long as
care is taken that you are not deleting the only copy of the source file that
you are uploading, this works great for both hard and floppy users. With some
clever placement and timing of the files uploaded (sizewise), you should be 
able to download some good sized files onto the same floppy, as I believe
BImodem deletes the source file as soon as it is done transferring it, rather
than when done with the session as a whole.
	The third field, Dest(ination) File, is optional. In this case (uploading),
I leave it blank, as the BBS knows where to put the received file. In the next
field, Description, type a 40 character description of the file being sent from
your computer. The next field, Refresh, is optional. I leave it blank, which
presents no problems (Unless you are overwriting the file on the BBS, a
situation you are not likely to encounter, as the BBS will nix the transfer if
it already has that file catalogued). A quick search when online to make sure
the file isn't already catalogued doesn't hurt. The next field, Replace, is
similar to Refresh. I don't use it. (What point is there to overwriting files
that are already catalogued. If you're Resuming a prior failed transfer, why not
use Zmodem?). If you just leave the Refresh field blank, BImodem will use the
default entered in BiConfig (under the heading General Options) Item #3 -
Rename the file if it already exists - N. Another default in BIconfig (under 
the heading Upload defaults) Item #2 - If file exists, replace it - N. The next
field, Verify When Done is optional. Entering - Y here will have an effect on
the overall characters per second, which normally comes in at about the same as
Zmodem, but it doesn't hurt much. In fact, it's kinda wild to watch BImodem 
zoom through the comparison at warp speed. 
	The next field, Include Sub Directories, is not used at this time. Leave
it blank. The last field, Delete SOURCE When Done, in this case, applies to the
file(s) that you are uploading. If within BiConfig (under the heading Upload
Defaults) Item #4, you specify Delete source file when done - N, for safety,
you can always over-ride this when doing Transfer List Maintenance. If you
leave this field blank, the value that you had specified in BiConfig (under the
heading Upload Defaults stands. The file will not be deleted when done. An
entry of - Y here will over-ride the Default in BiConfig.
	Now you have completed the Tranfer List Maintenance and you can Exit by
pressing Alt-X (safer than assuming Esc-Undo will leave your list functional,
although I think it does). Right now is a good time to check the environment
variables that you have set for BImodem, BiMenu and BiPath. If you do not
already have them set, you can do this either through the DOS - SET Command,
or by placing them in your Autoexec.bat file. If you are running Bimodem from a
floppy disk, enter at the DOS prompt:

	SET BIMODEM=A:\
	SET BIMENU=A:\
	SET BIPATH=A:\

	If you are running BImodem from a hard disk, you would enter one of these
sets of entries:

1. If you have placed all of the BImodem files in a subdirectory of your hard
disk entitled C:\COMM  -	then enter:

	SET BIMODEM=C:\COMM			
	SET BIMENU=C:\COMM
	SET BIPATH=C:\COMM
	

2. If you have placed all of the BImodem files in a subdirectory of your hard
disk entitled C:\BIMODEM - then enter:

	SET BIMODEM=C:\BIMODEM
	SET BIMENU=C:\BIMODEM
	SET BIPATH=C:\BIMODEM

Obviously, if you have the BImodem files in a directory further down the
directory tree, then include it when setting the Environment Variables.
	You should also use the PATH Command to ensure that Bimodem will be able
to find its files by including the particular directory in your PATH statement.
If you don't already have one, enter at the DOS prompt:

	SET PATH=C:\COMM

		OR

	SET PATH=C:\BIMODEM

Or, whichever subdirectory that you have all of the BImodem files in.
	Naturally, your Autoexec.bat file will take care of this permanently.

The above procedures will handle running BImodem from the DOS shell, which both
Boyan and ProComm Plus are fully capable of. It is my belief that this is the
easiest way to run BImodem externally. You are not subject to all of the
idiotsyncrasies of the particular Comm-Program that you are running other than
their demands for RAM while shelled. I think this eliminates a number of
possible things that you wonder whether they are set right or not. Like, did I
set up the Hot-Key correctly? In ProComm Plus, this is fairly straightforward,
but in Boyan, how can you be sure what memory is allocated to the DOS shell,
when the Scrollback buffer grabs an unknown quantity of memory? The
documentation for Boyan isn't clear on this point. (See BOYANDOC.ZIP, this BBS
for insight into the world of Boyan - which incidentally has released v5.0!)
	At any rate, armed with your transfer list already completed, you can log
onto your favorite BBS (Star Factory, of course) and proceed to the files
directory. Request Upload, then choose BImodem for your protocol. After a short
pause, a messeage will appear that you have 120 seconds to invoke BImodem on
your end. No problem, you just go to the DOS shell from your Comm-Program, type
BiMenu and press enter. Now use the cursor keys to select Remote BImodem and
press enter. The rest is taken care of for you! Be patient, it takes a few
moments for Remote BImodem to invoke BiBat, the mini Terminal Emulator that
monitors the connection on the other end (the BBS) and invokes BImodem there.
You will see the message - DOS to Comm Gateway, Invoke Bimodem on the other 
end. Again, you don't have to touch a key! Your Transfer List is being proces-
sed and shortly BImodem's Menu Screen will appear with a window on the left
showing the file currently being uploaded and some other stats to captivate 
you. The window on the right will show the file currently being downloaded.
You will notice some extra activity from your disk drive as the Reads/Writes
alternate. The Chat windows below will keep you busy if you page the Sysop
and he is available (and if he has configured his side to allow a page).
Ctrl/G is the key combo to page the Sysop. 
	The transfer should continue normally to its conclusion and will verify
files when done if you have choosen that option and/or will delete the source
file (yours) when done if you have choosen that option. Don't worry you can't
delete the BBS's source file(s), nor should you try (shame, shame).
	I haven't used the other options in BImodem, such as BiHot, which is a TSR
that enables you to change the keys used for certain operations. (Probably for
designating which key combination is used for a Hot-Key). Also, there are
some features that are only enabled by registering BImodem, a few of which are
adding files to be uploaded and/or downloaded while online. This may be the
source of some of the problems users encounter when they figure that additional
input is needed to initiate the transfer. If your transfer list if properly
completed, no further input is needed after you - 1. Select BImodem from the
BBS. 2. Go to the DOS shell of your Comm-Program after being prompted to invoke
BImodem on your end. 3. Type BImenu and press enter. 4. Select Remote BImodem
from the menu and press enter.
	I hope that this short text will help clear up some of the problems that
users have encountered. I know the BImodem manual is rather involved and there
are quite a few entries to make in the configuration process, some of which I
will try to answer in another text I plan to include which will show the menu
screens and the entries I made for the configuration process. Please bear in
mind that I am in no way shape or form authorized by Erik Labs to be expounding
on these subjects, and this is intended solely as one BBSer trying to help
others. I know it's nice to get BImodem up and running first before deciding
whether to register your copy, but I feel as though I would be remiss if I
didn't encourage you to do so. Further than that, remember that my configura-
tion is set-up to run BImodem from a single floppy disk system with limited 
RAM. I'm sure that if you are comfortable with TSR's and would prefer to use
a Hot-Key to invoke BiMenu, then by all means do so.
											Sincerely,
											SuperCAD
 

	

	