Dec 272017
 
ProMenu is an advanced file transfer protocol shell.
File PROM0303.ZIP from The Programmer’s Corner in
Category Communications
ProMenu is an advanced file transfer protocol shell.
File Name File Size Zip Size Zip Type
BIHOT.EXE 19232 12033 deflated
PROMENU.DOC 36567 12436 deflated
PROMENU.EXE 67196 37903 deflated
PROMENU.REG 3921 1670 deflated
PRO_READ.1ST 5114 2162 deflated
PRO_VERS.ION 4786 2182 deflated

Download File PROM0303.ZIP Here

Contents of the PROMENU.DOC file


PROMENU 03/03/90 Modern Protocol Shell Key_Board BBS 1:114/35 (602)-846-2940
PROM0303.ZIP





SEE PRO_READ.1ST


ProMenu is a menu shell, for some of the newer, and commonly used
protocols.


Protocols should be placed into a directory contained in your DOS PATH
statement. A DOS PATH statement is usualy contained, as one of the first
lines in the AUTOEXEC.BAT file.


EXAMLPE ==>> PATH=C:;C:\DOS;C:\TC;C:\EDITOR;C:\PROTS

Or,

If protocols are in a separate directory specified in the PROMENU.CFG
file, ProMenu will append your path statement with this directory.
Appended PATH statements last only while ProMenu is running.

My setup contains the protocol directory in PROMENU.CFG, and not in my
PATH statement. The appendage works here, ProMenu has not been out long
enough to get much user feedback.

SET PROMCFG=path ProMenu will use this directory for CFG file
set promcfg=c:\prots

ProMenu reads it's cfgfile for all protocols, and also the BIMODEM.CFG
file while in BiMenu part of ProMenu.
ProMenu will create it's cfgfile if none is found, in the current
directory. It checks CFG filesize, to see if it's a ok version.


Bimenu reads the BIMODEM.CFG file for filenames, directories, and port.

**>>BiMenu /BiHot, will use whatever PTH "filename" is contained in the
BIMODEM.CFG file. Allowing for multiples. Use C)onfig to change names.
I changed the TAG-BI to BIHOT for registered users of BIMODEM. Registration
is encouraged, as if for no other reason enables ALL BIMODEM features.


ProMenu's P)ut Pick function is many times faster, if your config.sys
contains:
files=20
buffers=10
This will allow your editors, directory listers etc. to run much faster,
than most DOS default settings.




PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps






PROMxxxx.ZIP Was Zipped and Uploaded to the Key_Board BBS containing:

PRO_READ.1ST
PROMENU.DOC
PROMENU.REG
PRO_VERS.ION
PROMENU.EXE
BIHOT.EXE

Please do not add to or take from the above files package.
This includes Commpresion comments.














PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps





________________Contents________________








ProMenu Pg's 1-4,10

1.........ProMenu.CFG
2.........CFG/Protocols
3.........Command Lines to Protocols
4.........Command Lines to Protocols
5.........Transfers

6.........PATH statements/ProMenu arguments

Bimodem/BiMenu Pg's 5-9,11-13

7.........Function Summary (short)
8.........BIHOT.EXE/P)ut-Pick
9.........BIMODEM.PTH / E)dit / D)elete
10.........S)tart / C)onfigure / Bimenu-use-files
11.........Installation - Configure Bimodem, Directory paths, Options
12.........Telix, Boyan - Installation examples
13.........Extended SetUp Help \
14.........Extended SetUp Help -- Bimodem
15.........Extended SetUp Help /

16.........Distribution






PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_1_


ProMenu -Modern Protocol shell.


Basics...


===========
PROMENU.CFG
===========

The CFG file will be created with user input when ProMenu is invoked
and cannot locate it's CFG file in the current directory, or as set
with the DOS 'SET promcfg=c:\prots` command. Using "SET" will show
ProMenu a full pathname to it's CFG file.


