
 ˻            ɻ  ɻ               ɻ
   ˻        λμ   ˻  ͹   MaXimus eXternal msgEDitor
       ɻɻ   μ    ʼ         Copyright (C) 1996-2002
       μ   λ    ʼ  ʼ       By Thomas Mueller
 ȼ      λ  μλ   MxXEd/2               All Rights Reserved
     ȼ  ȼ  ȼȼ  ȼ  ȼ


              D O C U M E N T A T I O N - as by 14th JUN 1998

Ŀ
 Preface 

    Please keep in mind that English is not my native language and therefore
    I might use wrong words and make mistakes. If you find any errors I
    would be glad if you send me your corrections.

Ŀ
 Version 

    The current version of MxXEd is 1.02.000 compiled 2002-02-24. Please
    don't forget to mention it when mailing me.

Ŀ
 Disclaimer 

    This program is sold as is. There is no warranty of any kind.

Ŀ
 Features 

    - navigation by cursor keys
    - very simple installation, uses the Maximus configuration
    - supports Maximus divisions
    - "Umlaut" conversion for areas without the HiBit flag
    - supports the netmail flags set in the system section
      (Message Edit Assume/Ask)
    - Watchdog for carrier (lost) and timeout
    - sort order of areas can be changed by the user
    - nodelistlookup with V7(+)-Nodelist
    - context sensitive online help
    - newmail rescan
    - shows *emphasized*, _underlined_ and /italic/ words in different
      colours
    - shows area rules
    - supports the maximus alias system
    - supplies the missing feature in Maximus: Comment to Cosysop
    amm.

Ŀ
 What is MxXEd? 

    MxXEd/2 is a mail editor for Maximus which can be used by bbs users
    to read and write messages online and also by the sysop to use it
    offline.

Ŀ
 System requirements 

    Hardware: Every computer capable of running OS/2 and the OS/2 version
              of Maximus.
    Software: MxXEd/2 was tested under OS/2 Warp 3.0 Connect. It should
              also work with OS/2 2.x and Warp 4.
              It uses the configuration files of Maximus 3.x so it cannot
              be used with earlier versions of Maximus.

Ŀ
 How it works 

    MxXEd is called as a door program from Maximus. It reads the
    configuration files of Maximus including the access rights and
    shows the areas according to the division structure.
    You can also use MxXEd as a local message editor. The only thing you
    must know is the number of the sysops lastread pointer in the
    messagebase. This should normally be the 0 as the sysop account is
    the first account created by Maximus.

Ŀ
 How to use it 

    To navigate use the cursor keys, esc, return/enter and the
    "wordstar"-keys. It depends on the terminal program which keys are
    actually available. You should switch it to "doorway mode".
    Locally you can use all of the keys.

    MxXEd uses the Maximus configuration in every task:

    It converts "Umlaute" for all areas without the HiBit flag.

    It honors the netmail flags given in the system section of MAX.CTL
    (see Maximus documentation).

    For more information about using and a more detailed description of
    the available functions and keys see MXXED.HLP. This file is shown
    locally when pressing F1 and remote when pressing ?.

