| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | message area woes |
Ok.... Have you run any of the recovery tools on the message base? What is the maximum number of messages in the given .sqd file? Have you taken a power interuption while processing any of the squish files? (Either during clean up or during normal activity?) BJ> Which versions of the programs are you using (squishp or sq386p)? AH> sq386p Good. This has higher limits before you hit something.... BJ> How large are the .sqd files? AH> Various sizes. BJ> How much free disk space to you have on the partition? AH> 50 meg - far larger than any .sqd file (largest is about 1.6 meg.) Ok. So largest is about 1.6 meg. How many messages is in that file? BJ> Have you scripted any cleanup of the databases? AH> Yes - twice per week. What type of cleanup do you have scripted? BJ> Are you running anything to regularly or periodically pack the BJ> squish files? AH> Yes - sqpack. Ok. Are you deleting messages based on age or size prior to the sqpack? BJ> Do you have any bad packets sitting arround, in either the BJ> inbound or squish directories? AH> No. Good. BJ> Just some starting questions. I'm not sure I've seen this BJ> problem in the past.... AH> Neither have I, in all the years I've run Max and Squish. AH> Thanks. *adh* Well, we haven't figure it out yet.... As to the person who suggested deleting and starting over, a few other suggestions to try: (1) Run the tool for fixing databases and/or the tool that checks databass that came with squish. (2) If you want to delete the existing database, convert the format from .sqd to *.msg (in unique directories per .sqd file), delete the related .sq? files for that one area, and then convert back (from *.msg to .sqd format)..... Don't know if that will help, but if you have any internal file corruption, you should be cleared when done..... Doing (2) without doing (1) may loose messages without warning. Doing (1) should tell you if there is internal corruption and in the case of the fixing tool attempt to fix the problem. Best wishes.... Bob Jones, 1:343/41 --- Maximus/2 3.01* Origin: Top Hat 2 BBS (1:343/41) SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 343/41 138/146 392 123/500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.