JetMail Diagnostic Reference ---------------------------- If JetMail shuts down due to a fatal error, it may be as simple as a missing Spitfire system file, JetMail system file, or a problem in the DOS environment. If the fatal/shutdown error message refers to one of the system files, please check your configuration. If JetMail has an error otherwise, the error value should correspond to one of the items below. 0 Error 0 1 Invalid function number 2 File not found 3 Path not found 7 Memory blocks destroyed 9 Invalid memory block address 10 Invalid environment 11 Invalid format 12 Invalid access code 13 Invalid data 15 Invalid drive specified 16 Attempt to remove CurDir 17 Not same device 18 No more files 2 No such file or directory 4 Too many open files 5 Permission denied 6 Bad file number 8 Not enough core 15 No such device 19 Invalid argument 20 Arg list too long 21 Exec format error 22 Cross-device link 33 Math argument 34 Result too large 35 File already exists Should JetMail return with one of the following error messages, here are some common diagnosis: ERROR: Unable to open file! One of the basic files needed for JetMail operation is missing. This could be the JETMENU.BBS/.CLR files, if no menu is showing up in JetMail. Make sure the JETMENU.BBS file exists in the JetMail home directory. * Error opening system file SFSYSTEM.DAT. JetMail is unable to open the SFSYSTEM.DAT file. Is another node on the network editing this file? * Memory allocation error. Not enough memory to run JetMail. If running under DesqView, try to allocate more memory to the node. If that doesn't work, then it may be an idiosyncracy with your DOS not allocating memory in a manner compatible with JetMail. Refer to next error message for another remedy. * Tried to allocate bytes, with available. If is greater than , or is negative, chances are that JetMail has a memory management problem with your DOS. This was discovered in a pre-release version of JetMail, which somehow triggered this idiosyncracy. By default, JetMail will allocate a 7000-byte buffer for JetMail to import/export messages. This will cover a message over 700 lines long (even though Spitfire limits messages to 99 lines, it might be possible in the future to allow longer message and/or a Fidonet mail tosser might allow more than 99 lines of text). An undocumented function has been added in JetMail in case you need to use it, which may remedy this problem. If you want to allocate more (or less) memory for this buffer, simply enter the BUFFER=mmmmm parameter in JetMail's .CNF configuration file, where mmmmm is the size of the buffer. This is a 'tinker' parameter, so try some different buffer sizes (small, and overly large) to see if JetMail can be adjusted to work with your system. * Error building CONTROL.DAT file. Common error message when JetMail is unable to access the temporary work directory. * Error locating user in Spitfire database. JetMail needs to find the Spitfire user record number to properly access the SFMSG.LMR file, which contains the users' last message read pointers for each conference. JetMail uses these message pointers to scan for new messages. JetMail searches the SFUSERS.PTR file for the user named in DOOR.SYS. You may have a corrupt DOOR.SYS, or a non-existing user using JetMail. * User name mismatched in SFUSERS.DAT. This may indicate a corrupt DOOR.SYS or Spitfire users file. This error only occurs when using the user record number to access the SFUSERS.DAT results in a mismatched between the name in the Spitfire database and in the DOOR.SYS. Possibly solution is to regenerate the AUTOJET.SYS if you are using Auto-Pilot with a local copy of DOOR.SYS in the JetMail home directory, which has a user record number out of sync due to a newly packed user database. * Error opening system file SFUSERS.DAT. Is the user file being edited by another node? * Error creating MESSAGE.DAT file. JetMail writes all the new messages scanned into a file named MESSAGES.DAT, in the QWK format. If JetMail is unable to create this file, it may have problems with disk space in the JetMail work directory. * Error building .PNT pointers file. Unable to build the .PNT file, perhaps because of disk space. * Error reading .PNT pointers file. Uploaded pointers file was probably corrupt. * Error copying .QWK packet to local destination. JetMail was unable to copy the file to the destination, probably disk space error. * REP packet not found. JetMail detected a successful transfer (denoted by deleted XFER_ERR.JET), but isn't able to find a .REP in the JetMail temporary work directory. Be sure to receive the .REP file into the JetMail temporary work directory (or the .REP file gets copied to the JetMail work directory). * Error copying .REP packet from local directory. No .REP packet was found in the specified directory during local JetMail use. * Error transferring file JetMail returns this error whenever it find XFER_ERR.JET still remaining in the Spitfire Externals path if using XFERTYPE=SFEXT, or in the JetMail work directory when using XFERTYPE=JET. If the file transfer was successful, be sure you delete the XFER_ERR.JET so JetMail can detect the successful transfer. Consult your DOS manual if needed; make sure the DOS batch file is properly deleting XFER_ERR.JET upon successful transfers. Use the sample batch files in JETXFER.ZIP and set XFERTYPE=JET in the JetMail .CNF, if you are unable to correct the error, and be sure DSZ.COM or DSZ.EXE is in the DOS path. * QWK not found. Unable to run compression utility? JetMail shells out to compress the contents of a QWK packet, based on the PACKQWK command lines specified in the JetMail .CNF configuration, where can be 1 to 3. After returning from the shell, JetMail finds no .QWK generated. The selected compression utility is needing more memory than what is available after JetMail is loaded. You may need to run JetMail from the Spitfire Doors menu instead of as a menu extension. [The command line of the PACK1QWK is passed two parameters by JetMail, the first parameter is path and filename of the .QWK packet to generate, and the second parameter is *.* of the JetMail work directory. If your compression utility is unable to use these parameters, please contact author.] * Error opening LMR file for Conf # , or * Error reading LMR file for Conf # Spitfire automatically generates SFMSG.LMR files when new conferences are added. If a LMR file is doesn't exist for conference numbered , check your Spitfire's message path to make sure the conference message files are intact. If you just added some conferences to Spitfire, login to Spitfire first, before running JetMail, to have Spitfire generate the LMR files appropriately. * Error reading user's last msg read pointer, or * Error writing user's last msg read pointer. JetMail uses Spitfire's user record number to access the corresponding last message read pointer for the user. The SFMSG.LMR file may have been generated, but it wasn't adjusted in size for the new JetMail user. * Error building index file for .QWK packet, or * Error writing to index file. JetMail builds .NDX files for the QWK packet, which are index files used by the offline mail reader. The indices point to where the messages for each conference are; actual messages are stored in MESSAGES.DAT. May be a disk space problem. * Error building Personal msgs index file, or * Error writing to Personal msgs index file. JetMail builds a PERSONAL.NDX file for the QWK packet, which are index files used by the offline mail reader to locate messages addressed to the user. If there are no personal messages, the .QWK will not have a PERSONAL.NDX. May be a disk space problem. * Error building MESSAGES.DAT file. Disk space problem? * PNT packet not found. When using JetMail's "P" command to upload a pointers file, the transfer may have been aborted, or during local use, the .PNT file was not found in the designated directory. * Error opening replies file. When a .REP packet is received, JetMail will try to process that packet for message replies to post into the Spitfire conferences. The .MSG file may simply be corrupt, but more likely the compression utility used to make the .REP packet doesn't match the user's currently configured compression utility in JetMail. * Error opening message base JetMail tried to read Spitfire's conference message bases and encountered an error. Make sure your SFMSG.* files are intact in the Spitfire messages path. Detected Truncated Message. While JetMail is processing a .REP packet, it may encounter a message reply that is corrupt. Check the offline reader to make sure the .REP packet generated is intact. * Error opening JetMail configuration file. JetMail is unable to open the default JETMAIL.CNF in the JetMail home directory (which should be the current directory, when JetMail is first started). This error may also occur if the .CNF file specified on the JetMail command line doesn't exist. Check your batch file to make sure JetMail knows which configuration file it is trying to read. * Unable to find JetMail users file. When a new user enters JetMail, JetMail records the users name in the JetMail users database file named USERS.JET in the JetMail home directory. Before JetMail returns to Spitfire, JetMail tries to write the user's JetMail configuration to the users database. However, if it can't find the user's name in the users database, JetMail gets confused - after all, it was supposed to have written the users name to the users database when the door was first opened. * Unable to create JetMail users file, or * Error creating JetMail users file. Disk space error? JetMail creates a USERS.JET user database file to keep track of user's JetMail configuration. * Unable to find protocols list JetMail uses SFEXTDN.BBS as its transfer protocols if XFERTYPE= parameter is set to SFEXT in the JetMail .CNF configuration file, or if XFERTYPE= parameter is not specified, JetMail also defaults to using SFEXTDN.BBS, and the SFEXT.BAT files. If XFERTYPE=JET is set in the JetMail .CNF file, JetMail looks for JETXFER.LST in the JetMail home directory. * JetMail is for use with SPITFIRE 3.x only! JetMail only works with Spitfire 3.x versions. JetMail does use the DOOR.SYS which Spitfire generates. * Error making temporary JetMail work directory. When no WORKDIR= is specified in the JetMail configuration file, JetMail makes its own temporary work directory off of the JetMail home directory. However, an error was encountered trying to make this directory, usually named TMP1.$$$ or something like that. Please use the WORKDIR= parameter in the JetMail .CNF configuration file and specify a temporary work directory for proper JetMail operation. Unable to find SFFILES.BBS for File Area # When the user is configured for scanning new files in JetMail, JetMail looks for the SFFILES.BBS in the file directories and looks for new files. This error means that JetMail couldn't find a directory file SFFILES.BBS for the designated File Area. Check your path specification in SFFAREA.DAT. - Error locating SPITFIRE system file. Notify Sysop. JetMail uses a number of Spitfire system files, including SFMCONF.DAT, SFFAREA.DAT, SFNODE.DAT, SFSYSTEM.DAT, SFUSERS.DAT. Make sure the paths specified in SFNODE.DAT are correct for the current node. * Error removing temporary work directory. When no WORKDIR= is specified in the JetMail configuration file, JetMail makes its own temporary work directory off of the JetMail home directory. JetMail will automatically remove this directory upon exiting the door; however, an error was encountered trying to remove this directory, usually named TMP1.$$$ or something like that. You may safely delete the files in this directory and the directory once JetMail is done. Invalid argument: Invalid argument This error is only shown locally. JetMail encountered a DOS error when trying to determine the file date on the bulletins and/or newsletter, or determining file size prior to .QWK transfer. JetMail can encounter this error in an unexpected DOS environment, or conflict with TSR (memory resident) utilities. Try to not load unnecessary memory resident utilities and this should clear up. Error creating New Files list. Disk space problem? When the user is configured in JetMail to scan for new files, JetMail will generate a text file named NEWFILES.DAT in the JetMail temporary work directory.