Ŀ
 Installation as online editor 

    To start MxXEd needs the following files:

      MXXED.EXE - the program itself
      MXXED.CFG - the configuration
      MXXED.TPL - the message template
      MXXED.HLP - the online help

    You can copy these files into a directory of your choice p.e. into
    \MAX\MXXED, a subdirectory of the Maximus directory. The examples given
    assume this location.

    MxXEd/2 needs the Maximus nodenumber (not the fidonet address, see
    multinode operation in the Maximus documentation) and the COM handle.
    everything else is retrieved from the Maximus configuration.

    Usage:

       MXXED /H:xx /K:<nodenumber> [optional params]

           /H:xx         = COM handle (not the COM port number!)
           /K:XX         = Nodenumber of Maximus
                           (Not the fidonet address but the number of the
                            Maximus line.)

       the following parameters are optional:

           /C:<mxxedcfg> = Configuration file for MxXEd, if not in the
                           current directory or in the directory of the
                           executable (see sample configuration).
           /L:<lreadidx> = Lastread index of the User (for local mode only)
           /M:<maxdir>   = Directory, where the Maximus configuration files
                           (MAREA.*, USER.BBS and ACCESS.*) are located,
                           normally the Maximus directory, required only if
                           it is not the current directory.
           /S:<msgbase>  = Base directory of the messagebase if not fully
                           given in MAREA.DAT.
           /N:<nodelist> = Base directory for the nodelist files if not
                           fully given in MAX.PRM.

           The switches /S: and /N: can be useful if you want to start
           MxXEd over the network. They are used without any plausibility
           tests! Normally you should not need them.

           /R:<time>     = Starts background rescan every <time> second
                           (default: no rescan).
                           Please note: Some users have reported that MxXEd/2
                           hangs when exiting after counting down.
                           This can be circumvented by specifying /R:0

           With the following parameters you can predefine some data:

           /E:[dest_name[@destaddr]]/[area]/["subject"]

                   [dest_name] = destination name of msg.
                                 (defaults to sysop name)
                   [destaddr]  = destination address of msg. if needed
                   [area]      = area to post msg in (defaults to Maximus
                                 comment area)
                   ["subject"] = subject of message (defaults to "Comment
                                 from <username>")

           /A:<area>     = Sets the area / division where MxXEd starts.
           /F:<area>     = Restricts access to an area / division.


    Sample entry for MENUS.CLT:

      Menu Message
        UsrRemote reread Xtern_Run \MAX\MXXED\MxXEd.exe_/H:%P_/K:%k disgrace/x "MxXEd"

    Alternatively you can put this line into a MECCA file and call
    it from MENUS.CTL:

      Menu Message Display_File Mail\MxXEd\mxxed Limited/B "M"

      This is the called MECCA file:

      ------------------- MXXED.MEC -------------------------
      Starting MxXEd Maileditor, please wait ...

      [Xtern_Run]\MAX\MXXED\mxxed.exe /H:%P /K:%k
      -------------------------------------------------------

    You can also use MxXEd to let the user write a comment to the sysop:
    (Please join lines at ... )

      UsrRemote reread Xtern_Run ...
        ... \max\mxxed\mxxed.exe_/H:%P_/M:\MAX_/K:%k_/E://"comment_about_your_BBS" ...
        ... disgrace "comment to sysop"

      UsrLocal reread Xtern_Run ...
        ... \dfue\max\mxxed\mxxed.exe_/K:%k_/E://"comment_about_your_BBS" ...
        ... disgrace "comment to sysop"

    Or if you want him write to your cosysop instead:

      UsrRemote reread Xtern_Run ...
        ... \max\mxxed\mxxed.exe_/H:%P_/M:\MAX_/K:%k_/E:Co-Sysop//"comment_about_the_BBS" ...
        ... disgrace "comment to cosysop"

      UsrLocal reread Xtern_Run ...
        ... \dfue\max\mxxed\mxxed.exe_/K:%k_/E:Co-Sysop//"comment_about_the_BBS" ...
        ... disgrace "comment to cosysop"


Ŀ
 Config file 

    All comment lines in the config file of MxXEd start with ; (semicolon).
    The commands listed here are also described in the sample MXXED.CFG.

    Commands are case insensitive, parameters have "<>" around them.

    lastread=<NUMBER> : Lastread index to use. The sysop should normally
                        have 0. If not you should change it with the
                        supplied utility ChgLrIdx (see below).
                        (see parameter /L )

    maxdir=<PATH> : Directory where the configuration files of Maximus
                    (MAREA.*, USER.BBS und ACCESS.*) are located,
                    normally the Maximus directory, only required if not
                    the current directory.
                    (see parameter /M )

    msgbase=<PATH> : Base directory of the message base if not fully given
                     in MAREA.DAT.
                     (see parameter /S )

    nodelist=<PATH> : Base directory of the nodelist if not fully given
                      in MAX.PRM.
                      (see parameter /N )

    helpfile=<PATH>\<FILE> : Directory and file which contains the online
                             help. Displayed with ?. Defaults to MXXED.HLP
                             in the executable directory.
                             Note: If you change (or translate) the help
                                   file do NOT change chapter frames and
                                   numbers. If you do the online help will
                                   no longer work.

    template=<PATH>\<FILE> : Directory and file which contains the template
                             used for creating a message. Defaults to
                             MXXED.TPL in the executable directory.
                             (see chapter "Template")

    BrowseFields=<FIELDS> : Sets the displayed fields in the message list
                            according to this table:

                            Field      Description             Key to toggle

                            MsgNum     messagenumber             N
                            FromName   name in the from field    F
                            ToName     name in the to field      T
                            Subject    subject                   <none>
                            DTWritten  date/time written         W
                            DTArrived  date/time arrived         A

    Lines=<COUNT> : This is the number of lines used in offline mode.
                    In online mode it is read from LASTUSxx.BBS.

    ColorXX=<COLOURCODE> : If you do not like colours you can change them
                           using this statement. Please refer to MXXED.COL
                           as a reference about colour codes and affected
                           elements.
                           Colours are given as two hex digits, the first
                           digit defines the foreground colour the second
                           digit defines the background colour.

                           example:
                           Color29=0F
                           Set the area selection bar to black on white.

    RulesPath=<PATH> : Directory where the rules files are located which are
                       displayed when the user presses shift F1 or *.


Ŀ
 Templates 

    Since the homo sapiens is lazy (at least I am ;-) ) he appreciates every
    part of (stupid) work already done by a machine (I would really like a
    machine that types stupid manuals ;-)) ). By using a template
    you can supply the user with some text he normally would have to
    type himself. It is very convenient when replying or forwarding a
    message.

    Templates can also be defined on a per area basis. For Squish style
    areas put them into a file with the same name as the squish base and
    the extension *.TPL. For SDM areas put them in a file named MXXED.TPL
    in the directory of the messagebase.
    MxXEd will always look for an area specific template first.

    This is a list of all tokens recognised by MxXEd. For a working example
    see the supplied MXXED.TPL.

    All comments start with a ; (semicolon).

    All tokens start with a @ (at sign). All text is copied into the message as
    given in the template. If you want a @ (at sign) in normal text use
    two of it (@@ -> @).

     @Follow    = Inserted when replying in a different area.

     @Moved     = Inserted when moving a message.

     @Copied    = Inserted when copying a message.

     @Reply     = Inserted when replying without quotes.

     @Request   = Inserted in a filerequest message.
                  Please note: Normally you should _not_ send any text
                               with a filerequest message.

     @Changed   = Inserted when changing a message which is not from you.

     @Own       = Inserted when writing an own message (not change / copy /
                  move ).

     @Comment   = Inserted when writing a comment reply.

     @Quoted    = Inserted when replying with quotes.

     @New       = Inserted when writing a new (non reply) message.

     @Forward   = Inserted when forwarding a message.

     @Quotes    = Inserts quoted lines of the original message.

     @Message   = Inserts lines of the original message when forwarding /
                  copying, moving or changing a message.

     @Position  = Sets the cursor position. Can be used along with
                  other tokens.

     @CAddr     = address of the current user
     @CLName    = last name of the current user
     @CFName    = first name of the current user
     @CName     = full name of the current user
     @CDate     = current date
     @CTime     = current time
     @DFName    = first name of addressee in original message
     @DLName    = last name of addressee in original message
     @DName     = full name of addressee in original message
     @OAddr     = original address
     @ODesc     = original area description
     @OEcho     = original area id (name)
     @OFName    = first name of original author
     @OLName    = last name of original author
     @OName     = full name of original author
     @ODate     = original date
     @OTime     = original time
     @Subject   = subject line of message
     @TName     = full name of addressee
     @TFName    = first name of addressee
     @TLName    = last name of addressee

     @@         = single @ (at sign) p.e. for internet addresses


