Hi Bob,

 BJ> Linda Hargraves wrote in a message to Roy J. Tellason:

 RJT> I wouldn't worry too much about losing your utilities.  I am so 
 RJT> in the habit of typing "silt max -p -2a" because something or 
 RJT> other needed the old-style files that I don't even think about it 
 RJT> any more.  I can't even remember what it was that needed it.

 LH>      What do those switches do?  I don't believe I have ever seen
 LH> any reference to them, unless they pertain to v3.01.

 BJ> Running Max 3.01's SILT.EXE with no command line arguments yields this:


 BJ> Command-line format:

 BJ>   SILT  [[-x]...]

 BJ> Valid switches are:

 BJ>   -p      Generates Maximus .PRM file, and Opus .PRM files (if requested).
 BJ>   -a      Generates msg/file data files. (Implies -am and -af.)
 BJ>   -am     Generates message area data.
 BJ>   -af     Generates file area data.
 BJ>   -m      Generates *.MNU menu data files.
 BJ>   -x      Generates all of the above.
 BJ>   -2a     Generates optional Max 2.0-compatible AREA.* files (normal)
 BJ>   -2u     As above, but use underscores instead of dots in area name
 BJ>   -2s     As above, but use short area names (no divisions)
 BJ>   -u      Unattended mode -- tells SILT never to prompt for user input.

 BJ> If no switches are specified, then SILT defaults to generating everything
 BJ> except the Max 2.x-compatible area files.

    This is an example of exactly why I don't like most upgrades.  Too much
gets changed, not always for the better.  This is one time, I guess I will
HAVE to upgrade, like it or not.  Why do programmers not listen to their
users?
Don't we try to support them?  Shouldn't they at least attempt to
understand our needs/wants?

  Right now, I have not even found the upgrade.

   TTYL
      Linda
        cat.lady{at}cats.gratisnet.com

--- Maximus 2.02