Download path specified will be used for download activity.
ProMenu will change directories for download activity. Directory
specified in PROMENU.CFG will receive downloads. ProMenu changes back
when download activity is finished.


Upload path is the directory initialy listed by P)ut Pick.
Manual entries require a full pathname.

Uploads are presented to protocols with full pathname,
DRIVE\DIRECTORY\FILENAME.EXT . File names listed
in the batch window (uploads) are listed as filename only, full path
is contained in the list file.

PATHS are entered as: EXAMPLE==>> C:\BOYAN\DOWN
or: DOWN
Where down is a subdirectory of the current directory.

A "\" need not follow PATHS. ProMenu appends a "\" where needed, and
will strip a trailing "\" anyway.

Best to just enter DRIVE:\DIRCTORY format.

Your in the download directory during downloads, and the current directory
for uploads, except jmodem is in the upload directory.
ProMenu's M)anual option, accordingly, will expect a full path name.

SEE also the %PF switch;

Transfer protocol path will be appended to any existing PATH statement
found in the environment, or create a PATH, if non is found.
Environment changes will be restored to original when ProMenu exits.
ProMenu exits automaticaly after any transfer session.

@LISTFILE is the filename that ProMenu stores uploads to, for use with
protocols with batch capability. Default is PROMENU.BCH


Port numbers are specified as "1" = "com1, "2" = "com2" etc., suports
com1 thru com4.




PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_2_





PROMENU.CFG -continued


Default protocol selection determines which menu will come up at
startup. This may be overriden with the [p] on commandline.

All CFG options may be changed/toggled from any menu with the C)onfig
option.




====================
INDIVIDUAL PROTOCOLS
====================

All protocols supported are available on the Key_Board. ProMenu will
use CFG information and invoke protocols with all needed information, first
changing directories (DownLoad), or supplying filenames (Upload). Batch
protocols will operate in Batch or Single-file mode. Protocols with
batch capability, always, are fed a list file, in the form:

@DRIVE:\DIR\LISTFILE



While ProMenu provides easier operation to some users for supported
protocols, It is recommended that those often used be registered.

I'm not going to go into explaining each protocol operation. Except
that PUMA has a PUMASETUP program, which writes terminal specific data
to the PUMA.EXE file. If you don't use COM1, you will at least have to
run the setup, and change comm ports.
Superk will need to know it's overlay path.
Bimodem needs to have it's own CFG file in order.

DSZ.COM/EXE
PUMA.EXE -- Full batch capability, crash recovery, or enable resume
LYNX.EXE
SUPERK.EXE


JMODEM.COM -- Single file (This is not the J found with SK package)


BIMODEM.COM -- Bidirectional, interupt recovery,refresh







PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_3_



==========================
Command Lines to Protocols
==========================



From the C)onfigure menu, will be displayed two sets of command-lines.
The T)oggle option, toggles which set is currently in use. Each
protocol has a "Default" set (Up/Dn), and a "Custom" set of command
lines to protocol. Editing the command sets, is possible with the E)dit
option from C)onfigure menu. Set in use is displayed next to the toggle
option. Command-line "Switch" symbols, and their meaning, are visible
in the lower box.


The fillowing switches will take place, as represented on the command line
to protocol.

Switch symbals -meanings
======
%B Switch
%B replaced by BAUD BAUD[p],BAUDCFG
Baud as an argument [p] to ProMenu will always over ride CFG file. Baud as
default in CFG file, is a last-resort-option, for those who can't do it any
other way.

%P Switch
%P replaced with PORT NUMBER

%PF Switch
%PF replaced with filename, This switch will probably come last on command
line. When ProMenu sees the %PF switch, it will prompt for a filename, and
optionaly, prefix the filename with UpDir/DnDir as case may be.
The function will allow other switchs/args to follow...

%LF Switch
%LF replace by listfile, as @DRIVE:\DIR\LISTFILE




PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_4_



