THE TCP/IP STACK PROVIDED WITH 5PM TERM 3.x FOR WINDOWS
PART II
-----------------------------------------------------------
COEXISTENCE OF OUR TCP/IP STACK AND OTHER NETWORKS
----------------------------------------------------

Our TCP/IP Stack can be used concurrently with other
network software on the same PC, although the sequence
of loading of the drivers can be important.

Since our stack useds Novell's ODI driver standard, 
concurrent operation of our stack and other networks is
easiest to configure if they also use ODI.  Our stack is also
compatible to network software which does not run
under ODI, but in this case you nearly always need
to install seperate network cards.

The ODI driver architecture allows you to run more than
one protocol on a single network card, as long as the
protocols are different.  ODI also allows you to run
the same protocol on more than one network card in the
same PC.

To configure for 2 protocol types, they must each
be in the NET.CFG file.  Remember to make sure
that all protocols access the same NET.CFG file.

The following paragraphs describe some of the more
popular network types which can coexist successfully
on the same PC with our stack.

-------------------------------------------------------
OUR TCP/IP STACK AND MS WINDOWS 3.1 General Information
-------------------------------------------------------
If you want to use our stack together with Windows
3.x, to prevent conflicts you must exclude the 
network card's shared memory from the memory
available to Windows and the EMM386 driver.  Not all
cards need this.  If the card has MEMSIZE and BASE
MEMORY ADDRESS configured, then this should be done.
This can be done with an entry similar to the following
in your Windows configuration file, located in
your windows directory, called SYSTEM.INI:

	[386Enh]
	EMMExclude=d000-d3ff

This implies that for your network card parameters
you had (in your .ins file) the following parameters
set:
	MEM (base memory address)
	d000

	MEMSIZE (memory size)
	1024


ALSO NOTE that in all cases, the WIN.INI file should have
the following in the PCShare section:  (This is done in the installer)

[PCShare]
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0
....
See below for the rest of the requirements


ALSO NOTE that in cases where you are running WfW 3.11,
you need to include the odihlp.exe in your startnet.bat file!


-------------------------------------------------
OUR TCP/IP STACK AND 
--WINDOWS 3.1 WITHOUT Networks
or 
--Windows for Workgroups 3.11 WITHOUT Peer-to-Peer
networking and WITHOUT Networking 
-------------------------------------------------
The only special configuration to do is done by
the installer.  This is to modify the system.ini file.
The installer will create a backup of this file called
system.asc.

In the [boot] section, you will need the following 
entry:
SYSTEM.INI file
[boot]
network.drv=pcshare.dll
...

WIN.INI file
[PCShare]
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0

--------------------------------------------
OUR TCP/IP STACK AND 
--Windows 3.1 WITH NOVELL NETWARE 3.x/4.x
--------------------------------------------
You will need to adapt the starnet.bat file
to load the Novell components, as described
below:

Novell's IPXODI.COM and NETX.COM drivers
are not provided with our stack.  You should
have these with your novell installation.
In order to make the Netware connection, you
only need to load these two drivers before
loading the pcs_odi.exe.
Your startnet.bat file with look like:

set PCSHARE=c:\5pm\conn
c:\5pm\conn\lsl.com
c:\5pm\conn\ne2000.com
c:\5pm\conn\ipxodi.com
c:\5pm\conn\netx.com
c:\5pm\conn\pcs_odi.com

In order to run our stack and NETBIOS 
concurrently, you need to replace the netx.com
with netbios.exe.

The files SYSTEM.INI and WIN.INI will be modified
in the installer as follows:

system.ini file
   [boot]
   network.drv=pcsmux.dll

win.ini file
   [PCShare]
   network.0=netware.drv   ; This must be first
   network.1=pcshare.dll
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0


------------------------------------------------
OUR TCP/IP STACK AND 
--WINDOWS FOR WORKGROUPS 3.11 with peer-to-peer
AND WITH networking like Novell Netware
------------------------------------------------
Your startnet.bat file with look like:

set PCSHARE=c:\5pm\conn
c:\5pm\conn\lsl.com
c:\5pm\conn\ne2000.com
c:\5pm\conn\ipxodi.com
c:\5pm\conn\netx.com
c:\5pm\conn\pcs_odi.com
odihlp.exe  ; This should be in your windows directory

SYSTEM.INI file
[boot]
   network.drv=wfwnet.drv
   secondnet.drv=pcsmux.dll

WIN.INI file
[PCShare]
   network.0=netware.drv  ; this must be first
   network.1=pcshare.dll 
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0


------------------------------------------------
OUR TCP/IP STACK AND 
--WINDOWS FOR WORKGROUPS 3.11 WITHOUT peer-to-peer
AND WITH networking like Novell Netware
------------------------------------------------
Your startnet.bat file with look like:

