==============================================================================

Notes on upgrading to IPX/SPX ODI drivers
Notes on NET.CFG file for IPX/SPX ODI drivers.
Notes on NET.CFG file for LAN WORKPLACE for DOS ODI drivers
Notes on LAN Manager 2.1 FDOS 2.6.E (NetWare Connectivity)
Notes on LAN Manager 2.1 FDOS 2.6.E (No NetWare Connectivity)
Notes on LAN Manager 2.1, 2.6.D, Ethernet (No NetWare Connectivity)
Notes on LAN Manager 2.1, 2.6.D, Token-Ring (No NetWare Connectivity)
Notes on LAN Manager 2.0 FDOS 2.6.D or 2.6.E, Ethernet
Notes on LAN Manager 2.0 FDOS 2.6.D, Token-Ring
Notes on DEC Pathworks for DOS (NetWare Coexistence)
Notes on Banyan Vines
Notes on IBM LAN Server 
Notes on Other Token-Ring NICs and LAN Support Program
Notes on Ethernet Encapsulation 

==============================================================================

Subject:  Notes on upgrading to IPX/SPX ODI drivers

Summary:

WBS/WFD users who are upgrading to WBS/WFD 3.0 release that have 
ODI drivers installed as a result of the SETUP process no longer 
need the monolithic IPX/SPX driver (IPXXNS.COM).  The SETUP 
program may not remove the previous IPXXNS.COM line from the
AUTOEXEC.BAT file.  If the NetWare Operating system was chosen, it is 
likely that an extra NET?.COM line is written in the AUTOEXEC.BAT file.

Procedure:

If NET?.COM appears twice delete one of the lines in the 
AUTOEXEC.BAT file:

   NET?.COM      where ? = 3 for DOS 3
                           4 for DOS 4
                           5 for DOS 5
                           x for any DOS version

Otherwise delete IPXXNS.COM.

------------------------------------------------------------------------------


Subject:  Notes on NET.CFG file for IPX/SPX ODI drivers

Summary:

SETUP provides a NET.CFG for IPX/SPX ODI driver configurations.  The
NET.CFG file contains a driver name, frame specification, and
protocol specification.   This is all that is needed for many Network
Interface Cards (NICs).  Some NICs require parameters to be added to
the NET.CFG file.  These additional parameters specify the NIC
settings such as interrupt level, port address, etc.

Procedure:

The parameter settings for cards requiring additional parameters
differ depending on the NIC being used.  The user should refer to
the NIC manufacturer's documentation to determine if additional
parameters are required and if so, modify the NET.CFG file. Do not
change the location of the NET.CFG file.

An example showing the procedure for the 3C503 card follows:

The NET.CFG for the 3C503 produced by SETUP with encapsulation selection
of 8137 follows:

        LINK DRIVER 3C503
           FRAME ETHERNET_II
           PROTOCOL IPX 8137 FRAME ETHERNET_II

The NET.CFG should be modified as follows:

        LINK DRIVER 3C503   
           INT #1 3
           PORT #1 300
           MEM #1 C8000
           FRAME ETHERNET_II         
           PROTOCOL IPX 8137 FRAME ETHERNET_II


------------------------------------------------------------------------------

Subject:  Notes on NET.CFG file for LAN WORKPLACE for DOS ODI drivers

Summary:

SETUP provides a NET.CFG for LAN WORKPLACE for DOS ODI driver 
configurations.  The NET.CFG file contains a driver name, frame
specification, buffers specification, and protocol specification.   
This is all that is needed for many Network Interface Cards (NICs). 
Some NICs require parameters to be added to the NET.CFG file.  These
additional parameters specify the NIC settings such as interrupt
level, port address, etc.

Procedure:

The parameter settings for cards requiring additional parameters
differ depending on the NIC being used.  The user should refer to
the NIC manufacturer's documentation to determine if additional
parameters are required and if so, modify the NET.CFG file. Do not
change the location of the NET.CFG file.

The NET.CFG for the 3C503 produced by SETUP follows:

        LINK DRIVER 3C503
           FRAME ETHERNET_II

        LINK SUPPORT
          Buffers 8 1586
          MemPool 4096

        PROTOCOL TCPIP
          ip_address	 197.0.0.76
          ip_router      0.0.0.0
          ip_netmask     0.0.0.0
          tcp_sockets	 8
          udp_sockets	 8
          raw_sockets    1


The NET.CFG should be modified to look as follows:

        LINK DRIVER 3C503   
           INT #1 3
           PORT #1 300
           MEM #1 C8000
           FRAME ETHERNET_II         

        LINK SUPPORT
          Buffers 8 1586
          MemPool 4096

        PROTOCOL TCPIP
          ip_address	 197.0.0.76
          ip_router      0.0.0.0
          ip_netmask     0.0.0.0
          tcp_sockets	 8
          udp_sockets	 8
          raw_sockets    1

