ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

home *** CD-ROM | disk | FTP | other *** search

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / MISC / PROM0701.ZIP / PROMENU.DOC < prev

Wrap

Text File | 1990-07-01 | 35.0 KB | 1,230 lines

▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒ ▒▒▒▒ ▒▒▒▒▒▒▒ ▒▒▒▒▒▒ ▒▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒ ▒▒ ▒▒ ▒▒▒ ▒▒ ▒▒ ▒▒ ▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒ ▒▒ ▒▒ ▒▒ ▒ ▒▒ ▒▒▒▒ ▒▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒ ▒▒▒▒ ▒▒ ▒▒ ▒▒▒▒▒▒ ▒▒ ▒▒▒ ▒▒▒▒▒▒ by Michael G Phelps of 1:114/35 =================================================================== Contents =================================================================== ProMenu Protocol Manager Utility Documentation ProMenu v.07/04/90 Copyright 1989/1990 by Michael G Phelps ------------ Introduction I ProMenu at a glance ------------ II ------- ---- Chapter Page ------- ---- 1 PROMENU.CFG ........................................... 1 2 INDIVIDUAL PROTOCOLS .................................. 5 3 COMMAND LINE to PROTOCOL .............................. 7 Default Command line to Protocol Set's ................ 11 4 PROMENU ARGUMENTS ..................................... 12 5 TRANSFERS ............................................. 13 6 ProMenu Installation .................................. 14 7 ProMenu/BiMenu - BiModem .............................. 15 Distribution Information ...............................18 =================================================================== ============ Introduction ============ ProMenu is simply a manager for some of the newer protocols including DSZ, BIMODEM, PUMA, LYNX, SUPERK, JMODEM. Each protocol is equipped with two sets "command line to protocol". Command line to protocols are both viewable and editable from the C)onfigure menu. PROMENU.CFG, initialy contains working default sets for each protocol. Protocols may be placed into a separate directory. You will enter the directory path as the "Prot Dir", in PROMENU.CFG. ProMenu will append your path statement with this directory. Appended PATH statements last only while ProMenu is running. Or, Protocols may be placed into a seperate directory in your DOS PATH statement. A DOS PATH statement is usualy contained, as one of the first lines in the AUTOEXEC.BAT file. My setup contains the protocol directory in PROMENU.CFG, and not in my PATH statement. Since BOYAN v 4.0x, allows a "path to protocols". ProMenu is written while using the very excellent Comm program Boyan version 4 or recent. If you must keep all these files in your Comm prog's directory then enter that directory as "Prot Dir" in PROMENU.CFG. SET PROMCFG=path ProMenu will use this directory for CFG file and attach the LISTFILE to this directory as well. set promcfg=c:\prots ( put as a line in your AUTOEXEC.BAT file ) This allows for a much cleaner setup, as Comm Program directory need not be cluttered with all the protocols, and batch files associated with them. ProMenu reads it's cfgfile for all protocols, and also the BIMODEM.CFG file while in B)iModem part of ProMenu. Since ProMenu is a take off from the original BiMenu, I'l be refering to B)imodem Menu from ProMenu, as BiMenu thruout most of this documentation. BiMenu reads the BIMODEM.CFG file for filenames, directories, and port. ========================== Introduction , continued ========================== BiMenu will use whatever PTH "filename" is contained in the BIMODEM.CFG file. Allowing for multiples. Use B)iconfig to change names. ProMenu's Put Pick function is many times faster, if your config.sys file contains: files=20 buffers=10 This will allow your editors, directory listers etc. to run much faster, than most DOS default settings. =================================================================== ProMenu Was Zipped: PROMENU.DOC * Hopefully instructional information PROCFG.EXE * Builds PROMENU.CFG, filling in defaults PROM.EXE * Main program Please do not add to or take from the above files package. This includes Commpresion comments! =================================================================== C:\TC\BIM\X>pkzip -v prom0701 *.exe PKZIP (R) FAST! Create/Update Utility Version 1.1 03-15-90 Copr. 1989-1990 PKWARE Inc. All Rights Reserved. PKZIP/h for help PKZIP Reg. U.S. Pat. and Tm. Off. Searching ZIP: PROM0701.ZIP Length Method Size Ratio Date Time CRC-32 Attr Name ------ ------ ----- ----- ---- ---- ------ ---- ---- 24902 Implode 14133 44% 07-01-90 13:21 93622168 --w PROCFG.EXE 56140 Implode 34162 40% 07-01-90 13:21 6e949dfe --w PROM.EXE ------ ------ --- ------- 81042 48295 41% 2 ----------- Directories ----------- PROMENU.CFG contains three directory PATHS PATHS are entered as: EXAMPLE==>> C:\BOYAN\DOWN A "\" need not follow PATHS. ProMenu appends a "\" where needed and will strip a trailing "\" anyway. PgDn / R)ecv Dir * Directory where downloads are to go PgUp / S)end Dir * Directory P)ut Pick will list by default ( may be the same or seperate directories ) Recv PATH specified will be used for download activity. ProMenu will change directories for download activity. Recv PATH specified in PROMENU.CFG will receive downloads. See the %RD switch symbal. If D)ir swap is "On" ProMenu changes to the Recv PATH just before spawning a protocol, changes back to original Dir, when download activity is finished. Note the use of O)verlay mode as it applies to D)ir swap "On" Send PATH is the directory initialy listed by Put Pick. Put Pick is the "Listfile" / "PTH" builder. Manual entries to "Listfile" require a full pathname, or be located in the working directory. ProMenu will stay in the working directory for uploading, all filenames contained in the "Listfile" created with Put Pick do, require a FULL "DRIVE:\DIR\FILENAME" format. From any of ProMenu's "Main" menus you will see the contents of the "Listfile". ( except BiMenu, which uses it's PTH file ) Prot Dir * Directory Path to Protocols * "PATH to Protocols" will be appended to any existing PATH statement found in the environment, or creat a PATH, if non is found. Environment changes will be restored to original when ProMenu exits. ProMenu exits automaticaly after any transfer session. PAGE 2 You don't need to include the Prot Dir in your DOS Path statement. ProMenu will add this while running. Quality Communication programs like "BOYAN4.+" allow a separate directory be kept soley for protocols. ProMenu appreciates and uses this "clean" approach. -------- LISTFILE -------- "LISTFILE" * ( See also the %LF switch ) "LISTFILE" is the filename that ProMenu stores uploads to for use with protocols with batch capability. Put Pick writes to the "LISTFILE". Default "LISTFILE" name is PROMENU.BCH. You may rename this from ProMenu's C)onfigure menu. Multiple "LISTFILE" names may be used P)ut Pick / %LF switch will use which ever "LISTFILE" name is current. "LISTFILE" names are appended the extension ".BCH", if none is given. ------------------- Port / Default Baud ------------------- (#) Port Num * ( see also %P switch ) ($) Baud (default) * ( see also %B switch ) Port numbers are entered in decimal. COM1 = 1 COM2 = 2 etc. ( For the send 'B CR` from BiMenu with Bimodem, I support to COM4 ) Use beyond Port 4 only means I won't be sending a 'B CR` out the port when S)tart BiModem option is chosen. Baud as found in PROMENU.CFG is a "last resort" option. And will be overidden by Baud as ProMenu's first argument. [b] arg See ProMenu Arguments, the [b] arg, also the %B switch. PAGE 3 ------- C)olors ------- C)olor customizing is possible within the C)onfig menu. Use your arrow keys for color toggle of HighLighted Menu type. Default colors are restored with creation of a NEW cfg file using PROCFG.EXE ------------- O)verlay mode ------------- Overlay mode determines whether ProMenu gives up it's location in memory to the protocol, or remains till after transfer. Reasons for ProMenu sticking around will be for D)ir swap "on", ProMenu has changed to your Recv Dir, and will change back after a download session. Also if you want your bell to ring after transfers, overlay mode will have to be "off". Now it is important to realize that when overlay mode is "on", ProMenu will cease to run immediatly upon execution of your protocol. Overlay mode "off" and ProMenu is in the background, and able to finish up after. If you a Registered version of DSZ, want to use the %RD switch You will most aggresivly have overlay mode "on", and dir hopping "off". In this configuration all available memory is given up for DSZ. It boils down to squeezing all you can from what RAM you have. ------------ D)ir swap ------------ All Dir swap means is that ProMenu will change directories for downloading before executing a protocol, to insure that files get into your Recv Dir. This is the meathod used by any comm prog which redirects downloads for external protocols, which do not except a Recv Dir Arg. For instance UnReg. DSZ versions. Note::: Puma and Lynx are written by the same author, and will lock my machines everytime, when executed in Overlay mode "on". Until this bug is fixxed, ProMenu has internaly locked out the Overlay mode "on" option when it detects Puma or Lynx being used. Those who wish to play with this, have the source code used in ProMenu for the spawn functions, may netmail me, and will make available a ProMenu version which allows for launching Puma and Lynx with a P_OVERLAY call to TC 2.0's spawn function, as well as the C src. I use. All other protocols I can get my hands on do not have this problem. PAGE 4 CHAPTER TWO =========================================== INDIVIDUAL PROTOCOLS =========================================== ------------------- Protocols supported ------------------- -Batch capable Batch capaple protocols ALL will except a "LISTFILE" in the form @DRIVE:\DIR\FILENAME.LST ProMenu's L)istfile option will creat this with "SPACEBAR" tagging. Batch capable protocols use the "LISTFILE" for uploading filenames. Batch capable protocols WILL recieve filenames from other end for downloading single or batch. BiModem however, needs to be "Pre-Loaded" in it's "PTH" file with Up / Dn load filenames. *NOTE well that Registered versions of BiModem will allow user updating from either end, of the "PTH" file while a transfer is in progress. This "File-Request" method may be turned off on a BBS end, if the SysOp is aware of the flag. DSZ.COM/EXE * OMEN TECH PUMA.EXE * Mathew Thomas LYNX.EXE * Mathew Thomas SUPERK.EXE * -Bidirectional Bimodem is Batch capable but uses it's own "PTH" file. Put Pick uses "PTH" file when invoked from BiMenu. BIMODEM.COM * ERIK LABS -Single file Single file (Jmodem) is not using the L)istfile function at this time. It may be "Pre-Loaded" by entering a filename directly onto "command line to protocol" or, it uses the %PF switch. (NOT the J found with SK package) JMODEM.COM * PD PAGE 5 Batch protocols will operate in both single and batch modes. A "LISTFILE " needn't contain more than 1 filename. DSZ allows up 9,999 file names be presented via "LISTFILE". All protocols supported are available on most BBS's. ProMenu will use PROMENU.CFG file information, and invoke protocol's with current appropriate Recv/Send "command line to protocol". ::D)ir Hopping "on" If Recv Dir found in PROMENU.CFG is not "Working Dir", ProMenu first changes directories for a download, before spawning protocol. ProMenu will remain in "Working Dir" for upload activity. ::Dir Hopping "off" ProMenu will not change dirs for Recv. See also O)verlay mode and the %RD switch symbal. Batch capable protocols, are best fed a "LISTFILE". @DRIVE:\DIR\LISTFILE ( see %LF switch ) Use of a "LISTFILE" is most convenient, however you may edit a "command line to protocol" entering "FULL PATHNAME" optionaly. 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 in detail. PUMA has a PUMASETUP program, which writes terminal specific data to the PUMA.EXE file. If you don't use COM1, you should at least 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. Jmodem "command line to protocol" format defaults, are meant for the PD Jmodem package. However you may simply rename the "J" executable wich comes with the SuperK package, and edit the "command line to protocol" accordingly. If you want Jmodem Batch. PAGE 6 CHAPTER THREE ======================================== Command Line to Protocol ======================================== ------- E)dit ------- From the C)onfigure menu, will be displayed two sets of "command line to protocol", for each protocol. The UpARROW DnARROW, toggles which set is currently in use. Each protocol has a "Default" set (Send/Recv), and a "Custom" set of "command line to protocol". Editing the command sets, is possible using the E)dit option from ProMenu's C)onfigure menu. S-String 'command line to protocol` R-String 'command line to protocol` The "command line to protocol" is presented on the edit line at time of editing. You will be prompted for both Up and Dn formats with a single selection of the E)dit option. Simply press <ENTER>, or ESC key to skip. All changes are saved to PROMENU.CFG file. <ENTER> after editing to "save", ESC to abort changes. -------------- Switch Symbals -------------- The following switches will take place, as represented in the "command line to protocol". %B Switch * BAUD %B replaced by [Baud] or default Baud NOTE: ( Argument order ( ProMenu [baud] [prot] [u/d] ) ) SEE Also Chapter on "ProMenu Arguments" Baud as argument [baud] to ProMenu will always over ride CFG file. Baud in CFG file, is a last-resort-option, for those who can't do it any other way. ( default baud is for a ProComm user that couldn't use the Excellent Comm Prog BOYAN4+! ) %P Switch * Port %P replaced with PORT NUMBER ( as found in PROMENU.CFG file ) PAGE 7 %PF Switch * Prompt for Filename %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 Send Dir / Recv Dir , as case may be. The function "will" allow other switchs/args to follow... %LF Switch * LISTFILE %LF Replace by "LISTFILE", as @DRIVE:\DIR\LISTFILE Listfile is simply an ascii file containing filenames for upload and the L)istfile option creates this. All entries into a "LISTFILE" should contain filenames in DRIVE:\DIR\FILENAME.EXT format. L)istfile will update "LISTFILE" in FULL PATH format. All Batch protocols supported, with exception to BiModem use the "LISTFILE". "LISTFILE" names may be changed at any time with the LISTFILE option available from ProMenu's C)onfigure menu. You may have differantly named "LISTFILE" names for differant calls. Default "LISTFILE" name is PROMENU.BCH. Your "LISTFILE" names will be appended a "BCH" extension if none is given. Say you have three "LISTFILE" names as ( 1, 2, keyboard ). ProMenu will have named them ( 1.BCH, 2.BCH KEYBOARD.BCH ). You needn't type the extension "BCH" to switch between the "LISTFILE" names. As "BCH" is assumed. However, if the "LISTFILE" name KEYBOARD.LST, will will need to be specified as NAME.EXT Bimodem uses it's own PTH file. ( BIMODEM.PTH by default ) M)anual entries are added to "LISTFILE". Jmodem does not use the "LISTFILE". If you have used the SET promcfg=PATH option, then "LISTFILE" will be attatched to that PATH. The "environmental" PATH is probably the more "sure-footed" means of using any program which accesses DOS environment variables. PAGE 8 %RD Switch * Recv Dir %RD found as switch symbal will be replaced with your Recv Dir as found in PROMENU.CFG. See Cus DSZ R-String for example usage. *NOTE that this example is set up for registered versions of DSZ. You will probably want O)verlay mode "on" and Dir Hopping "off" when using this switch on command line to protocol. Please note the Puma/Lynx bug explained under O)verlay mode. %SD Switch * Send Dir %SD will be replaced with Send Dir Send and Recv Dirs may be same or seperate. Send dir will be listed "Listfile" display by default. Switch symbal (macro) ideas for ProMenu may be netmailed to me at 1:114/35 or left in a message on the Comm echo. I monitor this as thorouly as my hub gets the mail to me. PAGE 9 ------- EXAMPLE ------- Example use of the switches are contained as defaults, when PROCFG.EXE builds a NEW PROMENU.CFG file. All Protocol defaults contain working examples. *NOTE "command line to protocol" does NOT contain "PROTOCOL NAME" EXAMPLE "command line to protocol" for DSZ **Assuming a 2400 baud modem and conection for port 2 I get ALL of the following to do the same thing. A DSZ zmodem download on port 2 at 2400 baud ( %B = BAUD %P = PORT ) %B [baud] arg CFG file default baud Protocol command line to protocol ( EXPANDED ) DSZ speed %B port %P rz ( speed 2400 port 2 rz ) %P rz ( 2 rz ) %B %P rz ( 2400 2 rz ) %P %B rz ( 2 2400 rz ) Excepted method: port %P speed %B rz ( port 2 speed 2400 rz ) How many protocols do you know that allow such a rearrangment of their arguments and not fuss. Command lines to protocols may expand up to 127 characters... ( DOS LIMIT ) NOTE that "DSZ" is not part of the command line... If you mess things up, PROCFG.EXE will fill in all defaults each time a new CFG file is built. Command lines to protocols are built up at transfer time, display in the C)onfigure menu, is in "Switch Symbol" form. Arguments to ProMenu such as, 'promenu 2400 z u` will use the current "SET" "command line to protocol", as set with the Toggle option from ProMenu's C)onfigure menu. ARGUMENT: PROMENU 2400 Z U Callable from a script, Immediate DSZ upload at 2400 baud, using current set "command line to protocol". NOTE [baud] overrides CFG file's default baud. PAGE 10 ------------------------------------ Default command line to protocol set 07/01/90 ------------------------------------ DSZ Def Up "port %P sz -m %LF" Cus Up "port %P sz -m %SD\PROM0701.ZIP" %SD (Send Dir) -Note the "\" Def Dn "port %P rz -mr" Cus Dn "%P rz -m %RD" You may have Dir Hopping "off" when using the %RD switch symbal with registered DSZ versions. PUMA Def Up "S %LF" Cus Up "B+ E%B N- P%P S %LF" Def Dn "R %RD\" Cus Dn "B+ E%B N- P%P R+ R %RD\" LYNX Def Up "S /%P /NC %LF" Cus Up "S /%P %LF" Def Dn "R /%P /NC /R %RD\" Cus Dn "R /%P %RD\" SUPERK Def Up "p%P s%B ssb f %LF" Cus Up "p%P s%B ss f %PF" Def Dn "p%P s%B rsb" Cus Dn "p%P s%B rs f %PF" JMODEM Def Up "S%P %PF" Cus Up "S%P %SD\PROM0701.ZIP" Def Dn "R%P %PF" Cus Dn "R%P %RD\KEYFILES.ZIP" BIMODEM Def "/B%B" Cus "/B%B /MYBIM.LOG" NOTE protocol NAME is not contained in "command line to protocol" ProMenu calls protocol NAMES with "command line to protocol" as argument. Protocol NAMES are hardcoded into ProMenu. I do plan to add ability for adding external protocols with the next major update to ProMenu. PAGE 11 CHAPTER FOUR ============================================== ProMenu Arguments ============================================== ProMenu [baud] [p] [u/d] [baud] always preceeds a [p] arg, [p] always preceeds [u/d] args [b] -overrides default baud from PROMENU.CFG [p] -overrides default protocol from PROMENU.CFG [u] -Automatic Upload [d] -Automatic 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 download without further user input, using current set "command line to protocol". [u] option requires that LISTFILE be preloaded with one or more filenames In Jmodem's Case You will use the %PF swich, or have a "preloaded" filename in "command line to protocol" --------------- Calling ProMenu --------------- From BOYAN v4.0x+ Boyan's Macro set ( EXPANDED ) ( switch symbals ) /dc[promenu %MS ( promenu [baud] ) Call ProMenu with a BAUD arg /dc[promenu %MS z u ( promenu [baud] z u ) Call ProMenu with BAUD arg, protocol arg, transfer arg PAGE 12 CHAPTER FIVE =========================================== PROTOCOL TRANSFERS =========================================== --------- Uploading --------- BATCH PROTOCOLS: Filenames entered for upload format, all are placed into a "LISTFILE" and handed to the protocol at runtime. Put Pick option will list whatever directory is found as the Send Dir in PROMENU.CFG. M)anual entries also are added to the "LISTFILE". Remember if not in local directory to include a FULL PATH when using M)anual option. Batch protocols will also operate as single file. SINGLE FILE PROTOCOLS: ( Jmodem ) Single file protocols are at this time not using a LISTFILE therefore cannot be "preloaded", as with batch capable protocols. With exception that editing "command line to protocol" Such as: R%P %SD\KEYFILES.ZIP Will serve to "pre-load" Jmodem. NOTE: Include FULL PATH\NAME when filenames NOT in local directory. The %PF switch found as command to protocol will prompt for filename, and insert filename, as found on command line to protocol. ----------- DOWNLOADING ----------- All Batch protocols get download filenames from other end. SuperK as sb (single(Cus Set)) and Jmodem will require a filename at your end. PAGE 13 CHAPTER SIX ============================================== Comm Prog Installation ============================================== ------------- Telix Install ------------- Select the external protocols menu. External Key Protocol Upload Download Bat or DL Protocols Name Filename Filename Script Name A............ P ProMenu prom.bat prom.bat Batch N B............ C............ The 'Key' option is the letter that will invoke ProMenu from TELIX's protocol menu. May be set up as default. ==>> EXAMPLE: PROM.BAT promenu %1 ^^ traps the baud arg passed by Telix ------------- Boyan install ------------- ProMenu is 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 Boyan's default "memory for DOS shell" will have to be changed from 180k to 200k PAGE 14 CHAPTER SEVEN =========================================== ProMenu / BiModem =========================================== NOTE ProMenu's BiModem Menu will be refered to as BiMenu from here on in. ProMenu is a take off from the BiMenu package to begin with. BiMenu started out as a Shell for the BiModem protocol in January of 1989. --------------- BiModem Package --------------- NEEDED FILES: BIMODEM.COM,BIPATH.COM,BICONFIG.COM Storing above files along your DOS PATH or better yet in the Prot Dir specified in PROMENU.CFG is a cleaner way of doing things. BiMenu will find them as fast any way. ProMenu will come up for all but BiMenu menu, with only a PROMENU.CFG file present. BiMenu will require a BIMODEM.CFG file be present for proper operation. As will BIMODEM.COM If BiMenu can't locate a BIMODEM.CFG file, it 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. ProMenu/BiMenu and BiModem.COM will use a full path to BIMODEM.CFG. BiMenu does a quick read of the BIMODEM.CFG file gathering default RECV/SEND Dir, PORT Num, LogFile, and "PTH" file. BiMenu then checks the "PTH" file and calculates number of entries. BiMenu will use what ever "PTH" file is current in BIMODEM.CFG. You may have several "PTH" files, B)iconfig to change. In BICONFIG.COM, remember to W)rite your changes before exiting. Before BiMenu reads/writes to "PTH" file, they first check BIMODEM.CFG, for "PTH" file, allowing changes on the fly without restarting BiMenu. S)tart option will send a "B" wait 1/10th second, send a <CR> over Port as found in CFG file, wait a second and invoke BIMODEM.COM at your end. ( I support to COM4 for "send B CR" as of 05/05/90 ) Most BBS's will use a B) option for bimodem, this allows starting each end from BiMenu. Current method of sending a 'B CR` , are placed directly into the UART chip. PAGE 15 ---------- "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. Registered versions allow "PTH" file updates during an actual transfer session. The "PTH" file also excepts file descriptions for uploads, and descriptions will be automaticly tranfered along with the upload. It is up to the other end to properly deal with filenames and descriptions contained in the "intercommunications" log file. 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. The "Destination" filename is intended for renaming at the other end. This option will likely be disabled via a flag in the other end's CFG file. 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, using your <Pg Up> and <Pg Dn> keys will move the filenames from window to window, in the PTH file. Default "PTH" filename is BIMODEM.PTH. You may change the name at any session time. ------------------ E)dit / BIPATH.COM ------------------ The function invokes BIPATH.COM, and will allow editing of the "PTH" file entries. <CTRL-D> will delete an entry posted in the lower window. One entry is posted in the lower window at a time. <Pg Up> initialy clears the upper window, but entries are not deleted, but are on deck ready to be popped in using the <Pg Dn> key. Spending a few minutes popping and pushing filenames along with upload-descriptions, will prove time-saving, for later online. The Edit option uses the current PTH filename as in CFG file. NOTE! BiMenu calls BiPath as" BIPATH "PTH"NAME Starting BiPath from DOS may cause your PTH file be erased. See Bimodem Doc. D)ELETE option from BiMenu part of ProMenu immediatly deletes current "PTH" file. PAGE 16 -------------- S)tart BiModem -------------- The function is designed especially for BBS's that use a B) option to invoke BIMODEM. S)tart function will send a "B" over Comm Port wait 1/10th second, send a "CR" over Comm Port, pause 1 second and spawn BIMODEM.COM with it's current "command line to protocol". In most cases this will start BIMODEM on each end. Rather than first returning to Terminal mode and making the selection directly. I can never be sure that line noise won't intercept a character. Also My sending a "B" "CR" is supported thru Com4 as of 05/05/90. The sending of a "B" "CR" over Comm Port, will not affect having already started BiModem at the other end. --------- B)iConfig --------- Invokes BICONFIG.COM, for CFG file creation/editing. Until you become familiar with BiModem, it is best only specify your upload and download directories, and COMM port to be used. Don't change any COMM port addresses unless you know EXACTLY what you are 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. PAGE 17 Distribution ================================================ Licese to Use and Distribute ================================================ ProMenu is distributed as SHAREWARE Right to use and distribute this program is subject to the following: PROMxxxx.ZIP Zipped containing: PROMENU.DOC PROM.EXE PROCFG.EXE Please do not add to or take from the above files package. This includes Commpresion comments. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ProMenu is result of many hours work. Providing a fast and efficient protocol menu manager, with minimum overhead. Use of ProMenu beyond an evaluation period, requires your support. The "ShareWare" concept allows your use,and evaluation of a software program, for a period of time, while deciding whether it suits your needs. If you find ProMenu to be a useful utility please consider the author. I have been pretty good about responding to suggestions and specific requested changes. Your support lets me know whether the ProMenu project merits continuance. Creating my own personal version is simple. Creating a version suitable for the wide variety of users who use ProMenu, takes a great deal of time, and effort. Phoenix BBS Key_Board Sys (602)846-2940 1:114/35 SysOp Michael G Phelps To Support ProMenu Two meathods, take your pick... Send me a letter or postcard expressing your comments/evaluation of my software. or Remit $10.00 to: While currently living in Phoenix, my Mailing address is: Michael G Phelps Box 10 Route 3 Cannon Falls Minnesota 55009 ========================= ProMenu User Registration ========================= Name: =====>> ____________________ ______________________ first last Address:===>> _________________________________________________ street _________________________________________________ city state zip ProMenu Version you have ___/___/___ ==>> ______ Number of copies you intend to register at this time. Amount enclosed:==>> $______.____