Ŀ
 Displaying Area Rules 

    You can display the area rules by pressing Shift F1 (local) or
    * (remote).

    For squish areas you must save them into a file with the same name
    as the squish base and the extension *.SQR. (See special features, write
    to disk)

    sample:
    echoarea os2.ger m:\msgbase\os2 -> Rules = m:\msgbase\os2.sqr

    For SDM (Star dot MSG) areas you must supply them in a file named
    RULES.BBS located in the same directory as the *.MSG files.

    If you prefer to keep all rules files in one directory just set
    the RULESPATH parameter in the MXXED.CFG to this directory. In this
    case you should use the directory name of SMD areas for the filename.

    Note: If you use the RULESPATH all areas must have different filenames.
          Do *NOT* use something like OS2.GER=\ger\os2 and OS2=\intern\os2.

    If MxXEd finds a rules file it displays a hint on the status line.


Ŀ
 Tools 

    ChgLrIdx - ChangeLastreadIndex

      With this program you can exchange the lastread index of two
      users. This is recommended if for some reason not the sysop but
      another bbs user has the lastread index 0. This user would probably
      have noted that his lastread pointers changed without him reading
      any mails, because most external tools use this index.

      usage:

        ChgLrIdx <OrigUserBBS> <NewUserBBS> <Lastread index> <Username>

      sample:

        If JOCHEN SCHNUERLE = 0 and THOMAS MUELLER = 1

        CHGLRIDX USER.BBS  USER1.BBS 0 THOMAS MUELLER

        result: In USER1.BBS JOCHEN SCHNUERLE has now index 1 and
                  THOMAS MUELLER has Index 0.

        You can achieve the same result with this command:

        CHGLRIDX USER.BBS USER1.BBS 1 JOCHEN SCHNUERLE

        To prevent corruption you must supply different filenames for
        <OrigUserBBS> and <NewUserBBS>. If everything works fine you
        have to rename the created file.

        This program is a quick'n'dirty hack which works for me (Thomas
        W. Mueller) and Jochen. There is no warranty that it works for
        anybody else.


    SortUser

      Resorts the USER.BBS file based on the lastread index.

      usage:

        SortUser <OrigUserBBS> <NewUserBBS>

      sample:

        SORTUSER USER.BBS USER1.BBS

      Note: The warnings on ChgLrIdx also apply here.