NOTE: The ip_address, ip_router and ip_netmask parameters are 
input to the SETUP program.

------------------------------------------------------------------------------

Subject:  Notes on LAN Manager 2.1 FDOS 2.6.E (NetWare Connectivity)

Summary:

The IPX.COM generated by the LAN Manager NetWare Connectivity
procedure might need to be ECONFIGED (See Novell NetWare Manuals for
information on this process) to access the FileNet server.  For
additional information see the section "Notes on Ethernet
Encapsulation".

------------------------------------------------------------------------------

Subject: Notes on LAN Manager 2.1, FDOS 2.6.E (No NetWare Connectivity)

Summary:

After the WorkFlo Business System SETUP program has been run, the
configuration steps to enable FileNet applications to communicate
with the LAN Manager configuration are nearly complete.  You must now
update your PROTOCOL.INI file with the following information:

Procedure:    

Add the [IPX_XIF] section to the PROTOCOL.INI file as shown below:

[PROTMAN]
  DRIVERNAME = PROTMAN$
  DYNAMIC = YES
  PRIORITY = NETBEUI

[NETBEUI_XIF]
  Drivername = netbeui$
  SESSIONS = 6
  NCBS = 12
  BINDINGS = "ELNKMC_NIF"
  LANABASE = 0

[IPX_XIF]
   Drivername = IPX$
   LOAD = IPXMARK[U],IPX[U]
   UNLOAD = IPXREL[C]
  BINDINGS = "ELNKMC_NIF"

[ELNKMC_NIF]
;
;   3C523 3Com EtherLink /MC adapter
;
    DRIVERNAME = ELNKMC$
;       2nd driver name = ELNKMC2$
;   MAXTRANSMITS = 40
;       number of transmit queue elements (optional, default = 12)
;       Min = 8, Max = 50
;       Use the default for DOS and normal OS/2 clients
;       Set MAXTRANSMITS = 40 for OS/2 servers
;   NETADDRESS = "02608C123456"
;       network address (optional, default = network adapter PROM value)
;       the network address is 12 hex digits enclosed in quotes
;   SLOTNUMBER = 4
;       Microchannel slot number (optional, default = scan for adapter)
;       Min = 1, Max = 8
;       This parameter is needed to install the 2nd adapter in a higher
;       slot number

If you have done all of the above, then you should be able to attach
to a FileNet Server from your workstation.
               

Note: The NDIS compatible version of IPX/SPX is part of the LAN Manager
2.1 product.

------------------------------------------------------------------------------

Subject: Notes on LAN Manager 2.1, 2.6.D, Ethernet (No NetWare Connectivity)

Summary:

After the WorkFlo Business System SETUP program has been run, the
configuration steps to enable FileNet applications to communicate
with the LAN Manager configuration are nearly complete.  You must now
update your PROTOCOL.INI file with the following information:

Procedure:    

Add the [IPX_XIF] section to the PROTOCOL.INI file as shown below:

[PROTMAN]
  DRIVERNAME = PROTMAN$
  DYNAMIC = YES
  PRIORITY = NETBEUI

[NETBEUI_XIF]
  Drivername = netbeui$
  SESSIONS = 6
  NCBS = 12
  BINDINGS = "ELNKMC_NIF"
  LANABASE = 0

[IPX_XIF]
   Drivername = IPX$
   LOAD = IPXMARK[U],IPX[U]
   UNLOAD = IPXREL[C]
  BINDINGS = "ELNKMC_NIF"

[ELNKMC_NIF]
;
;   3C523 3Com EtherLink /MC adapter
;
    DRIVERNAME = ELNKMC$
;       2nd driver name = ELNKMC2$
;   MAXTRANSMITS = 40
;       number of transmit queue elements (optional, default = 12)
;       Min = 8, Max = 50
;       Use the default for DOS and normal OS/2 clients
;       Set MAXTRANSMITS = 40 for OS/2 servers
;   NETADDRESS = "02608C123456"
;       network address (optional, default = network adapter PROM value)
;       the network address is 12 hex digits enclosed in quotes
;   SLOTNUMBER = 4
;       Microchannel slot number (optional, default = scan for adapter)
;       Min = 1, Max = 8
;       This parameter is needed to install the 2nd adapter in a higher
;       slot number

If you have done all of the above, then you should be able to attach
to a FileNet Server from your workstation.
               

Note: The NDIS compatible version of IPX/SPX is part of the LAN Manager
2.1 product.

------------------------------------------------------------------------------

Subject: Notes on LAN Manager 2.1, 2.6.D, Token-Ring (No NetWare Connectivity)

Summary:      

After the WorkFlo Business System SETUP program has been run, the
configuration steps to enable FileNet applications to communicate
with the LAN Manager configuration are nearly complete. 

