LH> BJ> Linda Hargraves wrote in a message to Bob Juge:

LH> BJ> Expecting Scott to upgrade 2.02 to Y2K just isn't realistic, since
LH> BJ> he worked very hard on its successor, 3.0x, which is now the
LH> BJ> current version.  Would you also expect him to fix Max 1.0x too?

LH> LH>     No, but given the amount of difference, I think a patch would
LH> LH> not be too much to ask for the people who want to stay with
LH> LH> software they are comfortable with.

LH> BJ> Not a realistic expectation, I'm afraid.  Move on.  :-)

LH>    You may be right.  I am considering it.  Will I have
LH>any problems with the control files and menus?  Do you
LH>think I can keep everything as it is now?

    I'm another one still using Maximus 2.n - on the idea that if it
    ain't broke - why fix it?  There is nothing fancy being done on
    my BBS - and 2.n works just fine.  However - I do have version 3
    waiting - just in case.  I have one other sysop friend who
    'upgraded' just for the fun of it - and had absolutely no
    problems - though she is still sticking with version 2 for now.

    I'm not sure how many 'serious' bugs might pop up with version 2
    - as long as you don't use the option of deleting messages by
    date.  I was told that version 2.n will absolutely trash your
    bases when it rolls over.  (Bad pun - rolls over and squishes
    them)?  Seriously - get version 3.n (I think it's 3.2 - not
    sure) and give it a try sometime.  Just read with care on how
    the base file names are handled and you won't get into any
    trouble.


 * SLMR 2.1a * 

--- Maximus/2 3.01