#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'NetWare Client for DOS and MS Windows Technical ReferenceNetWare Client for DOS and MS Windows Technical ReferenceNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=5 ID="BP1"How to Use This ManualRENDERAS="SECT1"IntroductionNetWare Client for DOS and MS Windows Technical Reference provides you with detailed information to configure the NetWare® DOS 
RequesterTM software, modify the NetWare ClientTM configuration file, and troubleshoot client workstation error messages in order to manage client workstations on a NetWare network.This document is for supervisors responsible for managing NetWare client workstations.NetWare Client for DOS and MS Windows Technical Reference covers concepts and procedures for configuring and using NetWare workstation software on NetWare 2, NetWare 3TM, and NetWare 4TM networks. References are made to each version of NetWare. Ignore any references which do not pertain to the version of NetWare you are connecting to.Use NetWare Client for DOS and MS Windows User Guide for procedures and information on installation and basic client workstation setup.RENDERAS="SECT1"Contents OverviewTo configure your NetWare Client software, use the chapters as described in the following checklist.MARK=CHECKBOXUse Chapter 1, IDREF="FM55385""Optimizing the NetWare Client Software," to learn how to improve workstation performance by using Packet BurstTM and Large Internet Packets (LIP) and to enhance security on client workstations by using NCPTM packet signatures.Use Chapter 2, IDREF="FM37847""NET.CFG Options Reference," to learn how to set up and modify the NetWare Client (NET.CFG) configuration file and to reference information for setting NET.CFG option parameters.PAGENUM=6 ID="BP2"Use Chapter 3, IDREF="FM62716""Command Line Parameters Reference," to learn how to reference information for setting command line parameters.Use Chapter 4, IDREF="FM27972""System Messages," to receive an explanation of each client workstation system message and a recommendation on a course of action for each message.RENDERAS="SECT1"Documentation IDXID="w11475"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
ConventionsThis manual uses the following Novell® conventions:RENDERAS="SECT2"Asterisk ( * )An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, TM, etc.).An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a "Trademarks" section at the back of printed manuals. A trademarks list is also available in the DynaText* online documentation.RENDERAS="SECT2"CommandsBoldface characters indicate items that you type, such as IDXID="w11476"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
commands and options. You can use any combination of uppercase and lowercase letters.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\A INSTALLRENDERAS="SECT2"Delimiter Bar ( | )In IDXID="w11477"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
syntax examples, a delimiter bar separating two command options indicates that you can choose one of the options.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"-S | -RDo not type the bar.PAGENUM=7 ID="BP3"RENDERAS="SECT2"IDXID="w11478"BOOK="_idx" COLLECTION="nw41" TIDREF="i1186"
DOS IDXID="w11479"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
CommandsDOS commands and command option letters are shown in uppercase letters. For example: FTPD.Because DOS is not case-sensitive, you can type DOS commands in uppercase or lowercase letters.RENDERAS="SECT2"IDXID="w11480"BOOK="_idx" COLLECTION="nw41" TIDREF="i1479"
DOS IDXID="w11481"BOOK="_idx" COLLECTION="nw41" TIDREF="i1186"
Filenames, Directory Names, and PathnamesDOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT.Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters.RENDERAS="SECT2"EllipsesEllipses in syntax examples indicate that parameters, options, or settings can be repeated.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SERVER1/SUPERVISOR /option...you could replace option with any number of available options.RENDERAS="SECT2"EmphasisItalic type also indicates emphasized text. For example:Remember to load the driver before you install the application.RENDERAS="SECT2"IconsChecklists, which often contain prerequisites, are marked with the "Checklist" icon to the left of this text.Procedures to follow in order to accomplish a specified task are marked with the "Procedure" icon to the left of this text.PAGENUM=8 ID="BP4"Additional or "nonessential" but noteworthy information is marked with the "Note" icon to the left of this text.Vital information about system or software requirements, etc., that deserves particular attention is marked with the "Important" icon to the left of this text.Guidelines or tips about fine-tuning, optimizing, etc., which might be applicable to your site or situation but maybe not to all, are emphasized with the "Suggestion" icon to the left of this text.Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text. RENDERAS="SECT2"Key IDXID="w11482"BOOK="_idx" COLLECTION="nw41" TIDREF="i2009"
NamesAngle brackets surround the name of a key. For example, MOREINFO="NONE"<Enter> corresponds to the MOREINFO="NONE"Enter key on your keyboard. MOREINFO="NONE"<Ctrl>+<c> means hold down the MOREINFO="NONE"Ctrl key and simultaneously type the letter MOREINFO="NONE"c (in lowercase, in this case).RENDERAS="SECT2"NET.CFG IDXID="w11483"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
File Section Headings and Parameter SettingsIDXID="w11484"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG section headings and parameter settings are shown in uppercase when used as a reference item and lower case when used in syntax or working examples.For example:NETBIOS VERIFY TIMEOUT specifies how often in (ticks) NetBIOS sends a keep-alive packet to the other side of a session to preserve the session.If no packets are being exchanged on the NetBIOS session by the software that established the session, NetBIOS sends packets at regular intervals to make sure that the session is still valid.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios verify timeout numberReplace number with a number of ticks. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"54 (approximately 3 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make NetBIOS wait longer before sending a request-for-acknowledgment packet, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios verify timeout 1350PAGENUM=9 ID="BP5"Because interpretation of this file is not case-sensitive, you can type its contents in uppercase or lowercase letters.RENDERAS="SECT2"OptionsIn syntax examples, braces indicate that you are required to choose one of the enclosed options. For example, the following notation means that you must include a 0 or a 1 in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"{0, 1}RENDERAS="SECT2"Square BracketsIn syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP [ -D ] [ -F ]RENDERAS="SECT2"System ResponseMonospace type shows system-generated responses that appear on your workstation screen. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"TNVT220>RENDERAS="SECT2"UNIX IDXID="w11485"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
CommandsIDXID="w11486"BOOK="_idx" COLLECTION="nw41" TIDREF="i4655"
UNIX® commands are shown in boldface letters. For example, MOREINFO="NONE"vi. Because UNIX is case-sensitive, these commands are usually lowercase. Type UNIX commands exactly as shown.PAGENUM=10 ID="BP6"RENDERAS="SECT2"UNIX IDXID="w11487"BOOK="_idx" COLLECTION="nw41" TIDREF="i1479"
Filenames, Directory Names, and PathnamesIDXID="w11488"BOOK="_idx" COLLECTION="nw41" TIDREF="i4655"
UNIX filenames, directory names, and pathnames are shown in italics. For example, /etc/hosts.Because UNIX is case-sensitive, these names usually are in lowercase letters. Type UNIX filenames exactly as shown.RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_hostyou type the name of a computer on your network in place of remote_host.RENDERAS="SECT1"Supplemental DocumentationThe following publications provide supplemental information specifically related to the NetWare Client for DOS and MS Windows technology and software:MARK=BULLET"The Functions and Operations of the NetWare DOS Requester 1.1," Novell Application Notes, May 94, Vol. 5, No. 5."Installing and Configuring Novell's Token-Ring Source Routing Drivers," NetWare Application Notes, Oct 91 (Novell part # 164-000030-010)"Logging In to IBM LAN Server and NetWare from a DOS Workstation," NetWare Application Notes, Nov 91 (Novell part # 164-000030-011)"Managing Memory in a DOS Workstation: Part 1," NetWare Application Notes, Aug 92 (Novell part # 164-000031-008)"Managing Memory in a DOS Workstation: Part 2," NetWare Application Notes, Oct 92 (Novell part # 164-000031-010)"Managing Memory in a DOS Workstation: Using Novell DOS 7," NetWare Application Notes, Oct 93 (Novell part # 164-000032-010)PAGENUM=11 ID="BP7""Migrating Ethernet Frame Types from 802.3 Raw to IEEE 802.2," NetWare Application Notes, Sep 93 (Novell part # 164-000032-009)"Multilingual PC Setup with DR DOS," NetWare Application Notes, Sep 93 (Novell part # 164-000032-009)"NET.CFG Parameters for the NetWare DOS Requester 1.1," Novell Application Notes, Jun 94, Vol. 5, No. 6 "NetWare and LAN Server Client Interoperability via ODINSUP: Part 1," NetWare Application Notes, Sep 92 (Novell part # 164-000031-009)"NetWare and LAN Server Client Interoperability via ODINSUP: Part 2," NetWare Application Notes, Nov 92 (Novell part # 164-000031-011)"NetWare and Windows for Workgroups 3.1 Interoperability," NetWare Application Notes, Mar 93 (Novell part # 164-000032-003)NetWare Client for DOS and MS Windows User Guide, Novell Publication (Novell part # 100-001623-002)"ODINSUP Interoperability Configurations for DOS Workstations," NetWare Application Notes, Feb 93 (Novell part # 164-000032-002)"Using the DOS Requester with NetWare 4.0," NetWare Application Notes, Apr 93 (Novell part # 164-000032-004)"Understanding Token-Ring Source Routing," NetWare Application Notes, May 91 (Novell part # 164-000030-005)"Workstation Memory Management: Using QEMM386, 386 To The Max, and MS-DOS 6," NetWare Application Notes, Dec 93 (Novell part # 164-000032-012)RENDERAS="SECT1"Online 
HelpIDXID="w11489"BOOK="_idx" COLLECTION="nw41" TIDREF="i4460"MARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press MOREINFO="NONE"<F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For example, for help with the RIGHTS command, type "RIGHTS /?".PAGENUM=12 ID="BP8"Online MS Windows help. Microsoft* (MS) Windows help viewer allows you to read NetWare help developed for the MS Windows environment. To access the NetWare help screens within MS Windows, press <MOREINFO="NONE"F1> or the "?" button.DynaText online documentation. The DynaText viewer allows you to read NetWare documentation from your DOS, MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4TM and 3.12 documentation except the Quick Access Guide are available on the NetWare Online Documentation CD-ROM.RENDERAS="SECT1"IDXID="w11490"BOOK="_idx" COLLECTION="nw41" TIDREF="i4460"
Additional 
Help ResourcesMARK=BULLETCustomer service. You can contact your Novell Authorized Reseller for technical assistance.Most Novell Authorized Resellers have Certified NetWare EngineerSM representatives on their staffs ready to assist users with their networking problems.Novell Authorized Service
CenterSM (NASC) locations. NASCSM facilities are local support providers authorized and supported by Novell. They provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, in the U.S. and Canada call 1-800-338-NASC.Hardware documentation. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS) services. NMSTM services helps you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized ResellerCLM representative.PAGENUM=13 ID="BP9"Other Novell publications. Novell Application Notes and the Novell Research ReportsTM publications cover technical aspects of NetWare based system design, implementation, and management.Application Notes is a collection of technical articles published monthly. Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications from within the United States or Canada, call the Novell Research Order Desk at 1-800-UPDATE1. From other locations, call 801-429-5380.Third-party books and periodicals. Books on NetWare, including books published by Novell PressTM publishing, are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWire® forum on the CompuServe* bulletin board. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers and ask for "Representative 200"MARK=BULLETIn the United States or Canada: 1-800-524-3388In the United Kingdom: 0800-289-378In Germany: 0130-37-32In other European countries: 44-272-255-111In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.Technical Support Database and NetWire forum on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems. Over 9,000 documents exist on the WWW system for providing technical hints and information.To access the Novell Internet sites, log in as ANONYMOUS and use your E-mail address as your password.   Contact one of the following site addresses:TYPE="VERT"In the United States: ftp.novell.comIn Germany: ftp.novell.dePAGENUM=14 ID="BP10"In the United Kingdom: ftp.salford.ac.ukIn Canada: novell.nrc.caSee public areas in these sites for possible listings of other sites addresses. FaxBack Service. Novell provides a FaxBack Service for obtaining additional product information to help with support needs.To access the Novell FaxBack Service, complete the following steps.MARK=BULLETWithin the continental United StatesTYPE="VERT"1. Dial 1-800-NETWARE (1-800-638-9273).2. Press #1 (the "Presale Product Information and Upgrade Information" option).3. Again press #1 (the "Receive Product Information via Fax" option).Outside the continental United StatesDial 1-801-429-2772. You are connected directly to the FaxBack Service.Follow the directions provided on the phone. You are prompted to enter a document number and then a fax number to send the document to.Network Support Encyclopedia Professional VolumeSM (NSE Pro) package. This encyclopedia gives customers access to regularly updated information on products and services---plus patches, fixes, and more---from Novell and other vendors.The NSE ProSM package is distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. More information is available on NetWire or from your Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as the Novell LANalyzer® software, are available to help you isolate network problems.PAGENUM=15 ID="BP11"RENDERAS="SECT1"User CommentsWe are continually looking for ways to make our products and our documentation as easy to use as possible.You can help us by sharing your comments and suggestions about how our documentation could be made more useful to you and about inaccuracies or information gaps it might contain.Submit your comments either by filling out the "User Comments" form at the end of this document or by writing to us directly at the following address:TYPE="VERT"Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LABEL="1"PAGENUM=1 ID="BP12"ID="FM55385"Optimizing the NetWare Client SoftwareRENDERAS="SECT1"OverviewThis chapter explains how to optimize the NetWare® ClientTM software for increasing the speed of client workstations by using the Packet BurstTM protocol and Large Internet Packets (LIP). It also explains how to protect information on client workstations.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM14044"Increasing Speed COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM14044"1COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM54039"Improving Security COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54039"5COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11308"Using Other Client Security Guidelines COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11308"12RENDERAS="SECT1"IntroductionYou can increase the speed and improve the security of client workstations by using the Packet Burst protocol and Large Internet Packets (LIPs), and by implementing the NCPTM packet signature feature available in NetWare 4TM and 3.12 software. RENDERAS="SECT1"ID="FM14044"Increasing SpeedIDXID="w11491"BOOK="_idx" COLLECTION="nw41" TIDREF="i3104"
NetWare 3.12 and 4 support the Packet Burst and Large Internet Packet technologies which increase the access speed of network resources and services for client workstations.PAGENUM=2 ID="BP13"RENDERAS="SECT2"Using the IDXID="w11492"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"IDXID="w11493"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"
Packet Burst ProtocolThe Packet Burst protocol allows high-performance data transmission between client workstations and servers.Some network topologies, such as Ethernet and token ring, allow large packets to be sent over the network. The LIP (Large Internet Packet) capability enhances throughput over bridges or routers by increasing the packet size. The following sections provide you with information and procedures for setting parameters used in the client workstation configuration file (NET.CFG). Packet Burst on the client workstation is enabled automatically in the NetWare DOS RequesterTM software. RENDERAS="SECT3"Requirement for IDXID="w11494"BOOK="_idx" COLLECTION="nw41" TIDREF="i2385"
Packet IDXID="w11495"BOOK="_idx" COLLECTION="nw41" TIDREF="i3804"
BurstIDXID="w11496"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"
The Packet Burst protocol code IDXID="w11497"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
requires about 6 KB of memory. However, as a default, the NetWare DOS Requester uses the Open Data-Link InterfaceTM architecture for Packet Burst and doesn't require additional workstation memory.RENDERAS="SECT3"How Packet Burst WorksAt connection time, maximum burst sizes are negotiated with each server. Since Packet Burst is established with each connection, it's possible to "burst" with one server but not with another.Once you establish a Packet Burst connection between a client workstation and a NetWare server, the client workstation automatically uses the Packet Burst service whenever an application requests to write more than one physical packet of data.RENDERAS="SECT3"When to Use IDXID="w11498"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"
Packet BurstPacket Burst is not required for every installation; however, disabling LIP will results in noticable speed degradation. Some network supervisors might choose not to use Packet Burst because some of the servers that the client workstations are connecting to do not support it.PAGENUM=3 ID="BP14"RENDERAS="SECT2"Configuring for Packet BurstAlthough Packet Burst is automatically enabled in the NetWare DOS Requester, you can configure it for your needs. See IDREF="FM83220""PB BUFFERS=number" on page 143, IDREF="FM46002""PBURST READ WINDOWS SIZE=number" on page 144, and IDREF="FM39829""PBURST WRITE WINDOWS SIZE=number" on page 144 for details on how to configure for Packet Burst.RENDERAS="SECT2"Disabling IDXID="w11499"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"
Packet IDXID="w11500"BOOK="_idx" COLLECTION="nw41" TIDREF="i1101"
BurstTo disable Packet Burst at client workstations, add this line to the IDXID="w11501"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file under the "NetWare DOS Requester" option heading:FORMAT="LINESPECIFIC"MOREINFO="NONE"pb buffers = 0For example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   pb buffers=0RENDERAS="SECT2"Using IDXID="w11502"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"
Large Internet IDXID="w11503"BOOK="_idx" COLLECTION="nw41" TIDREF="i2065"
Packet FunctionalityLarge Internet Packet (LIP) functionality allows the packet size to be increased from the default of 576 bytes. LIP is enabled automatically in the NetWare DOS Requester software.IDXID="w11504"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"
Previously, the size of packets that cross bridges or routers on NetWare networks was limited to 576 total bytes. Some network architectures like Ethernet and token ring allow larger packets to be sent over the network.By allowing the packet size to be increased, LIP enhances the throughput over bridges and routers if the routers aren't limited to the smaller packet size.The following sections provide you with information and procedures for setting parameters used in the client workstation configuration file (NET.CFG). The Large Internet Packet technology on the client workstation is enabled automatically in the NetWare DOS Requester software. PAGENUM=4 ID="BP15"Some LAN drivers might not operate correctly using this parameter. If you experience trouble, disable this parameter or update the version of your LAN driver.RENDERAS="SECT3"How Large Internet Packet WorksIn previous NetWare versions, the NetWare ClientTM software initiated a negotiation with the NetWare server to determine an acceptable packet size.If the NetWare server software detected a router between it and the client workstation, the server returned a maximum packet size of 576 bytes to the NetWare Client software.In the current NetWare version, the NetWare Client software still initiates packet size negotiation. However, because of LIP, the NetWare server no longer returns a packet size of 576 bytes when a router is detected.Instead, the NetWare Client software negotiates with the NetWare server software to agree on the largest packet size available.RENDERAS="SECT3"When to Use IDXID="w11505"BOOK="_idx" COLLECTION="nw41" TIDREF="i2065"
Large Internet PacketLarge Internet Packet is not required for every installation; however, disabling LIP results in noticable speed degradation. Some network supervisors might choose not to use Large Internet Packet because some of the servers that the client workstations are connecting to do not support it, such as NetWare 2 and NetWare 3.11 and earlier.RENDERAS="SECT2"Configuring for Large Internet PacketAlthough LIP is automatically enabled in the NetWare DOS Requester, you can configure it for your needs. See IDREF="FM31456""LARGE INTERNET PACKETS=[on | off]" on page 130 for details on how to configure for Packet Burst.RENDERAS="SECT2"Disabling IDXID="w11506"BOOK="_idx" COLLECTION="nw41" TIDREF="i2065"
LIPIDXID="w11507"BOOK="_idx" COLLECTION="nw41" TIDREF="i1101"
To disable LIP functionality at the client workstation, add this line to the IDXID="w11508"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file under the "NetWare DOS Requester" option heading:FORMAT="LINESPECIFIC"MOREINFO="NONE"large internet packets = off
PAGENUM=5 ID="BP16"For example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   large internet packets = offRENDERAS="SECT1"ID="FM54039"Improving SecurityIDXID="w11509"BOOK="_idx" COLLECTION="nw41" TIDREF="i3104"
You can increase the security of your network by using the NCP packet signature feature available in NetWare 4 and 3.12.The following sections provide you with information and procedures for setting a parameter used in the client workstation configuration (NET.CFG) file and the SET command used at each NetWare server.RENDERAS="SECT2"Using NCP IDXID="w11510"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
Packet Signature to IDXID="w11511"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Improve SecurityIDXID="w11512"BOOK="_idx" COLLECTION="nw41" TIDREF="i3169"IDXID="w11513"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NCP packet signature is an enhanced 
security feature that protects servers and client workstations using the NetWare Core ProtocolTM architecture by preventing packet forgery.The NCP packet signature is optional IDXID="w11514"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"
because the packet signature process consumes CPU resources and slows performance, both for the client workstation and the NetWare server.Without the NCP packet signature installed, a knowledgeable network operator can manipulate the client workstation software to send a forged NCP request to a NetWare server. By forging the proper NCP request packet, an intruder can gain rights to access all network resources.RENDERAS="SECT3"How NCP Packet Signature WorksNCP packet signature prevents forgery by requiring the server and the client workstation to "sign" each NCP packet, using the RSA public and private key encryption. The packet signature changes with every packet.PAGENUM=6 ID="BP17"NCP packets with incorrect signatures are discarded without breaking the client workstation's connection with the server. However, an alert message about the source of the invalid packet is sent to the error log, the affected client workstation, and the NetWare server console.If NCP packet signature is installed on the server and all of the network client workstations, it is virtually impossible to forge an NCP packet that would appear valid.RENDERAS="SECT3"When to Use IDXID="w11515"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NCP Packet SignatureNCP packet signature is not required for every installation. Some network supervisors might choose not to use it because they can tolerate certain security risks.RENDERAS="SECT4"Tolerable Security RisksThe following are examples of network situations that might not need NCP packet signature:MARK=BULLETOnly executable programs reside on the serverAll client workstation users on the network are known and trusted by the network supervisorData on the NetWare server is not sensitive; access, loss, or corruption of this data would not affect operationsRENDERAS="SECT4"Serious Security RisksIDXID="w11516"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
NCP packet signature is recommended for security risks such as these:MARK=BULLETUnauthorized client workstation users on the networkEasy physical access to the network cabling systemAn unattended, publicly accessible client workstation within your networkRENDERAS="SECT3"NCP Packet Signature IDXID="w11517"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
OptionsIDXID="w11518"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"PAGENUM=7 ID="BP18"Several signature options are available, ranging from never signing NCP packets to always signing NCP packets. NetWare servers and network client workstations both have four signature levels, which are explained in the following table.LABEL="1-1" PGWIDE=0 TOCENTRY="1"ID="FM37052" NCP Packet Signature LevelsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Level NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Doesn't sign packets.COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Signs packets only if the server requests it (NetWare server NCP option is 2 or higher).COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Signs packets if the server is capable of signing (NetWare server NCP option is 1 or higher).COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Signs packets and requires the server to sign packets (or logging in will fail).RENDERAS="SECT3"ID="FM59303"Effective Packet Signature LevelsIDXID="w11519"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
The signature levels for the IDXID="w11520"BOOK="_idx" COLLECTION="nw41" TIDREF="i4062"
server and the client workstations combine to determine the overall level of NCP packet signature on the network called the effective packet signature level.Some combinations of server and client packet signature levels might slow performance. However, low-CPU-demand systems might not show any performance degradation. You can choose the packet signature level that meets both their performance needs and their security requirements.The following table shows the interactive relationship between the server packet signature levels and the client workstation signature levels.LABEL="1-2" PGWIDE=1 TOCENTRY="1" Effective Packet Signature Combinations of Server and Client WorkstationsCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="6*"COLNAME=5 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IFCOLNAME=2 ROTATE="0" MOREROWS="0"Server = 0COLNAME=3 ROTATE="0" MOREROWS="0"Server = 1COLNAME=4 ROTATE="0" MOREROWS="0"Server = 2COLNAME=5 ROTATE="0" MOREROWS="0"Server = 3VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Client Workstation = 0COLNAME=2 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=3 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=4 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=5 ROTATE="0" MOREROWS="0"No logging inCOLNAME=1 ROTATE="0" MOREROWS="0"Client Workstation = 1COLNAME=2 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=3 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=4 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=5 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=1 ROTATE="0" MOREROWS="0"Client Workstation = 2COLNAME=2 ROTATE="0" MOREROWS="0"No packet signatureCOLNAME=3 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=4 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=5 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=1 ROTATE="0" MOREROWS="0"Client Workstation = 3COLNAME=2 ROTATE="0" MOREROWS="0"No logging inCOLNAME=3 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=4 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=5 ROTATE="0" MOREROWS="0"Packet signaturePAGENUM=8 ID="BP19"RENDERAS="SECT2"Examples of Using Packet IDXID="w11521"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Signature LevelsThis section includes some examples of when you would use different signature levels.RENDERAS="SECT3"All Information on the Server Is SensitiveCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"If an intruder gains access to any information on the IDXID="w11522"BOOK="_idx" COLLECTION="nw41" TIDREF="i4062"
NetWare server, it could damage the company.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The network supervisor sets the server to level 3 and all client workstations to level 3 for maximum protection.RENDERAS="SECT3"Sensitive and Nonsensitive Information Reside on the Same ServerCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"The NetWare server has a directory for executable programs and a separate directory for corporate finances (such as accounts receivable).COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The network supervisor sets the server to level 2 and the client workstations that need access to accounts receivable to level 3. All other client workstations remain at the default level 1.RENDERAS="SECT3"Client Workstation Users Often Change LocationsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"The network supervisor is uncertain which employees will be using which client workstations, and the NetWare server contains some sensitive data.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The network supervisor sets the server to level 3. Client workstations remain at the default level 1.PAGENUM=9 ID="BP20"RENDERAS="SECT3"Client Workstation Is Publicly AccessibleCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"An unattended client workstation is set up for public access to nonsensitive information, but another server on the network contains sensitive information.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The network supervisor sets the sensitive server to level 3 and the unattended client workstation to level 0.RENDERAS="SECT2"Installing IDXID="w11523"BOOK="_idx" COLLECTION="nw41" TIDREF="i1827"
NCP IDXID="w11524"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Packet SignatureTo install the NCP packet signature support you must set a parameter used in the NET.CFG file on each client workstation and a SET command used at each NetWare server.RENDERAS="SECT3"Workstation SettingTo install IDXID="w11525"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"
NCP packet signature on a DOS or MS Windows client workstation, add this line to the NET.CFG file under the NetWare DOS Requester option:FORMAT="LINESPECIFIC"MOREINFO="NONE"signature level = numberFor example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   signature level = 2Replace number with 0, 1, 2, or 3. The default is level 1, which provides the most flexibility while still offering protection from forged packets.See IDREF="FM38061""SIGNATURE LEVEL=number" on page 154 for details on how to configure for NCP packet signature support on the client workstation.Some LAN drivers might not operate correctly using this parameter. If you experience trouble, disable this parameter or update the version of your LAN driver.RENDERAS="SECT3"Server SettingTo ensure that the SET parameter "NCP PACKET SIGNATURE OPTION" is added to the system at each server you want NCP packet signature support on, type the following command at each server console:PAGENUM=10 ID="BP21"FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NCP PACKET SIGNATURE OPTION = number MOREINFO="NONE"<Enter>Replace number with 0, 1, 2, or 3. The default is level 1, which provides the most flexibility while still offering protection from forged packets.See "BOOK="superenu" COLLECTION="nw41"Preventing Packet Forgery," in Chapter 6 of Supervising the NetWork for details on how to configure for NCP packet signature support on the server. RENDERAS="SECT2"Disabling IDXID="w11526"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Packet SignatureIDXID="w11527"BOOK="_idx" COLLECTION="nw41" TIDREF="i1101"
To disable NCP packet signature support at the client workstation, add this line to the IDXID="w11528"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file under the "NetWare DOS Requester" option heading:FORMAT="LINESPECIFIC"MOREINFO="NONE"signature level = 0For example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   signature level = 0For explanations of packet signature levels and their combined use, IDREF="FM37052"see Table 1-1 on page 7.RENDERAS="SECT2"ID="FM57060"Troubleshooting 
NCP IDXID="w11529"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Packet SignatureThis section 
describes some solutions to problems that might be associated with using NCP packet signature.RENDERAS="SECT3"Client Workstations Are Not Signing 
PacketsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"Client workstations are not signing NCP packets.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The SECURITY.VLM file is not loading. Ensure the signature level on the client workstation is not set to 0. SECURITY.VLM loads by default when the client signature level is set to 1, 2 or 3.Use the VLM /V4 command line parameter when loading the VLM software to display load time information.PAGENUM=11 ID="BP22"RENDERAS="SECT3"Client Workstations Cannot 
Log InCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"Client workstations cannot log in.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"Make sure the packet signature levels on the server and the client workstation are correct. See IDREF="FM59303""Effective Packet Signature Levels" on page 7Note that the following situations do not allow logging in:Server packet signature = 3, client workstation  signature = 0Server packet signature = 0, client workstation  signature = 3The LOGIN utility is an older version that doesn't support packet signatureThe NetWare DOS Requester or the shell is an older version that doesn't support packet signatureRENDERAS="SECT3"The Error Message "Error Receiving from the Network" AppearsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"The error message "Error receiving from the network" appears.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The client workstation is using a version of LOGIN.EXE file that doesn't include NCP packet signature. Make sure the new LOGIN.EXE and other new utility files are installed on all NetWare servers on the network.RENDERAS="SECT3"Third-Party IDXID="w11530"BOOK="_idx" COLLECTION="nw41" TIDREF="i2759"
NLM 
Programs 
Do Not WorkCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"Third-party NetWare Loadable ModuleTM (NLM) programs do not work.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"If the SET parameter "Allow Change to Client Rights" is set to "OFF," some IDXID="w11531"BOOK="_idx" COLLECTION="nw41" TIDREF="i4476"
third-party NLMTM programs might not function. Set this parameter to "ON."PAGENUM=12 ID="BP23"RENDERAS="SECT3"Insecure Client Workstations Log In to a Secure ServerCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ProblemCOLNAME=2 ROTATE="0" MOREROWS="0"Insecure client workstations log in to a secure server.COLNAME=1 ROTATE="0" MOREROWS="0"SolutionCOLNAME=2 ROTATE="0" MOREROWS="0"The client workstations are using an old LOGIN.EXE file that does not include NCP packet signature. Make sure the new LOGIN.EXE and other new utility files are installed on all servers on the network.Use the "Preferred Server" option in the NET.CFG file for all client workstations that have access to secure servers (level 3). IDREF="FM66900"See "PREFERRED SERVER="server_name"" on page 145for details on how to configure for this option.RENDERAS="SECT1"ID="FM11308"Using Other Client Security GuidelinesIDXID="w11532"BOOK="_idx" COLLECTION="nw41" TIDREF="i3104"
In addition to IDXID="w11533"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"IDXID="w11534"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
installing NCP packet signature, you can use other NetWare security features and protective measures to keep client workstations secure.We suggest the following security guidelines for client workstations:MARK=BULLETUse only the most current versions of system software, NetWare Client software, and patches.Check for viruses regularly.Use the SECURITY utility to detect vulnerable access points to the server.Enable intruder detection and lockout.Advise users to log out when their client workstations are unattended.Enable NCP packet signature level 3 on all unattended client workstations.Require passwords of at least five characters on all accounts.Force password changes at least every three months.Require unique passwords.Limit the number of grace logins.PAGENUM=13 ID="BP24"Limit the number of concurrent connections.Enforce login time restrictions and station restrictions.RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modify your NET.CFG file for Packet Burst, LIP, and NCP packet signaturesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37847"Chapter 2, "NET.CFG Options Reference," on page 15COLNAME=1 ROTATE="0" MOREROWS="0"Setting up Packet Burst support on a NetWare serverCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 7, "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"Setting up Large Internet Packet (LIP) support on a NetWare serverCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 7, "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"Setting up NCP packet signature support on a NetWare serverCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 7, "BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server" in Supervising the NetworkLABEL="2"PAGENUM=15 ID="BP25"ID="FM37847"NET.CFG Options ReferenceRENDERAS="SECT1"OverviewThis chapter explains how to create or modify a 
NET.CFG file and contains an alphabetical listing and discussions of the currently available NET.CFG file options.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM37540"Creating and Modifying a NET.CFG FileCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37540"16COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83677"Using NET.CFG Options and ParametersCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83677"18COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM64803"Using the NET.CFG Reference PagesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64803"24RENDERAS="SECT1"IntroductionIDXID="w11535"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"IDXID="w11536"BOOK="_idx" COLLECTION="nw41" TIDREF="i760"
NET.CFG is the IDXID="w11537"BOOK="_idx" COLLECTION="nw41" TIDREF="i652"
configuration file that you use to specify nondefault value settings for your NetWare ClientTM software configuration options.IDXID="w11538"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
Use entries in the NET.CFG file to change the client workstation's network environment or configuration. For example, you might want to change the configuration in these cases:MARK=BULLETYou changed the default hardware settings on the network boardYou are using multiple protocolsYou are using the Novell® LAN Workplace® softwarePAGENUM=16 ID="BP26"Older versions of the DOS client workstation software used the SHELL.CFG file, which contained network configuration information specific to the shell and not to protocols or other layers. You can specify SHELL.CFG options in the NET.CFG file.RENDERAS="SECT1"ID="FM37540"Creating and 
Modifying a IDXID="w11539"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG 
FilePERFORMANCE="REQUIRED"Use a DOS text editor to type section headings and options in an existing NET.CFG file or a NET.CFG file that you create to set up your client workstation configuration. (The default location of the NET.CFG file is C:\NWCLIENT.)PERFORMANCE="REQUIRED"After a NET.CFG file is created or modified, copy or save the NET.CFG file to the client workstation diskette or directory.If all client workstations use the same NET.CFG file, you can save time by copying the file onto a master client workstation diskette, then copying the NET.CFG file to each client workstation. (The default location of the NET.CFG file is C:\NWCLIENT.)If each client workstation requires a unique NET.CFG file, you must copy a unique file to each client workstation diskette or directory.RENDERAS="SECT2"Entering Options and IDXID="w11540"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
Parameters into IDXID="w11541"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
the NET.CFG FileUse the following IDXID="w11542"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
conventions when IDXID="w11543"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
creating or modifying a IDXID="w11544"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file:MARK=BULLETType one option or parameter per line.Options and parameters are not case-sensitive unless used in quotation marks. Blank lines are ignored, but they can be helpful in separating the options and parameters to make the NET.CFG file easier to read.Enter options at the left margin of the file with no spaces before or after them.Each option can have several parameters.Enter parameters, one per line, below the option that they apply to, and indent each parameter line.Use the MOREINFO="NONE"Spacebar or MOREINFO="NONE"Tab key to indent parameters. Parameters must be indented at least one space.PAGENUM=17 ID="BP27"Place a hard return at the end of every line in the file, including the last line.If you don't put a return at the end of the last line, that line is ignored.Precede comment lines with a semicolon.User a semicolon (;) in front of a line to disable the option and parameter or write a comment.If a semicolon is placed in front of a NET.CFG option line, all of the parameters listed below are disabled.The following figure illustrates the NET.CFG file format.LABEL="2-1" FLOAT="0"ID="FM14458"NET.CFG File FormatFILEREF="c41tr21a.tif"PAGENUM=18 ID="BP28"RENDERAS="SECT2"Sample IDXID="w11545"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG FileFollowing is a sample NET.CFG file thatMARK=BULLETChanges the IRQ on the link driver to 4Changes the port to 340Sets up F: as the first network drive when logging in to the networkFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   ; Change the interrupt (IRQ) to 4
   int #1 4
   ; Change the port to 340 (hex)
   port #1 340FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   ; Set up F: as the first drive on network
   first network drive = fChanging the value setting in the NET.CFG does not change the hardware setting for the device you are using. Run the appropriate configuration utility or manually change the appropriate jumper settings to correspond with value setting used in the NET.CFG file.RENDERAS="SECT1"ID="FM83677"Using NET.CFG Options and 