Command lines to protocols
==========================

Example use of the switches are contained as defaults, whenever ProMenu
builds a CFG file from scratch. All Protocol defaults contain working
examples.

Editing the current "SET", is available from the E)dit option, within
the C)onfigure menu.
Use T)oggle to select set for edit. The command line to protocol will
NOT contain "PROTOCOL NAME", as first argument.

EXAMPLE command lines to protocol for DSZ

port %P speed %B sz %LF
%P sz %LF
Both above will have the same affect, a DSZ Zmodem upload on port 2
using the listfile as source of filenames.
NOTE that "DSZ" is not part of the command line...

If you mess things up, ProMenu will fill in all defaults, each time a
new CFG file is built.

Command lines to protocols are built up at transfer time, The display within
the C)onfigure menu, displays command lines in "Switch-symbol" form.

Arguments to ProMenu such as, 'promenu 2400 z u` will use the current "SET"
of command lines to the protocol, and require the listfile contain filenames.
A valid filename may be used on the command line to protocol, in lew of
listfile, for single file transfer. You will need to include a full pathname,
or keep in mind, ProMenu will be in the DownLoad directory when invoking
DSZ. The above argument will cause an immediate DSZ zmodem upoload at 2400
baud, on the comm port as found in CFG file. This type of argument makes
ProMenu callable from a script. It is this area new ideas for "Switches"
will have the most impact.

ProMenu is in Download DIRECTORY during downloads, and in Current
DIRECTORY during uploads, -Jmodem uploads are from Upload DIRECTORY.





PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_5_


=========
UPLOADING
=========

BATCH PROTOCOLS:
Filenames entered for upload format, all are placed into a listfile
handed to the protocol at runtime. P)ut Pick option will list whatever
directory specified in PROMENU.CFG as SEND Directory. The file list
is displayed alphabeticaly. Listfile contents are presented in a window
located to the right of the protocol menu. M)anual entries are added
to the listfile.
Batch protocols will also operate as single file.


SINGLE FILE PROTOCOLS:

Single file protocols are at this time not using a LISTFILE and cannot
be "preloaded", as with batch capable protocols.

The %PF switch found as command to protocol will prompt for filename,
and insert filename, as found on command line to protocol.

===========
DOWNLOADING
===========

Most protocols get download filenames from the other end, Jmodem
requires a filename, ProMenu will prompt for a filename for a Jmodem
download. THE %PF MUST be present for filename prompting. See the
default settings to jmodem, to see the %PF switch in use.

ProMenu changes to your Specified DOWNLOAD directory before starting
a selected protocol. This directory change requires that the directory
protocols are stored in, be included in your DOS PATH statement, or
entered into the PROMENU.CFG file.

Protocols stored in the current "COMM" directory, will require that
"COMM" directory be included in your DOS PATH statement. I keep mine
in a specific directory "C:\PROTS" , and enter this path in the CFG
file. ProMenu will append your existing PATH statement with whatever
path-name is contained in the CFG file.(just to make sure),



PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_6_



* How ProMenu handles your "PATH" statement as found or not found
in the environment.

1. First check current environment for a PATH statement
2. If we have one, append it with ";protocol-path"(as found in CFG file)
3. If no path statement found, make one
4. Add to current environment "PATH=protocol-path"(as found in CFG file)
( Changes dissapear when ProMenu exits, leaving your original )

Commands passed to protocols are basic, using recovery where applicable.

After a download transfer ProMenu will change back to original
directory, and exit.


=================
ProMenu Arguments
=================

ProMenu [baud] [p] [u/d]

[baud] always preceeds a [p] arg, [p] always preceeds [u/d] args

[p] -overrides default protocol found in CFG file
[u] -Automatic "do upload" Batch-capable protocols only
[d] - download


promenu <<== Default baud, protocol used from CFG file

promenu 9600 <<== Baud arg always overrides CFG file's baud


