This TOKODI.DOC accompanies DOSUP8.EXE which includes DOS ODI drivers for IBM Token-Ring and Lan Support NetWare Clients. The following file(s) are included: TOKEN COM 27381 4-12-93 6:27p LANSUP COM 21943 2-02-93 11:54a TOKODI DOC (this file) Token.com and lansup.com have been enhanced to include 'Least Significant Bit' first (LSB) node addresses per the 'IEEE canonical form' when sending frames above the Data-Link layer. Previously, token.com and lansup.com drivers provided 'Most Significant Bit' first (MSB) only when sending MAC header node address information above the Data-Link layer. This LSB ability provides node ID bit-reversal compatibility with IBM 8209 Bridges. Bit-reversals take place on all source and destination node addresses when 8209 bridges transfer frames from ethernet segments to token-ring segments unless "IPX Support" has been enabled on the 8209. The 8209 will not bit-reverse IPX (E0E003/AAAA03/8137) node addresses when "IPX Support" has been enabled. The new LSB feature of lansup.com and token.com allow compatibility with the 8209 without "IPX Support" enabled. It is advised only to use the LSB parameter on the Token- Ring segments with 8209 bit-reversal enabled. (see paragraphs below on Bit-Reversals) Additionally, these drivers provide full compatibility with the latest IBM locally administered node address standard for Token-Ring adapters. In the past, IBM recommended that locally administered addresses for Token-Ring adapters fall within a range between and including the following addresses: 4000 0000 0000 to 4000 7FFF FFFF (HEX) IBM has expanded the range of recommended locally administered addresses to the following: 4000 0000 0000 to 7FFF FFFF (HEX) There are some restrictions that apply to the above changes. Some devices and/or programs may only be able to use decimal addresses. In this case, the following locally administered address range would be appropriate: 4000 0000 0000 to 7999 9999 9999 (HEX) It is recommended that 'NSSS FLASH N1005' be obtained from IBM for all details pertaining to the above LAA changes and associated restrictions. ********* USAGE ********** The following NET.CFG file demonstrates the enhanced abilities and usage of lansup.com and token.com. Please refer to the Novell ODI shell for DOS manual (part #100-000871-001) for further information on individual parameters. Additional information regarding implementation of token.com and lansup.com is available in DOSODIWS.DOC found in DOSUP8.EXE also available on NetWire. Sample NET.CFG IPX SOCKETS = 20 IPX RETRY COUNT = 20 CACHE BUFFERS = 5 LONG MACHINE TYPE = IBM_PC PROTOCOL ipx BIND Token (or Lansup) LINK DRIVER Token (or Lansup) Node Address 444400002D43 Slot 2 Frame TOKEN-RING_SNAP LSB SAPS 2 Link Stations 2 ALTERNATE Max Frame Size = 2168 *********** BIT-REVERSALS ******** Bit-reversals are necessary because of the difference between ethernet adapters and token-ring adapters: Ethernet adapters transmit data onto the wire by transmitting one byte of data at a time in the following manner: Each byte of data is bit-wise right-shifted one bit at a time onto the wire until all 8 bits of the byte are transmitted onto the wire. The next byte of data is then loaded into the transmit register and the process repeats itself. The least significant bit, therefore, goes onto the wire first with ethernet adapters. Token-Ring adapters do the opposite. They take one byte of data and do a bit-wise left-shift one bit at a time onto the wire until all 8 bits of the byte are transmitted onto the wire. Another byte of data is then loaded into the transmit register for transmission. The most significant bit, therefore, goes onto the wire first. Therefore, the byte 'AA (hex)' on an ethernet wire would appear as the byte '55 (hex)' on a Token-Ring wire after being bit-reversed by an IBM 8209 Ethernet to Token-Ring Bridge. ************* TOKODI MODIFICATION HISTORY ************** 3-12-91: Initial release of TOKODIFT.ZIP beta drivers. 6-3-92: Lansup.com has been updated to allow frame sizes above 1K during RPL. A new "OPEN" parameter for the NET.CFG has been added. This feature allows lansup.com to open the token-ring adapter and set the frame size. If dxmt0mod.sys is also loading, one of two actions must be performed: (1) set "o=n" on the dxmt0mod.sys command argument line in the config.sys and use the "OPEN" parameter for lansup.com in the net.cfg. -or- (2) Set "o=y" in dxmt0mod.sys command line allowing dxmt0mod.sys to open the adapter and set the frame size, and exclude lansup.com's "OPEN" parameter from the net.cfg. Use the following net.cfg syntax when using "OPEN": LINK DRIVER LANSUP OPEN 9/14/92: Lansup.com has been updated to be compatible with DXME0MOD.sys from IBM Lan Support program v1.30. Token.com has also been updated to work with Odinsup.com where DXME0MOD.SYS V1.30 is involved. Files included in the previous revision: (Included in TOKODI.ZIP) LANSUP COM 21524 6-03-92 9:47a TOKODIFT DOC (this file) Files also in a previous revision: TOKEN COM 23564 8-05-92 2:55p LANSUP COM 21588 8-05-92 2:56p TOKODI DOC (This File) ************* END OF MODIFICATION HISTORY ********************* *************************************************************** DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ***************************************************************