Some common questions and answers regarding ConEd usage:

Q:  When I press F3 or F4 to edit my AUTOEXEC.xxx or CONFIG.xxx, I get an
    error message "No such file or directory, Press any key to continue".
    What is wrong?

A:  In the configuration menu, you are asked to provide the path to your
    editor, and the editors file name.  Ensure you have indicated the
    correct path and file name to your editor.  If you entered "QEDIT.COM"
    and the correct file name is "QEDIT.EXE", this error will appear.


Q:  My configuration descriptions are all messed up.  Seems as though they
    start on one line, and continue to the next, whats up?

A:  The ConEd26.CFG file is 55 characters in length.  Characters 1 thru 50
    are reserved for your configuration description, characters 51 thru 53
    are used for your configuration extensions, and characters 54 and 55
    are used internally.  If you use an editor to go into this file, and
    that editor deletes trailing spaces, you will change the file format,
    thus changing the display.  

Q:  When I use ConEd to change my current configuration by pressing the
    <ENTER> key (or using <ALT-C> to update my config), either I get a
    zero byte AUTOEXEC/CONFIG in my root directory, or my configurations
    haven't changed.  What am I doing wrong?

A:  There a few possibilities here.  If you are using a program such as
    PC-TOOLS mirror, or some other such program that 'protects' your
    root directory configuration files, there is a conflict.  ConEd is
    trying to modifiy these files, and the other programs are doing their
    job by protecting them.  Try invoking these programs later on in your
    AUTOEXEC, or turning them off before invoking ConEd.
    Another possibility is you are using a disk cache (software) of some
    kind, and you did not enter the 'flush' command in the ConEd
    configuration menu (F5 will get you there).  One of the functions of
    a disk cache is to store the last file write in memory before actually
    writing to disk, if this memory is not written to disk before a reboot,
    the 'copy' never really happens.  To fix this, enter the command to
    flush your disk cache.