promenu 2400 z d <<== Starts DSZ-Zmodem download without further
user input.



[u] option requires that LISTFILE be preloaded with one or more
filenames

[d/u] options must be preceded with a [p] option









PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_7_


BiMenu starts here
------------------
Function Summary



BIMODEM PKG. NEEDED FILES: BIMODEM.COM,BIPATH.COM,BICONFIG.COM

NOTE==> storing above files in a util directory or???, rather than the
current dir, is cleaner and BiMenu will find them as fast any way.
Use your PATH statement. example:>> PATH=C:\UTIL;C:\DOS;C:\EDITOR
^^^^^^^^^^^^^^^^^^^^^^^^
If not in current dir, then the DOS PATH is searched. Files not found result
in a not found "filename" message and BiMenu expects a 'keypress' to continue.
If the BIMODEM.CFG file is missing or incomplete, BiMenu will invoke
BICONFIG.COM.
==>> Bimod120.xxx BiConfig.com will come up from the DOS PATH, and build
a CFG file, in "it's" current directory. Not "Your" current directory. To get
around the hassle, BiMenu uses searchpath, seeks out and moves the CFG
file to your current DIR.

If BiMenu has found it's needed files(normal), it does a qwick read of the
BIMODEM.CFG file, gathering default RECV/SEND directories, PORT num,
LogFilename to use and the PathFilename to use.
BiMenu then checks the 'default PTH' file and calculates number of entries.

Main Menu- Will display options, CFG defaults, PORT num., Baud arg,
Number of PTH file entries.

BiMenu/BiHot.EXE, will use what ever PTH filename is contained in the
CFG file. You may have several PTH files, just C)onfig to change the name
and alt-x to quit/save. ESC for 1.2 and newer versions of Bimodem.
In other words The default PTH file is
BIMODEM.PTH, but it could be A,B,C,D, etc.. or king_bbs,Key_bbs, etc..
Each time BiMenu or BiHOT.EXE, read/write to the PTH file, they first check
CFG file to know PTH 'filename', allowing changes on the fly, without
restarting BiMenu.
NOTE ==>> BIHOT.COM provided to registered users reads the CFG file for PTH
file when started, not with each pop-up.
The TSR BIHOT.EXE provided with PROMENU is at best a simple utility
and for regular use, I encourage the registration of BIMODEM, and
getting the REAL thing.

P)ut-Pick does upload format only, and BiHot.EXE does download format only.
P)ut will use the Send path as specified in CFG file, as default.

S)tart option will send a "B" wait 1/10th second send a over PORT
as found in CFG file, wait a second and invoke BIMODEM.COM at your end.
Most BBS's will use a B) option for bimodem, and this allows starting both
ends from BiMenu.
Current meathod of sending a B CR uses the Bios function interupt 14 hex.

NOTE==> BIMODEM package comes with a whole bunch of CFG files. I sugest
deleting all these as, the C)onfig option will create the one you need.
Most user confusion setting up is over these files. For a detailed setup
guide see "Installation" (Pg-5) this doc.





PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_8_



BIHOT.EXE will load and may be brought up with LEFTSHIFT-ALT-B

Tag, supports [spacebar] tagging, [K]eep (resident, but exit), or
[ESC] to unhook and exit. The usual "row-25" help-bar displays all possible
choices. TAG-BI.EXE writes directly to the PTH file and is configured
for the Download format. Uploads must use P)ut-Pick.(from BiMenu)

BiMenu and BIHOT.EXE, read the BIMODEM.CFG for PTH filename, before any
read/write operations. This allows for useing differantly named PTH files
by popping up the C)onfigure option.

Tagging will be most aggressivley used while online.
BIHOT.EXE will be popped up after a files display from the BBS,
has filled the screen. THE TSR will pop into any Comm Prog, allow filename
tagging, and a choice of exits. (remain memory resident(K)) or (UnHook (ESC))


