home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Spezial
/
SPEZIAL2_97.zip
/
SPEZIAL2_97.iso
/
ANWEND
/
ONLINE
/
TE2_134T
/
te2inst.001
/
ReadMe.TCP
< prev
next >
Wrap
Text File
|
1997-07-03
|
3KB
|
64 lines
TE/2 Version 1.34
TCP/IP Support DLLs
4 July, 1997
Oberon Software, Inc.
1405 East Main St
Mankato, MN 56001-5070
Voice: 507-388-7001
Fax: 507-388-7568
BBS: 507-388-1154
Using the TCP/IP Support DLLS
-----------------------------
Once you have installed a version of OBTCPIP.DLL onto your system, you
may now use TE/2 to connect with a TCP/IP socket as well as with a COM
port or a Named Pipe. To accomplish this, you must edit your TE2.INI
and change the "Device" statement.
To designate a socket the first seven characters of the Device setting
MUST be "AF_INET" (upper or lower case). The very next character after
this flag is important in that it defines a delimiter which will be
used in the remainder of the Device designation. It can be any character
which does not otherwise appear in your HOST or SOCKET name. A good choice
would be the slash ("/") character.
Next is your HOST name or address. This can be a standard internet
address (123.123.123.123) or a name as defined to your protocol
installation (i.e., in your HOSTS file). This is followed by the delimiter
again.
Next is the socket designation which can be either a simple numeric value
(i.e., 23) or a "well known port" specification as definied in your
SERVICES file (i.e., telnet). In the latter case, the port name MUST
be followed by another delimiter and the letters "tcp".
Several examples will hopefully make this seem less intimidating:
1. AF_INET/server/2000
2. AF_INET!30.96.92.1!login!tcp
3. AF_INET,joehost,telnet,tcp
Notice that each uses a different delimiter character but each uses that
delimiter consistantly throughout. #1 uses a slash, #2 uses an exclamation
point, and #3 uses a comma. #1 and #3 connect to named servers whereas
#2 specifies an internet address for the host. #1 connects to a socket
with a hardcoded port number and #2 and #3 use "well know ports".
TE/2 as a Telnet Client
-----------------------
If you are going to be using TE/2 as Client, you should enable the "Telnet"
keyword in TE2.INI when you change the "Device" statement. Setting
"Telnet" to TRUE will cause TE/2 to perform standard Telnet handshaking
with the server.
It has been our experience with the IBM TCP/IP TelnetD Telnet server, that
using VT100 emulation mode in TE/2 results in MUCH better performance
than does ANSI mode due to different screen painting algorithms used by
the server. Unfortunately one loses color in this situation, even though
TE/2 is fully able to do colors in VT100 mode, because the server does not
assume color capability in VT100s.