Ŀ
 Using MxXEd as Offline-Editor 

    One of the design goals of MxXEd is that it can be used as both, an
    online editor for the bbs users and an offline editor for the sysop.
    By doing this you can save a lot of time you would normally spend on
    configuring a messageeditor.
    Since it is not possible to read the data from the LASTUSxx.BBS because
    this file is only created by maximus when spawning bbs doors, you must
    supply the lastread index either in the MXXED.CFG file or by using the
    /L: commandline parameter. Normally the sysop has the lastread index 0.

    mxxed.exe /m:\max /l:0

    If you do not have access to the netmail area or experience other
    problems you should check first, if your username has really the
    lastread index 0. If not use the supplied program to change it.


Ŀ
 Errorlevels 

    MxXEd sets the Errorlevel according to the Maximus configuration.
    (Descriptions are copied from the Maximus documentation.)

    Errorlevel

     [ 0] Carrier Lost or Timeout

     [ 1] Internal error

     [ 5] After Call Exit <errorlevel>

            This keyword tells Maximus which errorlevel to use after a
            caller logs off (without leaving any messages).

     [11} After EchoMail Exit <errorlevel>

            This keyword tells Maximus which errorlevel to use when a
            user enters EchoMail messages. This errorlevel will super-
            sede the After Edit errorlevel.

     [12] After Edit Exit <errorlevel>

            This keyword tells Maximus which errorlevel to use when a
            user enters NetMail messages. This errorlevel is superseded
            by the After EchoMail errorlevel.

     [13] After Local Exit <errorlevel>

            This keyword tells Maximus which errorlevel to use when a
            user enters local messages. This errorlevel is superseded
            by both the After EchoMail and After Edit errorlevels.


