TIP: Click on subject to list as thread! ANSI
echo: muffin
to: Bo Simonsen
from: Peter Knapper
date: 2003-10-18 08:32:56
subject: Maximus message editing

Hi Bo,

 BS> Well, it works now, so it wasn't a bug.. The problem was that
 BS> maximus could find the menu which is "message", but on my system
 BS> it uppercase so it's "MESSAGE", and Linux is case sentitive.

 BS> Does anyone have a clue where to find the place where "message" is?

Boy, does this ring bells here....;-)  Yes... the MENU NAME may be CRITICAL
to the operation of Maximus in non-obvious ways!!!

The following is a rather verbose message I sent to Scott outlining what
happened here and in reply he confirmed my finding's, however I can't find
his reply.....;-( I thought he said that future code should remove this
issue but maybe it never got into the source you are using. Anyway, the
following might be of use to you...

===================================================================
   From: Peter Knapper                        (3:772/1.10)
     To: Scott Dudley                         (1:249/106)
Subject: Bug report!

Hi Scott, greetings from down in the South Pacific.

You may already know about this one but its a trap I dropped into
nicely, so I thought I should bug you with it. At least I found the
solution without screaming for help...

I have been running Maximus/2 for some months fine,
however on May 10th things went wrong. At 06:26 a user uploaded
a QWK reply packet and the messages tossed ok. Sometime during
the day a large backlog of mail arrived (about 1.5MB compressed)
and filled up the HD (at least past the trigger level I had set).
When I arrived home that night QWK reply uploads were failing
(surprise), however after clearing the mail and making space,
QWk reply uploads worked, but the toss failed with 'Invalid area'
messages. Even if the user listed the areas and provided an area
manually it would not be accepted. All normal online message entry
and uploading was working exactly as planned.

Several nights later, after clearing out MTAG.BBS, and OLR\DAT\*.DAT
files, restoring USER.BBS and re-running Siltp I still could not get
it working again. About this time I also found out that the
CheckMail command was not allowing users to reply to mail. I
remembered a note about this and found a reference in your 2.01
upgrade Doc's about the QWK reply processing and Checkmail
processing using the access levels in the message reading menu and
this got me on the right track. The access levels in my menu were
correct, however Max seemed to be ignoring them!!!!

Going back in history, about 1 - 2 months before all this I had
introduced a new Menu system by building one using all new menu
names and making it selectable from the MAIN menu. Once I had the
new system up and working I replaced the standard Max one with
mine by swapping in my new MAIN menu. All options from MAIN menu
selected new menu names. Everything from then on ran swimingly
until the QWK saga started.

To cut the story short, my new menu system used menu names
different to the standard system and several new menu names were
added (FILE was FILE2, MESSAGE was MESSAGE2, CHANGE became SETUP,
and ACCESS menu was added, etc...). Of course when my HD filled
I looked for files not needed, and I removed all the old .MNU
files that had not been needed since I compiled the new menus.
The reason QWK replies kept working after the menu change was
because the old MESSAGE.MNU file was still on the HD, and this
was what Max was using for QWK and Checkmail access levels, not
my new MESSAGE2.MNU. It seems that the QWK access routine must be
using a hard coded filename of MESSAGE.MNU. As soon as I replaced
this file, QWk and Checkmail worked again. A real good trap that
one...;-)

I realize there is no way for you to know what my message menu is
likely to be called so I dont know how it could be handled, but if
you have not run into this by now, you may come up with a way of
preventing this from happening again.........;-)

Anyway, thanks for some excellent S/W, its been doing a grand job
and on OS/2 its totally stable (except for QWK replies.....;-)).

Regards............pk (Sysop 3:772/1).
==============================================================

I hope this helps............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
SEEN-BY: 633/267 270
@PATH: 772/1 140/1 106/2000 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™.