Procedure: 

You must add the [IPX_XIF] section shown below to your PROTOCOL.INI.
Your PROTOCOL.INI file should look similar to the PROTOCOL.INI 
below taking into account the adapter card installed on your PC.

[PROTMAN]
  DRIVERNAME = PROTMAN$
  DYNAMIC = YES
  PRIORITY = NETBEUI

[NETBEUI_XIF]
  Drivername = netbeui$
  SESSIONS = 6
  NCBS = 12
  BINDINGS = "IBMTOKA_NIF"
  LANABASE = 0

[IPX_XIF]
   Drivername = IPX$
   LOAD = IPXMARK[U],IPX[U]
   UNLOAD = IPXREL[C]
   BINDINGS = "WEDGE"

[WEDGE]
   Drivername = NWEDGE$
   BINDINGS = "IBMTOKA_NIF"

[IBMTOKA_NIF]

; protocol.ini section for the IBM Token-Ring Adapter
   drivername = IBMTOK$

If you have done all of the above, then you should be able to attach 
to a FileNet Server from your workstation.
               

Note: The NDIS compatible version of IPX/SPX is part of the LAN Manager
2.1 product.


------------------------------------------------------------------------------

Subject: Notes on LAN Manager 2.0 FDOS 2.6.D or 2.6.E, Ethernet

Summary:  

After the WorkFlo Business System SETUP program has been run, the
configuration steps to enable FileNet applications to communicate
with the LAN Manager configuration are nearly complete.  You must now
update your PROTOCOL.INI file with the following information:

Procedure:    

Add the following to your PROTOCOL.INI file:

[PROTOCOL MANAGER]
  DRIVERNAME = PROTMAN$

[NETBEUI_XIF]
  Drivername = netbeui$
  BINDINGS = "ELNKMC_NIF"

[ELNKMC_NIF]
  DRIVERNAME = elnkmc$

[IPX]
  DRIVERNAME= IPX$
  BINDINGS= "ELNKMC_NIF"


If you have done all of the above, then you should be able to attach
to a FileNet Server from your workstation.
               

Note: the 3COM 3+Open for NetWare is needed to generate an NDIS 
compatible version of IPX/SPX.  

------------------------------------------------------------------------------

Subject: Notes on LAN Manager 2.0 FDOS 2.6.D, Token-Ring

Summary:      

After the WorkFlo Business System SETUP program has been run, the
configuration steps to enable FileNet applications to communicate
with the LAN Manager configuration are nearly complete.  You must now
update your PROTOCOL.INI file with the following information:

Procedure: 

Make sure the following is contained in your PROTOCOL.INI file:

[PROTOCOL MANAGER]
  DRIVERNAME = PROTMAN$

[NETBEUI_XIF]
  Drivername = netbeui$
  BINDINGS = "IBMTOKA_NIF"

[IBMTOKA_NIF]
  Drivername = IBMTOK$

[IPX]
  DRIVERNAME= IPX$
  BINDINGS= "WEDGE"

[WEDGE]
  DRIVERNAME= NWEDGE$
  BINDINGS= "IBMTOKA_NIF"


If you have done all of the above, then you should be able to attach 
to a FileNet Server from your workstation.
               

Note: the 3COM 3+Open for NetWare is needed to generate an NDIS 
compatible version of IPX/SPX.


------------------------------------------------------------------------------

Subject:  Notes on DEC Pathworks for DOS

Summary:

DEC Pathworks for DOS (NetWare Coexistence) lets Novell IPX/SPX
software and Pathworks for DOS software operate together on the same
PC.  Pathworks for DOS (NetWare Coexistence) and Novell IPX/SPX
coexist by using drivers that comply with the Network Driver
Interface Specification (NDIS).  PCs in the DECNET environment use
the IPX/SPX software to access FileNet services.

PC workstations that use DEC Pathworks for DOS (NetWare Coexistence)
to access NetWare servers may require modification to the IPX.COM
generated by DEC Pathworks.  The IPX.COM might need to be ECONFIGED
(see Novell NetWare manuals for information on this process) to
enable access to FileNet services.  For additional information, see
the section "Notes on Ethernet Encapsulation."

If DEC Pathworks for DOS (NetWare Coexistence) is not used to access
NetWare Servers, follow the procedure described below.

Procedure:

To use the Pathworks for DOS (NetWare Coexistence) DEC Pathworks for
DOS must be configured to support NDIS.  During the Pathworks for DOS
installation type "OTHER" as the response to "Select Ethernet
Controller Type".

Refer to Pathworks for DOS (NetWare Coexistence) Installation and
Configuration Guide for instructions on how to install the DEC
Pathworks for DOS (NetWare Coexistence).  Skip the section
"Creating the IPX driver," as it requires the SHGEN utility to
generate the IPX.COM driver.  Instead, use the IPX.COM driver placed
in the FILENET\NETWORK directory by the FileNet SETUP program.

