INSTALLATION
============
Note that VBRUN100.DLL is required in the path or in c:\windows\system !!! 
I did not add it for the ZIP version of NCOM because authors are generaly 
asked to do not. The reason is that this file is available at most shareware 
places anyway and it would drastically increase the ZIP file size. Please 
download from well known places if you do not have it (eg. at 
"ftp.cc.monash.edu.au" in "/pub/win3/util" with user name "anonymous")!

Automatic Installation
----------------------
Use only one of the following two installation procedures

1) Under Windows

  I have just written a windows installation procedure with the name 
  INST_WIN.EXE. Also this installation procedure uses VBRUN100.DLL. Please 
  get it and copy it in the windows system directory (c:\windows\system) 
  before running INST_WIN.EXE.


2) Under DOS

  I have also written as alternative INSTALL.BAT which shall be called from 
  the disk or the directory where the installation files are located in 
  following way:
      INSTALL.BAT {drive:\NCOM-dir} {drive:\MS-Windows-dir}
  An example could be
      INSTALL.BAT C:\NCOM C:\WINDOWS


Note that both installation procedures do not create an Icon in the Program 
Manager. This has to be done manually. Note also that if the Visual Basic 
Libraries (extension: .vbx) with NCOM are newer, copy them manually because 
the Install Batch does not copy if the file is already there regardless
of the version.

Creating an Icon in the Program Manager
---------------------------------------
You may use the MS-File Manager and drag the file NCOM.EXE into the 
MS-Program Manager in order to create an icon there. This will automatically
assign the NCOM directory as default startup directory which is necessary
if you need to use the HELP menu.

Using Long File Names for the Impatient
---------------------------------------
After calling NCOM you may try the feature of long file names by selecting 
a file and enter F6 or the rename button and enter any file name you want.
It will immediately appear in the file list. That's it. Now you can work 
in NCOM with the long file name as with every other file (copy, delete, 
move etc.). It even works for subdirectories which you might create by 
entering F7 or the MkDir button. If you have the file extension associated 
with some application just double click on the long name and the application 
with that file comes up.

Manual Installation
-------------------
Both, the disk version or the ZIP file have a windows subdirectory. This
subdirectory indicates the files which shall be copied into the
MS-Windows systems directory (eg. "c:\windows\system"). Especially,
the files "cmdialog.vbx", "mlistbox.vbx", "vbio.vbx", "vbrun100.dll", 
and "d&dserve.dll" must be copied or moved there. Please check if they are 
already there and, if so, if they have a newer version. You may not want to 
overwrite the newer version. 

For trying NCOM it is a good idea to copy the sample configuration files, 
such as "ncom.mnu" and "ncom.dmn" into the windows directory which enables 
you to call the Menu or Dir-Menu. 

Please copy the rest of the files in the NCOM subdirectory (eg. "c:\ncom").