home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
dbox20c1.exe
/
DBOXC1.ZIP
/
DOC
/
readme.dbx
< prev
Wrap
Text File
|
1994-07-19
|
21KB
|
451 lines
TCP/IP 2.0 for OS/2 DOS/Windows Access Kit
This kit includes these APAR fixes from PTF UN50383
Corrective Service.
--------------------------------------------------------------------
1.0 Obtaining CSDs
You can obtain Corrective Service Diskettes (CSDs) electronically
by:
o Using FTP to access SOFTWARE.WATSON.IBM.COM as Anonymous.
NOTE: Fixes for TCP/IP for OS/2 are located in the
pub\tcpip\os2 directory.
o Establishing a modem connection to the NCSBBS bulletin
board at 1-919-517-0001.
NOTE: Set your modem settings to: none,8,1.
The latest CSDs for TCP/IP Version 2.0 for OS/2 are shown in the
following table:
+---------------------------+---------------------------+
| KIT NAME | PACKAGE NAME |
+---------------------------+---------------------------+
| Applications Kit | APP20CSD.PKG |
+---------------------------+---------------------------+
| Base Kit | TCP20CSD.PKG |
+---------------------------+---------------------------+
| Domain Name Server Kit | DNS20CSD.PKG |
+---------------------------+---------------------------+
| DOS/Windows Access Kit | DOS20CSD.PKG |
+---------------------------+---------------------------+
| Extended Networking Kit | XNT20CSD.PKG |
+---------------------------+---------------------------+
| Network File System Kit | NFS20CSD.PKG |
+---------------------------+---------------------------+
| Programmer's Tool Kit | PGM20CSD.PKG |
+---------------------------+---------------------------+
| X Window System Client | XCL20CSD.PKG |
| Kit | |
+---------------------------+---------------------------+
| X Window System Server | PMX20CSD.PKG |
| Kit | |
+---------------------------+---------------------------+
This README file reflects new and changed functions for
the TCP/IP 2.0 for OS/2: DOS/Windows Access kit, and
documents changes introduced in the original product
as well as changes due to Corrective Service Diskette
(CSD) UN50383.
This file contains information you will need after you install
the DOS/Windows Access Kit. It contains a brief description
of the kit, the software requirements, and information you
will need to configure and use the kit.
The order of information in this file is:
1. What is the DOS/Windows Access Kit?
2. Software requirements
3. What does the DOS/Windows Access Kit support?
4. The ETC environment variable.
5. Name resolution
6. Coexistence with TCP/IP Version 2.1 for DOS
7. COMTCP
8. Tracing
1. What is the DOS/Windows Access Kit?
The DOS/Windows Access Kit is a virtual device driver and a
set of TCP/IP Version 2.1 for DOS programs and dynamic link
libraries. After you install this kit, you can run selected
TCP/IP Version 2.1 for DOS applications in an OS/2 V2.1
Virtual DOS Machine (VDM), including a WINOS2 session. This
kit also lets you run DOS and Windows applications written to
any of the documented TCP/IP Version 2.1 for DOS APIs.
2. Software requirements
The TCP/IP Version 2.0 for OS/2 DOS/Windows Access Kit
requires OS/2 V2.1.
If you want to run Windows applications written to any of the
TCP/IP Version 2.1 for DOS APIs, then you must also install
the Windows support provided with OS/2 V2.1.
3. What does the DOS/Windows Access Kit support?
This section describes what is supported by the DOS/Windows
Access Kit, as well as any restrictions that apply.
Supported TCP/IP Version 2.1 for DOS APIs
-----------------------------------------
The following list shows the TCP/IP Version 2.1 for DOS
application programming interfaces that are supported by the
DOS/Windows Access Kit. Any application written to these
libraries will run in an OS/2 V2.1 VDM.
Library Description
------- -----------
SOCKETS.LIB Real mode small model sockets library
SOCKETL.LIB Real mode large model sockets library
RPCS.LIB SUN RPC small model library
RPCL.LIB SUN RPC large model library
FTPAPI.LIB FTP Application Programming Interface
library
WINSOCK.LIB Windows Sockets API V1.1 library
WFTPAPI.LIB Windows FTP Application Programming
Interface library
BIOS int14h BIOS Interrupt 14 Telnet
Redirector (see COMTCP below).
NOTE: For more information on TCP/IP Version 2.1 for DOS
application programming interfaces, see "TCP/IP Version 2.1
for DOS: Programmer's Reference," SC31-7046.
Restrictions
------------
Although the DOS/Windows Access Kit supports all of the
documented TCP/IP Version 2.1 for DOS APIs, there are some
applications, shipped with TCP/IP Version 2.1 for DOS, that
are not supported by the DOS/Windows Access Kit because they
manage the DOS TCP/IP protocol stack (INET). Because the
DOS/Windows Access Kit lets you run on the OS/2 TCP/IP stack,
there is no DOS stack to manage. The following table lists
DOS TCP/IP applications that are not supported in a VDM, and
the corresponding (suggested) OS/2 TCP/IP applications:
DOS OS/2
Application Application Description
----------- ----------- ------------
ifconfig ifconfig Used to manage network interfaces.
arp arp Used to manage ARP table entries.
netstat netstat Used to query internal structures.
route route Used to manage static routes.
routed routed RIP support.
snmpd snmpd SNMP Agent support.
inet -d <flg> vdebug <flg> Internal protocol stack tracing.
4. The ETC environment variable
Both OS/2 and DOS TCP/IP applications use the ETC environment
variable to find the path to the TCP/IP configuration and name
resolution files. The OS/2 TCP/IP installation program
initializes the ETC variable by creating an entry like this in
CONFIG.SYS, on the boot drive:
SET ETC=<path>\ETC
The DOS/Windows Access Kit initializes the ETC variable by
creating an entry like this in in the AUTOEXEC.BAT file on
your boot drive:
SET ETC=<path>\DOS\ETC
The two different directories are used because some files have
different formats in OS/2 and DOS systems.
When you install the DOS/Windows Access Kit, the following
files are stored in the <path>\DOS\ETC directory.
File Description
---- -----------
RESOLV Domain Name Server name resolution
HOSTS HOSTS file name resolution
SERVICES Service name to port number mapping
PROTOCOL Protocol name to protocol ID mapping
5. Name resolution
The DOS TCP/IP programming interfaces use name resolution
files like those used by OS/2 TCP/IP. These files are:
File Description
---- -----------
RESOLV Domain Name Server name resolution
HOSTS HOSTS file name resolution
When you install the DOS/Windows Access Kit, the installation
program sets the ETC environment variable (in the AUTOEXEC.BAT
file on the boot drive) to the directory that contains the
name resolution files. This is usually the <path>\DOS\ETC
subdirectory. If you change the ETC path in AUTOEXEC.BAT, or
if you would like to use a HOSTS file, you must update one or
both of the RESOLV and HOSTS files pointed to by the ETC path
in AUTOEXEC.BAT. In most cases, you can just copy the
corresponding files from the ETC path specified in CONFIG.SYS
to the ETC path specified in AUTOEXEC.BAT.
If you do NOT modify the ETC environment variable in
AUTOEXEC.BAT (to point to a path other than the path set
during installation), the configuration notebook (TCPIPCFG)
will update the RESOLV file when you change the configuration
notebook pages that correspond to the RESOLV file. The
configuration program does this by copying the RESOLV file
from the ETC path specified in CONFIG.SYS to the ETC path
specified in AUTOEXEC.BAT after it makes any changes.
6. Coexistence with TCP/IP Version 2.1 for DOS
You can use the DOS/Windows Access Kit to run TCP/IP Version
2.1 for DOS applications in an OS/2 virtual DOS machine (VDM).
Because TCP/IP Version 2.1 for DOS does not have a separate
Applications Kit, and because you don't run the OS/2 TCP/IP
stack and the DOS TCP/IP stack at the same time, there are
some considerations when you install and configure DOS TCP/IP
on an OS/2 machine using the DOS/Windows Access Kit.
1. The TCP/IP Version 2.0 for OS/2 DOS/Windows Access Kit is
available after the TCP/IP Version 2.1 for DOS CSD
2.1.0.3. If you are installing TCP/IP Version 2.1 for DOS
(CSD 2.1.0.3 or earlier) and the DOS/Windows Access Kit on
the same workstation and expect to run TCP/IP Version 2.1
for DOS applications in an OS/2 VDM, then you must replace
the following files from TCP/IP Version 2.1 for DOS with
the corresponding files from the DOS/Windows Access Kit:
Module Description
------ -----------
WINSOCK.DLL Windows Sockets API V1.0 and V1.1
support.
2. When running TCP/IP Version 2.1 for DOS in an OS/2 VDM,
you do not use the TCP/IP Version 2.1 for DOS stack nor
any of the DOS TCP/IP network interface support. Instead
you use the TCP/IP Version 2.0 for OS/2 stack and its
interfaces. For this reason you should not allow CUSTOM
(the TCP/IP Version 2.1 for DOS configuration program) to
modify your CONFIG.SYS file.
3. After installing both the DOS/Windows Access Kit and
TCP/IP Version 2.1 for DOS, you should modify the
AUTOEXEC.BAT on the boot drive to set the ETC environment
variable to the ETC directory that was created when you
installed TCP/IP Version 2.1 for DOS.
7. COMTCP
The COMTCP command lets you intercept BIOS Serial Port
Services Interrupt (int 14H) requests and redirect them over a
Transmission Control Protocol connection.
┌─ -c 1────────┐ ┌─ -p 23───────┐
>>──COMTCP──┬─────┬──┼──────────────┼──┼──────────────┼──────────>
└─ -o─┘ └─ -c com_port─┘ └─ -p tcp_port─┘
┌─ -t 3───────┐
>──┼─────────────┼── host── dos_command─────────────────────────><
└─ -t timeout─┘
COMTCP Help
>>──COMTCP──┬─ -?──┬────────────────────────────────────────────><
└─ -??─┘
Parameter Description
--------- -----------
-o Instructs COMTCP not to use the TELNET
protocol.
By default, COMTCP uses the TELNET protocol to
support initial option negotiation with the
host and to quote the TELNET command
character. When the TELNET protocol is turned
off, option negotiation is inhibited and all
bytes sent and received are passed by COMTCP
without being quoted. If this parameter is
omitted, COMTCP uses the TELNET protocol.
-C com_port Specifies the DOS communication port to
intercept. Valid port numbers are 1, 2, 3,
and 4, which correspond to communication
devices COM1, COM2, COM3, and COM4. The
default communication port is 1.
-P tcp_port Specifies a port (other than the default
TELNET port) associated with the connection.
The default TELNET port is 23.
host Specifies the name of the host or internet
address of the host with which you want to
establish a TELNET connection.
dos_command Specifies the command to be initiated when
TCP/IP is connected to the remote host. In
many instances the dos_command starts a
terminal emulator. Enter the dos_command as
you would from the DOS prompt.
-? Displays information about the COMTCP command.
-?? Displays detailed information about the COMTCP
command.
8. Tracing
The DOS/Windows Access Kit virtual device driver supports
tracing. The following instructions are supplied to help you
create a trace so that we can better service our product.
This facility is not intended for general use. The tracing
support has two possible output destination options. You can
route the trace output to an internal 64K buffer or to a COM
port. If you want to route the trace output to a COM port,
add the /C:n parameter to the "DEVICE=<dbox>\BIN\VDOSTCP.VDD"
statement that was added to the CONFIG.SYS file, on the boot
drive, when you installed the DOS/Windows Access Kit. This
parameter specifies the COM port to which trace output is
sent. The format of this parameter is:
/C:{1|2}
To specify that trace output is sent to the COM2 port, you
would enter the device statement like this:
DEVICE=<dbox>\BIN\VDOSTCP.VDD /C:2
Tracing with VDEBUG
-------------------
The DOS/Windows Access Kit contains the VDEBUG trace program.
You can use VDEBUG.EXE to set tracing on and off, and to dump
the current state of the internal trace buffer (if tracing to
the internal buffer). The VDEBUG parameters can be either a
series of flags separated by logical operators:
& and
| or
~ not
or you can specify the -d option to dump the internal trace
buffer.
Here are the flags and the traces they produce:
Flag Trace Description
---- ----- -----------
Tobuffer Sends trace output to the internal trace
buffer instead of a COM port
Kentry Traces TCP/IP Version 2.1 for DOS kernel
calls
Vsocket Traces calls from the virtual device
driver to the TCP/IP Version 2.0 for
OS/2 protocol stack
All Turns on all of the trace flags
NOTE: You need specify only enough characters to uniquely
identify a flag when passing parameters to VDEBUG.EXE. In the
list above, the characters necessary to uniquely identify a
flag are shown in uppercase.
TRACE EXAMPLES: The following table shows what is produced by
various combinations of trace options.
VDEBUG Parameters Trace Description
----------------- -----------------
all&~tobuffer Turns on all tracing, and sends the
output to the COM port specified on the
DEVICE=<dbox>\BIN\VDOSTCP.VDD statement
in the CONFIG.SYS.
vsocket|kentry Traces all calls from an OS/2 VDM to the
VDD, and calls from the VDD to the
TCP/IP Version 2.0 for OS/2 stack; Sends
trace output to the COM port specified
in config.sys.
k|t Traces all calls from an OS/2 VDM to the
VDD. Sends trace output to the internal
buffer where you can view it using the
vdebug -d command.
--------------------------------------------------------------------
APAR Fixes
The following is a list of APARs fixed in CSD UN57546.
+------------+-------------+---------------------------------------+
| PN45654 | VDOSTCP.VDD | Fixed: DOS BOX COMTCP transmits |
| | | before checking line status. |
+------------+-------------+---------------------------------------+
| PN46358 | COMTCP.EXE | Fixed: Customer cannot connect to |
| | WINSOCK.DLL | mail in the DOS box when using SUN |
| | | Select system. |
+------------+-------------+---------------------------------------+
| PN46944 | WINSOCK.DLL | Fixed: Customer cannot access INFO |
| | PING.EXE | application when accessing DOS box. |
| | WPING.EXE | |
| | DSKDBOX.TCP | |
+------------+-------------+---------------------------------------+
| PN48210 | PING.EXE | Fixed: WIN-OS/2 Memory corruption |
| | WPING.EXE | causing other WIN OS/2 components to |
| | DSKDBOX.TCP | trap. |
+------------+-------------+---------------------------------------+
| PN52335 | ASYNCSEL | Fixed: Cello does not work correctly. |
+------------+-------------+---------------------------------------+
| PN53497 | WPING.EXE | Fixed: WPING that ships with DOS |
| | | Box Access Kit receives General |
| | | Protection fault. |
+------------+-------------+---------------------------------------+
The following is a list of APARs fixed in CSD UN50383.
+------------+-------------+---------------------------------------+
| PN45654 | VDOSTCP.VDD | Fixed: DOS BOX COMTCP transmits |
| | | before checking line status. |
+------------+-------------+---------------------------------------+
| PN46358 | COMTCP.EXE | Fixed: Customer cannot connect to |
| | WINSOCK.DLL | mail in the DOS box when using SUN |
| | | Select system. |
+------------+-------------+---------------------------------------+
| PN46944 | WINSOCK.DLL | Fixed: Customer cannot access INFO |
| | PING.EXE | application when accessing DOS box. |
| | WPING.EXE | |
| | DSKDBOX.TCP | |
+------------+-------------+---------------------------------------+
| PN48210 | PING.EXE | Fixed: WIN-OS/2 Memory corruption |
| | WPING.EXE | causing other WIN OS/2 components to |
| | DSKDBOX.TCP | trap. |
+------------+-------------+---------------------------------------+