Ŀ
 Special Features 

    ECHOAREA.LOG

      If you configure "log echomail" in the "matrix and echomail section"
      of the maximus configuration, MxXEd creates a file containing a list
      of areas where the user has written messages.
      Please note: This file is never overwritten but appended to. The
                   sysop (Yes, that's you!) is responsible to delete
                   it when appropriate.


    Write / Print / Download

      By pressing W in the message display a user can write the current
      message to a file, print it or export it to the rules file of the
      current area. Remote users can download the message as a file.
      Writing to the local harddisk and the printer is restricted by the
      access level for MsgXport (override message Msg_XPort).
      Please note: This is a potential dangerous command because a
                   malicious user could overwrite the CONFIG.SYS file
                   if the access level is not set correctly.
                   Because of that this command is by default only
                   available to the sysop. If you want your cosysop
                   have access to it you have to use override in the
                   Maximus configuration.


    Maximus Alias System

      MxXEd supports the alias system of Maximus. If it does not work,
      please make sure that 1. it is activated and 2. the user really
      has an alias. If not MxXEd will use the realname.
      * For areas where anonymous messages are allowed (eg. messages
        which use neither the realname nor the given alias) the user gets
        a selection menu for his realname or his alias when he presses
        Tab, Return or Down with an *empty* from field.
      * For areas where the realname or the alias is allowed (eg. areastyle
        neither alias nor realname but the alias system activated) the
        user gets this selection menu every time he tries to enter text
        into the from field.
      * For areas with areastyle alias or realname the appropriate name
        is set automatically and cannot be changed (except the user has the
        MsgAttrAny flag set for his access class).
      (Hopefully MxXEd handles this in the same manner as Maximus does.
      Since I have never used the alias system I could not test it
      thoroughly.)
      The template tokens CNAME, CFNAME and CLNAME refer to the alias
      if the alias is used as originating name.
      MxXEd honors the setting of "No Realname Kludge" and the areastyle
      NoNameKludge. Please note that the areastyle toggles the general
      setting. According to the documentation this is the same as under
      Maximus.


    Binkley and other "Dumb" terminals

      The built in terminal of BinkleyTerm and some other terminal
      programs do not support the ANSI control sequence for deleting
      a line. Since this sequence is a very efficient way for scrolling
      the screen I do not want to punish users of "smarter" terminal
      programs by not using it. So MxXEd asks each user the first time
      it is started by him if he can see a line that it has just deleted
      using the mentioned sequence. If the user can see it he is using
      a "dumb" terminal. MxXEd saves this result into the MXXUSER.BBS file
      so the user does not need to answer this question every time he starts
      the program.


    V7+ nodelists

      The most recent version of fastlist can create so called V7+
      nodelists. This nodelist format has some advantages over the "old"
      V7 nodelist (capitalization of and dots in sysop names) but is
      backward compatible to V7 so it can be used even by older software.
      MxXEd uses V7+ format but can also handle V7 format.


Ŀ
 Netmail Flags 

    MxXEd honors the edit entries in the Matrix and EchoMail section of
    the MAX.CTL file:

    Message Edit <Action> <Attribute> <AccessControlString>

       These entries tell Maximus (and MxXEd) which flags it should use
       when a user writes a netmail.

       ASSUME entries set the corresponding flag ASK entries allow the
       user to toggle it.

       There are several possible <Attribute> names:

           * Private
           * Crash
           * FileAttach
           * KillSent
           * Hold
           * FromFile
           * FileReq
           * UpdateReq
           * LocalAttach

       sample:

           Message Edit Assume Private       Normal
           Message Edit Assume Crash         Hidden
           Message Edit Assume FileAttach    Hidden
           Message Edit Assume KillSent      Hidden
           Message Edit Assume Hold          Hidden
           Message Edit Assume FileRequest   Hidden
           Message Edit Assume UpdateRequest Hidden

           Message Edit Ask Private          Hidden
           Message Edit Ask Crash            Sysop
           Message Edit Ask FileAttach       Sysop
           Message Edit Ask KillSent         Hidden
           Message Edit Ask Hold             Sysop
           Message Edit Ask FileRequest      Hidden
           Message Edit Ask UpdateRequest    Hidden
           Message Edit Ask LocalAttach      Normal

       Please note: The default setting of Maximus is

           Message Edit Assume Crash         Sysop

       so mails written by the sysop  by default have the Crash flag
       set. This is normally not desired.


Ŀ
 Controlchars and lines 

    A Kludge lines:
    ~~~~~~~~~~~~~~~~
    Kludge lines are special control lines which start with ^a (ASCII 1)
    followed by a command (see list) and further information.
    MxXEd creates and uses the following kludge lines:

    MSGID: <origaddress> <serialno>
      This provides a method to uniquely identify a message described
      in FTS-0009. It is used for dupe checking and reply linking.

      Sample: ^aMSGID: 2:2474/10 32c56444

    PID: <identifier> <Version> [serialno]
      This is no official kludge line but a proposal in FSC-0046.
      It identifies the program that created the message. Formerly this
      information appeared on the tearline but since some tossers have changed
      this line PID is a safer method to find problems in fidonet software.

      Sample: ^aPID: MxXEd 1.0 970001

    REPLY: <replyaddress> <replyserialno>
      MSGID of the original message to which this message refers.
      Described in FTS-0009.

      Sample: ^aREPLY: 2:240/5353.0 2c4e5421

    INTL <destaddress> <origaddress>
      Solves the problem of missing zone information in netmails.
      Described in FTS-0001

      Sample: ^aINTL 2:240/5353 2:2474/10

    TOPT <to point>
      Solves the problem of missing point information in netmails.
      Described in FTS-0001

      Sample: ^aTOPT 44

    B Tearline:
    ~~~~~~~~~~~
    The tearline is the last line of a message followed only by the
    origin line. It contains the program name which has created the
    message if not changed by the tosser.
    The tearline must be no longer than 30 characters.

    Sample:  --- MxXEd/2 1.0

    C Origin:
    ~~~~~~~~~
    The origin line is the last line of a message. It often contains
    some silly or very important words. Technically the only important
    part is the origin address which is enclosed in brackets "(..)".
    This is the only method described by FTS to get the originating
    address of an echomail.

    Sample: * Origin: Written by my Boxuser - BetaBox  (2:2474/10)

    D VIA:
    ~~~~~~
    These control lines are only used in netmails. They document the
    way a netmail has travelled.

    Sample:
    ^aVia 2:24/99@FiDoNeT @19961228.104728.78.UTC Itrack+
    ^aVia 2:2474/0@FidoNet @19961229.001352.02.UTC Itrack+
    ^aVia SFSQ/32 0.98.2 2:2474/10.0, Sat Dec 28 1996 at 19:28


Ŀ
 Appendix 

    A Problems and missing features
    -------------------------------
      Yes - even a program as perfect as MxXEd and all Microsoft products ;-)
      might have bugs and shortcomings. Some of them are listed in
      MXXED.TD (TD = to do) together with a comment why they exist or don't.
      If you want to have a feature added to MxXEd please tell me.


    B Other operating systems
    -------------------------
      MxXEd/2 is only available for OS/2. There will never be a DOS
      Version. I will perhaps consider writing a Win32 version when
      I see a market for it (currently I don't).
      Since Virtual Pascal is now available for OS/2 and Win32 it
      would theoretically be possible to port MxXEd to Windows NT.
      Anybody who is really interested in such a port, should contact
      me.


    C Support and bug reports
    -------------------------
      Please send comments and bug reports to

        Thomas W. Mueller
        Fidonet...: 2:2454/917
        email.....: mxxedbug@s2h.cx

      Please make sure to mention the version of MxXEd you are using and
      enclose the (hopefully) created MXXED.ERR file.

    D Versions
    ----------

      MxXEd/2 can be downloaded from my homepage at http://www.s2h.cx
      This will most likely be the last version because I haven't used
      OS/2 for several years.


    E Acknowledgments
    -----------------

      I wish to thank my beta testers and all others who have supported
      me while writing MxXEd.

      Especially:
      -----------
        * Peter Meerwald for his Virtual Pascal version of the Squish
          MsgApi which made me think that writing a message reader would be
          a very simple thing to do ;-))
        * Mike Nix for his translation of the Maximus CTL files into
          PASCAL.
        * Matt Scott whose xgetch.mh gave me the idea how to implement
          navigation by cursor keys.
        * Jim Dailey for his excellent documentation of his V7NL.DLL
          which helped me much in implementing a V7 nodelist lookup.
        * Joy Mukherjee whose V7Engine I used as a basis for my code.
          (What a pity it contained so many bugs that I ended up in
          completely rewriting it.)
        * fPrint UK and Vitaly Miryanov for Virtual Pascal which is a
          really fantastic BP clone for OS/2.
        * Scott Dudley und Lanius Corp. for Maximus and Squish and the
          slightly buggy MsgApi32.DLL.
        * Michael Buenter whose Binkley EE version was the reason why
          I switched my fidonet node to OS/2 software.
        * Jochen Schnuerle who pushed me into implementing the message
          creation, converted my small README into this documentation
          and who tested every new version thoroughly.

      And last but not least my girl friend who has endured my
      obsession to fidonet and computers for many years. :-)


    F Ordering information
    ----------------------

      MxXEd/2 is now FREEWARE, so no registration is necessary.



    G Copyrights
    ------------

       Virtual Pascal is copyrighted by fprint UK ltd.
       Maximus is copyrighted by Scott J. Dudley, Lanius corp.
       OS/2 and OS/2 Warp are copyrighted by IBM
       Windows NT and Bug are copyrighted by Microsoft corp.


    H Miscellaneous
    ---------------

       The fact that I was workin for fPrint UK Ltd when I wrote
       MxXED/2 does not mean that MxXEd is in any way related to
       my employer. He does not have any rights on it nor does he
       have any resposibilities for it.