File listers which change directories while displaying a file will
cause BIHOT.EXE to create a new PTH file in that directory. PTH files MUST
be in your Comm progs current dir, or along the default path in the CFG file.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


==>>BIHOT.EXE should not be activated while your comm programs screen display is
active. Wait for the incoming to stop. Calling BIHOT.EXE during io activity,
may cause your comm program's "low-level" IN/OUT routine trouble. Popping
up after the display has stopped cannot cause any trouble.
TeSeReact.LIB Copyright 1986,1987,1988 TeSeReact Development Team





P)ut-Pick: The function will read BIMODEM.CFG file for a default Upload
directory. You have the option of pressing for default, or you
may specify another directory. EXAMPLES===>> \boyan\d, a:, d:\prog
A \ should not be entered after the directory, Bimenu will append \
itself.

File names chosen with P)ut-Pick, will be written to the PTH file
directly, with full path. Adding the path-filename in this mannor
allows uploads from other than BIMODEM.CFG's upload directory. The P)ut
function contains helpfull prompts, making clear it's proper use.

**** P)ut's delete option is instant, so be aware!



PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_9_



PTH FILE: This is a formatted file, BIMODEM.COM reads to know
what files are to be transfered, and where to find them. Uploads and
downloads may be specified in advance, or online, or both, and your
uploads will be transferred at the same time as the downloads. The
PTH file will also except any file descriptions for uploads, and
descriptions will be automaticly tranfered along with the upload.

All filenames are entered at the "Source Filename" position directly
under U or D in the PTH file. The "Destination" position should not be
used for normal BBS use. As this is for the "new file name" at the other
end. For a Demo of the PTH file layout use the Pick functions,
then select BIMENU's E)dit option. You will see your selections where they
belong and using your and keys will move the filenames
from window to window,(in the PTH file).

Default PTH filename is BIMODEM.PTH. You may change the filename at any
time, and BiMenu/BiHot.EXE, will use the current PTH file interactivley.
^^^^^^^^^^^^^^^^^




E)dit: The function invokes BIPATH.COM ,and will allow edditing of the
current PTH file entries. will delete an entry posted in the
lower window. One entry is posted in the lower window at a time.
initialy clears the upper window, but the entries are not deleted, they
are on deck ready to be popped in using the key. Spending a few
minutes popping and pushing filenames, along with upload-descriptions,
will prove time-saving, for \"online\" conditions.

The Edit option uses the current PTH filename as in CFG file.

NOTE! BiMenu calls BiPath as BIPATH FILENAME
Starting BiPath from DOS may cause your PTH file be erased.
See Bimodem Doc.



DELETE option from main menu...
D)elete: The function immediatly deletes the current PTH filename.
Remember, you may have several PTH files, as quickly as popping CFG up, and
typing new name. BiMenu works on the current PTH file, as found in CFG.









PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_10_




S)tart: The function is designed especially for BBS's that use a B)
option to invoke BIMODEM. S)tart function will send a B to the BBS,
wait 1/10th second then send a carriage return , to the BBS,
then pauses 3 seconds before activating BIMODEM.COM at this end.
(Uses Bios function, interrupt 14 hex.)

BiMenu will attach a baud arg , if present when BiMenu is started.
BiMenu uses the int 14h meathod and should be compatable with most
systems, and fossils.

In most cases this will start BIMODEM on each end. With this an exit
from editing, DOS or whathave you, provides for starting the transfer
without first returning to Terminal mode and making the selection directly.


==>> The sending of a B CR will not affect your having already invoked
Bimodem on the other end.



C)onfigure: Invokes BICONFIG.COM, for CFG file creation. Also make
quick changes (directories, crash recovery, refresh, etc) while
online.
Bimodem 1.2 package: Calling Biconfig.com from DOS, Biconfig will build
a CFG file in it's current directory. If you have
your executables along your PATH statement, you may
have to copy the CFG file to your current working
directory manualy. BiMenu will copy the CFG file
from wherever Biconfig.com comes up, to your current
working directory.

