If the application calling CCIIPX is a Console type application running on Windows 95 or Windows NT, a display will appear on the screen at the connection of a client to a server giving details of the type of connection that was established. These details include the protocol revision number (200, 201 or 202) and the maximum packet size that can be used to transmit data on the new session. If the application calling CCIIPX is not a Console type application running on one of the systems listed above, the output is lost. An example of output for an Ethernet based connection which doesn't use CRC checks is:
"Con_Accepted: CRC_NO_SEND - v201 client, max pkt 1394 bytes"
Create a Cyclic Redundancy Check checksum and include this in outgoing packets, this process slows down data transmission but ensures greater data integrity on links where corruption is suspected. Connections with CRC checking switched on appear as protocol versions 200 and 202.
Some servers will automatically discard CRC information from clients to save time, use of this flag will force the receiving servers to create a session which always uses the CRC information when sent from this client machine. Links with this flag set are seen as protocol type 202. NetWare Client v4.0 for NT has a inherent data integrity problem, when this client is installed CCIIPX will detect this and will always include CRC data in sessions created from these machines, CCIIPX clients on these machines will always force any server accepting their connections to use this CRC information, hence these clients will always be of protocol type 202.
This is a debugging setting, which can be used to display a notification message whenever a CRC check fails. This setting is obviously redundant in the default installations which do not utilize CRC checking at all.
This is a debugging setting, which allows a system setup to use CRC checking to behave as if no CRC checking were being performed. Used in conjunction with "CRC_REPORT_FAILS=y" it can confirm a data integrity error on a link and appropriate action can be taken on the client and server systems to enable CRC checking to always preserve data, at the expense of speed on the links.
This option defines in bytes the maximum size of a data packet that can be used by CCIIPX. It will not always be possible to connect two machines at this size of packet, but negotiation to determine the largest possible packet to transmit and receive takes place at the initialization of a new session, so the largest possible packet that can be carried on the intervening link between two machines, up to this limit, will be used whenever possible.