TBBS 2.x - MFSQZ Lock-Ups (Bad Message Records)

Contact:   eSoft, Inc. (Makers of TBBS)
           15200 E. Girard Ave., Suite 3000
           Aurora, CO  80014
           (303) 699-6565      Voice
           (303) 699-6872      Fax
           (303) 699-8222      BBS
           support@esoft.com   E-Mail

MFSQZ LOCK-UPS (BAD MESSAGE RECORDS)
------------------------------------

Occasionally, MFSQZ, the TBBS message base maintenance utility, may experience 
"lock-ups" while performing a "squeeze" operation.  These lock-ups are 
typically due to a bad record (message) within the message base files.  

There are many different causes for bad records developing in the message 
base.  A defect developing on the hard disk, incorrect or incomplete 
operations of third party programs, and severe power fluctuations are just a 
few of the possible causes.  One cause which involves no problems on your part 
is a badly malformed EchoMail message (which would only happen to users that 
use the TBBS NetMail Option package in the Amateur FidoNet). 

If your message base should develop a bad record, there are two approaches you 
may take to rectifying the situation.  

                           Method One - Easy Method
                       Message Base WILL NOT Be Current

Revert to a back-up of your message base files.  The message base is contained 
in two files, MSG.BBS (the message text) and MSGHDR.BBS (information about 
each message).  If you have recent back-ups that have been made to a tape 
drive or floppy disk, you may wish to restore those back-ups to your system.  
NOTE:  Do not use the MSG.BAK and MSGHDR.BAK files that may exist on your 
system -- these are in use during the squeezing operation, and are not 
reliable back-ups when MFSQZ fails. 

                          Method Two - Complex Method
                         Message Base WILL Be Current

You may try to locate the bad record, delete the message associated with that 
record, and try the squeezing operation again.  The numbers shown during the 
squeeze operation represent total messages, not message numbers.  However, the 
number shown on the screen when the MFSQZ operation locks-up indicates how 
many messages from the BACK of the message base the bad record can be found. 

For example, if MFSQZ locks up displaying the number "287," then the bad 
record is 287 messages from back of the message base.  You can then get a 
general idea which message (or record) is causing the problem.  If your 
message base is sequentially numbered with NO gaps, simple math can direct you 
to the specific message in question. 

MFSQZ should be used to locate and delete the bad message record.  Invoke 
MFSQZ, select <2>, then <2> again to examine all message headers.  Page 
through using the minus (-) and semi-colon (;) keys.  The bad message should 
be immediately detectable -- frequently the "to" name, "from" name, subject 
and/or message chain references (numbers of the messages previous and next in 
the message chain) are garbled, or out of the range of possibility.  Delete 
the message by pressing the "D" key, then quit by pressing the "Q" key.  Try 
the squeeze again by selecting <9> to exit and do squeeze.  

                                    Summary

If the latter method of fixing this problem is not successful, then chances 
are excellent that the only chance of recovering is to use a back-up copy as 
described in the first method.  Keeping frequent back-ups of your system -- in 
particular the TBBS system files -- is extremely important and is highly 
recommended. 

If the damage appears to be caused by a defect on the hard disk, then you 
would be well advised to rectify the situation by using the appropriate third-
party hard disk utilities.  Hard disk defects will often show themselves by 
displaying the appropriate DOS error after MFSQZ stops running. 

- END -
TBBS0057
Rev. ??/??

Copyright (C) 1994 eSoft, Inc., All Rights Reserved.  Permission granted
to distribute this file in its entirety, without modification, to any
interested party.  Any other use requires the written permission of
eSoft, Inc.

IMPORTANT:  The information herein is subject to change without notice.
Please call or write to confirm factual information of importance to you
or your organization.