Changing PTH filenames, may be done fron C) option, A quick PTH change
will be detected and used without restarting BiMenu.
==>> Default PTH filename is "Bimodem.PTH"



Until you become familiar with BiModem, it is best to specify only
your upload and download directories, the COMM port to be used, and
some of the file characteristics for transfers. After specifing the
upload and download directories, press until you get to the
COMM port #'s 1, 2, etc. Select your correct COMM port and then
continue to press until you've gone through all the options.

Don't change any COMM port addresses unless you know EXACTLY what
you're doing. Read BIMODEM.DOC, supplied with BiModem, before
resetting any other options.

BiMenu invokes BICONFIG.COM ==> Bimodem v1.1 and later.
For earlier Bimodem versions, use bimodem /i from DOS.





PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_11_




Installation:




Configure BIMODEM: Only two files are needed in your COMM-PROG's directory.
BIMODEM.CFG, & PTH file... BIMODEM.COM,BIPATH.COM,BIMENU.EXE,BIHOT.EXE may be
located anywhere along your DOS-PATH. Before using the BiModem protocol,
you have the option to change BIMODEM's default values. BIMODEM uses
port 1 as default. Default Upload/Download directories, are the current
directory. Basicaly, if you use Comm Port 1, you can get by without
makeing any changes, and a CFG file will be created automaticaly.

Of most confusion, are all the CFG files contained with the BIMODEM
package. I suggest deleting all those CFG files. Then run C)onfig to
create a CFG file for your system.

C)onfigure option will invoke BICONFIG.COM for CFG. Default Port is 1.
If using another Comm Port, you will need to specify it.


Directory Paths: It may be more convenient to have your transfer files
come and go from directories of your choice. The very first entries in
BIMODEM's CFG window are "User specified" default download directory and
upload directory, consecutivly. Here you may enter the path for downloads
to be put, and uploads to originate from. NOTE:=>> \ is not to be put
after the path string. EXAMPLE:=>> C:\BOYAN\D <<= CORRECT
C:\BOYAN\D\ <<= WRONG-won't work

Options: There are many transfer characteristics which may be altered.
It is best to past these until you have the protocol working and
are ready to make intelligent changes. The Defaults will work fine.











PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_12_
==================
Telix installation
==================

Select the external protocols menu.




External Key Protocol Upload Download Bat or DL
Protocols Name Filename Filename Script Name
A................. P ProMenu's prom.bat prom.bat Batch N
B.................
C.................

The 'Key' option is the letter that will invoke ProMenu from TELIX's
protocol menu.


==>> EXAMPLE: PROM.BAT promenu %1
^^ traps the baud arg passed by Telix

You will have to type in the baud arg when prompted from Telix, or with
ProMenu versions 02/27 and later, except the default Baud, as found in
PROMENU.CFG file.


===================
Boyan installation
===================

ProMenu was written using this Comm program. Passing current baud arg is made
simple for Boyan users, with the %MS macro.

Macros: (select any key you want) F1-F9 or alt-F1-F9, etc.

Examples calls to ProMenu,
F9 >> \dc[promenu %MS
F10 >> \dc[promenu %MS z d

BIMODEM.COM, BIPATH.COM, PROMENU.EXE and BIHOT.EXE can be located along your
DOS path. You will need to run the BiMenu C)FG option or BiModem's
BISETUP.COM. The .CFG file must be in the same directory as your
communications program, and PTH file will be created there when using the
Bimenu P)ut,T)ag or E)dit options.
For DSZ form ProMenu, Boyan's default "memory for DOS shell" will have to
be changed from 180k to 200k, for Bimodem to 220k, I use 240k.




PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_13_



=================================================
EXTENDED HELP WITH SETUP/INSTALLATION
Using the Bimodem Protocol
-------------------------------------------------



