16 bit Windows

Loading

Networking components are loaded from the command line, where available or from an icon on the desktop. The DP4 client appears as an icon on the desktop. The network server can be run in foreground mode or minimised to appear as an icon on the desktop. Name-to-address mapping mechanisms are identical to those described for WIN32 programs. Command tails may be supplied either on the command line/icon properties or in the appropriate program section in the DP4 configuration file. To specify command tails in the [program] section of the DP4 configuration file use this syntax:

[tcpw] tcpw=-server 99 -timeout 20

Note If any command tails are supplied as part of the command line, the program section in the DP4 configuration file is not processed at all. You cannot mix the two methods by specifying some tails on the command line and some in the DP4 configuration file.

The required network components can be added to the startup group so that they are loaded automatically. If a network server is to be started automatically from the startup group, only tcpmgrw.exe should be added to the startup group and the autoload facility must be enabled in the DP4 configuration file.

Unloading the Network Software

The client, tcpw.exe, can be unloaded by clicking on the icon and choosing the close option. This will only succeed if no DP4 applications have an active connection at the time. The DP4 shutdown program can also be used.

The network manager and database manager must be closed separately in the normal way. If a network server is closed down, network clients with active connections will generate a Fail 7 network error when they next access the server.

Diagnostics

tcpw.exe and tcpmgrw.exe (and the corresponding programs for NetBIOS and IPX/SPX) accept the -debug and -debug_error command tails. Diagnostic output is limited to screen output via the DBWIN utility (supplied with Visual C 1.52 or the Windows SDK).

Command Tail specific to 16 bit Windows Network Requesters

-ALLOW_CLOSE n where n is 0, 1 or 2

n = 0 gives the default behaviour described above. tcpw (and ipxw,ntbw) ignores the close command if any DP4 applications are still active.
n = 1 forces tcpw to ask the operator to confirm that it should close if the close option is selected while DP4 applications are still active. If confirmed, tcpw exits and any DP4 applications still active will generate an error when they next try to access the server.
n = 2 forces tcpw to exit immediately. Any applications still active will generate an error when they next try to access the server.