Digital Dynamics Technical Bulletin #1001 (02/20/96) Answers to Frequently Asked Questions about Synchronet BBS Software Version 2.x =============================================================================== Missing PKZIP/PKUNZIP --------------------- Q. When I try to upload files to my BBS, SBBS reports the file has ZIP errors even though I know the file is fine. Q. When I attempt to create a QWK packet or upload a REP packet on my BBS, I get an "error - executing" message. A. You need to copy PKZIP.EXE, PKUNZIP.EXE, and any other compression utilities you want to support on your BBS into your Synchronet EXEC directory (e.g. C:\SBBS\EXEC). It is not enough that the files are in your search path, they must exist in your Synchronet EXEC directory. Missing/Incorrect Logon Module ------------------------------ Q. I've upgraded to v2.2 from v2.1 or earlier, and when anyone logs on, the logon events don't run and the normal logon displays (last few callers, etc) don't show up (goes straight to the main menu). A. Version 2.2 comes with a stock logon module (EXEC\LOGON.BIN) which emulates the v2.1 and earlier logon procedure. Make sure you have SCFG->System-> Loadable Modules->Logon set to "LOGON" and you have the LOGON.BIN the came with SBBS v2.2 in your EXEC directory. Attempting to use DSZ with FOSSIL Command Line ---------------------------------------------- Q. When someone tries to upload or download from by BBS, DSZ reports "invalid port" and immediately aborts. A. You have Synchronet set to use FOSSIL for it's communications. This is not the recommended configuration (even though you have a FOSSIL loaded), Synchronet should be set to use the UART for it's communications (in SCFG-> Nodes->Node #->Modem Configuration). If you do not have a UART on your serial ports (e.g. DigiBoard), you will need to use a file transfer program other than DSZ. There is a FOSSIL version of DSZ (FDSZ), but it is not a good performer compared to other file transfer programs written specifically for FOSSILs (CEXYZ, SDPD, etc). Not Enough Memory for Message Buffer ------------------------------------ Q. When some/all of my users attempt to post a message or send e-mail, I receive an "error - allocating memory" and the message is aborted. A. You have set the "Maximum Lines Per Message" for that user's security level (in SCFG->System->Security Level Values) to a number higher than your system configuration can allocate. With Synchronet for DOS (16-bit), the maximum lines per message for all security levels should not exceed 1000 lines for most system configurations. Synchornet v2.1 and earlier had an absolute maximum lines per message of 500. This limit was removed in v2.2 (the absolute maximum is now however much memory is available). Even though you can enter "9999" for the maximum lines per message for a specific user, the 16-bit DOS version will never have enough available memory for that many lines of text. 500-1500 lines is more realistic range for the 16-bit DOS version of Synchronet. Unknown Result Codes -------------------- Q. When some/all of my users call my BBS, it answers but hangs-up immediately and returns to waiting for call. When I check my error log (DATA\ERROR.LOG), I see an entry for an "Unknown modem result code 'xx'" (where xx is a number). A. Your modem is returning a connection result code that is not listed in your modem configuration information. You may have selected the wrong modem for auto-configuration or you have a different version of a modem listed in the auto-configuration list (assuming you used the SCFG modem auto-config). The solution is to go into SCFG->Nodes->Node #->Modem Configuration->Result Codes and add (hit the Insert key) an entry for the unknown result code. For the details of the result code (connect speed and description), see your modem's manual. A rough estimate for the CPS would be the connect speed divided by 10 (e.g. 1440 for a 14400 connection). The CPS is used for estimating download times, so it is not super critical that it be totally accurate. In reality, error-correcting connections get higher CPS rates at roughly the connect speed divided by 9 (e.g. 1600 CPS for a 14400 BPS connection). Synchronet v2.3 (not released as of this writing) now defaults to the last configured result code when answering a call with an unknown result code and the user is still connected and given the login prompt. This behavior can be turned off by setting SCFG->Nodes->Node #->Modem Config-> Toggles->Allow Unknown Result Codes to "No". An error message is still logged for the sysop (to inform you that you need look-up the result code in your modem manual and add it to your configuration in SCFG). If your modem manual does not list the result code in question, call your modem manufacturer and request an updated manual with all the current result codes. At the very least, have them fax you a complete list of current result codes. Digital Dynamics wishes to keep our modem auto-configuration database as current as possible. If your modem is not listed or you suspect the auto-configuration information (including result codes) is not current, please fax or mail us a copy of your modem manual and we will update our database for the next release of Synchronet. All Users Meet Sysop Chat Requirements -------------------------------------- Q. All/some of my users can page me even though I have scroll-lock off. A. You have set SCFG->System->Advanced Options->Sysop Chat Requirements to an ARS that allows all/some of your users to page you at any time. Set this option to BLANK if you do not want anyone to be able to page you when scroll-lock is off. Set this option to "LEVEL 90" if you want only user with level 90 and higher to be able to page you when scroll-lock is off. Any/all users can page the local sysop when scroll-lock is on. Users with the 'C' restriction cannot page the sysop or other users at any time. ASCII/ANSI/RIP Message Upload ----------------------------- Q. How do I or my users upload prepared ASCII/ANSI/RIP files as messages? A. From the main menu, hit Ctrl-Z to enable RAW input mode. Hit 'P' to post a message, or 'E' to send e-mail (or whatever command is appropriate for your command shell). When the RAW message input mode appears (where normally you would see a message editor), begin an ASCII upload of your ASCII/ANSI/RIP file. If using a terminal program, hit PgUp or whatever the appropriate upload key-sequence is and select "ASCII" for the transfer protocol. If logged on via the local console, hit PgUp then enter the path and filename. When the ASCII upload is complete, it will either automatically terminate and save the message or you will need to hit Ctrl-Z (once) to end the message. Disable New User Feedback ------------------------- Q. How do I remove the requirement of new users to send me e-mail? A. Set SCFG->Nodes->Node #->Advanced Options->Validation User to "0". If you want your new user validation feedback (e-mail) to go to another user, enter that user's number here. Since you can have a different validation user for each node, you will need to set the validation user to 0 for all of your nodes if you want to totally disable the new user feedback. Exclusive Events Don't Run -------------------------- Q. When some/all of my timed events come up, SBBS tells me it's waiting for all nodes to become inactive before running the event. A. You have some/all of your timed events setup to execute exclusively. This is the default mode for the MSGMAINT event setup in the default Synchronet configuration (packing the message bases requires all other nodes be inactive). Exclusive events will not execute until all other nodes are either OFFLINE or in exclusive event mode. If the other nodes are running and waiting for call (not in a front-end mailer or turned off), they will automatically go into exclusive event mode (take the phone off hook and go inactive) until all pending exclusive events have been executed. If your exclusive event is not executing, one or more of your nodes are not in OFFLINE or exclusive event mode. If you're using a 24hour front-end mailer on one or more of your nodes (the most common cause of this problem), you will need to have your mailer automatically exit at the event time and run "SBBS O" (the 'O' switch is new to SBBS v2.2). This will cause that node to run all pending timed events and network call-outs and/or go into exclusive event mode until all pending exclusive events have been run. It will then automatically exit back to the front-end mailer. If using SBBS v2.1 or ealier, you will need to have your timed event or network call-out "down" your front-end mailer nodes to force them to return to the front-end mailer. This is done by executing "NODE DOWN ON #" (where # is the node number you want to down). See the Synchronet sysop manual for more information on the NODE utility. If you're still unsure as to why your exclusive event is not automatically running unattended, use the NODE utility to display the status of all your nodes (type "NODE LIST" at the DOS prompt in the Synchronet EXEC directory). Any nodes that are listed as in use or waiting for call and aren't actually running are nodes that were either turned off or rebooted while in use or waiting for call. These nodes need to be reset to offline. You can do this by downing all of your nodes and then typing "NODE STATUS=5" at the DOS prompt (setting all nodes to OFFLINE) or running the node(s) in question and downing them properly. Some programs, designed to run as events, MUST run exclusively or data corruption may occur. SMBUTIL, for example, when run with the (P)ack command (as per the default configuration) must be run exclusively. No user or process may access a message base while it is being packed or corruption will occur. SMBUTIL may be run non-exclusively only if you remove 'P' from the SMBUTIL command line (in SCFG->External Programs->Timed Events-> MSGMAINT) and set all of your message bases to use "Self-packing" storage method. "Hyper-allocation" (the default) message base storage method is the preferred storage method. Another Synchronet program, SMMUTIL (Synchronet Match Maker Utility) must be run exclusively. No user or process may access the SMM database while it is being maintained by SMMUTIL or corruption will occur. Many door program (e.g. TradeWars) events must also be run exclusively. Consult all event program documentation before attempting to run non-exclusively. Run all event programs exlusively unless absolutely sure it is okay for other users or processes to access the files while they are being maintained/updated. Invalid Start-Up Directory -------------------------- Q. When some of my timed events try to run, I get an error in my error log (DATA\ERROR.LOG) reporting an error - changing directory. The directory exists. Why can't it change into it? A. Make sure you are specifying the full path to the Start-Up directory in SCFG (and not using any Synchronet command line % specifiers) and you DO NOT have a trailing backslash on the directory (i.e. C:\SBBS\XTRN\MYDOOR\ is incorrect - remove the trailing backslash). Logon Bulletins --------------- Q. How do I have a set of prepared text files that all/some users are prompted to read during logon? A. The SBBS logon display files (TEXT\MENU\LOGON*.ASC) usually meet this requirement. See the customization chapter in the Synchronet sysop manual for details. If you want to use an actual "Logon Bulletins" program to intelligently display only new/updated bulletins, allow new-scans of bulletins, force reading of specific bulletins, etc. use a bulletins program as a logon event (e.g. download DBULLET.ZIP from our BBS and configure as shown in its documentation). Stray Swap Files ---------------- Q. Hidden files with strange names are collecting in one or more of my node directories. A. These are most likely lost swap files (created by SBBS or an external program that supports swapping to disk). They are normally automatically deleted, but if your BBS is rebooted or turned off while a program is swapped out to disk, the file will remain. If the node in question is down, you can safely delete the file(s). Blinking Heart -------------- Q. What does the blinking heart in the upper right of my waiting for call screen indicate? A. It is a multitasker performance indicator. The faster the heart beats, the better the performance for the node in question's session. A slower heart beat indicates other processes and/or nodes are eating up system resources/time slices. ADDFILES -------- Q. How can I have files automatically added to my file database? A. ADDFILES (included with Synchronet) can be used for this purpose. If you do not have a description for the file to be added to the database and you do not know the name(s) of the file(s), you can use the '/s' switch to search for any files in the storage directory and add them to the database. You will probably also want to use the '/n' switch to keep it from updating the database entries of files that are already in the database. Example command line: ADDFILES dircode /sn Where "dircode" is the internal code of the directory. Use '*' in place of dircode if you wish ADDFILES to search all directories that have "Auto-ADD" toggled ON in SCFG. If you're importing File Distribution Networks or CD-ROMs with FILES.BBS, you'll probably use the following command line instead: ADDFILES * /diz See the ADDFILES chapter in the sysop manual for more details. General Purpose Online Database ------------------------------- Q. How can I create a online database? A. Synchronet has quite a few internal databases for user data, file directories, messages, external programs, etc. To create your own general purpose database, you will need to utilize a third party BBS database application such as: Modem Base Pro Online DBMS from Integrated Solutions at 909-695-6677 (voice) DC Genesys from Durand Communications Network at 805-961-8700 (voice) QRDB from Mountain Retreat Software at 408-335-4672 (voice) Main-stream Applications Running Online --------------------------------------- Q. How can I run main-stream applications as doors/external programs on my BBS? A. If the application is a text-mode application, it can be run as a door using a utility called DoorWay available for download from Vertrauen as DRWY*.ZIP. Graphics programs (including Windows applications) cannot be run as doors unless they were specifically designed to run on a BBS. Internet Connectivity --------------------- Q. How can I connect my BBS to the Internet? A. Contact Merlin Systems regarding their Internet solutions for Synchronet: Web: http://www.merlinsys.com E-mail: info@merlinsys.com BBS: (613) 741-7583 Phone: (613) 749-0888 Fax: (613) 741-7583 The main dealer for NetXpress in the United States is Craftech: Web: http://www.craftech.com E-mail: sales@craftech.com Phone: (800) 743-9923 Fax: (610) 566-6340 BBS: (610) 566-9435 OS/2 DOS Console Incompatibility -------------------------------- Q. When I run external programs (that require I/O interrupts to be intercepted) under OS/2 (like PKZIP, Synchronet Blackjack, Domain Bulletins, etc) the output does not display remotely and ANSI escape sequences display as garbage. A. The OS/2 DOS console driver has a DOS incompatibility that effects SBBS's ability to intercept DOS console output. To remedy this incompatibilty, Digital Dynamics developed a replacement console driver for VDMs (Virtual DOS Machines) under OS/2. See DOCS\SVDMANSI.DOC for details. SBBS.EXE Read/Write ------------------- Q. When I attempt to run more than one SBBS node, I get a "Sharing Violation Reading Drive C" message. A. Somehow, the READ ONLY attribute was removed from SBBS.EXE (in your EXEC directory). To replace it, type "ATTRIB +R C:\SBBS\EXEC\SBBS.EXE" from the DOS prompt. SCFG.EXE requires the READ ONLY attribute to be run from multiple sessions as well. Both of these files have the READ ONLY attribute by default, when installed. Date/Time Set to Future ----------------------- Q. My BBS statistics and user logon list aren't being reset at midnight. My system date may have been set to the future. Q. I'm getting an error - file: LOGON.C action: Checking object: Daily stats time stamp A. Down all your BBS nodes, fix your system date/time (with the DOS DATE and TIME commands), then run EXEC\DSTSEDIT in your Synchronet CTRL directory. Change the "Date Stamp" to yesterday's date. Re-run all your nodes. Mail Corruption --------------- Q. My E-mail database appears corrupted (errors, mail going to the wrong users, garbage in messages, etc), how can I fix it? What's causing it? A. If you suspect any e-mail corruption, the first thing you should do is run CHKSMB (included in your Synchronet EXEC directory) on your e-mail database (e.g. CHKSMB C:\SBBS\DATA\MAIL). If CHKSMB reports your e-mail database as OK, then it is most likely OK and does not require any repair. If CHKSMB does report any errors with your message base (errors are totaled in the end report with an (!) next to each error total), note the errors and if possible save a complete screen capture of the final end report for possible review by Digital Dynamics tech support staff. Always run CHKSMB and any repair utilities with ALL NODES OFFLINE. E-mail corruption is not normal. If your BBS locks up or is rebooted while a user is saving or deleting e-mail, you may end up with a small amount of recoverable e-mail corruption, but nothing severe. If you are getting e-mail corruption on a regular basis, the first thing you need to do is isolate the program that is causing the corruption. If you are using any third party programs to import/export e-mail or netmail from your e-mail database, try temporarily removing these programs to see if they are the cause (or better still, run CHKSMB before and after import/exporting using each of your third party program to verify if it is or is not corrupting the mail database). SMBUTIL run with the PACK command (e.g. SMBUTIL /A P C:\SBBS\DATA\MAIL) will fix most mail database corruption. You can verify this by running CHKSMB again after SMBUTIL to see if any errors remain. If errors remain after packing the message base with SMBUTIL, then run FIXSMB /M on your e-mail database (e.g. FIXSMB /M C:\SBBS\DATA\MAIL). FIXSMB is a last resort utility. It entirely rebuilds the message base index, thus renumbering and possibly reordering your e-mail database. Only use FIXSMB if packing with SMBUTIL fails to repair all corruption. FIXSMB only repairs index errors. Most types of corruption can only be fixed by SMBUTIL (pack). If upgrading from v2.1 or earlier of SBBS, you may need to manually add the E-MAIL attribute to your e-mail database (for compatibility with the SMBUTIL E command and possibly some third party programs). When viewing the status of your e-mail database (e.g. SMBUTIL S C:\SBBS\DATA\MAIL), the ATTR field should read 0001h. If it does not, then you need to change the status (e.g. SMBUTIL C C:\SBBS\DATA\MAIL), hitting ENTER for all fields and entering a 1 for the attr field when prompted. You will only have to do this once for the life of your BBS. This "1" simply tells external programs (outside of SBBS.EXE) that this is an e-mail database (as oppposed to a sub-board) and requires special treatment. If CHKSMB continues to report errors with "Unsupported Translation (xlat) Types", even after packing with SMBUTIL (v2.0 or later), either ignore the CHKSMB errors (unsupported xlats do not cause errors in the BBS), or locate the corrupted messages (CHKSMB /E displays extended information on corrupted messages supplying you with the static message number) by reading all mail on the BBS and delete them by hand. SMBUTIL v2.0 and later will delete messages with unsupported xlat types in dfield[0] automatically. If SBBS, CHKSMB, SMBUTIL, and FIXSMB can't even open the message base, it has probably been corrupted beyond repair and must be deleted. If you wish to save a copy of your corrupted message base for review by Digital Dynamics, you may do so. Such drastic measures (deleting a corrupted message base) are not normally necessary except in cases of extreme file system or external program data corruption. The most common causes of e-mail corruption are: Under-tested third party programs, file system corruption, and running SMBUTIL while nodes are in use or other programs are import/exporting mail. NetXpress (third party Internet e-mail gateway) for Synchronet has been reported to cause e-mail database corruption. We expect the developers will fix this ASAP, but have not heard any reports of such a fix to date (Feb, 19th 1996). File system corruption can be detected by running SCANDISK (or CHKDSK for older versions of DOS). If SCANDISK finds errors on your hard disk, this is a very likely cause of your e-mail corruption. Again, under-tested third party programs (often doors) can cause file system corruption, which can in turn corrupt any data (in any directory) on your hard disk. With file system corruption, the most commonly accessed files get corrupted first and foremost (regardless of where the program that caused the initial corruption is located). It can be hard to locate the program (if indeed it is an individual program) that is causing the file system corruption. It is a good idea to run SCANDISK periodically and keep records to try and pin- point what is causing the corruption (if it is reoccuring). A locked or rebooted program (including SBBS) can easily cause file system corruption. When packing message bases (with SMBUTIL), all nodes should be offline or in "event waiting" mode. No other processes should be writing to the e-mail database while it is being packed. Normally, the e-mail database needs no packing (so this is a somewhat moot point). Programming Command Shells/Modules ---------------------------------- Q. I would like to add/remove/change some of the keys on my BBS menus. How do I accomplish this? A. The simplest way is to look through the available command shells (Synchronet comes with several, and there are many, many more available for download on the Synchronet support BBS) and pick one that most closely meets your preferences. You can make this command shell the default shell for all new users on your BBS or the ONLY shell on your BBS if you prefer. If you wish to create your own command shell, your best bet is to modify one of the command shells that comes with Synchronet (*.SRC files included in your EXEC directory) or one of the third party shells (if supplied with source code). For details, see DOCS\BAJA.DOC. Node Upgrades ------------- Q. How much does it cost to upgrade from an X node license to a Y node license? A. Our node upgrade policy is simple: the price difference plus 10%. If you paid $199 for your 4-node license and the current price for an 8-node license is $299, then the upgrade price is $110 (plus shipping and handling if applicable). If you just want to download your upgraded key file from the support BBS, you can save the shipping and handling fees. All orders can be placed online (on the support BBS) using a Visa or Mastercard. Upgrade keys are available for download within 48 hours of your approved order. 32-bit Synchronet ----------------- Q. When will Synchronet for OS/2 be released? How much will it cost? Will there be a Synchronet for Win95/WinNT? If so, when? A. Synchronet for OS/2 (native 32-bit multi-threaded console-mode program under OS/2 v2.x and higher) is currently in alpha testing and will be released as soon as possible. All major developement has been completed and we expect to be in wide-beta (we are not currently accepting beta applications) soon with a firm release date to follow shortly. SBBS4OS2 has been in the hands of our alpha testers for over two weeks and problem reports are twindling. Vertrauen (the Synchronet support BBS), as always, is participating in this alpha test as well (with two of our eight nodes) with reports of excellent performance and reliability. Synchronet for OS/2 will retail for $50 more than Synchronet for DOS. It will be a $25 upgrade from Synchronet for DOS v2.2 and a $50 upgrade from Synchronet for DOS v2.1 or earlier (regardless of the node license). SBBS4OS2 is a drop in replacment (no major conversions or upgrade hassles) and supports mixed operating system environments (different nodes running different flavors of SBBS) as well as DOS and OS/2-native external programs. The OS/2 version of Synchronet looks and feels very much like its DOS older brother. Most of our callers never even notice they're using SBBS4OS2. We do not at this time plan on developing OS/2 versions of Synchronet Match Maker or Callback Verifier (the DOS versions run quite nicely under SBBS4OS2). We do, however, have OS/2 versions of SBBSecho and most of the Synchronet utilities that are included free (SMBUTIL, ADDFILES, FILELIST, DELFILES, NODE, etc). Synchronet for Win32 (native 32-bit under both Windows 95 and Windows NT) is expected to be released in 90 days. We estimate the retail price to be inline with Synchronet for OS/2. A firm retail and upgrade price has not yet been established. Digital Dynamics will notify the public of the final prices when the product is closer to release. Synchronet Version 2.2 Upgrade ------------------------------ Q. How much to upgrade to the current version? Does it come with a manual? Can I get upgrades automatically? Synchronet for DOS Version 2.2 Upgrade ====================================== 1) Purchaser Name ____________________________________ Phone _______________ Company Name ____________________________________ Phone _______________ Street Address ___________________________________________________________ City __________________________ State ____________ Zip _______________ Synchronet Registation Number _____________________ BBS # _______________ 2) Payment Method ( ) Visa ( ) MasterCard ( ) Check/M.O. ( ) C.O.D. Credit Card Number ____________________________ Expiration ____/____ Print Cardholder's Name __________________________________________________ Cardholder's Signature __________________________________________________ 3) Version 2.2 Upgrade (FREE if purchased after May 1st 1995) $ 25.00 Or, if upgrading from version 1 (purchased before 8/27/93) $ 50.00 Or a one year subscription to our Auto-Update plan $ 60.00 ** Or a one year subscription to our Auto-Update plan w/Manuals $ 100.00 ** ** All upgrades (including v3.x) automatically shipped Options: Printed and bound Sysop Manual (glossy cover) Add $ 25.00 $ Printed and bound Baja v2.00 Programmer's Manual Add $ 10.00 $ Callback Verifier Add $ 29.00 $ Match Maker (our best seller!) Add $ 69.00 $ SBBSecho (FidoNet EchoMail Tosser) Add $ 49.00 $ Sub-Total $ California residents add sales tax of 7.75% $ 4) Shipping (check one) ( ) Priority Mail 1-3 day (USA Only) $ 8.00 ( ) International AirMail (Canada) $ 10.00 ( ) International AirMail (Elsewhere) $ 20.00 ( ) Download (No printed manual) $ 0.00 ( ) Auto-Update Plan $ 0.00 All payments MUST be made in U.S. funds! Total $ 5) Make check or money order payable to DIGITAL DYNAMICS. 6) Send to: Digital Dynamics PO Box 501 Yorba Linda, CA 92686 (714) 529-9721 FAX