Step by Step...
BiMenu will refer to the ProMenu-BiMenu menu
callable directly with "PROMENU [baud] b"
1...Copy BIMODEM.COM, BIPATH.COM, BICONFIG.COM, PROMENU.EXE
all into a directory along your DOS PATH, or into your Comm directory.
BiMenu will search for needed files, and if any missing, will tell you
so.
2...Do Not copy all the CFG files! Above files are all needed. Other
BIMODEM pkg files like (BIMENU.COM,etc.) are of coarse optional.
You will create your own CFG file.
3...With the above. Start BiMenu, then if no CFG file(new user),
You will be asked to creat one, and BICONFIG.COM is invoked by BiMenu.



NOTE==> BiMenu will not come up without a CFG file present. Also if it
is incomplete you will see blank spaces next to the CFG data
display from Bimenu.

Anoying for checking out new BiMenu versions, but it will save some
new users alot of BBS time.
In other words type in the dir selections RECV,SEND. This is minimum
for BiMenu to come up to main menu...



Filenames and Paths <== Select this option from BICONFIG

4...CFG file: The first two entries deal with directories. Specificaly,
default RECV (downloads), and default SEND (uploads). May be same
directory or two separate ones.

EXAMPLE ==>
RECV directory
C:\B\D NOTE:==>> a \ does not trail...
SEND directory
C:\B\U







PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_14_


Terminal Options <== Select this option from BICONFIG

5...Run thru BICINFIG and set the port #, default BAUD.
6...All other options, by default, are fine for now.
7...Write Setup to Disk <== Select this option
8..Your BIMODEM.CFG file should be ready for use.
NOTE==> All the other options can be fooled with after a few succesful
transfers. Best to keep simple for first time.
With this BiMenu should come right up, when invoked. It will check for
needed files, read CFG, and display your settings from the main menu.

PTH file:
Your PTH file comes in to play whenever using tagging, editing, or when
BIMODEM.COM, needs to transfer. You don't have a PTH file yet.

9...With BiMenu running, you should see the CFG file directories you entered
in your lower left corner of screen.
PTH file display "ENTRIES" will be dim, and a 0 number.
If your Send directory contains files, P)ut-Pick option will default to
that directory, and you may use UP DN keys to move cursor, then
use your spacebar for tagging. Selections are written directly to
PTH file (default is "BIMODEM.PTH")
You are in P)ut-Pick (Uploads) so BiMenu will prompt for a description
after each Tag. You may simply press for next, or enter a
description now. BIMODEM.COM prompts the other end for a description when
none is attached to a file. Best to enter descriptions off line.
A good description enhances any BBS, Files, and stimulating an environment
for quality.


ESC key exits from P)ut-Pick. Now you have a PTH file, and if not changed
in CFG file, it is BIMODEM.PTH .
BiMenu's "ENTRIES" display should be lit, and the number of selections
in decimal.
10...BiMenu/BIMODEM should be set for any session where you are uploading.

But that's no fun. Your first time should be both ways or nothing.

If you know the BBS you will be calling, just use the edit option to
add a file. Allfiles.xxx

EXAMPLE==> (U)pload/(D)ownload D <== you enter the "D"
Source file-> KEYFILES.ZIP

You needn't enter anything else for a download.




PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_15_



DISPLAY
BiMenu will be displaing any info needed for a successful BIMODEM
session. Below BiMenu's Option's are your CFG file settings.

Check for:
- BAUD arg
- PORT #
- SEND DIR if these are correct, BiMenu is popping "right up",
- RECV DIR you should be ready.


Use BiHot.EXE after you see what's going on.


11...(later on, and online)
If the BBS has B)imodem, and your in the file arera, and B) is the Bimodem
option, Then BiMenu should start both ends. Bring up BiMenu(baud arg not
neccassary for success). Your display of "ENTRIES" should be lit, and the
decimal value for entries displayed.
Since you are now "online", the BiMenu's "CARRIER" light should be on.