ParametersIDXID="w11546"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NetWare and Personal NetWareTM workstations support the following configuration options in the 
NET.CFG file:MARK=BULLETIDREF="FM35992"Desktop SNMP OptionIDREF="FM65508"Link Driver OptionIDREF="FM35529"Link Support OptionIDREF="FM13477"Named Pipes OptionsIDREF="FM96250"NetBIOS OptionIDREF="FM76848"NetWare DOS Requester OptionPAGENUM=19 ID="BP29"IDREF="FM81529"NetWare DOS TSA OptionIDREF="FM17940"Protocol IPX OptionIDREF="FM61267"Protocol ODINSUP OptionIDREF="FM39423"Protocol RFCNBIOS OptionIDREF="FM64767"Protocol RPL OptionIDREF="FM51477"Protocol SPX OptionIDREF="FM83096"Protocol TCPIP OptionIDREF="FM73019"TBMI2 OptionIDREF="FM73159"Transport Provider IPX | UDP OptionBecause many products use the NET.CFG file for managing configuration information, this might not be a comprehensive list of all the options used in your NET.CFG file.  See the third-party manufacturer's product documentation or the most current README file provided with this NetWare Client for DOS and MS Windows kit for information.IDREF="FM27157"Figure 2-2 on page 20 shows the various parameters and 
values that you can use. Notice the following markings in figure text:* The default value is the maximum value for NetWare 2 and NetWare 3TM networks.+ This option is valid for NetWare 4TM networks only.PAGENUM=20 ID="BP30"LABEL="2-2" FLOAT="0"IDXID="w11547"BOOK="_idx" COLLECTION="nw41" TIDREF="i961"ID="FM27157"NET.CFG OptionsFILEREF="c41tr07a.tif"PAGENUM=21 ID="BP31"PAGENUM=22 ID="BP32"PAGENUM=23 ID="BP33"PAGENUM=24 ID="BP34"RENDERAS="SECT1"ID="FM64803"Using the NET.CFG Reference PagesThe following figure explains how to read the following NET.CFG reference pages in this chapter.LABEL="2-3" FLOAT="0"Format of NET.CFG Reference PagesFILEREF="c41tr08a.tif"RENDERAS="SECT1"PAGENUM=25 ID="BP35"ID="FM35992"Desktop SNMP OptionIDXID="w11548"BOOK="_idx" COLLECTION="nw41" TIDREF="i1003"
Use this IDXID="w11549"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option to manage MIB-II support and communities for SNMP desktops on NetWare and Personal NetWare networks.RENDERAS="SECT2"Available Parameters and Values for the Desktop SNMP OptionThis option has the following 
categories, 
parameters, and values, which are discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="17*"COLNAME=3 COLWIDTH="2*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CategoryCOLNAME=2 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78487"Asynchronous Timeout ConnectionsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99404"ASYNCHRONOUS TIMEOUT numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM99404"27COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM99276"Community Types and NamesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM71734"MONITOR COMMUNITY ["name | public | private"]IDREF="FM61013"CONTROL COMMUNITY ["name | public | private"]IDREF="FM27739"TRAP COMMUNITY ["name | public | private"]COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM71734"29 IDREF="FM61013"29IDREF="FM27739"30COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM85714"Community Access ManagementCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM58418"ENABLE MONITOR COMMUNITY [specified | any | off | omitted]IDREF="FM21722"ENABLE CONTROL COMMUNITY [specified | any | off | omitted]IDREF="FM91262"ENABLE TRAP COMMUNITY [specified | off | omitted]COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM58418"32IDREF="FM21722"32IDREF="FM91262"32COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM63339"MIB-II (Management Information Base) SupportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM63121"SNMPENABLEAUTHENTRAP [on | off]IDREF="FM37544"SYSCONTACT "contact"IDREF="FM61025"SYSLOCATION "location"IDREF="FM42412"SYSNAME "name"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM63121"36IDREF="FM37544"37IDREF="FM61025"37IDREF="FM42412"37PAGENUM=26 ID="BP36"RENDERAS="SECT2"ID="FM70245"DESKTOP SNMPSpecifies the IDXID="w11550"BOOK="_idx" COLLECTION="nw41" TIDREF="i1003"
desktop SNMP option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"desktop snmp  parameter_name valueReplace parameter_name with the name of the parameter you want to use.Replace value with the number or setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To identify the name of the system administrator for MIB II, you would place these lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  sysname "Suzanne Morley x893"For transport providers used with SNMP desktops, IDREF="FM73159"see "Transport Provider IPX | UDP Option" on page 207. RENDERAS="SECT2"ID="FM78487"Asynchronous Timeout ConnectionsUse this parameter and value to manage the timeout for asynchronous connections, which is discussed on the indicated page:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM99404"ASYNCHRONOUS TIMEOUT numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99404"27Desktop SNMP provides a way to monitor and control asynchronous connections for managing Desktop SNMP and other SNMP entities over asynchronous lines.PAGENUM=27 ID="BP37"RENDERAS="SECT3"ID="FM99404"ASYNCHRONOUS TIMEOUT numberMonitors and controls your SNMP connections.IDXID="w11551"BOOK="_idx" COLLECTION="nw41" TIDREF="i311"
When an SNMP manager requests information from a managed object, the desktop SNMP waits a set amount of time before attempting to cancel requests it has made against managed objects.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"asynchronous timeout numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"For example, to have Desktop SNMP wait 35 system ticks (approximately 2 seconds) before attempting to cancel a request, you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  asynchronous timeout 35The timeout number is in ticks (18.21 ticks per second on IBM* PCs and compatibles).RENDERAS="SECT2"ID="FM99276"Community Types and NamesUse these 
parameters and values to identify types and names of access control groups, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM71734"MONITOR COMMUNITY ["name | public | private"]IDREF="FM61013"CONTROL COMMUNITY ["name | public | private"]IDREF="FM27739"TRAP COMMUNITY ["name | public | private"]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM71734"29IDREF="FM61013"29IDREF="FM27739"30Desktop SNMP provides default community names for the monitor (read-only) and control (read/write) communities, as well as a default community types used for traps. Desktop SNMP and other SNMP entities use these types and names for access control. PAGENUM=28 ID="BP38"The community name contained in a request message from an SNMP management station must match the name expected by Desktop SNMP. For examples of complete files, IDREF="FM63443"see "Example of NET.CFG Files Using the Community Name and Types" on page 33.If Desktop SNMP receives a request protocol data unit (PDU) whose community name is not authorized, it does not respond to the request.  For example, suppose the control community name is "secret," and Desktop SNMP receives a SETRequest PDU with a community name of "public." Desktop SNMP discards the SETRequest UDP and does not respond to the UDP. However, Desktop SNMP does send an authentication trap to the trap targets if MOREINFO="NONE"SNMPENABLEAUTHENTRAPS ON. A community name can be any arbitrary, case-sensitive ASCII string up to 32 characters in length. It can include any characters except space, tab, open square bracket ( [ ), equal sign ( = ), colon ( : ), semicolon ( ; ), single quotation mark ( " ), or number sign ( # ).Community name strings are case-sensitive. Always enclose the community name string in double quotation marks.In the Desktop SNMP section of the NET.CFG file, you can define three communities, as described in the following table:LABEL="2-1" PGWIDE=0 TOCENTRY="1" Desktop SNMP Option Parameters for Community NamesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"control communityCOLNAME=2 ROTATE="0" MOREROWS="0"Describes the read/write community (the community that is allowed to do SET operations). Any community name established for read/write access is also valid for read-only access. The default value is "public." When the control community is disabled, all write access is disabled.COLNAME=1 ROTATE="0" MOREROWS="0"monitor community COLNAME=2 ROTATE="0" MOREROWS="0"Describes the read-only community (the community that is allowed to do GET and GET NEXT operations). The default value is "public." When the monitor community is disabled, all read access is disabled.COLNAME=1 ROTATE="0" MOREROWS="0"trap communityCOLNAME=2 ROTATE="0" MOREROWS="0"Describes the community name used for traps. The default value is "public." When the trap community name is disabled, Desktop SNMP does not send traps.PAGENUM=29 ID="BP39"RENDERAS="SECT3"ID="FM71734"MONITOR COMMUNITY ["name | public | private"]IDXID="w11552"BOOK="_idx" COLLECTION="nw41" TIDREF="i2504"
Specifies the monitor community name.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"monitor community ["nameMOREINFO="NONE" | public | private"]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"publicCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the monitor community as "private," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  monitor community "private" RENDERAS="SECT3"ID="FM61013"CONTROL COMMUNITY ["name | public | private"]IDXID="w11553"BOOK="_idx" COLLECTION="nw41" TIDREF="i819"
Specifies the control community name.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"control community ["nameMOREINFO="NONE" | public | private"]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"publicCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the control community as "secret," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  control community "secret" PAGENUM=30 ID="BP40"RENDERAS="SECT3"ID="FM27739"TRAP COMMUNITY ["name | public | private"]IDXID="w11554"BOOK="_idx" COLLECTION="nw41" TIDREF="i4568"
Specifies the trap community name.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"trap community ["nameMOREINFO="NONE" | public | private"]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"publicCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the trap community as "agenttrap," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  trap community "agenttrap" RENDERAS="SECT2"ID="FM85714"Community Access ManagementUse these
 parameters
 and values to manage access control of SNMP agents and resources, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="23*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and Values COLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM58418"ENABLE MONITOR COMMUNITY [specified | any | off | omitted]IDREF="FM21722"ENABLE CONTROL COMMUNITY [specified | any | off | omitted] IDREF="FM91262"ENABLE TRAP COMMUNITY [specified | off | omitted]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM58418"32IDREF="FM21722"32IDREF="FM91262"32Community types can also be disabled. When a community type is disabled, no management entity can access information for that community that you named. For example, if you disable the control community, no one can use Desktop SNMP to do SET operations against the data it manages. For examples of complete files, IDREF="FM63443"see "Example of NET.CFG Files Using the Community Name and Types" on page 33.PAGENUM=31 ID="BP41"Desktop SNMP reads the community name definition as follows, depending on the MOREINFO="NONE"enable community_typeMOREINFO="NONE" community line:LABEL="2-2" PGWIDE=1 TOCENTRY="1" Desktop SNMP Option Values for Community Type ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ValueCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AnyCOLNAME=2 ROTATE="0" MOREROWS="0"If MOREINFO="NONE"enable community_typeMOREINFO="NONE" community is set to "any" for a community type, any community string can be used to gain access. The line defining the community name can be omitted. If it is present, Desktop SNMP ignores it. For trap community strings, the "any" option is not applicable. If you specify MOREINFO="NONE"enable trap community any, Desktop SNMP interprets the line as if the community type were specified.COLNAME=1 ROTATE="0" MOREROWS="0"OffCOLNAME=2 ROTATE="0" MOREROWS="0"If MOREINFO="NONE"enable community_typeMOREINFO="NONE" community is set to "off" for a community type, access for that community type is disabled. The line defining the community name can be omitted. If the line is present, Desktop SNMP ignores it.COLNAME=1 ROTATE="0" MOREROWS="0"OmittedCOLNAME=2 ROTATE="0" MOREROWS="0"If MOREINFO="NONE"enable community_typeMOREINFO="NONE" community is set to "omitted" for a specific community type, Desktop SNMP defaults to "specified" for that community type and looks for a line defining a community name for the community type. If no community name is specified, Desktop SNMP defaults to "public."COLNAME=1 ROTATE="0" MOREROWS="0"SpecifiedCOLNAME=2 ROTATE="0" MOREROWS="0"If MOREINFO="NONE"enable community_typeMOREINFO="NONE" community is set to "specified" for a community type, Desktop SNMP uses the only the specified community name for that community type. If none is specified, Desktop SNMP defaults to "public."PAGENUM=32 ID="BP42"RENDERAS="SECT3"ID="FM58418"ENABLE MONITOR COMMUNITY [specified | any | off | omitted]IDXID="w11555"BOOK="_idx" COLLECTION="nw41" TIDREF="i1312"
Enables the value settings for the monitor community.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"enable monitor community [specified | any | off | omitted]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"specifiedCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable the monitor community as "private" only, you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  enable monitor community specifiedRENDERAS="SECT3"ID="FM21722"ENABLE CONTROL COMMUNITY [specified | any | off | omitted]IDXID="w11556"BOOK="_idx" COLLECTION="nw41" TIDREF="i1310"
Enables the value settings for the control community.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"enable control community [specified | any | off | omitted]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"specifiedCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable full access to the control community "secret," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  enable control community anyRENDERAS="SECT3"ID="FM91262"ENABLE TRAP COMMUNITY [specified | off | omitted]IDXID="w11557"BOOK="_idx" COLLECTION="nw41" TIDREF="i1315"
Enables the value settings for the trap community.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"enable trap community [specified | off | omitted]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"specifiedCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable the trap community name "agenttrap," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  enable trap community offPAGENUM=33 ID="BP43"RENDERAS="SECT4"ID="FM63443"Example of IDXID="w11558"BOOK="_idx" COLLECTION="nw41" TIDREF="i707"
NET.CFG Files Using the Community Name and TypesTo use the default trap IDXID="w11559"BOOK="_idx" COLLECTION="nw41" TIDREF="i710"
community, allow any IDXID="w11560"BOOK="_idx" COLLECTION="nw41" TIDREF="i708"
community name to be used for read access, but set the read/write community name to "secret," you would place the following lines in your NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   enable monitor community any
   enable control community specified
   control community "secret"To disable all traps and use the default values for the monitor and control communities, you would place the following lines in your NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   enable trap community offTo specify a NULL string for the control community and use the default values for the monitor and trap communities, you would place the following lines in your NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   enable control community specified
   control community ""Setting a NULL string is the same as setting the MOREINFO="NONE"enable community_typeMOREINFO="NONE" community line to "off."To allow only the "private" community to have access and set the community name for traps to "agenttrap," you would place the following lines in your NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
PAGENUM=34 ID="BP44"   enable monitor community specified
   monitor community "private"
   enable control community specified
   control community "private"
   enable trap community specified
   trap community "agenttrap"To temporarily allow any community name to have read-only access in the previous example, you would modify the lines in your NET.CFG file as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   enable monitor community any
   monitor community "private"
   enable control community specified
   control community "private"
   enable trap community specified
   trap community "agenttrap"Desktop SNMP ignores the MOREINFO="NONE"monitor community "private" line until you reset the MOREINFO="NONE"enable monitor community line to "specified." This allows you to temporarily change the value to "any" or "off" without deleting the specific community name.RENDERAS="SECT2"ID="FM63339"MIB-II (Management Information Base) SupportDesktop SNMP automatically supports three MIB-II 
groups: MARK=BULLETSystem and SNMP groupsInterface groupTCP/IP groups (all groups except interface, system, and SNMP, which are supported by other VLMTM files, and EGP and transmission, which are not supported)PAGENUM=35 ID="BP45"RENDERAS="SECT3"System and SNMP GroupsUse these 
parameters and values to define information that can be retrieved by IDXID="w11561"BOOK="_idx" COLLECTION="nw41" TIDREF="i4186"
SNMP management stations or reported in SNMP traps, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="23*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM63121"SNMPENABLEAUTHENTRAP [on | off]IDREF="FM37544"SYSCONTACT "contact"IDREF="FM61025"SYSLOCATION "location"IDREF="FM42412"SYSNAME "name"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM63121"36IDREF="FM37544"37IDREF="FM61025"37IDREF="FM42412"37Desktop IDXID="w11562"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
SNMP automatically supports two MIB-II groups, IDXID="w11563"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
systemIDXID="w11564"BOOK="_idx" COLLECTION="nw41" TIDREF="i4380"
 and IDXID="w11565"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
SNMP. These groups provide SNMP management stations with information about your workstation and about Desktop SNMP.You can define some parameters for your workstation environment in the NET.CFG file (or other defined configuration file). The following table explains these parameters.LABEL="2-3" PGWIDE=1 TOCENTRY="1" Desktop SNMP Option Parameters for MIB-II SupportCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"snmpenableauthentrapCOLNAME=2 ROTATE="0" MOREROWS="0"The snmpenableauthentraps parameter defaults to "off." When set to "on," it instructs Desktop SNMP to send a trap message if someone without proper access tries to use SNMP to get or change information that Desktop SNMP manages.COLNAME=1 ROTATE="0" MOREROWS="0"syscontactCOLNAME=2 ROTATE="0" MOREROWS="0"Use the real name of the person who should be contacted if your workstation needs maintenance.COLNAME=1 ROTATE="0" MOREROWS="0"syslocationCOLNAME=2 ROTATE="0" MOREROWS="0"Use the physical location of your workstation.COLNAME=1 ROTATE="0" MOREROWS="0"sysnameCOLNAME=2 ROTATE="0" MOREROWS="0"Use your user or login name---or your  TCP/IP host name, if one is assigned. PAGENUM=36 ID="BP46"Each of these parameters is optional and can be used in groups or separately.The first parameter enables the workstation to notify a network supervisor that an unauthorized user is trying to access the workstation without proper authority.The last three parameters define information that can be retrieved by SNMP management stations or reported in SNMP traps.Following is an example of a NET.CFG entry that notifies Suzanne Morley that an unauthorized user is tying to access the network:FORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   sysname "Suzanne Morley x893"
   syslocation "Building 2"
   syscontact "suzanne@acompany.com"
   snmpenableauthentraps onAlways enclose the name, location, or contact information in quotation marks.RENDERAS="SECT3"ID="FM63121"SNMPENABLEAUTHENTRAP [on | off]IDXID="w11566"BOOK="_idx" COLLECTION="nw41" TIDREF="i4191"
Instructs the Desktop SNMP to send a trap message if someone without proper access tries to use SNMP to get or change information that Desktop SNMP manages.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"snmpenableauthentrap [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase security on your workstation, you would enable the Desktop SNMP to send a trap message to the manager by placing the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  snmpenableauthentrap onPAGENUM=37 ID="BP47"RENDERAS="SECT3"ID="FM37544"SYSCONTACT "contact"IDXID="w11567"BOOK="_idx" COLLECTION="nw41" TIDREF="i4366"
Informs the SNMP manager of your workstation's system administrator.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"syscontact "contact"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To notify the SNMP manager that the name of your workstation's system administrator is "Bob Jones" at "x324," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  syscontact "Bob Jones x324"RENDERAS="SECT3"ID="FM61025"SYSLOCATION "location"IDXID="w11568"BOOK="_idx" COLLECTION="nw41" TIDREF="i4369"
Informs the SNMP manager of the physical location of your workstation.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"syslocation "locationMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To notify the SNMP manager that your workstation is in "Building 2," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  syslocation "Building 2"RENDERAS="SECT3"ID="FM42412"SYSNAME "name"IDXID="w11569"BOOK="_idx" COLLECTION="nw41" TIDREF="i4370"
Informs the SNMP manager of your username.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"sysname "nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To notify the SNMP manager of your username "Suzanne," you would place the following lines in your NET.CFG file:MOREINFO="NONE"desktop snmpMOREINFO="NONE"  sysname "Suzanne"PAGENUM=38 ID="BP48"RENDERAS="SECT3"Interface GroupIDXID="w11570"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
Desktop SNMP provides a separate VLM file, MIB2IF.VLM, that supports the interface group. This IDXID="w11571"BOOK="_idx" COLLECTION="nw41" TIDREF="i1849"
group provides information about your network connection, such as the number of packets transmitted and received and whether it is Ethernet or token ring.Add the following lines to the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm=mib2if.vlmAlways place the MOREINFO="NONE"vlm=mib2if.vlm line after the lines that load the Desktop SNMP VLM suite of files.RENDERAS="SECT3"TCP/IP GroupsIDXID="w11572"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
Desktop IDXID="w11573"BOOK="_idx" COLLECTION="nw41" TIDREF="i4451"
SNMP also provides a separate VLM file, MIB2PROT.VLM, that supports the TCP/IP groups (all groups except interface, system, and SNMP, which are supported by other VLM files, and EGP and transmission, which are not supported). Load this VLM when you are using the TCP/IP stack from LAN WorkPlace® software.Add the following lines to the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm=mib2prot.vlmAlways place the MOREINFO="NONE"vlm=mib2prot.vlm line after the lines that load the Desktop SNMP VLM suite of files.PAGENUM=39 ID="BP49"RENDERAS="SECT3"Example of NET.CFG File Including Each Group SupportIDXID="w11574"BOOK="_idx" COLLECTION="nw41" TIDREF="i2444"
On a IDXID="w11575"BOOK="_idx" COLLECTION="nw41" TIDREF="i4380"
workstation IDXID="w11576"BOOK="_idx" COLLECTION="nw41" TIDREF="i1849"
where IDXID="w11577"BOOK="_idx" COLLECTION="nw41" TIDREF="i4451"
the IDXID="w11578"BOOK="_idx" COLLECTION="nw41" TIDREF="i4186"
NetWare DOS RequesterTM and comprehensive MIB-II support are both loaded, the entire Netware DOS Requester and Desktop SNMP sections of your NET.CFG file might read as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm=wssnmp.vlm
   vlm=wstrap.vlm
   vlm=wsreg.vlm
   vlm=wsasn1.vlm
   vlm=mib2if.vlm
   vlm=mib2prot.vlmFORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   sysname "Suzanne Morley x893"
   syslocation "Building 2"
   syscontact "Suzanne@acompany.com"
   snmpenableauthentraps onRENDERAS="SECT1"ID="FM65508"Link Driver OptionIDXID="w11579"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"
Use this IDXID="w11580"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option to specify the hardware and software configurations of the IDXID="w11581"BOOK="_idx" COLLECTION="nw41" TIDREF="i1231"
LAN drivers for each IDXID="w11582"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
network board in your workstation. The value settings you specify for each parameter with this option should match the hardware and software settings for your network board. This option also allows you to set up the proper frame type and protocols for NetWare supported LAN drivers.PAGENUM=40 ID="BP50"RENDERAS="SECT2"Available Parameters and Values for the Link Driver OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM12007"ACCM [remote_host_address]IDREF="FM51142"ACCOMP [yes | no]IDREF="FM46032"ALTERNATE  IDREF="FM19947"AUTHEN PAP username passwordIDREF="FM40590"BAUD baud_rateIDREF="FM22860"BUS ID name number  IDREF="FM82966"COUNTER [protocol] timeout max_config max_term max_nak IDREF="FM18937"DIAL phone_number IDREF="FM13749"DIRECT [yes | no] IDREF="FM40017"DMA [#1 | #2] channel_numberIDREF="FM67805"FRAME frame_type_name [addressing_mode] IDREF="FM19377"IRQ [#1 | #2] interrupt_request_numberIDREF="FM25731"IPADDR [remote_host_address] IDREF="FM31144"LINK STATIONS numberIDREF="FM30258"LISTENIDREF="FM31874"MAGIC numberIDREF="FM35848"MAX FRAME SIZE numberIDREF="FM32376"MEM [#1 | #2] hex_starting_address [hex_length] IDREF="FM12376"MRU number [m] IDREF="FM64936"NODE ADDRESS hex_address [mode]IDREF="FM39667"OPENIDREF="FM10076"PCOMP [yes | no]  IDREF="FM95912"PORT [#1 | #2] hex_starting_address [hex_number_of_ports] IDREF="FM56496"PROTOCOL "name" hex_protocol_ID frame_typeIDREF="FM33016"SAPS number IDREF="FM12602"SLOT number  IDREF="FM25970"TCPIPCOMP [vj | no] slots comp_slotCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM12007"42IDREF="FM51142"43IDREF="FM46032"44IDREF="FM19947"44IDREF="FM40590"45IDREF="FM22860"45IDREF="FM82966"46IDREF="FM18937"48IDREF="FM13749"49IDREF="FM40017"49IDREF="FM67805"50IDREF="FM19377"57IDREF="FM25731"58IDREF="FM31144"59IDREF="FM30258"59IDREF="FM31874"60IDREF="FM35848"61IDREF="FM32376"62IDREF="FM12376"62IDREF="FM64936"63IDREF="FM39667"64IDREF="FM10076"66IDREF="FM95912"66IDREF="FM56496"67IDREF="FM33016"72IDREF="FM12602"73IDREF="FM25970"74PAGENUM=41 ID="BP51"RENDERAS="SECT2"ID="FM39992"LINK DRIVER driver_nameSpecifies the IDXID="w11583"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"
LAN driver you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"link driver driver_name    parameter_name, valueReplace driver_name with the name of the LAN driver.Replace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.(IDREF="FM49865"See Table 2-6, "List of ODI LAN Driver Names and Supported Network Boards," on page 75for more information.)COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure an NE2000TM driver, you could typeMOREINFO="NONE"link driver ne2000MOREINFO="NONE"  int 5MOREINFO="NONE"  port 360MOREINFO="NONE"  frame ethernet_802.2RENDERAS="SECT3"ID="FM12007"ACCM [remote_host_address]IDXID="w11584"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Specifies whether the PPP protocol should use the asynchronous control character map (ACCM). IDXID="w11585"BOOK="_idx" COLLECTION="nw41" TIDREF="i59"
ACCM is a configuration option that provides a way to negotiate the use of control characters (0x0 through 0x1F) for mapping on an asynchronous link.When sending data, each character with a value less than 0x20 that is flagged in the remote ACCM is replaced by a two-byte sequence consisting of the Control-Escape character (0x7D) and the original character with bit 6 complemented. PAGENUM=42 ID="BP52"Conversely, when receiving data, the mapped two-character sequence is converted back to the original character.The eight hexadecimal bytes in ACCM use bit numbering from 31 to 0, from left to right. Each numbered bit corresponds to a control character with the same number value. When the bit is set to 0, the character does not need to be mapped; when the bit is set to 1, the character needs to be mapped.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"accm [remote_host_addressMOREINFO="NONE"]Replace remote_host_address with the correct address for that host.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"ffffffffCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the remote host to escape XON (0x11) and XOFF (0x13) characters, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  accm 000A0000RENDERAS="SECT3"ID="FM51142"ACCOMP [yes | no]IIDXID="w11586"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
nstructs the IDXID="w11587"BOOK="_idx" COLLECTION="nw41" TIDREF="i60"
PPP protocol to compress the address and control field of the PPP header.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"accomp [yes | no]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"noCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To instruct the PPP protocol to compress the address and control field of the PPP header, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  accomp yesPAGENUM=43 ID="BP53"RENDERAS="SECT3"ID="FM46032"ALTERNATEIDXID="w11588"BOOK="_idx" COLLECTION="nw41" TIDREF="i166"
Specifies an alternate network board. Normally, the LANSUP and NTR2000 drivers use the primary board. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"alternateCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the LANSUP.COM driver to use an alternate network board, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver lansupMOREINFO="NONE"  alternateRENDERAS="SECT3"ID="FM19947"AUTHEN PAP username passwordSpIDXID="w11589"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
ecifies whether the IDXID="w11590"BOOK="_idx" COLLECTION="nw41" TIDREF="i350"
PPP protocol should use authentication. If selected, PPP uses the username and password to identify the local system to the peer host. This process is based on the Password Authentication Protocol (PAP). If this parameter is specified, a local username and password database are formed to authenticate a remote host. Up to five remote host entries can be entered in the NET.CFG file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"authen pap usernameMOREINFO="NONE" passwordCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable PAP and specify a username and password for a remote host with the name "brent" and a password "rmt12434", you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  authen pap brent rmt12434Maximum size of username and password database is 32 bytes.PAGENUM=44 ID="BP54"RENDERAS="SECT3"ID="FM40590"BAUD baud_rateIDXID="w11591"BOOK="_idx" COLLECTION="nw41" TIDREF="i423"
Specifies the baud rate for the SLIP_PPP driver to use. The baud rate values are 300, 1200, 2400, 4800, 9600, 14400, 19200, and 38400.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"baud baud_rateCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"2400COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"300 to 38400COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a baud rate of 9600, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  baud 9600RENDERAS="SECT3"ID="FM22860"BUS ID name numberIDXID="w11592"BOOK="_idx" COLLECTION="nw41" TIDREF="i555"
Specifies the bus that the network board is inserted into. Use this parameter with LAN drivers that support multiple bus types.The currently defined bus ID types and numbers are as follows:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Bus TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Identification NumberVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ISACOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"MCACOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"EISACOLNAME=2 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"PCMCIACOLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"PCICOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"VL (VESA Local Bus)COLNAME=2 ROTATE="0" MOREROWS="0"5PAGENUM=45 ID="BP55"This is not a conclusive list of bus types. You can obtain an updated list of identifiers from the Novell LabsTM facility.  The default value indicates that the LAN driver should search each of the machine's buses for a supported network board. The LAN driver should then initialize the first supported network board it finds. The LAN driver determines the order that the buses are searched in.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"bus id nameMOREINFO="NONE" numberReplace name with the name of the bus type you want to use. Replace number with the identification number that corresponds with the bus type that you want to use.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"-1 0FFhCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the bus type for an ISA adapter, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ntr2000MOREINFO="NONE"  bus id isa 0RENDERAS="SECT3"ID="FM82966"COUNTER [protocol] timeout max_config max_term max_nakSpecifies a protocol, which can be any of the following:MARK=BULLETLCP (Link Control Protocol)IPCP (Internet Protocol Control Protocol)PAP (Password Authentication Protocol)If the protocol value is not specified, changes are applied to each of the listed protocols.PAGENUM=46 ID="BP56"This parameter also IDXID="w11593"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
specifies a timeout value and three retry counters for the IDXID="w11594"BOOK="_idx" COLLECTION="nw41" TIDREF="i858"
PPP protocol. All values are in decimal. The available values and descriptions are as follows:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"timeoutCOLNAME=2 ROTATE="0" MOREROWS="0"The timeout value for restarting the transmission of request packets.COLNAME=1 ROTATE="0" MOREROWS="0"max_configCOLNAME=2 ROTATE="0" MOREROWS="0"The maximum number of retries for sending a configuration request.COLNAME=1 ROTATE="0" MOREROWS="0"max_termCOLNAME=2 ROTATE="0" MOREROWS="0"The maximum number of retries for sending a terminate request. This value is not used by PAP. COLNAME=1 ROTATE="0" MOREROWS="0"max_nakCOLNAME=2 ROTATE="0" MOREROWS="0"The maximum number of retries for sending a configuration NAK.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"counter [protocol] timeoutMOREINFO="NONE" max_configMOREINFO="NONE" max_termMOREINFO="NONE" max_nakCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The values are defined as follows:MARK=BULLETprotocol can be LCP, IPCP, or PAPtimeout restarts timer timeout in secondsmax_config retries counter for configuration requestmax_term retries counter for terminate requestmax_nak retries counter for configuration NAKCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a timeout value and three retry counters for the PAP protocol, you could place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  counter pap 5 10 5 10PAGENUM=47 ID="BP57"RENDERAS="SECT3"ID="FM18937"DIAL phone_numberIDXID="w11595"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Specifies a phone number for the IDXID="w11596"BOOK="_idx" COLLECTION="nw41" TIDREF="i1033"
SLIP_PPP driver to call when it is loaded. This parameter is used only when the DIRECT parameter is set to a value of "no."This parameter accepts all dial modifiers supported by your modem, up to 30 characters maximum. For example, the Hayes* Smartmodem 9600* modem supports the following list of characters:TYPE="VERT"0-9,*,#,A,B,C,D and -,(,),,,P,T.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"dial phone_numberReplace phone_number with any of the dial modifiers supported by your modem, up to 30 characters maximum.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the phone number "9, (801) 328-7000" for a 9600 baud Hayes Smartmodem 9600, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  direct noMOREINFO="NONE"  dial p9,801,3287000The p indicates pulse dialing; the default is tone dialing.For this parameter to work, also set the DIRECT parameter to a value of "no."PAGENUM=48 ID="BP58"RENDERAS="SECT3"ID="FM13749"DIRECT [yes | no]IDXID="w11597"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Selects whether the IDXID="w11598"BOOK="_idx" COLLECTION="nw41" TIDREF="i1036"
SLIP or PPP link is direct. Set this parameter to "no" only if you plan to use the DIAL or LISTEN parameters.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"direct [yes | no]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"YesCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that you want to use the DIAL parameter, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  direct noRENDERAS="SECT3"ID="FM40017"DMA [#1 | #2] channel_numberIDXID="w11599"BOOK="_idx" COLLECTION="nw41" TIDREF="i1163"
Specifies the hardware setting of the network board used in the workstation. It allows DMA channels to be configured.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"dma [#1 | #2] channel_numberEnter the channel number to be used. You can specify two DMA values.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"#1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"If the first configurable DMA channel on your NE2100TM network board uses DMA channel 3 and the second configurable channel uses channel 4, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  dma #1 3MOREINFO="NONE"  dma #2 4 PAGENUM=49 ID="BP59"RENDERAS="SECT3"ID="FM67805"FRAME frame_type_name [addressing_mode]IDXID="w11600"BOOK="_idx" COLLECTION="nw41" TIDREF="i1564"
Enables the frame types used by the LAN driver. When the LAN driver initializes the network board, it creates a logical board for the frame type name that is specified. You can create multiple frame types concurrently on each client workstation. This parameter also allows for configuration of the addressing mode for some LAN drivers on the basis of frame types. The following keywords determine the address mode:MARK=BULLETLSB canonical addressing modeMSB non-canonical addressing modeFor example, the frame type Token-Ring can be used in LSB, and Token-Ring_SNAP can be used in MSB.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"frame frame_type_nameMOREINFO="NONE" [addressing_modeMOREINFO="NONE"]Replace frame_type_name with the supported frame type of the network you are connecting to.Replace addressing_mode with the address mode for your frame type.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Ethernet LAN drivers: Ethernet_802.2  Token-ring LAN drivers: Token-Ring  TCP/IP LAN driver SLIP_PPP: SLIPIDREF="FM57837"See Table 2-4, "List of Frame Types, Protocols, and LAN Drivers," on page 51for more information.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable the Token-Ring_SNAP frame type for an NTR2000 LAN driver, you would place the following lines in your NET.CFG file: MOREINFO="NONE"link driver ntr2000  token-ring_snap lsbTo enable the Ethernet_II and Ethernet 802.2 frame type for an NE2000 LAN driver, you would place the following lines in your NET.CFG file (for two logical networks):MOREINFO="NONE"link driver ne2000MOREINFO="NONE"  frame ethernet_iiMOREINFO="NONE"  frame ethernet_802.2PAGENUM=50 ID="BP60"The NetWare Client binds to the first frame type listed under the LINK DRIVER heading. RENDERAS="SECT2"Frame Types, Protocols, and LAN DriversThe following table shows the frame types currently defined by Novell and their respective protocols. Included is a list of the supporting LAN drivers for each frame type that currently ship with the NetWare Client Kit for DOS and MS Windows.LABEL="2-4" PGWIDE=1 TOCENTRY="1"ID="FM57837" List of Frame Types, Protocols, and LAN DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Frame Type and DescriptionCOLNAME=2 ROTATE="0" MOREROWS="0"ProtocolsCOLNAME=3 ROTATE="0" MOREROWS="0"LAN DriversVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"3270_COAXAHarris Adacom frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"802.4 Token-passing bus envelope COLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"DATACO_OSIDataco frame envelope COLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"ETHERNET_802.2Ethernet (802.3) using an 802.2 envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX  NetBIOS  RPL  SNACOLNAME=3 ROTATE="0" MOREROWS="0"3C1100, 3C501, 3C501, 3C503, 3C505, 3C523, 3C5X9, CEODI, E20ODI, E2HODI, E30ODI, E31ODI, ES3210, EXP16ODI, HPMCAODI, IBMFDDIO, IBMODISH, ILANAT, INTEL593, INTEL595, INTEL596, LANSUP, NCRWL05, NE1000, NE1500T, NE2, NE2_32, NE2000, NE2100, NE3200, NI5210, NI6510, NI9210, ODINSUP, PCMDM, PE2ODI, SMC8000, TCE16ATW, TCE16MCW, TCE32MCW, TCNSW, UBODICOLNAME=1 ROTATE="0" MOREROWS="0"ETHERNET_802.3 IPX 802.3 raw encapsulationCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=3 ROTATE="0" MOREROWS="0"3C1100, 3C501, 3C501, 3C503, 3C505, 3C523, 3C5X9, CEODI, E20ODI, E2HODI, E30ODI, E31ODI, ES3210, EXP16ODI, HPMCAODI, IBMFDDIO, IBMODISH, ILANAT, INTEL593, INTEL595, INTEL596, NCRWL05, NE1000, NE1500T, NE2, NE2_32, NE2000, NE2100, NE3200, NI5210, NI6510, NI9210, ODINSUP, PCMDM, PE2ODI, SMC8000, TCE16ATW, TCE16MCW, TCE32MCW, TCNSW, UBODICOLNAME=1 ROTATE="0" MOREROWS="0"ETHERNET_II Ethernet using a DEC Ethernet II envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"AARP  AppleTalk*  ARP  IP  IPX/SPX  RARP  XNS*COLNAME=3 ROTATE="0" MOREROWS="0"3C1100, 3C501, 3C501, 3C503, 3C505, 3C523, 3C5X9, CEODI, E20ODI, E2HODI, E30ODI, E31ODI, ES3210, EXOS, EXP16ODI, HPMCAODI, IBMFDDIO, IBMODISH, ILANAT, INTEL593, INTEL595, INTEL596, NCRWL05, NE1000, NE1500T, NE2, NE2_32, NE2000, NE2100, NE3200, NI5210, NI6510, NI9210, ODINSUP, PCMDM, PE2ODI, SMC8000, TCE16ATW, TCE16MCW, TCE32MCW, TCNSW, UBODICOLNAME=1 ROTATE="0" MOREROWS="0"ETHERNET_SNAPEthernet (802.3) using an 802.2 envelope with SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"AARP  AppleTalk 8000  ARP  IP  IPX/SPX  RARP  XNSCOLNAME=3 ROTATE="0" MOREROWS="0"3C1100, 3C501, 3C501, 3C503, 3C505, 3C523, 3C5X9, CEODI, E20ODI, E2HODI, E30ODI, E31ODI, ES3210, EXOS, EXP16ODI, HPMCAODI, IBMFDDIO, IBMODISH, ILANAT, INTEL593, INTEL595, INTEL596, LANSUP, NCRWL05, NE1000, NE1500T, NE2, NE2_32, NE2000, NE2100, NE3200, NI5210, NI6510, NI9210, ODINSUP, PCMDM, PE2ODI, SMC8000, TCE16ATW, TCE16MCW, TCE32MCW, TCNSW, UBODICOLNAME=1 ROTATE="0" MOREROWS="0"FDDI_802.2FDDI using an 802.2 envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX  RPL  SNACOLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"FDDI_SNAP FDDI using 802.2 with an SNAP envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"AARP  AppleTalk 80007  ARP  IP  IPX/SPX  RARP  XNS COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"Frame_RelayNovell frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"GNET Gateway G/Net frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"IBM_PCN2_802.2COLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX  NETBIOSCOLNAME=3 ROTATE="0" MOREROWS="0"LANSUP, PCN2COLNAME=1 ROTATE="0" MOREROWS="0"IBM_PCN2_SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"IP  IPX/SPX  NETBIOSCOLNAME=3 ROTATE="0" MOREROWS="0"LANSUP, PCN2COLNAME=1 ROTATE="0" MOREROWS="0"IBM_SDLCNovell frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"IP IP Tunnel frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IP  IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"ISDNIntegrated Services Digital Network (not available) COLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"IVDLAN_802.9 Commutex, Inc. frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"IWI_BUS-NET_SNAPIntegrated Workstations frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"LANPAC_II Racore frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"LOCALTALKThe Apple* LocalTalk* frame COLNAME=2 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"NOVELL_RX-NETNovell RX-NetTM envelope COLNAME=2 ROTATE="0" MOREROWS="0"IP  IPX/SPXCOLNAME=3 ROTATE="0" MOREROWS="0"SMCARCWS, TCCARC, TRXNETCOLNAME=1 ROTATE="0" MOREROWS="0"OMNINET/4 Corvus frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"PCO_FDDITP PC Office frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"PRONET-10Proteon* ProNET* I/O frame envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"PPPNovell frame type COLNAME=2 ROTATE="0" MOREROWS="0"IP COLNAME=3 ROTATE="0" MOREROWS="0"SLIP_PPPCOLNAME=1 ROTATE="0" MOREROWS="0"RANGELANProxim frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"SLIPNovell frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"IP  IPX  LATCOLNAME=3 ROTATE="0" MOREROWS="0"SLIP_PPPCOLNAME=1 ROTATE="0" MOREROWS="0"SNA_LINKSNovell frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"Token-Ring Token ring (802.5) using an 802.2 envelopeCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPX  RPL  SNA  NetBIOSCOLNAME=3 ROTATE="0" MOREROWS="0"LANSUP, MADGEODI, NTR2000, ODINSUP, OSH391R, OSH392R, OSH89XR, OSH990R, SMC8100, T20ODI, T30ODI, TCTOKSH, NTR2000COLNAME=1 ROTATE="0" MOREROWS="0"Token Ring_SNAP Token ring (802.5) using an 802.2 envelope with SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=3 ROTATE="0" MOREROWS="0"LANSUP, MADGEODI, NTR2000, ODINSUP, OSH391R, OSH392R, OSH89XR, OSH990R, SMC8100, T20ODI, T30ODI, TCTOKSH, NTR2000COLNAME=1 ROTATE="0" MOREROWS="0"VIRTUAL_LANFor use where no Frame ID/MAC envelope is necessaryCOLNAME=2 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"WAIDNETHypercommunications frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"WAN_Client_LANNovell frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--COLNAME=1 ROTATE="0" MOREROWS="0"X.25Novell frame type COLNAME=2 ROTATE="0" MOREROWS="0"Unknown COLNAME=3 ROTATE="0" MOREROWS="0"--PAGENUM=55 ID="BP61"-- Currently, no LAN drivers supporting this frame type are available in the NetWare Client for DOS and MS Windows Client kit. Contact third-party vendors for details.You can specify more than one frame type statement for a single driver.For example, you can specify that an Ethernet NE2000 board can use both Ethernet_802.2 and Ethernet_802.3 frame types. 802.2 is the type of communications sent on one network, and 802.3 is the type of communication sent on the other network.RENDERAS="SECT3"ODINSUP LAN DriverIf you are using the ODINSUP LAN driver, you must enable multiple frame types for each driver. For more information about ODINSUP, see Chapter 12, "BOOK="ws_d1enu" COLLECTION="nw41"Setting Up the NetWare ODI Interface for NDIS Protocols," in NetWare Client for DOS and MS Windows User Guide for information.RENDERAS="SECT3"Ethernet LAN DriversFor Ethernet, enable Ethernet_802.3, Ethernet_II, Ethernet_802.2, and Ethernet_SNAP frame types.You can use up to four frame types for a single Ethernet cable segment. You can use either four network boards each with one frame type defined, or you can use one network board with four frames defined, or any similar combination. RENDERAS="SECT3"Token-Ring LAN DriversFor token ring, enable token ring and Token Ring_SNAP frame types. You can use up to two frame types for a single token-ring cable segment. PAGENUM=56 ID="BP62"RENDERAS="SECT3"ID="FM19377"IRQ [#1 | #2] interrupt_request_numberIDXID="w11601"BOOK="_idx" COLLECTION="nw41" TIDREF="i1984"
Specifies which interrupt (IRQ) the network board is set to use. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"irq [#1 | #2] interrupt_request_numberUse the same interrupt request number that is set on the network board.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"#1See your LAN driver documentation for the specific IRQ default values. COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify interrupt 5 on an NE2100 network board, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  irq 5To specify more than one interrupt request number, you could place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  irq #1 5MOREINFO="NONE"  irq #2 3 The syntax for this parameter has changed from INT to IRQ. The INT syntax is still supported, but it is recommended that you update client workstations to use IRQ.Before changing the value of the interrupt request number for your network board, be sure you know what interrupt value settings are used on other hardware (such as monitors) that you are using. For example, interrupts 2 and 9 through 15 are usually reserved, so don't use those numbers (especially 2) for your network board. We recommend using 3, 5, or 7 for most network boards. PAGENUM=57 ID="BP63"The default interrupt value of your COMn device for the SLIP_PPP driver is 4 for
COM1.
Other standard interrupt values for COMn ports are as follows: COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PortCOLNAME=2 ROTATE="0" MOREROWS="0"Int (Interrupt)VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"COM1COLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"COM2COLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"COM3COLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"COM4COLNAME=2 ROTATE="0" MOREROWS="0"3The SLIP_PPP driver's internal dial or answer capability (when set up to use an INDIRECT connection) requires that the modem be set up to track the status of a carrier detect signal (with the &C1 AT command in effect). The SLIP_PPP driver assumes the line is on and does not dial or answer if the modem's DCD is asserted.  If you are using a PS/2* computer on a token ring network, do not autoconfigure with the CLASS=DISKReference diskette. Doing so might cause problems.RENDERAS="SECT3"ID="FM25731"IPADDR [remote_host_address]IDXID="w11602"BOOK="_idx" COLLECTION="nw41" TIDREF="i1907"
Specifies the IP addresses for IDXID="w11603"BOOK="_idx" COLLECTION="nw41" TIDREF="i1919"
PPP negotiation (in dotted decimal notation). If the remote_host_address value is specified, PPP tries to assign the address to the remote host if the remote host did not specify an address to use in its configuration request.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ipaddr remote_host_addressReplace remote_host_address with the correct address for that host.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the correct IP address for the remote host "129.47.30.6", you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  ipaddr 129.47.30.6PAGENUM=58 ID="BP64"RENDERAS="SECT3"ID="FM31144"LINK STATIONS numberIDXID="w11604"BOOK="_idx" COLLECTION="nw41" TIDREF="i2118"
Specifies the number of link stations needed for the LANSUP driver. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"link stations numberSet this parameter to allow for all applications using the IBM* LAN Support Program. The maximum value depends on the type of network board used.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify five links on an NE2100 network board, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver lansupMOREINFO="NONE"  link stations 5LINK STATIONS is ignored if another application already opened the adapter before the LANSUP.COM driver was loaded.RENDERAS="SECT3"ID="FM30258"LISTENIDXID="w11605"BOOK="_idx" COLLECTION="nw41" TIDREF="i2486"
Signifies the passive end of a modem connection for the IDXID="w11606"BOOK="_idx" COLLECTION="nw41" TIDREF="i2130"
SLIP or PPP protocol.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"listenCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To signify passive end of a modem connection, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  direct noMOREINFO="NONE"  listenFor this parameter to work, also set the DIRECT parameter to "no."PAGENUM=59 ID="BP65"RENDERAS="SECT3"ID="FM31874"MAGIC numberIDXID="w11607"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Provides a way to detect looped-back links and other data-link anomalies. The value specified is used by the IDXID="w11608"BOOK="_idx" COLLECTION="nw41" TIDREF="i2299"
SLIP_PPP driver as a seed number to generate a unique number for process recognition. If remote is specified, PPP tries to get the peer to use the number specified (if the peer does not indicate that it uses the magic number in its initial configuration request). This parameter is a four-byte hexadecimal number.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"magic numberReplace number with a unique number that is specified by the remote host.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"DisabledCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the magic number "1243FFFF", you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  magic 1243ffffPAGENUM=60 ID="BP66"RENDERAS="SECT3"ID="FM35848"MAX FRAME SIZE numberIDXID="w11609"BOOK="_idx" COLLECTION="nw41" TIDREF="i2350"
Sets the IDXID="w11610"BOOK="_idx" COLLECTION="nw41" TIDREF="i1566"
maximum number of bytes that can be put on the network by the NTR2000.COM and LANSUP.COM LAN drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"max frame size numberIf the line speed is 16 Mbps, the value for number must be between 638 and 17,954. If the line speed is 4 Mbps, the value must be between 638 and 4464.The value must include the number of bytes for the data packet (usually 1, 2, 4, or 8KB), and for the largest possible header (currently, 52 bytes LAN header + 74 bytes protocol header = 126 bytes).For example, to use 2KB data packets, you would calculate the value for number as2048 + 52 + 74 = 2174COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The NTR2000.COM driver's default size is 4222 bytes. But if your network board has 8 KB of shared RAM available, the default size is 2174 bytes.The LANSUP.COM driver's default is 1150 bytes. But if you're using the IBM LAN Support Program with an Ethernet network board driver, the maximum size is 1496 bytes.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the maximum frame size of an NTR2000 LAN driver, you would place the following line in your NET.CFG file:MOREINFO="NONE"link driver ntr2000MOREINFO="NONE"  max frame size 2174If you are running MS Windows in enhanced mode, the VIPX.386 device driver requires the maximum frame size to be less than 8000 bytes. If the frame size exceeds 8000 bytes, network communication fails.  If you are running TBMI2.COM or TASKID, you can't use MAX FRAME SIZE.PAGENUM=61 ID="BP67"RENDERAS="SECT3"ID="FM32376"MEM [#1 | #2] hex_starting_address [hex_length]IDXID="w11611"BOOK="_idx" COLLECTION="nw41" TIDREF="i2372"
Specifies a memory range to be used by the network board.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"mem [#1 | #2] hex_starting_addressMOREINFO="NONE" [hex_lengthMOREINFO="NONE"]Replace hex_starting_address with the hexadecimal physical (absolute) address of the memory used by the network board. Replace the hex_length with the memory address range (in hexadecimal paragraphs, with each paragraph being 16 bytes) used by the network board. Usually, the hex length is not needed.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"#1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"When the node address on a network board is set from D0000 to D4000 (bytes), the starting address is D0000 and the range is 400 hexadecimal paragraphs. Therefore, for an NE2000 network board, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2000MOREINFO="NONE"  mem d0000 400Assign each board a unique memory range. Be sure you don't assign a range that is already used by other hardware. (VGA monitors commonly use A0000-C6FFF and XVGA monitors commonly use A0000-CFFFF.)RENDERAS="SECT3"ID="FM12376"MRU number [m]IDXID="w11612"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Specifies the maximum receive and transmit units (MRU) for the IDXID="w11613"BOOK="_idx" COLLECTION="nw41" TIDREF="i2530"
SLIP or 
PPP protocol.The SLIP_PPP driver uses half of the MRU as its largest receive size, and the protocol stack uses that receive size as the maximum datagram size it can send. PAGENUM=62 ID="BP68"The optional parameter "m" instructs the SLIP_PPP driver to assume the worst-case scenario for character mapping where every data byte in a packet is mapped into two bytes, as is required by the ACCM configuration. For example, a 500-byte packet could double its size to 1000 bytes.The optional parameter "m" applies to PPP only. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"mru numberMOREINFO="NONE" [m]Replace number with the maximum number of receive and transmit units for SLIP_PPP in decimal. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"PPP: 1500  SLIP: 1006COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"76 to 1500COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a size of 960 for the maximum size of receive and transmit units for the SLIP protocol, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  mru 960RENDERAS="SECT3"ID="FM64936"NODE ADDRESS hex_address [mode]IDXID="w11614"BOOK="_idx" COLLECTION="nw41" TIDREF="i2946"
Overrides the hard-coded node address in the LAN driver, if the hardware allows it. The new address is used to program the network board.Changing the node address for a network board can create conflicts with other LAN drivers. Use the hard-coded node address whenever possible.You can use either the canonical or non-canonical mode. Use the following keywords to determine the mode:MARK=BULLETLSB (canonical addressing mode)MSB (non-canonical addressing mode)For example, node addresses for both modes could appear as follows:PAGENUM=63 ID="BP69"MARK=BULLETnode address 0800005A656BL (canonical LSB)node address 1000005AA6D6M (non-canonical MSB)If the "M" or "L" is not specified, the default mode for the node address is the physical layer form of the address. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"node address hex_addressMOREINFO="NONE" [modeMOREINFO="NONE"]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the node address of an NTR2000 LAN driver to "1000005aa6d6" for non-canonical mode, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ntr2000MOREINFO="NONE"  node address 1000005aa6d6mEven though FDDI is a non-canonical topology at the physical layer, all address are sent and received in canonical (LSB) mode.  A node labeled with an "M" for non-canonical mode address supports media setup for canonical mode, because the LAN driver simply swaps the provided address to obtain the appropriate canonical (LSB) address.RENDERAS="SECT3"ID="FM39667"OPENThis parameter is supported by the PPP protocols for TCP/IP networks and the LANSUP software for IBM LAN Support programs.RENDERAS="SECT4"PPP ProtocolIDXID="w11615"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Specifies the active or passive open mode for the following IDXID="w11616"BOOK="_idx" COLLECTION="nw41" TIDREF="i3086"
PPP protocols:MARK=BULLETLCP Link Control ProtocolPAGENUM=64 ID="BP70"IPCP Internet Protocol Control ProtocolCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"open modeReplace mode with type of control protocol you want to establish.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"ActiveCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set your workstation to handle LCP in passive mode, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  open passiveRENDERAS="SECT4"LANSUP SoftwareIDXID="w11617"BOOK="_idx" COLLECTION="nw41" TIDREF="i2060"
This parameters allows the IDXID="w11618"BOOK="_idx" COLLECTION="nw41" TIDREF="i4524"
LANSUP.COM file set to the frame size for a token-ring driver. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"openCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow the RPL protocol to increase the frame size for a remote boot workstations running the LANSUP software above 1 KB, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver lansupMOREINFO="NONE"  openIf the IBM LAN Support driver's DXMT0MOD.SYS file is to load in the CONFIG.SYS file, one of two actions must be performed: NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Set "o=n" on the command line for loading the DXMT0M0D.SYS file in the CONFIG.SYS file and use this parameter in the NET.CFG file.PAGENUM=65 ID="BP71"Set "o=y" on the command line to load the DXMT0M0D.SYS file and set the frame size for the NDIS driver. Do not use this parameter in the NET.CFG file.RENDERAS="SECT3"ID="FM10076"PCOMP [yes | no]IDXID="w11619"BOOK="_idx" COLLECTION="nw41" TIDREF="i4168"
Instructs the IDXID="w11620"BOOK="_idx" COLLECTION="nw41" TIDREF="i3269"
PPP protocol to compress the protocol field of the PPP header.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"pcomp [yes | no]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"noCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To instruct the SLIP_PPP driver to compress the protocol field of the PPP header, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  pcomp yesRENDERAS="SECT3"ID="FM95912"PORT [#1 | #2] hex_starting_address [hex_number_of_ports]IDXID="w11621"BOOK="_idx" COLLECTION="nw41" TIDREF="i3341"
Specifies the starting port (hex_starting_address) and number of ports in the range (hex_number_of_ports).COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"port [#1 | #2] hex_starting_addressMOREINFO="NONE" [hex_number_of_portsMOREINFO="NONE"]All values must be written in hexadecimal notation.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"#1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"If the starting I/O port on an NE2100 LAN driver is 300 and 16 ports are in the first range, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  port 300 16To specify two ranges with 32 ports in each range, you could place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  port #1 300 32MOREINFO="NONE"  port #2 340 32PAGENUM=66 ID="BP72"RENDERAS="SECT3"ID="FM56496"PROTOCOL "name" hex_protocol_ID frame_typeIDXID="w11622"BOOK="_idx" COLLECTION="nw41" TIDREF="i3593"
Allows existing LAN drivers to handle new network protocols. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol nameMOREINFO="NONE" hex_protocol_IDMOREINFO="NONE" frame_typeReplace name with the name of the new protocol. Replace hex_protocol_ID with the assigned hexadecimal protocol ID that the protocol is assigned. Replace frame_type with the frame type that the new protocol ID applies to.IDREF="FM49865"See Table 2-6, "List of ODI LAN Driver Names and Supported Network Boards," on page 75for more information.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To use a new protocol named "XYZ" with an NE/2-32TM LAN driver using the Ethernet_SNAP frame type, you would place the following lines in your NET.CFG file: MOREINFO="NONE"link driver ne2_32MOREINFO="NONE"  frame ethernet_snapMOREINFO="NONE"  protocol xyz 904a ethernet_snap PAGENUM=68 ID="BP73"RENDERAS="SECT2"Defined Protocols and Frame TypesThe following table lists the protocols and frame types currently defined within the industry and their corresponding protocol ID and frame ID numbers.LABEL="2-5" PGWIDE=0 TOCENTRY="1" List and Description of Protocols and Frame Types with Their Identification NumbersCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="5*"COLNAME=4 COLWIDTH="5*"COLNAME=5 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Frame IDCOLNAME=2 ROTATE="0" MOREROWS="0"Frame TypeCOLNAME=3 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=4 ROTATE="0" MOREROWS="0"Protocol ID NumberCOLNAME=5 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"VIRTUAL_LANCOLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=4 ROTATE="0" MOREROWS="0"0COLNAME=5 ROTATE="0" MOREROWS="0"Use where no Frame ID/MAC envelope is necessary.COLNAME=1 ROTATE="0" MOREROWS="0"1 COLNAME=2 ROTATE="0" MOREROWS="0"LOCALTALK COLNAME=3 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=4 ROTATE="0" MOREROWS="0"0COLNAME=5 ROTATE="0" MOREROWS="0"Apple LocalTalk frameCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"8137h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC* Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"XNS COLNAME=4 ROTATE="0" MOREROWS="0"600h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"AARPCOLNAME=4 ROTATE="0" MOREROWS="0"80F3h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"AppleTalk COLNAME=4 ROTATE="0" MOREROWS="0"809Bh COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"ARP COLNAME=4 ROTATE="0" MOREROWS="0"806h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"RARP COLNAME=4 ROTATE="0" MOREROWS="0"8035h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"2 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_II COLNAME=3 ROTATE="0" MOREROWS="0"IP COLNAME=4 ROTATE="0" MOREROWS="0"800h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet using a DEC Ethernet II envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"3 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"E0h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"3 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"RPL COLNAME=4 ROTATE="0" MOREROWS="0"FCh COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"3 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"SNA COLNAME=4 ROTATE="0" MOREROWS="0"04h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"3 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"NetBIOS COLNAME=4 ROTATE="0" MOREROWS="0"F0h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"4 COLNAME=2 ROTATE="0" MOREROWS="0"Token-Ring COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"E0h COLNAME=5 ROTATE="0" MOREROWS="0"Token ring (802.5) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"4 COLNAME=2 ROTATE="0" MOREROWS="0"Token-Ring COLNAME=3 ROTATE="0" MOREROWS="0"RPL COLNAME=4 ROTATE="0" MOREROWS="0"FCh COLNAME=5 ROTATE="0" MOREROWS="0"Token ring (802.5) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"4 COLNAME=2 ROTATE="0" MOREROWS="0"Token-Ring COLNAME=3 ROTATE="0" MOREROWS="0"SNA COLNAME=4 ROTATE="0" MOREROWS="0"04h COLNAME=5 ROTATE="0" MOREROWS="0"Token ring (802.5) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"4 COLNAME=2 ROTATE="0" MOREROWS="0"Token-Ring COLNAME=3 ROTATE="0" MOREROWS="0"NetBIOS COLNAME=4 ROTATE="0" MOREROWS="0"F0h COLNAME=5 ROTATE="0" MOREROWS="0"Token ring (802.5) using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"5 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.3 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=4 ROTATE="0" MOREROWS="0" 00h COLNAME=5 ROTATE="0" MOREROWS="0"IPX 802.3 raw encapsulationCOLNAME=1 ROTATE="0" MOREROWS="0"6 COLNAME=2 ROTATE="0" MOREROWS="0"802.4 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=4 ROTATE="0" MOREROWS="0" N/A COLNAME=5 ROTATE="0" MOREROWS="0"Token-passing bus envelope COLNAME=1 ROTATE="0" MOREROWS="0"7 COLNAME=2 ROTATE="0" MOREROWS="0"RESERVED COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Reserved for future use. COLNAME=1 ROTATE="0" MOREROWS="0"8 COLNAME=2 ROTATE="0" MOREROWS="0"GNET COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"E0h COLNAME=5 ROTATE="0" MOREROWS="0"Gateway G/Net frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"9 COLNAME=2 ROTATE="0" MOREROWS="0"PRONET-10 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Proteon ProNET I/O frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"8137h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAPCOLNAME=3 ROTATE="0" MOREROWS="0" XNS COLNAME=4 ROTATE="0" MOREROWS="0"600h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"AARP COLNAME=4 ROTATE="0" MOREROWS="0"80F3h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"AppleTalk 8000COLNAME=4 ROTATE="0" MOREROWS="0"7809Bh COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"ARP COLNAME=4 ROTATE="0" MOREROWS="0"806h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"RARP COLNAME=4 ROTATE="0" MOREROWS="0"8035h COLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"10 COLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"IP COLNAME=4 ROTATE="0" MOREROWS="0"800hCOLNAME=5 ROTATE="0" MOREROWS="0"Ethernet (802.3) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"11 COLNAME=2 ROTATE="0" MOREROWS="0"Token-Ring_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=4 ROTATE="0" MOREROWS="0"8137h COLNAME=5 ROTATE="0" MOREROWS="0"Token ring (802.5) using an 802.2 envelope with SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"12 COLNAME=2 ROTATE="0" MOREROWS="0"LANPAC_II COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Racore frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"13 COLNAME=2 ROTATE="0" MOREROWS="0"ISDN COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Integrated Services Digital Network (not available)COLNAME=1 ROTATE="0" MOREROWS="0"14 COLNAME=2 ROTATE="0" MOREROWS="0"NOVELL_RX-NET COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"FAh COLNAME=5 ROTATE="0" MOREROWS="0"Novell RX-Net envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"17 COLNAME=2 ROTATE="0" MOREROWS="0"OMNINET/4 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Corvus frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"18 COLNAME=2 ROTATE="0" MOREROWS="0"3270_COAXA COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Harris Adacom frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"19 COLNAME=2 ROTATE="0" MOREROWS="0"IP COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"IP Tunnel frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"20 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPXCOLNAME=4 ROTATE="0" MOREROWS="0"E0h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"20 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"RPL COLNAME=4 ROTATE="0" MOREROWS="0"FCh COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"20 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_802.2 COLNAME=3 ROTATE="0" MOREROWS="0"SNA COLNAME=4 ROTATE="0" MOREROWS="0"04h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using an 802.2 envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"21 COLNAME=2 ROTATE="0" MOREROWS="0"IVDLAN_802.9 COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Commtex, Inc. frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"22 COLNAME=2 ROTATE="0" MOREROWS="0"DATACO_OSI COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"N/A COLNAME=5 ROTATE="0" MOREROWS="0"Dataco frame envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"IPX/SPX COLNAME=4 ROTATE="0" MOREROWS="0"8137h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAPCOLNAME=3 ROTATE="0" MOREROWS="0" XNS COLNAME=4 ROTATE="0" MOREROWS="0"600h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"AARP COLNAME=4 ROTATE="0" MOREROWS="0"80F3h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"AppleTalk 80007COLNAME=4 ROTATE="0" MOREROWS="0"809Bh COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"ARP COLNAME=4 ROTATE="0" MOREROWS="0"806h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"RARP COLNAME=4 ROTATE="0" MOREROWS="0"8035h COLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"23 COLNAME=2 ROTATE="0" MOREROWS="0"FDDI_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"IP COLNAME=4 ROTATE="0" MOREROWS="0"800hCOLNAME=5 ROTATE="0" MOREROWS="0"FDDI using 802.2 with a SNAP envelopeCOLNAME=1 ROTATE="0" MOREROWS="0"24 COLNAME=2 ROTATE="0" MOREROWS="0"IBM_SDLC COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"25 COLNAME=2 ROTATE="0" MOREROWS="0"PCO_FDDITP COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"PC Office frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"26 COLNAME=2 ROTATE="0" MOREROWS="0"WAIDNET COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Hypercommunications frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"27 COLNAME=2 ROTATE="0" MOREROWS="0"SLIPCOLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"28 COLNAME=2 ROTATE="0" MOREROWS="0"PPP COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"29 COLNAME=2 ROTATE="0" MOREROWS="0"RANGELAN COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Proxim frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"30 COLNAME=2 ROTATE="0" MOREROWS="0"X.25 COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"31 COLNAME=2 ROTATE="0" MOREROWS="0"Frame_Relay COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"32 COLNAME=2 ROTATE="0" MOREROWS="0"IWI_BUS-NET_SNAP COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Integrated Workstations frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"33 COLNAME=2 ROTATE="0" MOREROWS="0"SNA_LINKSCOLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typeCOLNAME=1 ROTATE="0" MOREROWS="0"34 COLNAME=2 ROTATE="0" MOREROWS="0"WAN_Client_LAN COLNAME=3 ROTATE="0" MOREROWS="0"Unknown COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=5 ROTATE="0" MOREROWS="0"Novell frame typePAGENUM=71 ID="BP74"RENDERAS="SECT3"ID="FM33016"SAPS numberIDXID="w11623"BOOK="_idx" COLLECTION="nw41" TIDREF="i3952"
Specifies the number of Service Access Points (SAPS) needed for the LANSUP driver.PAGENUM=72 ID="BP75"Set this option to allow for all applications using the IBM LAN Support Program.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"saps numberThe maximum value depends on the type of network board used.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify five SAPS for a NE2100 LAN driver, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver ne2100MOREINFO="NONE"  saps 5SAPS is ignored if another application already opened the LAN driver before the LANSUP.COM LAN driver was loaded.RENDERAS="SECT3"ID="FM12602"SLOT numberIDXID="w11624"BOOK="_idx" COLLECTION="nw41" TIDREF="i4170"
In slot-based machines, the LAN driver usually locates the network board by scanning through the slots in order from lowest to highest. This option directs the driver to locate the network board in the specified slot, instead of scanning for it. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"slot numberUse the number of the slot you inserted the network board into. The slot number is usually found on the back of the computer.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"If you were using two NE/2TM boards in the same workstation and you inserted one network board into slot 1 and the other into slot 2, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver NE2MOREINFO="NONE"  slot 1MOREINFO="NONE"link driver NE2 MOREINFO="NONE"  slot 2 PAGENUM=73 ID="BP76"RENDERAS="SECT3"ID="FM25970"TCPIPCOMP [vj | no] slots comp_slotIDXID="w11625"BOOK="_idx" COLLECTION="nw41" TIDREF="i4747"
Enables Van Jacobson (VJ) IDXID="w11626"BOOK="_idx" COLLECTION="nw41" TIDREF="i1650"
header IDXID="w11627"BOOK="_idx" COLLECTION="nw41" TIDREF="i728"
compression for the IDXID="w11628"BOOK="_idx" COLLECTION="nw41" TIDREF="i4446"
SLIP or PPP protocols.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"tcpipcomp [vj | no] slotsMOREINFO="NONE" comp_slotReplace slots with the conversation slot you want.Replace comp_slot with the number 0 to not compress slot ID or with 1 to compress slot ID.If "no" is specified (for no compression), the slots and comp_slot values are omitted. If the slots and comp_slot values are specified with the "no" value, they are ignored.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"compression: no  slots: 16  comp_slot: 0COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"compression: vj or no  slots: 1 to 16  comp_slot: 0 or 1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable compression for conversation slot number 16, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver slip_pppMOREINFO="NONE"  tcpipcomp vj 16 1PAGENUM=74 ID="BP77"RENDERAS="SECT2"Listing of Commonly Used ODI LAN DriversThe following table lists some of the IDXID="w11629"BOOK="_idx" COLLECTION="nw41" TIDREF="i2033"
common ODITM LAN drivers used with NetWare ClientTM software for DOS and MS Windows. This is not a comprehensive list of all LAN drivers certified by Novell. See the documentation included with your network board for information concerning the appropriate LAN driver to use with the NetWare operating system.The table also includes a list of ODI LAN driver names and supported network boards. for information on the available parameters for each driver, see the .INS file accompanying each LAN driver.LABEL="2-6" PGWIDE=0 TOCENTRY="1"ID="FM49865" List of ODI LAN Driver Names and Supported Network BoardsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Driver Name (.COM)COLNAME=2 ROTATE="0" MOREROWS="0"Network BoardVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"3C501COLNAME=2 ROTATE="0" MOREROWS="0"3Com* 3C1100 3Station* EthernetCOLNAME=1 ROTATE="0" MOREROWS="0"3C501COLNAME=2 ROTATE="0" MOREROWS="0"3Com 3C501 EtherLink*COLNAME=1 ROTATE="0" MOREROWS="0"3C503COLNAME=2 ROTATE="0" MOREROWS="0"3Com 3C503 EtherLink II*  3Com 3C503 EtherLink II TP  3Com 3C503 EtherLink II/163C  3Com 3C503 EtherLink II/16 TPCOLNAME=1 ROTATE="0" MOREROWS="0"3C505COLNAME=2 ROTATE="0" MOREROWS="0"3Com 3C505 EtherLink Plus*COLNAME=1 ROTATE="0" MOREROWS="0"3C523COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink/MC  3Com EtherLink/MC TPCOLNAME=1 ROTATE="0" MOREROWS="0"3C5X9COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink III* Parallel Tasking FamilyCOLNAME=1 ROTATE="0" MOREROWS="0"CEODICOLNAME=2 ROTATE="0" MOREROWS="0"Xircom Credit Card Ethernet AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"E20ODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Ethernet E20COLNAME=1 ROTATE="0" MOREROWS="0"E2HODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Ethernet E2HUBCOLNAME=1 ROTATE="0" MOREROWS="0"E30ODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Ethernet E3010  Cabletron Systems Ethernet E3010-X  Cabletron Systems Ethernet E3020  Cabletron Systems Ethernet E3020-X  Cabletron Systems Ethernet E3030  Cabletron Systems Ethernet E3030-X  Cabletron Systems Ethernet E3040E  Cabletron Systems Ethernet E3040-XCOLNAME=1 ROTATE="0" MOREROWS="0"E31ODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Ethernet E31  Cabletron Systems Ethernet E31-XCOLNAME=1 ROTATE="0" MOREROWS="0"ES3210COLNAME=2 ROTATE="0" MOREROWS="0"Racal-Datacom* ES3210COLNAME=1 ROTATE="0" MOREROWS="0"EXP16ODICOLNAME=2 ROTATE="0" MOREROWS="0"Intel EtherExpress* ISA Family  Intel EtherExpress MCA FamilyCOLNAME=1 ROTATE="0" MOREROWS="0"HPMCAODICOLNAME=2 ROTATE="0" MOREROWS="0"Hewlett-Packard* MC Adapter 16COLNAME=1 ROTATE="0" MOREROWS="0"HPISAODI.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Hewlett-Packard PC Adapter 8/16/16+COLNAME=1 ROTATE="0" MOREROWS="0"HP32ODI.COMCOLNAME=2 ROTATE="0" MOREROWS="0"HP Ethertwist LAN Adapter/32COLNAME=1 ROTATE="0" MOREROWS="0"AM2100.COMCOLNAME=2 ROTATE="0" MOREROWS="0"HP PC LAN Adapter NC/16 TPCOLNAME=1 ROTATE="0" MOREROWS="0"IBMFDDIOCOLNAME=2 ROTATE="0" MOREROWS="0"IBM FDDICOLNAME=1 ROTATE="0" MOREROWS="0"IBMODISHCOLNAME=2 ROTATE="0" MOREROWS="0"IBM PS/2 Ethernet AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"ILANATCOLNAME=2 ROTATE="0" MOREROWS="0"Racal-Datacom InterLan AT/XT COLNAME=1 ROTATE="0" MOREROWS="0"INTEL593COLNAME=2 ROTATE="0" MOREROWS="0"Intel 593 Based Adapter  Zenith Data Systems Z-NOTECOLNAME=1 ROTATE="0" MOREROWS="0"INTEL595COLNAME=2 ROTATE="0" MOREROWS="0"Intel 82595 Based AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"INTEL596COLNAME=2 ROTATE="0" MOREROWS="0"Intel 596 Based AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11630"BOOK="_idx" COLLECTION="nw41" TIDREF="i1232"
LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"ODI Module for the IBM LAN Support ProgramCOLNAME=1 ROTATE="0" MOREROWS="0"MADGEODICOLNAME=2 ROTATE="0" MOREROWS="0"Madge Smart 16/4 PC Ringnode  Madge Smart 16/4 AT Ringnode  Madge Smart 16/4 MC Ringnode  Madge Smart 16/4 MC32 Ringnode  Madge Smart 16/4 EISA Ringnode  Madge Smart 16/4 EISA Mk II RingnodeCOLNAME=1 ROTATE="0" MOREROWS="0"NCRWL05COLNAME=2 ROTATE="0" MOREROWS="0"NCR* WaveLAN*COLNAME=1 ROTATE="0" MOREROWS="0"NE1000COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE1000COLNAME=1 ROTATE="0" MOREROWS="0"NE1500TCOLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE1500TNCOLNAME=1 ROTATE="0" MOREROWS="0"NE2COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE/2COLNAME=1 ROTATE="0" MOREROWS="0"NE2_32COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE2-32COLNAME=1 ROTATE="0" MOREROWS="0"NE2000COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE2000  National Semiconductor NE2000 InfoMoverCOLNAME=1 ROTATE="0" MOREROWS="0"NE2100COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE2100COLNAME=1 ROTATE="0" MOREROWS="0"NE3200COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE3200COLNAME=1 ROTATE="0" MOREROWS="0"NE3300.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Microdyne NE3300 EthernetCOLNAME=1 ROTATE="0" MOREROWS="0"NI5210COLNAME=2 ROTATE="0" MOREROWS="0"Racal-Datacom NI5210COLNAME=1 ROTATE="0" MOREROWS="0"NI6510COLNAME=2 ROTATE="0" MOREROWS="0"Racal-Datacom NI6510COLNAME=1 ROTATE="0" MOREROWS="0"NI9210COLNAME=2 ROTATE="0" MOREROWS="0"Racal-Datacom NI9210COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11631"BOOK="_idx" COLLECTION="nw41" TIDREF="i1232"
NTR2000COLNAME=2 ROTATE="0" MOREROWS="0"Novell NTR2000 Token-Ring Adapter  IBM Token-Ring Network Adapter II  IBM Token-Ring Network 16/4 Adapter  IBM Token-Ring Network Adapter /A  IBM Token-Ring Network 16/4 Adapter /A  IBM Token-Ring 16/4 Credit Card Adapter compatibleCOLNAME=1 ROTATE="0" MOREROWS="0"NULLDRVCOLNAME=2 ROTATE="0" MOREROWS="0"This is not a working LAN driver. The NetWare client installation program copies this file to the client directory during installation for dedicated (not ODI) IPX drivers.Contact the network board manufacturer for copies of the latest ODI drivers.This LAN driver can also be used to support the Personal NetWareTM client and server software running on a workstation without a network board installed.COLNAME=1 ROTATE="0" MOREROWS="0"OC32TR16.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Olicom EISA 32 Token-Ring 16/4 AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"OCTOK16.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Olicom Token-Ring MC 16/4 AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"OSH391RCOLNAME=2 ROTATE="0" MOREROWS="0"Proteon p1391 RapiDriverCOLNAME=1 ROTATE="0" MOREROWS="0"OSH89XRCOLNAME=2 ROTATE="0" MOREROWS="0"Proteon p189X RapiDriverCOLNAME=1 ROTATE="0" MOREROWS="0"OSH990RCOLNAME=2 ROTATE="0" MOREROWS="0"Proteon p1990 RapiDriverCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11632"BOOK="_idx" COLLECTION="nw41" TIDREF="i1232"
ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"ODI Module for the NDIS protocol stackCOLNAME=1 ROTATE="0" MOREROWS="0"PCMDMCOLNAME=2 ROTATE="0" MOREROWS="0"NSC Ethernet PCMCIA CardCOLNAME=1 ROTATE="0" MOREROWS="0"PE2ODICOLNAME=2 ROTATE="0" MOREROWS="0"Xircom Credit Card Ethernet AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11633"BOOK="_idx" COLLECTION="nw41" TIDREF="i1232"
SLIP_PPPCOLNAME=2 ROTATE="0" MOREROWS="0"Novell LAN WorkPlace® Asynchronous SLIP & PPP DriverThis driver runs on workstations serial hardware with either PPP or SLIP frame types. It supports both direct- connection line and indirect modem connections.COLNAME=1 ROTATE="0" MOREROWS="0"SMC8000COLNAME=2 ROTATE="0" MOREROWS="0"SMC* EtherCard* PLUS* Family AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"SMC8100COLNAME=2 ROTATE="0" MOREROWS="0"SMC Token Ring Elite Family AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"SMC9000.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Standard Microsystems Corporation SMC9000COLNAME=1 ROTATE="0" MOREROWS="0"SMCARCWSCOLNAME=2 ROTATE="0" MOREROWS="0"SMC PC130/130E/270E  SMC PC500WS/550WS (short or long card)  SMC PC600WS/650WS  SMC PS110//210/310 PS/2COLNAME=1 ROTATE="0" MOREROWS="0"T20ODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Token-Ring T20COLNAME=1 ROTATE="0" MOREROWS="0"T30ODICOLNAME=2 ROTATE="0" MOREROWS="0"Cabletron Systems Token-Ring T30COLNAME=1 ROTATE="0" MOREROWS="0"TCCARCCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC6x42 ARCnet 8-bit Adapter  Thomas-Conrad TC6x45 ARCnet 16-bit Adapter  Thomas-Conrad TC6x46 ARCnet MC AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"TCE16ATWCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC5045 Ethernet AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"TCE16MCWCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC5046 Ethernet Adapter - 16 bitCOLNAME=1 ROTATE="0" MOREROWS="0"TCE32MCWCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC5046 Ethernet Adapter - 32 bitCOLNAME=1 ROTATE="0" MOREROWS="0"TCNSWCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC3042 TCNS 8-bit Adapter  Thomas-Conrad TC3045 TCNS 16-bit Adapter  Thomas-Conrad TC3046 TCNS MC Adapter  Thomas-Conrad TC3047 TCNS EISA AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"TCTOKSHCOLNAME=2 ROTATE="0" MOREROWS="0"Thomas-Conrad TC4035/TC4045 Adapter  Thomas-Conrad TC4046 AdapterCOLNAME=1 ROTATE="0" MOREROWS="0"TRXNETCOLNAME=2 ROTATE="0" MOREROWS="0"Novell RX-Net & RX-Net II®  Novell RX-Net/2TTMCOLNAME=1 ROTATE="0" MOREROWS="0"UBODICOLNAME=2 ROTATE="0" MOREROWS="0"Ungermann-Bass* NIUpc/EOTP  Ungermann-Bass NIUps  Ungermann-Bass NIUpc  Ungermann-Bass Personal NIU/ex  Ungermann-Bass Personal NIURENDERAS="SECT1"PAGENUM=78 ID="BP78"ID="FM35529"Link Support OptionPAGENUM=79IDXID="w11634"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"
Use this IDXID="w11635"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to configure the number and size of the receive buffers, the size of the memory pool buffers, and the number of boards and stacks used by the Link Support LayerTM (LSL). RENDERAS="SECT2"Available Parameters and Values for the Link Support OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM66912"BUFFERS communication_number [buffer_size]IDREF="FM45014"MAX BOARDS numberIDREF="FM76995"MAX STACKS number  IDREF="FM66317"MEMPOOL number [k]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM66912"81 IDREF="FM45014"83  IDREF="FM76995"84  IDREF="FM66317"85RENDERAS="SECT2"ID="FM87340"LINK SUPPORTIDXID="w11636"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"
Determines the number and size of the receive buffers, the size of the memory pool buffers, and the number of boards and stacks used by the LSLTM program.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"link support  parameter_name valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure for four network boards, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link supportMOREINFO="NONE"  max boards 4PAGENUM=80 ID="BP79"RENDERAS="SECT3"ID="FM66912"BUFFERS communication_number [buffer_size]IDXID="w11637"BOOK="_idx" COLLECTION="nw41" TIDREF="i550"
Configures the number and size of receive buffers that the Link Support Layer (LSL) manages.RENDERAS="SECT4"Communication NumberThe number of communication buffers must be large enough to hold all protocol headers and the maximum data size. If you make many connections, you should increase the number of buffers to increase performance.If the protocol you are using builds the media header (MAC) for the LAN driver, then you need to set the buffer size large enough to manage the header also. For example, IPX requires 512 bytes (LAN header) + 74 bytes (protocol header) + 52 bytes (MAC) = 638 bytes.See the manufacturer's specifications for possible parameters and values required for third-party protocol stacks.RENDERAS="SECT4"Buffer SizeThe total buffer size must share a 64KB segment with the mempool and resident program code from the LSL.COM file when loaded into memory (approximately 5 KB).This means that the communication number multiplied by the buffer size (plus the code size and mempool) cannot be greater than 65,536 bytes.PAGENUM=81 ID="BP80"For example, 20 communication buffers multiplied by a buffer size of 1514 bytes equals 30,280 bytes.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"buffers communication_numberMOREINFO="NONE" [buffer_sizeMOREINFO="NONE"]Replace communication_number with a number of buffers greater than 1. Replace buffer_size with a number of bytes greater than 638. The buffer size is optional.COLNAME=1 ROTATE="0" MOREROWS="0"  DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"  For IPX:communication_number: The IPX protocol utilizes its own buffers and does not require the Link Support Layer software to provide buffers for it.  buffer_size: 1500 bytes  For TCP/IP:communication_number: 8 buffers  buffer_size: 1500 bytesTCP/IP requires only 1500 bytes, because the LAN driver places the 14 bytes of media header on the frame, prior to transmission.   For LSL:buffer_size: 1514 bytesThis accommodates any protocol that utilizes raw sends on Ethernet.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To ensure that the communication buffers are large enough to hold all media headers, you could place the following lines in your NET.CFG file:[For an Ethernet configuration]MOREINFO="NONE"link supportMOREINFO="NONE"  buffers 8 1514  [For a token-ring configuration]MOREINFO="NONE"link supportMOREINFO="NONE"  buffers 8 4222PAGENUM=82 ID="BP81"For the most efficient communication, your link support buffer size should be the same size as the packets that your workstation receives over the network. You might want to set the link support buffer size equal to the largest buffer size that the network boards in your workstation supports. RENDERAS="SECT3"ID="FM45014"MAX BOARDS numberIDXID="w11638"BOOK="_idx" COLLECTION="nw41" TIDREF="i2349"
Configures the maximum number of logical boards that the LSL.COM file can manage.Each LAN driver can use more than one board resources.If a LAN driver fails to load because of an out-of-resource condition, increase the value for this option. The amount of resident memory the LSL.COM file consumes increases with larger MAX BOARD values and decreases with smaller values. Thus, you can conserve some memory by reducing the value to the actual number of boards used by a particular system.PAGENUM=83 ID="BP82"For example, if you had the NE2000.COM file configured to load all possible Ethernet frame types (ETHERNET_II, ETHERNET_802.3, ETHERNET_802.2, and ETHERNET_SNAP), four network board resources would be used. Therefore, to load all four frame types, MAX BOARDS must be set to a value of 4 or higher. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"max boards numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 16COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that two boards can be loaded, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link supportMOREINFO="NONE"  max boards 2Each LAN driver resource or frame type requires approximately 200 bytes of memory. RENDERAS="SECT3"ID="FM76995"MAX STACKS numberIDXID="w11639"BOOK="_idx" COLLECTION="nw41" TIDREF="i2351"
Configures the maximum number of logical protocol stack IDs the LSL.COM file can manage.Each protocol stack can use more than one stack ID resources.If a protocol stack fails to load because of an out-of-resource condition, increase the value for this option. The amount of resident memory the LSL.COM file consumes increases with larger MAX STACKS values and decreases with smaller values. Thus, you can conserve some memory by reducing the value to the actual number of stack IDs used by a particular system.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"max stacks numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 16COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that three logical protocol stack IDs can be loaded, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link supportMOREINFO="NONE"  max stacks 3PAGENUM=84 ID="BP83"RENDERAS="SECT3"ID="FM66317"MEMPOOL number [k]IDXID="w11640"BOOK="_idx" COLLECTION="nw41" TIDREF="i2394"
Configures the size of the memory pool that the LSL program maintains for allocating buffers for some protocols. Thus, the k notation means to multiply by 1024. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"mempool numberMOREINFO="NONE" [k]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure the size of the memory pool, you could place the following lines in your NET.CFG file:MOREINFO="NONE"link supportMOREINFO="NONE"  mempool 1024The IPXODI protocol stack does not use memory pool buffers.RENDERAS="SECT1"ID="FM13477"Named Pipes OptionsIDXID="w11641"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"
Use this IDXID="w11642"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to configure the number of communication buffers, the number of machine names and sessions, and the number of open Named Pipes used by the Named Pipes protocol. PAGENUM=85 ID="BP84"RENDERAS="SECT2"Available Parameters and Values for the Named Pipes OptionUse these 
parameters and values to configure Named Pipes extender (the DOSNP.EXE file) for client workstations, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM19308"NP MAX COMM BUFFERS number IDREF="FM41498"NP MAX MACHINE NAMES numberIDREF="FM74676"NP MAX OPEN NAMED PIPES numberIDREF="FM66802"NP MAX SESSIONS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM19308"87IDREF="FM41498"87IDREF="FM74676"88IDREF="FM66802"89RENDERAS="SECT2"NAMED PIPESIDXID="w11643"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"
Controls the way your client workstation interacts with a Named Pipes server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"named pipes  parameter_name valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the number of communication buffers that the extender can use to communicate with the Named Pipes server from the default to 10, you would place the following lines in your NET.CFG file:MOREINFO="NONE"named pipesMOREINFO="NONE"np max comm buffers 10Placement of Named Pipes parameters in the NET.CFG file should be left-justified. This is an exception to the rule. PAGENUM=86 ID="BP85"RENDERAS="SECT3"ID="FM19308"NP MAX COMM BUFFERS number IDXID="w11644"BOOK="_idx" COLLECTION="nw41" TIDREF="i2995"
Specifies the number of communication buffers that the extender can use to transmit data to and receive data from the Named Pipes server. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"np max comm buffers numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"6COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 40COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the number of communication buffers that the extender can use to communicate with the Named Pipes server from the default to 10, you would place the following lines in your NET.CFG file:MOREINFO="NONE"named pipesMOREINFO="NONE"np max comm buffers 10RENDERAS="SECT3"ID="FM41498"NP MAX MACHINE NAMES number IDXID="w11645"BOOK="_idx" COLLECTION="nw41" TIDREF="i2996"
Specifies the number of Named Pipes servers that the DOSNP software maintains in a local name table. It also sets the DOSNP software for peer mode and controls the number of Named Pipes servers that the extender can communicate with.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"np max machine names numberReplace number with the number of Named Pipe servers cached on the client workstations.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 50COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the number of Named Pipes servers that the workstation can communicate with from the default to 14, you would place the following lines in your NET.CFG file:MOREINFO="NONE"named pipesMOREINFO="NONE"np max machine names 14PAGENUM=87 ID="BP86"RENDERAS="SECT3"ID="FM74676"NP MAX OPEN NAMED PIPES number IDXID="w11646"BOOK="_idx" COLLECTION="nw41" TIDREF="i2997"
Specifies the maximum number of Named Pipes the client workstation can have open simultaneously. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"np max open named pipes numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 128COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the maximum number of pipes that the workstation can have open simultaneously from the default to 6, you would place the following lines in your NET.CFG file:MOREINFO="NONE"named pipesMOREINFO="NONE"np max open named pipes 6RENDERAS="SECT3"ID="FM66802"NP MAX SESSIONS number IDXID="w11647"BOOK="_idx" COLLECTION="nw41" TIDREF="i2998"
Specifies the number of Named Pipes servers the extender can communicate with in default mode. This parameter is not used in peer mode.If both the Maximum Machine Names and Maximum Sessions parameters are used, the value set for Maximum Machine Names overrides the value set for Maximum Sessions.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"np max sessions numberReplace number with the maximum number of Named Pipes servers cached on the client workstations.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 50COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the number of sessions that the extender can use to connect to Named Pipes server from the default to 25, you would place the following lines in your NET.CFG file:MOREINFO="NONE"named pipesMOREINFO="NONE"np max sessions 25RENDERAS="SECT1"PAGENUM=88 ID="BP87"ID="FM96250"NetBIOS OptionUse this option of the NET.CFG file to configure and control the number of broadcasts, buffers, and sessions used by the NetBIOS protocol. RENDERAS="SECT2"Available 
Parameters and Values for the NetBIOS OptionIDXID="w11648"BOOK="_idx" COLLECTION="nw41" TIDREF="i2653"
Use these categories, parameters, and values to manage 
NetBIOS names and sessions or to change the internal memory allocation for NetBIOS, as discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="16*"COLNAME=3 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CategoryCOLNAME=2 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83882"Command ManagementCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41746"NETBIOS COMMANDS numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM41746"92COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM97392"Name ManagementCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM26871"NETBIOS BROADCAST COUNT numberIDREF="FM58843"NETBIOS BROADCAST DELAY numberIDREF="FM69242"NETBIOS INTERNET [on | off]COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM26871"93IDREF="FM58843"93IDREF="FM69242"94COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM96742"Patch Data SegmentsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47129"NPATCH byte_offset, valueCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM47129"95COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM73941"Protocol ManagementCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87069"NETBIOS RECEIVE BUFFERS numberIDREF="FM91618"NETBIOS SEND BUFFERS numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM87069"96IDREF="FM91618"97COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11141"Session CreationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM49505"NETBIOS RETRY COUNT numberIDREF="FM58357"NETBIOS RETRY DELAY numberIDREF="FM37637"NETBIOS SESSION numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM49505"97IDREF="FM58357"98 IDREF="FM37637"99COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM43111"Session ManagementCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55934"NETBIOS ABORT TIMEOUT numberIDREF="FM60621"NETBIOS LISTEN TIMEOUT numberIDREF="FM90486"NETBIOS VERIFY TIMEOUT numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM55934"100IDREF="FM60621"101IDREF="FM90486"101PAGENUM=89 ID="BP88"You can also specify command line parameters for this section. IDREF="FM62716"See Chapter 3, "Command Line Parameters Reference," on page 211 for more information.RENDERAS="SECT2"NETBIOSIDXID="w11649"BOOK="_idx" COLLECTION="nw41" TIDREF="i2653"
Controls the way your client workstation interacts with a NetBIOS application and the network.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios  parameter_name MOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To run an application that requires a larger number of outstanding commands than the default allows, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios commands 64Placement of NetBIOS parameters in the NET.CFG file should be left-justified. This is an exception to the rule.PAGENUM=90 ID="BP89"RENDERAS="SECT3"ID="FM83882"Command ManagementUse this parameter and value to specify how many NetBIOS commands can be buffered in the NetBIOS driver at any one time, which is discussed on the indicated page:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM41746"NETBIOS COMMANDS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41746"92The number of commands needed might vary between applications. In most cases, the default value of 12 is sufficient. However, if a NetBIOS command error 22 occurs, increase the value. Most applications ignore this error and retry if a NetBIOS command is unavailable. In this case, increasing the number of commands improves application performance.For specifics, contact the application's software developer to find out how many commands are required.RENDERAS="SECT3"ID="FM41746"NETBIOS COMMANDS numberIDXID="w11650"BOOK="_idx" COLLECTION="nw41" TIDREF="i2648"
Specifies how many NetBIOS commands can be buffered in the NetBIOS driver at any one time. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios commands numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"12 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 250COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To run an application that requires a larger number of outstanding commands than the default allows, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios commands 64PAGENUM=91 ID="BP90"RENDERAS="SECT3"ID="FM97392"Name ManagementUse these parameters and values to manage waits between query or claim broadcasts and delivery of name resolution and datagram packets on the internetwork, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM26871"NETBIOS BROADCAST COUNT numberIDREF="FM58843"NETBIOS BROADCAST DELAY numberIDREF="FM69242"NETBIOS INTERNET [on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM26871"93IDREF="FM58843"93IDREF="FM69242"94PAGENUM=92 ID="BP91"RENDERAS="SECT3"ID="FM26871"NETBIOS BROADCAST COUNT numberIDXID="w11651"BOOK="_idx" COLLECTION="nw41" TIDREF="i2645"
Specifies how many queries or claims NetBIOS broadcasts for the name being used by an application. Increase the value of this number if youMARK=BULLETHave many LAN segments on the network with nodes that need NetBIOS supportCannot attach to a gatewayMOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios broadcast count numberReplace number with a number of queries. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"If "netbios internet on": 4If "netbios internet off": 2COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"2 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To broadcast more often than either default allows, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios broadcast count 8To determine the total time (in ticks) needed to broadcast a name resolution packet across the network, multiply this value by the value used for the NETBIOS BROADCAST DELAY parameter.  There are approximately 18.21 ticks per second on IBM PCs and compatibles.RENDERAS="SECT3"ID="FM58843"NETBIOS BROADCAST DELAY numberIDXID="w11652"BOOK="_idx" COLLECTION="nw41" TIDREF="i2646"
Specifies the number of ticks NetBIOS waits between query or claim broadcasts.MARK=BULLETIncrease this value if the packet loss rate is high or if the traffic is high.PAGENUM=93 ID="BP92"Reduce the NETBIOS BROADCAST COUNT parameter value by a similar amount to maintain the same name resolution timeout value.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios broadcast delay numberReplace number with a number of ticks.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"If "netbios internet on": 36If "netbios internet off": 18COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"18 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To wait longer between broadcasts than either default allows, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios broadcast delay 3000To determine the total time (in ticks) needed to broadcast a name resolution packet across the network, multiply this value by the value used for the NETBIOS BROADCAST COUNT parameter.  There are approximately 18.21 ticks per second on IBM PCs and compatibles.RENDERAS="SECT3"ID="FM69242"NETBIOS INTERNET [on | off]IDXID="w11653"BOOK="_idx" COLLECTION="nw41" TIDREF="i2651"
Transmits name-claim packets to and from all workstations on the internetwork, or to and from workstations on the local network only. Name-claim packets are packets that attempt to establish the uniqueness of the name of the workstation that NetBIOS is running on.MARK=BULLETIf you are running NetBIOS applications on a single network with a dedicated NetWare server, this parameter speeds up the delivery of name resolution and datagram packets when its value is set to "off."If you are running on more than one network or LAN segment and are communicating through bridges, or if you are running a nondedicated NetWare server, the value must remain set to "on."MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios internet [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To send and receive through bridges and routers, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios internet onPAGENUM=94 ID="BP93"RENDERAS="SECT3"ID="FM96742"Patch Data SegmentsUse this parameter and value to patch any location in the NETBIOS.EXE data segment with a value of your choice, which is discussed on the indicated page:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM47129"NPATCH byte_offset, valueCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47129"95RENDERAS="SECT3"ID="FM47129"NPATCH byte_offset, valueIDXID="w11654"BOOK="_idx" COLLECTION="nw41" TIDREF="i3001"
Patches any location in the NETBIOS.EXE data segment with a value of your choice. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"npatch byte_offsetMOREINFO="NONE", valueReplace byte_offset with a number data segment you want patched.Replace value with the number data segment you want to patch it with.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To patch the NETBIOS.EXE data segment xx with the value yy, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"npatch xx,yyPAGENUM=95 ID="BP94"RENDERAS="SECT3"ID="FM73941"Protocol ManagementUse these parameters and values to configure the number of IPX receive and send buffers that NetBIOS uses, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM87069"NETBIOS RECEIVE BUFFERS numberIDREF="FM91618"NETBIOS SEND BUFFERS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87069"96IDREF="FM91618"97These parameters and values are useful in controlling incoming burst traffic situations, such as that from a 3270 gateway. You should increase the value of these parameters if any of these is true:MARK=BULLETThe workstation is configured for a client-server environment The send and receive buffers are experiencing a many-to-one relationshipThe send and receive buffers are experiencing an incoming burst traffic situation RENDERAS="SECT3"ID="FM87069"NETBIOS RECEIVE BUFFERS numberIDXID="w11655"BOOK="_idx" COLLECTION="nw41" TIDREF="i2657"
Configures the number of IPX receive buffers that NetBIOS uses. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios receive buffers numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"6 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 20COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the speed at which NetBIOS manages incoming bursts of traffic, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios receive buffers 12PAGENUM=96 ID="BP95"RENDERAS="SECT3"ID="FM91618"NETBIOS SEND BUFFERS numberIDXID="w11656"BOOK="_idx" COLLECTION="nw41" TIDREF="i2660"
Configures the number of IPX send buffers that NetBIOS uses. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios send buffers numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"6 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 250COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the speed at which NetBIOS manages outgoing transmissions, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios send buffers 24RENDERAS="SECT3"ID="FM11141"Session CreationUse these parameters and values to monitor and control timeouts for your NetBIOS connections, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and Values COLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM49505"NETBIOS RETRY COUNT numberIDREF="FM58357"NETBIOS RETRY DELAY numberIDREF="FM37637"NETBIOS SESSION numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM49505"97IDREF="FM58357"98 IDREF="FM37637"99RENDERAS="SECT3"ID="FM49505"NETBIOS RETRY COUNT numberIDXID="w11657"BOOK="_idx" COLLECTION="nw41" TIDREF="i2658"
Specifies how many requests NetBIOS transmits for connection or how many failed communications it retransmits.Adjust the value for this parameter with the value for NETBIOS RETRY DELAY to vary the timeout on establishing NetBIOS sessions. Increase the value of the parameter if either of the following situations is true:MARK=BULLETThere are many LAN segments on the network with nodes that need NetBIOS supportPAGENUM=97 ID="BP96"Client workstations cannot attach to a gatewayMOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios retry count numberReplace number with a number of requests (retries). COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"If "netbios internet on": 20  If "netbios internet off": 10COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 20COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To retransmit 15 times, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios retry count 15RENDERAS="SECT3"ID="FM58357"NETBIOS RETRY DELAY numberIDXID="w11658"BOOK="_idx" COLLECTION="nw41" TIDREF="i2659"
Specifies how long (in ticks) NetBIOS waits between transmissions while establishing a connection or resending a data packet. Adjust the value of this parameter with the value for NETBIOS RETRY COUNT to vary the timeout on establishing NetBIOS sessions. Increase the value of this number if either of the following is true:MARK=BULLETHave many LAN segments on the network with nodes that need NetBIOS supportCannot attach to a gatewayMOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios retry delay numberReplace number with a number (of ticks) greater than 10. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"10 (about .5 second)COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"10 to 65,535 ticksCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To wait 800 ticks between retransmission attempts, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios retry delay 800PAGENUM=98 ID="BP97"There are approximately 18.21 ticks per second on IBM PCs and compatibles.  RENDERAS="SECT3"ID="FM37637"NETBIOS SESSION numberIDXID="w11659"BOOK="_idx" COLLECTION="nw41" TIDREF="i2661"
Specifies how many simultaneous NetBIOS sessions can be supported by the NetBIOS driver. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios sessions numberReplace number with a number of sessions. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"32COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 250COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow 100 NetBIOS sessions, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"netbios sessions 100RENDERAS="SECT3"ID="FM43111"Session ManagementUse these parameters and values to monitor and control your NetBIOS connections, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55934"NETBIOS ABORT TIMEOUT numberIDREF="FM60621"NETBIOS LISTEN TIMEOUT numberIDREF="FM90486"NETBIOS VERIFY TIMEOUT numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55934"100IDREF="FM60621"101IDREF="FM90486"101PAGENUM=99 ID="BP98"When the NetBIOS sessions at a sending computer do not receive any transmissions from the receiving computer for the length of the "verify timeout" interval, NetBIOS sends a request-for-acknowledgment packet to the receiving computer.NetBIOS then waits the length of the "listen timeout" interval to receive a response. If no response is received, NetBIOS sends another packet requesting immediate response. NetBIOS then waits the length of the "abort timeout" interval to receive a response. If no response is received, NetBIOS terminates the session.The ratio between these three parameters must remain the same. For example, if you double the NETBIOS TIMEOUT value, you must also double the NETBIOS ABORT TIMEOUT and NETBIOS VERIFY TIMEOUT values.RENDERAS="SECT3"ID="FM55934"NETBIOS ABORT TIMEOUT numberIDXID="w11660"BOOK="_idx" COLLECTION="nw41" TIDREF="i2644"
Specifies how long (in ticks) NetBIOS waits without receiving any response from the other side of a session before it terminates the session. Increase this value if there are NetBIOS nodes across asynchronous lines or large internetworks.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios abort timeout numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"540 (approximately 30 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify one minute before NetBIOS terminates a request-for-acknowledgment packet session, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"  netbios abort timeout 1080There are approximately 18.21 ticks per second on IBM PCs and compatibles.  PAGENUM=100 ID="BP99"RENDERAS="SECT3"ID="FM60621"NETBIOS LISTEN TIMEOUT numberIDXID="w11661"BOOK="_idx" COLLECTION="nw41" TIDREF="i2652"
Specifies how long (in ticks) NetBIOS waits without receiving any packets from the other side of a session before it requests a keep-alive packet from the other side to assure the session is still valid.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios listen timeout numberReplace number with a number of ticks.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"108 (approximately 6 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make NetBIOS wait longer before sending a request- for-acknowledgment packet, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"  netbios listen timeout 2700There are approximately 18.21 ticks per second on IBM PCs and compatibles.  RENDERAS="SECT3"ID="FM90486"NETBIOS VERIFY TIMEOUT numberIDXID="w11662"BOOK="_idx" COLLECTION="nw41" TIDREF="i2665"
Specifies how often in (ticks) NetBIOS sends a keep-alive packet to the other side of a session to preserve the session.If no packets are being exchanged on the NetBIOS session by the software that established the session, NetBIOS sends packets at regular intervals to make sure that the session is still valid.MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netbios verify timeout numberReplace number with a number of ticks. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"54 (approximately 3 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 65,535COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make NetBIOS wait longer than the default before sending a request-for-acknowledgment packet, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netbiosMOREINFO="NONE"  netbios verify timeout 1350PAGENUM=101 ID="BP100"There are approximately 18.21 ticks per second on IBM PCs and compatibles. RENDERAS="SECT1"ID="FM76848"NetWare DOS Requester OptionUse this option of the NET.CFG file to configure the NetWare Client software for various types of networking support and connectivity.IDXID="w11663"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
The 
NetWare DOS Requester IDXID="w11664"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
software provides networking support for DOS and Microsoft (MS) Windows client workstations. The NetWare DOS Requester is built on an architecture of Virtual Loadable Module (VLM) software. The VLM.EXE (VLM manager) file is responsible for loading the required modules.IDXID="w11665"BOOK="_idx" COLLECTION="nw41" TIDREF="i2734"
Previous versions of the NetWare DOS and MS Windows client software relied on the single shell file NETX.EXE to provide networking support.The NetWare DOS Requester is not compatible with the NETX.COM or NETX.EXE file. Use the NETX.VLM file for compatibility with shell calls.The following topics are covered in this section.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM63224"Current Core Virtual Loadable Module (VLM) ProgramsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM63224"104COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM16456"Current Non-Core Virtual Loadable Module ProgramsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16456"105COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM45863"Compatibility with NetWare Shell ParametersCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45863"106COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM14590"Managing the NetWare DOS RequesterCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM14590"108COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM89803"Optimizing the NetWare DOS RequesterCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM89803"109COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM18532"Available Parameters and Values for the NetWare DOS Requester OptionCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18532"113PAGENUM=103 ID="BP101"RENDERAS="SECT2"ID="FM63224"Current IDXID="w11666"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Core 
Virtual Loadable Module (VLM) ProgramsThe following table lists the current IDXID="w11667"BOOK="_idx" COLLECTION="nw41" TIDREF="i854"
core VLM programs in their default load order. The table also includes descriptions and flags indicating whether the module is required (R) or optional (O) for NetWare Directory ServicesTM (NDS) support, bindery services (BIND), and Personal NetWareTM (PNW) services.LABEL="2-7" PGWIDE=1 TOCENTRY="1" List of Current Core VLM Programs and the Respective Load OrderCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="15*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="4*"COLNAME=5 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Module NameCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"NDSCOLNAME=4 ROTATE="0" MOREROWS="0"BINDCOLNAME=5 ROTATE="0" MOREROWS="0"PNWVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BIND.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare protocol implementation using the binderyCOLNAME=3 ROTATE="0" MOREROWS="0"OCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"OCOLNAME=1 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Connection table managerCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"File Input/OutputCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"GENERAL.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Miscellaneous functions for the NETX.VLM and REDIR.VLM filesCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"IPXNCP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Transport protocol implementation using IPXCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"NDS.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare protocol implementation using NDSTM supportCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"OCOLNAME=5 ROTATE="0" MOREROWS="0"OCOLNAME=1 ROTATE="0" MOREROWS="0"NETX.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare shell compatibilityCOLNAME=3 ROTATE="0" MOREROWS="0"OCOLNAME=4 ROTATE="0" MOREROWS="0"OCOLNAME=5 ROTATE="0" MOREROWS="0"OCOLNAME=1 ROTATE="0" MOREROWS="0"NWP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare protocol multiplexorCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare protocol implementation using Personal NetWareCOLNAME=3 ROTATE="0" MOREROWS="0"OCOLNAME=4 ROTATE="0" MOREROWS="0"OCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Printer redirectorCOLNAME=3 ROTATE="0" MOREROWS="0"OCOLNAME=4 ROTATE="0" MOREROWS="0"OCOLNAME=5 ROTATE="0" MOREROWS="0"OCOLNAME=1 ROTATE="0" MOREROWS="0"REDIR.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"DOS redirectorCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RCOLNAME=1 ROTATE="0" MOREROWS="0"SECURITY.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare enhanced securityCOLNAME=3 ROTATE="0" MOREROWS="0"OCOLNAME=4 ROTATE="0" MOREROWS="0"OCOLNAME=5 ROTATE="0" MOREROWS="0"OCOLNAME=1 ROTATE="0" MOREROWS="0"TRAN.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Transport protocol multiplexorCOLNAME=3 ROTATE="0" MOREROWS="0"RCOLNAME=4 ROTATE="0" MOREROWS="0"RCOLNAME=5 ROTATE="0" MOREROWS="0"RPAGENUM=104 ID="BP102"RENDERAS="SECT2"ID="FM16456"Current Non-Core Virtual Loadable Module ProgramsThe following table lists the current IDXID="w11668"BOOK="_idx" COLLECTION="nw41" TIDREF="i2964"
non-core VLM programs. Non-core VLM programs do not automatically load by default. Use the VLM path_vlm parameter and value to load any non-core modules. IDREF="FM82853"See "VLM=path_VLM" on page 157 for details on how to use this parameter and value.The table also includes descriptions and flags indicating whether the module is used (U) or not used (N) for NetWare Directory Services (NDS), bindery services (BIND), and Personal NetWare (PNW) services.LABEL="2-8" PGWIDE=1 TOCENTRY="1" List of Current Non-Core VLM ProgramsCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="15*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="4*"COLNAME=5 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Module nameCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"NDSCOLNAME=4 ROTATE="0" MOREROWS="0"BINDCOLNAME=5 ROTATE="0" MOREROWS="0"PNWVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AUTO.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Auto-reconnect/auto-retryCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"MIB2IF.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"MIB-II interface groups supportCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"MIB2PROT.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"MIB-II support for the TCP/IP groupsCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"NMR.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare management responderCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"RSA.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"RSA encryption for NetWare Directory Services re-authenticationCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"WSASN1.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"SNMP ASN.1 translationCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"WSDRVPRN.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The print information collection file for gathering information about print mappings and captured printersCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"WSREG.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"SNMP MIB registrationCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"WSSNMP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"Desktop SNMP module, which includes support for MIB-II System and SNMP groupsCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UCOLNAME=1 ROTATE="0" MOREROWS="0"WSTRAP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"SNMP trapCOLNAME=3 ROTATE="0" MOREROWS="0"UCOLNAME=4 ROTATE="0" MOREROWS="0"UCOLNAME=5 ROTATE="0" MOREROWS="0"UPAGENUM=105 ID="BP103"RENDERAS="SECT2"ID="FM45863"Compatibility with NetWare Shell Parameters** Parameter is supported under the IDXID="w11669"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
NetWare DOS Requester heading in the NET.CFG file. See specific reference to the parameter for more information.¤ No longer supported. The functionality of this parameter was either developed into the NetWare DOS Requester software or is no longer required because of the NetWare DOS Requester architecture. Existing lines in your NET.CFG file for these parameters will be ignored.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"StatusVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"all servers=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"cache buffers=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"checksum=[on | off](Now requires a number value from 0 to 3.)COLNAME=2 ROTATE="0" MOREROWS="0"¤ COLNAME=1 ROTATE="0" MOREROWS="0"dos name=nameCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"entry stack size=numberCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"environment pad=numberCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"eojs=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"file handles=number(Functionality is provided by the FILES parameter setting in the CONFIG.SYS file.)COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"get local target stacks=numberCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"hold=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"lipackets=[on | off](Functionality is provided by LARGE INTERNET PACKETS.)COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"local printers=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"lock delay=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"lock retries=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"long machine type=nameCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"max cur dir length=number(Because of a limitation in DOS, the maximum character length is hard set to a value of 63 characters.)COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"max path length=numberCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"max tasks=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"patch=byte_offset_valueCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"pb buffers=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"preferred server=server_nameCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"print header=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"print tail=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"read only compatibilitys=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"search mode=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"set station times=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"share=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"short machine type=nameCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"show dots=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"sign 386 modeCOLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"signature level=numberCOLNAME=2 ROTATE="0" MOREROWS="0"**COLNAME=1 ROTATE="0" MOREROWS="0"special uppercases=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"¤COLNAME=1 ROTATE="0" MOREROWS="0"task mode=numberCOLNAME=2 ROTATE="0" MOREROWS="0"¤PAGENUM=107 ID="BP104"RENDERAS="SECT2"ID="FM14590"Managing the NetWare DOS RequesterIDXID="w11670"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Use the following information to manage loading and using the VLM.EXE file and its modules under specific conditions.LABEL="2-9" PGWIDE=1 TOCENTRY="1" Managing the NetWare DOS RequesterCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ConditionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Loading the VLM.EXE file from a directory other than your current directoryCOLNAME=2 ROTATE="0" MOREROWS="0"The current directory is used for VLM software. To load the VLM software from another directory, use the "VLM =" command in the NET.CFG file.For example:MOREINFO="NONE"VLM=C:\NWCLIENT\CONN.VLMMOREINFO="NONE"COLNAME=1 ROTATE="0" MOREROWS="0"Specifying a NET.CFG file outside the current directoryCOLNAME=2 ROTATE="0" MOREROWS="0"At the command line, enter a command similar to the following (or add the command to the AUTOEXEC.BAT file):MOREINFO="NONE" VLM /C=C:\NWCLIENT\NET.CFGCOLNAME=1 ROTATE="0" MOREROWS="0"Loading the NetWare DOS Requester memory managers under MS Windows 3.0COLNAME=2 ROTATE="0" MOREROWS="0"If you are running MS Windows 3.0, ensure that the VLM.EXE file is loaded after any upper- or high-memory managers are loaded.COLNAME=1 ROTATE="0" MOREROWS="0"Avoid Loading VLM software in expanded memory with MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"Don't use the expanded memory option (/ME). Run MS Windows with the NetWare DOS Requester only if you use the extended memory option (/MX, preferred) or the conventional memory option (/MC).COLNAME=1 ROTATE="0" MOREROWS="0"Disabling the VLM softwareCOLNAME=2 ROTATE="0" MOREROWS="0"The following are the preferred ways to disable specific VLM software:MARK=BULLETRename the module with an extension other than .VLM.Use the parameter and value. IDREF="FM13904"See "USE DEFAULTS=[on | off]" on page 155Use the parameter and value. IDREF="FM26176"See "EXCLUDE VLM=path_vlm" on page 128PAGENUM=108 ID="BP105"RENDERAS="SECT2"ID="FM89803"Optimizing the NetWare DOS RequesterYou can optimize the NetWare DOS Requester software for the following three conditions:MARK=BULLETIDREF="FM87890"Best PerformanceIDREF="FM53573"Best Conventional Memory UsageIDREF="FM92168"Best CompromiseRENDERAS="SECT3"ID="FM87890"Best PerformanceIDXID="w11671"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
For the IDXID="w11672"BOOK="_idx" COLLECTION="nw41" TIDREF="i3104"
best performance, use the following parameters under the NetWare DOS Requester option in the NET.CFG file.LABEL="2-10" PGWIDE=0 TOCENTRY="1" Parameters and Values Used to Configure for Best PerformanceCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="17*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33534"AUTO LARGE TABLE=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99234"LOAD LOW CONN=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM15902"AUTO RECONNECT=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88067"LOAD LOW IPXNCP=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM25779"AVERAGE NAME LENGTH=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18576"MINIMUM TIME TO NET=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM58957"CACHE BUFFER SIZE=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83430"NETWARE PROTOCOL=netware_protocol_listCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94123"CACHE BUFFERS=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83220"PB BUFFERS=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33185"CACHE WRITES=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83120"PRINT BUFFER SIZE=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM70333"CHECKSUM=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38061"SIGNATURE LEVEL=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31456"LARGE INTERNET PACKETS=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10063"TRUE COMMIT=[on | off]PAGENUM=109 ID="BP106"Use the /MC command line parameter when loading the VLM.EXE file. /MC loads all of the VLM programs into conventional memory.  Loading the NetWare DOS Requester into conventional memory requires approximately 100 KB of memory.Following is a sample NET.CFG file entry for a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   cache buffers=64
   cache buffer size=1540
   cache writes=on
   checksum=0
   exclude=nds.vlm
   large internet packet=on
   load low conn=on
   load low ipxncp=on
   minimum time to net=0
   netware protocol=bind,nds,pnw
   pb buffers=3
   print buffer size=256
   signature level=0
   true commit=offThis entry indicates the following:MARK=BULLETThe CACHE BUFFER SIZE is set for an Ethernet network boardThe "DOS FILES=" command in the CONFIG.SYS file is set above 64 filesThe servers are running NetWare 3.12PAGENUM=110 ID="BP107"RENDERAS="SECT3"ID="FM53573"Best Conventional Memory UsageIDXID="w11673"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
For the IDXID="w11674"BOOK="_idx" COLLECTION="nw41" TIDREF="i3104"
best memory usage, use the following parameters under the NetWare DOS Requester option in the NET.CFG file.LABEL="2-11" PGWIDE=1 TOCENTRY="1" Parameters and Values Used to Configure for Best Memory UsageCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="17*"COLNAME=2 COLWIDTH="17*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33534"AUTO LARGE TABLE=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99234"LOAD LOW CONN=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM15902"AUTO RECONNECT=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88067"LOAD LOW IPXNCP=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM25779"AVERAGE NAME LENGTH=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM25724"NETWORK PRINTERS=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94123"CACHE BUFFERS=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83220"PB BUFFERS=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29223"CONNECTIONS=numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18170"PRINT HEADER=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM26176"EXCLUDE VLM=path_vlmCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM49693"PRINT TAIL=numberCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31456"LARGE INTERNET PACKETS=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38061"SIGNATURE LEVEL=numberConfiguring for the smallest conventional memory usage will result in some performance degradation.Following is a sample NET.CFG file entry for a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   auto large table=off
   auto reconnect=off
   average name length=7
   cache buffers=0
   connections=4
   exclude=pnw.vlm
   exclude=netx.vlm
   load low conn=off
   load low ipxncp=off
   network printers=0
   pb buffers=0
   print header=0
   print tail=0
PAGENUM=111 ID="BP108"   signature level=0This entry indicates the following:MARK=BULLETThe sum of character length of server names attached to is 24You are not running any NETX applicationsYou print to a local printer onlyThe servers are running NetWare 4 only (no bindery or Personal NetWare connections)RENDERAS="SECT3"ID="FM92168"Best CompromiseIDXID="w11675"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
The IDXID="w11676"BOOK="_idx" COLLECTION="nw41" TIDREF="i961"
default settings for the NetWare DOS Requester provide the best compromise between performance and memory usage. You should use the default settings until you can determine the optimal configuration for your particular network and client workstations.Following is a sample working IDXID="w11677"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file for a client workstation. Wherever feasible, default settings are used. Otherwise, example variable replacements are used (for example, the preferred server name):FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   port 300
   int 3
   frame ethernet_802.2
PAGENUM=112 ID="BP109"FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   netware protocol=nds,bind
   first network drive=f
   preferred server=sales
   auto retry=10
   bind reconnect=on
   cache buffers=40
   checksum=0
   connections=16
   large internet packet=on
   load low conn=on
   load low ipxncp=on
   message timeout=183
   pb buffers=8
   signature level=0
   pburst read window size=64
   pburst write window size=64RENDERAS="SECT2"ID="FM18532"Available Parameters and Values for the NetWare DOS Requester OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33534"AUTO LARGE TABLE=[on | off]IDREF="FM15902"AUTO RECONNECT=[on | off]IDREF="FM94986"AUTO RETRY=numberIDREF="FM25779"AVERAGE NAME LENGTH=numberIDREF="FM22133"BIND RECONNECT=[on | off]IDREF="FM50684"BROADCAST RETRIES=numberIDREF="FM68028"BROADCAST SEND DELAY=numberIDREF="FM48554"BROADCAST TIMEOUT=numberIDREF="FM58957"CACHE BUFFER SIZE=numberIDREF="FM94123"CACHE BUFFERS=numberIDREF="FM33185"CACHE WRITES=[on | off]IDREF="FM70333"CHECKSUM=numberIDREF="FM30762"CONFIRM CRITICAL ERROR ACTION=[on | off]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33534"115IDREF="FM15902"116IDREF="FM94986"116IDREF="FM25779"117IDREF="FM22133"118IDREF="FM50684"118IDREF="FM68028"120IDREF="FM48554"121IDREF="FM58957"121IDREF="FM94123"122IDREF="FM33185"123IDREF="FM70333"123IDREF="FM30762"124COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29223"CONNECTIONS=numberIDREF="FM71782"DOS NAME="name"IDREF="FM69676"EOJ=[on | off]IDREF="FM26176"EXCLUDE VLM=path_vlmIDREF="FM41018"FIRST NETWORK DRIVE=drive_letterIDREF="FM95316"FORCE FIRST NETWORK DRIVE=[on | off]IDREF="FM36547"HANDLE NET ERRORS=[on | off]IDREF="FM31456"LARGE INTERNET PACKETS=[on | off]IDREF="FM38196"LIP START SIZE=numberIDREF="FM46920"LOAD CONN TABLE LOW=[on | off]IDREF="FM99234"LOAD LOW CONN=[on | off]IDREF="FM88067"LOAD LOW IPXNCP=[on | off]IDREF="FM27448"LOAD LOW REDIR=[on | off]IDREF="FM85505"LOCAL PRINTERS=numberIDREF="FM47395"LOCK DELAY=numberIDREF="FM50633"LOCK RETRIES=numberIDREF="FM55838"LONG MACHINE TYPE="name"IDREF="FM75203"MAX TASKS=numberIDREF="FM56219"MESSAGE LEVEL=numberIDREF="FM50257"MESSAGE TIMEOUT=numberIDREF="FM18576"MINIMUM TIME TO NET=numberIDREF="FM83779"NAME CONTEXT="name_context"IDREF="FM83430"NETWARE PROTOCOL=netware_protocol_listIDREF="FM25724"NETWORK PRINTERS=numberIDREF="FM83220"PB BUFFERS=numberIDREF="FM46002"PBURST READ WINDOWS SIZE=numberIDREF="FM39829"PBURST WRITE WINDOWS SIZE=numberIDREF="FM66900"PREFERRED SERVER="server_name"IDREF="FM74063"PREFERRED TREE="tree_name"IDREF="FM39892"PREFERRED WORKGROUP="workgroup_name"IDREF="FM83120"PRINT BUFFER SIZE=numberIDREF="FM18170"PRINT HEADER=numberIDREF="FM49693"PRINT TAIL=numberIDREF="FM92475"READ ONLY COMPATIBILITY=[on | off]IDREF="FM96139"RESPONDER=[on | off]IDREF="FM54415"SEARCH MODE=numberIDREF="FM42168"SET STATION TIME=[on | off]IDREF="FM91125"SHORT MACHINE TYPE="name"IDREF="FM72900"SHOW DOTS=[on | off]IDREF="FM38061"SIGNATURE LEVEL=numberIDREF="FM10063"TRUE COMMIT=[on | off]IDREF="FM13904"USE DEFAULTS=[on | off]IDREF="FM82853"VLM=path_VLMIDREF="FM65506"WORKGROUP NET=workgroup_net_addressCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29223"125IDREF="FM71782"127IDREF="FM69676"127IDREF="FM26176"128IDREF="FM41018"129IDREF="FM95316"129IDREF="FM36547"130IDREF="FM31456"130IDREF="FM38196"131IDREF="FM46920"132IDREF="FM99234"132IDREF="FM88067"133IDREF="FM27448"134IDREF="FM85505"135IDREF="FM47395"135IDREF="FM50633"136IDREF="FM55838"137IDREF="FM75203"138IDREF="FM56219"138IDREF="FM50257"139IDREF="FM18576"140IDREF="FM83779"141IDREF="FM83430"141IDREF="FM25724"142IDREF="FM83220"143IDREF="FM46002"144IDREF="FM39829"144IDREF="FM66900"145IDREF="FM74063"146IDREF="FM39892"146IDREF="FM83120"147IDREF="FM18170"147IDREF="FM49693"148IDREF="FM92475"149IDREF="FM96139"150IDREF="FM54415"151IDREF="FM42168"152IDREF="FM91125"153IDREF="FM72900"153IDREF="FM38061"154IDREF="FM10063"155IDREF="FM13904"155IDREF="FM82853"157IDREF="FM65506"159PAGENUM=114 ID="BP110"RENDERAS="SECT2"ID="FM95375"NETWARE DOS REQUESTERIDXID="w11678"BOOK="_idx" COLLECTION="nw41" TIDREF="i2734"
Controls network requests from your client workstation to a NetWare server or network.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netware dos requester  parameter_nameMOREINFO="NONE"=valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure for four server connections, you would place these lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  connections=4RENDERAS="SECT3"ID="FM33534"AUTO LARGE TABLE=[on | off]IDXID="w11679"BOOK="_idx" COLLECTION="nw41" TIDREF="i355"
Allocates a small table of 34 bytes per connection for bindery reconnects. When the parameter is enabled, the AUTO.VLM program allocates a large connection table of 178 bytes per connection for bindery reconnects. Change the default value to "on" if the length of your username and password combined is more than 16 characters.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"auto large table=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"AUTO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To use a username and password longer than 16 characters combined, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  auto large table=onPAGENUM=115 ID="BP111"Use this parameter for binder connections if your username and password total more than 32 characters. For this parameter to work, also set BIND RECONNECT=ON. RENDERAS="SECT3"ID="FM15902"AUTO RECONNECT=[on | off]IDXID="w11680"BOOK="_idx" COLLECTION="nw41" TIDREF="i356"
When this parameter is set to "on," the AUTO.VLM program reconnects a client workstation to a NetWare server and rebuilds the workstation's environment (excluding file-specific items) prior to connection loss.When this parameter is set to "off," the AUTO.VLM program load fails at pre-initialization time.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"auto reconnect=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"AUTO.VLM, NDS.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make reconnecting to a NetWare server the user's responsibility, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  auto reconnect=offTo enable the VLM.EXE program to load the AUTO.VLM file, you must include the VLM=AUTO.VLM parameter and value. You must also load RSA.VLM if you are re-establishing a NetWare Directory Services (NDS) connection, by using the VLM=RSA.VLM parameter.RENDERAS="SECT3"ID="FM94986"AUTO RETRY=numberIDXID="w11681"BOOK="_idx" COLLECTION="nw41" TIDREF="i357"
Sets the number of seconds the AUTO.VLM program waits before attempting a retry after receiving a network critical error.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"auto retry=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 3640COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"AUTO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make the AUTO.VLM program wait for one minute before retrying a connection, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  auto retry=60PAGENUM=116 ID="BP112"To enable the VLM.EXE program to load the AUTO.VLM file, you must include the VLM=AUTO.VLM parameter and value. You must also load RSA.VLM if you are re-establishing a NetWare Directory Services (NDS) connection, by using the VLM=RSA.VLM parameter. When the value for this parameter is set to 0, the AUTO.VLM program makes no retry attempts. RENDERAS="SECT3"ID="FM25779"AVERAGE NAME LENGTH=numberIDXID="w11682"BOOK="_idx" COLLECTION="nw41" TIDREF="i385"
Allows the NetWare DOS Requester to set aside space for a table of NetWare server names based on the values set for the AVERAGE NAME LENGTH and CONNECTIONS parameters. For shorter NetWare server names, you can save some memory by setting the average length to a lower number.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"average name length=numberReplace number with the sum of the average character length of your network server names, divided by the number set in the CONNECTIONS parameter plus 1.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"48 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"2 to 48 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To save memory by shortening the average name length allowed to eight characters, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  average name length=9PAGENUM=117 ID="BP113"RENDERAS="SECT3"ID="FM22133"BIND RECONNECT=[on | off]IDXID="w11683"BOOK="_idx" COLLECTION="nw41" TIDREF="i435"
Automatically rebuilds bindery connections and restores drive mappings and printer connections. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"bind reconnect=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"AUTO.VLM, BIND.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make reconnecting to bindery services automatic, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  bind reconnect=onTo enable the VLM.EXE program to load the AUTO.VLM file, you must include the VLM=AUTO.VLM parameter and value.  For this parameter to work, also set AUTO RECONNECT=ON.  RENDERAS="SECT3"ID="FM50684"BROADCAST RETRIES=numberIDXID="w11684"BOOK="_idx" COLLECTION="nw41" TIDREF="i525"
Sets the number of times the NetWare DOS Requester software broadcasts a request. Set this to a higher number if you are not seeing some resources in various utility lists. PAGENUM=118 ID="BP114"Increasing this number decreases the response time of some utilities. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"broadcast retries=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 255COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable a workgroup to display in the WGLIST utility that is not reachable by using the default value, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  broadcast retries=10PAGENUM=119 ID="BP115"RENDERAS="SECT3"ID="FM68028"BROADCAST SEND DELAY=numberIDXID="w11685"BOOK="_idx" COLLECTION="nw41" TIDREF="i526"
Sets the number of ticks the NetWare DOS Requester software waits between performing any function. Set this to a higher number if you are using slow links such as modem or serial links on your network.Increasing this number decreases the response time of some utilities. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"broadcast send delay=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 255COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To ensure that utilities find resources connected by a serial cable, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  broadcast send delay=10PAGENUM=120 ID="BP116"RENDERAS="SECT3"ID="FM48554"BROADCAST TIMEOUT=numberIDXID="w11686"BOOK="_idx" COLLECTION="nw41" TIDREF="i527"
Sets the number of ticks the NetWare DOS Requester software waits between broadcast retries. Set this to a higher number if you are trying to see resources physically located at a long distance from your workstation. Increasing this number decreases the response time of some utilities. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"broadcast timeout=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 255COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To enable a workgroup to display in the WGLIST utility that is unreachable by using the default value, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  broadcast timeout=60RENDERAS="SECT3"ID="FM58957"CACHE BUFFER SIZE=numberIDXID="w11687"BOOK="_idx" COLLECTION="nw41" TIDREF="i571"
Sets the buffer size (in bytes) for the cache buffers that the FIO module uses. Increasing the value of the parameter allows you to cache larger amounts of data, thereby increasing performance and also memory use.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"cache buffers size=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Media maximum minus 64 bytes  (For example, Ethernet: 1500 - 64 = 1436) See the manufacturer's documentation for the cache buffer size for your media type.COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"64 to 4096 bytesCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To cache larger amounts of data than the default allows, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  cache buffers size=1024PAGENUM=121 ID="BP117"When specifying the value for this parameter, don't exceed the maximum packet size of the network board. Doing so might cause system failure. RENDERAS="SECT3"ID="FM94123"CACHE BUFFERS=numberIDXID="w11688"BOOK="_idx" COLLECTION="nw41" TIDREF="i573"
Sets the number of cache buffers the NetWare DOS Requester software uses for local caching of nonshared, nontransactionally tracked files.Each buffer allocated allows one file to be cached.You can increase the number of cache buffers to speed up the process of sequential reads/writes. Increasing the value of this parameter decreases available memory. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"cache buffers=numberReplace number with the value from the DOS CONFIG.SYS command "FILES = number" minus 5, or with any number through 64.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"5 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 64COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To speed up the process of sequential reads/writes to match a FILES=30 setting in the CONFIG.SYS file, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  cache buffers=25PAGENUM=122 ID="BP118"RENDERAS="SECT3"ID="FM33185"CACHE WRITES=[on | off]IDXID="w11689"BOOK="_idx" COLLECTION="nw41" TIDREF="i577"
Sets the cache write requests to "on" or "off." The default setting "on" increases performance of the NetWare Client software by waiting for a request from the server before writing data to disk.Setting the value for this parameter to "off" increases data integrity but decreases performance. Leaving the value for this parameter set to the "on" default can cause data loss if the NetWare server runs out of disk space between write requests. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"cache writes=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase data integrity at the expense of performance, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  cache writes=offRENDERAS="SECT3"ID="FM70333"CHECKSUM=numberIDXID="w11690"BOOK="_idx" COLLECTION="nw41" TIDREF="i625"
Provides a higher level of data integrity by validating NetWare Core ProtocolTM, or NCPTM, packets. Setting the value for this parameter to 2 or 3 increases data integrity but decreases performance. The checksum values are the following:TYPE="VERT"0 = Disabled1 = Enabled but not preferred2 = Enabled and preferred3 = Required COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"checksum=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"IPXNCP.VLM, NWP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase data integrity at the expense of performance, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  checksum=3PAGENUM=123 ID="BP119"Ethernet frame type 802.3 doesn't support checksums.  RENDERAS="SECT3"ID="FM30762"CONFIRM CRITICAL ERROR ACTION=[on | off]IDXID="w11691"BOOK="_idx" COLLECTION="nw41" TIDREF="i772"
Determines the default method used for handling network critical error messages in MS Windows.MS Windows often intercepts critical errors intended for the NetWare DOS Requester and displays the following error messageFORMAT="LINESPECIFIC"MOREINFO="NONE""Cannot read from device network"or intercepts the error message, but does not display the message because MS Windows is running in Auto Fail mode.If the error message response is to "Cancel", or MS Windows automatically fails, the network connection that issued the critical error is torn down and the NetWare DOS Requester proceeds to clean up the connection. Nevertheless, the client workstation is not informed of which connection that was lost. The two values are as follows:TYPE="VERT"ON = A dialog box is displayed showing the server name of the connection that has gone down. You are prompted to "Cancel" or "Retry" before MS Windows responds. The dialog box provides additional information about the error and notifies the user in case of an Auto Fail.PAGENUM=124 ID="BP120"OFF = MS Windows often intercepts critical errors and automatically responds to error messages intended for the NetWare DOS Requester.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"confirm critical error action=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow MS Windows to handle network critical errors, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  confirm critical error action=offFor this parameter to function properly, use the NETWARE.DRV version 3.03 or later, and include the "network.drv=netware.drv" line under the [boot] heading in the MS Windows SYSTEM.INI file.This parameter affects the performance of your MS Windows environment.  RENDERAS="SECT3"ID="FM29223"CONNECTIONS=numberIDXID="w11692"BOOK="_idx" COLLECTION="nw41" TIDREF="i791"
Sets the maximum number of connections the NetWare DOS Requester software supports. The NetWare DOS Requester supports up to 50 connections in its connection table. A value larger than needed uses memory unnecessarily.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"connections=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"2 to 50 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"AUTO.VLM, CONN.VLM, FIO.VLM, NDS.VLM, SECURITY.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the number of server connections you can have to 12, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  connections=12PAGENUM=126 ID="BP121"Setting the value to other than 8 might decrease NETX compatibility. Do not use this parameter if you are unsure of the maximum number of connections you are making to NetWare 3 or earlier servers.  If you lower the number of connections to fewer than 8, ensure that your client workstation does not exceed the number during operation. If the maximum number of connections is exceeded, you might experience some problems with all of your server connections.RENDERAS="SECT3"ID="FM71782"DOS NAME="name"IDXID="w11693"BOOK="_idx" COLLECTION="nw41" TIDREF="i1192"
Sets the name of the operating system used in the shell. The %OS variable in the login or profile script uses this variable when mapping a search drive to the network DOS directory.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"dos name="nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"MSDOSCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 5 charactersCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLM, NETX.VLM COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the operating system used for the shell to DR DOS®, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  dos name=drdosThe NetWare DOS Requester software automatically recognizes DR DOS and sets this option. However, setting this option overrides the auto-detect feature. RENDERAS="SECT3"ID="FM69676"EOJ=[on | off]IDXID="w11694"BOOK="_idx" COLLECTION="nw41" TIDREF="i1332"
Specifies whether files, locks, semaphores, etc., are closed automatically at end of a job.PAGENUM=127 ID="BP122"This supports End Of Job (EOJ) commands from a DOS INT 21 D6 function call.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"eoj=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"NETX.VLM, REDIR.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a client workstation to not send End Of Job commands for closing files to the server, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  eoj=offRENDERAS="SECT3"ID="FM26176"EXCLUDE VLM=path_vlmIDXID="w11695"BOOK="_idx" COLLECTION="nw41" TIDREF="i1370"
Specifies a .VLM file that the VLM.EXE program should not load. This parameter causes any .VLM file listed in the VLM.EXE program default load table or in the VLM vlm_path parameter to not load when the VLM.EXE program runs.You must specify the complete filename, including the .VLM extension.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"exclude vlm=path_vlmCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 50COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To exclude the loading of the PRINT.VLM, SECURITY.VLM, and NMR.VLM files with the core modules, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  exclude vlm=c:\nwclient\print.vlmMOREINFO="NONE"  exclude vlm=c:\nwclient\security.vlmMOREINFO="NONE"  exclude vlm=c:\nwclient\nmr.vlmPAGENUM=128 ID="BP123"RENDERAS="SECT3"ID="FM41018"FIRST NETWORK DRIVE=drive_letterIDXID="w11696"BOOK="_idx" COLLECTION="nw41" TIDREF="i1514"
Sets the first network drive to the letter of choice when the NetWare DOS Requester software makes a connection to the NetWare server. This parameter accepts only the drive letter and not the colon.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"first network drive=drive_letterCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"First available driveCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"A to ZCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLM, NETX.VLM, REDIR.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the first drive to G:, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  first network drive=gRENDERAS="SECT3"ID="FM95316"FORCE FIRST NETWORK DRIVE=[on | off]IDXID="w11697"BOOK="_idx" COLLECTION="nw41" TIDREF="i1533"
Specifies the network drive letter the SYS:LOGIN directory is mapped to after logging out of a server or network. Setting the value to "on" specifies that the drive letter must be the same as the one use in FIRST NETWORK DRIVE.  Previously, if you typed "LOGOUT" from any drive other than a local drive or the FIRST NETWORK DRIVE, the SYS:LOGIN drive would be mapped to the drive letter you logged out from.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"force first network drive=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that the first network drive letter be the same before and after you log out, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  force first network drive=onPAGENUM=129 ID="BP124"For this parameter to work, also set FIRST NETWORK DRIVE=drive.  The drive is map rooted to the first network drive and not to the \LOGIN directory as with the NetWare Shell software such as NETX. You should modify any batch files effected by this change.RENDERAS="SECT3"ID="FM36547"HANDLE NET ERRORS=[on | off]IDXID="w11698"BOOK="_idx" COLLECTION="nw41" TIDREF="i1629"
Determines the default method for handling network errors. A network error is generated when the client workstation doesn't receive a response from the NetWare server. The two values are as follows:TYPE="VERT"On = interrupt 24 handles network errorsOff = return NET_RECV_ERROR (example: 8805h)COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"handle net errors=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"IPXNCP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To receive an error return of "NET_RECV_ERROR," you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  handle net errors=onRENDERAS="SECT3"ID="FM31456"LARGE INTERNET PACKETS=[on | off]IDXID="w11699"BOOK="_idx" COLLECTION="nw41" TIDREF="i2069"
Sets the Large Internet Packet (LIP) packet size above the default of 576 bytes.In the past, NetWare communicated across routers and bridges with a 576-byte maximum packet size. However, Ethernet and token ring are capable of using larger packets for communication.When the value for this parameter is set to "on," the maximum packet size negotiated between the NetWare server and the client workstation is used, even across routers and bridges.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"large internet packets=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"IPXNCP.VLM, NWP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To minimize the packet size used between the NetWare server and client workstation, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  large internet packet=offPAGENUM=130 ID="BP125"Some routers and bridges have been hardcoded to use 576-byte packets. In this case, the NetWare DOS Requester can use only 576-byte packets, regardless of this parameter.RENDERAS="SECT3"ID="FM38196"LIP START SIZE=numberIDXID="w11700"BOOK="_idx" COLLECTION="nw41" TIDREF="i2127"
Specifies the packet size of used by the NetWare DOS Requester when starting LIP negotiations. Use this parameter to reduce the amount of traffic caused by the negotiation process across slow links.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"load conn table low=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase conventional memory requirements required by the NetWare Client software for supporting the initial release of NetWare 4.0 utilities, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  load conn table low=onFor this parameter to work, also set LARGE INTERNET PACKETS=ON.  PAGENUM=131 ID="BP126"RENDERAS="SECT3"ID="FM46920"LOAD CONN TABLE LOW=[on | off]IDXID="w11701"BOOK="_idx" COLLECTION="nw41" TIDREF="i2139"
Specifies whether the connection table is loaded in high or conventional memory.When using the initial release of NetWare 4.0 network operating system utilities, you must set the value of the LOAD CONN TABLE LOW parameter to "on."This loads the connection table low, which increases conventional memory requirements required by the initial release of NetWare 4.0 utilities.If you are not using the initial release of the NetWare 4.0 utilities, the default value (off) gives you better memory performance. The default setting loads the connection table in an Upper Memory Block (UMB), if available.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"load conn table low=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase conventional memory requirements required by the NetWare Client software for supporting the initial release of NetWare 4.0 utilities, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  load conn table low=onUse the VLM /D command-line parameter to determine how much conventional memory is used by this parameter setting. RENDERAS="SECT3"ID="FM99234"LOAD LOW CONN=[on | off]IDXID="w11702"BOOK="_idx" COLLECTION="nw41" TIDREF="i2142"
Specifies whether the connection manager is loaded in high or conventional memory.By default, the connection manager, CONN.VLM, is loaded in conventional memory. PAGENUM=132 ID="BP127"If the value for this parameter is set to "off," CONN.VLM loads in upper memory, saving memory but sacrificing performance.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"load low conn=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To load CONN.VLM in upper memory, thereby saving memory but sacrificing performance, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  load low conn=offUse the VLM /D command-line parameter to determine how much conventional memory is used by this parameter setting. RENDERAS="SECT3"ID="FM88067"LOAD LOW IPXNCP=[on | off]IDXID="w11703"BOOK="_idx" COLLECTION="nw41" TIDREF="i2143"
Specifies whether the transport manager for IPX is loaded in high (XMS or EMS) or conventional memory.By default, the transport protocol implementation for IPX, IPXNCP.VLM, is loaded in conventional memory. If the value for this parameter is set to "off," IPXNCP.VLM loads in upper memory, saving memory but sacrificing performance.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"load low ipxncp=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"IPXNCP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To load IPXNCP.VLM in upper memory, thereby saving memory but sacrificing performance, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  load low ipxncp=offPAGENUM=133 ID="BP128"Use the VLM /D command-line parameter to determine how much conventional memory is used by this parameter setting. RENDERAS="SECT3"ID="FM27448"LOAD LOW REDIR=[on | off]IDXID="w11704"BOOK="_idx" COLLECTION="nw41" TIDREF="i2143"
Specifies whether the redirector is loaded in high or conventional memory.This parameter influences the speed of repeated small file read/writes to the network, such as database transactions.By default, the redirector portion of the NetWare DOS Requester software, REDIR.VLM, is loaded in high memory. If the value for this parameter is set to "on," REDIR.VLM loads in conventional memory, increasing performance but sacrificing memory.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"load low redir=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"REDIR.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To load REDIR.VLM in conventional memory, thereby increasing performance but sacrificing memory, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  load low redir=onUse the VLM /D command-line parameter to determine how much conventional memory is used by this parameter setting. PAGENUM=134 ID="BP129"RENDERAS="SECT3"ID="FM85505"LOCAL PRINTERS=numberIDXID="w11705"BOOK="_idx" COLLECTION="nw41" TIDREF="i2168"
Overrides the number of local printers connected to the client workstation, which is normally determined by the BIOS. The BIOS defaults to one local printer for each parallel port.By setting the number of local printers to 0, you can prevent your workstation from hanging when you press MOREINFO="NONE"<Shift>+MOREINFO="NONE"<Print Screen> without any port capture or local printer connection.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"local printers=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 9COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To prevent your workstation from hanging when you press MOREINFO="NONE"<Shift> and MOREINFO="NONE"<Print Screen> without any port capture or local printer connection, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  local printers=0RENDERAS="SECT3"ID="FM47395"LOCK DELAY=numberIDXID="w11706"BOOK="_idx" COLLECTION="nw41" TIDREF="i2175"
Determines the amount of time (in ticks) the NetWare DOS Requester software waits before trying to get a lock.When many users access a file at the same time, the NetWare DOS Requester software might be unable to gain access before its allotted wait time.Use this parameter if client workstations frequently receive error messages when a file is requested.PAGENUM=135 ID="BP130"This number is used for lock types that do not have a wait ability. For locks that have a wait ability, the wait time is calculated by multiplying this parameter number by the LOCK RETRIES number and then multiplying by 2. The resulting number is the time, in ticks, the client workstation waits for a lock.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"lock delay=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1 tickCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 255 (approximately six hours)COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To automatically clear messages from a user's screen after three hours, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  lock delay=50To determine the total time (in ticks) needed to broadcast a name resolution packet across the network, multiply this value by the value used for the LOCK RETRIES parameter.  There are approximately 18.21 ticks per second on IBM PCs and compatibles. RENDERAS="SECT3"ID="FM50633"LOCK RETRIES=numberIDXID="w11707"BOOK="_idx" COLLECTION="nw41" TIDREF="i2176"
Specifies the number of times the NetWare DOS Requester software attempts to get a lock on the network. It is part of an equation that determines the total time the NetWare DOS Requester waits when attempting to access a locked file. If a client workstation frequently receives error messages when a file is requested, increase the value of this parameter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"lock delay=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1 tickCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 255 (approximately six hours)COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To automatically lock files, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  lock retires=50PAGENUM=136 ID="BP131"This number is used for lock types that do not have a wait ability. For locks that have a wait ability, the wait time is calculated by multiplying this parameter number by the LOCK DELAY number and then multiplying by 2. The resulting number is the time, in ticks, the client workstation waits for a lock.To determine the total time (in ticks) needed to broadcast a name resolution packet across the network, multiply this value by the value used for the LOCK DELAY parameter.  There are approximately 18.21 ticks per second on IBM PCs and compatibles. RENDERAS="SECT3"ID="FM55838"LONG MACHINE TYPE="name"IDXID="w11708"BOOK="_idx" COLLECTION="nw41" TIDREF="i2234"
Tells the NetWare DOS Requester software what type of machine is being used each time the %MACHINE variable is accessed. Use this parameter and value to set the machine's search path to the correct version of DOS.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"long machine type="nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"IBM-PCCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 6COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLM, NETX.VLM COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the machine type as COMPAQ, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  long machine type="compaq"PAGENUM=137 ID="BP132"RENDERAS="SECT3"ID="FM75203"MAX TASKS=numberIDXID="w11709"BOOK="_idx" COLLECTION="nw41" TIDREF="i2352"
Configures the maximum number of tasks that can be active simultaneously.Certain multitasking applications, such as MS Windows and DESQview*, allow several applications to run simultaneously.If you have problems running a new application, increase the value of this parameter. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"max tasks=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"31 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"5 to 254 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"CONN.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow for 68 tasks to run simultaneously, you would place the following lines in your NET.CFG file: MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  max tasks=68RENDERAS="SECT3"ID="FM56219"MESSAGE LEVEL=numberIDXID="w11710"BOOK="_idx" COLLECTION="nw41" TIDREF="i2413"
Sets how load-time messages are displayed. Each message level implies the previous level's message (for example, 1 implies 0). The values are as follows:TYPE="VERT"0 = Display copyright message and critical errors1 = Display warning messages2 = Display program load information for VLM programsPAGENUM=138 ID="BP133"3 = Display configuration information4 = Display diagnostic informationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"message level=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To display only configuration information, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  message level=3RENDERAS="SECT3"ID="FM50257"MESSAGE TIMEOUT=numberIDXID="w11711"BOOK="_idx" COLLECTION="nw41" TIDREF="i2416"
Defines how long (in ticks) before broadcast messages are cleared from the screen without user intervention.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"message timeout=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 (wait for user) to 10,000 (approximately nine minutes)COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"NWP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To automatically clear messages from a user's screen after approximately five minutes, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  message timeout=5000PAGENUM=139 ID="BP134"RENDERAS="SECT3"ID="FM18576"MINIMUM TIME TO NET=numberIDXID="w11712"BOOK="_idx" COLLECTION="nw41" TIDREF="i2467"
Overrides the time-to-net value defined by the local router during connection.This parameter is used for bridged WAN/Satellite links with time-to-net values set too low for workstations to make a connection under either of the following conditions:MARK=BULLETThe server on the other side of the link is a NetWare 3TM or earlier server not running the Packet BurstTM protocolThe transfer rate for the link is 2400 baud or lessCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"minimum time to net=numberReplace number with the number of milliseconds (1000=one second) needed for maintaining a connection over bridges and routers.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 65535COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"IPXNCP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the time-to-net value for a 2400-baud link to 10 seconds, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  minimum time to net=10000PAGENUM=140 ID="BP135"RENDERAS="SECT3"ID="FM83779"NAME CONTEXT="name_context"IDXID="w11713"BOOK="_idx" COLLECTION="nw41" TIDREF="i2576"
Allows you to set your current position, or context, in the Directory tree structure. This parameter and value apply only to client workstations connecting to a NetWare 4 network.The default is the root, which might cause confusion if duplicate usernames exist.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"name context="MOREINFO="NONE"name_contextMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"RootCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"Root to 257 (256 characters plus the NULL command)COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"NDS.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set your name context to the marketing Organization, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  name context="ou=mngt.o=marketing"RENDERAS="SECT3"ID="FM83430"NETWARE PROTOCOL=netware_protocol_listIDXID="w11714"BOOK="_idx" COLLECTION="nw41" TIDREF="i2782"
Allows you to list the order that the NetWare protocols (NDS, BIND, and PNW) are used in. For example, you can give priority to a specific protocol for login, load order, or other functions performed by the NetWare DOS Requester software.Each protocol is separated by a comma or a space in the list.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netware protocol=netware_protocol_listCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"nds bind pnwCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To speed up login to a Personal NetWare server, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  netware protocol=pnw nds bindPAGENUM=141 ID="BP136"If using this parameter, list it first under the NetWare DOS Requester option of the NET.CFG file. RENDERAS="SECT3"ID="FM25724"NETWORK PRINTERS=numberIDXID="w11715"BOOK="_idx" COLLECTION="nw41" TIDREF="i2877"
Sets the number of LPT ports the NetWare DOS Requester software can capture. This parameter allows you to capture and redirect LPT1 through LPT9.Increasing the number value increases memory use. Setting the value for this parameter to 0 specifies that PRINT.VLM does not load.If you are setting more than three ports in MS Windows, edit the MS Windows WIN.INI file with an ASCII text editor and add as many lines as you need under the [port] section.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"[port]
lp1:=
lp2:=
lp3:=
lp4:=
net1:=
record.prn=Add a filename to a line under the [ports] option to have print files print directly to this file. The filename should have a .PRN file extension followed by an equal sign.PAGENUM=142 ID="BP137"This causes the named file to appear in the Control Panel "Printer Configuration" dialog box. Any print jobs sent to this file direct their output to it.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"network printers=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 9COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow for seven printer connections, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  network printers=7If you are using any application that uses the "netx=off" command, such as Microsoft Office, ensure that this parameter value is set to "on."  RENDERAS="SECT3"ID="FM83220"PB BUFFERS=numberIDXID="w11716"BOOK="_idx" COLLECTION="nw41" TIDREF="i3260"
Controls the use of the Packet Burst protocol for file input/output. Packet Burst is automatically enabled in the NetWare DOS Requester software.The values are as follows:TYPE="VERT"0 = offnonzero = on and increases the number of buffers.Setting this option to 0 decreases memory use and, in some cases, performance.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"pb buffers=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 10COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLM, IPXNCP.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable Packet Burst, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  pb buffers=0PAGENUM=143 ID="BP138"RENDERAS="SECT3"ID="FM46002"PBURST READ WINDOWS SIZE=numberIDXID="w11717"BOOK="_idx" COLLECTION="nw41" TIDREF="i3262"
Sets the read buffer size (in bytes) for MS Windows. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"pburst read windows size=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"3 to 128COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the read buffer size for better performance, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  pburst read windows size=64If you are using this option on any client workstation not running Packet Burst, changing the default of this parameter might result in critical network errors. RENDERAS="SECT3"ID="FM39829"PBURST WRITE WINDOWS SIZE=numberIDXID="w11718"BOOK="_idx" COLLECTION="nw41" TIDREF="i3263"
Sets the write buffer size (in bytes) for MS Windows.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"pburst write windows size=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"3 to 128COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase write buffer size, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  pburst write windows size=24PAGENUM=144 ID="BP139"If you are using this option on any client workstation not running Packet Burst, changing the default of this parameter might result in critical network errors. RENDERAS="SECT3"ID="FM66900"PREFERRED SERVER="server_name"IDXID="w11719"BOOK="_idx" COLLECTION="nw41" TIDREF="i3370"
Sets the NetWare server you attach to first and helps guarantee your connection to the network. If the server specified has a connection available, the NetWare DOS Requester attaches to that server. Otherwise, it responds to the nearest broadcasting server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"preferred server="server_nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"BIND.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the MKT_9 server as your preferred server connection, thereby speeding up log in to bindery services, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  preferred server=mkt_9If both preferred tree (for NetWare Directory Services) and preferred server (for bindery services) are specified, then the first protocol to successfully build an attachment is used. PAGENUM=145 ID="BP140"RENDERAS="SECT3"ID="FM74063"PREFERRED TREE="tree_name"IDXID="w11720"BOOK="_idx" COLLECTION="nw41" TIDREF="i3373"
Sets the Directory tree you first want to connect to in a NetWare 4 network if you have multiple trees.If the tree specified has a server with a free connection, the NetWare DOS Requester attaches to that tree. Otherwise, it attaches to the nearest tree that contains a User object for the user authenticating to the network server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"preferred tree="tree_nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"NDS.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the MARKETING tree as your preferred tree connection, thereby speeding up log in to NetWare Directory Services, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  preferred tree=marketingIf both PREFERRED TREE (for NetWare Directory Services) and PREFERRED SERVER (for bindery services) are specified, then the first protocol to successfully attach is used, such as NetWare Directory Services or Bindery services. RENDERAS="SECT3"ID="FM39892"PREFERRED WORKGROUP="workgroup_name"IDXID="w11721"BOOK="_idx" COLLECTION="nw41" TIDREF="i4833"
Sets the Personal NetWare workgroup you attach to first and helps guarantee your connection to the network. If the workgroup specified has a connection available, the NetWare DOS Requester software attaches to that workgroup. Otherwise, it connects to the nearest workgroup.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"preferred workgroup="workgroup_name"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the MKT_9 workgroup as your preferred workgroup connection, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  preferred workgroup=mkt_9PAGENUM=146 ID="BP141"If the PREFERRED TREE (for NetWare Directory Services), PREFERRED SERVER (for bindery services), and PREFERRED WORKGROUP (for Personal NetWare Services) parameters are all specified, then the first protocol to successfully build an attachment is used. RENDERAS="SECT3"ID="FM83120"PRINT BUFFER SIZE=numberIDXID="w11722"BOOK="_idx" COLLECTION="nw41" TIDREF="i3392"
Determines the size (in bytes) for the print buffer. The print buffer acts as a cache for 1-byte print requests, which increases the size of some jobs.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"print buffer size=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"64 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 256 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the buffer size for printing to 86, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  print buffer size=86While increasing the speed in some of your printing output, this parameter also increases memory use. RENDERAS="SECT3"ID="FM18170"PRINT HEADER=numberIDXID="w11723"BOOK="_idx" COLLECTION="nw41" TIDREF="i3415"
Sets the size of the buffer (in bytes) that holds the information used to initialize a printer for each print job.PAGENUM=147 ID="BP142"If you send print jobs with many instructions in the header (such as initializing a printer for an emulated mode or changing defaults, font selections, page length, or orientation) and the printer is not delivering all the requested attributes, increase the print header size.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"print header=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"64 COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 1024 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the size of the print header in order for all the printer attributes of a larger header to be delivered, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  print header=960RENDERAS="SECT3"ID="FM49693"PRINT TAIL=numberIDXID="w11724"BOOK="_idx" COLLECTION="nw41" TIDREF="i3472"
Sets the size of the buffer (in bytes) that holds the information used to reset the printer after a print job.If your printer is not clearing out the buffer completely or resetting after each print job, increase the print tail size.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"print tail=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 1024COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PRINT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the size of the print header, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  print header=64PAGENUM=148 ID="BP143"RENDERAS="SECT3"ID="FM92475"READ ONLY COMPATIBILITY=[on | off]IDXID="w11725"BOOK="_idx" COLLECTION="nw41" TIDREF="i3682"
Determines whether a file marked Read Only can be opened with a read/write access call. Certain applications require the value for this parameter to be set to "on." See the documentation provided with your application for details.Prior to NetWare 2.1, a program could open a Read Only file with write access without getting an error, though any attempt to write to the file produced an error. To be compatible with DOS, NetWare 2.1 or later does not allow a Read Only file to be opened for write access. PAGENUM=149 ID="BP144"Setting this parameter to "on" causes the shell to revert to the old mode and allow the open request to succeed.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"read only compatibility=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"REDIR.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To cause the shell to revert to the old mode and allow the open request to succeed, you would place the following in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  read only compatibility=onIf you are using any application that uses the "netx=off" command, such as Microsoft Office, ensure that this parameter value is set to "on."  RENDERAS="SECT3"ID="FM96139"RESPONDER=[on | off]IDXID="w11726"BOOK="_idx" COLLECTION="nw41" TIDREF="i3822"
Controls the communication and response of the client workstation. Also helps in reducing the NetWare DOS Requester software memory use on the client workstation. Setting the value to "off" causes the client workstation to ignore broadcasts and diagnostic communication.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"responder=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To reduce conventional memory use, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  responder=offPAGENUM=150 ID="BP145"RENDERAS="SECT3"ID="FM54415"SEARCH MODE=numberIDXID="w11727"BOOK="_idx" COLLECTION="nw41" TIDREF="i3978"
Alters the NetWare DOS Requester software's method for finding a file if it is not in the current directory.In previous NetWare ClientTM software versions, the default drive had to be a network drive for this parameter to function. But the NetWare DOS Requester is global and affects all .EXE and .COM files, regardless of the current drive.When using Search Mode, select the search mode that works correctly with most of your .EXE and .COM files.If you want to set a search mode for one particular .EXE or .COM file, use the "Search Mode" option in FLAG (see "BOOK="utlrfenu" COLLECTION="nw41"FLAG" in Utilities Reference).Valid search mode values are as follows:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="22*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ValueCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"No search instructions. Default value for executable files.COLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"If a directory path is specified in the executable file, the executable file searches only that path.If a path is not specified, the executable file searches the default directory and network search drives.COLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches only the default directory or the path specified.COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"If a directory path is specified in the executable file, the executable file searches only that path. If a path is not specified and the executable file opens data files flagged Read Only, the executable file searches the default directory and search drives.COLNAME=1 ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"Reserved.COLNAME=1 ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"The executable file searches the default directory and NetWare search drives whether or not the path is specified. If a search mode is set, the shell allows searches for any files with .XXX extension; otherwise the executable file searches only for .EXE, .COM, and .BAT files.COLNAME=1 ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"Reserved.COLNAME=1 ROTATE="0" MOREROWS="0"7COLNAME=2 ROTATE="0" MOREROWS="0"If the executable file opens data files flagged Read Only, the executable file searches the default directory and search drives whether or not the path is specified in the executable file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"search mode=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To cause the executable file to search only the default directory or the path specified, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  search mode=2PAGENUM=151 ID="BP146"RENDERAS="SECT3"ID="FM42168"SET STATION TIME=[on | off]IDXID="w11728"BOOK="_idx" COLLECTION="nw41" TIDREF="i4096"
Synchronizes the client workstation date and time with that of the NetWare server that the client workstation initially attaches to.Setting this option to "off" disables the synchronization feature.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"set station time=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable the synchronization feature, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  set station time=offPAGENUM=152 ID="BP147"RENDERAS="SECT3"ID="FM91125"SHORT MACHINE TYPE="name"IDXID="w11729"BOOK="_idx" COLLECTION="nw41" TIDREF="i4139"
Specifies which overlay files to use with the specific machine type of your client workstations.This parameter is similar to LONG MACHINE TYPE, except that it is used specifically with overlay files. Use it when the %SMACHINE variable is accessed. Examples of files using this parameter and value include the IBM$RUN.OVL file for the windowing utilities and the CMPQ$RUN.OVL file that uses a default black-and-white color palette for NetWare menus.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"short machine type="nameMOREINFO="NONE""COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"IBMCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 4 COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"GENERAL.VLM, NETX.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the machine type as AST, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  short machine type=astRENDERAS="SECT3"ID="FM72900"SHOW DOTS=[on | off]IDXID="w11730"BOOK="_idx" COLLECTION="nw41" TIDREF="i4142"
Specifies to display parent dots in list boxes for file and directory navigation.This parameter is supported only by NetWare 2.11 and later. PAGENUM=153 ID="BP148"The NetWare server doesn't have directory entries for ("." and "..") as DOS does. To see "." and ".." in directory listings, set the value for this parameter to "on."COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"show dots=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"REDIR.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To see parent dots in a directory listings, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  show dots=onYou should set SHOW DOTS=ON when using MS Windows 3.x or DOS graphical user interface (GUI) with NetWare.  RENDERAS="SECT3"ID="FM38061"SIGNATURE LEVEL=numberIDXID="w11731"BOOK="_idx" COLLECTION="nw41" TIDREF="i4151"
Designates the level of enhanced security support. Enhanced security includes the use of a message digest algorithm and a per connection/per request session state. The values are as follows:TYPE="VERT"0 = Disabled (the SECURITY.VLM file does not load)1 = Enabled but not preferred2 = Preferred3 = RequiredSetting this option to 2 or 3 increases security but decreases performance. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"signature level=numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"NWP.VLM, SECURITY.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To designate the level of enhanced security support as "required," you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  signature level=3PAGENUM=154 ID="BP149"Do not set the signature level in the NET.CFG file to a value of 0 if you are using AUTO RECONNECT or BIND RECONNECT parameters when connecting to NetWare 3 or earlier servers.  If this value is set to 0 in this situation, the reconnect feature will not function.RENDERAS="SECT3"ID="FM10063"TRUE COMMIT=[on | off]IDXID="w11732"BOOK="_idx" COLLECTION="nw41" TIDREF="i4587"
Selects whether the commit NCP is sent on DOS commit requests. TYPE="VERT"Off = Opts for performance over integrityOn = Opts for integrity over performanceSet this option to "on" when processing critical data (for example, database applications) to guarantee data integrity.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"true commit=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"offCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"FIO.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To select integrity over performance, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  true commit=onRENDERAS="SECT3"ID="FM13904"USE DEFAULTS=[on | off]IDXID="w11733"BOOK="_idx" COLLECTION="nw41" TIDREF="i4699"
Overrides the default .VLM files that the VLM.EXE program loads. Without it, the VLM.EXE program attempts to load the following files in the given order:PAGENUM=155 ID="BP150"TYPE="VERT"CONN.VLMIPXNCP.VLMTRAN.VLMSECURITY.VLMNDS.VLMBIND.VLMNWP.VLMFIO.VLMGENERAL.VLMREDIR.VLMPRINT.VLMNETX.VLMAUTO.VLMIf you specify VLM programs that are normally loaded by default in the NET.CFG file and you don't set the value for this parameter to "off," any default VLM program you specify attempts to load twice, producing an error during load.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"use defaults=[on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To load the AUTO.VLM file with the core modules and disable loading of the BIND.VLM file, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  use defaults=offMOREINFO="NONE"  vlm=conn.vlmMOREINFO="NONE"  vlm=ipxncp.vlmMOREINFO="NONE"  vlm=tran.vlmMOREINFO="NONE"  vlm=security.vlmMOREINFO="NONE"  vlm=nds.vlmMOREINFO="NONE"  ;vlm=bind.vlmMOREINFO="NONE"  vlm=nwp.vlmMOREINFO="NONE"  vlm=fio.vlmMOREINFO="NONE"  vlm=general.vlmMOREINFO="NONE"  vlm=redir.vlmMOREINFO="NONE"  vlm=print.vlmMOREINFO="NONE"  vlm=netx.vlmMOREINFO="NONE"  vlm=auto.vlmPAGENUM=156 ID="BP151"The EXCLUDE VLM parameter should be used instead of the USE DEFAULTS parameter for excluding specific core VLM programs.RENDERAS="SECT3"ID="FM82853"VLM=path_VLMSpecifies a .VLM file that the VLM.EXE program should load. This parameter and value allow VLM programs not listed in the default load table for the VLM.EXE program to be added to the table. The following .VLM files are not listed in the default load table:TYPE="VERT"AUTO.VLMMIB2IF.VLMMIB2PROT.VLMNMR.VLMRSA.VLMWSASN1.VLMWSDRVPRN.VLMPAGENUM=157 ID="BP152"WSREG.VLMWSSNMP.VLMWSTRAP.VLMYou must specify the complete filename, including the .VLM extension.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"vlm=path_vlmCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 50COLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"VLM.EXECOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To load AUTO.VLM, RSA.VLM, and NMR.VLM with the core modules, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  vlm=c:\nwclient\auto.vlmMOREINFO="NONE"  vlm=c:\nwclient\rsa.vlmMOREINFO="NONE"  vlm=c:\nwclient\nmr.vlmPAGENUM=158 ID="BP153"RENDERAS="SECT3"ID="FM65506"WORKGROUP NET=workgroup_net_addressIDXID="w11734"BOOK="_idx" COLLECTION="nw41" TIDREF="i4834"
Provides a way for your client workstation to find workgroup information outside of your local network. If your client workstation resides physically on a network segment other than the one that the workgroup you want to connect to is on, setting this address ensures that a connection is found.This parameter and value should be modified only with the Personal NetWare utilities and should not be edited manually. Manually setting a value for this parameter might result in loss of connection.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"workgroup net=workgroup_net_addressCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ModulesCOLNAME=2 ROTATE="0" MOREROWS="0"PNW.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a network address of 00123099:FFFFFFFFFFFF for your workgroup, you would place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos requesterMOREINFO="NONE"  workgroup net=00123099:FFFFFFFFFFFFRENDERAS="SECT1"ID="FM81529"NetWare DOS TSA OptionIDXID="w11735"BOOK="_idx" COLLECTION="nw41" TIDREF="i2738"
Use this IDXID="w11736"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to change the default values of parameters for the DOS Target Service AgentTM (TSA) software.PAGENUM=159 ID="BP154"RENDERAS="SECT2"Available Parameters and Values for the NetWare DOS TSA OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM36353"DISK BUFFERS numberIDREF="FM86268"DRIVES drive_letterIDREF="FM89589"PASSWORD nameIDREF="FM12381"STACK SIZE numberIDREF="FM33638"TSA SERVER NAME server_nameIDREF="FM84905"WORKSTATION NAME unique_nameCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36353"161IDREF="FM86268"161IDREF="FM89589"162IDREF="FM12381"162IDREF="FM33638"163IDREF="FM84905"163RENDERAS="SECT2"ID="FM35545"NETWARE IDXID="w11737"BOOK="_idx" COLLECTION="nw41" TIDREF="i2738"
DOS TSAControls network requests from your client workstation to a NetWare server for the TSA.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"netware dos tsa  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use.Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a password for a client workstation, you could place these lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  password station1PAGENUM=160 ID="BP155"RENDERAS="SECT3"ID="FM36353"DISK BUFFERS numberIDXID="w11738"BOOK="_idx" COLLECTION="nw41" TIDREF="i1111"
Determines the size (in bytes) for the disk buffers. The disk buffer acts as a cache for 1-byte disk requests. Increasing the size of the buffers increases the speed of the data transfer, but it requires more RAM.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"disk buffers numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 30COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the number of buffers, thereby increasing throughput speed, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  disk buffers 23RENDERAS="SECT3"ID="FM86268"DRIVES drive_letterIDXID="w11739"BOOK="_idx" COLLECTION="nw41" TIDREF="i1234"
Specifies the hard drives managed by the Target Service Agent. The TSA does not manage floppy drivers or network drives.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"drives drive_letterCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"CCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a drive you want managed by the TSA, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  drives DTo specify more than one drive letter, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  drives D EPAGENUM=161 ID="BP156"RENDERAS="SECT3"ID="FM89589"PASSWORD nameIDXID="w11740"BOOK="_idx" COLLECTION="nw41" TIDREF="i3244"
Identifies the target workstation's unique password, or is used initially to specify a password. Limited to ten characters.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"password nameCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a password for the TSA to use when managing the workstation, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  password station1RENDERAS="SECT3"ID="FM12381"STACK SIZE numberIDXID="w11741"BOOK="_idx" COLLECTION="nw41" TIDREF="i4248"
Specifies the stack size for TSA. Use only if the available RAM on your workstation is extremely limited or you receive a "Stack Overflow" message.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"stack size numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"2048COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"512 to 4096COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the number of protocol stack IDs that can be loaded, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  stack size 1024PAGENUM=162 ID="BP157"RENDERAS="SECT3"ID="FM33638"TSA SERVER NAME server_nameIDXID="w11742"BOOK="_idx" COLLECTION="nw41" TIDREF="i4597"
Specifies the name of the NetWare server you want the target workstation to connect to.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"tsa server name server_nameCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the name of the TSA server you want to connect to, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  tsa server name server3RENDERAS="SECT3"ID="FM84905"WORKSTATION NAME unique_nameIDXID="w11743"BOOK="_idx" COLLECTION="nw41" TIDREF="i4839"
Identifies the target workstation's unique name. Also used initially to name a client workstation. A value for this parameter is required the first time you load the TSASMS.COM file for a particular server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"workstation name unique_nameReplace unique_name with the name of a client workstation. The name must be unique from other workstation names.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 10 charactersCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a unique name for the workstation you want managed through the TSA, you could place the following lines in your NET.CFG file:MOREINFO="NONE"netware dos tsaMOREINFO="NONE"  workstation name bob_486RENDERAS="SECT1"PAGENUM=163 ID="BP158"ID="FM17940"Protocol IPX OptionIDXID="w11744"BOOK="_idx" COLLECTION="nw41" TIDREF="i3591"
Use this IDXID="w11745"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to change the default value of parameters for the IPXTM protocol.RENDERAS="SECT2"Available Parameters and Values for the Protocol IPX OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM59339"BIND LAN_driver_name [#number]IDREF="FM82975"INT64 [on | off]IDREF="FM89509"INT7A [on | off]IDREF="FM21910"IPATCH byte_offset, valueIDREF="FM39584"IPX PACKET SIZE LIMIT numberIDREF="FM73289"IPX RETRY COUNT numberIDREF="FM57912"IPX SOCKETS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM59339"165IDREF="FM82975"166IDREF="FM89509"166IDREF="FM21910"167IDREF="FM39584"167IDREF="FM73289"168IDREF="FM57912"168RENDERAS="SECT2"ID="FM78647"PROTOCOL IDXID="w11746"BOOK="_idx" COLLECTION="nw41" TIDREF="i3591"
IPXSpecifies the protocol option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol ipx  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use.Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure for the IPX protocol to not use interrupt 64h, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  int64 offPAGENUM=164 ID="BP159"RENDERAS="SECT3"ID="FM59339"BIND LAN_driver_name [#number]IDXID="w11747"BOOK="_idx" COLLECTION="nw41" TIDREF="i431"
Usually a protocol binds to the first LAN driver it finds. This parameter forces the protocol to bind to the LAN driver you specify.You are informed of the board number you are binding to when the LAN driver is loading.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"bind LAN_driver_nameMOREINFO="NONE" [#numberMOREINFO="NONE"]Replace LAN_driver_name with the name of the LAN driver you want the protocol to bind to.Replace number with the occurrence of the LAN driver you are loading. If you are binding only one LAN driver, you do not need to set this value.If you want to bind multiple LAN drivers, specify the BIND parameter multiple times, each on a different line in the NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind protocol IPXODI to your NE2000 LAN driver, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  bind ne2000To bind protocol IPXODI to the second and third logical LAN drivers, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  bind ne2000 #2, #3Some protocols do not support binding to multiple LAN drivers. Refer to the protocol's documentation for binding information.PAGENUM=165 ID="BP160"RENDERAS="SECT3"ID="FM82975"INT64 [on | off]IDXID="w11748"BOOK="_idx" COLLECTION="nw41" TIDREF="i1890"
Allows applications to use interrupt 64h to access IPX services. IPX now uses interrupt 64h to maintain compatibility with earlier versions of NetWare software. If an application's documentation requests interrupt 64h, or if you have an application that works with earlier versions of NetWare but hangs with NetWare 3.1, set the value for this parameter to "off." COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"int64 [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow an application use interrupt 64h, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  int64 offRENDERAS="SECT3"ID="FM89509"INT7A [on | off]IDXID="w11749"BOOK="_idx" COLLECTION="nw41" TIDREF="i1892"
Allows applications to use interrupt 7Ah to access IPX services. IPX now uses interrupt 7Ah to maintain compatibility with NetWare 2.0a. If an application's documentation requests interrupt 7Ah, or if an application works on earlier versions of NetWare software but hangs with NetWare 3.1, set the value for this parameter to "off." COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"int7a [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow an application to use interrupt 7Ah, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  int7a offPAGENUM=166 ID="BP161"RENDERAS="SECT3"ID="FM21910"IPATCH byte_offset, valueIDXID="w11750"BOOK="_idx" COLLECTION="nw41" TIDREF="i1920"
Allows any address in the IPXODI.COM file to be patched with any specified byte offset value. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ipatch byte_offsetMOREINFO="NONE", valueCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To patch a byte offset value in the IPXODI.COM file, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  ipatch 6775RENDERAS="SECT3"ID="FM39584"IPX PACKET SIZE LIMIT numberIDXID="w11751"BOOK="_idx" COLLECTION="nw41" TIDREF="i1945"
Reduces the maximum packet size (in bytes) set by each LAN driver. Even though a LAN driver could send 16KB packets across the wire, the wasted memory for most operations might be unacceptable.The optimum packet size for token ring drivers is 4160 bytes. For Ethernet, the optimum is 1500 bytes. Reduce the maximum packet size if you receive out-of-memory errors at the client workstation.This parameter is a new feature, and not all LAN drivers support it. See the documentation provided with your LAN driver for details.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ipx packet size limit numberReplace number with the size set by the LAN driver.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The lesser of either 4160 or the size specified by the LAN driverCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"576 to 6500COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To reduce the maximum packet size for an Ethernet ODI LAN driver from the default, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  ipx packet size limit 1200PAGENUM=167 ID="BP162"RENDERAS="SECT3"ID="FM73289"IPX RETRY COUNT numberIDXID="w11752"BOOK="_idx" COLLECTION="nw41" TIDREF="i1954"
Sets the number of times the client workstation resends a packet. On networks that lose many packets, this retry count might need to be increased.The IPX protocol does not actually resend a packet. It uses this count to recommend the number of retries to the NetWare DOS Requester software and the SPX protocol.Increasing this number causes a longer delay for some network functions, such as establishing a NetBIOS session or registering a NetBIOS name.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ipx retry count numberReplace number with the number of times the client workstation resends a packet.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20 COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of times the client workstation resends a packet to 30, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  ipx retry count 30RENDERAS="SECT3"ID="FM57912"IPX SOCKETS numberIDXID="w11753"BOOK="_idx" COLLECTION="nw41" TIDREF="i1960"
Specifies the maximum number of sockets that IPX can have open at the client workstation.PAGENUM=168 ID="BP163"A program developed to the IPX protocol standard, such as the LANSchool utility, might require more than the default number of sockets.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ipx sockets numberReplace number with the maximum number of sockets that IPX can have open at the client workstation.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20 COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of open sockets on a client workstation to 30, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol ipxMOREINFO="NONE"  ipx sockets 30RENDERAS="SECT1"ID="FM61267"Protocol ODINSUP OptionIDXID="w11754"BOOK="_idx" COLLECTION="nw41" TIDREF="i3595"
Use this IDXID="w11755"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option to allow the 
NDIS protocol stack (used with Extended Services* and LAN Services*) to communicate using ODI token ring or Ethernet drivers.RENDERAS="SECT2"Available Parameters and Values for the Protocol ODINSUP OptionThis option has the following 
parameter and value, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM69414"BIND odi_driver [number]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69414"171PAGENUM=169 ID="BP164"RENDERAS="SECT2"ID="FM85171"PROTOCOL IDXID="w11756"BOOK="_idx" COLLECTION="nw41" TIDREF="i3595"
ODINSUPSpecifies the protocol option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol odinsup  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind ODINSUP to a single NE2000 ODI LAN driver, you would add the following lines to your NET.CFG file:MOREINFO="NONE"protocol odinsupMOREINFO="NONE"  bind ne2000PAGENUM=170 ID="BP165"RENDERAS="SECT3"ID="FM69414"BIND odi_driver [number]IDXID="w11757"BOOK="_idx" COLLECTION="nw41" TIDREF="i432"
Binds the ODINSUP protocol to an ODI LAN driver. When ODINSUP is bound to an ODI LAN driver, the network board that corresponds to the LAN driver is the network board used for transmissions to and from the network.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"bind odi_driverMOREINFO="NONE" [numberMOREINFO="NONE"]Replace odi_driver with the name of a token-ring or Ethernet ODI LAN driver.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Replace number with the instance of the LAN driver number.Use of this number binds ODINSUP to a particular occurrence of a network board when you have two boards with the same name.If multiple LAN drivers are to be bound to, specify the BIND parameter multiple times, each on a different line in the NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 4COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The first Ethernet or token-ring ODI LAN driver that ODINSUP.COM locates.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind ODINSUP to a single NE2000 ODI LAN driver, you would add the following lines to your NET.CFG file:MOREINFO="NONE"protocol odinsupMOREINFO="NONE"  bind ne2000To bind ODINSUP to both the first and the second NE2000 network boards in your client workstation, you would add the following lines to your NET.CFG file:MOREINFO="NONE"Protocol odinsupMOREINFO="NONE"  bind ne2000 1MOREINFO="NONE"  bind ne2000 2RENDERAS="SECT1"PAGENUM=171 ID="BP166"ID="FM39423"Protocol RFCNBIOS OptionIDXID="w11758"BOOK="_idx" COLLECTION="nw41" TIDREF="i3599"
Use this IDXID="w11759"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to change the default value of parameters for running NetBIOS applications with the TCP/IP protocol stack. IDREF="FM83096"See "Protocol TCPIP Option" on page 185 for information on configuring the TCP/IP protocol stack.The RFCNBIOS.EXE file implements the NetBIOS B-node protocols as defined in RFC 1001 and 1002. (The B-node protocols use broadcast datagrams for network management and some NetBIOS datagram operations.) With this RFCNBIOS software, you can run any network application designed for the standard NetBIOS interface. Run the TCP/IP Transport for DOS installation program provided on the CLASS=DISKTCP/IP Transport for DOS diskette to obtain a copy of the RFCNBIOS.EXE file. See Chapter 1, "Installing the Transport," in TCP/IP Transport for DOS Installation Guide for more information.All directly connected NetBIOS nodes that you plan to communicate with must use an RFC1001/1002-compliant NetBIOS program. Also, all NetBIOS implementations must be B-node configurations. RENDERAS="SECT2"Available Parameters and Values for the Protocol RFCNBIOS OptionThis option has the following 
parameter and value, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM70558"REMOTENAME number ip_addressCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM70558"173PAGENUM=172 ID="BP167"RENDERAS="SECT2"PROTOCOL IDXID="w11760"BOOK="_idx" COLLECTION="nw41" TIDREF="i3599"
RFCNBIOSSpecifies the protocol option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol rfcnbios  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that two IP address that are not on the same broadcast network as your client workstation be preloaded into the NetBIOS name cache, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol rfcnbiosMOREINFO="NONE"  remotename1 129.57.52.6MOREINFO="NONE"  remotename2 129.57.32.8RENDERAS="SECT3"ID="FM70558"REMOTENAME number ip_addressIDXID="w11761"BOOK="_idx" COLLECTION="nw41" TIDREF="i3768"
Specifies an IP address that is not on the same broadcast network as your client workstation. This address is preloaded in the NetBIOS name cache.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"remotename numberMOREINFO="NONE" ip_addressReplace number with the number of addresses to be preloaded in the NetBIOS name cache. Replace ip_address with the Internet Protocol address you have assigned to your particular workstation.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"1 to 16COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that two IP address that are not on the same broadcast network as your client workstation be preloaded into the NetBIOS name cache, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol rfcnbiosMOREINFO="NONE"  remotename1 129.57.52.6MOREINFO="NONE"  remotename2 129.57.32.8RENDERAS="SECT1"PAGENUM=173 ID="BP168"ID="FM64767"Protocol RPL OptionUse this IDXID="w11762"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to allow the Remote Program Load (RPL) protocol stack (used with Novell Remote Reset PROMs) to communicate using the RPL.NLM program for NetWare servers and the RPL.COM program for Personal NetWare servers.RENDERAS="SECT2"Available Parameters and Values for the Protocol RPL OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM12353"BIND driver [number]IDREF="FM30785"BUFFERS numberIDREF="FM24306"CACHE SIZE decimal_numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM12353"175IDREF="FM30785"178IDREF="FM24306"179PAGENUM=174 ID="BP169"RENDERAS="SECT2"PROTOCOL 
RPLSpecifies the protocol option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol rpl  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the size of receive buffers to 10, you would add the following line to your NET.CFG file:MOREINFO="NONE"protocol rplMOREINFO="NONE"  buffers 10RENDERAS="SECT3"ID="FM12353"BIND driver [number]Binds the IDXID="w11763"BOOK="_idx" COLLECTION="nw41" TIDREF="i433"
RPL protocol to a specific NetWare ODI LAN driver that is configured for the IEEE 802.2 frame type. Use only when running RPL on enhanced Remote Boot PROMs. For information on command line parameters for binding the RPL protocol to a LAN driver, IDREF="FM62716"See Chapter 3, "Command Line Parameters Reference," on page 211.PAGENUM=175 ID="BP170"If BIND is not specified on the command line or in the NET.CFG file, the RPL.COM file searches for and uses the first network board that supports an 802.2 LAN driver that is loaded into memory.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"bind odi_driver [number] [optional_value]Replace odi_driver with the name of a token-ring or Ethernet ODI LAN driver.Replace number the instance of the LAN driver number.Use of this number binds RPL to a particular occurrence of a LAN driver when you have two drivers with the same name.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Replace optional value with If multiple LAN drivers are to be bound to, specify the BIND parameter multiple times, each on a different line in the NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"RPL binds to the first Ethernet or token-ring LAN driver it locates.COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"number: 1 to 4  optional value: COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind RPL to a single NE2000 network board in your client workstation, you would add the following lines to your NET.CFG file:MOREINFO="NONE"protocol rplMOREINFO="NONE"  bind ne2000To bind RPL to both the first and the second NE2000 boards in your client workstation, you would add the following lines to your NET.CFG file:MOREINFO="NONE"Protocol rplMOREINFO="NONE"  bind ne2000 1MOREINFO="NONE"  bind ne2000 2PAGENUM=176 ID="BP171"Optional values for the IDXID="w11764"BOOK="_idx" COLLECTION="nw41" TIDREF="i433"
BIND parameter are listed in the following table.LABEL="2-12" PGWIDE=1 TOCENTRY="1" Optional Parameter Values for the BIND Protocol RPL OptionCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ValueCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11765"BOOK="_idx" COLLECTION="nw41" TIDREF="i75"
ackCOLNAME=2 ROTATE="0" MOREROWS="0"Configures the RPL Remote Boot PROM module to acknowledge FILE.DATA.RESPONSE frames sent by the RPL.COM file. By default, the RPL.COM file sends FILE.DATA.RESPONSE frames in a burst mode. This value allows you to set the pace that your client workstation receives these frames at.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11766"BOOK="_idx" COLLECTION="nw41" TIDREF="i1608"
gnsCOLNAME=2 ROTATE="0" MOREROWS="0"Sets up your client workstation to do a Get Nearest Server request when the appropriate bootstrap program is downloaded. Normally, the RPL.COM or RPL.NLM file fills in the bootstrap program with the Personal NetWare or NetWare server information, so that it does not need to do a Get Nearest Server request. Using this value might cause the client workstation to find a server other than the one where the RPL.COM or RPL.NLM file is located.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11767"BOOK="_idx" COLLECTION="nw41" TIDREF="i2955"
nodefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Informs the RPL.COM or RPL.NLM file to not respond to a Find Frame request unless the node address of the client workstation is found in the BOOTCONF.SYS file. For security reasons, the client workstation does not boot until the network supervisor inserts the node address and associated disk image filename into the BOOTCONF.SYS file used when booting the client workstation.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11768"BOOK="_idx" COLLECTION="nw41" TIDREF="i3582"
protectCOLNAME=2 ROTATE="0" MOREROWS="0"Informs the RPL.COM or RPL.NLM file to configure the bootstrap program to protect the memory it occupies. Using this value reduces the amount of memory that the client workstation has available for DOS by about 12 KB. We recommend that you use this value only when memory conflicts occur. COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11769"BOOK="_idx" COLLECTION="nw41" TIDREF="i3784"
repCOLNAME=2 ROTATE="0" MOREROWS="0"Dynamically reconfigures a disk image file during the RPL process. It is useful for tailoring files such as AUTOEXEC.BAT or CONFIG.SYS to a specific client workstation.There are three rules for using REP:MARK=BULLETThe search is done in uppercase ASCII text.All occurrences of string1 are replaced with string2 in the disk image file.String2 must be equal to or shorter than string1.    If string2 is shorter than string1, the disk image file is padded with ASCII Blanks when the substitution is made.PAGENUM=177 ID="BP172"RENDERAS="SECT3"ID="FM30785"BUFFERS numberSpecifies the number of receive IDXID="w11770"BOOK="_idx" COLLECTION="nw41" TIDREF="i551"PAGENUM=178 ID="BP173"buffers to configure. This parameter and value allow you to optimize for better performance.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"buffers numberReplace number with the maximum number of receive buffers the LAN driver can handle. COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"5COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"4 to 40COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the size of receive buffers to 10, you would add the following line to your NET.CFG file:MOREINFO="NONE"protocol rplMOREINFO="NONE"  buffers 10RENDERAS="SECT3"ID="FM24306"CACHE SIZE decimal_numberIDXID="w11771"BOOK="_idx" COLLECTION="nw41" TIDREF="i576"
Specifies the maximum memory size to use for loading the BOOTCONF.SYS file. If the BOOTCONF.SYS file is larger than the value set, the RPL.COM or RPL.NLM file does not cache the BOOTCONF.SYS file. The bootstrap program then makes a request through the network to load the BOOTCONF.SYS file.You can increase the size of cache to speed up the loading process. However, increasing the value for this parameter also increases memory use.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"cache size decimal_numberReplace decimal_number with amount of memory you want used.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the size of cache used, you could add the following line to your NET.CFG file:MOREINFO="NONE"protocol rplMOREINFO="NONE"  cache size 1024RENDERAS="SECT1"PAGENUM=179 ID="BP174"ID="FM51477"Protocol SPX OptionIDXID="w11772"BOOK="_idx" COLLECTION="nw41" TIDREF="i3602"
Use this IDXID="w11773"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to change the default value of parameters for the SPX protocol.RENDERAS="SECT2"Available Parameters and Values for the Protocol SPX OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM46541"MINIMUM SPX RETRIES numberIDREF="FM38327"SPX ABORT TIMEOUT numberIDREF="FM15658"SPX CONNECTIONS numberIDREF="FM45368"SPX LISTEN TIMEOUT numberIDREF="FM34466"SPX VERIFY TIMEOUT numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46541"181IDREF="FM38327"182IDREF="FM15658"182IDREF="FM45368"183IDREF="FM34466"183RENDERAS="SECT2"ID="FM49583"PROTOCOL IDXID="w11774"BOOK="_idx" COLLECTION="nw41" TIDREF="i3602"
SPXSpecifies the protocol option you are making configurations for. Use it to override the SPX retry value set by an application if SPX sessions are being destroyed because of a lack of acknowledgement between session hosts.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol spx  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of retries to 30, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  minimum spx retries 30PAGENUM=180 ID="BP175"RENDERAS="SECT3"ID="FM46541"MINIMUM SPX RETRIES numberIDXID="w11775"BOOK="_idx" COLLECTION="nw41" TIDREF="i2466"
Determines how many unacknowledged transmit requests are allowed before assuming the connection has failed.SPX applications have two methods of specifying a transmit retry count to SPX:MARK=BULLETThe application can specify a retry value at the time of connection.If the application doesn't specify a retry value, SPX uses the configured value setting for the IPX RETRY COUNT parameter (default is 20).This option is especially useful if an application that uses the SPX protocol is abnormally losing its connections. This might be due to a low value specified in the default retry count in the application or in the IPX RETRY COUNT parameter.This parameter is supported by IPXODI.COM 2.00 and later.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"minimum spx retries numberReplace number with the minimum number of times unacknowledged transmit requests are allowed before assuming the connection has failed.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 255COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of retries to 30, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  minimum spx retries 30PAGENUM=181 ID="BP176"RENDERAS="SECT3"ID="FM38327"SPX ABORT TIMEOUT numberIDXID="w11776"BOOK="_idx" COLLECTION="nw41" TIDREF="i4235"
Specifies how long (in ticks) the SPX protocol waits without receiving any response from the other side of the connection before it terminates the session. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"spx abort timeout numberReplace number with a number of ticks.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"540 (about 30 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the amount of time (in ticks) that SPX waits before it terminates the session to 20 seconds, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  spx abort timeout 300There are approximately 18.21 ticks per second on IBM PCs and compatibles. RENDERAS="SECT3"ID="FM15658"SPX CONNECTIONS numberIDXID="w11777"BOOK="_idx" COLLECTION="nw41" TIDREF="i4238"
Specifies the maximum number of SPX connections a client workstation can use at one time.The NPRINTER and RCONSOLE utilities use this setting. Increase the value of this setting if you are running multiple occurrences of these or other applications that use SPX.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"spx connections numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"15 COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of concurrent SPX connections to 10, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  spx connections 10PAGENUM=182 ID="BP177"RENDERAS="SECT3"ID="FM45368"SPX LISTEN TIMEOUT numberIDXID="w11778"BOOK="_idx" COLLECTION="nw41" TIDREF="i4239"
Specifies how long (in ticks) the SPX protocol waits without receiving a packet from the other side of the connection before it requests the other side to send a packet to ascertain whether the connection is still valid. If SPX has not heard from the other side of the connection within this time, it sends packets to the other side asking for verification that the connection still exists.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"spx listen timeout numberReplace number with a number of ticks.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"108 (about 6 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the amount of time (in ticks) that SPX waits before it requests a packet to 11 seconds, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  spx listen timeout 200There are approximately 18.21 ticks per second on IBM PCs and compatibles.  RENDERAS="SECT3"ID="FM34466"SPX VERIFY TIMEOUT numberIDXID="w11779"BOOK="_idx" COLLECTION="nw41" TIDREF="i4241"
Specifies how often (in ticks) the SPX protocol sends a packet to the other side of a connection to indicate that it is still alive. If no packets are being exchanged on the SPX connection by the software that established the session, SPX sends packets at regular intervals to verify its presence in the connection.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"spx verify timeout numberReplace number with a number of ticks.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"54 (about 3 seconds)COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that SPX send a packet to the other side of a connection every six seconds, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol spxMOREINFO="NONE"  spx verify timeout 108PAGENUM=183 ID="BP178"There are approximately 18.21 ticks per second on IBM PCs and compatibles.  RENDERAS="SECT1"ID="FM83096"Protocol TCPIP OptionIDXID="w11780"BOOK="_idx" COLLECTION="nw41" TIDREF="i3607"
Use this IDXID="w11781"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
option of the NET.CFG file to configure the TCP/IP protocol stack used by the IDXID="w11782"BOOK="_idx" COLLECTION="nw41" TIDREF="i4447"
TCPIP.EXE program. The TCPIP.EXE program reads the NET.CFG file for configuration information while loading. Run the IDXID="w11783"BOOK="_idx" COLLECTION="nw41" TIDREF="i4454"
TCP/IP Transport for DOS installation program provided on the CLASS=DISKTCP/IP Transport for DOS diskette to obtain a copy of the TCPIP.EXE file. See Chapter 1, "Installing the Transport," in TCP/IP Transport for DOS Installation Guide for instructions.RENDERAS="SECT2"Available Parameters and Values for the Protocol TCPIP OptionThis option has the following 
categories, 
parameters, and values, which are discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="17*"COLNAME=3 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CategoryCOLNAME=2 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM66425"LAN DriversCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87450"BIND odi_driver [number frame_type network_name]COLNAME=3 ROTATE="0" MOREROWS="0"  IDREF="FM87450"187COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM77537"IP AddressesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39115"IP_ADDRESS ip_address [network_name]IDREF="FM57133"IP_NETMASK net_mask_address [network_name]IDREF="FM93095"IP_ROUTER ip_address [network_name]COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM39115"189IDREF="FM57133"190IDREF="FM93095"191COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31944"Connection SocketsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80070"TCP_SOCKETS numberIDREF="FM46722"UDP_SOCKETS numberIDREF="FM95476"RAW_SOCKETS numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM80070"192IDREF="FM46722"193IDREF="FM95476"194COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM39326"NetBIOS SupportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM13708"NB_ADAPTER [0 | 1]IDREF="FM37979"NB_BRDCAST [0 | 1]IDREF="FM40756"NB_COMMANDS numberIDREF="FM80618"NB_DOMAIN domain_nameIDREF="FM46685"NB_SESSIONS numberCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM13708"196IDREF="FM37979"197IDREF="FM40756"197IDREF="FM80618"198IDREF="FM46685"198COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM60390"Additional SupportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM61542"NO_BOOTPIDREF="FM94924"PATH TCP_CFG [[ drive: ]path [ ; ... ]]COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM61542"199IDREF="FM94924"200PAGENUM=184 ID="BP179"RENDERAS="SECT2"PROTOCOL IDXID="w11784"BOOK="_idx" COLLECTION="nw41" TIDREF="i3607"
TCPIPSpecifies the protocol option you are making configurations for.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"protocol tcpip  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the IP address for your client workstation and distinguish your connection to the network, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  bind ne2000 2 finance-netMOREINFO="NONE"  ip_address 129.47.30.6 finance-netRENDERAS="SECT2"ID="FM66425"LAN DriversUse this parameter and value to bind the TCP/IP protocol stack to a LAN driver, which is discussed on the indicated page:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM87450"BIND odi_driver [number frame_type network_name]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87450"187PAGENUM=185 ID="BP180"The NetWare Client for DOS and MS Windows software provides ODI LAN drivers and COMn device drivers for the TCP/IP protocol stack. You can set up client workstations to use either an Ethernet connection with a SLIP/PPP serial link or a network gateway machine with two network boards.Protocol TCPIP supports one network board and LAN driver per client workstation.RENDERAS="SECT3"ID="FM87450"IDXID="w11785"BOOK="_idx" COLLECTION="nw41" TIDREF="i434"
BIND odi_driver [number frame_type network_name]Binds the TCP/IP protocol stack to a LAN driver. When TCP/IP is bound to a LAN driver, the network board or COMn device for that LAN driver is the board or device used for transmissions to and from the network. PAGENUM=186 ID="BP181"This parameter is needed only if you are running more than one ODI LAN driver to support TCP/IP.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"bind odi_driverMOREINFO="NONE" [numberMOREINFO="NONE" frame_typeMOREINFO="NONE" network_nameMOREINFO="NONE"]Replace odi_driver with a token-ring or Ethernet ODI LAN driver name, or with the SLIP_PPP driver name.Replace number with the instance of the LAN driver number.Use of this number binds TCP/IP to a particular occurrence of a network board when you have two boards with the same name. This number reflects the load sequence number of the network board (not the same as the logical board number displayed by the LAN driver when it is loaded). Using board number 0 instructs TCP/IP to bind to the first board it finds that supports both TCP/IP and the specified frame type.Replace frame_type with the frame type used for your network connection. This value is the same as the frame value for the LINK DRIVER parameter.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Replace network_name with a descriptive name for this network connection. The network name is used with the IP_ADDRESS, IP_ROUTER, and IP_NETMASK parameters to distinguish between the values for each network connection.If multiple LAN drivers are to be bound to, specify the BIND parameter multiple times, each on a different line in the NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind TCP/IP to an NE2000 LAN driver for a single network board in your client workstation connected to the FINANCE-NET network, you would add the following lines to your NET.CFG file:MOREINFO="NONE"protocol TCPIPMOREINFO="NONE"  bind ne2000 finance-netTo bind TCP/IP to an NE2000 LAN driver for both the first and the second network boards in your client workstation, you would add the following lines to your NET.CFG file:MOREINFO="NONE"Protocol TCPIPMOREINFO="NONE"  bind ne2000 1MOREINFO="NONE"  bind ne2000 2PAGENUM=187 ID="BP182"RENDERAS="SECT2"ID="FM77537"IP AddressesUse these parameters and values to specify your client workstation's IP address, the subnetwork mask, and the default network router address, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM39115"IP_ADDRESS ip_address [network_name]IDREF="FM57133"IP_NETMASK net_mask_address [network_name]IDREF="FM93095"IP_ROUTER ip_address
[network_name]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39115"189IDREF="FM57133"190IDREF="FM93095"191PAGENUM=188 ID="BP183"RENDERAS="SECT3"ID="FM39115"IP_ADDRESS ip_address [network_name]IDXID="w11786"BOOK="_idx" COLLECTION="nw41" TIDREF="i1979"
Specifies the IP address for your client workstation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ip_address ip_addressMOREINFO="NONE" [network_nameMOREINFO="NONE"]Replace ip_address with the correct address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address.Replace network_name with a descriptive name for this network connection. The network name is used with the BIND, IP_ROUTER, and IP_NETMASK parameters to distinguish between the values for each network connection. The network name is required only if you are configuring multiple ODI LAN drivers for TCP/IP.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the IP address for your client workstation and distinguish your connection to the network, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  bind ne2000 2 finance-netMOREINFO="NONE"  ip_address 129.47.30.6 finance-netMOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0PAGENUM=189 ID="BP184"RENDERAS="SECT3"ID="FM57133"IP_NETMASK net_mask_address [network_name]IDXID="w11787"BOOK="_idx" COLLECTION="nw41" TIDREF="i1980"
Specifies the default subnetwork mask if subnetworks are used.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ip_netmask net_mask_addressMOREINFO="NONE" [network_nameMOREINFO="NONE"]Replace net_mask_address with the correct subnetwork mask address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address.Replace network_name with a descriptive name for this network connection. The network_name is used with the BIND, IP_ADDRESS, and IP_ROUTER parameters to distinguish between the values for each network connection.The network name is required only if you are configuring multiple ODI LAN drivers for TCP/IP.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the IP netmask for your client workstation and distinguish your connection to the network, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  bind ne2000 2 finance-netMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0 finance-netPAGENUM=190 ID="BP185"RENDERAS="SECT3"ID="FM93095"IP_ROUTER ip_address [network_name]IDXID="w11788"BOOK="_idx" COLLECTION="nw41" TIDREF="i1981"
Specifies the default router address for all packets being sent to remote networks. All other gateways are dynamically discovered using the ICMP redirect mechanism.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ip_router ip_addressMOREINFO="NONE" [network_nameMOREINFO="NONE"]Replace ip_address with the correct address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address.Replace network_name with a descriptive name for this network connection. The network name is used with the BIND, IP_ADDRESS, and IP_NETMASK parameters to distinguish between the values for each network connection. The network name is required only if you are configuring multiple ODI LAN drivers for TCP/IP.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the IP address for your client workstation and distinguish your connection to the network, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  bind ne2000 2 finance-netMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6 finance-netMOREINFO="NONE"  ip_netmask 255.255.0.0 finance-netRENDERAS="SECT2"ID="FM31944"Connection SocketsPAGENUM=191 ID="BP186"Use these parameters and values to specify the maximum number of concurrent Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and raw socket connections that your client workstation can support, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80070"TCP_SOCKETS numberIDREF="FM46722"UDP_SOCKETS numberIDREF="FM95476"RAW_SOCKETS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80070"192IDREF="FM46722"193IDREF="FM95476"194RENDERAS="SECT3"Transmission Control Protocol (TCP) SocketsIDXID="w11789"BOOK="_idx" COLLECTION="nw41" TIDREF="i785"
Transmission Control Protocol (TCP) sockets are used to support concurrent TCP connections. If you configure multiple ODI LAN drivers for TCP/IP and anticipate using applications that make heavy concurrent use of sockets, modify the number of TCP sockets by configuring the TCP_SOCKETS parameter value to a larger number.RENDERAS="SECT3"ID="FM80070"TCP_SOCKETS numberIDXID="w11790"BOOK="_idx" COLLECTION="nw41" TIDREF="i4457"
Specifies the maximum number of concurrent TCP sockets (connections). If you are configuring multiple ODI LAN drivers for TCP/IP, set the number of TCP sockets to the total shared by all drivers.The value for your TCP_SOCKETS must be at least equal to the NB_SESSIONS value plus 1. IDREF="FM46685"See "NB_SESSIONS number" on page 198 for more information.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"tcp_sockets numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 64COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a maximum of sixteen concurrent TCP connections, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  tcp_sockets 16PAGENUM=192 ID="BP187"RENDERAS="SECT3"User Datagram Protocol (UDP) SocketsIDXID="w11791"BOOK="_idx" COLLECTION="nw41" TIDREF="i785"
User Datagram Protocol (UDP) sockets are used by the LWPCON utility and by all applications that query a name server using the domain name system (DNS). IDXID="w11792"BOOK="_idx" COLLECTION="nw41" TIDREF="i2584"
DNS name IDXID="w11793"BOOK="_idx" COLLECTION="nw41" TIDREF="i4062"
servers are the only type of name server that the IDXID="w11794"BOOK="_idx" COLLECTION="nw41" TIDREF="i4454"
TCP/IP Transport for DOS software supports. The software accesses a 
DNS name server through the information provided in the RESOLV.CFG file. See Chapter 2, "Setting Up Domain Name Systems (DNS) Support," in the TCP/IP Transport for DOS Configuration Guide for more information.Because UDP sockets are used briefly to send and receive datagrams and are then released, you need more than the default eight UDP sockets only if you make very heavy use of DNS.RENDERAS="SECT3"ID="FM46722"UDP_SOCKETS numberIDXID="w11795"BOOK="_idx" COLLECTION="nw41" TIDREF="i4627"
Specifies the maximum number concurrent UDP sockets (connections).If you are using IDXID="w11796"BOOK="_idx" COLLECTION="nw41" TIDREF="i1173"
DNS, set at least one UDP socket for each concurrently run application.If you are using IDXID="w11797"BOOK="_idx" COLLECTION="nw41" TIDREF="i2664"
NetBIOS, set at least two UDP sockets. If you are configuring multiple ODI LAN drivers for TCP/IP, set the number of UDP sockets to the total shared by all LAN drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"udp_sockets numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 32COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a maximum of sixteen concurrent UDP connections, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  udp_sockets 16PAGENUM=193 ID="BP188"RENDERAS="SECT3"Raw SocketsOne IDXID="w11798"BOOK="_idx" COLLECTION="nw41" TIDREF="i785"
raw socket is required when using the PING utility, the LWPCON utility, or other applications that have ping functions.The default NET.CFG file configured by the TCP/IP Transport for DOS installation program provides for eight TCP sockets, eight UDP sockets, and one raw socket. These default values are sufficient for most configurations.Run the TCP/IP Transport for DOS installation program provided on the CLASS=DISKTCP/IP Transport for DOS diskette to obtain a copy of the PING.EXE and LWPCON.EXE files. See Chapter 1, "Installing the Transport," in the TCP/IP Transport for DOS Installation Guide for more information.RENDERAS="SECT3"ID="FM95476"RAW_SOCKETS numberIDXID="w11799"BOOK="_idx" COLLECTION="nw41" TIDREF="i3673"
Specifies the maximum number of raw IP sockets (connections).If you are using the PING utility, the LWPCON utility, or other utilities that have ping functions, set one raw IP socket. If you are not using utilities that have ping functions, set the number of raw IP sockets to 0.PAGENUM=194 ID="BP189"If you are configuring multiple ODI LAN drivers for TCP/IP, set the number of raw sockets to the total shared by all LAN drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"raw_sockets numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To decrease memory used by IP sockets, you would place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  raw_sockets 0RENDERAS="SECT2"ID="FM39326"NetBIOS SupportUse these parameters and values to manage and configure the RFCNBIOS.EXE file, as discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM13708"NB_ADAPTER [0 | 1]IDREF="FM37979"NB_BRDCAST [0 | 1]IDREF="FM40756"NB_COMMANDS numberIDREF="FM80618"NB_DOMAIN domain_nameIDREF="FM46685"NB_SESSIONS numberCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM13708"196IDREF="FM37979"197IDREF="FM40756"197IDREF="FM80618"198IDREF="FM46685"198The RFCNBIOS.EXE program implements the NetBIOS B-node protocols as defined in RFC 1001 and 1002. (The B-node protocols use broadcast datagrams for network management and some NetBIOS datagram operations.) With this software, you can run any network application designed for the standard NetBIOS interface. Run the TCP/IP Transport for DOS installation program provided on the CLASS=DISKTCP/IP Transport for DOS diskette to obtain a copy of the RFCNBIOS.EXE file. See Chapter 1, "Installing the Transport," in the TCP/IP Transport for DOS Installation Guide for more information.PAGENUM=195 ID="BP190"All directly connected NetBIOS nodes that you plan to communicate with must use an RFC1001/1002-compliant NetBIOS program. Also, all NetBIOS implementations must be B-node configurations. Configuration for NetBIOS software support is done for the Protocol TCP/IP and Protocol RFCNBIOS options in your NET.CFG file. IDREF="FM39423"See "Protocol RFCNBIOS Option" on page 172 for information on configuring client workstations to run RFC1001/1002-compliant NetBIOS programs on the TCP/IP protocol stack.RENDERAS="SECT3"ID="FM13708"NB_ADAPTER [0 | 1]IDXID="w11800"BOOK="_idx" COLLECTION="nw41" TIDREF="i2611"
Specifies the network board to use for binding NetBIOS to the TCP/IP protocol stack.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"nb_adapter [0 | 1]Specify "0" for the first network board.Specify "1" for the second network board.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bind NetBIOS to the TCP/IP protocol stack using the second network board, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  nb_adapter 1PAGENUM=196 ID="BP191"RENDERAS="SECT3"ID="FM37979"NB_BRDCAST [0 | 1]IDXID="w11801"BOOK="_idx" COLLECTION="nw41" TIDREF="i2612"
Specifies the format of IP broadcasts used when the RFCNBIOS.EXE program sends broadcast messages.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"nb_brdcast [0 | 1]Specify "0" to set the broadcast address to use zeros for the host portions of the IP address.Therefore, a Class B network with a network address of 129.47 would have a broadcast address of 129.47.0.0.Specify "1" to set the broadcast address to use 255 for the host portions of the IP address.Therefore, a Class B network with a network address of 129.47 would have a broadcast address of 129.47.255.255.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that the format of the IP broadcasts the RFCNBIOS program sends uses zeros for the host portions of the IP address, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  nb_brdcast 0RENDERAS="SECT3"ID="FM40756"NB_COMMANDS numberIDXID="w11802"BOOK="_idx" COLLECTION="nw41" TIDREF="i2613"
Specifies the maximum number of asynchronous NetBIOS commands. Each pending NetBIOS command requires 32 bytes of memory.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"nb_commands numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 80COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set a maximum of sixteen asynchronous NetBIOS commands, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  nb_commands 16PAGENUM=197 ID="BP192"RENDERAS="SECT3"ID="FM80618"NB_DOMAIN domain_nameIDXID="w11803"BOOK="_idx" COLLECTION="nw41" TIDREF="i2614"
Specifies the name of the logical domain for a NetBIOS client workstation. All client workstations in the same logical domain must use the same value for this parameter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"nb_domain domain_nameCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify BIOSPHERE_2 as the name of your logical domain, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  nb_domain biosphere_2RENDERAS="SECT3"ID="FM46685"NB_SESSIONS numberIDXID="w11804"BOOK="_idx" COLLECTION="nw41" TIDREF="i2615"
Specifies the maximum number of concurrent NetBIOS sessions.PAGENUM=198 ID="BP193"The value for your TCP_SOCKETS must be at least one number higher the NB_SESSIONS value. IDREF="FM80070"See "TCP_SOCKETS number" on page 192 for more information.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"nb_sessions numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"4COLNAME=1 ROTATE="0" MOREROWS="0"RangeCOLNAME=2 ROTATE="0" MOREROWS="0"0 to 64COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify eight concurrent sessions, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0MOREINFO="NONE"  nb_sessions 8RENDERAS="SECT2"ID="FM60390"Additional SupportUse these parameters and values to configure your client workstation's boot process and path to client workstation configuration files, as discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM61542"NO_BOOTPIDREF="FM94924"PATH TCP_CFG [[ drive: ]path [ ; ... ]]COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM61542"199IDREF="FM94924"200RENDERAS="SECT3"ID="FM61542"NO_BOOTPIDXID="w11805"BOOK="_idx" COLLECTION="nw41" TIDREF="i2993"
Directs your client workstation to bypass any network BOOTP (a standard protocol that provides TCP/IP configuration information) server and uses Reverse Address Resolution Protocol (RARP) to identify a client workstation's IP address. PAGENUM=199 ID="BP194"If your network has a BOOTP server that is configured to supply your client workstation with its IP address, router address, and subnetwork mask, you don't need to configure this parameter in your NET.CFG file. See Chapter 2, "Using a BOOTP Server," in the TCP/IP Transport for DOS Configuration Guide for more information.If you want to bypass a BOOTP server, specify values for the IP_ADDRESS, IP_ROUTER, and IP_NETMASK parameters in your NET.CFG file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"no_bootpCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To bypass a BOOTP server, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  no_bootpMOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0RENDERAS="SECT3"ID="FM94924"PATH TCP_CFG [[ drive: ]path [ ; ... ]]IDXID="w11806"BOOK="_idx" COLLECTION="nw41" TIDREF="i3254"
Specifies the directories that contain the database configuration files HOSTS, NETWORKS, PROTOCOL, SERVICES, and RESOLV.CFG. The Syntax is the same as the DOS PATH command.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"path tcp_cfg [[drive:MOREINFO="NONE"] pathMOREINFO="NONE" [; ...]]Replace drive with the letter of the drive where the database configuration files exist.Replace path with the directory path to the location of the database configuration files.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"drive: C  path: \net\tcpCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the directory \TCPNET\TCP for the database configuration files, you could place the following lines in your NET.CFG file:MOREINFO="NONE"protocol tcpipMOREINFO="NONE"  path c:\tcpnet\tcp;%path%MOREINFO="NONE"  ip_address 129.47.6.84MOREINFO="NONE"  ip_router 144.52.6.6MOREINFO="NONE"  ip_netmask 255.255.0.0RENDERAS="SECT1"PAGENUM=200 ID="BP195"ID="FM73019"TBMI2 OptionUse this option of the NET.CFG file to modify the 
task-switching environment.RENDERAS="SECT2"Available IDXID="w11807"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
Parameters and IDXID="w11808"BOOK="_idx" COLLECTION="nw41" TIDREF="i4440"
Values for the TBMI2 OptionThis option has the following 
parameters and values, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameters and ValuesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM50869"DATA ECB COUNT numberIDREF="FM84434"ECB COUNT numberIDREF="FM24286"INT64 [on | off]IDREF="FM80454"INT7A [on | off]IDREF="FM64075"USE MAX PACKETSIDREF="FM78551"USING WINDOWS 3.0COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50869"203IDREF="FM84434"203IDREF="FM24286"204IDREF="FM80454"205IDREF="FM64075"205IDREF="FM78551"205PAGENUM=201 ID="BP196"RENDERAS="SECT2"ID="FM68639"TBMI2IDXID="w11809"BOOK="_idx" COLLECTION="nw41" TIDREF="i4440"Allows you to run applications in a task-switching mode with NetWare software.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"tbmi2  parameter_name valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure for TBMI2, you could place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  int7a offYou can also specify command line parameters for TBMI2. IDREF="FM62716"See Chapter 3, "Command Line Parameters Reference," on page 211 for more information.RENDERAS="SECT3"ID="FM50869"DATA ECB COUNT numberIDXID="w11810"BOOK="_idx" COLLECTION="nw41" TIDREF="i916"
Specifies how many data event control blocks (ECBs) are allocated for use by DOS programs needing virtualization. These ECBs apply to most IPX and SPX send-and-receive packets. If a nondata ECB request is made when none is available, a data ECB is used.Each allocated data ECB requires 628 bytes of memory; therefore, the 60 ECB default requires 37,680 bytes. The maximum allocation also depends upon available memory. The total size of all ECBs must be under 64 KB, which usually limits the data ECB count to under 255. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"data ecb count numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"60COLNAME=1 ROTATE="0" MOREROWS="0"MaximumCOLNAME=2 ROTATE="0" MOREROWS="0"89COLNAME=1 ROTATE="0" MOREROWS="0"MinimumCOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify 40 data ECBs for use by the DOS SHELL command, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  data ecb count 40PAGENUM=202 ID="BP197"RENDERAS="SECT3"ID="FM84434"ECB COUNT numberIDXID="w11811"BOOK="_idx" COLLECTION="nw41" TIDREF="i1284"
Specifies how many nondata event control blocks (ECBs) are allocated for use by DOS programs needing virtualization. These ECBs apply to most asynchronous events services. If TBMI2 runs out of nondata ECBs, data ECBs can be allocated for use with this setting. Each allocated ECB requires 52 bytes of memory; therefore, the 20 ECB default requires 1,040 bytes. The maximum allocation also depends upon available memory. The total size of all ECBs must be under 64 KB, which usually limits the ECB count to under 255. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"ecb count numberCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20COLNAME=1 ROTATE="0" MOREROWS="0"MaximumCOLNAME=2 ROTATE="0" MOREROWS="0"255COLNAME=1 ROTATE="0" MOREROWS="0"MinimumCOLNAME=2 ROTATE="0" MOREROWS="0"10COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify 40 nondata ECBs for use by the DOS SHELL command, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  ecb count 40PAGENUM=203 ID="BP198"RENDERAS="SECT3"ID="FM24286"INT64 [on | off]IDXID="w11812"BOOK="_idx" COLLECTION="nw41" TIDREF="i1891"
Allows applications to use interrupt 64h to access IPX and SPX services. IPX and SPX now use interrupt 64h to maintain compatibility with earlier versions of NetWare software. If an application's documentation requests interrupt 64h, set the value of this parameter to "off." COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"int64 [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow an application use interrupt 64h, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  int64 offRENDERAS="SECT3"ID="FM80454"INT7A [on | off]IDXID="w11813"BOOK="_idx" COLLECTION="nw41" TIDREF="i1893"
Allows applications to use interrupt 7Ah to access IPX and SPX services. IPX and SPX protocol stacks now use interrupt 7Ah to maintain compatibility with NetWare 2.0a software. If an application's documentation requests interrupt 7Ah, set the value for this parameter to "off." COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"int7a [on | off]COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"onCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow an application use interrupt 7Ah, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  int7a offPAGENUM=204 ID="BP199"RENDERAS="SECT3"ID="FM64075"USE MAX PACKETSIDXID="w11814"BOOK="_idx" COLLECTION="nw41" TIDREF="i4700"
Directs TBMI2 to use the maximum packet size as specified by the IPX MAX PACKETS parameter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"use max packetsCOLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To use the maximum number of packets specified, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  use max packetsRENDERAS="SECT3"ID="FM78551"USING WINDOWS 3.0IDXID="w11815"BOOK="_idx" COLLECTION="nw41" TIDREF="i4734"
Directs TBMI2 to use TASKID. Setting a value for this parameter directs the NetWare software to identify tasks in each DOS BOX as separate tasks.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"using windows 3.0COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To direct NetWare to separately identify tasks in each DOS box, you would place the following lines in your NET.CFG file:MOREINFO="NONE"tbmi2MOREINFO="NONE"  using windows 3.0RENDERAS="SECT1"ID="FM73159"Transport Provider IPX | UDP OptionIDXID="w11816"BOOK="_idx" COLLECTION="nw41" TIDREF="i4566"
The Desktop SNMP IDXID="w11817"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
transport providers, IDXID="w11818"BOOK="_idx" COLLECTION="nw41" TIDREF="i4300"
STPIPX.COM and IDXID="w11819"BOOK="_idx" COLLECTION="nw41" TIDREF="i4301"
STPUDP.COM, read the configuration file to discover trap targets on NetWare networks.PAGENUM=205 ID="BP200"Use this option of the IDXID="w11820"BOOK="_idx" COLLECTION="nw41" TIDREF="i2904"
NET.CFG file to specify the trap target address for your SNMP desktops. For more information, IDREF="FM35992"see "Desktop SNMP Option" on page 25.RENDERAS="SECT2"Available Parameters and Values for the Transport Provider IPX | UDP OptionThis option has the following 
parameter and value, which are discussed on the indicated pages:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Parameter and ValueCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM49868"TRAP TARGET ipxaddress | ipaddressCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM49868"208RENDERAS="SECT2"ID="FM85338"TRANSPORT PROVIDER IPX | UDPIDXID="w11821"BOOK="_idx" COLLECTION="nw41" TIDREF="i4566"
Specifies the 
Transport Provider option IPX or UDP configurations.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"transport provider ipx | udp  parameter_nameMOREINFO="NONE" valueReplace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.Select either IPX or UDP as the transport protocol used by the management station.COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set your client workstation for a management station of "ab123456:0123456789ab," you would place the following lines in your NET.CFG file:MOREINFO="NONE"transport provider ipxMOREINFO="NONE"  trap target ab123456:0123456789abPAGENUM=206 ID="BP201"RENDERAS="SECT3"ID="FM49868"TRAP TARGET ipxaddress | ipaddressIDXID="w11822"BOOK="_idx" COLLECTION="nw41" TIDREF="i4571"
Trap targets define the addresses that the SNMP manager sends SNMP traps to. To receive traps sent by Desktop SNMP, make sure your management workstation address is listed in the IPX (for IPX transport) or UDP (for UDP/IP transport) section of the NET.CFG file.If you do not configure at least one trap target, Desktop SNMP does not send traps. MOREINFO="NONE"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"SyntaxCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"trap target ipxaddressMOREINFO="NONE" | ipaddressMOREINFO="NONE" Replace ipxaddress or ipaddress with the management station address for IPX transport or for UDP/IP transport, respectively.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set your client workstation for a management station of "ab123456:0123456789ab," you would place the following lines in your NET.CFG file:MOREINFO="NONE"transport provider ipxMOREINFO="NONE"  trap target ab123456:0123456789abTo set your client workstation to use both IPX and  UDP/IP transport you could place the following lines in your NET.CFG file:MOREINFO="NONE"transport provider ipxMOREINFO="NONE"  trap target ab123456:0123456789abMOREINFO="NONE"  trap target cd654321:ba9876543210MOREINFO="NONE"transport provider udpMOREINFO="NONE"  trap target 999.88.77.66MOREINFO="NONE"  trap target 888.11.22.33LABEL="3"PAGENUM=211 ID="BP202"ID="FM62716"Command Line Parameters ReferenceRENDERAS="SECT1"OverviewThis chapter contains a listing of command line parameters for the NetWare® ClientTM for DOS and MS Windows software.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM67384"Core NetWare Client Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67384"213COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78075"DOSNP Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78075"218COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM53469"Remote Program Load (RPL) Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM53469"219COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78835"ROUTE Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78835"222COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM41774"TBMI2 and TASKID Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41774"227COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM27751"TSASMS Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27751"228RENDERAS="SECT1"IntroductionIDXID="w11823"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"The command line parameters for the NetWare Client software are used to specify nondefault value settings for NetWare Client software configuration options.IDXID="w11824"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
Command line parameters require a specific syntax format. The following example and table explain these syntax format IDXID="w11825"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
conventions. PAGENUM=212 ID="BP203"FORMAT="LINESPECIFIC"MOREINFO="NONE"PROGRAM_NAME /parameter [option] MOREINFO="NONE"<Enter> COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ConventionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PROGRAM_NAMECOLNAME=2 ROTATE="0" MOREROWS="0"Uppercase words. Type these words as shown. (However, you can use uppercase or lowercase.)COLNAME=1 ROTATE="0" MOREROWS="0"[ ]COLNAME=2 ROTATE="0" MOREROWS="0"Square brackets. The item enclosed in brackets is optional: you can use the command with or without the item.COLNAME=1 ROTATE="0" MOREROWS="0"optionCOLNAME=2 ROTATE="0" MOREROWS="0"Italicized words.  Replace them with the value that you want to use.COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Enter>COLNAME=2 ROTATE="0" MOREROWS="0"Angle brackets. Press the key whose name is enclosed in them.PAGENUM=213 ID="BP204"RENDERAS="SECT1"ID="FM67384"Core NetWare IDXID="w11826"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
Client SoftwareIDXID="w11827"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
The core NetWare Client software for the DOS and MS Windows environment are four terminate-and stay-resident (TSR) programs, listed and described in the following table.LABEL="3-1" PGWIDE=1 TOCENTRY="1" Explanation of the Core NetWare Client SoftwareCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11828"BOOK="_idx" COLLECTION="nw41" TIDREF="i1967"
IPXODI.COM  (Internetwork Packet ExchangeTM Open Data-Link InterfaceTM)COLNAME=2 ROTATE="0" MOREROWS="0"Delivers requests and replies between a client workstation and the network.Handles packet sequencing and acknowledgment for the client-server connection.Takes requests that the NetWare DOS RequesterTM software has determined are for the network, "packages" them with transmission information (such as their destination), and hands them to the LSLTM program.Supports mobile IPX client workstations. Allows client workstations to respond to the NetWare Event Service Layer (NESL) software (a DOS TSR program that provides a means by which programs running on client workstations can generate or receive event notifications).Allows IPXODI to detect changes in network connections, dynamically bind or unbind to new network boards, and autoswitch between a primary and secondary network board when problems are detected. COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11829"BOOK="_idx" COLLECTION="nw41" TIDREF="i2119"

LSL.COM  Link Support LayerTM  (LSL)COLNAME=2 ROTATE="0" MOREROWS="0"Puts the packaged requests from the IPXODI driver into the proper format for transmission on the particular physical network that the client workstation is running on.Takes replies for the client workstation from the network (via the network LAN driver), removes the network-specific information it has added, and passes the reply to IPXODI.COLNAME=1 ROTATE="0" MOREROWS="0"ODI LAN driver.COM  (example: NE2000TM)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11830"BOOK="_idx" COLLECTION="nw41" TIDREF="i3058"
Takes requests from the LSL and sends them to the network; receives replies from the network and passes them to the LSL.Is specific to the network board installed in your client workstation.COLNAME=1 ROTATE="0" MOREROWS="0"VLM.EXE  NetWare DOS RequesterCOLNAME=2 ROTATE="0" MOREROWS="0"DOS client software that provides the interface between DOS and the network. Is loaded when you run the STARTNET.BAT file. Consists of individual modules that provide various network services.Loads drivers that the NetWare DOS Requester needs in order to communicate with the network hardware.PAGENUM=214 ID="BP205"Use the IDXID="w11831"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
command line parameters discussed in the following sections in order to set nondefault settings for the core NetWare Client software.RENDERAS="SECT2"IPXODI.COMIDXID="w11832"BOOK="_idx" COLLECTION="nw41" TIDREF="i1967"
Use the following command line parameters to manage the IPXODI.COM software. COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="3*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Configuration FileCOLNAME=2 ROTATE="0" MOREROWS="0"/CCOLNAME=3 ROTATE="0" MOREROWS="0"Indicates alternate filename for configuration information./C = [path\]filenameCOLNAME=1 ROTATE="0" MOREROWS="0"Eliminate Diagnostic Responder and SPXCOLNAME=2 ROTATE="0" MOREROWS="0"/ACOLNAME=3 ROTATE="0" MOREROWS="0"Eliminates diagnostic responder and SPX, reducing memory size by 9 KB.COLNAME=1 ROTATE="0" MOREROWS="0"Eliminate Diagnostic ResponderCOLNAME=2 ROTATE="0" MOREROWS="0"/DCOLNAME=3 ROTATE="0" MOREROWS="0"Eliminates diagnostic responder, reducing memory size by 3 KB.COLNAME=1 ROTATE="0" MOREROWS="0"Force UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/FCOLNAME=3 ROTATE="0" MOREROWS="0"Forcibly unloads IPXODI.COM file from memory. Might cause system to hang.COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"Mobile IPXCOLNAME=2 ROTATE="0" MOREROWS="0"/MCOLNAME=3 ROTATE="0" MOREROWS="0"Loads diagnostic responder and SPX.Disables /D and /A values.Requires NESL.COM be loaded before loading IPXODI.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads IPXODI.COM file from memory.PAGENUM=215 ID="BP206"The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXODI [option]IDXID="w11833"BOOK="_idx" COLLECTION="nw41" TIDREF="i1967"
Following is an example of an IPXODI command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXODI /D /C=C:\NWCLIENT\NET.CFGThis command indicates the following:MARK=BULLETThe diagnostic responder portion of the code does not load.The NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory.RENDERAS="SECT2"LSL.EXEUse the following IDXID="w11834"BOOK="_idx" COLLECTION="nw41" TIDREF="i2119"
command line parameters to manage the Link Support Layer software.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Configuration FileCOLNAME=2 ROTATE="0" MOREROWS="0"/CCOLNAME=3 ROTATE="0" MOREROWS="0"Indicates alternate filename for configuration information./C = [path\]filenameCOLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads LSL.EXE file from memory.The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL [option]IDXID="w11835"BOOK="_idx" COLLECTION="nw41" TIDREF="i2119"
Following is an example of an LSL command that you could execute at a client workstation:PAGENUM=216 ID="BP207"FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL /C=C:\NWCLIENT\NET.CFGThis command indicates the following:MARK=BULLETThe NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory.RENDERAS="SECT2"ODI LAN driver.COMIDXID="w11836"BOOK="_idx" COLLECTION="nw41" TIDREF="i3058"
Use the following command line parameters to manage the LAN driver software. COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads ODI LAN driver.COM file from memory.The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"ODI_LAN_driver [option]IDXID="w11837"BOOK="_idx" COLLECTION="nw41" TIDREF="i3058"
Following is an example of an ODI LAN driver command that you could execute at a client workstation for an NE2000TM ODITM LAN driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"NE2000 /UThis command indicates the following:MARK=BULLETThe NE2000 LAN driver is unloaded from memory.PAGENUM=217 ID="BP208"RENDERAS="SECT2"VLM.EXEUse the following command line parameters to manage the NetWare DOS Requester software. COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="3*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Configuration FileCOLNAME=2 ROTATE="0" MOREROWS="0"/CCOLNAME=3 ROTATE="0" MOREROWS="0"Indicates alternate filename for configuration information./C = [path\]filenameCOLNAME=1 ROTATE="0" MOREROWS="0"Conventional MemoryCOLNAME=2 ROTATE="0" MOREROWS="0"/MCCOLNAME=3 ROTATE="0" MOREROWS="0"Uses conventional memory when loading VLM.EXE file.COLNAME=1 ROTATE="0" MOREROWS="0"DiagnosticsCOLNAME=2 ROTATE="0" MOREROWS="0"/DCOLNAME=3 ROTATE="0" MOREROWS="0"Displays VLM.EXE file diagnostics.COLNAME=1 ROTATE="0" MOREROWS="0"Expanded MemoryCOLNAME=2 ROTATE="0" MOREROWS="0"/MECOLNAME=3 ROTATE="0" MOREROWS="0"Uses expanded memory when loading VLM.EXE file.COLNAME=1 ROTATE="0" MOREROWS="0"Extended MemoryCOLNAME=2 ROTATE="0" MOREROWS="0"/MXCOLNAME=3 ROTATE="0" MOREROWS="0"Uses extended memory when loading VLM.EXE file.COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"Message Level (verbosity)COLNAME=2 ROTATE="0" MOREROWS="0"/VxCOLNAME=3 ROTATE="0" MOREROWS="0"0 = Displays copyright message and critical errors.1 = Displays warning messages.2 = Displays program load information for VLM programs.3 = Displays configuration information.4 = Displays diagnostic information.COLNAME=1 ROTATE="0" MOREROWS="0"Preferred ServerCOLNAME=2 ROTATE="0" MOREROWS="0"/PS=COLNAME=3 ROTATE="0" MOREROWS="0"Specifies the preferred sever connection.COLNAME=1 ROTATE="0" MOREROWS="0"Preferred TreeCOLNAME=2 ROTATE="0" MOREROWS="0"/PT=COLNAME=3 ROTATE="0" MOREROWS="0"Specifies the preferred tree connection.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads VLM.EXE file from memory.The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"VLM [option]
PAGENUM=218 ID="BP209"IDXID="w11838"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Following is an example of a 
VLMTM (NetWare DOS Requester) command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /D /C=C:\NWCLIENT\NET.CFG /PS=SALES /MCThis command indicates the following:MARK=BULLETDiagnostic information is displayed.The NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory.SALES is the preferred server connection.The VLM software is loaded into conventional memory.RENDERAS="SECT1"ID="FM78075"DOSNP SoftwareIDXID="w11839"BOOK="_idx" COLLECTION="nw41" TIDREF="i1201"
Use the following command line parameters for managing the DOSNP IDXID="w11840"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
 software.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads file from memory.COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"/ICOLNAME=3 ROTATE="0" MOREROWS="0"Displays version and load information.The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNP [option]IDXID="w11841"BOOK="_idx" COLLECTION="nw41" TIDREF="i1201"
Following is an example of a DOSNP command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNP /UThis command indicates the following:MARK=BULLETThe DOSNP program will be unloaded from memory.PAGENUM=219 ID="BP210"RENDERAS="SECT1"ID="FM53469"Remote IDXID="w11842"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
Program 
Load (RPL) SoftwareThis section contains descriptions of the values for the RPL BIND command line parameter that you can specify in the IDXID="w11843"BOOK="_idx" COLLECTION="nw41" TIDREF="i498"
BOOTCONF.SYS file. RENDERAS="SECT2"BIND Parameter ValuesUse the following values to control the way RPL IDXID="w11844"BOOK="_idx" COLLECTION="nw41" TIDREF="i428"
binds to specific LAN driversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="5*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ValueCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11845"BOOK="_idx" COLLECTION="nw41" TIDREF="i75"
ACKCOLNAME=3 ROTATE="0" MOREROWS="0"Configures the RPL Remote Boot PROM module to acknowledge FILE.DATA.RESPONSE frames sent by the RPL.COM or RPL.NLM file. Allows you to set the pace that your client workstation receives these frames at.By default, the RPL.COM or RPL.NLM file sends FILE.DATA.RESPONSE frames in a burst mode. COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11846"BOOK="_idx" COLLECTION="nw41" TIDREF="i1608"
GNSCOLNAME=3 ROTATE="0" MOREROWS="0"Sets up your client workstation to do a Get Nearest Server request when the appropriate bootstrap program is downloaded. Normally, the RPL.COM or RPL.NLM file fills in the bootstrap program with the Personal NetWare or NetWare server information, so that it does not need to do a Get Nearest Server request. Using this value might cause the client workstation to find a server other than the one where the RPL.COM or RPL.NLM file is located.COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11847"BOOK="_idx" COLLECTION="nw41" TIDREF="i2955"
NODEFAULTCOLNAME=3 ROTATE="0" MOREROWS="0"Informs the RPL.COM or RPL.NLM file to not respond to a find frame unless the node address of the client workstation is found in the BOOTCONF.SYS file. For security reasons, the client workstation does not boot until the network supervisor inserts the node address and associated disk image filename into the BOOTCONF.SYS file used when booting the client workstation.COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11848"BOOK="_idx" COLLECTION="nw41" TIDREF="i3582"
PROTECTCOLNAME=3 ROTATE="0" MOREROWS="0"Informs the RPL.COM or RPL.NLM files to configure the bootstrap program to protect the memory it occupies. Using this value reduces the amount of memory that the client workstation has available for DOS by about 12 KB. We recommend that you use this value only when memory conflicts occur. COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11849"BOOK="_idx" COLLECTION="nw41" TIDREF="i3784"
REP string1 | string2COLNAME=3 ROTATE="0" MOREROWS="0"Dynamically reconfigures a disk image file during the RPL process. There are four rules for using REP:MARK=BULLETThe search is done in uppercase ASCII text.Use the | (ASCII 7Ch) delimiter to delimit the string values.All occurrences of string1 are replaced with string2 in the disk image file.String2 must be equal to or shorter than string1.If string2 is shorter than string1, the disk image file is padded with ASCII Blanks when the substitution is made.RPL parses the node address line of the BOOTCONF.SYS file looking for these strings. If an entry is found but does not match one of the strings, REP assumes it to be a disk image filename.Therefore, you should not have a disk image file named the same as any of these keywords.An example of a line used in the BOOTCONF.SYS file using REP is as follows:MOREINFO="NONE"0x*1234 = NET$DOS.SY REP NODE ADDRESS ^^^^^ NODE ADDRESS 67890The example shows that the string MOREINFO="NONE"NODE ADDRESS ^^^^^ will be replaced with MOREINFO="NONE"NODE ADDRESS 67890 wherever it occurs in the disk image file.PAGENUM=221 ID="BP211"RENDERAS="SECT2"BIND IDXID="w11850"BOOK="_idx" COLLECTION="nw41" TIDREF="i3159"
Parameter Override ValuesWhen the 
RPL software IDXID="w11851"BOOK="_idx" COLLECTION="nw41" TIDREF="i428"
parses the BOOTCONF.SYS file, it allows value settings that override the BIND parameter specific to a particular client workstation that is being booted.PAGENUM=222 ID="BP212"Use the following values to modify the way that RPL binds to a specific LAN drivers. The following values are allowed on a per-node basis. They override the BIND parameter values:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ValueCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11852"BOOK="_idx" COLLECTION="nw41" TIDREF="i2944"
NOACKCOLNAME=3 ROTATE="0" MOREROWS="0"Overrides the ACK value for BIND. The ACK value configures the RPL Remote Boot PROM module to acknowledge FILE.DATA.RESPONSE frames sent by RPL. The NOACK parameter allows the adapter to respond in a nonburst mode.COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11853"BOOK="_idx" COLLECTION="nw41" TIDREF="i2958"
NOGNSCOLNAME=3 ROTATE="0" MOREROWS="0"Overrides the GNS value for BIND. The GNS value specifies that you want the client workstation to issue a Get Nearest Server request when the appropriate bootstrap program gets downloaded. COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11854"BOOK="_idx" COLLECTION="nw41" TIDREF="i2976"
NOPROTECTCOLNAME=3 ROTATE="0" MOREROWS="0"Overrides the PROTECT value for BIND. The PROTECT value notifies RPL to configure the bootstrap program so that it will protect itself in the client workstation's memory.COLNAME=1 ROTATE="0" MOREROWS="0"BindCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11855"BOOK="_idx" COLLECTION="nw41" TIDREF="i2989"
NOTROCOLNAME=3 ROTATE="0" MOREROWS="0"Overrides the TRO value for BIND. The IDXID="w11856"BOOK="_idx" COLLECTION="nw41" TIDREF="i4576"
TRO value specifies that you want the bootstrap program to do a This Ring Only count of three (3) on all Broadcast frames.RENDERAS="SECT1"ID="FM78835"ROUTE 
SoftwareMost of the paramater settings have default values that should work with simple configurations for IBM bridges. If you have installed parallel IBM bridges, you can use 
ROUTE software (ROUTE.COM file) to change some of the parameters to reduce traffic on some of the paths.PAGENUM=223 ID="BP213"You can use any of the following IDXID="w11857"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
command line IDXID="w11858"BOOK="_idx" COLLECTION="nw41" TIDREF="i1744"
parameters with the ROUTE software.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BoardCOLNAME=2 ROTATE="0" MOREROWS="0"BOARD = number COLNAME=3 ROTATE="0" MOREROWS="0"Specifies board number for network board.MARK=BULLETIf this parameter is not specified when ROUTE.COM is loaded, the default of 1 is used.If you have loaded more than IDXID="w11859"BOOK="_idx" COLLECTION="nw41" TIDREF="i1232"
one IDXID="w11860"BOOK="_idx" COLLECTION="nw41" TIDREF="i1744"
LAN driver in the client workstation, the board number is determined by the order in which the LAN drivers are loaded (the first board is 1). See your STARTNET.BAT file for the order you specified.    Load ROUTE.COM for each frame type enabled by the token-ring LAN driver. COLNAME=1 ROTATE="0" MOREROWS="0"ClearCOLNAME=2 ROTATE="0" MOREROWS="0"CLEARCOLNAME=3 ROTATE="0" MOREROWS="0"Clears source routing table and forces dynamic rebuilding of table by sending default frame type to each workstation in network.Use this parameter when IBM bridge on network has gone down and alternate route is available.COLNAME=1 ROTATE="0" MOREROWS="0"DEFCOLNAME=2 ROTATE="0" MOREROWS="0"DEFCOLNAME=3 ROTATE="0" MOREROWS="0"Prevents frames that have unknown (default) destination addresses from being sent across single-route IBM bridges. MARK=BULLETIf this parameter is specified, these frame types are forwarded as All Routes Broadcast frames.If this parameter is not specified when ROUTE.COM is loaded, all frame types that have addresses not in the client workstation's source routing table are forwarded as Single Route Broadcast frames.If ROUTE.COM has already been loaded with DEF parameter, reloading ROUTE.COM with this parameter broadcasts all subsequent Single Route Broadcast frames as All Routes Broadcast frames. COLNAME=1 ROTATE="0" MOREROWS="0"GBRCOLNAME=2 ROTATE="0" MOREROWS="0"GBRCOLNAME=3 ROTATE="0" MOREROWS="0"Specifies that all General Broadcast frames are to be sent as All Routes Broadcast frames.MARK=BULLETIf this parameter is not specified when ROUTE.COM is loaded, all General Broadcast frames are broadcast as Single Route Broadcast frames.If ROUTE.COM has already been loaded with the GBR parameter, reloading ROUTE.COM with this parameter broadcasts all subsequent General Broadcast frames as All Routes Broadcast frames. COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=OPTION MOREINFO="NONE"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help or usage information. COLNAME=1 ROTATE="0" MOREROWS="0"MBRCOLNAME=2 ROTATE="0" MOREROWS="0"MBRCOLNAME=3 ROTATE="0" MOREROWS="0"Specifies that all Multicast Broadcast frames are to be sent as All Routes Broadcast frames.MARK=BULLETIf this parameter is not specified when the ROUTE.COM file is loaded, all Multicast Broadcast frames are broadcast as Single Route Broadcast frames.If ROUTE.COM has already been loaded with the MBR parameter, reloading ROUTE.COM with this parameter broadcasts all subsequent Multicast Broadcast frames as All Routes Broadcast frames.COLNAME=1 ROTATE="0" MOREROWS="0"NodesCOLNAME=2 ROTATE="0" MOREROWS="0"NODE=numberCOLNAME=3 ROTATE="0" MOREROWS="0"Specifies number of table entries in source routing table.MARK=BULLETYou must enter this parameter the first time ROUTE.COM is loaded.The parameter can't be changed by reloading ROUTE.COM.Replacenumber with a value from 8 through 255. Default is 16.If this parameter is not specified when ROUTE.COM is loaded, the default is assumed.COLNAME=1 ROTATE="0" MOREROWS="0"RemoveCOLNAME=2 ROTATE="0" MOREROWS="0"REMOVE=numberCOLNAME=3 ROTATE="0" MOREROWS="0"Removes node address from client workstation's source routing table.MARK=BULLETUse this parameter when a bridge has gone down.Removing client workstation from source routing table forces other client workstations to determine alternate path.Replace number with 12-digit (6-byte) hexadecimal number.    If fewer than 9 digits are entered, the ROUTE.COM file prefixes address with 4000h. For example, REMOVE=2 is interpreted as REMOVE=400000000002. COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/U COLNAME=3 ROTATE="0" MOREROWS="0"Unloads ROUTE.COM. PAGENUM=226 ID="BP214"The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE [option]IDXID="w11861"BOOK="_idx" COLLECTION="nw41" TIDREF="i1744"
Following is an example of a ROUTE command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE BOARD=3, DEF, GBR, MBRThis command indicates the following:MARK=BULLETPackets are sent through logical board 3 All frames that are not addressed in the client workstation's source routing table are sent as All Routes BroadcastGeneral Broadcast frames are sent as All Routes BroadcastMulticast Broadcast frames are sent as All Routes BroadcastBecause the NODES parameter is not specified, the default of 16 is assumedPAGENUM=227 ID="BP215"For more information on using source routing, see the IBM Token-Ring Network Architecture Reference.RENDERAS="SECT1"ID="FM41774"TBMI2IDXID="w11862"BOOK="_idx" COLLECTION="nw41" TIDREF="i4441"
 and TASKID SoftwareUse the following IDXID="w11863"BOOK="_idx" COLLECTION="nw41" TIDREF="i4432"
command line parameters for managing the IDXID="w11864"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
TMBI2 and IDXID="w11865"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
TASKID softwareCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Configuration FileCOLNAME=2 ROTATE="0" MOREROWS="0"/CCOLNAME=3 ROTATE="0" MOREROWS="0"Indicates alternate filename for configuration information./C = [path\]filenameCOLNAME=1 ROTATE="0" MOREROWS="0"DiagnosticsCOLNAME=2 ROTATE="0" MOREROWS="0"/DCOLNAME=3 ROTATE="0" MOREROWS="0"Displays TBMI2 or TASKID file diagnostics.COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads file from memory.COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"/ICOLNAME=3 ROTATE="0" MOREROWS="0"Displays version and load information.The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"TBMI2 [option]FORMAT="LINESPECIFIC"MOREINFO="NONE"TASKID [option]IDXID="w11866"BOOK="_idx" COLLECTION="nw41" TIDREF="i4441"
Following is an example of a TBMI2 command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"TBMI2 /D /C=C:\NWCLIENT\NET.CFGThis command indicates the following:MARK=BULLETThe diagnostic information is displayed.The NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory.PAGENUM=228 ID="BP216"RENDERAS="SECT1"ID="FM27751"TSASMSIDXID="w11867"BOOK="_idx" COLLECTION="nw41" TIDREF="i4598"
 SoftwareUse the following command line parameters for managing the IDXID="w11868"BOOK="_idx" COLLECTION="nw41" TIDREF="i686"
TSASMS software.COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"OptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BuffersCOLNAME=2 ROTATE="0" MOREROWS="0"/B=nCOLNAME=3 ROTATE="0" MOREROWS="0"Sets TSA 1KB buffers (n =1 through 30). The default is 1. Increasing the number increases throughput speed, but requires more RAM on client workstation. COLNAME=1 ROTATE="0" MOREROWS="0"DriveCOLNAME=2 ROTATE="0" MOREROWS="0"/D=xCOLNAME=3 ROTATE="0" MOREROWS="0"Indicates DOS drives where data that you want to back up resides or drives that you want to restore data to. Replace x with drive letters. Don't type colon after drive letters. For example:/D = CE    where C stands for drive C: and E stands for drive E:.COLNAME=1 ROTATE="0" MOREROWS="0"HelpCOLNAME=2 ROTATE="0" MOREROWS="0"/?COLNAME=3 ROTATE="0" MOREROWS="0"Displays help screen.COLNAME=1 ROTATE="0" MOREROWS="0"NameCOLNAME=2 ROTATE="0" MOREROWS="0"/N=client nameCOLNAME=3 ROTATE="0" MOREROWS="0"Sets client workstation unique name. Maximum is 10 characters.This option is necessary only if NetWare Directory Services software for NetWare 4TM networks has been initialized (or reinitialized) on a server.COLNAME=1 ROTATE="0" MOREROWS="0"PasswordCOLNAME=2 ROTATE="0" MOREROWS="0"/P=passwordCOLNAME=3 ROTATE="0" MOREROWS="0"Sets password for client workstation. If you use this option, anyone doing a backup must know the password. The Trust option can be used instead.COLNAME=1 ROTATE="0" MOREROWS="0"RemoveCOLNAME=2 ROTATE="0" MOREROWS="0"/R=server name client nameCOLNAME=3 ROTATE="0" MOREROWS="0"Removes client workstation address from server bindery or NetWare Directory Services.COLNAME=1 ROTATE="0" MOREROWS="0"ServerCOLNAME=2 ROTATE="0" MOREROWS="0"/SE=server nameCOLNAME=3 ROTATE="0" MOREROWS="0"Specifies name of server you want this client workstation to connect to for SMS management.COLNAME=1 ROTATE="0" MOREROWS="0"StackCOLNAME=2 ROTATE="0" MOREROWS="0"/ST=nCOLNAME=3 ROTATE="0" MOREROWS="0"Specifies stack size represented as a decimal (512 through 4096 bytes). Default is 2048 bytes.Do not change this number unless RAM is extremely limited or you receive "Stack Overflow" messages.COLNAME=1 ROTATE="0" MOREROWS="0"TrustCOLNAME=2 ROTATE="0" MOREROWS="0"/TCOLNAME=3 ROTATE="0" MOREROWS="0"If you use this option, anyone doing a backup must have ADMIN- or SUPERVISOR-equivalent rights on the server. This option can be used instead of Password option.COLNAME=1 ROTATE="0" MOREROWS="0"UnloadCOLNAME=2 ROTATE="0" MOREROWS="0"/UCOLNAME=3 ROTATE="0" MOREROWS="0"Unloads TSASMS from client workstation memory.PAGENUM=229 ID="BP217"The syntax for using these parameters is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS [option]IDXID="w11869"BOOK="_idx" COLLECTION="nw41" TIDREF="i4598"
Following is an example of a TSASMS command that you could execute at a client workstation:FORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS /SE=SALES /T /D=C /B=30 /N=TSCLNT332This command indicates the following:MARK=BULLETTSASMS is the .COM filename.SALES is the server name.The Trust option is set.The drive is set to C:. There are 30 1KB TSA buffers.PAGENUM=230 ID="BP218"TSCLNT332 is the client workstation name.LABEL="4"PAGENUM=231 ID="BP219"ID="FM27972"System MessagesA 
system 
message IDXID="w11870"BOOK="_idx" COLLECTION="nw41" TIDREF="i4386"
points to a software or hardware error that doesn't allow further processing. An explanation of the nature of the message and a recommended course of action follow each message. AUTO-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.AUTO-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.AUTO-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first. PAGENUM=232 ID="BP220"Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.AUTO-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.AUTO-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.AUTO-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.BIND-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.PAGENUM=233 ID="BP221"Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.BIND-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first. Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.BIND-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.BIND-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=234 ID="BP222"BIND-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.BIND-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.CONN-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.CONN-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first. Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.PAGENUM=235 ID="BP223"CONN-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.CONN-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.CONN-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.CONN-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.PAGENUM=236 ID="BP224"Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.CONN-1.00-50: DOS version is not 3.1 or later. The NetWare Requester for DOS cannot be loaded. Reboot your computer with DOS 3.1 or later; then load the NetWare Requester for DOS files.Explanation: The NetWare® DOS RequesterTM software requires DOS 3.1 or later in order to operate. Because the current DOS version is not 3.1 or later, the NetWare DOS Requester cannot be loaded.Action: Upgrade the DOS version on your machine to 3.1 or later.CONN-1.00-51: An older version of the shell is loaded. The NetWare Requester for DOS cannot be loaded. Unload the shell; then load the NetWare Requester for DOS files.Explanation: The NetWare® DOS RequesterTM software cannot be loaded with the NetWare shell. The NetWare shell has been loaded in your machine. For NetWare shell compatibility.Action: Type "NETX /U" to unload the NetWare shell. If the version of the NetWare shell in use does not support the /U parameter, reboot the machine without loading the NetWare shell.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.CONN-1.00-52: The NetWare DOS Named Pipes Extender is currently loaded. The NetWare Requester for DOS cannot be loaded. Unload the NetWare DOS Named Pipes Extender; then load the NetWare Requester for DOS files.Explanation: The NetWare® DOS RequesterTM software cannot be loaded after the NetWare DOS Named Pipes Extender. To use both the NetWare DOS Requester and NetWare DOS Named Pipes Extender, load the NetWare DOS Requester first.Action: Type "DOSNP /U" to unload the DOS Named Pipes Extender; then load the NetWare DOS Requester before reloading the DOS Named Pipes Extender.  IDREF="FM13477"See "Named Pipes Options" on page 86 for more information about Named Pipes parameters in the NET.CFG file.PAGENUM=237 ID="BP225"DOSCLINST-1.0-1: <Filename> could not be installed.Explanation: The indicated file could not be installed on the destination drive because either the file was not found on the master diskettes or the INSTALL utility was unable to write to the INSTALL directory.Action: Make sure that the file is on the master diskettes. Also make sure that the destination drive is not write-protected or has some other condition that would prevent the indicated file from being copied.DOSCLINST-1.0-2: This program requires more disk space. Installation could not be completed.Explanation: Adequate disk space is not available on the destination drive. More space must be available for the installation to be completed.Action: Delete unnecessary files from the hard disk.DOSCLINST-1.0-3: The INSTALL.OVL file could not be found.Explanation: The INSTALL.OVL file could not be found. This file is an integral piece of the INSTALL utility; it must be in the same directory as the INSTALL.EXE file.Action: Make sure that INSTALL.OVL is in the same directory as the INSTALL.EXE file; then run INSTALL again.DOSCLINST-1.0-4: A read error occurred while the program was reading INSTALL.OVL.Explanation: The file INSTALL.OVL has been corrupted. The INSTALL utility requires INSTALL.OVL for successful installation.Action: Copy INSTALL.OVL from the master diskettes to the same directory as the INSTALL.EXE file; then run INSTALL again.FIO-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.PAGENUM=238 ID="BP226"FIO-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.FIO-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.FIO-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.FIO-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.PAGENUM=239 ID="BP227"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.FIO-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-60: Too much cache is configured. The FIO.VLM file will reduce the cache blocks by <number> blocks and load successfully. Check the CACHE BUFFERS and BUFFER SIZE parameters in the NET.CFG file; then load the FIO.VLM file.Explanation: The amount of cache available in DOS is limited by conventional memory. Neither of the parameters determining the amount of memory to be used, CACHE BUFFERS nor BUFFER SIZE, can be configured to use more than 64 KB of memory. Action: Reduce the CACHE BUFFERS or BUFFER SIZE parameter in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-61: The IPX interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI v2.00 or later to use packet burst or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the use of the Packet BurstTM protocol.  Packet Burst, which is a part of the FIO.VLM file, requires IPXODI.COM version 2.00 or later to function properly. No IPXTM interface was loaded in this machine.Action: If you want Packet Burst, make sure that IPXODI.COM version 2.00 or later is loaded before the NetWare DOS Requester. PAGENUM=240 ID="BP228"If you do not want Packet Burst, add MOREINFO="NONE"PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file.  See IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-62: The LSL interface is not loaded. The FIO.VLM file will load successfully without packet burst support. Load the LSL module or add PB BUFFERS=0 to the NET.CFG file; then load FIO.VLM.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the use of the Packet BurstTM protocol.  Packet Burst, which is a part of the FIO.VLM file, requires the LSL.COM file to be loaded to function properly.Action: If you want Packet Burst, make sure that the LSL.COM file is loaded before the NetWare DOS Requester.  If you do not want Packet Burst, add MOREINFO="NONE"PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-63: The IPX socket for packet burst could not be opened. The FIO.VLM file will load successfully without packet burst support. configure the IPXODI.COM file for enough sockets in the NET.CFG file or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the use of the Packet BurstTM protocol.  Packet Burst, which is a part of the FIO.VLM file, requires an IPXTM socket to function properly. The request to open a socket failed, indicating that not enough IPX sockets are available.Action: If you want Packet Burst, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the NetWare DOS Requester.  If you do not want Packet Burst, add MOREINFO="NONE"PB BUFFERS=0PAGENUM=241 ID="BP229" to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-64: The IPX interface is not version 2.00 or later. The FIO.VLM file will load successfully without packet burst support. Load the IPXODI.COM file version 2.00 or later or add PB BUFFERS=0 to the NET.CFG file; then load the FIO.VLM file.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the use of the Packet BurstTM protocol.  Packet Burst, which is a part of the FIO.VLM file, requires IPXODI.COM version 2.00 or later to function properly. No IPXTM interface version 2.00 or later was loaded in this machine.Action: If you want Packet Burst, make sure that IPXODI.COM version 2.00 or late is loaded before the NetWare DOS Requester. If you do not want Packet Burst, add MOREINFO="NONE"PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.FIO-1.00-65: The NetWare DOS Requester is being loaded in a MS Windows DOS box. The FIO.VLM file will load successfully without packet burst support.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the use of the Packet BurstTM protocol.  Packet Burst, which is a part of the FIO.VLM file, cannot function when loaded in an MS Windows DOS box.Action: You can use Packet Burst if it is loaded before starting MS Windows. To do this, exit MS Windows and load the VLMTM files; then restart MS Windows.GENERAL-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.PAGENUM=242 ID="BP230"GENERAL-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.GENERAL-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.GENERAL-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.GENERAL-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.PAGENUM=243 ID="BP231"Action: No action is required at this point. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.GENERAL-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.IPXNCP-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.IPXNCP-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.IPXNCP-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3PAGENUM=244 ID="BP232">.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.IPXNCP-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.IPXNCP-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.IPXNCP-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.IPXNCP-1.00-53: The IPX interface is not loaded. The IPXNCP.VLM file cannot be loaded. Load the IPXODI.COM file first and then try loading the IPXNCP.VLM file.Explanation: An attempt was made to load the IPXNCP.VLM file without having previously loaded the IPXTM interface.PAGENUM=245 ID="BP233"Action: Load the IPXODI.COM file before attempting to load IPXNCP.VLM.IPXNCP-1.00-54: The IPX sockets could not be opened. The IPXNCP.VLM file cannot be loaded. Configure the IPXODI.COM file for enough sockets in the NET.CFG file and then try to load the IPXNCP.VLM file.Explanation: The IPXNCP.VLM file failed to open the IPXTM sockets needed in order to run. The IPXNCP.VLM file requires that four or more IPX sockets be available to run.Action: Increase the number of IPX sockets available by using the IPX SOCKETS= parameter in the NET.CFG file; then reload the IPXODI.COM and IPXNCP.VLM files.IPXNCP-1.00-55: The IPX interface does not support checksums. The IPXNCP.VLM file will load successfully without using checksums. Make sure the installed IPXODI. COM is version 2.01 or later and that it is not bound to a board configured to use the ETHERNET_802.3 frame format.Explanation: The IPXNCP.VLM file loads without supporting checksums. For checksum to be supported in IPXNCP.VLM, the loaded IPXODI.COM file must support checksums.  Either the loaded version of the IPXODI.COM file does not have checksum support or the protocol bound to the IPXTM software does not support checksums. Action: No action required at this point. However, to avoid receiving this message the next time the IPXNCP.VLM file is loaded, either load the IPXODI.COM file with checksum support enabled or add MOREINFO="NONE"CHECKSUM=OFF to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.IPXNCP-1.00-56: The IPX socket for large internet packets could not be opened. The IPXNCP.VLM file will load successfully without using large internet packets. Configure the IPXODI.COM file for enough sockets in the NET.CFG file or add LARGE INTERNET PACKETS=OFF to the NET.CFG file; then load the IPXNCP.VLM file.Explanation: This message is only a warning. The NetWare®PAGENUM=246 ID="BP234" DOS RequesterTM software functions properly without the use of large internet packets. The large internet packet protocol, which is a part of the IPXNCP.VLM module, requires an IPX socket to function properly.  The request to open a socket failed, indicating that not enough IPX sockets are available.Action: If you want large internet packets, make sure that the IPX interface is configured for enough sockets in the NET.CFG file before loading the NetWare DOS Requester.  If you do not want large internet packets, add MOREINFO="NONE"LARGE INTERNET PACKETS=OFF to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.NDS-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.NDS-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.NDS-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3PAGENUM=247 ID="BP235">.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.NDS-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NDS-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NDS-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.NETX-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.PAGENUM=248 ID="BP236"Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.NETX-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first. Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.NETX-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded before <module3>.VLM can run effectively.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.NETX-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=249 ID="BP237"NETX-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NETX-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.NETX-1.00-57: DOS is only configured for <number> drives, NETX.VLM requires 26 drives for full functionality. The NETX.VLM file will load with partial support. Add LASTDRIVE=Z to the CONFIG.SYS file and reboot the workstation; then load the NETX.VLM file.Explanation: This message is only a warning. However, if you want full compatibility with the NetWare® shell, you must set the DOS LASTDRIVE parameter in the CONFIG.SYS file to Z. Otherwise, problems occur when mapping drives, etc.Action: Set MOREINFO="NONE"LASTDRIVE=Z in the CONFIG.SYS file; then reboot the client workstation before loading the NetWare DOS RequesterTM software.NETX-1.00-58: The PRINT.VLM file has not been loaded. The NETX.VLM file will load successfully without print services. To enable printing services, load the PRINT.VLM file before loading the NETX.VLM file.Explanation: This message is only a warning. For full NetWare® shell compatibility, the PRINT.VLM file must be loaded.Action: If you want print functionality, load the PRINT.VLM file before loading the NETX.VLM file.PAGENUM=250 ID="BP238"NMR-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.NMR-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.NMR-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.NMR-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.PAGENUM=251 ID="BP239"NMR-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NMR-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.NWDRV-3.00-00: The NetWare VLM is not loaded or is not configured correctly. All network functions will be disabled. Reconfigure the VLM and restart MS Windows.Explanation: Without the NetWare® DOS RequesterTM (VLM) software, the client workstation cannot communicate with NetWare servers.  The NetWare MS Windows driver (NETWARE.DRV) depends on the VLMTM software in order to provide network support for MS Windows.Action: Exit MS Windows. Go to the directory where the VLM.EXE file is located and type "VLM". Then restart MS Windows.NWDRV-3.00-10: The VNETWARE.386 file has not been loaded. All network functions will be disabled. To use NetWare, install VNETWARE.386 and restart MS Windows.Explanation: The NetWare® MS Windows driver (NETWARE.DRV) depends on the VNETWARE.386 file to run MS Windows in enhanced mode.PAGENUM=252 ID="BP240"Action: Exit MS Windows. Copy the VNETWARE.386 file to the MS Windows SYSTEM (for example, C:\WINDOWS\SYSTEM). VNETWARE.386 should be on the CLASS=DISKNetWare CLASS=DISKClient For DOS and MS Windows Disk 3 diskette.  Also make sure that the "[386Enh]" section of the SYSTEM.INI file has the following line:  MOREINFO="NONE"NETWORK=*VNETBIOS, VNETWARE.386, VIPX.386  Then restart MS Windows. NWDRV-3.00-50: The temporary drive could not be mapped. Contact the network supervisor.Explanation: The NetWare® MS Windows driver (NETWARE.DRV) allocates temporary drives on the server to perform some functions.Action: Contact the network supervisor to make sure that NetWare is running and the server is operating correctly.NWP-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.NWP-1.00-5: <module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.NWP-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2PAGENUM=253 ID="BP241">.VLM file be loaded.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.NWP-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NWP-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.NWP-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.PAGENUM=254 ID="BP242"NWP-1.00-59: The SECURITY.VLM file has not been loaded. The NWP.VLM file will load successfully without NCP signature support. Load the SECURITY.VLM file before loading the NWP.VLM file or add SIGNATURE LEVEL=0 to the NET.CFG file; then load NWP.VLM.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without NetWare Core ProtocolTM (NCP) authentication.  For NCPTM authentication to operate properly, the SECURITY.VLM file must be loaded before the NWP.VLM file.  Either NWP.VLM is being loaded before SECURITY.VLM or SECURITY.VLM did not load successfully.Action: If you want NCP authentication, make sure that SECURITY.VLM is configured to load before NWP.VLM and that it loads successfully before attempting to load NWP.VLM. If you do not want NCP authentication, add MOREINFO="NONE"SIGNATURE LEVEL=0 to the NetWare DOS Requester section of the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.REDIR-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.REDIR-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.PAGENUM=255 ID="BP243"REDIR-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.REDIR-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.REDIR-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.REDIR-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.PAGENUM=256 ID="BP244"Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.RSA-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.RSA-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.RSA-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.RSA-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.PAGENUM=257 ID="BP245"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.RSA-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.RSA-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.SECURITY-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.SECURITY-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1PAGENUM=258 ID="BP246">.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.SECURITY-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.SECURITY-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.SECURITY-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time VLM.EXE is loaded, delete or correct the line specified by the error message.PAGENUM=259 ID="BP247"SECURITY-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.SECURITY-1.00-67: The SECURITY.VLM file must be loaded before any other NetWare Protocol Module. The SECURITY.VLM file will not be loaded. Load the SECURITY.VLM file before loading any NetWare Protocol Modules.Explanation: This message is only a warning. The NetWare® DOS RequesterTM software functions properly without the NetWare Core ProtocolTM (NCP) authentication.  The SECURITY.VLM file must be loaded before any NetWare protocol modules (BIND.VLM or NDS.VLM) to function properly.Action: If you want NCPTM authentication, load the SECURITY.VLM after TRAN.VLM and before any NetWare protocol module (BIND.VLM or NDS.VLM); then set the SIGNATURE LEVEL= parameter in the NET.CFG file.  If you do not want NCP authentication, set MOREINFO="NONE"SIGNATURE LEVEL=0 in the NetWare DOS Requester section of NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.TRAN-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.PAGENUM=260 ID="BP248"TRAN-1.00-5: <Module1>.VLM is not loaded. The <module2>.VLM file cannot be loaded before <module1>.VLM. Load the <module1>.VLM file first then try to load the <module2>.VLM file.Explanation: The <module2>.VLM file requires that the <module1>.VLM file be loaded first.  Either the current configuration has <module1>.VLM and <module2>.VLM loading out of order, or <module1>.VLM did not load successfully.Action: Make sure that <module1>.VLM is configured to load before <module2>.VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file.TRAN-1.00-7: In order to load the <module3>.VLM, one of the following VLMs must be loaded: <module1>.VLM, <module2>.VLM.Explanation: The <module3>.VLM file requires that the <module1>.VLM or <module2>.VLM file be loaded first.  Either the current configuration has <module3>.VLM loading before <module1>.VLM or <module2>.VLM, or <module1>.VLM or <module2>.VLM did not load successfully.Action: Make sure that <module1>.VLM or <module2>.VLM loads successfully before <module3>.VLM.TRAN-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.TRAN-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.PAGENUM=261 ID="BP249"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.TRAN-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.VLM-1.00-1: The message file <name> is invalid. The program cannot be loaded.Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version.Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS RequesterTM software uses the default messages that are bound to the binary files.VLM-1.00-8: The VLM.EXE file is already loaded. VLM.EXE cannot be reloaded. If you want to load VLM.EXE with a different configuration, unload VLM.EXE first with the /U parameter and then try loading the VLM.EXE file.Explanation: The VLM.EXE file has already been loaded into memory. There cannot be two copies of the VLM.EXE file loaded in memory at one time.Action: If the VLM.EXE file is being reloaded in an attempt to reconfigure the VLMTM program already loaded, you must first unload VLM.EXE using the /U parameter; then reload VLM.EXE.VLM-1.00-9: The VLM.EXE file is testing the VLMs.Explanation: This message is used to show the progress the VLM.EXE file is making in configuring the VLMTM programs to be loaded.  Because this process can take a few seconds, the progress is displayed using a period (.) to indicate each VLM being tested.Action: No action is required; this is simply an information message.PAGENUM=262 ID="BP250"VLM-1.00-10: The conventional memory block for the EMS stack cannot be resized. The VLM.EXE file cannot be loaded. DOS memory is probably corrupt. Reboot your computer and then try to load the VLM.EXE again.Explanation: This error indicates that the DOS memory chain has been corrupted.Action: It is unsafe to continue operating the computer. The best solution is to reboot the computer; then try to load the VLM.EXE file.VLM-1.00-11: There is insufficient memory to load the VLMs. The VLM.EXE file cannot be loaded. Reconfigure the VLMs to be loaded in the NET.CFG file and then try to load the VLM.EXE file.Explanation: The VLM.EXE file can use expanded memory (EMS), extended memory (XMS), or conventional memory.  The VLM.EXE file has determined that there is not enough of any one of these types of memory to support loading the VLMTM files.Action: Check the amount of all memory available. Some memory managers provide dynamic memory pools by converting extended memory to expanded memory or vice versa. Other memory managers require you to configure the amount and type of memory you want.  In either case, do one of the following:MARK=BULLETMake sure there is enough memory of any one type to support the VLM files.Reduce the number of VLM files to be loaded, either by using the EXCLUDE= parameter in the NET.CFG file or by renaming the files so the VLM.EXE file does not recognize the .VLM file that you do not want loaded.VLM-1.00-15: An invalid command line parameter was specified.Explanation: The VLM.EXE file was loaded with an invalid command line parameter.Action: Run VLM.EXE with the /? parameter (for example, type "VLM /?") to display the valid parameters; then load the VLM.EXE file with a valid command line parameter.PAGENUM=263 ID="BP251"VLM-1.00-16: The VLM.EXE file <version> is currently loaded.Explanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running the VLM.EXE file with the /D parameter.)Action: No action is required; this is simply an information message.VLM-1.00-17: The VLM.EXE file is not currently loaded.Explanation: This message is displayed during the VLM.EXE file diagnostics display. (The diagnostics display is accessed by running the VLM.EXE file with the /D parameter.) Action: No action is required; this is simply an information message.VLM-1.00-30: A task switcher has been detected in memory. The VLM.EXE file cannot be loaded under a task switcher. Exit the task switcher; then try again.Explanation: The NetWare® DOS RequesterTM software cannot function properly when loaded after a task switcher.  A task switcher has been previously loaded. (Task switchers include DR DOS® TaskMax, MS-DOS* 5.0 DOSSHELL, and MS Windows 3.1 in standard mode.)Action: Unload the task switcher before attempting to load the NetWare DOS Requester.VLM-1.00-31: Network error on server <name>. Check network cabling or server status.Explanation: This is a critical communications error between the client workstation and the NetWare® server. This error may also appear as "General failure on device NETWORK."  A communications error can be caused by either a hardware or software failure.Action: Check the hardware and make sure that the network cable is connected properly and that the NetWare server is up and running properly.  If the condition persists, report the problem to your Novell Authorized ResellerCLM representative.PAGENUM=264 ID="BP252"VLM-1.00-32: The VLM.EXE file is not loaded. VLM.EXE cannot be unloaded.Explanation: An attempt was made to unload the VLM.EXE file using the /U parameter. Action: The condition that caused this message to occur is invalid, so no action is required.VLM-1.00-33: The loaded VLM.EXE file has a different version. VLM.EXE cannot be unloaded. Make sure the VLM.EXE file you are using has the same version number and then try to unload VLM.EXE.Explanation: An attempt was made to unload the VLM.EXE file using the /U parameter. Action: Use the same version of the VLM.EXE file to try the unload as was used to load; otherwise, the VLM.EXE file that is loaded in memory can be removed only by rebooting the computer.VLM-1.00-34: The loaded VLM.EXE file indicates it is unsafe to execute an unload for VLM number <number>. VLM.EXE will not be unloaded. Unload all memory resident programs (TSRs) that were loaded after the VLM.EXE file and then try to unload VLM.EXE.Explanation: An attempt was made to unload the VLM.EXE file using the /U parameter. The loaded VLM.EXE file refused to unload.  This usually is caused by interrupts being used after the VLM.EXE file was loaded. Another possible cause is that a VLMTM program is in an unsafe state to unload.Action: Unload all the TSR (terminate-and-stay-resident) programs that were loaded after the VLM.EXE file; then try to unload VLM.EXE. Make sure all loaded VLM programs are in use before unloading.VLM-1.00-36: The VLM.EXE file cannot use expanded memory (EMS). VLM.EXE will use an alternate memory scheme.Explanation: An attempt was made to load the VLM.EXE file in expanded memory (EMS) using the /ME parameter.  Either no LIM EMS 4.0 expanded memory manager is present or insufficient expanded memory is available to load the VLMTM program.  The VLM.EXE file attempts to use an alternate type of memory, either extended (XMS) or conventional, before failing to load.PAGENUM=265 ID="BP253"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure an expanded memory manager is loaded with sufficient memory, or do not specify the /ME parameter when loading VLM.EXE.VLM-1.00-37: The VLM.EXE file is using expanded memory (EMS).Explanation: This message indicates that the VLM.EXE file is loading the VLMTM programs into expanded memory (EMS).Action: No action is required; this is simply an information message.VLM-1.00-38: The VLM.EXE file cannot use extended memory (XMS). VLM.EXE will use an alternate memory scheme.Explanation: An attempt was made to load the VLM.EXE file in extended memory (XMS) using the /MX parameter.  Either no XMS 2.0 extended memory manager is present or insufficient extended memory is available to load the VLMTM programs.  The VLM.EXE file attempts to use an alternate type of memory, either expanded (EMS) or conventional, before failing to load.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure an extended memory manager is loaded with sufficient memory, or do not specify the /MX parameter when loading VLM.EXE.VLM-1.00-39: The VLM.EXE file is using extended memory (XMS).Explanation: This message indicates that the VLM.EXE file is loading the VLMTM programs into extended memory (XMS).Action: No action is required; this is simply an information message.VLM-1.00-40: The VLM.EXE file cannot use conventional memory. VLM.EXE will use an alternate memory scheme.Explanation: An attempt was made to load the VLM.EXE file in conventional memory using the /MC parameter. Insufficient conventional memory is available to load the VLMTM programs.  The VLM.EXE file attempts to use an alternate type of memory, either expanded (EMS) or extended (XMS), before failing to load.PAGENUM=266 ID="BP254"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure there is sufficient conventional memory, or do not specify the /MC parameter when loading VLM.EXE.VLM-1.00-41: The VLM.EXE file is using conventional memory.Explanation: This message indicates that the VLM.EXE file is loading the VLMTM programs into conventional memory.Action: No action is required; this is simply an information message.VLM-1.00-42: There is a missing or invalid value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.VLM-1.00-43: There is a missing or invalid ON/OFF value for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.VLM-1.00-44: There is an invalid string length specified for `<parameter>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter that is defined to use a string of a specified minimum or maximum length, but a string has been entered that does not fit the specified limits. This invalid line is ignored by the configuration process.PAGENUM=267 ID="BP255"Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.VLM-1.00-45: The parameter specified for the following option was out of range and has been adjusted.Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message.Action: Check and correct the parameter specified in the NET.CFG file.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.VLM-1.00-46: A duplicate VLM ID was found during VLM load test. The file will not be loaded. check the VLM= and USE DEFAULTS= parameters specified in the NET.CFG file before continuing.Explanation: The VLMTM programs for the NetWare® DOS RequesterTM software have been improperly configured to include two programs with the same VLM ID.  This can be caused by either a VLM being included twice in the VLM= parameter list, or by a VLM attempting to reuse a VLM ID assigned to a different VLM.Action: Check the NET.CFG file for duplicates in the VLM list. Make sure that the USE DEFAULTS= parameter is set to OFF.  IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.VLM-1.00-47: A file server could not be found. Check the network cabling and the server's status before continuing.Explanation: No NetWare® server was found when attempting to build an initial connection. This could be caused by any of the following: MARK=BULLETAn improperly configured network board or LAN driverImproperly configured IPXTM softwareA disconnected network cablePAGENUM=268 ID="BP256"An attempt to load the NetWare DOS RequesterTM software before a NetWare server has been initialized.Action: Try one or more of the following:MARK=BULLETEnsure that the network board and LAN driver are properly configured by checking the network board settings and the NET.CFG file settings. IDREF="FM37847"See Chapter 2, "NET.CFG Options Reference," on page 15 for more information.Ensure that IPX is configured to be bound properly to the right LAN driver.Check the network cabling.Ensure that a NetWare server is up and running before attempting to load the NetWare DOS Requester.VLM-1.00-60: There is an unrecognized entry `<entry>' on line <number> of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.Explanation: The configuration file contains a parameter under a header where it does not belong. This invalid line is ignored by the configuration process.Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.