home *** CD-ROM | disk | FTP | other *** search
-
- Frequently asked Questions on successfully running BFE
- (Compiled by user submissions to the author and beta testers of BFE)
-
- Last updated: 30 October 1993
-
- Q) I am trying to call another door from one of my BFE menus, but it just
- simply isn't working! What can I do?
-
- A) For starters, replace the name of the door with the supplied CMDLINE.EXE
- program that came packed in the distribution archive. This program will
- simply echo the command line parameters to your console. The improper
- passing of command line parameters to a door is perhaps the number one
- cause of heart ailment in sysops today.
-
- Secondly, check the configuration of your menu item in BFE/Setup. Do you
- have PASSPARMS set to the proper value? If your door needs a dropfile,
- is BFE configured to create one for you?
-
- If all else fails, post a message in either DOORWARE, SPHINX, etc, and
- see if other sysops have it running successfully.
-
- Q) I am trying to run my BBS as an external process. Why won't it work?!
-
- A) This be quite a few things, the first being lack of conventional memory
- for the BBS to operate! Be sure that you have enabled the swapping
- features of BFE, to allow it to swap itself out when running external
- processes!
-
- Q) I am trying to display an ANSI animation, and I keep getting this
- annoying "continue?" prompt every few lines that go by! This is getting
- old, friend!
-
- A) By default, BFE uses an internal page pausing system. You can disable
- this feature, and show your animated ANSI screen, by using the following
- simple script example:
-
- main()
- {
- ToggleMore(); /* Disable the page pausing system */
- Displayfile("Cartoon"); /* Show the screen! */
- ToggleMore(); /* Re-enable the page pauser... */
- }
-
- Q) How can I display more than one "welcome" screen when a user goes into
- BFE?
-
- A) This can also be done very easily in BFE/Script. First, you must enable
- the BFE "startup" script option (see the docs). Then, create and call
- a script which looks something like:
-
- main()
- {
- DisplayFile("Welcome1"); /* Main welcome screen */
- DisplayFile("Welcome2"); /* Second welcome screen */
- }
-
- Q) BFE simply refuses to operate for me! What the heck is wrong here?
-
- A) Read! That is the key to using BFE, plain and simple. Chances are, you
- have a stray dropfile somewhere, or simply have BFE set up wrong. If all
- else fails, post a message in the SPHINX echo, or drop us a netmail
- message (we do read our mail!) :-)
-
- Q) When I try to use a custom user menu, it absolutely refuses to be
- displayed properly! It scrolls down the screen with a number of extra
- lines, etc.
-
- A) Chances are, you will need to manually modify any custom user menus that
- you create, as most ANSI paint programs will tack on "extra" lines and
- ANSI escape sequences at the end of the file. Basically, simply truncate
- the file at the end of your "select" prompt.
-
- Q) For some reason, every time a user selects a password-protected option,
- it keeps saying "access denied", but the user hasn't even entered a
- password yet? What kind of product is this anyway?!?!?!
-
- A) Relax! Check your password attempts setting in BFE/Setup under the
- Global Options menu. More than likely, you have it set to 0. :-)
-
- Q) Why doesn't the BFE Message System allow me to browse, delete, etc.
-
- A) Simple! The BFE Message System was never meant to provide a hook for
- online message reading. The purpose of the message system is to provide
- a method of entering feedback messages, netmail robot messages, etc. If
- you want to read and delete them, you should do this through your BBS
- softare, not BFE.
-
- Q) When BFE is running with the internal RIP menus, I can't see anything on
- the local screen, but the user can see everything just fine on his end!
-
- A) Unfortunately, without writing an internal RIP emulator, there is nothing
- we can do about this problem. You will find this to be a problem in a
- number of RIP compatible doors.
-
- Q) Again with the internal RIP menus, the text of some menu descriptions
- runs past the borders of the button!
-
- A) Due to the limited size of the graphics screen, we were forced to create
- two "columns" of selection buttons in RIP mode, in order to display as
- many menu options as possible on the screen. Hence, you will need to
- shorten your descriptions a bit. Of course, you could always create
- your own custom menus. The internal menus of BFE were designed to
- provide a quick way to get BFE up and running without having to spend
- any down time designing and testing custom screens.
-
-