==>> However all machines may not be so compatable, causing the auto start
at other end feature and Carrier light , incompatable. There always seems to
be a user out there who must do a manual start.

12...S)tart Bi option will send a B wait 1/10th
send a CR (same as ) wait 3 seconds
then start BIMODEM.COM at your end.

BiMenu calls BIMODEM.COM as
BIMODEM /B default -See C)ustom option

/B <== if baud arg is present it follows /B
if not present, ignored by BIMODEM.COM










PROMENU -MODERN PROTOCOL SHELL Copyright 1989/90 Michael G Phelps

_16_




Licese to use and distribute





This program is distributed as SHAREWARE
The right to use and distribute this program is subject to the following:

PROMxxxx.ZIP Was Zipped and Uploaded to the Key_Board BBS containing:

PRO_READ.1ST
PROMENU.DOC
PROMENU.REG
PRO_VERS.ION
PROMENU.EXE
BIHOT.EXE

Please do not add to or take from the above files package.
This includes Commpresion comments.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^



ProMenu Modern Protocol shell Copyright 1989/1990 Michael G Phelps





ProMenu is the result of many hours. Providing a fairly fast and efficient
protocol menu shell, with minimum overhead.

Use of ProMenu in a business or commercial environment, requires
prior registration.

ProMenu is distributed as shareware. The shareware concept allows you
to try out a program, for a period of time, while deciding whether it
suits your needs. If you find ProMenu to be a useful utility, and it
resides on your disk after a short trial period, you are obligated to
register the program.
Continued usage after 30 days, requires registration...

Registered versions of ProMenu are without pre-exit Add-Screens, and
may be somewhat cusomized upon request. Minor customizing will specificaly
deal with default commandlines used with protocols, and defaults in the
CFG file.
I have been pretty good about responding to suggestions and specific
requested changes. Your registrations let me know whether the ProMenu
project merits continuance. Creating my own personal version is simple,
a version suitable for the wide variety of users who will use ProMenu
takes a great deal of time, and effort.

Future version updates include custom protocol command lines, addition
of more "external" protocols, ability to be launched from a script,
your suggestions.




ProMenu




$10.00
Reasonably priced.


To Register ProMenu

Register: Once for all future versions

$10.00 Enables downloading a NO-ADD copy of ProMenu from the
Reg_user door, on the Key_Board, as updates are available.
$10.00 And a self addressed disk mailer (post-paid) and I'll mail
you the latest version. on a (5.25 ", MS-DOS DS/DD Disk

$12.50 You can skip sending the disk mailer, just include your Name
address,zipcode on the registration form.

All future versions will be downloadable from the Reg_User Door on
the Key_Board, or available by mail. Mail upgrades will require a
self addressed, postpaid Disk mailer, along with formatted Disk.
or,
$2.50, And I'll lick the stamps on a (5.25 ", MS-DOS DS/DD Disk

Remember to include your PASSWORD when updating ProMenu. (see below)






ProMenu Modern Protocol shell Copyright 1989/1990 Michael G Phelps



Information below is required for Pre-Log on status into Reg_User area,
and obtaining future upgrades.

( see filearea menu for door # )
Michael G Phelps
Key_Board System
4819 N 57'th Dr.
Phoenix AZ 85031
=========================
ProMenu User Registration
=========================

Name: =====>> ____________________ ______________________
first last

Address:===>> _________________________________________________
street

_________________________________________________
city state zip

PassWord:==>> _________________
( see below )


==>> ______
Number of copies you intend to register at this time.

Amount enclosed:==>> $______.____

Password you will use to log on to the Key_Board, as a Reg_User
Password format:
First & Last initial MP
BirthDate 10 04 55 Month Day Year
MP100455.ZIP You will be downloading your "PASSWORD.ZIP"

If you are already a user on the Key_Board, this password is just for
downloading of upgrades, not what what you need to log on...


 December 27, 2017  Add comments

Leave a Reply