This README file accompanies the Token-Ring drivers for NetWare 286 and 386. The following files are included (contents of .ZIP files are also displayed): ROUTE VP0 3832 04-18-90 10:35a RPL VP1 1806 05-08-90 4:29p RPCONFIG COM 2726 06-08-90 5:15p SRCONFIG COM 3086 06-11-90 3:13p TRCONFIG COM 3402 06-08-90 4:55p ROUTE COM 3431 01-18-90 11:56a TOKEN RPL 12788 06-05-90 4:51p BTOKENA2 OBJ 4975 05-28-90 8:02p CTOKENA2 OBJ 4975 05-28-90 8:02p DTOKENA2 OBJ 4975 05-28-90 8:03p ATOKENA2 OBJ 4975 05-28-90 8:02p STOKEN OBJ 5333 05-15-90 8:42a SLANSUP OBJ 4318 07-31-90 10:44a TOKENA2 LAN 206 06-14-90 3:04p SLANSUP LAN 117 10-26-90 2:26p STOKEN LAN 104 06-14-90 3:04p FILESCFG TXT 5935 08-06-90 12:17p ROUTENLM TXT 8092 08-03-90 1:18p SOURCERT TXT 9018 08-06-90 12:04p PRE215C ZIP 666 10-26-90 2:53p TOKENA2 LAN 204 06-14-90 3:04p SLANSUP LAN 115 10-26-90 2:27p STOKEN LAN 102 06-14-90 3:04p 30 ZIP 9048 06-21-90 9:56a ROUTE NLM 2934 01-12-90 3:12p TOKEN LAN 8839 04-19-90 8:30a 31 ZIP 17301 06-21-90 9:57a TOKEN LAN 9544 06-07-90 3:29p TOKENRPL NLM 16454 06-05-90 5:02p ROUTE NLM 4506 04-27-90 3:20p CURRENT ZIP 674 10-26-90 2:48p TOKENA2 LAN 206 06-14-90 3:04p SLANSUP LAN 117 10-26-90 2:26p STOKEN LAN 104 06-14-90 3:04p These Token-Ring drivers are self-configurable and support the various types of Token-Ring cards used. FILESCFG.TXT gives a description of the files and how the drivers can be configured. Source Routing is supported on the server side through a VAP or NLM; on the workstation side it is supported using ROUTE.COM. SOURCERT.TXT explains Source Routing support on both the server and workstations sides and ROUTENLM.TXT describes the parameters used with ROUTE.NLM. Remote Program Load is supported in v2.1x as a VAP and in v3.1 as an NLM; the TOKEN.RPL file is also used for this function. ---------------------------------------------------------------------------- NetWare 386 Server Driver Installation ---------------------------------------------------------------------------- NOTE: The 3.0 LAN drivers are provided for your convenience. THEY HAVE NOT BEEN CERTIFIED. 1) Copy TOKEN.LAN from either the 3.0 or the 3.1 directories, depending on the version of your server, to your NetWare system start-up area (SYS:SYSTEM and/or DOS partition). Load the TOKEN.LAN driver as you normally would on your system. ---------------------------------------------------------------------------- NetWare 286 Server/Bridge Driver Installation ---------------------------------------------------------------------------- NOTE These drivers are distributed in the LAN_DRV_050 kit on a diskette labelled the same. It is recommended you label a diskette LAN_DRV_050 with DOS LABEL, or if using the Network drive generation option create a subdirectory called LAN_DRV_.050, and copy the files from the root of this .ZIP file to the diskette or subdirectory. These new LAN_DRV_050 files should replace any Token-Ring driver files previously used. 1) If you are using Pre-2.15 Rev C, you must copy the *.LAN files from the PRE215C.ZIP file to the LAN_DRV_050 diskette or subdirectory. If, for some reason, you should need the previously-used *.LAN files, they can be found in the CURRENT.ZIP file. 2) If you must change the default settings of the driver, run TRCONFIG.COM and assign the settings to the LAN you are going to link into your Operating System or Bridge. Upon successful completion, the ?TOKENA2.OBJ file will be changed, reflecting the date of modification. 3) Run NETGEN (or BRGEN if generating a bridge) and choose the "LOAD and SELECT" option. Select the driver identified as IBM Token-Ring w/AT II v2.50 (900528). Regenerate the server or bridge as you normally would. CAUTION These drivers default to a 4 Kb packet size. This packet size uses up a larger portion of DGroup RAM, leaving less room for file service processes. It is recommended that you change the default packet size, even if file service processes appear to be adequate, to 1 or 2 Kb before linking it into the operating system. This is done by running TRCONFIG against the driver and changing the Transmit Buffer Size (for example, TBZ = 2048). ---------------------------------------------------------------------------- Workstation Client Driver Installation ---------------------------------------------------------------------------- NOTE See the note in the previous section. Each workstation will need to use these LAN_DRV_050 shell drivers. 1) Run SHGEN and choose the "LOAD and SELECT" option. Two workstation drivers will be loaded from the LAN_DRV_050 diskette or subdirectory: IBM Token-Ring V2.50 (900515) LAN Support Program Driver (900731) Choose the LAN Support driver if you need any of the LAN Support options, such as running non-Novell NetBIOS or 3270 emulation software. Otherwise, choose the IBM Token-Ring driver. Both support Remote Program Loading. Note: The LAN Support driver assembles a 1k packet, whereas the IBM Token-Ring driver supports a 4k packet. ---------------------------------------------------------------------------- Remote Program Load Function (for diskless workstations) ---------------------------------------------------------------------------- NOTE TOKENRPL.NLM will not work on a NetWare 386 v3.0 server. 1) On a NetWare 386 v3.1 server, LOAD the TOKENRPL.NLM to enable Remote Program Load. 2) On a NetWare 286 v2.1x server, copy the RPL.VP1 and RPCONFIG.COM files into your SYS:SYSTEM directory on your server to enable Remote Program Load. Run RPCONFIG to set up the VAP for Remote Program Load. Load the VAP as you normally would. 3) In either case, copy the TOKEN.RPL file into your SYS:SYSTEM directory on your server. Refer to the Novell IBM Token-Ring Network Supplement for BOOTCONF.SYS file generation. ---------------------------------------------------------------------------- SOURCE ROUTING function. ---------------------------------------------------------------------------- 1) On a NetWare 386 server, LOAD the ROUTE.NLM from 30.ZIP or 31.ZIP (depending upon the version you are running) to invoke Source Routing capabilities. 2) On a v2.1x server, copy the ROUTE.VP0 and SRCONFIG.COM into the SYS:SYSTEM directory on your server. Run SRCONFIG to set up the VAP for source routing. Load the VAP as you normally would. 3) On workstation clients, run ROUTE.COM after IPX.COM (generated during Workstation Client Driver Installation) is loaded and before the SHELL (ie: NET3.COM, NET4.COM, EMSNET3.EXE, EMSNET4.EXE, XMSNET3.EXE, and XMSNET4.EXE) is loaded. ***************************************************************************** CAUTION ALWAYS backup your system before implementing any program/utility revision involving the low-level functions of NetWare including re-linking of operating system .OBJ files, Bindery utilities, drive and volume operation, etc. *****************************************************************************