set PCSHARE=c:\5pm\conn
c:\5pm\conn\lsl.com
c:\5pm\conn\ne2000.com
c:\5pm\conn\ipxodi.com
c:\5pm\conn\netx.com
c:\5pm\conn\pcs_odi.com
odihlp.exe  ; This should be in your windows directory

SYSTEM.INI file
[boot]
   network.drv=pcsmux.dll

WIN.INI file
[PCShare]
   network.0=netware.drv  ; this must be first
   network.1=pcshare.dll 
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0
   

------------------------------------------------
OUR TCP/IP STACK AND 
--WINDOWS FOR WORKGROUPS 3.11 with peer-to-peer
AND WITHOUT networking
------------------------------------------------
Windows for Workgroups (WfW) includes peer-to-peer
file sharing and printer sharing technology which
does not require the use of other networking
software such as Novell Netware or others.
Its networking performance is suitable for 
small workgroups only, and the data throughput
can be compared with that offered by Netware Lite.
WfW uses a combination of the NETBEUI and IPX
protocols, whereas our stack uses TCP/IP.

WfW is compatible with our stack with the exception
of the WfW peer-to-peer sharing option.  It is not
necessary to install the WfW peer-to-peer sharing
option to use WinWord, Microsoft Schedule or Microsoft
Mail, since they are all file-based.  However, it is
needed for Calendar.

Our TCP/IP stack should offer much higher performance
for medium and large workgroups, in which case you may
decide not to install the WfW peer-to-peer sharing 
option at all, and use the central fileserver
arrangement instead.  This also has the advantage of
allowing a central data backup.

Nonetheless, since WfW also supports Novell's ODI
driver standard, WfW peer-to-peer sharing can be used
concurrently with our stack if required.  This is not
the case with WfW 3.1, where the peer-to-peer sharing 
only supports Microsoft's competing NDIS driver 
standard.

If you want to use WfW 3.11 peer-to-peer sharing with
our Stack, you need to edit the WfW installation manually,
as described below.

A) Install both WfW and our TCP/IP Stack.  

B) Disable Windows networking as follows: click the "Networks" 
button in the "Network setup" and check "No Windows Support 
for networks".

C)Then configure WfW to use ODI networking as follows:

1) Check whether your net.cfg file has at least the 
following lines in the Link Driver section
and modify it with an editor like notepad if necessary:

Link Driver SMC8000  ; your ethernet adapter name
	PORT 280
	MEM  D000
	FRAME ETHERNET_802.3
	FRAME ETHERNET_II
	PROTOCOL TCP/IP 800 ETHERNET_II
	PROTOCOL ARP/IP 806 ETHERNET_II
	PROTOCOL IPX 0 ETHERNET_802.3

2) Add a line similar to the following to the end of 
your startnet.bat file:

	c:\win311\odihlp.exe 
This is asssuming your windows directory is called win311.

3) Remove any reference to the NDIS or WfW 3.11 network
driver from the config.sys file.

4) Create or edit your protocol.ini file to be identical to
the following:  (This file is in your windows directory)
(Assuming you have an SM8000 ethernet card...)

[network.setup]
version=0x3110
netcard=ms$w13ep,1,MS$W13EP,4  ; This depends on your ethernet card!
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$w13ep,1,ms$netbeui   
lana1=ms$w13ep,1,ms$nwlinknb    ; This depends on your ethernet card!


[net.cfg]
PATH=c:\5pm\conn\net.cfg

[MS$W13EP]

[Link Driver SMC8000]    ; This depends on your ethernet card!
data=Frame Ethernet_II
data=Frame Ethernet_802.3
data=Link Driver SMC8000

[NWLINK]


BINDINGS=SMC8000         ; This depends on your ethernet card!

[NETBEUI]
BINDINGS=SMC8000         ; This depends on your ethernet card!
LANABASE=0


5) Make sure that the "boot" , "boot.description" and
"386Enh" sections in the system.ini file contain the
following entries:

[boot]
network.drv=wfwnet.drv
secondnet.drv=pcshare.dll

[boot.description]
network.drv=Microsoft Windows Network (ver. 3.11)
secondnet.drv=PCShare 2.0.0

[386Enh]
network=*vnetbios, *vwc, vnetsup.386, vserver.386
netmisc=ndis.386, msodisup.386
transport=nwlink.386, nwnblink.386, netbeui.386

6) Make sure that your win.ini file has the 
following entry:

[PCShare]
   nopcdll=1
   netwarn=0
   askpasswd=0
   startmsg=0


--------------------------------------------
OUR TCP/IP STACK AND NOVELL NETWARE LITE
--------------------------------------------
Please make sure that you only have one
net.cfg file for both our stack and Netware
lite.  Make sure you have both entries for
the Netware and our tcp/ip stack.
See above for any other configuration stuff.