A sample PROTOCOL.INI for a PC workstation residing on Ethernet 
and using the DEC Pathworks (NetWare Coexistence) follows:

   ; PROTOCOL.INI file create by DECNET.OMO V4.0.17
   ;                         via DECNET.WIK V4.0.26

          [protocol manager]
           DRIVERNAME = PROTMAN$

          [IPX4MAC]
           DRIVER = IPX$MAC
           BINDINGS = ELNKII.SYS   ;example of using the 3C503 interface
           
          [DATALINK]
           DRIVERNAME  = DLL$MAC
           LG_BUFFERS  = 16
           SM_BUFFERS  = 6
           OUTSTANDING = 32
           HEURISTICS  = 0
           BINDINGS    = ELNKII.SYS   ;example of using the 3C503 interface
           ;Specify IRQ level used by workstations network adapter
           ;NI_IRQ      = 5

          [ELNKII.SYS]
           DRIVERNAME = ELNKII$
           DMACHANNEL = 1
           IOADDRESS = 0X2e0
           INTERRUPT = 5
           MAXTRANSMITS = 8
           TRANSCEIVER = EXTERNAL
    
Note:  If you intend to use Archive or save a queue definition, perform the
following steps:

1. Edit LOGON.CFG to change the DataPacketSize line in the [Network]
section as follows:

DataPacketSize=512

2. Edit the file cor_config on the root server in either /usr/local/sd
(FDOS server) or /fnsw/local/sd (Series 6000 server) to change the 
packet size to 512.


------------------------------------------------------------------------------

Subject:  Notes on Banyan Vines

Summary:

Banyan Vines 4.1 provides an NDIS version 2.0 compatible network
environment.  In order to access FileNet servers, a Novell IPX/SPX
protocol stack is required.  Various third party software vendors
offer NDIS IPX/SPX protocol stacks.  FileNet has tested one of these
stacks from Spry Corporation called SPRY 2.0 IPX/NDIS Concurrent
software.

Note: Banyan Vines currently does not support multiple protocol stacks 
for the NDIS network environment on Token-Ring.

Procedure:

Users should refer to documentation from Banyan Vines and the third
party software vendor for instructions on how to install the NDIS
IPX/SPX protocol stack.  A sample PROTOCOL.INI for a PC workstation 
residing on Ethernet and utilizing the SPRY NDIS IPX/SPX follows:

   [protocol manager]
    DRIVERNAME = PROTMAN$

   [SPRY CONCURRENT]
    DRIVERNAME = SPRY$CONCURRENT
    BINDINGS = "ETHERLINK"
   
   [VINES_XIF]
    DRIVERNAME = NDISBAN$
    BINDINGS = "ETHERLINK"

   [ETHERLINK]
    DRIVERNAME = ELNKII$
    DMACHANNEL = 1
    IOADDRESS = 0x2e0
    INERRRUPT = 5
    MAXTRANSMITS = 8
    TRANSCEIVER = EXTERNAL


------------------------------------------------------------------------------

Subject:  Notes on IBM LAN Server 

Summary:

The IBM LAN Server requires the IBM LAN Support program or compatible
software to access an IBM LAN Server.  If a network adapter of Other
was chosen during the SETUP process, modifications need to be made to
configuration files.  See "Notes on Other Token-Ring NICs and LAN
Support Program."


------------------------------------------------------------------------------

Subject:  Notes on Other Token-Ring NICs and LAN Support Program

Summary:

Workstation configurations that include an "Other" Token-Ring card 
and the LAN Support driver option require card-specific modifications
to the CONFIG.SYS file.  The workstation also requires software
compatible with IBM LAN Support Program supplied by the network-card
manufacturer.  The SETUP program provides an ODI-driver LANSUP.COM
that interfaces network cards that are compatible with LAN Support
Program interface.


------------------------------------------------------------------------------

Subject:  Notes on Ethernet Encapsulation 

Summary:

There are two basic types of Ethernet encapsulation,  Ethernet 
Version II and IEEE 802.3.  Ethernet II includes a protocol 
identifier field.  The protocol identifier field value assigned 
to Novell is 8137 and the value assigned to XNS is 0600.  

FileNet FDOS releases prior to 2.6.E are able to recognize only
Ethernet II 0600 packets.  FileNet FDOS releases from 2.6.E and later
and can accept both Ethernet II 8137 and 0600 types.  

SETUP assigns 8137 as the type to these servers, because 8137 is
compatible with most routers and NetWare Servers.  If the workstation
is configured to use 802.3 encapsulation, a router must convert the 
encapsulation to Ethernet II.


------------------------------------------------------------------------------

