-------------------------
Loading NCSI With Windows
-------------------------

The client workstation interface, NCSI (Network Communication Services
Interface), needs to be loaded on every workstation that requires access to
the communication server.  NCSI does not need to be loaded on the
communication server unless that server is running NPC communication server
software as a TSR in a non-dedicated mode AND that workstation also requires
access to the communication server resident there.

There are three ways to load NCSI on a Windows workstation:

1.  Load NCSI prior to starting Windows. Note that the network drivers MUST
	be started prior to loading NCSI.  This may not be possible if you are
	using protected-mode drivers.

	You can save on memory by loading NCSI high (but avoid memory
    optimization programs) and disabling the command interpreter with a
    -C and limiting the number of virtual circuits with -Vn, where n is
    the number of virtual circuits desired. Note that some applications
    use more than one virtual circuit.  Note also that some applications
    use the command interpreter, but mask its use from the user.

2.  Create a file called WINSTART.BAT in your \WINDOWS sub-directory and using
    standard ASCII text editor enter the line NCSI -W.  NCSI detects the
    presence of the Windows kernel and needs the -W switch to instruct NCSI to
    load and unload properly under Windows.  WINSTART.BAT is analogous
    to AUTOEXEC.BAT for DOS and loads devices in extended memory after
    the Windows kernel and protected-mode networking functions are
    already loaded.

    When NCSI is loaded this way, NCSI services are only available to Windows
    applications and are unavailable to virtual DOS sessions started from
    within Windows.  If only Windows applications are being used with NCSI
    within Windows this may be an acceptable way to load NCSI.  If a DOS
    session started from within Windows requires NCSI services also, start
    another instance of NCSI within the virtual DOS session itself giving NCSI
    the -W and -D command-line switches.  NCSI detects the presence of the
    Windows kernel and needs the -W switch to instruct NCSI to load.
    The -D command-line switch tells NCSI to use a dynamic socket so the
    newly loaded NCSI will not interfere with the already resident, but
    undetected NCSI loaded in WINSTART.BAT.

3.  Load NCSI in a DOS session by supplying the -W command-line switch.
    NCSI will only be available to THIS virtual DOS machine.  You will
    not be able to "see" NCSI from any DOS Window or from Windows
    itself. Be sure to release NCSI by using NCSI-REL and supplying it
    the -W command- line switch also before closing the DOS Window.

NOTE: When NCSI is used with NetBIOS, Vines, or IPX systems without a NetWare
file server, it may be a minute or more after NCSI is loaded before the
client can locate the server.  This time can be shortened by running CCONFIG
and increasing the frequency of the server broadcast.


If still having problems, contact NPC.  Unregistered shareware is supported
only via fax (818) 441-6894, our BBS (818) 441-6933, CIS mail 75300,1105, or
Internet e-mail at techsupport@networkproducts.com.



Network Products Corporation
1440 West Colorado Boulevard, Pasadena California USA 91105
Telephone 818-441-6504 FAX 818-441-6894
Technical Support 818-440-1973
BBS 818-441-6933


PRODUCT NAMES IN THIS DOCUMENT ARE THE TRADEMARKS OR REGISTERED TRADEMARKS OF
THEIR RESPECTIVE OWNERS.

NCSI IS A REGISTERED TRADEMARK OF NETWORK PRODUCTS CORPORATION.

WINDOWS IS A TRADEMARK OF MICROSOFT CORP.