#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'NetWare Client for OS/2 User GuideNetWare Client for OS/2Novell, 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=9 ID="BP1"How to Use This ManualRENDERAS="SECT1"IntroductionNetWare Client for OS/2 describes how to use and configure NetWare® ClientTM for OS/2* workstation software.NetWare Client for OS/2 workstation software enables OS/2 workstations to access NetWare servers. After you install and configure NetWare Client for OS/2, you can connect to a NetWare network and perform basic network tasks.RENDERAS="SECT1"Contents OverviewRENDERAS="SECT2"Chapter 1: IntroductionDescribes the features available in NetWare Client for OS/2. Also provides information for DOS users migrating to OS/2 and for NetWare 2 and NetWare 3TM software users migrating to NetWare 4TMsoftware.RENDERAS="SECT2"Chapter 2: Preparing HardwareGives a list of hardware prequisites necessary to install and configure NetWare Client for OS/2.RENDERAS="SECT2"Chapter 3: Installing NetWare Client for OS/2Explains how to install the NetWare Client for OS/2 software on your OS/2 workstation.RENDERAS="SECT2"Chapter 4: Configuring NetWare Client for OS/2Explains how to configure NetWare Client for OS/2 using the NET.CFG file.PAGENUM=10 ID="BP2"RENDERAS="SECT2"Chapter 5: Using Network Boards and LAN DriversDiscusses issues regarding network boards, LAN drivers, and frame types.RENDERAS="SECT2"Chapter 6: Logging In to Your NetworkThis chapter explains how to log in to your NetWare network after you've installed NetWare Client for OS/2.RENDERAS="SECT2"Chapter 7: Using NetWare ToolsExplains how to use the NetWare ToolsTM utility.RENDERAS="SECT2"Chapter 8: Using Virtual DOS and WindowsDescribes ways of using the virtual DOS and WIN-OS/2* features available in OS/2 with NetWare.RENDERAS="SECT2"Chapter 9: Printing from Your WorkstationExplains how to access the NetWare print services available on your network from your OS/2 workstation.RENDERAS="SECT2"Chapter 10: Backing Up Your WorkstationDescribes the TSAOS2 program and how it allows your network supervisor to back up your OS/2 workstation to the network.RENDERAS="SECT2"Chapter 11: Using Remote Program LoadExplains how to add a Remote Program Load (RPL) workstation to your network.RENDERAS="SECT2"Chapter 12: Improving Speed and SecurityDescribes how Packet BurstTM, Large Internet Packets, and NCP Packet Signature functionality can improve speed and security on your network.PAGENUM=11 ID="BP3"RENDERAS="SECT2"Chapter 13: Using Token Ring NetworksExplains how to install and configure source routing on NetWare servers and OS/2 workstations.RENDERAS="SECT2"Chapter 14: Using Named PipesExplains how to install and configure Named Pipes support on your workstation.RENDERAS="SECT2"Chapter 15: Using NetBIOSExplains how to set up the Novell NetBIOS driver and how to configure your workstation for NetBIOS when you also have IBM Extended Services or LAN Services NetBIOS installed.RENDERAS="SECT2"Chapter 16: Using ODINSUPExplains how to set up ODINSUP on your OS/2 workstation.RENDERAS="SECT2"Chapter 17: Using LANSUPExplains how to set up LANSUP on your OS/2 workstation.RENDERAS="SECT2"Appendix A: NET.CFG Options ReferenceProvides an alphabetical listing of NET.CFG options.RENDERAS="SECT2"Appendix B: System MessagesProvides systems messages and explanations for all NetWare Client for OS/2 drivers and daemons.RENDERAS="SECT2"Appendix C: Architecture DiagramsProvides diagrams to help present a technical overview of NetWare Client for OS/2.PAGENUM=12 ID="BP4"RENDERAS="SECT1"Documentation 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 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 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.RENDERAS="SECT2"DOS 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.PAGENUM=13 ID="BP5"RENDERAS="SECT2"DOS 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.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.PAGENUM=14 ID="BP6"Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text. RENDERAS="SECT2"Key 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 File Section Headings and Parameter SettingsNET.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:[Begin 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 1350[End example]PAGENUM=15 ID="BP7"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 CommandsUNIX® 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.RENDERAS="SECT2"UNIX Filenames, Directory Names, and PathnamesUNIX 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.PAGENUM=16 ID="BP8"RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_hostyou type the name of a computer on your network in place of remote_host.RENDERAS="SECT1"Online HelpMARK=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 /?".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.Online OS/2 help. This manual is also available online in native OS/2 format. After you've installed NetWare Client for OS/2, you can access this manual from the "Novell" folder on the OS/2 desktop.RENDERAS="SECT1"Additional Help ResourcesMARK=BULLETNovell 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.PAGENUM=17 ID="BP9"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.Other Novell publications. Novell Applications Notes and Novell Research Reports 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-111PAGENUM=18 ID="BP10"In 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.deIn 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.PAGENUM=19 ID="BP11"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.Customer 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.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"IntroductionCOLS=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="FM53983"NetWare Client for OS/2 Features COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM53983"1COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM42008"Information for DOS Users Migrating to OS/2  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM42008"1COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM81198"NetWare 2 and 3 Users Upgrading to NetWare 4  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM81198"6RENDERAS="SECT1"ID="FM53983"
NetWare Client for OS/2 FeaturesNetWare ClientTM for OS/2* workstation software enables OS/2 workstations to access NetWare® servers. After you install NetWare Client for OS/2, you can connect to a NetWare network and perform basic network tasks. NetWare Client for OS/2MARK=BULLETSupports both NetWare 3 and NetWare 4 servers.Offers Remote Program Load (RPL) workstation access.Supports SFT IIITM for both the client and SPXTM.Provides access for up to nine parallel ports.Supports OS/2, DOS/MS Windows private sessions, DOS/MS Windows global sessions, VMBoot private sessions, and VMBoot global sessions for NetWare 3.RENDERAS="SECT1"ID="FM42008"Information for DOS Users Migrating to OS/2This section explains the basic differences between using NetWare from an OS/2 workstation and using NetWare from a DOS workstation.PAGENUM=2 ID="BP13"RENDERAS="SECT2"ID="FM81702"ODI LAN DriversIDXID="w11871"BOOK="_idx" COLLECTION="nw41" TIDREF="i3057"ODITM LAN drivers used by NetWare Client for OS/2 serve the same purpose and follow the same technical specifications as ODI LAN drivers used by NetWare Client for DOS and MS Windows.OS/2 ODI drivers have the same filenames as DOS ODI drivers, except they have a .SYS extension instead of a .COM extension.OS/2 ODI drivers are loaded in the CONFIG.SYS file, whereas the DOS ODI drivers are loaded in the AUTOEXEC.BAT file.For OS/2, network drivers and device drivers are always IDXID="w11872"BOOK="_idx" COLLECTION="nw41" TIDREF="i3057"
loaded in CONFIG.SYS. AUTOEXEC.BAT is not used in OS/2.IDXID="w11873"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"RENDERAS="SECT2"ID="FM62427"IPXIDXID="w11874"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"NetWare Client for OS/2 uses the IPXTM protocol to connect to NetWare servers. For OS/2, IPX is a .SYS file and is loaded in the CONFIG.SYS file with the other NetWare drivers.If you use virtual DOS sessions in OS/2, those sessions use a virtualized version of IPX, called VIPX. VIPX talks to IPX to allow DOS sessions to communicate on the network.In a virtual DOS session, you run VIPX provided with NetWare Client for OS/2 rather than the IPX provided with NetWare Client for DOS and MS Windows.When you install NetWare Client for OS/2, lines to load IPX and VIPX are loaded in CONFIG.SYS.RENDERAS="SECT2"ID="FM45879"NET.CFG FileIDXID="w11875"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"The NET.CFG file serves the same purpose under OS/2 as it does under DOS: it allows you to configure your network connection.NET.CFG for OS/2 has options and settings just as NET.CFG for DOS. However, options and settings are somewhat different. Some use different syntax and configure different software components. Because of this, you cannot just copy NET.CFG from a DOS workstation to an OS/2 workstation and expect it to work. Instead, create a new NET.CFG file for the OS/2 workstation if you have nondefault configurations.PAGENUM=3 ID="BP14"In OS/2, NET.CFG is a text file that can be created or edited with the NetWare Client for OS/2 installation program. This program contains online help showing the syntax of all options. (NET.CFG can be edited with a text editor as well.)You can put DOS and OS/2 NET.CFG options into the same NET.CFG file on your OS/2 workstation. Then, when you run a private virtual DOS session, NetWare Client for DOS and MS Windows will use the DOS options. NetWare Client for OS/2 ignores the DOS options.RENDERAS="SECT2"ID="FM74310"Logging InIDXID="w11876"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"When you boot your workstation, NetWare Client for OS/2 maps drive L: as the default drive to the SYS:LOGIN directory (configurable in NET.CFG).This mapping combines with the L:\OS2 mapping that the NetWare Client for OS/2 installation puts in your path, and gives you a search path to the login utilities. (You don't have to change to drive L: to log in.)NetWare Client for OS/2 does not support a IDXID="w11877"BOOK="_idx" COLLECTION="nw41" TIDREF="i2092"
LASTDRIVE setting in CONFIG.SYS.You can log in from any OS/2 session or from the desktop, and your login applies to all other OS/2 sessions.For example, if you logged in from the command line of an OS/2 session and then you went to the desktop and used NetWare ToolsTM, you would already be logged in to the same location you logged in to at the command line.The attachment from IDXID="w11878"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
NetWare Tools does not run a login script. To execute a login script, run LOGIN from the command line.You can also log in from virtual DOS sessions running on OS/2.You can set up virtual sessions so that each session can support its own login to the network (private sessions), or so that all sessions---including OS/2---share a single login to the network (global sessions). Network support from virtual DOS sessions works much the same as network support from regular DOS workstations. You use a NETX.EXE shell and a virtualized version of IPX, called VIPX.SYS.PAGENUM=4 ID="BP15"When logging in from virtual sessions, you do not have NetWare Directory ServicesTM (NDS) support. IDXID="w11879"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"This means that you can only log in to a NetWare 4 network that has bindery emulation.RENDERAS="SECT2"ID="FM61363"UtilitiesNetWare utilities for OS/2 have the same names as NetWare utilities for DOS. However, OS/2 utilities are different executable files than DOS utilities.NetWare OS/2 utilities are in the SYS:PUBLIC\OS2 and SYS:LOGIN\OS2 directories so they do not overlap with NetWare utilities for DOS in the SYS:PUBLIC and SYS:LOGIN directories.If you run a NetWare DOS utility in OS/2, OS/2 will try to start a DOS session to run that utility.The following utility files are available from the NetWare Client for OS/2 diskettes:MARK=BULLETIDXID="w11880"BOOK="_idx" COLLECTION="nw41" TIDREF="i908"
CX.EXEIDXID="w11881"BOOK="_idx" COLLECTION="nw41" TIDREF="i2339"
MAP.EXEIDXID="w11882"BOOK="_idx" COLLECTION="nw41" TIDREF="i2899"
NETX.EXEIDXID="w11883"BOOK="_idx" COLLECTION="nw41" TIDREF="i2923"
NLIST.EXEIDXID="w11884"BOOK="_idx" COLLECTION="nw41" TIDREF="i3008"
NPRINTER.EXERENDERAS="SECT2"ID="FM50248"Drive 
MappingsIDXID="w11885"BOOK="_idx" COLLECTION="nw41" TIDREF="i1221"
 and Search DrivesIDXID="w11886"BOOK="_idx" COLLECTION="nw41" TIDREF="i3977"Search drives are not used in OS/2. Instead, the search functionality to NetWare utilities and other programs is set up with PATH, LIBPATH, and DPATH statements in CONFIG.SYS. RENDERAS="SECT3"Mapping to Login UtilitiesWhen you boot your workstation, NetWare Client for OS/2 connects to the first server it finds and maps drive L: to the SYS:LOGIN directory (configurable in NET.CFG).PAGENUM=5 ID="BP16"This mapping combines with the L:\OS2 mapping that the NetWare Client for OS/2 installation puts in your path and gives you a search path to the login utilities.Once you log in, drive L: disappears.RENDERAS="SECT3"Mapping to Public UtilitiesThe NetWare default login script for OS/2 contains the following line mapping drive P: to public utilities:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP P:=SYS:PUBLICThis mapping combines with the P:\OS2 mapping that the NetWare Client for OS/2 installation puts in your path and gives you a search path to the SYS:PUBLIC\OS2 directory.When you type a utility name from any drive other than drive P:, the utility from the \OS2 subdirectory is executed.Even though your search path gets set to SYS:PUBLIC\OS2 by default, drive P: stays mapped to SYS:PUBLIC. If you change to drive P:, you are in SYS:PUBLIC, not SYS:PUBLIC\OS2. If you type a utility name at drive P:, the DOS version of the utility is executed.RENDERAS="SECT2"ID="FM55507"ID="FM74329"Other ProtocolsIDXID="w11887"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"NetWare Client for OS/2 provides support for the following protocols:TYPE="VERT"IPXSPXNamed PipesNetBIOSThese protocols support OS/2 client workstations and servers on a distributed application network. SPX supports some NetWare printing utilities.DOS client workstations running DOS Named Pipes or NetBIOS can connect to OS/2 application servers running Named Pipes or NetBIOS.You can select support for these protocols in the NetWare Client for OS/2 installation program. The protocols you select are loaded into CONFIG.SYS.PAGENUM=6 ID="BP17"To access SPX, Named Pipes, and NetBIOS support from virtual DOS and MS Windows sessions on OS/2, you must load some programs provided with NetWare Client for OS/2. (See IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255.)RENDERAS="SECT1"ID="FM81198"NetWare 2 and 3 Users Upgrading to NetWare 4Significant changes have been made in the following areas:MARK=BULLETDefault frame type for Ethernet ODI driversSelecting a preferred serverLogging in to the networkLogin scriptsMappings in the default login scriptMapping to the public utilitiesVirtual DOS and MS Windows sessionsRENDERAS="SECT2"ID="FM73975"Default Frame Type for Ethernet ODI DriversThe default frame type for Ethernet ODI drivers has changed.In NetWare 2 and 3, Ethernet drivers defaulted to the Ethernet 802.3 frame type. In NetWare 4, they default to the Ethernet 802.2 frame type. NetWare 4 server drivers for Ethernet also default to the Ethernet 802.2 frame type. Servers and workstations use the same frame type to communicate with each other.Routers must also support the frame type or your workstation can't get a connection. Some routers on your network may not support the Ethernet 802.2 frame type default.If you use the Ethernet 802.2 frame type on your workstation, it can't connect to a network expecting the Ethernet 802.3 frame type.PAGENUM=7 ID="BP18"To eliminate a potential conflict, you can define both frame types (Ethernet 802.2 and Ethernet 802.3) on your network. For the workstation, define frame types in NET.CFG. Include a line similar to the following, replacing NE2000 with the name of your ODI driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
frame ethernet_802.2
frame ethernet_802.3The first frame type defined is the only one used for the initial "Get Nearest Server" request. Therefore, if some of your servers use only one frame type, such as Ethernet 802.3, put that frame type first. That way your workstation can make a default connection to those servers.RENDERAS="SECT2"ID="FM53587"Selecting a Preferred IDXID="w11888"BOOK="_idx" COLLECTION="nw41" TIDREF="i3372"
ServerNetWare Directory ServicesTM (NDS) provided in NetWare 4 uses trees and contexts rather than servers to identify what you log in to. A new NET.CFG setting called IDXID="w11889"BOOK="_idx" COLLECTION="nw41" TIDREF="i3375"preferred tree has been created. Use preferred tree in NetWare 4 the same way you used preferred server in NetWare 2 and 3 (except that you specify a tree name rather than a server name).Use preferred tree only for sites that have more than one Directory tree.For example, to initially connect to a tree called Novell, add the following lines to your NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
preferred tree novellPreferred server is still a supported setting; however, the syntax has changed. You now type the word server as well as a server name. For exampleFORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
preferred server fs1
PAGENUM=8 ID="BP19"Regardless of your NET.CFG file, NetWare Client for OS/2 first tries to establish a default connection to an NDS server. This connection is made to the first NDS server that responds.If NetWare Client for OS/2 succeeds in connecting to an NDS server, it then looks for a preferred tree. Once it connects to a preferred tree, it checks to see if you have a preferred server specified. If that server is in the current context, it connects to that server.If NetWare Client for OS/2 can't connect to an NDS server, it tries to establish a default connection to a bindery server. If it connects to a bindery server, it first looks for a preferred server, ignoring any preferred tree you specified.RENDERAS="SECT2"ID="FM81379"Logging In to the NetworkIDXID="w11890"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"When you log in under NetWare 4, you log in to a Directory tree rather than a server. This means you log in to a location in the Directory (called a context) rather than to a server.RENDERAS="SECT3"Logging In from the OS/2 Command LineIDXID="w11891"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"You use the NetWare 4 LOGIN utility to log in from a command line. This utility is located in the SYS:LOGIN\OS2 directory.With LOGIN, you can specify a context in the Directory tree. A context includes a User object and an Organization object.For example, to log in to a NetWare 4 network, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN .JOHN.SALES_MKTGJOHN is the User object. SALES_MKTG is the Organization object.You can use the NetWare 4 LOGIN utility to log in to NetWare 3.1x servers. Use the same login syntax you used for NetWare 3.1x LOGIN and add the /B option. For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SALES_MKTG/NANCY /B
PAGENUM=9 ID="BP20"RENDERAS="SECT2"NetWare Tools Attach FeatureIDXID="w11892"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"The attachment from NetWare Tools does not run a login script. You must run LOGIN from the command line to execute a login script.RENDERAS="SECT2"ID="FM11635"IDXID="w11893"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
MappingsIDXID="w11894"BOOK="_idx" COLLECTION="nw41" TIDREF="i1221"
 in Default Login ScriptIDXID="w11895"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
In NetWare 2 and 3 a default login script was executed if you had no other login script.In NetWare 4, the default login script still exists. Unless the network supervisor specifies otherwise, using a parameter in the system login script, it is executed when a user login script doesn't exist.Also, search drives aren't used in OS/2. Instead, the search functionality to the NetWare utilities and other programs is set up with PATH, LIBPATH, and DPATH statements in CONFIG.SYS.The NetWare 4 default login script contains the following line mapping drive P: to the 
utilities:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP P:=SYS:PUBLICThis mapping combines with the P:\OS2 mapping that the NetWare Client for OS/2 installation puts in your path and gives you a search path to the SYS:PUBLIC\OS2 directory.When you execute a utility from any drive other than drive P:, the utility from the \OS2 subdirectory is executed. Even though your search path is set to SYS:PUBLIC\OS2 by default, drive P: stays mapped to SYS:PUBLIC. If you change to drive P:, you are in SYS:PUBLIC, not SYS:PUBLIC\OS2. If you execute a utility at drive P:, the DOS version of the utility is executed.RENDERAS="SECT2"ID="FM15972"Mapping to the Public UtilitiesWhen setting up system or user login scripts for OS/2 users, always map drive P: to SYS:PUBLIC, as shown:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP P:=SYS:PUBLIC
PAGENUM=10 ID="BP21"RENDERAS="SECT2"Why Drive P:This mapping combines with the P:\OS2 directory that the NetWare Client for OS/2 installation puts in your path. The combination gives you a search path to SYS:PUBLIC\OS2. If you use another mapping besides P:, that mapping will not combine with the P:\OS2 directory that NetWare Client for OS/2 puts in your path, leaving you without a search path to the utilities. When you execute a utility from a drive other than drive P:, the utility from the \OS2 subdirectory is executed.RENDERAS="SECT2"Why SYS:PUBLIC and not SYS:PUBLIC\OS2Do not map drive P: to SYS:PUBLIC\OS2.The NetWare utilities for OS/2 need to find language-specific files in the parent directory of the directory they are executed from.For example, a utility executed from SYS:PUBLIC\OS2 expects to find an \NLS subdirectory in SYS:PUBLIC.If the drive allowing access to the utilities is mapped to SYS:PUBLIC\OS2, that directory becomes the root of the drive, since all network drives mapped in OS/2 are root drives.This means that OS/2 doesn't recognize a parent directory for utilities. When utilities try to locate the \NLS subdirectory in their own parent directory, OS/2 returns an error and your utility won't run.If you change to drive P:, you are in SYS:PUBLIC, not SYS:PUBLIC\OS2. If you execute a utility from drive P:, the DOS version of the utility is executed.PAGENUM=11 ID="BP22"RENDERAS="SECT2"ID="FM58503"Login ScriptsThe following table shows the login script executed for the type of login and how to edit the login script.LABEL="1-1" PGWIDE=1 TOCENTRY="1" How to Edit Login Scripts for Each Type of SessionCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you log in fromCOLNAME=2 ROTATE="0" MOREROWS="0"Login script runCOLNAME=3 ROTATE="0" MOREROWS="0"How login script is editedVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"OS/2 sessionCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare 4 Login Profile objectCOLNAME=3 ROTATE="0" MOREROWS="0"With the NetWare Administrator for OS/2 utility.COLNAME=1 ROTATE="0" MOREROWS="0"OS/2 sessionCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare 3.12COLNAME=3 ROTATE="0" MOREROWS="0"Use SYSCONCOLNAME=1 ROTATE="0" MOREROWS="0"Private DOS/MS Windows sessionCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare 3.1x DOS login scriptCOLNAME=3 ROTATE="0" MOREROWS="0"From a text editor.Edit the SYS:MAIL\userID\LOGIN file or use a NetWare 3.1x utility, such as SYSCON.COLNAME=1 ROTATE="0" MOREROWS="0"Global DOS/MS Windows sessionCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare 3.1x DOS login scriptCOLNAME=3 ROTATE="0" MOREROWS="0"From a text editor. Edit the SYS:MAIL\userID\LOGIN file or use a NetWare 3.1x utility, such as SYSCON.COLNAME=1 ROTATE="0" MOREROWS="0"Global session booted from real DOS kernel and running NETX.EXECOLNAME=2 ROTATE="0" MOREROWS="0"NetWare 3.1x DOS login scriptCOLNAME=3 ROTATE="0" MOREROWS="0"From a text editor. Edit the SYS:MAIL\userID\LOGIN file or use a NetWare 3.1x utility, such as SYSCON.COLNAME=1 ROTATE="0" MOREROWS="0"Private session booted from real DOS kernel and running NetWare Client for DOS and MS Windows 4.COLNAME=2 ROTATE="0" MOREROWS="0"NetWare 4 Login Profile objectCOLNAME=3 ROTATE="0" MOREROWS="0"With the NetWare Administrator for OS/2 utility.RENDERAS="SECT2"ID="FM90581"Login Script Commands Not Supported in OS/2OS/2 login scripts do not support the following commands:COMPSEC DOS BREAK MACHINE NAMEPAGENUM=12 ID="BP23"The following commands have unique functions or limitations when used in OS/2 login scripts.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"CommandCOLNAME=2 ROTATE="0" MOREROWS="0"LimitationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"EXITCOLNAME=2 ROTATE="0" MOREROWS="0"Does not support the filename parameter.COLNAME=1 ROTATE="0" MOREROWS="0"DRIVECOLNAME=2 ROTATE="0" MOREROWS="0"Sets the default for the login process only.COLNAME=1 ROTATE="0" MOREROWS="0"INCLUDECOLNAME=2 ROTATE="0" MOREROWS="0"If you use an include statement, you must specify a Universal Naming Convention (UNC) pathname for the file to be included. For example, if the file to be included is called INCLUDE.TXT and it located on NetWare server FS1, volume SYS, directory PUBLIC, the include statement should read: MOREINFO="NONE"INCLUDE \\FS1\SYS\PUBLIC\  INCLUDE.TXTCOLNAME=1 ROTATE="0" MOREROWS="0"MAPCOLNAME=2 ROTATE="0" MOREROWS="0"You cannot map search drives in OS/2. The same functionality is provided by using the OS/ 2 PATH and DPATH commands. See the OS/2 documentation.COLNAME=1 ROTATE="0" MOREROWS="0"SETCOLNAME=2 ROTATE="0" MOREROWS="0"Sets the environment variable for the login process only. Spawned processes inherit the variable, but the variable disappears when LOGIN terminatesRENDERAS="SECT2"Virtual DOS and MS Windows SessionsIDXID="w11896"BOOK="_idx" COLLECTION="nw41" TIDREF="i4773"With NetWare Client for OS/2, you have full NetWare 3.1x functionality from both private and global sessions. However, you don't have NDS functionality (provided with NetWare 4).This means you can run NetWare 4 DOS utilities from a DOS session, but you can't access NetWare Directory Services. To a NetWare 4 server, your client appears to be a NetWare 3.1x bindery emulation client.To obtain NDS functionality, boot from a different DOS kernel than the one included with OS/2 and load the NetWare Client for DOS and MS Windows 4 software.Boot from a real DOS kernel by using the DOS_STARTUP_DRIVE setting. The OS/2 online Master Help Index explains how.PAGENUM=13 ID="BP24"Sessions booted from a IDXID="w11897"BOOK="_idx" COLLECTION="nw41" TIDREF="i1208"
real IDXID="w11898"BOOK="_idx" COLLECTION="nw41" TIDREF="i4773"
DOS kernel can have private or global support. Global sessions booted with a real DOS kernel have NetWare 3.1x support.Private sessions booted with a real DOS kernel can have NetWare 4 support if you load NetWare Client for DOS and MS Windows.IDREF="FM94086"Figure 1-1 on page 14 shows the NetWare functionality you have under all types of virtual sessions.PAGENUM=14 ID="BP25"LABEL="1-1" FLOAT="0"ID="FM94086"NetWare Support in DOS/MS Windows SessionsFILEREF="c41q74a.tif"PAGENUM=15 ID="BP26"LABEL="2"PAGENUM=17 ID="BP27"Preparing HardwareCOLS=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="FM74509"Hardware Prerequisites COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74509"17COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM39654"Network Cabling COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39654"18COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62756"Determining Network Board Settings COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62756"18RENDERAS="SECT1"ID="FM74509"Hardware PrerequisitesThe following checklist will help you prepare your workstation for installing NetWare ClientTM for OS/2*.MARK=CHECKBOXAn IBM* personal computer (or compatible) with a 386 (SX or DX) processor. OS/2 2.x operates only with 386 (SX and DX) processors and above because of its 32-bit architecture IDXID="w11899"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"
A hard disk with 3 MB of free storage for NetWare Client for OS/2 files8 MB of RAMA 1 to 1.44MB 3.5-inch diskette driveIf you want to use Remote Program Load (RPL), a Remote Reset PROM inserted in each RPL workstationA mouse or compatible pointing deviceA network board installed in your workstationA VGA monitorPAGENUM=18 ID="BP28"RENDERAS="SECT1"ID="FM39654"IDXID="w11900"BOOK="_idx" COLLECTION="nw41" TIDREF="i563"
Network CablingEach type of network board requires unique cabling. For requirements, see the manufacturer's documentation packaged with the board.Token ring network boards must have a physical connection to the MAU before you install NetWare Client for OS/2. Otherwise, the TOKEN driver will not load.RENDERAS="SECT1"ID="FM62756"Determining Network Board SettingsIDXID="w11901"BOOK="_idx" COLLECTION="nw41" TIDREF="i2848"
The NetWare Client for OS/2 installation program requires specific information about the network board in your workstation.Before installing NetWare Client for OS/2, record the values for the following settings:MARK=CHECKBOXIDXID="w11902"BOOK="_idx" COLLECTION="nw41" TIDREF="i1640"
Hardware interruptIn most cases, you can use interrupt line 3 or interrupt line 5 for your network board. If neither interrupt line 3 nor interrupt line 5 is available, see the manufacturer's documentation.We recommend that you don't use interrupt line 2. It may interfere with the VGA adapter.IDXID="w11903"BOOK="_idx" COLLECTION="nw41" TIDREF="i413"IDXID="w11904"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"
Base I/O portEach hardware device included in your workstation must have a different base I/O port setting. For more information, see the manufacturer's documentation.IDXID="w11905"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
Frame typeAll workstations and servers using a single network address must use the same frame type. The default for Novell ODITM drivers is 802.2.Other settingsOther settings are unique to the network board installed in your workstation. (See the documentation provided with your network board.)In most cases, leave your network board set to the factory settings. If you need to change the default settings, see the manufacturer's documentation.PAGENUM=19 ID="BP29"IDXID="w11906"BOOK="_idx" COLLECTION="nw41" TIDREF="i2848"
You can obtain setting information for your network board by using the following procedures.LABEL="2-1" PGWIDE=1 TOCENTRY="1" Finding Board SettingsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you have COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"EISA or MCA network boardsCOLNAME=2 ROTATE="0" MOREROWS="0"Run the computer's setup or reference program. This program will list the values for your network board settings.COLNAME=1 ROTATE="0" MOREROWS="0"ISA network boardsCOLNAME=2 ROTATE="0" MOREROWS="0"Physically view the network board to obtain the specific settings. The documentation provided with your network board will direct you where to locate each value.LABEL="3"PAGENUM=21 ID="BP30"ID="FM87895"Installing NetWare Client for OS/2COLS=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="FM46792"Installation Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46792"21COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM40337"Installing NetWare Client for OS/2 from Diskettes  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40337"25COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM96914"Installing NetWare Client for OS/2 from CD-ROM COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96914"31COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM67985"Upgrading NetWare Client for OS/2 from a Network Directory COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67985"33COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11062"Installing and Using NetWare VLM Boot COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11062"34RENDERAS="SECT1"IDXID="w11907"BOOK="_idx" COLLECTION="nw41" TIDREF="i1829"ID="FM46792"Installation OverviewFour things happen when you install NetWare® ClientTM for OS/2*:MARK=BULLETA directory is created on your workstationFiles are copiedThe Novell® group icon is createdThe CONFIG.SYS file is modifiedRENDERAS="SECT2"A Directory Is Created on Your WorkstationBy default, a \NETWARE directory is created in the root of the drive from which you boot OS/2. (If you specify another directory, it is created.)PAGENUM=22 ID="BP31"RENDERAS="SECT2"Files Are CopiedAll NetWare Client for OS/2 files are copied to the directory specified during installation. You can change your settings later without copying additional files from theCLASS=DISK WSOS2_1 diskette.Six kinds of files are copied:MARK=BULLETNetWare Client for OS/2 program filesDynamic Link Library (DLL) files for OS/2DLL files for MS WindowsNetwork board driversUtility files (INSTALL, NPRINTER, NWTOOLS, LOGIN, NLIST, MAP, CX, OS2_TSA)Unicode* tablesMost files on the diskette are compressed. The installation program decompresses them. To decompress a file, use the NWUNPACK utility on the diskette. Type "NWUNPACK" and the target directory, followed by the name of a file.If you install NetWare Client for OS/2 on an OS/2 for Windows workstation, the files are copied to the WINDOWS\SYSTEM directory.RENDERAS="SECT2"The Novell Group Icon Is CreatedA group icon called "Novell" is created on the OS/2 desktop. This group containsMARK=BULLETThe NetWare Client for OS/2 installation programThe NetWare ToolsTM utilityThe NPRINTER remote printing utilityThe OS2_TSA programPAGENUM=23 ID="BP32"RENDERAS="SECT2"The CONFIG.SYS File Is ModifiedThe previous version of CONFIG.SYS is automatically saved as CONFIG.BAK.The NETWARE directory (or the directory you specify) is included at the end of the PATH, LIBPATH, and DPATH statements so that OS/2 can find the NetWare Client for OS/2 files.Based on the ODITM driver and settings you choose, the NetWare Client section of CONFIG.SYS includes lines for loading NetWare Client for OS/2 components. This section is identified by comment lines before and after.Don't delete the comment lines before and after the NetWare Client for OS/2 lines. Everything between these comments is deleted and rewritten when you use the installation program to edit CONFIG.SYS.  Therefore, make a backup copy of CONFIG.SYS after your NetWare Client for OS/2 installation is completed.  Other configuration programs, such as IBM Extended Services, might rearrange CONFIG.SYS in such a way as to invalidate NetWare Client for OS/2.IDREF="FM32138"Figure 3-1 is a sample CONFIG.SYS file after installing NetWare Client for OS/2.PAGENUM=24 ID="BP33"LABEL="3-1" FLOAT="0"ID="FM32138"Sample CONFIG.SYS File after NetWare Client for OS/2 InstallationFILEREF="c41q34a.tif"PAGENUM=25 ID="BP34"RENDERAS="SECT1"ID="FM40337"Installing NetWare Client for OS/2 from DiskettesIf you are installing NetWare Client for OS/2 from diskettes for the first time, complete the following.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXIDXID="w11908"BOOK="_idx" COLLECTION="nw41" TIDREF="i1829"
Working copies of the following NetWare Client for OS/2 diskettes:MARK=BULLETCLASS=DISKWSOS2_1CLASS=DISKWSOS2 _2CLASS=DISKWSOS2_3CLASS=DISKWSDRV_1CLASS=DISKOS2UTIL1CLASS=DISKOS2DOC_1(Optional) Working copies of any NetWare compatible third-party network board driversIDXID="w11909"BOOK="_idx" COLLECTION="nw41" TIDREF="i2851"
You need a third-party MLIDTM driver for the network board installed in your workstation if one is not provided with the NetWare Client for OS/2 software.NetWare Client for OS/2 supports most network boards. If NetWare Client for OS/2 does not list a driver for your network board, check the network board package for a driver or contact the network board manufacturer to obtain a compatible driver.If NetWare Client for OS/2 was running previously on your workstation, then a number of NetWare files have been opened by OS/2 through the NetWare Client for OS/2 statements in the CONFIG.SYS.  As new files are being copied by the installation utility, you will see errors appear because the existing files of the same name cannot be closed and replaced by the installation utility. This might cause compatability problems because of the files that were not updated.  The best way to resolve this issue is to boot your OS/2 workstation without NetWare Client for OS/2 loaded. That way, all of the necessary files are copied correctly.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Go to the OS/2 desktop.PAGENUM=26 ID="BP35"PERFORMANCE="REQUIRED"Insert the 
WSOS2_1 diskette into a disk drive.PERFORMANCE="REQUIRED"Choose the "Drive A" icon on the desktop.The "Drive A - Tree View" window appears.PERFORMANCE="REQUIRED"From the "Drive A - Tree View" window, select the "Drive A" icon.PERFORMANCE="REQUIRED"Load the installation program by selecting the "INSTALL.EXE" icon.PERFORMANCE="REQUIRED"ID="FM95268"From the "Installation" menu, select "Requester on workstation..."The "Set Target Directory" window appears.LABEL="3-2" FLOAT="0""Set Target Directory" WindowFILEREF="c41q20a.tif"PERFORMANCE="REQUIRED"Set the appropriate path and source drive, and then choose "OK."The "Requester Installation" window appears.
PAGENUM=27 ID="BP36"LABEL="3-3" FLOAT="0""Requester Installation" WindowFILEREF="c41q21a.tif"PERFORMANCE="REQUIRED"Accept the default of" Edit CONFIG.SYS and Copy All Files" by choosing "OK."The other three choices are for changing the initial installation of NetWare Client for OS/2.The "Step 1 - Choose the ODI LAN Driver" window appears.LABEL="3-4" FLOAT="0""Step 1 - Choose the ODI LAN Driver" WindowFILEREF="c41q22a.tif"PERFORMANCE="REQUIRED"Select the appropriate driver.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose the arrow next to the "ODI LAN Driver" window.PERFORMANCE="REQUIRED"Insert 
CLASS=DISKWSDRV_1 into drive A: as instructed and choose "OK."PERFORMANCE="REQUIRED"Select the LAN Driver provided by the NetWare Client for OS/2 software or a third-party vendor.PERFORMANCE="REQUIRED"Choose "Continue."
PAGENUM=28 ID="BP37"The "Step 2 - Choose NetWare Support for DOS and Windows Applications" window appears.LABEL="3-5" FLOAT="0""Step 2 - Choose NetWare Support for DOS and Windows Applications" WindowFILEREF="c41q23a.tif"PERFORMANCE="REQUIRED"Select "IPX Support for DOS and MS Windows" and "Default NetWare Shell Support," and then choose "Continue."For more information on available selections, choose "Help."The "Suggested Default Settings to AUTOEXEC.BAT" window appears.
PAGENUM=29 ID="BP38"LABEL="3-6" FLOAT="0""Suggested Default Settings to AUTOEXEC.BAT" WindowFILEREF="c41q24a.tif"PERFORMANCE="REQUIRED"Accept the default by choosing "Save."For more information on available selections, choose "Help."PERFORMANCE="REQUIRED"When asked if you want to add files to another batch file, select "No."If you select "Yes," you can customize boot files for individual DOS sessions. Typically, all DOS sessions use the same boot file (for example, the AUTOEXEC.BAT file).PERFORMANCE="REQUIRED"If prompted to change the DOS_LASTDRIVE setting, select "OK."Make sure your DOS_LASTDRIVE setting is correct upon completion of NetWare Client for OS/2 installation. See "Changing and Saving DOS and WIN-OS/2 Settings" in the OS/2 Master Help Index.The "Step 3 - Choose Optional Protocols" window appears.
PAGENUM=30 ID="BP39"LABEL="3-7" FLOAT="0""Choose Optional Protocols" WindowFILEREF="c41q36a.tif"PERFORMANCE="REQUIRED"Accept the defaults by choosing "Save."For more information on available selections, choose "Help."The "Save Changes to CONFIG.SYS" window appears.PERFORMANCE="REQUIRED"To save the file as CONFIG.SYS, choose "OK." To save the file under a different name, edit the window.The "Copy ODI LAN Driver Files" window appears.PERFORMANCE="REQUIRED"Accept the default by choosing "OK."For more information on available selections, choose "Help."The "Copy Requester Files" window appears.PERFORMANCE="REQUIRED"Choose "Copy."If NetWare Client for OS/2 was running previously on your workstation, then a number of NetWare files have been opened by OS/2 through the NetWare Client for OS/2 statements in the CONFIG.SYS. As new files are being copied by the installation utility, you will see errors appear because the existing files of the same name cannot be closed and replaced by the installation utility. This might cause compatability problems because of the files that were not updated.
PAGENUM=31 ID="BP40"The best way to resolve this issue is to boot your OS/2 workstation without NetWare Client for OS/2 loaded. That way, all of the necessary files are copied correctly.PERFORMANCE="REQUIRED"To complete installation, follow instructions on your screen.PERFORMANCE="REQUIRED"Read the final screen that appears after installation.PERFORMANCE="REQUIRED"Configure your workstation.Refer to 
IDREF="FM93081"Step 4 on page 43.Detailed information on each configuration option is located in 
IDREF="FM19476"Figure 4-5 on page 
IDREF="FM19476"47 and in 
IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255.For changes to take effect from your configuration, restart your workstation.RENDERAS="SECT1"IDXID="w11910"BOOK="_idx" COLLECTION="nw41" TIDREF="i1829"ID="FM96914"Installing NetWare Client for OS/2 from CD-ROMYou can use the NetWare server installation program on CD-ROM to copy workstation installation files to the PUBLIC\CLIENT directory of volume SYS:.RENDERAS="SECT2"Copying Client Installation Software from the CD-ROM to the ServerTo copy NetWare Client for OS/2 installation software from CD-ROM to the server, follow these steps below.RENDERAS="SECT3"PrerequisiteMARK=CHECKBOXCD-ROM drive installed as a device on your workstation according to the manufacturer's instructionsRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Log in.PERFORMANCE="REQUIRED"Make a subdirectory named CLIENT under SYS:PUBLIC for the workstation installation files.
PAGENUM=32 ID="BP41"PERFORMANCE="REQUIRED"Copy files from the CLIENT directory on the CD-ROM to SYS:PUBLIC\CLIENT.Type either
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY drive:\source path\*.* drive:\destination path /s /e /cor
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY drive:\source path\*.* drive:\destination path /s /e /vFor example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY D:\CLIENT\OS2\*.* H:\PUBLIC\OS2 /s /e /vDon't use the COPY command for this procedure. The directory structure within each subdirectory must be maintained.You can also set up your CD-ROM drive as a volume on your network. This allows you to run workstation installation programs directly from subdirectories under CLIENT on the CD-ROM.RENDERAS="SECT2"Creating Workstation Installation Diskettes from IDXID="w11911"BOOK="_idx" COLLECTION="nw41" TIDREF="i608"
CD-ROMTo install the CD-ROM either as a local volume or as a network device, follow these steps.RENDERAS="SECT3"IDXID="w11912"BOOK="_idx" COLLECTION="nw41" TIDREF="i1819"
ProcedurePERFORMANCE="REQUIRED"Format high-density diskettes using the FORMAT command.You must format three diskettes for the NetWare Client for OS/2 installation.PERFORMANCE="REQUIRED"Go to the drive corresponding to the CD-ROM.PERFORMANCE="REQUIRED"Change to the CLIENT directory on the CD-ROM.PERFORMANCE="REQUIRED"Change to the OS/2 subdirectory.PERFORMANCE="REQUIRED"Set the 
nwlanguage environment variable.Type the following at the command line:
PAGENUM=33 ID="BP42"FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NWLANGUAGE=language MOREINFO="NONE"<Enter>Replace 
language with the appropriate language found in the NLS subdirectory under CLIENT\OS2.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK drive_letter: languageMOREINFO="NONE" <Enter>For example, type either
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK A: ENGLISHMOREINFO="NONE" <Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK B: ENGLISHMOREINFO="NONE" <Enter>MAKEDISK copies client installation files from the CD-ROM directory to the diskettes.PERFORMANCE="REQUIRED"Save these diskettes until after you have installed all NetWare workstations.RENDERAS="SECT1"IDXID="w11913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1829"ID="FM67985"Upgrading NetWare Client for OS/2 from a Network DirectoryThis feature is available only on NetWare 3.12 and NetWare 4 servers.The following checklist and procedures help set up your workstation for installing NetWare workstation software from a network directory. It is the quickest and easiest way to upgrade NetWare Client software. RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXA version of the NetWare Client for OS/2 software running on your workstationA copy of the NetWare Client for OS/2 software on your networkPAGENUM=34 ID="BP43"If NetWare Client for OS/2 was running previously on your workstation, then a number of NetWare files have been opened by OS/2 through the NetWare Client for OS/2 statements in the CONFIG.SYS. As new files are being copied by the installation utility, you will see errors appear because the existing files of the same name cannot be closed and replaced by the installation utility. This may cause compatability problems because of the files that were not updated. The best way to resolve this issue is to boot your OS/2 workstation without NetWare Client for OS/2 loaded. Then, all of the necessary files will be copied correctly.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Log in.PERFORMANCE="REQUIRED"Map a drive to the PUBLIC\CLIENT\OS2 directory on volume SYS:.PERFORMANCE="REQUIRED"Type "INSTALL."PERFORMANCE="REQUIRED"Complete this installation by going to 
IDREF="FM95268"Step 6 on page 26 and following those instructions.RENDERAS="SECT1"Installing and UsingID="FM11062"
NetWare VLM BootIDXID="w11914"BOOK="_idx" COLLECTION="nw41" TIDREF="i2818"
NetWare Virtual Loadable ModuleTM (VLM) Boot makes it possible to have an acutal DOS kernel running on an OS/2 workstation. This DOS kernel allows you to effectively run NetWare Administrator from an OS/2 client workstation.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXOS/2 verison 2.11 installed on your client workstationNetWare VLMTM Boot will not run on OS/2 version 2.1 or earlier.NetWare Client for OS/2 installed on your client workstationA copy of the CLASS=DISKDOS_VLMBOOT disketteA floppy drive on your client workstationRENDERAS="SECT2"IDXID="w11915"BOOK="_idx" COLLECTION="nw41" TIDREF="i2818"
Installing NetWare VLM BootPERFORMANCE="REQUIRED"Go to the OS/2 desktop.PERFORMANCE="REQUIRED"Open the "Novell" folder.PERFORMANCE="REQUIRED"Choose the "Install" icon.
PAGENUM=35 ID="BP44"PERFORMANCE="REQUIRED"From the "Configuration" menu, choose "VLM Boot Setup."The "VLM Boot Setup" screen appears.PERFORMANCE="REQUIRED"Enter the source floppy drive letter or accept the default, and then select "OK."PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKDOS_VLMBOOT diskette into the selected source drive and then select "OK."The "Create a NetWare VLM Boot Image File" screen appears.PERFORMANCE="REQUIRED"Select the "Create a NetWare VLM Boot image file" checkbox.PERFORMANCE="REQUIRED"Enter the source floppy drive letter or accept the default and then select "OK."A NetWare VLM Boot file is created.PERFORMANCE="REQUIRED"Exit the Installation program and restart your workstation.RENDERAS="SECT2"IDXID="w11916"BOOK="_idx" COLLECTION="nw41" TIDREF="i2818"
Using NetWare VLM BootPERFORMANCE="REQUIRED"Go to the OS/2 desktop.PERFORMANCE="REQUIRED"Open the "Novell" folder.PERFORMANCE="REQUIRED"Choose the "VLMBOOT" icon.An actual DOS session is now open on your workstation and attached to your network.LABEL="4"PAGENUM=37 ID="BP45"ID="FM65037"Configuring NetWare Client for OS/2COLS=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="FM50525"Configuration Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50525"37COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM92505"Using NET.CFG COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92505"41COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM45501"NET.CFG Format Requirements COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45501"42COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM47597"Creating or Editing NET.CFG COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47597"43COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM28802"Troubleshooting Tips COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28802"46RENDERAS="SECT1"ID="FM50525"IDXID="w11917"BOOK="_idx" COLLECTION="nw41" TIDREF="i762"Configuration OverviewAfter you've installed NetWare ClientTM for OS/2* on your workstation, you must configure it to run with your network.Configuration options for NetWare Client for OS/2 are stored in the NET.CFG file. When you start up your workstation, NetWare Client for OS/2 searches for NET.CFG in the directories specified in the DPATH line in CONFIG.SYS. If NetWare Client for OS/2 doesn't find a NET.CFG file, it starts up using default configuration values built into the software.RENDERAS="SECT2"When Configuration Is RequiredYou must configure NetWare Client for OS/2 ifMARK=BULLETYour workstation has more than one network boardPAGENUM=38 ID="BP46"Your workstation has a single board, but the board is not using factory default settingsYour network uses an Ethernet frame type other than Ethernet 802.2NetWare Client for OS/2 will share a network board with other softwareRENDERAS="SECT2"ID="FM85634"Other Situations When Configuration Might Be UsefulConfiguration may also be useful in these circumstances:MARK=BULLETYou want to change the default packet signature security level.You want to turn off Packet BurstTM or Large Internet Packet transmissions.Your workstation will connect to a token ring network using source-routing.Your workstation will use NetBIOS or Dual NetBIOS protocols.Your workstation will use Named Pipes protocol.You want your workstation to connect to a preferred Directory tree.You are setting up Remote Program Load (RPL) workstations.You want to change your default login drive.RENDERAS="SECT2"ID="FM76859"About Protocol Support in NetWare Client for OS/2NetWare Client for OS/2 provides four kinds of protocol supportIDXID="w11918"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
:MARK=BULLETIPXTMSPXTMNamed PipesNetBIOS (emulation)PAGENUM=39 ID="BP47"IDXID="w11919"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"
NetWare® servers and client workstations use IPX as the primary protocol to communicate with each other. They also use SPX for some communications, such as communications between a workstation running NPRINTER and a NetWare print server.Support for IPX on the workstation is installed when you install NetWare Client for OS/2. IDXID="w11920"BOOK="_idx" COLLECTION="nw41" TIDREF="i261"
SPX, NetBIOS, and Named Pipes protocols are provided by Novell so that NetWare clients and servers can also function asMARK=BULLETDistributed application clients and serversNon-NetWare network clients and serversTerminals connected to mainframes or minicomputersFor example, the Lotus Notes* distributed application uses NetBIOS or SPX for communications; Microsoft* SQL Server uses Named Pipes. LAN Server networks use NetBIOS, and many Communications Manager connections to a gateway also use NetBIOS.Other protocols not provided with NetWare Client for OS/2 can be used for these purposes.For example, the TCP/IP protocol provided by Novell's LAN WorkPlaceTM for OS/2 is commonly used for connections to UNIX® hosts. These other protocols are not discussed in this book.IDREF="FM99461"Figure 4-1 illustrates the components of a IDXID="w11921"BOOK="_idx" COLLECTION="nw41" TIDREF="i1158"
distributed application network.PAGENUM=40 ID="BP48"LABEL="4-1" FLOAT="0"ID="FM99461"Protocol Software Is Separate from Distributed Application SoftwareFILEREF="c41q41a.tif"Several protocols can be installed on the same computer at the same time. All of these protocols can use the same network cabling, although each protocol might communicate on a completely separate logical network.IDREF="FM34504"Figure 4-2 shows how a NetWare network and a distributed application network share cabling. PAGENUM=41 ID="BP49"LABEL="4-2" FLOAT="0"ID="FM34504"A Distributed Application on a NetWare NetworkFILEREF="c41q42a.tif"RENDERAS="SECT1"ID="FM92505"Using NET.CFGConfiguration options for NetWare Client for OS/2 are stored in a NET.CFG file. When you turn on your workstation, NetWare Client for OS/2 searches for NET.CFG in the directories specified in the DPATH line of CONFIG.SYS.If NetWare Client for OS/2 does not find NET.CFG, it uses a set of default configuration values built into the software.NET.CFG is located in the root directory of your boot drive. If you have previously configured NetWare Client for OS/2 on a workstation, a NE
T.CFG file already exists for your workstation.You can change the current configuration by modifying and saving the existing file.PAGENUM=42 ID="BP50"Reinstalling NetWare Client for OS/2 will not overwrite an existing NET.CFG file; instead, the existing NET.CFG file will appear in the installation program for you to edit.If you have not configured NetWare Client for OS/2 on your workstation before, a NET.CFG file does not exist for your workstation. You must create this file to configure your workstation. RENDERAS="SECT1"IDXID="w11922"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"ID="FM45501"ID="FM83224"NET.CIDXID="w11923"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"
FG Format RequirementsIDREF="FM17825"Figure 4-3 illustrates the format required to create or modify NET.CFG.LABEL="4-3" FLOAT="0"ID="FM17825"NET.CFG FormatFILEREF="c41q01a.tif"To create or modify NET.CFG, use the following rules:PAGENUM=43 ID="BP51"MARK=BULLETType options at the left margin of the file with no spaces before or after them. Options are not case-sensitive. Type one option per line. Type settings, one per line, on the lines following the option to which they apply.When editing NET.CFG, use the Space bar, rather than the Tab key, to indent these settings. The Tab key moves to the next field on the screen. Indent settings at least one space. Settings are not case-sensitive.Place a hard return at the end of every line in the file, including the last line. If you don't put a hard return at the end of the last line, the line is ignored.Blank lines are not necessary and are ignored.Precede comment lines with a semicolon (;).RENDERAS="SECT1"ID="FM47597"Creating or Editing NET.CFGRENDERAS="SECT2"ID="FM12931"ID="FM53222"PrerequisiteMARK=CHECKBOXNetWare Client for OS/2 is installed on your workstation.RENDERAS="SECT2"ProceduresTo create or edit NET.CFG with the installation program,PERFORMANCE="REQUIRED"Go to the OS/2 desktop.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Novell icon on the desktop.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Install icon in the 
CLASS=MENUITEM MOREINFO="NONE"Novell window.PERFORMANCE="REQUIRED"ID="FM93081"From the 
CLASS=MENUITEM MOREINFO="NONE"Configuration menu, select 
CLASS=MENUITEM MOREINFO="NONE"This workstation. . .The 
CLASS=MENUITEM MOREINFO="NONE"Default Location for NET.CFG File window appears.PERFORMANCE="REQUIRED"Enter the path of your NET.CFG file and select
CLASS=MENUITEM MOREINFO="NONE" Edit.
PAGENUM=44 ID="BP52"The 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG edit screen appears. If this is a new installation, there is not a default NET.CFG file and the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box will be empty.PERFORMANCE="REQUIRED"Type the NET.CFG options you want in the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box.A typical NET.CFG might look likeFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
  int 5
  port 340
  frame ethernet_802.3FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
  default login drive f
  display hard errors off
  name context "finance.novell" preferred tree redwood
  signature level 3The "default login drive" setting requires changes to the CONFIG.SYS file. See IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255 for instructions.Signature level 3 is the most secure, requires Packet Burst to be enabled, and the server signature level needs to be set at level 1 or higher for login. See IDREF="FM99776"Chapter 12, "Improving Speed and Security," on page 155 for more information.For an explanation of how to use theCLASS=MENUITEM MOREINFO="NONE" Edit the NET.CFG file for this workstation window, see IDREF="FM89881"Figure 4-4.PAGENUM=45 ID="BP53"LABEL="4-4" FLOAT="0"IDXID="w11924"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"ID="FM89881"How to Edit the NET.CFG FileFILEREF="c41q04a.tif"PERFORMANCE="REQUIRED"To save your changes to NET.CFG, choose 
CLASS=MENUITEM MOREINFO="NONE"Save.
PAGENUM=46 ID="BP54"PERFORMANCE="REQUIRED"To exit the installation program, double-click in the upper left corner of the main window.PERFORMANCE="REQUIRED"For changes to take effect from your configuration, use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to restart your workstation.Installation and configuration changes will not take effect until you restart your workstation.RENDERAS="SECT1"ID="FM28802"IDXID="w11925"BOOK="_idx" COLLECTION="nw41" TIDREF="i4584"
Troubleshooting TipsSee that:MARK=BULLETframe types are set the same on the workstation and the server.board configurations and software parameters match.NET.CFG parameters, such as name context, match your NetWare system configuration.network cabling is within IEEE specifications and is properly connected and terminated.all network software is the most recent version available.RENDERAS="SECT1"Quick Reference List of NET.CFG OptionsIDREF="FM19476"Figure 4-5 lists NET.CFG options and settings and the default value for each.Detailed information on each configuration option is located in IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255.PAGENUM=47 ID="BP55"LABEL="4-5" FLOAT="0"ID="FM19476"NET.CFG Quick ReferenceFILEREF="c41q08a.tif"ID="FM57258"PAGENUM=48 ID="BP56"ID="FM11949"PAGENUM=49 ID="BP57"LABEL="5"PAGENUM=51 ID="BP58"ID="FM59288"Using Network Boards and LAN DriversCOLS=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="FM26624"Specifying Frame Types for Your Workstation  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM26624"51COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM24486"Matching Network Board and ODI Driver Settings COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24486"53COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88950"Cautions with the Default Frame Type  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88950"54COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31896"Defining Both Ethernet 802.2 and Ethernet 802.3 Frame Types COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM31896"55COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM23495"Using More Than One Network Board COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23495"55RENDERAS="SECT1"ID="FM26624"ID="FM64269"Specifying FrameIDXID="w11926"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
 Types for Your WorkstationRENDERAS="SECT2"OverviewAll communications on a network consist of packets of information being sent between workstation.There are different kinds of packets, distinguished from each other by the order and type of information in the packet. Each kind of packet has its own definition, called aIDXID="w11927"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"frame type.For each workstation to communicate by a certain frame type, each workstation on the network must be configured to use that frame type.A IDXID="w11928"BOOK="_idx" COLLECTION="nw41" TIDREF="i2850"network board in your workstation allows your workstation to communicate with other workstations on your network and with the NetWare® server.IDXID="w11929"BOOK="_idx" COLLECTION="nw41" TIDREF="i2035"LAN driver software serves as the link between your workstation's operating system and the network.PAGENUM=52 ID="BP59"By default, each LAN driver uses only one kind of frame type. However, most LAN drivers can support other frame types if they are configured to do so through the NET.CFG.For example, an NE2000TM LAN driver supports the following frame types: Ethernet 802.2, Ethernet 802.3, Ethernet II, and Ethernet SNAP.IDREF="FM83727"Table 5-1 lists some frame types and common LAN drivers.LABEL="5-1" PGWIDE=0 TOCENTRY="1"ID="FM83727" List of Frame Types and LAN DriversCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Frame typeIDXID="w11930"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"COLNAME=2 ROTATE="0" MOREROWS="0"LAN driverVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Ethernet 802.3COLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, 3C505, 3C523, EXOS205, EXOS215, ODINSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet 802.2COLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, EXOS205, EXOS215, ODINSUP, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet IICOLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, 3C505, 3C523, EXOS205, EXOS215, ODINSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, EXOS205, EXOS215, ODINSUP, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Token ringCOLNAME=2 ROTATE="0" MOREROWS="0"ODINSUP, TOKEN, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Token ring SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"ODINSUP, TOKEN, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"IBM pcn2 802.2COLNAME=2 ROTATE="0" MOREROWS="0"PCN2, PCN2L, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"IBM pcn2 snapCOLNAME=2 ROTATE="0" MOREROWS="0"PCN2, PCN2L, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Novell rx-netCOLNAME=2 ROTATE="0" MOREROWS="0"TRXNET, TRXNET2RENDERAS="SECT2"Link Driver OptionThe link driver option in NET.CFG tells the LAN driver which frame types you use. You can only specify frame types supported by that driver.PAGENUM=53 ID="BP60"RENDERAS="SECT3"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver name frame nameReplace name with the name of the frame type.RENDERAS="SECT3"ExampleFor example, to link your NE2000 LAN driver to the Ethernet 802.2 frame type, you would enter into your NET.CFG fileFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000 frame ethernet_802.2RENDERAS="SECT1"ID="FM24486"Matching Network Board and ODI Driver SettingsNetWare ClientTM for OS/2* software expects each network board to use the board's factory default settings. If you have changed the settings on your network board, you must make corresponding changes in the OS/2 Client software. This is done through the NET.CFG.Network boards come with factory IDXID="w11931"BOOK="_idx" COLLECTION="nw41" TIDREF="i2848"
defaults for such hardware settings asMARK=BULLETDirect memory access channel (DMA)IDXID="w11932"BOOK="_idx" COLLECTION="nw41" TIDREF="i1164"Interrupt line (IRQ)IDXID="w11933"BOOK="_idx" COLLECTION="nw41" TIDREF="i1841"Input/output portIDXID="w11934"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"Memory rangeIDXID="w11935"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"Node addressThe NetWare Client for OS/2 software, as shipped, expects each network board to be using the default settings.These factory defaults can usually be changed by moving jumpers, setting switches, or through a configuration utility provided by the manufacturer of the network board.Therefore, if you change the factory default for any of the hardware settings listed above, you must tell the OS/2 ODITM driver the new setting.PAGENUM=54 ID="BP61"To do this, use the link driver option in NET.CFG. The link driver option allows you to configure your software to match to your hardware settings:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver name
   dma [index] 
channel
   int [index]
 irq
   mem [index] 
starting_address [
size]
   node address number
   port [index] 
starting_port [
number]For more on the link driver option and its settings, see IDREF="FM28739""Link Driver" on page 257.RENDERAS="SECT2"Shortcut for Microchannel and EISA LAN DriversIf you are using a Microchannel or EISA network board, you do not need to specify the hardware settings shown above. The LAN driver scans the network board and determines which settings are in use.You must tell NetWare Client for OS/2 the slot number where the network board is located. You can also tell NetWare Client for OS/2 to scan all slots.To define the network board slot, use the "Link Driver" option in NET.CFG.FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver name slot numberReplace number with the slot number or with a question mark if you want to scan all slots. (See IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255.)RENDERAS="SECT1"Cautions with theID="FM88950"Default Frame TypeIn NetWare 2 and 3, Ethernet drivers default to the Ethernet 802.3 frame type. In NetWare 4, they default to the Ethernet 802.2 frame type.NetWare 4 server drivers for Ethernet default to the Ethernet 802.2 frame type. Servers and workstations must use the same frame types to communicate with each other.PAGENUM=55 ID="BP62"Routers must also support the same frame types or packets will not be routed correctly. This will distrupt communications and if your workstation does get a connection, it will likely fail.Some routers on your network might not support the new Ethernet 802.2 frame type.Your workstation will not IDXID="w11936"BOOK="_idx" COLLECTION="nw41" TIDREF="i782"
connect to a network expecting the old default of Ethernet 802.3 if you use the new default of Ethernet 802.2.RENDERAS="SECT1"ID="FM31896"Defining Both Ethernet 802.2 and Ethernet 802.3 Frame TypesYou can define both Ethernet 802.2 and Ethernet 802.3 on your workstation to eliminate conflicts due to default frame type settings.For your workstation, define frame types in NET.CFG. Include a line similar to the following, replacing ne2000 with the name of your ODI driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.3
   frame ethernet_802.2The first frame type defined is the only one used for the initial "Get Nearest Server" request. Therefore, if you have servers using only one frame type, such as Ethernet 802.3, put that frame type first. That way your workstation can make a default connection to those servers.For more about the link driver option, see IDREF="FM50568"Appendix A, "NET.CFG Options Reference," on page 255.RENDERAS="SECT1"ID="FM23495"Using More Than One Network BoardIDXID="w11937"BOOK="_idx" COLLECTION="nw41" TIDREF="i2851"In most cases, NetWare Client for OS/2 can share a network board with other communication packages so you do not need to purchase two network boards.This sections describesMARK=BULLETReasons for having more than one network boardPAGENUM=56 ID="BP63"Setting up two network boardsChoosing a primary network boardRENDERAS="SECT2"Reasons for Having More Than One Network BoardWhen using NetWare Client for OS/2, there are two conditions where you might benefit from having more than one network board in your computer:MARK=BULLETWhen each network board supports a different communications software packageWhen each network board is connected to a physically separate networkIf you have two network boards, be aware of the configuration issues in the following sections. Additional network boards (those after the second defined network board) are ignored.RENDERAS="SECT3"Different Communications Software PackagesYou might want to use multiple network boards when each board is supported by its own communications software package.For example, you might want to have Communications Manager use one network board and NetWare Client for OS/2 use another network board. Or you might want NetWare for OS/2 to use one network board and NetWare Client for OS/2 to use another network board.In these cases, each package provides the driver for its own board. The setup for NetWare Client for OS/2 is same as if only one network board existed. There are no additional steps to set up the second network board under NetWare, since that network board is controlled by the other communications package. It may need to be configured under the other communications package.In most cases, NetWare Client for OS/2 can share a network board with other communication packages, so you do not need to purchase two network boards.PAGENUM=57 ID="BP64"RENDERAS="SECT3"Physically Separate NetworksYou might want to use two network boards with each board being connected to its own network. This makes it possible for a custom application to access both networks at one time.However, a workstation with only NetWare Client for OS/2 cannot serve as a router between the two networks. This means that, although both networks are connected to the same physical machine, there is no communication between the two networks. (The OS/2 workstation can become a router using NetWare for OS/2.) If your two networks are connected through another machine serving as a router, your second network board may serve as a backup route if the connection to your first network board fails. Again, your OS/2 workstation is not routing (unless you use NetWare for OS/2).RENDERAS="SECT3"Using the Second Network Board as a BackupWhen the workstation boots, the IPX protocol binds to all network boards that have OS/2 ODI drivers loaded. Whenever NetWare Client for OS/2 needs to find a new destination on the network, it queries the network for possible routes to that destination.NetWare Client for OS/2 sends out a destination query only on the primary network board. It never queries the secondary (or other) network board for a route. If NetWare Client for OS/2 doesn't find the destination using the primary network board, you see a connection error, even if the destination could be found using the second network board. (However, the network on the second network board can be queried using IPX calls from a custom program.)Once NetWare Client for OS/2 finds a destination using the primary network board, it stores the route to that destination in a router table and makes a connection.After a connection is made, NetWare Client for OS/2 checks all networks connected to that destination for other possible routes from your OS/2 workstation to the destination.PAGENUM=58 ID="BP65"If it finds a secondary route, NetWare Client for OS/2 rebuilds the router tables and stores that route. If the primary connection fails, NetWare Client for OS/2 will use the secondary route to continue transmissions to that destination.If NetWare Client for OS/2 is using a route through the second network board, the primary connection can be broken without causing the secondary connection to fail.However, the secondary network board never becomes the primary board, even if the primary board fails. This means that if NetWare Client for OS/2 needs to find a new destination while the primary connection is down, it can't query for the destination, since queries are only sent on the primary board.To allow NetWare Client for OS/2 to find new destinations, restore the primary connection.RENDERAS="SECT2"ID="FM75291"Setting Up Two IDXID="w11938"BOOK="_idx" COLLECTION="nw41" TIDREF="i2851"
Network BoardsIf you have two network boards in your computer, you may need toMARK=BULLETDefine hardware settings and frame types for each network boardLoad a driver for each boardChoose a primary network boardRENDERAS="SECT3"ID="FM32863"Defining Hardware Settings and Frame Type for Each Network BoardIDXID="w11939"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"If you have more than one network board, you will need to load a separate driver and specify a "Link Driver" section for each network board.For example, if you have an NE2000 board (the primary board) and a token ring network board, you might include these lines in NET.CFG:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   int 5
   port 360
   frame ethernet_802.2
PAGENUM=59 ID="BP66"   frame ethernet_802.3
link driver token
   int 3
   port A20
   mem CC000
   frame token-ring
   frame token-ring_snapRENDERAS="SECT3"ID="FM49403"Loading the IDXID="w11940"BOOK="_idx" COLLECTION="nw41" TIDREF="i3057"
ODI Driver for an Additional Network BoardThe NetWare Client for OS/2 installation program allows you to select an ODI driver. That driver is then autoloaded in CONFIG.SYS, but you might need to load an additional ODI driver manually in the CONFIG.SYS file ifMARK=BULLETYou have two network boards, andThose network boards use different ODI driversIf the network boards use the same ODI driver (for example, two NE2000 LAN drivers), load the driver once when you install NetWare Client for OS/2.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXInstall NetWare Client for OS/2 with one of the ODI drivers.Check to see if the second network board is installed and free from hardware conflicts.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Using a text editor, open CONFIG.SYS.For example, to use the OS/2 System Editor at the OS/2 command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"E C:\CONFIG.SYS MOREINFO="NONE"<Enter>CONFIG.SYS is in the root of your boot drive (in this example, drive C: is the boot drive).
PAGENUM=60 ID="BP67"PERFORMANCE="REQUIRED"In NetWare Client for OS/2 lines, find the line loading the first ODI driver.PERFORMANCE="REQUIRED"Decide which driver you want IPX to recognize as primary.The driver for the primary network board is the only driver IPX uses to query the network for a route. The driver for the secondary network board is never queried.PERFORMANCE="REQUIRED"Type a new line to load an additional driver.To load a driver as primary, type the line above the existing driver line. To load a driver as secondary, type the line below the existing line.The first driver loaded in CONFIG.SYS is the primary driver.Type the path to the driver in the line. If you use a Novell-supplied driver, the driver is located in the directory where you installed the NetWare Client for OS/2 files, usually in C:\NETWARE.For example, to load an NE2000 driver from the default location, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\NE2000.SYSIf you have two network boards using the same driver name (such as two NE2000 LAN drivers), do not load the driver twice.PERFORMANCE="REQUIRED"Save and exit the CONFIG.SYS file.PERFORMANCE="REQUIRED"Edit NET.CFG to reflect the changes.PERFORMANCE="REQUIRED"Use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to reboot your machine in order to load the additional drivers.RENDERAS="SECT2"ID="FM69403"Choosing a Primary Network BoardIDXID="w11941"BOOK="_idx" COLLECTION="nw41" TIDREF="i2850"IDXID="w11942"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"The network board whose driver loads first in CONFIG.SYS is the primary network board. You can change which network board is primary byMARK=BULLETReordering drivers in CONFIG.SYS.Using a NET.CFG option to bind IPX to a different driver.To change which network board IPX views as primary, use the "Protocol Stack IPX" option in NET.CFG:PAGENUM=61 ID="BP68"FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol stack IDXID="w11943"BOOK="_idx" COLLECTION="nw41" TIDREF="i3604"
ipx
   bind 
drivernameReplace drivername with the name of the driver that controls the network board, and indent the "bind" setting. For example, to set a token ring network board as primary, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"protocol stack ipx
   bind tokenRENDERAS="SECT3"Switching the Network Board in Use on Unconnected NetworksIf you have two network boards and each is connected to a physically separate network, you might want toMARK=BULLETChange which board is primary in NET.CFG and reboot when you want to access the other network.Get a network switch box that allows you to change between physically separate networks.Connect the networks with a router.RENDERAS="SECT3"Specifying Primary with Two Network Boards of the Same IDXID="w11944"BOOK="_idx" COLLECTION="nw41" TIDREF="i2851"
TypeIf you have two network boards using the same type of ODI driver (such as two NE2000 LAN drivers), do not load the same driver twice in CONFIG.SYS and do not specify a "Protocol Stack IPX" option.Instead, use the "Link Driver" option in NET.CFG to specify that the driver is used twice. Do this by placing two "Link Driver" sections in NET.CFG, each one specifying the driver name and hardware settings used by that network board.The hardware settings for at least one of the network boards must be specified, since you cannot have two network boards of the same type both using default hardware settings.For example, if you have two NE2000 LAN drivers, you might include the following lines in NET.CFG:PAGENUM=62 ID="BP69"FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.2
   frame ethernet_802.3
   int 5
   port 360FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.2
   frame ethernet_802.3
   int 4
   port 320Putting two occurrences of "link driver ne2000" loads the NE2000 driver twice. If you do not specify two "Link Driver" sections, a driver will not be loaded for the second board, and the second network board will be ignored.With two network boards of the same type, the network board whose line comes first in NET.CFG is the one IPX uses as primary.RENDERAS="SECT3"Shortcut for Multiple Microchannel and EISA LAN DriversIf you use two Microchannel or EISA network boards that use the same driver (such as two NE3200TM or two 3C523), you still must specify a "Link Driver" section for each network board.However, instead of specifying the hardware settings used on the network board, you can specify the "slot" setting.The "slot" setting tells the LAN driver the slot where the network board is located. The driver then scans the network board and determines which hardware settings are in use.For example, for two NE3200 LAN drivers, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
  frame ethernet_802.3
  frame ethernet_802.2
  slot 2
PAGENUM=63 ID="BP70"FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
  frame ethernet_802.3
  frame ethernet_802.2
  slot 1In this example, the network board in slot 2 becomes the primary network board because the driver for it was loaded first.To change which network board is primary, reorder the "Link Driver" sections. For example, to set the network board in slot 1 as primary, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
  frame ethernet_802.3
  frame ethernet_802.2
  slot 1FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
  frame ethernet_802.3
  frame ethernet_802.2
  slot 2LABEL="6"PAGENUM=65 ID="BP71"ID="FM46753"Logging In to Your NetworkCOLS=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="FM30602"Setting Up Workstations to Log In COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM30602"65COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83119"Understanding Logging In to NetWare Directory Services (NDS)  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83119"66COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM27089"Logging In from the OS/2 Command Line  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27089"68COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94947"Logging In to NetWare 2 and 3 Bindery Servers Using NDS Utilities COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94947"69COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55033"Accessing Your Network Using NetWare Tools COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55033"69COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM95233"Modifying NET.CFG to Log In to NetWare 2 or 3  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM95233"71COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM73206"Network Login WindowCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM73206"72RENDERAS="SECT1"ID="FM30602"Setting Up Workstations to Log InOS/2* supports a variety of operating system platforms referred to as IDXID="w11945"BOOK="_idx" COLLECTION="nw41" TIDREF="i4088"
sessions. This chapter will help you with the kind of login that works best with the platform you use.Proper workstation setup can make logging in to a bindery and NetWare Directory ServicesTM network virtually transparent.This chapter assumes the following tasks are completed:MARK=CHECKBOXNetWare ClientTM for OS/2 is installed and running on your workstationYour workstation NET.CFG file has been modified for loginPAGENUM=66 ID="BP72"A User object or user account is created for each userA home directory is created for each userWith the necessary modifications made to your NET.CFG file, you need only your username and password to log in.RENDERAS="SECT1"IDXID="w11946"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"ID="FM83119"ID="FM22567"Understanding Logging In to NetWare Directory Services (NDS)NetWare Directory Services (NDS), used in NetWare 4, makes logging in convenient, because you log in to the network, rather than logging in to a server. User information resides in a global database. Each User object is assigned a position, or context, within the database that informs the network where your workstation is in relationship to the network. This IDXID="w11947"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
context is referred to as your name context.When you log in, the LOGIN utility must know your context, or where your particular User object is located. The User object's context forms its IDXID="w11948"BOOK="_idx" COLLECTION="nw41" TIDREF="i717"complete name. The path from the object to the root of the tree forms the object's complete name, which is unique among object names.Your User object's complete name is a bottom-up traversal of the tree, from the object up to the root.RENDERAS="SECT2"Using Your Complete Name for Logging InWhen you use the complete name of a User object, specify the common name first, followed by a period (.).Then specify the container object, also followed by a period, and so on, up through the Organization object name (and the Country object name, if used). So, depending on the way your network is defined, your User object's complete name might be represented byPAGENUM=67 ID="BP73"FORMAT="LINESPECIFIC"MOREINFO="NONE"COMMON NAME.ORGANIZATIONAL UNIT NAME. ORGANIZATION NAME.COUNTRY NAMERENDERAS="SECT2"Specifying the Name Type of an ObjectIDXID="w11949"BOOK="_idx" COLLECTION="nw41" TIDREF="i2590"
At times, such as when you move from one Container object to another, you must include the name type of the object when typing out the complete name of the object. A name type distinguishes the class of object to you are referring to, such as a User object or an Organizational Unit object.For example, you could expressFORMAT="LINESPECIFIC"MOREINFO="NONE"ESAYERS.SALES PV.SALES.NOVELL US as the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"CN=ESAYERS.OU=SALES PV.OU=SALES.O=NOVELL USwhere CN is the common name of the User object, OU is the Organizational Unit name, and O is the Organization name.IDXID="w11950"BOOK="_idx" COLLECTION="nw41" TIDREF="i2580"
If you refer to an IDXID="w11951"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
object that is in the same Container object as your User object, refer to that object only by its common name instead of its complete name.When you include the Country object in your Directory tree, you must always include the name type of the object (CN or OU or O) in the complete name, even when referring to objects located in the same Container object.RENDERAS="SECT2"IDXID="w11952"BOOK="_idx" COLLECTION="nw41" TIDREF="i908"Changing Your ContextYou might need to change your context to simplify your login or your reference to other objects in your Directory tree. Two ways to change your context areMARK=BULLETUsing IDXID="w11953"BOOK="_idx" COLLECTION="nw41" TIDREF="i892"
CX.EXE, included with NetWare Client for OS/2.Using the "name context" command in NET.CFG. (See IDREF="FM10812""name context" on page 288.)PAGENUM=68 ID="BP74"RENDERAS="SECT1"ID="FM27089"Logging In from the OS/2 Command LineIDXID="w11954"BOOK="_idx" COLLECTION="nw41" TIDREF="i1515"
The IDXID="w11955"BOOK="_idx" COLLECTION="nw41" TIDREF="i963"
default login drive is drive L:, unless it has been changed in your NET.CFG file.NetWare Client for OS/2 maps drive L: as the default login drive, mapped to SYS:LOGIN. However, you should log in from your NetWare workstation directory (default: C:\NETWARE). LOGIN connects your workstation to the network.RENDERAS="SECT2"IDXID="w11956"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"IDXID="w11957"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
Logging In to NetWare Directory ServicesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open an CLASS=MENUITEM MOREINFO="NONE"OS/2 Full Screen or an CLASS=MENUITEM MOREINFO="NONE"OS/2 Window.A prompt similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"[C:\]PERFORMANCE="REQUIRED"Log in using one of the following ways:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To log in using your username only, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"login username MOREINFO="NONE"<Enter>For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"login esayers MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"To log in to a specific server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"login servername\username MOREINFO="NONE"<Enter>For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"login tsmkt\esayers MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"If required, type your password.
PAGENUM=69 ID="BP75"RENDERAS="SECT1"ID="FM94947"Logging In to NetWare 2 and 3 Bindery Servers Using NDS UtilitiesThe default login drive is drive L:, unless it has been changed in your NET.CFG file.RENDERAS="SECT2"IDXID="w11958"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
ProcedurePERFORMANCE="REQUIRED"TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"login server/username /b MOREINFO="NONE"<Enter>Replace
 server with the name of the bindery server. Replace 
username with your username. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"F:\login tsmkt/esayers /b MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"If required, type your password.RENDERAS="SECT1"ID="FM55033"Accessing Your Network Using NetWare ToolsIDXID="w11959"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
Use NetWare ToolsTMIDXID="w11960"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
 on the desktop to attach to NetWare Directory Services or bindery-based servers.The attachment from IDXID="w11961"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
NetWare Tools does not run a login script. To execute a login script, run LOGIN from the command line.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon on your OS/2 desktop window.The 
CLASS=MENUITEM MOREINFO="NONE"Novell-Icon View window appears.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Novell-Icon View on your desktop, choose 
CLASS=MENUITEM MOREINFO="NONE"NetWare Tools.The 
CLASS=MENUITEM MOREINFO="NONE"NetWare Tools window appears.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Tools option.A menu box appears.PERFORMANCE="REQUIRED"From the menu list, select 
CLASS=MENUITEM MOREINFO="NONE"Tree.
PAGENUM=70 ID="BP76"The 
CLASS=MENUITEM MOREINFO="NONE"Directory Tree window appears.PERFORMANCE="REQUIRED"From the menu bar, choose 
CLASS=MENUITEM MOREINFO="NONE"Tree.A menu box appears.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Login.The following dialog appears.LABEL="6-1" FLOAT="0"Login to Directory Tree WindowFILEREF="c41q26a.tif"PERFORMANCE="REQUIRED"Log in.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"To log in to a NetWare 4 Directory tree (using NDS), select 
CLASS=MENUITEM MOREINFO="NONE"Tree.PERFORMANCE="REQUIRED"To log in to a NetWare 2, 3, or 4 server (using bindery services), select 
CLASS=MENUITEM MOREINFO="NONE"Server.PERFORMANCE="REQUIRED"Enter your username and password.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Login.If the login is unsuccessful, check your context and try again.For more information about this Tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.The NetWare Tools CLASS=MENUITEM MOREINFO="NONE"Login option doesn't run a login script. To run a login script, log in at the command line using LOGIN. To maintain your NetWare Tools connections, from the CLASS=MENUITEM MOREINFO="NONE"Network menu box, use CLASS=MENUITEM MOREINFO="NONE"Save Settings.PAGENUM=71 ID="BP77"RENDERAS="SECT1"ID="FM95233"Modifying NET.CFG to Log In to NetWare 2 or 3IDXID="w11962"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"
When logging in to NetWare 2 or 3, you attach to a server and then connect to other servers you have a user account on.RENDERAS="SECT2"IDXID="w11963"BOOK="_idx" COLLECTION="nw41" TIDREF="i3372"ID="FM99068"Using the Preferred Server SettingTo direct NetWare Client for OS/2 to the server your user information is saved on, use the "preferred server" setting in IDXID="w11964"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"
NET.CFG.For networks with multiple servers, this speeds up your network login and allows you to log in using only your username.RENDERAS="SECT2"ID="FM20828"Adding the Preferred Server Setting to NET.CFG for OS/2 RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Using a text editor, open your NET.CFG file.Your workstation's NET.CFG file was copied to the target directory for OS/2 files specified during the NetWare Client for OS/2 installation. PERFORMANCE="REQUIRED"Under the "NetWare Requester" option, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred server servernameFor example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred server mktsalesRENDERAS="SECT1"Modifying NET.CFG to Log In to NetWare 4IDXID="w11965"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"
When logging in to NetWare 4, you don't attach to servers (as with previous versions of NetWare), you log in to the network.Using your IDXID="w11966"BOOK="_idx" COLLECTION="nw41" TIDREF="i717"
complete name, you can simplify the login process by adding information to your workstation's IDXID="w11967"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"
NET.CFG file. You add lines to the "NetWare Requester" option.IDXID="w11968"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
If you add lines for the following settings, you don't need to type your complete name each time you log in. The settings arePAGENUM=72 ID="BP78"MARK=BULLETname contextpreferred treeYou must know your context before making these modifications. Without knowing the context, you can't add entries for the settings.RENDERAS="SECT2"ID="FM48848"Using the Name Context SettingIDXID="w11969"BOOK="_idx" COLLECTION="nw41" TIDREF="i2578"
To inform NetWare Client for OS/2 of your name context, use the "name context" setting in NET.CFG. LOGIN can then locate your User object and connect you to the network. If you are using NetWare 4, add this setting to NET.CFG. The setting is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
   name context 
"context"RENDERAS="SECT2"IDXID="w11970"BOOK="_idx" COLLECTION="nw41" TIDREF="i3375"ID="FM55326"Using the Preferred Tree SettingTo direct NetWare Client for OS/2 to the Directory tree where your name context is set, use the "preferred tree" setting in IDXID="w11971"BOOK="_idx" COLLECTION="nw41" TIDREF="i2908"
NET.CFG. LOGIN can then search only the preferred Directory tree.If you are using NetWare 4 on a network with multiple Directory trees, add this setting to your NET.CFG file. The setting is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
   preferred tree 
treenameThe default is set to the root, so if duplicate usernames exist within separate Directory trees, the "preferred tree" setting avoids confusion.Don't use both "preferred server" and "preferred tree" simultaneously. The second setting overrides the first.RENDERAS="SECT1"ID="FM73206"Network Login WindowIDXID="w11972"BOOK="_idx" COLLECTION="nw41" TIDREF="i376"PAGENUM=73 ID="BP79"When booting OS/2 2.1, a pop-up network login window sometimes displays, because OS/2 can restart PROGRAMS, TASKLIST, FOLDERS, and CONNECTIONS automatically by using the SET AUTOSTART variable in CONFIG.SYS.For example, if the following line is in CONFIG.SYS,FORMAT="LINESPECIFIC"MOREINFO="NONE"SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS, CONNECTIONSthen the pop-up login window displays.In a NetWare environment, it is best not to include the SET AUTOSTART=CONNECTIONS line in CONFIG.SYS. The recommended syntax isFORMAT="LINESPECIFIC"MOREINFO="NONE"SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERSUse the OS/2 version of LOGIN or NetWare Tools to log in because these utilities allow you to automatically set up your NetWare environment (map drives and capture ports) and the pop-up login window does not.The OS/2 version of LOGIN will run OS/2 login scripts (system and/or user login scripts) and NetWare Tools allows you to create and load file settings that function similar to login scripts.LABEL="7"PAGENUM=75 ID="BP80"Using NetWare ToolsCOLS=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="FM63779"Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM63779"75COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM15780"Prerequisites COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15780"75COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM54575"Accessing NetWare Tools COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46779"77COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM46779"Using the Menu Bar  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46779"77COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM70122"The Network Menu Option COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM70122"77COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29497"The Tools Menu Option COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29497"78COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86268"Window Menu  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23271"88COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM23271"Help Menu  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23271"88COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM65889"Exiting NetWare Tools COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM65889"88RENDERAS="SECT1"ID="FM63779"OverviewIDXID="w11973"BOOK="_idx" COLLECTION="nw41" TIDREF="i2809"IDXID="w11974"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
ID="FM64499"NetWare ToolsTM software provides you with a graphical way of accessing network resources, such as volumes, directories, printers, and users.NetWare Tools allow you to perform tasks such as managing drive mappings, managing printer connections and setup, managing the Directory tree, managing server connections, displaying network users, and sending messages.RENDERAS="SECT1"ID="FM15780"PrerequisitesIDXID="w11975"BOOK="_idx" COLLECTION="nw41" TIDREF="i2809"
Before you can use NetWare Tools, your workstation requires the following:PAGENUM=76 ID="BP81"MARK=CHECKBOXA physical connection to the network.OS/2* 2.x loaded and running.NetWare ClientTM for OS/2 files loaded and running (Files are loaded by the OS/2 CONFIG.SYS file during bootup.)RENDERAS="SECT1"ID="FM54575"Accessing NetWare ToolsRENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon on your OS/2 desktop.If the 
CLASS=MENUITEM MOREINFO="NONE"Novell icon is not displayed, press your right mouse button to show the system menu.If the 
CLASS=MENUITEM MOREINFO="NONE"Novell folder is still not on your desktop, open an OS/2 full screen or OS/2 window, change to the directory containing NetWare Client for OS/2 files (usually C:\NETWARE), and type 
MOREINFO="NONE"NWTOOLS. This loads the NetWare Tools software.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window on your desktop, choose 
CLASS=MENUITEM MOREINFO="NONE"NetWare Tools.
PAGENUM=77 ID="BP82"LABEL="7-1" FLOAT="0"Opening NetWare Tools for OS/2FILEREF="c41q06a.tif"For easier access to the network, you might want to keep the CLASS=MENUITEM MOREINFO="NONE"NetWare Tools window on your desktop.RENDERAS="SECT2"ID="FM46779"Using the Menu BarIDXID="w11976"BOOK="_idx" COLLECTION="nw41" TIDREF="i2809"
To complete a task, choose the menu option that corresponds with the task you are performing.RENDERAS="SECT3"ID="FM70122"The Network Menu OptionUse the CLASS=MENUITEM MOREINFO="NONE"Network menu to modify, save, and reload your workstation network settings. A window appears for each option.Choosing the CLASS=MENUITEM MOREINFO="NONE"New Settings option disconnects all server connections. Make sure that open files and applications are closed.For more information about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.PAGENUM=78 ID="BP83"LABEL="7-2" FLOAT="0"Network Menu OptionsFILEREF="c41q33a.tif"RENDERAS="SECT3"ID="FM29497"The Tools Menu OptionUse the CLASS=MENUITEM MOREINFO="NONE"Tools menu to use access the following options:TYPE="VERT"Disk drivesPrinter portsServersDirectory treeUser listsPrint queuesFor easier access, leave open the tools you commonly use. The CLASS=MENUITEM MOREINFO="NONE"Window option allows you to arrange the CLASS=MENUITEM MOREINFO="NONE"Tools window display for cascade or tile viewing.The menu bar refreshes itself according to the CLASS=MENUITEM MOREINFO="NONE"NetWare Tools window you have activated.RENDERAS="SECT3"The Disk Drives OptionIDXID="w11977"BOOK="_idx" COLLECTION="nw41" TIDREF="i1221"IDXID="w11978"BOOK="_idx" COLLECTION="nw41" TIDREF="i2318"
Use the CLASS=MENUITEM MOREINFO="NONE"Disk Drives option to map network resources in the Directory tree and file system to your workstation drives. Choose the drive letter for the drive you want to map.When using the CLASS=MENUITEM MOREINFO="NONE"Drives option, remember the following:PAGENUM=79 ID="BP84"MARK=BULLETTo see available volumes, you must be logged in to a Directory tree or to a server. If you can't see an object, use CLASS=MENUITEM MOREINFO="NONE"Attach to make sure you're attached to the appropriate server.The CLASS=MENUITEM MOREINFO="NONE"Attach feature only allows you to make a bindery connection. To make an NDS connection, use the CLASS=MENUITEM MOREINFO="NONE"Tree option.NetWare Tools recognizes all drive mappings made at the command line.LABEL="7-3" FLOAT="0"Disk Drives Menu OptionsFILEREF="c41q05a.tif"RENDERAS="SECT4"The Map WindowFrom the CLASS=MENUITEM MOREINFO="NONE"Map window, select the resource you want to connect to in the CLASS=MENUITEM MOREINFO="NONE"Volume and CLASS=MENUITEM MOREINFO="NONE"Directory lists, then choose the CLASS=MENUITEM MOREINFO="NONE"Map button at the bottom of the window. Keyboard entry is done within the CLASS=MENUITEM MOREINFO="NONE"Path field.PAGENUM=80 ID="BP85"LABEL="7-4" FLOAT="0"ID="FM38675"Map DialogFILEREF="c41q32a.tif"For more information about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.RENDERAS="SECT4"Volume and Directory ListsTheCLASS=MENUITEM MOREINFO="NONE" Volume and CLASS=MENUITEM MOREINFO="NONE"Directories lists within the CLASS=MENUITEM MOREINFO="NONE"Map window are listed in a hierarchical structure. Choose the CLASS=MENUITEM MOREINFO="NONE"Volume icon to display subdirectories.If you have an NDS connection, you can use CLASS=MENUITEM MOREINFO="NONE"Browse to view objects in other contexts. CLASS=MENUITEM MOREINFO="NONE"Browse does not support viewing for bindery connections.If the volume or directory you want to map does not appear in the CLASS=MENUITEM MOREINFO="NONE"Volume or CLASS=MENUITEM MOREINFO="NONE"Directory list, check to see if you are first attached to the server containing this resource. From the CLASS=MENUITEM MOREINFO="NONE"Tools option, choose CLASS=MENUITEM MOREINFO="NONE"Server to see connected servers.RENDERAS="SECT3"Printer Ports OptionIDXID="w11979"BOOK="_idx" COLLECTION="nw41" TIDREF="i3542"
Use the CLASS=MENUITEM MOREINFO="NONE"Printer Ports option to capture network print queues to your workstation printing ports. Choose the printer port you want to capture.When using the CLASS=MENUITEM MOREINFO="NONE"Printer Ports option, remember the following:PAGENUM=81 ID="BP86"MARK=BULLETYou must be logged in to a Directory tree or to a server to see the available volumes. If you can't see a printer object, use CLASS=MENUITEM MOREINFO="NONE"Attach to make sure that you're attached to the appropriate server.The CLASS=MENUITEM MOREINFO="NONE"Attach feature only allows you to make a bindery connection. To make an NDS connection, use the CLASS=MENUITEM MOREINFO="NONE"Tree option.NetWare Tools recognizes all print queue captures made at the command line. If you have an NDS connection, you can use the CLASS=MENUITEM MOREINFO="NONE"Browse feature to view objects in other contexts. The Browse feature does not support viewing for bindery connections.LABEL="7-5" FLOAT="0"Printer Ports Menu OptionsFILEREF="c41q14a.tif"RENDERAS="SECT4"The Capture WindowFrom the CLASS=MENUITEM MOREINFO="NONE"Capture window, select the resource you want to capture in the CLASS=MENUITEM MOREINFO="NONE"Printer/Queue list, then choose CLASS=MENUITEM MOREINFO="NONE"Capture at the bottom of the window. Keyboard entry is done within the CLASS=MENUITEM MOREINFO="NONE"Queue field.Before choosing the CLASS=MENUITEM MOREINFO="NONE"Capture option, highlight the port you want to capture a print queue to.PAGENUM=82 ID="BP87"Before choosing the CLASS=MENUITEM MOREINFO="NONE"View Queue option, you must also highlight the port and print queue name you want to view.LABEL="7-6" FLOAT="0"Capture DialogFILEREF="c41q27a.tif"RENDERAS="SECT4"Setting Printer OptionsIDXID="w11980"BOOK="_idx" COLLECTION="nw41" TIDREF="i3542"
Use the CLASS=MENUITEM MOREINFO="NONE"Printer Options section to assign the following settings:LABEL="7-1" PGWIDE=0 TOCENTRY="1" Printer OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Printer optionCOLNAME=2 ROTATE="0" MOREROWS="0"This functionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11981"BOOK="_idx" COLLECTION="nw41" TIDREF="i2988"
NotifyCOLNAME=2 ROTATE="0" MOREROWS="0"Confirms print job completionCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11982"BOOK="_idx" COLLECTION="nw41" TIDREF="i1553"
FormfeedCOLNAME=2 ROTATE="0" MOREROWS="0"Places a page break between print jobsCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11983"BOOK="_idx" COLLECTION="nw41" TIDREF="i838"
CopiesCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of copies to printCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11984"BOOK="_idx" COLLECTION="nw41" TIDREF="i4419"
Tabs SizeCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of characters in a tab stopCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11985"BOOK="_idx" COLLECTION="nw41" TIDREF="i1459"
File ContentsCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the type of print file being printedCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11986"BOOK="_idx" COLLECTION="nw41" TIDREF="i3391"
Print BannerCOLNAME=2 ROTATE="0" MOREROWS="0"Allows for a banner page to be printed at the front of your print jobCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=MENUITEM MOREINFO="NONE"IDXID="w11987"BOOK="_idx" COLLECTION="nw41" TIDREF="i1558"
FormCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to select a defined print formPAGENUM=83 ID="BP88"For more information about each option, choose CLASS=MENUITEM MOREINFO="NONE"Help.RENDERAS="SECT2"Servers OptionIDXID="w11988"BOOK="_idx" COLLECTION="nw41" TIDREF="i790"IDXID="w11989"BOOK="_idx" COLLECTION="nw41" TIDREF="i2318"
This tool is used only for bindery-based servers (NetWare 2 and 3).Use the CLASS=MENUITEM MOREINFO="NONE"Servers option toMARK=BULLETDisplay NDS server objectsDisplay bindery-based serversAttach to bindery-based serversChange passwordWhen using the CLASS=MENUITEM MOREINFO="NONE"Servers option, remember the following:MARK=BULLETThis tool is used with bindery-based NetWare 2 and 3 networks to attach to network servers.The CLASS=MENUITEM MOREINFO="NONE"Attach option does not run a login script for your workstation. Use the CLASS=MENUITEM MOREINFO="NONE"Save Settings option in the CLASS=MENUITEM MOREINFO="NONE"Network menu box to maintain your connections.To run the login script, use the LOGIN utility at the command line.Choosing the CLASS=MENUITEM MOREINFO="NONE"Servers option from the main menu causes a menu to appear.PAGENUM=84 ID="BP89"LABEL="7-7" FLOAT="0"Servers MenuFILEREF="c41q16a.tif"To attach to another server, choose the CLASS=MENUITEM MOREINFO="NONE"Attach option. The CLASS=MENUITEM MOREINFO="NONE"Attach To Server dialog appears.LABEL="7-8" FLOAT="0"Attach To Server DialogFILEREF="c41q31a.tif"RENDERAS="SECT3"Directory Tree OptionThis tool is used only for NDS servers (NetWare 4).IDXID="w11990"BOOK="_idx" COLLECTION="nw41" TIDREF="i790"IDXID="w11991"BOOK="_idx" COLLECTION="nw41" TIDREF="i2318"
Use the CLASS=MENUITEM MOREINFO="NONE"Directory tree option toTYPE="VERT"Display resourcesChange Directory treesPAGENUM=85 ID="BP90"Change context 
IDXID="w11992"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
within the networkLog in to the networkIDXID="w11993"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
Change passwordsMap network drivesCapture portsWhen using the CLASS=MENUITEM MOREINFO="NONE"Directory tree option, remember the following:MARK=BULLETThis tool is only used with NetWare 4 networks. For NetWare 2 and 3 networks, use the CLASS=MENUITEM MOREINFO="NONE"Servers option to attach to NetWare servers.The CLASS=MENUITEM MOREINFO="NONE"Login option does not run a login script for your workstation. From the CLASS=MENUITEM MOREINFO="NONE"Network menu, use the CLASS=MENUITEM MOREINFO="NONE"Save Settings option to maintain your connections.To run the login script, log in at the command line using the LOGIN utility. (See IDREF="FM46753"Chapter 6, "Logging In to Your Network," on page 65.)You can only be authenticated to one Directory tree at a timeChoosing the CLASS=MENUITEM MOREINFO="NONE"Directory tree option from the main menu bar causes a menu box to appear.LABEL="7-9" FLOAT="0"Tree Menu OptionsFILEREF="c41q03a.tif"PAGENUM=86 ID="BP91"From the CLASS=MENUITEM MOREINFO="NONE"Tree menu, choose the CLASS=MENUITEM MOREINFO="NONE"Login option to login to another Directory tree. The CLASS=MENUITEM MOREINFO="NONE"Login to Directory Tree dialog appears.LABEL="7-10" FLOAT="0"Login to Directory Tree DialogFILEREF="c41q26a.tif"For more information about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.RENDERAS="SECT3"User Lists OptionUse the CLASS=MENUITEM MOREINFO="NONE"Users dialog to display network users or groups and send a message to them. Select the resource you want to send a message to from the CLASS=MENUITEM MOREINFO="NONE"User list.The CLASS=MENUITEM MOREINFO="NONE"User List appears only if you are attached to a network.PAGENUM=87 ID="BP92"LABEL="7-11" FLOAT="0"Users Menu OptionsFILEREF="c41q19a.tif"From the CLASS=MENUITEM MOREINFO="NONE"Users menu, select CLASS=MENUITEM MOREINFO="NONE"Send Message. Type your message in the CLASS=MENUITEM MOREINFO="NONE"Messages field, then choose the CLASS=MENUITEM MOREINFO="NONE"Send button at the bottom of the dialog.LABEL="7-12" FLOAT="0"Send A Message DialogFILEREF="c41q12a.tif"Before choosing the CLASS=MENUITEM MOREINFO="NONE"Send Message option, highlight the users you want to send a message to.If the user you want to send messages to doesn't appear in the CLASS=MENUITEM MOREINFO="NONE"Users list, select the server the user is on, then choose CLASS=MENUITEM MOREINFO="NONE"Users list again.When using the CLASS=MENUITEM MOREINFO="NONE"Send A Message dialog, remember that you must first log in to a Directory tree or to a server that contains the object you want to send a message to.For more information about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.PAGENUM=88 ID="BP93"RENDERAS="SECT3"Print Queues OptionThe CLASS=MENUITEM MOREINFO="NONE"Print Queues option displays a window that contains the following:MARK=BULLETPrinter objectsPrint queue objectsIf the print queue you want to capture does not appear in the CLASS=MENUITEM MOREINFO="NONE"Queue list, check to see if you are attached to the server containing this resource. For a list of connected servers, under the CLASS=MENUITEM MOREINFO="NONE"Tools option, choose CLASS=MENUITEM MOREINFO="NONE"Server.For more information about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.RENDERAS="SECT2"ID="FM33292"ID="FM86268"Window MenuUse the CLASS=MENUITEM MOREINFO="NONE"Window menu to arrange the windows on the screen and switch between views.RENDERAS="SECT2"ID="FM23271"Help MenuUse the CLASS=MENUITEM MOREINFO="NONE"Help menu to access the online help. (You can also press MOREINFO="NONE"<F1> for help.) Use the CLASS=MENUITEM MOREINFO="NONE"Contents option to see a list of commands, keyboard instructions, and a comprehensive task list.RENDERAS="SECT1"ID="FM65889"Exiting NetWare ToolsRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Exit option within the CLASS=MENUITEM MOREINFO="NONE"Network menu, or press MOREINFO="NONE"<Alt><F4>.PERFORMANCE="REQUIRED"(Optional) If you want NetWare Tools to maintain the same window arrangement the next time you run the program, choose 
CLASS=MENUITEM MOREINFO="NONE"Save Window Positions.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Exit.
PAGENUM=89 ID="BP94"LABEL="7-13" FLOAT="0"Exit NetWare Tools DialogFILEREF="c41q29a.tif"LABEL="8"PAGENUM=91 ID="BP95"Using Virtual DOS and WindowsCOLS=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="FM89534"Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM89534"91COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM39661"Information for All Types of Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39661"93COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM18207"Logging In from an OS/2 Virtual DOS Session  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18207"94COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM35532"Customizing Icons For Global Support  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM35532"96COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM36228"Setting Up Drive Mappings in Global Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM36228"100COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM60865"Customizing Icons For Private Support COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM60865"102COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM24573"Special Instructions for Win-OS2 Icons COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24573"106COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM47202"Special Instructions for DOS_STARTUP_DRIVE Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47202"108COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM67637"Disabling Network Support in All Virtual Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67637"110COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM21725"Setting Up Named Pipes for Virtual DOS and MS Windows COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM21725"111COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62792"Setting Up NetBIOS for Virtual DOS and MS Windows  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62792"113RENDERAS="SECT1"ID="FM89534"OverviewFrom a virtual DOS or MS Windows session, you can have three kinds of NetWare® support:MARK=BULLETGlobal logins.IDXID="w11994"BOOK="_idx" COLLECTION="nw41" TIDREF="i1606"IDXID="w11995"BOOK="_idx" COLLECTION="nw41" TIDREF="i3556"All DOS, MS Windows, and OS/2* sessions that are set up for global login support share a single login to a NetWare server. Drives that are mapped in one session apply to the other sessions. This is useful in environments where the number of connections is carefully monitored. PAGENUM=92 ID="BP96"Private logins.All DOS and MS Windows sessions that are set up for private login support have their own logins to a NetWare server. Drive mappings and port captures from one session do not apply to the other sessions. This is useful in environments where users need more than one connection to a server and where users need logins from DOS or MS Windows sessions to be separate from logins from OS/2 sessions. No logins.Sessions with network support disabled have IPXTM/SPXTM support, but no NetWare login support.RENDERAS="SECT2"Setting Up NetWare Support for Virtual DOS and MS WindowsSet up NetWare support for virtual DOS and MS Windows in two ways:MARK=BULLETSet a default type of support (global, private, or none) that applies to DOS and MS Windows icons, as well as any new icons that are created. If you choose this default in the NetWare ClientTM for OS/2 installation program, it is loaded in the CONFIG.SYS file. To change the default support,MARK=BULLETRun the NetWare Client for OS/2 installation programUnder the CLASS=MENUITEM MOREINFO="NONE"Installation menu, choose CLASS=MENUITEM MOREINFO="NONE"Requester on workstation...Select the appropriate target directory and choose CLASS=MENUITEM MOREINFO="NONE"OK.Under the CLASS=MENUITEM MOREINFO="NONE"Requester Installation window, select CLASS=MENUITEM MOREINFO="NONE"Only Edit CONFIG.SYS... and choose CLASS=MENUITEM MOREINFO="NONE"OK.Under CLASS=MENUITEM MOREINFO="NONE"Choose ODI LAN driver, choose CLASS=MENUITEM MOREINFO="NONE"Continue unless changes have been made in your LAN driver configuration.Under CLASS=MENUITEM MOREINFO="NONE"Choose NetWare Support for DOS and Windows Applications, select the default support. Choose CLASS=MENUITEM MOREINFO="NONE"Continue.Continue installation. See IDREF="FM87895" Chapter 3, "Installing NetWare Client for OS/2," on page 21.PAGENUM=93 ID="BP97"Customize the type of support for each DOS and MS Windows icon on your desktop. All sessions started from the customized icon have the type of support you specify. For instructions on customizing NetWare support per icon, see the sections that follow.To set up icons with different kinds of network support, label the icons for those sessions something that indicates the type of support. For example, you might want to create CLASS=MENUITEM MOREINFO="NONE"Global DOS Full Screen and CLASS=MENUITEM MOREINFO="NONE"Private DOS Full Screen icons. RENDERAS="SECT1"ID="FM39661"Information for All Types of SessionsRENDERAS="SECT2"NetWare 3 and 4 SupportFrom a virtual DOS or MS Windows session, you can access NetWare 3 (bindery-based) networks. On these networks, you can receive full NetWare support just as if you were using an actual DOS or MS Windows workstation. You can also receive support for just the IPXTM, SPXTM, Named Pipes and NetBIOS protocols. You cannot access NetWare 4 networks from virtual DOS and MS Windows sessions unless those networks support bindery emulation. If a NetWare 4 network supports bindery emulation, your DOS or MS Windows session will be seen as a bindery-based client. RENDERAS="SECT2"IDXID="w11996"BOOK="_idx" COLLECTION="nw41" TIDREF="i4773"
Accessing the Correct Version of DOSFor all virtual sessions you start, the COMSPECIDXID="w11997"BOOK="_idx" COLLECTION="nw41" TIDREF="i734"
 variable must point to the correct version of DOS. If you use the version of DOS included with OS/2, set the COMSPEC variable to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET COMSPEC=drive:\OS2\MDOS\COMMAND.COMYou can set the COMSPEC variable at the command line, in a login script, or through CLASS=MENUITEM MOREINFO="NONE"DOS Settings from the OS/2 desktop.PAGENUM=94 ID="BP98"Replace drive: with the letter of your boot drive. If you are running another version of DOS, the COMSPEC variable should point to the location of the COMMAND.COM file for that version.NetWare login scriptsIDXID="w11998"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
 often contain a statement assigning COMSPEC to a network drive, so be sure to check---and if necessary, reset---the COMSPEC variable in your login script.RENDERAS="SECT2"Login IssuesIDREF="FM94086"Figure 1-1 on page 14 shows which login scripts are executed from which type of session and how to edit those login scripts.RENDERAS="SECT2"Logout IssuesWhen you log out from a local drive in a DOS session, the drive for your login directory is the last drive (set with DOS_LAST_DRIVE in DOS Settings) plus one.For example, if your last DOS drive is C:, the drive you see after logging out is drive D:.If you log out from a network drive, the drive remains the same.RENDERAS="SECT1"ID="FM18207"Logging In from an OS/2 Virtual DOS SessionIDXID="w11999"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
Logging in from an OS/2 virtual DOS session is the same as logging in from a DOS prompt.You cannot log in to a NetWare 4 network from a virtual DOS session unless the network supports IDXID="w12000"BOOK="_idx" COLLECTION="nw41" TIDREF="i443"
bindery emulation. If a NetWare 4 network supports bindery emulation, your DOS session is seen as a bindery-based workstation.RENDERAS="SECT2"ID="FM93789"ProcedureIf you added NETX.EXE to your AUTOEXEC.BAT file during the NetWare Client for OS/2 installation, skip to Step 2.PERFORMANCE="REQUIRED"Load the NetWare shell (IDXID="w12001"BOOK="_idx" COLLECTION="nw41" TIDREF="i2898"
NETX.EXE) for both global and private sessions. TypePAGENUM=95 ID="BP99"FORMAT="LINESPECIFIC"MOREINFO="NONE"NETX.EXEThe OS/2 virtual DOS environment does not support NDS and NetWare 4 VLMs. This means you can log in only to a NetWare 3 server. You must first load NETX.EXE before logging in. You can log into NetWare 4 through bindery emulation.PERFORMANCE="REQUIRED"Open a virtual 
CLASS=MENUITEM MOREINFO="NONE"DOS Full Screen or 
CLASS=MENUITEM MOREINFO="NONE"DOS Window.A prompt similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[C:\]PERFORMANCE="REQUIRED"Change to the first network drive.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"For global sessions, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"L:MOREINFO="NONE" <Enter>NetWare Client for OS/2 maps drive L: to the first network drive default unless you've changed the parameter in NET.CFG.PERFORMANCE="REQUIRED"For private sessions, use the drive that is the next letter away from the DOS LASTDRIVE, or your last physical drive.For example, if you indicated that drive D: is your last DOS drive, or last physical drive, you could map drive E: to a network drive. Drive E: is the next letter away from drive D:, your last physical drive.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"login server/username MOREINFO="NONE"<Enter>Replace 
server with the name of the bindery server. Replace 
username with your username. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"login tsmkt/esayers MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"If required, type your password.RENDERAS="SECT2"ID="FM94267"Logging In from an OS/2 Virtual DOS Boot Session (VMBOOT)IDXID="w12002"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"
Logging in from an OS/2 VMBOOT environment is the same as logging in from a DOS prompt.PAGENUM=96 ID="BP100"You must first open a VMBOOT full screen or window before initiating login procedures from the DOS prompt in OS/2.RENDERAS="SECT1"ID="FM35532"Customizing Icons For Global IDXID="w12003"BOOK="_idx" COLLECTION="nw41" TIDREF="i1606"
SupportRENDERAS="SECT2"PrerequisitesMARK=CHECKBOXRead IDREF="FM39661""Information for All Types of Sessions" on page 93.Make sure network support for virtual sessions is enabled. If not, enable it by running the NetWare Client for OS/2 Installation program. Virtual session support is enabled by default.RENDERAS="SECT2"ProceduresTo set up global NetWare support for an icon, do the following:PERFORMANCE="REQUIRED"Open the CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook for the DOS or Windows icon on your desktop.For information on opening DOS Settings, see "DOS Settings" in the OS/2 online Master Help Index. 
Figure 8-1 shows how to open DOS Settings.LABEL="8-1" FLOAT="0"Opening DOS SettingsFILEREF="c41q71a.tif"PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook, choose the 
CLASS=MENUITEM MOREINFO="NONE"Session tab.Figure 8-2 illustrates the 
CLASS=MENUITEM MOREINFO="NONE"Session tab page.
PAGENUM=97 ID="BP101"LABEL="8-2" FLOAT="0"Choosing the Session TabFILEREF="c41q67a.tif"PERFORMANCE="REQUIRED"On the 
CLASS=MENUITEM MOREINFO="NONE"Session screen, choose 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings ...Figure 8-3 illustrates the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings screen.
PAGENUM=98 ID="BP102"LABEL="8-3" FLOAT="0"The DOS Settings ScreenFILEREF="c41q72a.tif"PERFORMANCE="REQUIRED"(Optional) Enable the NetWare CAPTURE feature for the session.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "
CLASS=MENUITEM MOREINFO="NONE"IDXID="w12004"BOOK="_idx" COLLECTION="nw41" TIDREF="i1205"IDXID="w12005"BOOK="_idx" COLLECTION="nw41" TIDREF="i2244"IDXID="w12006"BOOK="_idx" COLLECTION="nw41" TIDREF="i589"IDXID="w12007"BOOK="_idx" COLLECTION="nw41" TIDREF="i2878"DOS_DEVICE" on the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings screenPERFORMANCE="REQUIRED"Type the following line in the 
CLASS=MENUITEM MOREINFO="NONE"Value field:
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\OS2\MDOS\LPTDD.SYSReplace drive with the drive letter of your boot drive. Add this line only if you want to use the CAPTURE command from the virtual session.If you want this device driver to be loaded for every virtual session you open, load it in the OS/2 CONFIG.SYS file instead of in the CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook. (See the OS/2 online Master Help Index for information on loading DOS device drivers.)PERFORMANCE="REQUIRED"Specify that all drives are available to NetWare.
PAGENUM=99 ID="BP103"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "DOS_LASTDRIVE.
IDXID="w12008"BOOK="_idx" COLLECTION="nw41" TIDREF="i1207"
"PERFORMANCE="REQUIRED"Type the drive letter for your last physical drive in the 
CLASS=MENUITEM MOREINFO="NONE"Value field.For example, if the last physical drive on your client workstation is drive D:, type MOREINFO="NONE"D in the CLASS=MENUITEM MOREINFO="NONE"Value field.The last physical drive for all global sessions will be the last physical drive indicated in the "DOS_LASTDRIVE" setting.PERFORMANCE="REQUIRED"Specify how many files the session can open simultaneously.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "DOS_FILES."PERFORMANCE="REQUIRED"Type 
MOREINFO="NONE"214.PERFORMANCE="REQUIRED"Choose Global NetWare support.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "
IDXID="w12009"BOOK="_idx" COLLECTION="nw41" TIDREF="i2835"
NETWARE_RESOURCES." PERFORMANCE="REQUIRED"Type 
MOREINFO="NONE"GLOBAL in the 
CLASS=MENUITEM MOREINFO="NONE"Value field.You can also choose "GLOBAL" from the drop-down list. Every session you start from this icon will have global support.PERFORMANCE="REQUIRED"Enable virtual IPX for this session. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "VIPX_ENABLED."PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Save and exit 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings.PERFORMANCE="REQUIRED"Load NETX. EXE 
IDXID="w12010"BOOK="_idx" COLLECTION="nw41" TIDREF="i2898"
 in each session where you want to log in to the network.To load NETX.EXE automatically for every session you start from a particular icon, use 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters on the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook for that icon.In the 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters box, type
MOREINFO="NONE" /K followed by a space, the directory path, and the NETX.EXE filename. The file will then execute at the start of every session opened from that icon.For example, to load NETX.EXE from the default location, type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"/K C:\NETWARE\NETX.EXE
PAGENUM=100 ID="BP104"For more about optional parameters, see "parameters, starting programs with" in the OS/2 online Master Help Index. To load NETX.EXE automatically for all DOS and MS Windows sessions, put the following command in an AUTOEXEC.BAT file at the root of your boot drive:
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\path\NETXReplace 
drive and 
path with the location of your NETX.EXE file. By default, NETX is installed in \NETWARE with the NetWare Client for OS/2 files. If you want IPX/SPX-only support, don't load NETX. If you don't load NETX, you can't log in to a NetWare network, but DOS and MS Windows applications can use the IPX protocol. RENDERAS="SECT1"ID="FM36228"Setting Up Drive IDXID="w12011"BOOK="_idx" COLLECTION="nw41" TIDREF="i1606"
MappingsIDXID="w12012"BOOK="_idx" COLLECTION="nw41" TIDREF="i1221"
 in Global IDXID="w12013"BOOK="_idx" COLLECTION="nw41" TIDREF="i4773"
SessionsDrive mappings in DOS differ from the drive mappings in OS/2. In OS/2, all mapped drives function like root drives, so drives mapped in OS/2 sessions show up as root drives in global DOS sessions.Root drives mapped in global DOS sessions show up as root drives in OS/2 sessions.Search drive mappings are not used in OS/2. Therefore, search drives mapped in global DOS sessions are ignored in OS/2 sessions. Also, search drives mapped in one global DOS session do not apply to other global DOS sessions. To eliminate confusion, avoid using search drives in a global environment. Instead, set up your environment as outlined in the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Decide which drives you want mapped in your global environment. Decide which of those drives need to be included in a search path.PERFORMANCE="REQUIRED"Edit your NetWare 4 login script (used in OS/2 sessions) and include MAP statements for all NetWare drives.
PAGENUM=101 ID="BP105"PERFORMANCE="REQUIRED"Edit your NetWare 3 DOS login script and include MAP ROOT statements for all NetWare drives.To edit your NetWare 3 DOS login script, use a text editor to edit the SYS:MAIL\
userID\LOGIN file, or use a NetWare 3 utility such as SYSCON.Use MAP ROOT rather than MAP for consistency between DOS and OS/2 sessions. For easiest maintenance, both login scripts should contain identical map statements.PERFORMANCE="REQUIRED"Edit your OS/2 CONFIG.SYS file and include the drive letters you want to be searchable in your PATH statement.This path is where OS/2 searches for .EXE, .CMD, and .COM files. For example, to include drive H: in the search path, add the following to your path:
FORMAT="LINESPECIFIC"MOREINFO="NONE"H:\;If needed, you can also include drive letters in the data path statement (DPATH). DPATH is where OS/2 searches for nonexecutable, non-.DLL files.PERFORMANCE="REQUIRED"Create a DOS.BAT file that includes a path to the same drives you included in CONFIG.SYS.This is where DOS searches for files. For example, to include drive H: in the search path, type the following in your .BAT file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET PATH=%PATH%;h:\;Note that the "%PATH%" appends whatever you type to the existing PATH statement. You can't include DPATH statements in the DOS.BAT file. PATH statements are limited to 123 characters, so try to map drives to the exact directories you need and minimize the number of subdirectories you specify.PERFORMANCE="REQUIRED"Run the .BAT file each time you open a DOS global session.You can use 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters on the 
CLASS=MENUITEM MOREINFO="NONE"Settings notebook.In the 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters box, type 
MOREINFO="NONE"/K followed by a space and the name of the .BAT file. The file is then executed at the start of every session opened from that icon. 
PAGENUM=102 ID="BP106"For more about PATH, DPATH, Settings, or Parameters, see the OS/2 online Master Help Index. RENDERAS="SECT1"ID="FM60865"Customizing Icons For IDXID="w12014"BOOK="_idx" COLLECTION="nw41" TIDREF="i4774"
Private SupportIDXID="w12015"BOOK="_idx" COLLECTION="nw41" TIDREF="i3556"RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXRead IDREF="FM39661""Information for All Types of Sessions" on page 93.Make sure network support for virtual sessions is enabled. If not, enable it by running the NetWare Client for OS/2 installation program. Virtual session support is enabled by default.RENDERAS="SECT2"ProceduresTo set up private NetWare support for an icon, do the following:PERFORMANCE="REQUIRED"Open the CLASS=MENUITEM MOREINFO="NONE"DOS Settings Notebook for the DOS or Windows icon on your desktop.For more on opening DOS Settings, see "DOS Settings" in the OS/2 online Master Help Index. 
IDREF="FM58788"Figure 8-4 shows how to open DOS Settings.LABEL="8-4" FLOAT="0"ID="FM58788"Opening DOS SettingsFILEREF="c41q71a.tif"PERFORMANCE="REQUIRED"In the
CLASS=MENUITEM MOREINFO="NONE" DOS Settings Notebook, choose 
CLASS=MENUITEM MOREINFO="NONE"Session.IDREF="FM92784"Figure 8-5 illustrates the 
CLASS=MENUITEM MOREINFO="NONE"Session tab page. 
PAGENUM=103 ID="BP107"LABEL="8-5" FLOAT="0"ID="FM92784"Choosing the Session TabFILEREF="c41q67a.tif"PERFORMANCE="REQUIRED"On the 
CLASS=MENUITEM MOREINFO="NONE"Session screen, choose 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings ...IDREF="FM43832"Figure 8-6 illustrates the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings screen.
PAGENUM=104 ID="BP108"LABEL="8-6" FLOAT="0"ID="FM43832"The DOS Settings ScreenFILEREF="c41q72a.tif"PERFORMANCE="REQUIRED"(Optional) Enable CAPTURE for the session.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED" Select 
IDXID="w12016"BOOK="_idx" COLLECTION="nw41" TIDREF="i589"IDXID="w12017"BOOK="_idx" COLLECTION="nw41" TIDREF="i2878"IDXID="w12018"BOOK="_idx" COLLECTION="nw41" TIDREF="i2244"
IDXID="w12019"BOOK="_idx" COLLECTION="nw41" TIDREF="i1205"CLASS=MENUITEM MOREINFO="NONE"DOS_DEVICE on the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings screenPERFORMANCE="REQUIRED"Type the following line in the 
CLASS=MENUITEM MOREINFO="NONE"Value field:
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\OS2\MDOS\LPTDD.SYSReplace drive with the drive letter of your boot drive. Add this line only if you want to use CAPTURE from the virtual session. If you want this device driver to be loaded for every virtual session you open, add it to the OS/2 CONFIG.SYS file instead of the CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook. (See the OS/2 online Master Help Index for information on loading DOS device drivers.)PERFORMANCE="REQUIRED"Specify how many files the session can open simultaneously.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "
IDXID="w12020"BOOK="_idx" COLLECTION="nw41" TIDREF="i1206"
DOS_FILES."
PAGENUM=105 ID="BP109"PERFORMANCE="REQUIRED"Type 
MOREINFO="NONE"214 in the 
CLASS=MENUITEM MOREINFO="NONE"Value field.PERFORMANCE="REQUIRED"Specify which drives are available to NetWare.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "DOS_LASTDRIVE.
IDXID="w12021"BOOK="_idx" COLLECTION="nw41" TIDREF="i1207"
"PERFORMANCE="REQUIRED"Type a drive letter other than Z in the 
CLASS=MENUITEM MOREINFO="NONE"Value field.All drives after this letter are available to the private NetWare connection in this session. All drives up to this letter are on your local hard drive or available for use in global session. PERFORMANCE="REQUIRED"Choose Private NetWare support.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "
IDXID="w12022"BOOK="_idx" COLLECTION="nw41" TIDREF="i2835"
NETWARE_RESOURCES." PERFORMANCE="REQUIRED"Type 
MOREINFO="NONE"PRIVATE in the 
CLASS=MENUITEM MOREINFO="NONE"Value field.You can also choose "Private" from the drop-down list. Every session you start from this icon will have its own NetWare login.PERFORMANCE="REQUIRED"Enable virtual IPX for this session.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "VIPX_ENABLED."PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"On.PERFORMANCE="REQUIRED"Save and exit 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings.PERFORMANCE="REQUIRED"ID="FM80167"Load NETX.EXE
IDXID="w12023"BOOK="_idx" COLLECTION="nw41" TIDREF="i2898"
 in each session where you want to log in to the network. To autoload NETX.EXE for every session you start from a particular icon, use 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters on the 
CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook for that icon. In the 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters box, type
MOREINFO="NONE" /K followed by a space, the directory path, and the NETX.EXE filename. The file is then executed at the start of every session opened from that icon.For example, to load NETX.EXE from the default location, type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"/K C:\NETWARE\NETX.EXEFor more about optional parameters, see "parameters, starting programs with" in OS/2 online Master Help Index.
PAGENUM=106 ID="BP110"To autoload NETX.EXE for all DOS and MS Windows sessions, put the following command in an AUTOEXEC.BAT file at the root of your boot drive:
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\path\NETX.EXEReplace 
drive and 
path with the location of NETX.EXE. By default, NETX.EXE is installed in \NETWARE with the NetWare Client for OS/2 files. If you want IPX/SPX-only support, don't load NETX.EXE. If you don't load NETX.EXE, you can't log in to a NetWare network, but DOS and MS Windows applications can use the IPX protocol.RENDERAS="SECT1"ID="FM24573"Special Instructions for IDXID="w12024"BOOK="_idx" COLLECTION="nw41" TIDREF="i4774"
Win-OS2IDXID="w12025"BOOK="_idx" COLLECTION="nw41" TIDREF="i4827"
 IconsNetWare and NetWare Client for OS/2 provides IDXID="w12026"BOOK="_idx" COLLECTION="nw41" TIDREF="i2587"
name space support. See Concepts for more about name space.These instructions apply to the MS Windows 3.x support shipped with OS/2 2.x.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXRead IDREF="FM39661""Information for All Types of Sessions" on page 93.Complete IDREF="FM35532""Customizing Icons For Global Support" on page 96 or IDREF="FM60865""Customizing Icons For Private Support" on page 102 for the Win-OS2 icon.RENDERAS="SECT2"ProcedureYou need several additional files for Win-OS2 NetWare support:TYPE="VERT"NWIPXSPX.DLLNETWARE.DRVTBMI2.COMNWPOPUP.EXENETWARE.HLPNWNETAPI.DLLNETAPI.DLLPAGENUM=107 ID="BP111"By default, these files are copied to the \OS2\MDOS\WINOS2\SYSTEM directory on your boot drive when you install NetWare Client for OS/2.If you are using OS/2 for Windows, these files are copied to the WINDOWS directory.The IDXID="w12027"BOOK="_idx" COLLECTION="nw41" TIDREF="i4509"
TBMI2.COMIDXID="w12028"BOOK="_idx" COLLECTION="nw41" TIDREF="i4442"
 file must be loaded before you run any MS Windows programs that make IPX or SPX calls.If you did not install TMBI2.COM during the NetWare Client for OS/2 installation, we recommend that you load it before you run any MS Windows programs. TBMI2.COM does not load automatically. To autoload TBMI2.COM for all sessions started from a single icon,PERFORMANCE="REQUIRED"Make and use a copy of a DOS icon.PERFORMANCE="REQUIRED"Create a batch file (.BAT extension) with the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\OS2\MDOS\WINOS2\SYSTEM\TBMI2.COM
WINOS2.COM
EXITReplace 
drive with the letter of your boot drive. PERFORMANCE="REQUIRED"Save the batch file in the following directory:
FORMAT="LINESPECIFIC"MOREINFO="NONE"\OS2\MDOS\WINOS2\SYSTEMPERFORMANCE="REQUIRED"Open the 
CLASS=MENUITEM MOREINFO="NONE"Settings for the icon.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Program. PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Optional Parameters field, type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"/K drive:\OS2\MDOS\WINOS2\batchfile.batReplace 
drive with the letter of your boot drive. Replace 
batchfile with the name of your batch file. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Session.PERFORMANCE="REQUIRED"Make sure "DOS Full Screen" is selected.
PAGENUM=108 ID="BP112"Each time you choose this icon, TBMI2 is loaded and Win-OS2 is started. For more about optional parameters, see "Parameters, starting programs with" in OS/2's online Master Help Index.To autoload TBMI2.COM for all DOS and MS Windows sessions, put the following command in an AUTOEXEC.BAT file in the root of your boot drive:FORMAT="LINESPECIFIC"MOREINFO="NONE"drive:\OS2\MDOS\WINOS2\SYSTEM\TBMI2.COMReplace drive with the letter of your boot drive. RENDERAS="SECT1"ID="FM47202"ID="FM63171"ID="FM19464"Special Instructions for IDXID="w12029"BOOK="_idx" COLLECTION="nw41" TIDREF="i1208"
DOS_STARTUP_DRIVE SessionsIf you want to boot a version of DOS other than the one shipped with OS/2, refer to the OS/2 online Master Help Index, which explains more about the DOS_STARTUP_DRIVE feature.The following explain how to set up DOS_STARTUP_DRIVE sessions globally or privately. RENDERAS="SECT2"Setting up Global DOS_STARTUP_DRIVE SessionsRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXRead IDREF="FM39661""Information for All Types of Sessions" on page 93.Set up your session to boot from another version of DOS. This involves several tasks, such as creating a boot IDXID="w12030"BOOK="_idx" COLLECTION="nw41" TIDREF="i494"
image file and setting DOS_STARTUP_DRIVE. You might want to set up another partition on your hard drive (although not necessary), as well as certain other IDXID="w12031"BOOK="_idx" COLLECTION="nw41" TIDREF="i4780"
tasks using the VMDISK utility. See the OS/2 online Master Help Index.Make sure network support for virtual sessions is enabled. If not, enable it by running the NetWare Client for OS/2 installation program. Virtual session support is enabled by default.PAGENUM=109 ID="BP113"Set up your session for global NetWare support by following the instructions in IDREF="FM36228""Setting Up Drive Mappings in Global Sessions" on page 100.RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED"Add the following lines to the CONFIG.SYS file on the DOS diskette or partition you boot from:FORMAT="LINESPECIFIC"MOREINFO="NONE"device=drive:\os2\mdos\fsfilter.sys
device=
drive:
path\dosvipx.sys
lastdrive=
last physical driveReplace 
drive and 
path with the drive and path names where the NetWare Client for OS/2 files are located.Type the 
lastdrive line only if you want the last global drive to be something different than the last drive in use by OS/2 at the time you start the virtual session.PERFORMANCE="REQUIRED"Load NETX.EXE. See 
IDREF="FM93789""Procedure" on page 94 for instructions on how to load NETX.EXE.RENDERAS="SECT2"Setting Up Private DOS_STARTUP_DRIVE SessionsRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXRead IDREF="FM39661""Information for All Types of Sessions" on page 93.Set up your session to boot from another version of DOS. This involves several tasks such as creating a boot image file and setting DOS_STARTUP_DRIVE. You might want to set up another partition on your hard drive (although not necessary), as well as certain other tasks using the VMDISK utility. See the OS/2 online Master Help Index.Make sure network support for virtual sessions is enabled. If not, enable it by running the NetWare Client for OS/2 installation program. PAGENUM=110 ID="BP114"Set up your session for private NetWare support by following the instructions in IDREF="FM60865""Customizing Icons For Private Support" on page 102.RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED"Add the following lines to the CONFIG.SYS file on the DOS diskette or partition you will boot from:FORMAT="LINESPECIFIC"MOREINFO="NONE"device=drive:\os2\mdos\fsfilter.sys
device=
drive:
path\dosvipx.sys
files=214
lastdrive=
letterReplace 
drive: and 
path with the drive and path names where the NetWare Client for OS/2 files are located. Replace 
letter with the last local drive accessible to the session for NETX.EXE or Z for VLMs. NetWare drives start after this letter. The FSFILTER.SYS driver provided by OS/2 gives the DOS_STARTUP_DRIVE session access to OS/2 HPFS drives and Named Pipes support. See the OS/2 documentation for more about FSFILTER.SYS.PERFORMANCE="REQUIRED"Load the NetWare Client for DOS and MS Windows software.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Follow the directions in 
NetWare Client for DOS and MS-Windows. Use the software on the NetWare Client for DOS and MS Windows diskette, 
CLASS=DISKWSDOS_1.PERFORMANCE="REQUIRED"To load NETX.EXE for NetWare 3 support, follow the instructions in 
IDREF="FM80167"Step 10 on page 105. Use the software on the NetWare Client for OS/2 diskette, 
CLASS=DISKWSOS2_1. Network drives mapped in an OS/2 session show up as local drives in a private DOS_STARTUP_DRIVE session. RENDERAS="SECT1"ID="FM67637"DisablingIDXID="w12032"BOOK="_idx" COLLECTION="nw41" TIDREF="i3556"IDXID="w12033"BOOK="_idx" COLLECTION="nw41" TIDREF="i1104"
NetworkIDXID="w12034"BOOK="_idx" COLLECTION="nw41" TIDREF="i1606"IDXID="w12035"BOOK="_idx" COLLECTION="nw41" TIDREF="i4773"
Support in All Virtual SessionsTo disable network support, run the NetWare Client for OS/2 installation program and deselect "Support for DOS and Windows Sessions." Then reboot your machine. PAGENUM=111 ID="BP115"This keeps VIPX.SYS and VSHELL.SYS from loading.To re-enable support, run the installation program and select "Support for DOS and Windows Sessions."RENDERAS="SECT1"ID="FM21725"Setting Up Named Pipes for Virtual DOS and MS WindowsIDXID="w12036"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"IDXID="w12037"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
IDXID="w12038"BOOK="_idx" COLLECTION="nw41" TIDREF="i4774"This section applies to virtual DOS and MS Windows sessions only. Virtual DOS and MS Windows sessions can function as Named Pipes clients; they cannot function as Named Pipes servers.If you've enabled Named Pipes support for OS/2 sessions, you automatically have Named Pipes support for virtual DOS sessions. See IDREF="FM25310""Installing Named Pipes for OS/2" on page 169 for instructions.Do not load the Named Pipes extender (DOSNP.EXE) in virtual DOS and MS Windows sessions. If you want Named Pipes support in either of the following situations, see the sections shown:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want Named Pipes forCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Virtual MS Windows sessionsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67244""For Virtual MS Windows SQL Named Pipes Clients" on page 111COLNAME=1 ROTATE="0" MOREROWS="0"Sessions with the DOS_STARTUP_DRIVE featureCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47202""Special Instructions for DOS_STARTUP_DRIVE Sessions" on page 108RENDERAS="SECT2"ID="FM67244"For Virtual MS Windows SQL Named Pipes ClientsIDXID="w12039"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"Verify that the IDXID="w12040"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"
NETAPI.DLL file from the \WINDOWS subdirectory on the CLASS=DISKWSOS2_1 diskette was copied to one of the following locations on your hard disk:MARK=BULLETThe \OS2\MDOS\WINOS2 subdirectory (which contains WINOS2.COM)PAGENUM=112 ID="BP116"The \OS2\MDOS\WINOS2\SYSTEM subdirectory (which contains the MS Windows KERNEL.EXE)The directory of the application that runs Named PipesThis NETAPI.DLL is an MS Windows file, not an OS/2 file, and is provided specifically for MS Windows SQL Named Pipes clients. Do not copy it over the NETAPI.DLL in the \NETWARE directory. RENDERAS="SECT2"ID="FM98918"For Sessions with IDXID="w12041"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"
DOS_STARTUP_DRIVE SetIDXID="w12042"BOOK="_idx" COLLECTION="nw41" TIDREF="i1208"Sessions set with DOS_STARTUP_DRIVE boot from a version of IDXID="w12043"BOOK="_idx" COLLECTION="nw41" TIDREF="i1578"
DOS other than the one included in OS/2. The OS/2 online Master Help Index explains more about the DOS_STARTUP_DRIVE feature.If you use DOS_STARTUP_DRIVE to boot a session, you do not need to get Named Pipes support from Novell. Instead, load the FSFILTER.SYS driver provided by OS/2. Load the FSFILTER.SYS driver in the CONFIG.SYS file for the DOS_STARTUP_DRIVE session. (CONFIG.SYS is bound into the image file you boot the session from. See your OS/2 documentation.)To load the FSFILTER.SYS driver, do the following:RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open CONFIG.SYS for the DOS_STARTUP_DRIVE session in a text editor.PERFORMANCE="REQUIRED"On a new line in the file, type a line to load FSFILTER.SYS.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\OS2\MDOS\FSFILTER.SYSPERFORMANCE="REQUIRED"Save and exit CONFIG.SYS.See your OS/2 documentation for more about loading FSFILTER.SYS in CONFIG.SYS.Do not load the Novell Named Pipes Extender for DOS in the DOS_STARTUP_DRIVE session. It will conflict with the OS/2 Named Pipes driver. PAGENUM=113 ID="BP117"RENDERAS="SECT1"ID="FM62792"Setting Up NetBIOS for Virtual DOS and MS WindowsIDXID="w12044"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"IDXID="w12045"BOOK="_idx" COLLECTION="nw41" TIDREF="i4774"This section applies to virtual DOS and MS Windows sessions under OS/2 only. To set up NetBIOS on an actual DOS or MS Windows workstation, see the 
BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows documentation.NetWare Client for OS/2 and the IBM LAPS program both support the NetBIOS protocol in a virtual session. However, the type of support is different. RENDERAS="SECT2"NetWare NetBIOS SupportNetWare NetBIOS support is not virtualized. This means that the session will not use the same NetBIOS driver that is used by OS/2 sessions. Instead, you must load the NETBIOS.EXE TSR program in the session, just as you would to get NetBIOS support on an actual DOS workstation.When you use NETBIOS.EXE in a virtual session, you can't get NetBIOS connections from OS/2 sessions or from other DOS or MS Windows sessions until NETBIOS.EXE is unloaded.You will only have one NetBIOS connection from a single virtual session. This is true even if your OS/2 NetBIOS drivers appears to be loaded. RENDERAS="SECT2"IBM LAPS NetBIOS SupportThe LAPS NetBIOS support is virtualized, meaning that you do not have a single-connection limitation.You do not have access to this virtualized support unless you have the LAPS protocols, included with both Extended Services and LAN Services from IBM. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To useCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Client for OS/2 non-virtualized NetBIOS supportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM66356""Using NetWare NetBIOS Support for a Single DOS Session" on page 114COLNAME=1 ROTATE="0" MOREROWS="0"LAPS virtualized NetBIOS supportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM30130""Using LAPS NetBIOS Support for Virtual Sessions" on page 115PAGENUM=114 ID="BP118"RENDERAS="SECT2"ID="FM66356"Using NetWare NetBIOS Support for a Single DOS SessionAs IDREF="FM63674"Figure 8-7 shows, NetWare NetBIOS support for a single DOS session goes through NETBIOS.EXE and VIPX.When using NetWare NetBIOS for a single DOS session, you cannot have NetBIOS connections from any other DOS, MS Windows, or OS/2 sessions. You must disable NetBIOS support for OS/2 sessions.LABEL="8-7" FLOAT="0"ID="FM63674"Novell NetBIOS Support for a Virtual SessionFILEREF="c41q66a.tif"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXEnable IPX support for virtual sessions. SeeIDREF="FM35532""Customizing Icons For Global Support" on page 96 or IDREF="FM60865""Customizing Icons For Private Support" on page 102.Disable NetBIOS support for OS/2 sessions. Novell's NetBIOS solution for DOS boxes is not virtual and doesn't allow other NetBIOS drivers to be running at the same time. Disable NetBIOS support by running the NetWare Client for OS/2 installation program and deselecting "NetBIOS Emulation for OS/2." IDREF="FM17293""Installing the Driver" on page 189 explains how to run the installation program.PAGENUM=115 ID="BP119"RENDERAS="SECT3"ProceduresFollow the instructions in the NetWare Client for DOS and MS Windows manual. Use that documentation to MARK=BULLETLoad NETBIOS.EXE in a single DOS session.Configure NetWare NetBIOS for DOS if necessary. RENDERAS="SECT2"ID="FM30130"Using LAPS NetBIOS Support for Virtual SessionsAs IDREF="FM38858"Figure 8-8 shows, LAPS virtual NETBIOS support goes through LANVDD and LANPDD. It uses the NETBIOS.OS2 interface to communicate with either the Novell or IBM NetBIOS driver.LABEL="8-8" FLOAT="0"ID="FM38858"LAPS NetBIOS Support for Virtual SessionsFILEREF="c41q62a.tif"LAPS NetBIOS support follows the NetBIOS 3.0 (NB30) standard. You can run NetBIOS applications in a virtual session even if those applications do not conform with NB30. However, the need for increasing resources in a session is more likely when running non-NB30 applications. PAGENUM=116 ID="BP120"RENDERAS="SECT3"Avoiding ResourceIDXID="w12046"BOOK="_idx" COLLECTION="nw41" TIDREF="i3819"
 ErrorsIDXID="w12047"BOOK="_idx" COLLECTION="nw41" TIDREF="i1346"IDXID="w12048"BOOK="_idx" COLLECTION="nw41" TIDREF="i386"As shown in IDREF="FM38858"Figure 8-8, virtualized NetBIOS sessions can be supported by Novell's OS/2 NETBIOS.SYS driver or by Extended Services's OS/2 NETBEUI.OS2 driver or by both.When virtual sessions are supported by Novell's OS/2 NetBIOS driver, be aware of a potential resource limitation. If you have previously followed the steps in IDREF="FM40784""Configuring NETBIOS.OS2 with PROTOCOL.INI" on page 195, you are using Novell's driver.LAPS NetBIOS support for virtual sessions follows the NetBIOS 3.0 (NB30) standard. Among other things, a NetBIOS 3.0 application reserves a certain number of names, commands, and sessions when it first executes.If you run NetBIOS applications in several virtual sessions, all resources in one of the NetBIOS components might be reserved and additional applications will not run. You see a resource error when you try and make NetBIOS connections.To minimize the possibility that NetBIOS will run out of resources, doing both or either of the following:MARK=BULLETWhenever you're using virtual NetBIOS connections, increase the default resources allowed for the NETBIOS driver in NET.CFG.IDREF="FM24938""Configuring the Driver" on page 191 explains how to increase the defaults for the OS/2 NetBIOS driver.Specify the resources consumed for each virtual session you use. IDREF="FM10500""Procedures" on page 117 explains how to specify resources.RENDERAS="SECT3"ID="FM52484"PrerequisitesMARK=CHECKBOXInstall Extended Services with NetBIOS support. See the Extended Services documentation.Install LAN Services if you have it. See the LAN Services documentation.Install NetWare Client for OS/2 with NetBIOS support. IDREF="FM79688""Setting Up the Novell NetBIOS Driver" on page 188 explains how to do this. PAGENUM=117 ID="BP121"Configure NETBIOS.OS2 to use both Novell and IBM drivers. See IDREF="FM40784""Configuring NETBIOS.OS2 with PROTOCOL.INI" on page 195.RENDERAS="SECT3"ID="FM10500"ProceduresThese instructions explain how to set resource information for Extended Services virtualized NetBIOS. This information is stored with a program called IDXID="w12049"BOOK="_idx" COLLECTION="nw41" TIDREF="i2250"
LTSVCFG.COM.LTSVCFG.COM is included with LAPS in Extended Services and LAN Services.PERFORMANCE="REQUIRED"Open the virtual session.PERFORMANCE="REQUIRED"Execute LTSVCFG.COM with the command line parameters you need.For example, to set the number of NetBIOS commands to 12 type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LTSVCFG.COM C=12Three parameters that apply to NetBIOS resources are
FORMAT="LINESPECIFIC"MOREINFO="NONE"s=number of NetBIOS sessionsIDXID="w12050"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"
n=
namesIDXID="w12051"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"IDXID="w12052"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"
c=
commandsIDXID="w12053"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"For more about these and other NetBIOS parameters, see the LAPS documentation on NetBIOS. You can't set parameters for LTSVCFG.COM to amounts higher than amounts set for the NETBIOS.OS2 or NETBIOS.SYS driver. The default sessions, names, and commands settings for the NETBIOS.SYS driver areSessions=16Names=24Commands=32You might have changed these defaults in your NET.CFG file.LABEL="9"PAGENUM=119 ID="BP122"Printing from Your WorkstationCOLS=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="FM20436"Understanding Network Printing COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20436"119COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62736"Prerequisites COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62736"119COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM91348"Setting Up Printing for OS/2 COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91348"120COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM64748"Loading NPRINTER.EXE COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64748"122RENDERAS="SECT1"ID="FM20436"Understanding Network PrintingNetwork printing allows users on the network to share printers. NetWare® uses a print queue, a print server, and a printer driver to allow network stations to print to a network printer.A network printer can be connected either directly to a server or to a workstation depending on the configuration of the printer and the network.Network printing requires some initial setup before the network recognizes print files sent from your workstation.RENDERAS="SECT1"ID="FM62736"PrerequisitesMARK=CHECKBOXMake sure you are connected to the network and have access to network printing resources.Make sure the NetWare ToolsTM icon is in your CLASS=MENUITEM MOREINFO="NONE"Novell folder on the desktop.PAGENUM=120 ID="BP123"RENDERAS="SECT1"ID="FM91348"Setting Up Printing for OS/2IDXID="w12054"BOOK="_idx" COLLECTION="nw41" TIDREF="i3542"
Setting up workstation printing in OS/2* is done using NetWare Tools for OS/2.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"From your desktop, choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon.PERFORMANCE="REQUIRED"From 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View, choose 
CLASS=MENUITEM MOREINFO="NONE"NetWare Tools.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Tools menu.PERFORMANCE="REQUIRED"ID="FM24579"Choose 
CLASS=MENUITEM MOREINFO="NONE"Printer Ports.A 
CLASS=MENUITEM MOREINFO="NONE"Printers window appears and a 
CLASS=MENUITEM MOREINFO="NONE"Printers option appears in the menu bar, seen in 
IDREF="FM80488"Figure 9-1.LABEL="9-1" FLOAT="0"ID="FM80488"NetWare Tools Printer OptionFILEREF="c41q14a.tif"PERFORMANCE="REQUIRED"Choose a port by double-clicking on the port name.(Or select a port and choose 
CLASS=MENUITEM MOREINFO="NONE"Printers from the upper menu bar; then choose 
CLASS=MENUITEM MOREINFO="NONE"Capture.)
PAGENUM=121 ID="BP124"A 
CLASS=MENUITEM MOREINFO="NONE"Capture window appears, seen in 
IDREF="FM70552"Figure 9-2.LABEL="9-2" FLOAT="0"ID="FM70552"Capture DialogFILEREF="c41q27a.tif"PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Printers/Queue list, highlight a print queue name and choose 
CLASS=MENUITEM MOREINFO="NONE"Capture.If the print queue you want to capture does not appear in the CLASS=MENUITEM MOREINFO="NONE"Printers/Queue list, check to see if you are first attached to the server containing this resource. Choose CLASS=MENUITEM MOREINFO="NONE"Server from the CLASS=MENUITEM MOREINFO="NONE"Tools option to see connected servers.To maintain your connections, useCLASS=MENUITEM MOREINFO="NONE" Save Settings from the CLASS=MENUITEM MOREINFO="NONE"Network menu.For more about this tool, choose CLASS=MENUITEM MOREINFO="NONE"Help.PAGENUM=122 ID="BP125"RENDERAS="SECT1"ID="FM64748"IDXID="w12055"BOOK="_idx" COLLECTION="nw41" TIDREF="i3008"
Loading NPRINTER.EXEEvery network printer requires a printer driver to create a print job from the network to the printer. The type of driver depends on how the printer is attached to the network. Network-attached printers store their own driver. Workstation- attached printers need NPRINTER.EXE loaded on the workstation.RENDERAS="SECT2"PrerequisitesWhen defining a printer, be sure to set up the printer as "remote-other" rather than "parallel."MARK=CHECKBOXNetWare 4 server.Print server, print queue, and printer that have been created and assigned using one of the following:MARK=BULLETNetWare AdministratorPCONSOLE.EXEPrinter set up as "remote-other" rather than "parallel."PSERVER.NLM loaded on the NetWare 4 server.Printer cabled to a workstation running OS/2, directly to the network, or to a NetWare server.Make sure each printer functions properly in its current environment. If a printer does not function properly in its current environment (non-network or otherwise), it will not work with NetWare print services.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon from your desktop.The 
CLASS=MENUITEM MOREINFO="NONE"Novell-Icon View window appears.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Network Printer icon from the Novell-Icon View window.The 
CLASS=MENUITEM MOREINFO="NONE"NPRINTER windows appears. If the printer you want to load is already configured, go to 
IDREF="FM24579"Step 4.PAGENUM=123 ID="BP126"PERFORMANCE="REQUIRED"Configure printers.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Load from the 
CLASS=MENUITEM MOREINFO="NONE"Printers menu.The CLASS=MENUITEM MOREINFO="NONE"Load Printers window appears.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Define from the 
CLASS=MENUITEM MOREINFO="NONE"Load Printers window.The CLASS=MENUITEM MOREINFO="NONE"Define Printers window appears. A list of printers defined on this workstation displays.PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Add button to define a printer for NPRINTER to load on this workstation.The CLASS=MENUITEM MOREINFO="NONE"Add/Edit Printer window appears.PERFORMANCE="REQUIRED"Type a printer name in the 
CLASS=MENUITEM MOREINFO="NONE"Description field.PERFORMANCE="REQUIRED"Double-click a print server from the list.A list of printers appears in the dialog. These printers were created using NetWare Administrator or PCONSOLE.PERFORMANCE="REQUIRED"Choose a printer by highlighting the name.This specifies the printer for NPRINTER to load.PERFORMANCE="REQUIRED"(Optional) Mark
CLASS=MENUITEM MOREINFO="NONE" Load on startup if you want the NetWare server to attach to this printer when NPRINTER is loaded.PERFORMANCE="REQUIRED"Choose the arrow box to the right of the 
CLASS=MENUITEM MOREINFO="NONE"Default OS/2 Print Queue and choose an OS/2 print queue.OS/2 print queues are created when you create printers as documented in your OS/2 manual. NPRINTER requires that an OS/2 print queue exist on the workstation.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.The printer now appears in the CLASS=MENUITEM MOREINFO="NONE"Define Printers window with other printers defined on this workstation.PERFORMANCE="REQUIRED"(Optional) Repeat Steps 3a through 3i for each additional printer NPRINTER will load on this workstation.You can define as many printers as you want, but NPRINTER can only run seven concurrently.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Exit to close the 
CLASS=MENUITEM MOREINFO="NONE"Define Printers window.PERFORMANCE="REQUIRED"ID="FM62416"Choose 
CLASS=MENUITEM MOREINFO="NONE"Load from the 
CLASS=MENUITEM MOREINFO="NONE"Printers menu.
PAGENUM=124 ID="BP127"The 
CLASS=MENUITEM MOREINFO="NONE"Load Printers window appears.If the CLASS=MENUITEM MOREINFO="NONE"Load option is grayed so that you cannot select it, or if the printer you want is not listed, you must configure a printer.PERFORMANCE="REQUIRED"Double-click a printer or highlight a printer and choose 
CLASS=MENUITEM MOREINFO="NONE"Load.NPRINTER makes an attachment from the workstation to the NetWare server.You can unload any or all printer drivers by choosing CLASS=MENUITEM MOREINFO="NONE"Unload from the CLASS=MENUITEM MOREINFO="NONE"Printers menu. Highlight the printers you want to unload and choose CLASS=MENUITEM MOREINFO="NONE"Unload, or unload them all by choosing CLASS=MENUITEM MOREINFO="NONE"Unload All.RENDERAS="SECT2"Automating the Loading of NPRINTERRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the OS/2 desktop, open the CLASS=MENUITEM MOREINFO="NONE"OS/2 System folder.The 
CLASS=MENUITEM MOREINFO="NONE"OS/2 System - Icon View window appears.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"OS/2 System - Icon View window, open the 
CLASS=MENUITEM MOREINFO="NONE"Startup folder.PERFORMANCE="REQUIRED"From the OS/2 desktop, open the 
CLASS=MENUITEM MOREINFO="NONE"Novell folder.The 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window appears.PERFORMANCE="REQUIRED"From the
CLASS=MENUITEM MOREINFO="NONE" Novell - Icon View folder, copy or move the 
CLASS=MENUITEM MOREINFO="NONE"Network Printer icon to the 
CLASS=MENUITEM MOREINFO="NONE"Startup folder.Now when OS/2 is booted, NPRINTER will autoload.RENDERAS="SECT2"Capturing Printer PortsNPRINTER cannot capture ports it is already connected to. If the port that the network printer is connected to is captured and a print job is sent to that port, the print job is put in an infinite loop between the NetWare print queue and the OS/2 workstation.The print job continues to appear and disappear from the NetWare print queue; however, it is never printed.PAGENUM=125 ID="BP128"For example, if the network printer is physically connected to the LPT1 port on the OS/2 workstation, do not CAPTURE the LPT1 port or the print job will be put in an infinite loop between the LPT1 port and your workstation.You should capture LPT2 and LPT3 instead of LPT1 in this case.RENDERAS="SECT2"Starting NPRINTER MinimizedNPRINTER for OS/2 cannot be started minimized.LABEL="10"PAGENUM=127 ID="BP129"Backing Up Your WorkstationCOLS=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"IDXID="w12056"BOOK="_idx" COLLECTION="nw41" TIDREF="i369"IDREF="FM80903"Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80903"127COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM68439"Starting TSA_OS2 Manually COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68439"128COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM70588"Starting TSA_OS2 Automatically COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM70588"129COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM23256"Setting Up Your TSA_OS2.CFG File COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23256"130RENDERAS="SECT1"ID="FM80903"OverviewThe network supervisor or backup supervisor can back up your OS/2* workstation to the network. To allow access, run the NetWare® IDXID="w12057"BOOK="_idx" COLLECTION="nw41" TIDREF="i4601"IDXID="w12058"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
TSA_OS2 (Target Service Agent) program on your workstation.TSA_OS2 runs as an application in an OS/2 session. You can continue working in other sessions while TSA_OS2 is running on your workstation. Whenever the TSA_OS2 is running, SBACKUP or another backup program can access the hard drive data. TSA_OS2 is installed automatically on the hard drive when you install the NetWare ClientTM for OS/2 software. An icon for the TSA_OS2 is placed in the CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop. With TSA_OS2, you can specifyMARK=BULLETWhich users on the network can access your hard driveWhat password must be typed in the backup program before accessing your hard driveWhich drives on the hard disk can be backed upPAGENUM=128 ID="BP130"RENDERAS="SECT1"ID="FM68439"Starting TSA_OS2 IDXID="w12059"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
ManuallyIDXID="w12060"BOOK="_idx" COLLECTION="nw41" TIDREF="i4601"This section explains how to start TSA_OS2 by choosing its icon on your desktop.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXLoad TSA_OS2.NLM on the server. See Supervising the Network.Install NetWare Client for OS/2. RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon on your OS/2 desktop.The 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window appears. PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window on your desktop, choose the 
CLASS=MENUITEM MOREINFO="NONE"NetWare TSA icon for the TSA_OS2.EXE program.The TSA_OS2 main window appears. See 
IDREF="FM34245"Figure 10-1. 
PAGENUM=129 ID="BP131"LABEL="10-1" FLOAT="0"ID="FM34245"The TSA_OS2 Main WindowFILEREF="c41q73a.tif"PERFORMANCE="REQUIRED"Choose the features you want from the menu bar.For more about this feature, choose 
CLASS=MENUITEM MOREINFO="NONE"Help.RENDERAS="SECT1"ID="FM70588"Starting TSA_OS2 IDXID="w12061"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
AutomaticallyIDXID="w12062"BOOK="_idx" COLLECTION="nw41" TIDREF="i4601"You can set up TSA_OS2 to start each time you boot your machine. To do this,MARK=BULLETPlace your TSA_OS2 icon in the CLASS=MENUITEM MOREINFO="NONE"Startup folderThis section explains how to put the icon in the CLASS=MENUITEM MOREINFO="NONE"Startup folder. PAGENUM=130 ID="BP132"Set up your TSA_OS2.CFG file IDREF="FM23256""Setting Up Your TSA_OS2.CFG File" on page 130 explains how to use a TSA_OS2.CFG file. RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXLoad the TSA_OS2.NLM on the server. See Supervising the Network.Install NetWare Client for OS/2. RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Open the CLASS=MENUITEM MOREINFO="NONE"OS/2 System folder on your desktop. The 
CLASS=MENUITEM MOREINFO="NONE"OS/2 System window appears. PERFORMANCE="REQUIRED"Open the 
CLASS=MENUITEM MOREINFO="NONE"Startup folder from the 
CLASS=MENUITEM MOREINFO="NONE"OS/2 System window. The 
CLASS=MENUITEM MOREINFO="NONE"Startup window appears.PERFORMANCE="REQUIRED"Without closing the 
CLASS=MENUITEM MOREINFO="NONE"Startup window, open the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop. The 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window appears. PERFORMANCE="REQUIRED"Drag the TSA_OS2.EXE icon from the 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window into the 
CLASS=MENUITEM MOREINFO="NONE"Startup folder. When you reboot your machine, the TSA_OS2 program will start automatically.If backups at your site are done after hours, remember to leave OS/2 workstations turned on or the backup supervisor can't access the hard disk.RENDERAS="SECT1"ID="FM23256"IDXID="w12063"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"
Setting Up Your TSA_OS2.CFG FileIDXID="w12064"BOOK="_idx" COLLECTION="nw41" TIDREF="i4602"You can create a text file called TSA_OS2.CFG to store settings for TSA_OS2. These settings are read by TSA_OS2 each time the program starts up. PAGENUM=131 ID="BP133"IDREF="FM12812"Table 10-1 lists the parameters you can include in the configuration file. LABEL="10-1" PGWIDE=1 TOCENTRY="1"IDXID="w12065"BOOK="_idx" COLLECTION="nw41" TIDREF="i4602"ID="FM12812" List of TSA_OS2.CFG ParametersCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="15*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"ExampleVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"WSNameIDXID="w12066"BOOK="_idx" COLLECTION="nw41" TIDREF="i4857"IDXID="w12067"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"COLNAME=2 ROTATE="0" MOREROWS="0"The Target Service name you assign to your workstation. Do not use spaces in the workstation name.COLNAME=3 ROTATE="0" MOREROWS="0"WSName JO_OS2COLNAME=1 ROTATE="0" MOREROWS="0"ServerNameIDXID="w12068"BOOK="_idx" COLLECTION="nw41" TIDREF="i4059"IDXID="w12069"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"COLNAME=2 ROTATE="0" MOREROWS="0"The name of the server where the Target Service Agent Router NLM is loaded. COLNAME=3 ROTATE="0" MOREROWS="0"ServerName SALES_MKTGCOLNAME=1 ROTATE="0" MOREROWS="0"UserNameIDXID="w12070"BOOK="_idx" COLLECTION="nw41" TIDREF="i4726"IDXID="w12071"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"COLNAME=2 ROTATE="0" MOREROWS="0"The User objects you allow to attach to the OS/2 workstation. Repeat this line for each User object. If you want to specify a password, specify it on the same line as the username.The username must be defined on the network. The password is unique to your workstation, not the same password the user types to access the network. If you specify a IDXID="w12072"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
password, the backup supervisor must type that password in the backup program.COLNAME=3 ROTATE="0" MOREROWS="0"UserName NANCYor to set a password of NEATO:UserName NANCY NEATOCOLNAME=1 ROTATE="0" MOREROWS="0"HideResourceIDXID="w12073"BOOK="_idx" COLLECTION="nw41" TIDREF="i1666"IDXID="w12074"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"COLNAME=2 ROTATE="0" MOREROWS="0"The drives you do not want to be backed up. Repeat this line for each drive. The colon after the driver letter is allowed, but not required.COLNAME=3 ROTATE="0" MOREROWS="0"HideResource CHideResource D:COLNAME=1 ROTATE="0" MOREROWS="0"AutoRegisterIDXID="w12075"BOOK="_idx" COLLECTION="nw41" TIDREF="i375"IDXID="w12076"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"COLNAME=2 ROTATE="0" MOREROWS="0"Automatically register with the Target Service Router NLM on the server whenever your workstation boots. To use this parameter, specify a valid WSName, ServerName, and UserName.COLNAME=3 ROTATE="0" MOREROWS="0"AutoRegister ONorAutoRegister OFFCOLNAME=1 ROTATE="0" MOREROWS="0"TempFilesDirIDXID="w12077"BOOK="_idx" COLLECTION="nw41" TIDREF="i4600"IDXID="w12078"BOOK="_idx" COLLECTION="nw41" TIDREF="i4463"COLNAME=2 ROTATE="0" MOREROWS="0"The location on your hard drive where the backup program can temporarily store files during backup. These files are removed when backup is completed. Do not use spaces in the directory name. If you don't specify this parameter, the temporary directory is located in the root of the directory where you executed TSA_OS2.EXE. COLNAME=3 ROTATE="0" MOREROWS="0"TempFilesDir C:\TEMP_TSAPAGENUM=132 ID="BP134"The following is a sample IDXID="w12079"BOOK="_idx" COLLECTION="nw41" TIDREF="i4602"
TSA_OS2.CFG configuration file:FORMAT="LINESPECIFIC"MOREINFO="NONE"WSName Joe's_Machine
ServerName SALES_MKTG
UserName FredJ
UserName Mark 
UserName admin   
UserName nancy NEATO
HideResource c:
hideresource b:
AUTOREGISTER on
tempfilesdir c:\ emp_os2The file is not case-sensitive.LABEL="11"PAGENUM=133 ID="BP135"Using Remote Program LoadCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="20*"COLNAME=2 COLWIDTH="5*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM92754"Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41226"133COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM54416"Prerequisites COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54416"137COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM25777"Determining Boot PROM Type COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM25777"139COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86543"Installing OS/2 Files for RPL Workstations COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86543"141COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM35976"Installing RPL Files for RPL Workstations COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM35976"144COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29241"Setting Up RPL Workstations COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29241"147COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86497"Creating Users and Granting Rights COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86497"150COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83948"Using RPL on Workstations with Hard Disks  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83948"152COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11537"Configuring NetWare Client for OS/2 for RPL Workstations COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11537"154ID="FM41226"To install Remote Program Load (RPL), you must have Supervisor object rights to the NetWare® server that the workstation will attach to.RENDERAS="SECT1"ID="FM92754"
OverviewRPL lets OS/2* workstations boot from network hard disks rather than booting from a local hard disk.RENDERAS="SECT2"What Happens When You Add RPL WorkstationsWhen you add RPL workstations to a network, the following actions occur:TYPE="VERT"Directories are createdFiles are createdPAGENUM=134 ID="BP136"Files are copiedCONFIG.SYS is copied and modifiedRENDERAS="SECT3"Directories Are CreatedIf you have not installed RPL workstation support, the IDXID="w12080"BOOK="_idx" COLLECTION="nw41" TIDREF="i4404"
SYS:RPL2 and the \USER and \COMPUTER directories will be created on each server and the following directories created for each workstation:MARK=BULLETA user's home directory under the \USER directory. This directory has the same name as the username you specify. For example, a user named JADAMS would have a home directory ofMOREINFO="NONE"SYS:RPL2\USER\JADAMSIf a logical name was specified (for example, LAB_1), then the home directory would beMOREINFO="NONE"SYS:RPL2\USER\JADAMS\LAB_1A user's node address directory under the \COMPUTER directory. This directory has the same name as the last 11 characters of the workstation node address. For example, if the address is 2223345BBBBB, the node address directory would beMOREINFO="NONE"SYS:RPL2\COMPUTER\223345BB.BBBA subdirectory containing the OS/2 desktop in each user's home directory. This directory is called Desktop for OS/2 2.1.A \SPOOL subdirectory in each user's home directory. This directory contains all desktop printing files.RENDERAS="SECT3"Files Are CreatedMARK=BULLETA file called IDXID="w12081"BOOK="_idx" COLLECTION="nw41" TIDREF="i771"IDXID="w12082"BOOK="_idx" COLLECTION="nw41" TIDREF="i497"
CONFIG.WSS is created in each user's node address directory on the server. This file tells OS/2 to use the OS2.INI, OS2SYS.INI, and CONFIG.SYS files from the user's home directory on the network instead of trying to find these files in their regular locations. It also tells OS/2 to use the desktop files and the \SPOOL subdirectory from the user's home directory, rather than from their regular locations. PAGENUM=135 ID="BP137"A BOOTCONF.SYS file is created in the SYS:LOGIN directory. If a BOOTCONF.SYS file exists (from other installations of RPL workstations), the information for the new workstations is added to the beginning of the file. This file tells the server which IDXID="w12083"BOOK="_idx" COLLECTION="nw41" TIDREF="i3744"IDXID="w12084"BOOK="_idx" COLLECTION="nw41" TIDREF="i494"
boot image file to use for each workstation and contains lines identifying which RPL workstation uses which type of network board. For example, a line for a NE2000 workstation might be as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"0xDOC20,1b0276A32222=NE2000.RPLIDREF="FM21028"Figure 11-1 explains the text in BOOTCONF.SYS.LABEL="11-1" FLOAT="0"ID="FM21028"Format of BOOTCONF.SYS File for Older Style Boot PROMsFILEREF="c41q17a.tif"RENDERAS="SECT3"Files Are CopiedAll files in the \DESKTOP and \SPOOL subdirectories are copied from the local drive of the OS/2 workstation to the server. Also, all files in CONFIG.WSS file are copied.These files allow RPL workstations to load customized versions of OS/2 and the OS/2 desktop. PAGENUM=136 ID="BP138"RENDERAS="SECT3"CONFIGIDXID="w12085"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"IDXID="w12086"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"
.SYS Is Copied and ModifiedA CONFIG.SYS file is copied from the local drive of the OS/2 workstation you are installing from to each user's subdirectory on each server. This CONFIG.SYS is modified for each user. The line that loads HPFS is commented out, and the directory in the SWAPPATH line is changed.All lines beginning with IFS= are commented out before the IFS=NWIFS line. The NWIFS line must be the first installable file system loaded. If the user wants to run a CD-ROM drive from the RPL workstation, the IFS=CDFS line must be moved to after the NetWare Requester statements in CONFIG.SYS.Also, disk caching is turned off and the ODI driver is changed to the driver you selected.IDREF="FM29696"Figure 11-2 shows the directory structure created for RPL workstation support.PAGENUM=137 ID="BP139"LABEL="11-2" FLOAT="0"IDXID="w12087"BOOK="_idx" COLLECTION="nw41" TIDREF="i1081"ID="FM29696"Directory Structure for RPL Workstation SupportFILEREF="c41q15a.tif"RENDERAS="SECT1"ID="FM54416"PrerequisitesThree computers are needed to install an RPL workstation:MARK=BULLETA computer to be used as the RPL workstation (referred to as the RPL workstation).The server that the RPL workstation will attach to.PAGENUM=138 ID="BP140"A computer with OS/2 and NetWare ClientTM for OS/2 installed that can access the server (referred to as the client workstation).ID="FM48471"There are prerequisites for each of these three computers.RENDERAS="SECT2"Prerequisites for the ServerMARK=CHECKBOXThe server must be running either NetWare 3 or 4.You must have Supervisor object rights to the server that the RPL workstation will attach to.Enough disk space must be on the server for RPL workstation installation. You need 30 MB for OS/2 plus enough space for additional files you need.RENDERAS="SECT2"Prerequisites for the Client WorkstationMARK=CHECKBOXMake sure OS/2 is installed on the workstation C: drive. It must be drive C:.Make sure that NetWare Client for OS/2 is installed in the \NETWARE directory.Make sure the client workstation is connected to the server.If drive C: has HPFS, make sure the OS/2 name space is loaded for volume SYS: or the server where the remote workstation files will be installed.Move or delete all personal files that are on drive C:. (The installation program copies all files from drive C: to the server.)Make sure the desktop is arranged in the way you want the RPL workstation to appear. The RPL workstation's desktop will look like the desktop of the workstation you're installing from.Make sure the workstation only loads the programs that the RPL workstations need. Programs can be loaded from CONFIG.SYS, .CMD files, or the CLASS=MENUITEM MOREINFO="NONE"Startup folder.PAGENUM=139 ID="BP141"Make sure all programs needed by RPL workstations are located on drive C: (this only applies to programs on the hard drive). For example, make sure your E-mail program on C:\EMAIL does not store mail files in the D:\MYMAIL directory or use E:\TEMP for initialization files. The RPL workstations will not have drives D: or E: available.If you set up PS/2* computers as RPL workstations, obtain an OS/2 installation diskette. If you use PS/2 computers as RPL workstations, the program copies some files from this diskette.RENDERAS="SECT2"Prerequisites for the RPL WorkstationMARK=CHECKBOXRPL workstations must have network boards with Remote Boot PROMs attached. Remote Reset PROMs allow workstations to connect to the network so that boot information can be accessed.Determine the type of Remote Reset PROM you have. The RPL workstation installation will ask if you have a IDXID="w12088"BOOK="_idx" COLLECTION="nw41" TIDREF="i495"IDXID="w12089"BOOK="_idx" COLLECTION="nw41" TIDREF="i2912"CLASS=MENUITEM MOREINFO="NONE"New Enhanced Boot PROM or anIDXID="w12090"BOOK="_idx" COLLECTION="nw41" TIDREF="i495"IDXID="w12091"BOOK="_idx" COLLECTION="nw41" TIDREF="i3070"CLASS=MENUITEM MOREINFO="NONE" Older Style Boot PROM. Older style boot PROMs were made before 1992. If you don't know the type of PROM you have, find the part number and contact the PROM manufacturer.IBM token ring E PROMS are always considered New Enhanced Boot PROMs, no matter what year they were manufactured.Make sure the workstation is cabled to the network.Make sure you know the network and node address of the RPL workstation.RENDERAS="SECT1"ID="FM25777"Determining Boot PROM TypeThe RPL workstation installation will ask if you have a IDXID="w12092"BOOK="_idx" COLLECTION="nw41" TIDREF="i495"IDXID="w12093"BOOK="_idx" COLLECTION="nw41" TIDREF="i2911"CLASS=MENUITEM MOREINFO="NONE"New Enhanced Boot PROM or anIDXID="w12094"BOOK="_idx" COLLECTION="nw41" TIDREF="i495"IDXID="w12095"BOOK="_idx" COLLECTION="nw41" TIDREF="i3069"CLASS=MENUITEM MOREINFO="NONE" Older Style Boot PROM.Older style boot PROMs were made before 1992. If you don't know the type of PROM you have, find the part number and contact the PROM manufacturer.Older style boot PROMs don't require RPL.NLM to be loaded on the server; new enhanced boot PROMs do. To load RPL.NLM, see IDREF="FM52148""Procedure" on page 140.PAGENUM=140 ID="BP142"RENDERAS="SECT2"Novell BoardsYou can use RPL with the following Novell boards:TYPE="VERT"NE1000TMNE2000TMNE/2TMThese boards can have either new enhanced boot PROMs or older style boot PROMs.RENDERAS="SECT2"IBM BoardsYou can use RPL with the following IBM boards:MARK=BULLETPCN2LTOKENThese boards are always considered new enhanced boot PROMs.RENDERAS="SECT2"Loading RPL.NLM for IBM Boards or New Enhanced Boot PROMsIf you use IBM boards or Novell boards that support New Enhanced Boot PROMs, use the following procedure.To set up the server to use RPL with this type of workstation, load and bind the RPL loadable module on each server.RENDERAS="SECT3"ID="FM52148"ProcedurePERFORMANCE="REQUIRED"At the server, type FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD RPLRPL.NLM is shipped with NetWare Client for OS/2. It is on CLASS=DISKWSOS2_1 in the RPL directory.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND RPL TO driver PS=servername NODEFAULT
PAGENUM=141 ID="BP143"Replace 
driver with the name of an LAN driver in your server. To bind to more than one driver, use additional bind statements.Replace 
servername with the name of the server that has the RPL files.PERFORMANCE="REQUIRED"For Ethernet PROMs, bind RPL to the 802.2 frame type.The first frame type in NET.CFG must correspond to the frame type that RPL is bound to. For example, if you typed at the server console prompt:MOREINFO="NONE"   BIND RPL TO NE2000 [FRAME=ETHERNET_802.2]The NET.CFG setting on the workstation should look likeMOREINFO="NONE"   link driver ne2000      MOREINFO="NONE" frame ethernet_802.2Where Ethernet_802.2 is the first frame type listed.For more about the RPL loadable module, see 
BOOK="utlrfenu" COLLECTION="nw41"NetWare Utilities Reference.RENDERAS="SECT1"ID="FM86543"Installing OS/2 Files for RPL WorkstationsRENDERAS="SECT2"What Happens When You Install OS/2 FilesWhen you install OS/2 files for RPL workstations, the following actions occur:MARK=BULLETA SYS:RPL2 directory is created on each server you select.All RPL workstations use this directory as if it is their local boot drive. Once RPL users log in, they can access all information in this directory.Since the IDXID="w12096"BOOK="_idx" COLLECTION="nw41" TIDREF="i4404"
SYS:RPL2 directory is on the server and not on a local disk, NetWare security still applies. For example, you can limit RPL users' access to specific directories and files. For more about securing the SYS:RPL2 directory and its subdirectories, see IDREF="FM86497""Creating Users and Granting Rights" on page 150.OS/2 1.3 RPL IDXID="w12097"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"
stations used a directory called SYS:RPL. This directory isn't erased when the SYS:RPL2 directory is created. OS/2 version 1.3 RPL stations and OS/2 version 2.10 RPL stations can both boot on the same network. Every file from workstation drive C: is copied to the SYS:RPL2 directory on the server.PAGENUM=142 ID="BP144"RENDERAS="SECT2"ID="FM18409"ProcedureComplete the steps in this section if you areMARK=BULLETSetting up RPL workstations for the first time.Upgrading existing RPL workstations from OS/2 1.3 to OS/2 2.x.Upgrading OS/2 on the server (i.e., from OS/2 2.0 to OS/2 2.1).Adding a server to the network where RPL workstations attach (only for the server you add).If you use older style boot PROMS, don't do the steps in this section every time you add an RPL workstation to the network. See IDREF="FM29241""Setting Up RPL Workstations" on page 147.RPL files must be installed on all network servers. If some servers don't use RPL support, use the following SET parameter at each server's console prompt, or include it in each server's AUTOEXEC.NCF file:MOREINFO="NONE"SET RESPOND TO GET NEAREST SERVER = OFFIf you set this parameter on each server, the server will not respond to Remote Reset PROMs and it can't boot RPL workstations, but you won't need to install the files for RPL workstations support on that server.For more about SET, see Utilities Reference.We recommend that you establish a separate physical network for RPL users. Put only the servers on this network that are needed to support the number of RPL users you have.If you want, connect this network to other networks at your site through routers. This setup saves time and server space.PERFORMANCE="REQUIRED"On the client workstation, login to the server where you want the OS/2 files for RPL workstations.PERFORMANCE="REQUIRED"Open the NetWare Client for OS/2 installation program. IDREF="FM95517"Figure 11-3 shows how to open the program. 
PAGENUM=143 ID="BP145"LABEL="11-3" FLOAT="0"ID="FM95517"Opening the Installation Program from the Novell GroupFILEREF="c41q11a.tif"The 
CLASS=MENUITEM MOREINFO="NONE"NetWare Requester for OS/2 Installation Utility window appears. Use the online help as necessary.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu, choose 
CLASS=MENUITEM MOREINFO="NONE"Remote workstations...The 
CLASS=MENUITEM MOREINFO="NONE"Remote Workstation Installation window appears.The CLASS=MENUITEM MOREINFO="NONE"Copy All Files and Setup Workstations... option has three separate components: copying OS/2 files, copying RPL files, and setting up RPL workstations. Each of these procedures are explained individually.PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Only Copy OS/2 Files . . . and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.You can also choose other actions from the 
CLASS=MENUITEM MOREINFO="NONE"Remote Workstation Installation screen.PERFORMANCE="REQUIRED"Choose the servers you want the files copied to.You are attached to the servers you select. The files must be installed on all servers on the local net (cable segment with same address).PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.All OS/2 and NetWare Client for OS/2 files are copied to the server.
PAGENUM=144 ID="BP146"PERFORMANCE="REQUIRED"After the files are copied, do the following.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Copy RPL filesCOLNAME=2 ROTATE="0" MOREROWS="0"Without exiting the installation program, go to IDREF="FM35976""Installing RPL Files for RPL Workstations" on page 144.COLNAME=1 ROTATE="0" MOREROWS="0"Add RPL workstations to the networkCOLNAME=2 ROTATE="0" MOREROWS="0"Without exiting the installation program, go to IDREF="FM29241""Setting Up RPL Workstations" on page 147.COLNAME=1 ROTATE="0" MOREROWS="0"Configure NetWare Client for OS/2 for RPL workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Without exiting the installation program, go to IDREF="FM11537""Configuring NetWare Client for OS/2 for RPL Workstations" on page 154. COLNAME=1 ROTATE="0" MOREROWS="0"Exit the installation programCOLNAME=2 ROTATE="0" MOREROWS="0"Choose CLASS=MENUITEM MOREINFO="NONE"Close from the system menu in the upper left corner of the CLASS=MENUITEM MOREINFO="NONE"Installation window.RENDERAS="SECT1"ID="FM35976"ID="FM65768"Installing RPL Files for RPL WorkstationsRENDERAS="SECT2"What Happens When You Install RPL FilesWhen you use the installation program to install RPL workstation support, the following actions occur:MARK=BULLETDirectories are created.Files are copied.RENDERAS="SECT3"ID="FM28360"Directories Are CreatedMARK=BULLETIDXID="w12098"BOOK="_idx" COLLECTION="nw41" TIDREF="i4404"
SYS:RPL2 is created if it doesn't already existThe \USER and \COMPUTER subdirectories are created under SYS:RPL2 on each server. For an illustration of the complete directory structure created when you install RPL workstation support and add RPL workstations, see IDREF="FM29696"Figure 11-2 on page 137. PAGENUM=145 ID="BP147"RENDERAS="SECT3"Files Are CopiedThe following RPL files are copied to the SYS:LOGIN directory: TYPE="VERT"NE2.200NE2000.200NE1000.200RPLOS2.200RBOOT.RPLETHER.RPLTOKEN.RPLThese files have different names than the RPL files used to boot OS/2 1.3. OS/2 1.3 RPL files are also located in the SYS:LOGIN directory.The following files are copied to the SYS:RPL2 directory:MARK=BULLETMINI.IFSMICRO.IFSRENDERAS="SECT2"ProcedureComplete the steps in this section if you areMARK=BULLETSetting up RPL workstations for the first time.Upgrading existing RPL workstations from OS/2 1.3 to OS/2 2.x.Installing a new version of NetWare Client for OS/2.Adding a server to the network where RPL workstations attach (only for the server you add).Don't do the steps in this section every time you want to add an RPL workstation to the network. See IDREF="FM29241""Setting Up RPL Workstations" on page 147.All RPL files must be installed on each server on the network. There is no way to specify which server an RPL workstation will initially establish a connection with.PAGENUM=146 ID="BP148"We recommend that you establish a separate physical network for RPL users. Put only the servers on this network that are needed to support the number of RPL users you have.If you want, connect this network to other networks at your site through routers. This setup saves time and server space.PERFORMANCE="REQUIRED"On the client workstation, open the NetWare Client for OS/2 installation program.IDREF="FM53458"Figure 11-4 shows how to open the program.LABEL="11-4" FLOAT="0"ID="FM53458"Opening the Installation Program from the Novell GroupFILEREF="c41q11a.tif"The 
CLASS=MENUITEM MOREINFO="NONE"NetWare Requester for OS/2 Installation Utility window appears. Use online help as necessary.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu, choose 
CLASS=MENUITEM MOREINFO="NONE"Remote workstations...The 
CLASS=MENUITEM MOREINFO="NONE"Remote Workstation Installation window appears.The CLASS=MENUITEM MOREINFO="NONE"Copy All Files and Setup Workstations... option has three separate components: copying OS/2 files, copying RPL files, and setting up RPL workstations. Each of these procedures are explained individually.PAGENUM=147 ID="BP149"PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Only Copy RIPL Files ...You can also choose other actions from the 
CLASS=MENUITEM MOREINFO="NONE"Remote Workstation Installation screen.PERFORMANCE="REQUIRED"Choose the server you want the RPL files copied to.You will be attached to the servers you select. They must be installed on all servers on the local net (cable segment with same address).PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK. All RPL files are copied to the servers.PERFORMANCE="REQUIRED"Select the source drive for the RPL files.The default is the drive where INSTALL.EXE was loaded. If you loaded INSTALL.EXE from the hard drive, change this to your floppy drive and insert the first installation diskette in it.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"After the files are copied, do the following:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Add RPL workstations to the networkCOLNAME=2 ROTATE="0" MOREROWS="0"Without exiting the installation program, go to IDREF="FM29241""Setting Up RPL Workstations" on page 147.COLNAME=1 ROTATE="0" MOREROWS="0"Configure NetWare Client for OS/2 for RPL workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Without exiting the installation program, go to IDREF="FM11537""Configuring NetWare Client for OS/2 for RPL Workstations" on page 154.COLNAME=1 ROTATE="0" MOREROWS="0"Exit the installation programCOLNAME=2 ROTATE="0" MOREROWS="0"Choose CLASS=MENUITEM MOREINFO="NONE"Close from the system menu in the upper left corner of the CLASS=MENUITEM MOREINFO="NONE"Installation window.RENDERAS="SECT1"ID="FM29241"Setting Up RPL WorkstationsRENDERAS="SECT2"What Happens When You Set Up RPL WorkstationsEach RPL workstation you boot from the network must be added to the RPL setup on the network. You identify to each server the user for that workstation, the node address, and the network board.PAGENUM=148 ID="BP150"RPL workstations are added by running the NetWare Client for OS/2 installation program from a workstation that has OS/2 installed on drive C:.RENDERAS="SECT2"ProcedureComplete the steps in this section on each server if you areMARK=BULLETSetting up RPL workstations for the first time Upgrading existing RPL workstations from OS/2 1.3 to OS/2 2.xAdding RPL workstations to the network Whenever possible, use the same type of IDXID="w12099"BOOK="_idx" COLLECTION="nw41" TIDREF="i2851"
network board in all RPL workstations. This saves you time when you install and configure RPL workstations.If the installation program is already running, go to Step 4.PERFORMANCE="REQUIRED"Log in from the client workstation.PERFORMANCE="REQUIRED"Open the 
CLASS=MENUITEM MOREINFO="NONE"Novell group icon on the desktop. PERFORMANCE="REQUIRED"Choose the 
CLASS=MENUITEM MOREINFO="NONE"Install icon in the 
CLASS=MENUITEM MOREINFO="NONE"Novell-Icon View window.
PAGENUM=149 ID="BP151"LABEL="11-5" FLOAT="0"Opening the Installation Program from the Novell GroupFILEREF="c41q11a.tif"The 
CLASS=MENUITEM MOREINFO="NONE"NetWare Workstation for OS/2 Installation Utility window appears. PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu, choose 
CLASS=MENUITEM MOREINFO="NONE"Remote workstations ...The 
CLASS=MENUITEM MOREINFO="NONE"Remote Workstation Installation menu appears.The CLASS=MENUITEM MOREINFO="NONE"Copy All Files and Setup Workstations... option has three separate components: copying OS/2 files, copying RPL files, and setting up RPL workstations. Each of these procedures are explained individually.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Only SetUp Workstations ...PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.The 
CLASS=MENUITEM MOREINFO="NONE"Select 1 or More File Servers window appears.PERFORMANCE="REQUIRED"Choose servers that you want to define RPL workstations on.For a list of available servers, choose 
CLASS=MENUITEM MOREINFO="NONE"Attach. Then choose the arrow at the end of the 
CLASS=MENUITEM MOREINFO="NONE"Server name field. For more information, use the online help.PERFORMANCE="REQUIRED"When you've selected the servers you want, choose 
CLASS=MENUITEM MOREINFO="NONE"OK.
PAGENUM=150 ID="BP152"The 
CLASS=MENUITEM MOREINFO="NONE"Select the type of BOOT PROM in the target workstation windows appears.PERFORMANCE="REQUIRED"Select the type of BOOT PROM you have.If you have an IBM board or if the board was manufactured during or after 1992, select 
CLASS=MENUITEM MOREINFO="NONE"New Enhanced BOOT PROM.If your board was manufactured before 1992, select 
CLASS=MENUITEM MOREINFO="NONE"Older Style BOOT PROM.If you aren't sure what type of board you have, find the board's part number and contact the board's manufacturer.If you use token ring, the boot PROM is always considered as a new enhanced boot PROM, no matter when it was manufactured.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.The 
CLASS=MENUITEM MOREINFO="NONE"Add Remote Boot Workstation window appears.Different versions of this window appear, depending on the type of boot PROM you selected in Step 9.PERFORMANCE="REQUIRED"Complete all fields in the window.CLASS=MENUITEM MOREINFO="NONE"User name should be the actual name or login name of the person you are setting up the RPL workstation for. CLASS=MENUITEM MOREINFO="NONE"Logical name becomes the name of the subdirectory under that user. For example, if you set up the user name as SUSAN and the logical name as LAB, the path would read RPL2\USER\SUSAN\LAB.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Add.PERFORMANCE="REQUIRED"Exit the installation program.RENDERAS="SECT1"IDXID="w12100"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"IDXID="w12101"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"ID="FM86497"Creating Users and Granting RightsThis procedure only works for NetWare 4 users. NetWare 3 users should use IDXID="w12102"BOOK="_idx" COLLECTION="nw41" TIDREF="i4367"
SYSCON.EXE.To complete the RPL installation, you must have Supervisor object rights to the server that the RPL workstation will attach to.You must set up accounts for RPL workstations. Do the following:PAGENUM=151 ID="BP153"RENDERAS="SECT2"ID="FM47608"ProcedurePERFORMANCE="REQUIRED"Create the IDXID="w12103"BOOK="_idx" COLLECTION="nw41" TIDREF="i3921"IDXID="w12104"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"
RPL User object.IDXID="w12105"BOOK="_idx" COLLECTION="nw41" TIDREF="i4716"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"From the client workstation, log in.PERFORMANCE="REQUIRED"At the C:> prompt, type 
MOREINFO="NONE"NWADMIN.The CLASS=MENUITEM MOREINFO="NONE"NetWare Administrator window appears.PERFORMANCE="REQUIRED"Highlight the Container object that will contain the new user.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Object menu, choose 
CLASS=MENUITEM MOREINFO="NONE"Create.The CLASS=MENUITEM MOREINFO="NONE"New Object window appears.PERFORMANCE="REQUIRED"Select the 
CLASS=MENUITEM MOREINFO="NONE"User icon.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"OK.The CLASS=MENUITEM MOREINFO="NONE"Create User window appears.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Login Name field, type 
MOREINFO="NONE"RPL.RPL is the username each RPL workstation uses to make the initial connection to the network.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Last Name field, type 
MOREINFO="NONE"RPL.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Create.You are returned to the CLASS=MENUITEM MOREINFO="NONE"NetWare Administrator window.PERFORMANCE="REQUIRED"Repeat Steps 1c through 1i to create a User object for each person who will use an RPL workstation.PERFORMANCE="REQUIRED"ID="FM57138"Grant access to the RPL User.Do not require a password for the RPL User object, or the RPL workstations can't make the connection. Protect the account by granting limited access, as explained in IDREF="FM15589"Step 4.The RPL user needs at least read and file scan access to
MARK=BULLETThe SYS:RPL2 directoryThe SYS:RPL2\COMPUTER directory and its subdirectoriesThese directories are created automatically during RPL workstation installation.
PAGENUM=152 ID="BP154"PERFORMANCE="REQUIRED"ID="FM15589"Grant minimal access rights to each 
IDXID="w12106"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"RPL workstation user.All RPL workstations need
MARK=BULLETFile scan and read access to the SYS:RPL2 directoryIDXID="w12107"BOOK="_idx" COLLECTION="nw41" TIDREF="i4404"File scan and read access to the \OS2 and \NETWARE subdirectories under SYS:RPL2Supervisory access rights to their home directories under SYS:RPL2\USERThese directories are created automatically during RPL workstation installation.Users do not have to be given access to other users' home directories under SYS:RPL2\USER.For more about NetWare security and granting and prohibiting access, see BOOK="superenu" COLLECTION="nw41"Supervising the Network.Since the SYS:RPL2 directory becomes the root of drive C: for all RPL workstations, all RPL users need access to this area. Do not store confidential files in this directory. Instead, store them in another network directory where access can be restricted.You might want to warn users about this lack of privacy and encourage them to store data in their home directories (for example, C:\USER\MARY) or in another location on the network.RENDERAS="SECT2"Using an RPL Workstation with Virtual DOSRPL workstations are unable to re-map drive C:. Even if you are using global DOS, RPL workstations treat global DOS the same as private DOS.For example, if you were in global DOS and remapped drive C:, the remapped drive C: will not show up when you go to a private DOS session.RENDERAS="SECT1"ID="FM83948"Using RPL on Workstations with Hard DisksTo use RPL on a workstation with a hard disk, label your hard drive a drive other than C:.Drive C: must be assigned to the SYS:RPL2 network directory. OS/2 thinks this network directory is the local drive C:. PAGENUM=153 ID="BP155"Also, you might need to determine whether your hard disk has an operating system or not. You can format it and use it to store your OS/2 SWAPPER.DAT file. This will cut down on network traffic.RENDERAS="SECT2"Placing SWAPPER.DAT LocallyRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Go to the home directory on the network for the user who will be using the RPL workstation.For example, if JOHN will be using the RPL workstation with a hard drive, go to the following directory:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:RPL2\USER\JOHNEach user's home directory on the network contains that user's CONFIG.SYS file and several other OS/2 files. 
IDREF="FM29696"Figure 11-2 on page 137 shows the network directory structure for RPL workstations. PERFORMANCE="REQUIRED"Using a text editor, open the CONFIG.SYS file. PERFORMANCE="REQUIRED"In the CONFIG.SYS file, find the line that designates the SWAPPATH.You can search for SWAPPATH. The line looks like the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SWAPPATH=C:\USER\JOHN 2048 2048Remember that to OS/2 the SYS:RPL2 directory is drive C:.PERFORMANCE="REQUIRED"Change the SWAPPATH line to point to the local hard drive.For example, to point to the root of local drive D:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SWAPPATH=D:\ 2048 2048PERFORMANCE="REQUIRED"Save and exit the CONFIG.SYS file.When you boot the RPL workstation, the SWAPPER.DAT will be stored locally.
PAGENUM=154 ID="BP156"RENDERAS="SECT1"ID="FM11537"ID="FM72905"ID="FM72733"ConfiguringIDXID="w12108"BOOK="_idx" COLLECTION="nw41" TIDREF="i3755"IDXID="w12109"BOOK="_idx" COLLECTION="nw41" TIDREF="i762"
 NetWare Client for OS/2 for RPL WorkstationsConfigure NetWare Client for OS/2 for RPL workstations by running the NetWare Client for OS/2 installation program and choosing CLASS=MENUITEM MOREINFO="NONE"Remote workstations . . . from the CLASS=MENUITEM MOREINFO="NONE"Configuration menu.When you configure RPL workstations, the NetWare Client for OS/2 installation program puts a NET.CFG file in the home directory of the users you specify. The home directory is located under SYS:RPL2\USER on each server on the local network.The NET.CFG you create with the installation program should be identical on all servers on the local network so RPL workstations boot the same way each time. For example, if user JOHN has a NET.CFG file in his user directory on SERVER1, then a copy of the same NET.CFG file should be placed in his home directory on SERVER2. The installation program puts a line in each user's IDXID="w12110"BOOK="_idx" COLLECTION="nw41" TIDREF="i771"
CONFIG.WSS file in the workstation subdirectory, telling NetWare Client for OS/2 where to find the NET.CFG file. For example, for John's NET.CFG file, the installation program puts in the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\NET.CFG C:\USER\JOHN\NET.CFGRemember that the SYS:RPL2 directory becomes the root of the C: drive.If the RPL workstation is using the Ethernet frame type, the frame type specified in the NET.CFG file must be the same as the frame type used by the boot PROM.New Enhanced Boot PROMs use 802.2. Older Style Boot PROMs use 802.3LABEL="12"PAGENUM=155 ID="BP157"ID="FM99776"Improving Speed and SecurityCOLS=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="FM81781"Improving Speed by Using Packet Burst COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM81781"155COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM98381"Improving Speed by Using Large Internet Packets  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98381"156COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94412"Improving Security by Using NCP Packet Signature  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94412"156ID="FM54026"This chapter discusses three features that help to improve speed and security on your network.RENDERAS="SECT1"ID="FM81781"IDXID="w12111"BOOK="_idx" COLLECTION="nw41" TIDREF="i3103"
Improving Speed by Using Packet Burst IDXID="w12112"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"IDXID="w12113"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"IDXID="w12114"BOOK="_idx" COLLECTION="nw41" TIDREF="i4223"Packet BurstTM is a protocol that speeds the transfer of multiple-packet NCP reads and writes.Packet Burst eliminates the need to sequence and acknowledge each packet. With Packet Burst, the server or client sends a whole set (or burst) of packets before it requires an acknowledgment.Packet Burst reduces network traffic by allowing multiple packets to be acknowledged. Packet Burst also monitors dropped packets and retransmits only the missing packets.At 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 workstation and a server, the workstation uses Packet Burst when an application requests to write more than three times the maximum packet size of data. This means that an application doesn't have to be aware of Packet Burst.PAGENUM=156 ID="BP158"RENDERAS="SECT2"Disabling Packet BurstIDXID="w12115"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"Packet Burst is enabled at the workstation by default. You can disable it by adding the following to the workstation's NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
packet burst off
ID="FM49792"RENDERAS="SECT1"ID="FM98381"IDXID="w12116"BOOK="_idx" COLLECTION="nw41" TIDREF="i3103"
Improving Speed by Using IDXID="w12117"BOOK="_idx" COLLECTION="nw41" TIDREF="i2068"IDXID="w12118"BOOK="_idx" COLLECTION="nw41" TIDREF="i4223"
Large Internet PacketsLarge Internet Packet (LIP) functionality allows the internet packet size to be increased from the default 576 bytes. By allowing the NetWare packet size to be increased, LIP enhances transmission over bridges and routers.In NetWare 4, the workstation requests an acceptable packet size. However, unlike previous versions of NetWare, the server doesn't default to 576 bytes when a router is detected.Instead, the workstation attempts to send larger packets to the server. The largest packet size that the server accepts is the packet size used to communicate.RENDERAS="SECT2"Disabling Large Internet PacketsLIP functionality is enabled by default on the workstation. To disable it, enter the following in the NET.CFG file: FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
large internet packets offRENDERAS="SECT1"ID="FM94412"IDXID="w12119"BOOK="_idx" COLLECTION="nw41" TIDREF="i3103"IDXID="w12120"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
Improving IDXID="w12121"BOOK="_idx" COLLECTION="nw41" TIDREF="i4002"
Security by Using IDXID="w12122"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"
NCP Packet SignatureNetWare Core ProtocolTM (NCP) Packet Signature is an enhanced security feature that protects servers and clients using NCP by preventing packet forgery.Without NCP Packet Signature, a network client can pose as a more privileged client to send a forged NCP request to a NetWare server. PAGENUM=157 ID="BP159"By forging the proper NCP request packet, an intruder could gain Supervisor rights and access to all network resources.NCP Packet Signature prevents packet forgery by requiring the server and the client to "sign" each NCP packet. The packet signature changes with every packet.NCP packets with incorrect signatures are discarded without breaking the client's connection with the server. However, an alert message about the invalid packet is sent to the error log, the affected client, and the server. The message contains the login name and station address of the affected client.A two-part process between client and server determines NCP Packet Signature:MARK=BULLETAt LOGIN, the server and client determine a shared, secret key known as the session key.For each request or response packet, the server and client calculate a signature based on the session key, a "fingerprint" algorithm, and the previous packet's signature. The unique signature is appended to the NCP packet.If NCP Packet Signature is installed correctly on the server and all of its clients, it is virtually impossible to forge a valid NCP packet.The Packet Burst loadable module, PBURST.NLM (NetWare 3.11 only), must be loaded on NetWare servers for NCP Packet Signature to work. However, using Packet Burst to transfer data between servers and clients is optional.RENDERAS="SECT2"NCP Packet Signature OptionsBecause packet signature consumes CPU resources and slows performance, both for the client and the server, NCP Packet Signature is optional.Several signature options are available, ranging from never signing NCP packets to always signing NCP packets. Servers and clients both have four signature levels that can be set.The signature options for servers and clients combine to determine the level of NCP Packet Signature on the network.PAGENUM=158 ID="BP160"Some combinations of server and client packet signature levels may slow performance. However, low CPU-demand systems may not show any performance degradation. Network supervisors can choose the packet signature level that meets both their performance needs and their security requirements.RENDERAS="SECT2"Server LevelsServer packet signature levels are assigned by a SET parameter. See 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference.RENDERAS="SECT2"Client LevelsPacket signature levels at the workstation are assigned by using the following NET.CFG option:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
signature level 
numberReplace number with 0, 1, 2, or 3. The default is 1.LABEL="12-1" PGWIDE=0 TOCENTRY="1" 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"NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Client doesn't sign packets (login fails if server is set to 3)COLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets only if the server requests it (server option is 2 or higher)COLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets if the server is capable of signing (server option is 1 or higher)COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Client signs packets and requires the server to sign packets (or login will fail)RENDERAS="SECT2"Effective Packet Signature LevelsThe packet signature levels for server and client interact to create the effective packet signature. Some combinations of server and client levels do not allow logging in.PAGENUM=159 ID="BP161"IDREF="FM67386"Table 12-2 shows the interactive relationship between the server packet signature levels and the client signature levels.LABEL="12-2" PGWIDE=1 TOCENTRY="1"ID="FM67386" Effective Packet Signature of Server and ClientCOLS=5 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="7*"COLNAME=4 COLWIDTH="7*"COLNAME=5 COLWIDTH="7*"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 = 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 loginCOLNAME=1 ROTATE="0" MOREROWS="0"Client = 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 = 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 = 3COLNAME=2 ROTATE="0" MOREROWS="0"No loginCOLNAME=3 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=4 ROTATE="0" MOREROWS="0"Packet signatureCOLNAME=5 ROTATE="0" MOREROWS="0"Packet signatureRENDERAS="SECT2"When to Use NCP Packet SignatureIDXID="w12123"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"NCP Packet Signature is not required for every installation. Some network supervisors might choose not to use NCP Packet Signature because they can tolerate certain security risks.You may not need to use NCP Packet Signature ifMARK=BULLETOnly executable programs reside on the server.All workstation users on the network are known and trusted by the supervisor.Data on the server is not sensitive; loss or corruption of this data will not impact operations.You may want to use NCP Packet Signature ifMARK=BULLETAn untrustworthy user uses a workstation on the network.Someone can easily access the network cabling system.There is an unattended, publicly accessible workstation on the network.PAGENUM=160 ID="BP162"The default NCP Packet Signature level is 1 for clients and 2 for servers. In general, this setting provides the most flexibility while still offering protection from forged packets. Following are some examples of using different signature levels.RENDERAS="SECT3"All Information on the Server Is SensitiveIf an intruder gains access to any information on the NetWare server, it could damage the company.The network supervisor should set the server to level 3 and all clients to level 3 for maximum protection.RENDERAS="SECT3"Sensitive and Non-Sensitive Information Reside on the Same ServerThe server has a directory for executable programs and a separate directory for corporate finances.The network supervisor should set the server to level 2 and the clients (including himself) that need access to corporate finances to level 3. All other clients remain at the default, level 1.RENDERAS="SECT3"Users Often Change Locations and WorkstationsThe network supervisor is uncertain which employees will be using which workstations, and the server contains sensitive data.The network supervisor should set the server to level 3. Clients should remain at the default, level 1.RENDERAS="SECT3"Workstation Is Publicly AccessibleAn unattended workstation is set up for public access to non-sensitive information, but another server on the network contains sensitive information.The network supervisor should set the sensitive server to level 3 and the unattended client to level 0.PAGENUM=161 ID="BP163"RENDERAS="SECT2"NCP Packet Signature Troubleshooting TipsIDXID="w12124"BOOK="_idx" COLLECTION="nw41" TIDREF="i2621"This section describes some solutions to problems that may be associated with using NCP Packet Signature.RENDERAS="SECT3"Clients Are Not Signing PacketsMake sure each OS/2 workstation has NetWare ClientTM for OS/2 installed.Make sure that NCP Packet Signature is not turned off in the NET.CFG file. RENDERAS="SECT3"Clients Cannot Log InIDXID="w12125"BOOK="_idx" COLLECTION="nw41" TIDREF="i782"IDXID="w12126"BOOK="_idx" COLLECTION="nw41" TIDREF="i2190"Make sure each workstation has NetWare Client for OS/2 installed. The following situations do not allow logging in:MARK=BULLETServer packet signature level=3, client packet signature level=0Server packet signature level=0, client packet signature level=3Utilities are old and do not support NCP Packet SignatureThe NetWare Client for OS/2 software is not version 2.1 and does not support NCP Packet Signature.RENDERAS="SECT3""Error Receiving From the Network" MessageThe client is using an old LOGIN.EXE file that does not include NCP Packet Signature. Make sure the new LOGIN.EXE and other new utilities are installed in the \OS2 subdirectory on all servers.RENDERAS="SECT3"Unsecure Clients Log In to Secure ServerThe clients are using an old LOGIN.EXE file that does not include NCP Packet Signature. Make sure the new LOGIN.EXE and other new utilities are installed in the \OS2 subdirectory on all servers. PAGENUM=162 ID="BP164"Add a preferred server statement to the NET.CFG file for all clients that have access to secure servers (level 3).LABEL="13"PAGENUM=163 ID="BP165"ID="FM57010"Using Token Ring NetworksCOLS=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="FM19613"Overview COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM19613"163COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM52823"Installing Source-Routing on the Server COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM52823"163COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80219"Installing Source-Routing on the Workstation  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80219"164COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55132"Configuring Source-Routing on the Workstation  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55132"165RENDERAS="SECT1"ID="FM19613"OverviewIDXID="w12127"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"IDXID="w12128"BOOK="_idx" COLLECTION="nw41" TIDREF="i4218"
If your token ring network includes IBM* source-routing bridges, your computers use source routing to communicate across those bridges.This chapter explains how to install and configure source routing on NetWare® servers and OS/2* workstations.If your network requires source routing, install source-routing software on both workstations and servers. Novell's source-routing software includesMARK=BULLETROUTE.NLM (for servers)ROUTE.SYS (for OS/2 client workstations)This software routes only IPXTM packets.RENDERAS="SECT1"ID="FM52823"Installing IDXID="w12129"BOOK="_idx" COLLECTION="nw41" TIDREF="i4218"
Source-Routing on the ServerIDXID="w12130"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"At the server console, load ROUTE.NLM by typingPAGENUM=164 ID="BP166"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ROUTEROUTE.NLM is located in the SYS:SYSTEM directory. You can load it with command line parameters. You can also load ROUTE from a startup file. See 

BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference.PERFORMANCE="REQUIRED"(Conditional) If you have two network boards in your server, load ROUTE.NLM again.Use the "board" parameter to specify a board number. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ROUTE BOARD=02You can change a source-routing parameter after ROUTE is loaded. Type the LOAD ROUTE
MOREINFO="NONE"IDXID="w12131"BOOK="_idx" COLLECTION="nw41" TIDREF="i3896" command followed by the parameter you want to change. RENDERAS="SECT1"ID="FM80219"Installing Source-IDXID="w12132"BOOK="_idx" COLLECTION="nw41" TIDREF="i4218"
Routing on the WorkstationIDXID="w12133"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXInstall Netware ClientTM for OS/2 with a TOKEN ODI driver.Understand source-routing. (See the September 1990 Novell Application Notes.)RENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED"Using a text editor, open the CONFIG.SYS file.For example, to use the OS/2 System Editor at an OS/2 command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"E C:\CONFIG.SYSCONFIG.SYS is always located in the root of your boot drive. PERFORMANCE="REQUIRED"In the NetWare Client for OS/2 lines, find the line loading your TOKEN ODI driver.If you use Novell-supplied ODITM drivers, the driver is called TOKEN.SYS.If you use LANSUP.SYS and an NDIS driver, you do not have an ODI driver loaded. In this case, find LANSUP.SYS.PAGENUM=165 ID="BP167"PERFORMANCE="REQUIRED"After the line that loads the TOKEN ODI driver, add a line to load the ROUTE.SYS driver.Specify the location of ROUTE.SYS. ROUTE.SYS is located where the other NetWare Client for OS/2 files are, usually in C:\NETWARE. For example, to load ROUTE.SYS, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\ROUTE.SYSPERFORMANCE="REQUIRED"Save and exit the CONFIG.SYS file. PERFORMANCE="REQUIRED"Use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to reboot your machine. RENDERAS="SECT1"ID="FM55132"Configuring Source-RoutingIDXID="w12134"BOOK="_idx" COLLECTION="nw41" TIDREF="i4218"
 on the WorkstationFollow the procedures in this section toMARK=BULLETDetermine whether you need to configure source routing, and Configure source routing, if needed. RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXInstall NetWare Client for OS/2.Install source routing on the server. For instructions, see IDREF="FM52823""Installing Source-Routing on the Server" on page 163.Install source routing on the workstation.Understand source-routing thoroughly. This section does not explain source-routing terminology or how packets are routed. See related IBM publications, such as IBM Token Ring Network Architecture Reference, or the September 1990 Novell Application Notes.RENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED"Start the NetWare Client for OS/2 Installation program.You can choose the 
CLASS=MENUITEM MOREINFO="NONE"Installation icon from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop.
PAGENUM=166 ID="BP168"PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"This workstation ... from the 
CLASS=MENUITEM MOREINFO="NONE"Configuration menu.PERFORMANCE="REQUIRED"Verify the location of NET.CFG and choose 
CLASS=MENUITEM MOREINFO="NONE"Edit.The 
CLASS=MENUITEM MOREINFO="NONE"Edit NET.CFG window appears. See 
IDREF="FM88360"Figure 13-1.
 You can cut and paste text from the help window at the bottom of the screen to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents window. Use the following keys:LABEL="13-1" PGWIDE=0 TOCENTRY="1" Key Definitions for the NET.CFG WindowCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Highlight textCOLNAME=2 ROTATE="0" MOREROWS="0"Click and drag with the mouse, or move the cursor with the arrow keys while holding down the MOREINFO="NONE"<Shift> keyCOLNAME=1 ROTATE="0" MOREROWS="0"Copy textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Cut text (text will reappear the next time you refresh the window)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Delete>COLNAME=1 ROTATE="0" MOREROWS="0"Paste textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Delete text (deleted text cannot be pasted)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Delete>PAGENUM=167 ID="BP169"LABEL="13-1" FLOAT="0"ID="FM88360"Editing NET.CFG for Source-RoutingFILEREF="c41q70a.tif"PAGENUM=168 ID="BP170"PERFORMANCE="REQUIRED"Select "Token-Ring source routing" from the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box on the left of your screen.PERFORMANCE="REQUIRED"Determine whether to change the configuration for the "def", "gbr", "mbr", "nodes," and "board" settings under "Token-Ring source routing."PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select one of the five settings.Example: select "def".PERFORMANCE="REQUIRED"Read the help window at the bottom of the screen to determine whether to change the configuration for the setting. You can choose the CLASS=MENUITEM MOREINFO="NONE"Usage, CLASS=MENUITEM MOREINFO="NONE"Description, and CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of the window for more about the setting you've selected.PERFORMANCE="REQUIRED"(Optional) To change the configuration, add the configuration lines (as shown in the 
CLASS=MENUITEM MOREINFO="NONE"Usage help window) in the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box.You must follow the format requirements explained in the "Format of NET.CFG Options" topic. To see these requirements, select this topic from the CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box and choose CLASS=MENUITEM MOREINFO="NONE"Usage.Repeat Steps 5a through 5c for each setting. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save.PERFORMANCE="REQUIRED"Exit the NetWare Client for OS/2 Installation program and use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to restart your computer.LABEL="14"PAGENUM=169 ID="BP171"Using Named PipesCOLS=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="FM25310"Installing Named Pipes for OS/2  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM25310"169COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM50371"Configuring Named Pipes for OS/2  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50371"171COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM18112"Using the Named Pipes Extender for DOS  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18112"175COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM91398"Special Instructions for SQL Client Workstations  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91398"180RENDERAS="SECT1"ID="FM25310"Installing Named Pipes for OS/2You must install Named Pipes support on each computer that will use Named Pipes on the network. In most cases, you must also set configuration options for the protocol. ID="FM26379"Named Pipes support between sessions on a single OS/2* workstation is provided by the OS/2 operating system. However, if you need OS/2 sessions to communicate with other computers on the network using Named Pipes, you must install remote Named Pipes support.RENDERAS="SECT2"PrerequisiteMARK=CHECKBOXInstall your Named Pipes distributed application. See the documentation for your application. RENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED"Start the NetWare ClientTM for OS/2 Installation program. If NetWare Client for OS/2 is not installed, you can start the program from your 
CLASS=DISKWSOS2_1 diskette. Type 
MOREINFO="NONE"INSTALL. 
PAGENUM=170 ID="BP172"You can install NetWare Client for OS/2 at the same time you install Named Pipes. If NetWare Client for OS/2 is already installed, start the program by choosing 
CLASS=MENUITEM MOREINFO="NONE"Installation from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Requester on Workstation from the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu. PERFORMANCE="REQUIRED"Verify the target directory and source drive and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select an action from the
CLASS=MENUITEM MOREINFO="NONE" Requester Installation screen, based on whether NetWare Client for OS/2 is installed.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is not installed, select 
CLASS=MENUITEM MOREINFO="NONE"Edit CONFIG.SYS and Copy All Files... and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is installed, select
CLASS=MENUITEM MOREINFO="NONE" Only Edit CONFIG.SYS... and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select the ODI LAN driver for your network board and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue...PERFORMANCE="REQUIRED"Select your preferences for NetWare support for DOS and MS Windows applications and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue...PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"Remote Named Pipes Support. PERFORMANCE="REQUIRED"Set up your workstation as a Named Pipes client or server.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Client Support Only to set up your workstation as a Named Pipes application client. If your workstation will be a client for the SQL Server distributed application, you must do some additional steps. After completing this section and IDREF="FM50371""Configuring Named Pipes for OS/2" on page 171, go to IDREF="FM91398""Special Instructions for SQL Client Workstations" on page 180. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Client and Server Support and type a machine name to set up your workstation as a Named Pipes application server. Choose CLASS=MENUITEM MOREINFO="NONE"Help for syntax requirements for the machine name. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save... PAGENUM=171 ID="BP173"PERFORMANCE="REQUIRED"Verify the filename and location and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.If you have not installed NetWare Client for OS/2, the 
CLASS=MENUITEM MOREINFO="NONE"Copy Requester Files screen appears. Continue with 
IDREF="FM28749"Step 11. If you have installed NetWare Client for OS/2, the main installation menu appears.PERFORMANCE="REQUIRED"ID="FM28749"Choose 
CLASS=MENUITEM MOREINFO="NONE"Copy and follow the screens to finish installing NetWare Client for OS/2. RENDERAS="SECT1"ID="FM50371"Configuring Named Pipes for OS/2IDXID="w12135"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"IDXID="w12136"BOOK="_idx" COLLECTION="nw41" TIDREF="i762"Novell's Named Pipes support comes with default configuration settings. You might want to customize the configuration. Follow the instructions below toMARK=BULLETDetermine whether you need to change the default configuration for Named Pipes and SPXTM.Change the configuration if necessary. You can change the configuration for such features as MARK=BULLETAvailable number of client and server sessions.Number of SPX sessions available for Named Pipes and other SPX communication (Named Pipes uses SPX).RENDERAS="SECT2"PrerequisiteMARK=CHECKBOXNetWare Client for OS/2 must be installed.RENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED"Start the NetWare Client for OS/2 Installation program. The program might already be running if you just installed Named Pipes support. If it is not running, choose 
CLASS=MENUITEM MOREINFO="NONE"Installation from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"This workstation... from the 
CLASS=MENUITEM MOREINFO="NONE"Configuration menu. PERFORMANCE="REQUIRED"Verify the location of the NET.CFG file and choose 
CLASS=MENUITEM MOREINFO="NONE"Edit.
PAGENUM=172 ID="BP174"The 
CLASS=MENUITEM MOREINFO="NONE"Edit NET.CFG window appears. See 
IDREF="FM56085"Figure 14-1. You can cut and paste text from the help window at the bottom of the screen to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents window. Use the following keys:LABEL="14-1" PGWIDE=0 TOCENTRY="1" Key Definitions for the NET.CFG WindowCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Highlight textCOLNAME=2 ROTATE="0" MOREROWS="0"Click and drag with the mouse, or move the cursor with the arrow keys while holding down the MOREINFO="NONE"<Shift> keyCOLNAME=1 ROTATE="0" MOREROWS="0"Copy textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Cut text (text will reappear the next time you refresh the window)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Delete>COLNAME=1 ROTATE="0" MOREROWS="0"Paste textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Delete text (deleted text cannot be pasted)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Delete>PAGENUM=173 ID="BP175"LABEL="14-1" FLOAT="0"ID="FM56085"Editing NET.CFG for Named PipesFILEREF="c41q69a.tif"PAGENUM=174 ID="BP176"PERFORMANCE="REQUIRED"Select "Named Pipes" from the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box on the left of your screen. PERFORMANCE="REQUIRED"Determine whether to change the configuration for the "client sessions" and "server sessions" settings under "Named Pipes."If you decide not to change the configuration for a setting, no action is required for that setting.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select one of the three settings. For example, select "client sessions."PERFORMANCE="REQUIRED"Read the help window at the bottom of the screen to determine whether to change the configuration for the setting. You can choose the CLASS=MENUITEM MOREINFO="NONE"Usage, CLASS=MENUITEM MOREINFO="NONE"Description, and CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of your screen for more about the setting you've selected. PERFORMANCE="REQUIRED"(Optional) To change the configuration, add the configuration lines (shown in the 
CLASS=MENUITEM MOREINFO="NONE"Usage help window) to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box.You must follow the format requirements explained in the "Format of NET.CFG Options" topic. To see these requirements, select this topic from the CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box and choose CLASS=MENUITEM MOREINFO="NONE"Usage.Repeat Steps 5a through 5c for each setting.PERFORMANCE="REQUIRED"Select "Protocol Stack SPX" from the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box on the left of your screen.PERFORMANCE="REQUIRED"Select the "sessions" setting under "Protocol Stack SPX."PERFORMANCE="REQUIRED"Read the help window at the bottom of the screen to determine whether to change the configuration for "sessions."You can choose the 
CLASS=MENUITEM MOREINFO="NONE"Usage, 
CLASS=MENUITEM MOREINFO="NONE"Description, and 
CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of your screen for more about the setting you've selected. PERFORMANCE="REQUIRED"(Optional) To change the configuration, add the configuration lines (shown in the 
CLASS=MENUITEM MOREINFO="NONE"Usage help window) to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box.If you decide not to change the configuration, no action is required.
PAGENUM=175 ID="BP177"You must follow the format requirements explained in the Format of NET.CFG Options topic. To see these requirements, select this topic from the CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box and choose CLASS=MENUITEM MOREINFO="NONE"Usage.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save.PERFORMANCE="REQUIRED"Exit the NetWare Client for OS/2 Installation program.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If your workstation will be a client for the SQL Server distributed application, close the installation program and go to 
IDREF="FM91398""Special Instructions for SQL Client Workstations" on page 180. 
Do not restart your computer.PERFORMANCE="REQUIRED"If your workstation will not be an SQL client, close the installation program and use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to restart your computer.RENDERAS="SECT1"ID="FM18112"IDXID="w12137"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"
Using the Named Pipes Extender for DOSThis is for users of real DOS only.The Named Pipes extender for DOS is a terminate-and-stay-resident (TSR) program that extends the capability of DOS to include use of remote Named Pipes. You must have an OS/2 Named Pipes server on your network to use this extenderThere are two reasons to use the Named Pipes Extender for DOS:MARK=BULLETIf you don't want to use protected mode Named Pipes drivers in the OS/2 CONFIG.SYS.If you have a second network board and want to load DOS Named Pipes on top of separate DOS ODI drivers.If you use a DOS driver, you lose the multi-processing functionality of OS/2. This section explains how to install and configure the extender.PAGENUM=176 ID="BP178"RENDERAS="SECT2"Loading the Extender into MemoryRENDERAS="SECT3"PrerequisiteMARK=CHECKBOXThe workstation on which you install the extender must be running DOS 3.3 or above.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the WSDOS_1 diskette into drive A:.PERFORMANCE="REQUIRED"Change to drive A:.PERFORMANCE="REQUIRED"Type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNPThe extender is now loaded in memory.PERFORMANCE="REQUIRED"Remove the diskette.PERFORMANCE="REQUIRED"For a report of the status of the Named Pipes extender, at the DOS prompt type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNP /IYour OS/2 workstation may require up to one minute after you run the extender for DOS before can run a Named Pipes application.RENDERAS="SECT2"Unloading the Extender from MemoryTo unload the extender, at the DOS prompt typeFORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNP /URENDERAS="SECT2"Loading the Extender AutomaticallyTo have the extender loaded into memory each time you boot your workstation, follow these steps.PAGENUM=177 ID="BP179"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the WSDOS_1 diskette into drive A:.PERFORMANCE="REQUIRED"Copy the following file to the boot drive (hard drive or floppy diskette):
FORMAT="LINESPECIFIC"MOREINFO="NONE"COPY A:\DOSNP.EXEPERFORMANCE="REQUIRED"Add a line to your AUTOEXEC.BAT file that executes DOSNP.EXE that you put on the boot drive.This line should be placed 
after the line that loads IPX.COM and 
before the line that loads NetWare Client for DOS and MS Windows (usually called VLM.EXE).PERFORMANCE="REQUIRED"Remove the diskette.Each time you boot the workstation, the extender is loaded into memory.RENDERAS="SECT2"IDXID="w12138"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"Configuring the Named Pipes ExtenderYou can use NET.CFG to specify various options of the Named Pipes extender. The Named Pipes DOS extender (DOSNP) can operate in two modes:MARK=BULLETIDXID="w12139"BOOK="_idx" COLLECTION="nw41" TIDREF="i966"Default mode (NETX.EXE loaded prior to DOSNP.EXE)IDXID="w12140"BOOK="_idx" COLLECTION="nw41" TIDREF="i3286"
Peer mode (NETX.EXE not loaded)In default mode, the DOSNP extender will query the NetWare server or IPX-compliant router whenever it needs a Named Pipes server resource.In peer mode, a local name table is created and maintained using Service Advertising Protocol (SAP) broadcasts from Named Pipes servers.Using the "Maximum Machine Names" setting changes the DOSNP extender from default mode to peer mode.The following characteristics of the extender can be specified in NET.CFG.TYPE="VERT"Maximum machine namesMaximum sessionsMaximum open Named PipesMaximum communication buffersPAGENUM=178 ID="BP180"RENDERAS="SECT3"Maximum Machine NamesRENDERAS="SECT4"DescriptionControls the number of Named Pipe servers with which the extender can communicate in peer mode.Using the Maximum Machine Names setting changes the DOSNP extender from default mode to peer mode.RENDERAS="SECT4"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX MACHINE NAMES = numberReplace number with the number of Named Pipes servers you want cached on the DOS machine.TYPE="VERT"Range: 4 to 50Default: 10RENDERAS="SECT4"ExampleThe following line in NET.CFG changes the number of Named Pipes servers that the workstation can communicate with from 10 to 14:FORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX MACHINE NAMES = 14RENDERAS="SECT3"Maximum SessionsRENDERAS="SECT4"DescriptionControls the number of Named Pipes servers the extender can communicate with in default mode. This parameter is not used in peer mode.If both "Maximum Machine Names" and "Maximum Sessions" are used, the setting for "Maximum Machine Names" overrides the setting used for "Maximum Sessions."RENDERAS="SECT4"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX SESSIONS = number
PAGENUM=179 ID="BP181"Replace number with the maximum number of Named Pipes servers you want cached on your workstation.TYPE="VERT"Range: 4 to 50Default: 10RENDERAS="SECT4"ExampleThe following line in NET.CFG changes the maximum sessions of Named Pipes the workstation can communicate with from 10 to 25:FORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX SESSIONS = 25RENDERAS="SECT3"Maximum Open Named PipesRENDERAS="SECT4"DescriptionSpecifies the maximum number of Named Pipes the workstation can have open simultaneously.RENDERAS="SECT4"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"NP MAX OPEN NAMED PIPES = numberReplace number with the maximum number of Named Pipes that can be open simultaneously.TYPE="VERT"Range: 4 to 128Default: 4RENDERAS="SECT4"ExampleThe following line in NET.CFG changes the maximum number of pipes the workstation can have open simultaneously from the default to 6:FORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX OPEN NAMED PIPES = 6
PAGENUM=180 ID="BP182"RENDERAS="SECT3"Maximum Communication BuffersRENDERAS="SECT4"DescriptionSpecifies the number of communication buffers that the extender can use to transmit data to and receive data from the Named Pipes server.RENDERAS="SECT4"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX COMM BUFFERS = numberReplace number with the maximum number of communication buffers the extender can use to communicate with the Named Pipes server.TYPE="VERT"Range: 4 to 40Default: 6RENDERAS="SECT4"ExampleThe following line in NET.CFG changes the number of communication buffers that the extender can use to communicate with the Named Pipes server from 6 to 10:FORMAT="LINESPECIFIC"MOREINFO="NONE"NP MAX COMM BUFFERS = 10RENDERAS="SECT1"ID="FM91398"Special Instructions for SQL Client WorkstationsIDXID="w12141"BOOK="_idx" COLLECTION="nw41" TIDREF="i4246"OS/2 client workstations for the SQL Server distributed application must use special versions of NETAPI.DLL and NETOEM.DLL. These files are contained in a \SQL directory on the CLASS=DISKWSOS2_1 diskette. The \SQL IDXID="w12142"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"
NETAPI.DLL contains everything that the default NETAPI.DLL contains (including the NETBIOS calls), as well as additional function calls required by SQL clients and servers. Complete the following steps to copy these files to the correct location.RENDERAS="SECT2"Procedure PERFORMANCE="REQUIRED"Insert the CLASS=DISKWSOS2_1 diskette into a floppy disk drive.PAGENUM=181 ID="BP183"PERFORMANCE="REQUIRED"Copy the existing NETAPI.DLL located in the \NETWARE subdirectory to NETAPI.BAK.PERFORMANCE="REQUIRED"Create a \NETWARE\INSTALL$.NEW subdirectory.PERFORMANCE="REQUIRED"Copy the NETAPI.DLL and NETOEM.DLL files from the \SQL subdirectory on the diskette to the \NETWARE\INSTALL$.NEW subdirectory. Be sure to copy the files from the \SQL directory, since there is also a NETAPI.DLL in the root directory on the diskette. The two NETAPI.DLL files are not the same.The \SQL NETAPI.DLL emulates features of LAN Manager support that are required for SQL clients. However, this NETAPI.DLL does not provide full LAN Manager support. An application that assumes full LAN Manager support if it finds any LAN Manager calls may not run properly. PERFORMANCE="REQUIRED"Use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to restart your computer. LABEL="15"PAGENUM=183 ID="BP184"ID="FM33934"Using NETBIOSCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicsCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM51130"Overview  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM51130"183COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM75002"Determining Which NetBIOS Drivers to Set Up  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM75002"184COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM79688"Setting Up the Novell NetBIOS Driver COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM79688"188COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM40784"Configuring NETBIOS.OS2 with PROTOCOL.INI COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40784"195ID="FM58219"The NetBIOS protocol was designed for small scale networks. While Novell has added functionality to the original specification, Novell's NetBIOS emulation still works most effectively with small scale networks. We recommend that you use SPXTM instead of NetBIOS if your applications support SPX, your network contains several thousand workstations, and your LAN segments are interconnected with more than one router.RENDERAS="SECT1"ID="FM51130"OverviewIDXID="w12143"BOOK="_idx" COLLECTION="nw41" TIDREF="i2649"IDXID="w12144"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"This chapter explains how to set up Novell's NetBIOS driver and how to configure your workstation for NetBIOS when you also have IBM's Extended Services or LAN Services NetBIOS installed.NetWare ClientTM for OS/2* provides a NetBIOS driver, NETBIOS.SYS, that emulates the NetBIOS protocol. The NetBIOS provided by Novell is an emulator because it does not transmit NetBIOS packets. Instead, NetBIOS packets are encapsulated in IPXTM packets, and the IPX packets are transmitted.IBM Extended Services and LAN Services provide a native NetBIOS driver, NETBEUI.OS2, rather than an emulation.PAGENUM=184 ID="BP185"RENDERAS="SECT1"ID="FM75002"Determining Which NetBIOS Drivers to Set UpWhen this section refers to the NetBIOS support available with an IBM product (such as Extended Services), we assume the product includes the files we list.By default, the files shown here are included in Extended Services and LAN Services packages. By default, LAPS is included in both packages, although different NetBIOS components are actually used in each package.However, the files shown may also be included in other packages. For example, you may have received the IBM LAPS program without receiving Extended Services.In this case, you might have the NetBIOS support usually provided by Extended Services without having the whole Extended Services product. Contact IBM to resolve questions about the IBM files you have relating to NetBIOS.Use this section to determine whether your application needs access to the Novell NETBIOS.SYS driver, the IBM NETBEUI.OS2 driver, or both. The drivers your application can access depends on the following:MARK=BULLETWhether you have Extended Services or LAN Services installed on your workstation.The interface used by your application.RENDERAS="SECT2"Your Installed IBM SoftwareNetBIOS support is provided withTYPE="VERT"Extended ServicesLAN ServicesRENDERAS="SECT3"Extended ServicesIDXID="w12145"BOOK="_idx" COLLECTION="nw41" TIDREF="i1398"Extended Services NetBIOS support is included in the LAPS programs. NetBIOS-related pieces of LAPSIDXID="w12146"BOOK="_idx" COLLECTION="nw41" TIDREF="i2063"
 areTYPE="VERT"NETAPI.DLLIDXID="w12147"BOOK="_idx" COLLECTION="nw41" TIDREF="i1740"IDXID="w12148"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"ACSNETB.DLLPAGENUM=185 ID="BP186"NETBIOS.OS2NETBEUI.OS2LANPDD LANVDDRENDERAS="SECT3"LAN ServicesLAN Services NetBIOS support is included in the LAPS program and in NETWKSTA.200.RENDERAS="SECT2"Your Application's InterfaceOS/2 NetBIOS applications use Dynamic Link Libraries (DLLs) to interface with NetBIOS drivers. The DLL your application uses depends on the NetBIOS interface standard your application follows:MARK=BULLETACSNETB.DLLIDXID="w12149"BOOK="_idx" COLLECTION="nw41" TIDREF="i80"IDXID="w12150"BOOK="_idx" COLLECTION="nw41" TIDREF="i2610"
IDXID="w12151"BOOK="_idx" COLLECTION="nw41" TIDREF="i2666"
. This is IBM's NetBIOS 3.0 (NB30) interface introduced in OS/2 Version 2.0. Applications written before OS/2 Version 2.0 most likely cannot use it. The NETAPI.DLLIDXID="w12152"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"IDXID="w12153"BOOK="_idx" COLLECTION="nw41" TIDREF="i1742"
IDXID="w12154"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"
. This is the original OS/2 NetBIOS Submit interface, supported by IDXID="w12155"BOOK="_idx" COLLECTION="nw41" TIDREF="i2038"
LAN Manager and LAN ServerIDXID="w12156"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
 before OS/2 Version 2.0 was released.You can run applications that use different interfaces at the same time as long as you have the support for each interface installed and configured.For example, you can run an NB30 application and a NetBIOS Submit application on the same workstation. Refer to the documentation for your application to determine which NetBIOS interface it uses; then follow the flowcharts in IDREF="FM87108"Figure 15-1 or IDREF="FM69194"Figure 15-2 to seeMARK=BULLETWhether the IBM or Novell NetBIOS driver can be accessed by your application.Where to find instructions on setting up the drivers.PAGENUM=186 ID="BP187"LABEL="15-1" FLOAT="0"IDXID="w12157"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"ID="FM87108"ID="FM16027"Determine the NetBIOS Support You Have for NetBIOS 3.0 (NB30) ApplicationsFILEREF="c41q10a.tif"PAGENUM=187 ID="BP188"LABEL="15-2" FLOAT="0"ID="FM69194"Determine the NetBIOS Support You Have for NetBIOS Submit ApplicationsFILEREF="c41q09a.tif"PAGENUM=188 ID="BP189"RENDERAS="SECT1"ID="FM79688"Setting Up the Novell NetBIOS DriverUse this section only if you were directed here from the flow chart in IDREF="FM69194"Figure 15-2 because youMARK=BULLETHave a NetBIOS Submit applicationHave Extended ServicesDo not have LAN ServicesAs IDREF="FM47459"Figure 15-3 shows, the IDXID="w12158"BOOK="_idx" COLLECTION="nw41" TIDREF="i2650"
Novell NetBIOS driver interfaces with Novell's NETAPI.DLL file when you do not have Extended Services.LABEL="15-3" FLOAT="0"ID="FM47459"NetBIOS Requests through Novell's NetBIOS DriverFILEREF="c41q63a.tif"As IDREF="FM47459"Figure 15-3 shows, if you use Extended Services, the NETAPI.DLL is the one from the Extended Services package. This NETAPI.DLL interfaces with a NETSUB.DLL file from Novell, which in turn works with the Novell NetBIOS driver. PAGENUM=189 ID="BP190"LABEL="15-4" FLOAT="0"NetBIOS Requests through Novell's NetBIOS Driver with Extended Services InstalledFILEREF="c41q75a.tif"Follow the procedures in IDREF="FM17293""Installing the Driver" on page 189 to use the Novell NetBIOS driver. The procedures apply whether or not you have Extended Services.If you use Extended Services, you must get an updated IDXID="w12159"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"
NETAPI.DLL file from IBM. The one shipped with base Extended Services 1.0 does not provide the intended NetBIOS support. RENDERAS="SECT2"ID="FM17293"Installing the DriverIDXID="w12160"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"IDXID="w12161"BOOK="_idx" COLLECTION="nw41" TIDREF="i2650"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXInstall Extended Services if you have it. See the IBM documentation for Extended Services.Install your NetBIOS application. See the documentation for your application.RENDERAS="SECT3"ProcedureYou can install NetWare Client for OS/2 from this procedure. You must install the Novell NetBIOS driver on each computer that will use Novell NetBIOS. PAGENUM=190 ID="BP191"PERFORMANCE="REQUIRED"Start the NetWare Client for OS/2 installation program.If NetWare Client for OS/2 is not installed, start the program from your 
CLASS=DISKWSOS2_1 diskette. Type 
MOREINFO="NONE"INSTALL. You can install NetWare Client for OS/2 when you install NetBIOS. If NetWare Client for OS/2 is installed, start the program by choosing 
CLASS=MENUITEM MOREINFO="NONE"Installation from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop. PERFORMANCE="REQUIRED"Choose
CLASS=MENUITEM MOREINFO="NONE" Requester on Workstation from the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu. PERFORMANCE="REQUIRED"Verify the target and source directory and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select an action from the 
CLASS=MENUITEM MOREINFO="NONE"Requester Installation screen based on whether NetWare Client for OS/2 is installed.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is not installed, select 
CLASS=MENUITEM MOREINFO="NONE"Edit CONFIG.SYS and Copy All Files... and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is installed, select 
CLASS=MENUITEM MOREINFO="NONE"Only Edit CONFIG.SYS... and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select the ODI driver for your network board and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue...PERFORMANCE="REQUIRED"Select your preferences for NetWare support for DOS and MS Windows applications and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue...PERFORMANCE="REQUIRED"Select 
CLASS=MENUITEM MOREINFO="NONE"NetBIOS Emulation for OS/2 Sessions. PERFORMANCE="REQUIRED"Choose
CLASS=MENUITEM MOREINFO="NONE" Save... PERFORMANCE="REQUIRED"Verify the filename and location and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.If you have not previously installed NetWare Client for OS/2, the 
CLASS=MENUITEM MOREINFO="NONE"Copy Requester Files screen appears. Continue with 
IDREF="FM32721"Step 10. If you have previously installed NetWare Client for OS/2, the main installation menu appears. Go to 
IDREF="FM24938""Configuring the Driver" on page 191.PERFORMANCE="REQUIRED"ID="FM32721"Choose 
CLASS=MENUITEM MOREINFO="NONE"Copy and follow the screens to finish installing NetWare Client for OS/2. When the main menu returns, go to 
IDREF="FM24938""Configuring the Driver" on page 191. 
PAGENUM=191 ID="BP192"RENDERAS="SECT2"ID="FM24938"Configuring the DriverIDXID="w12162"BOOK="_idx" COLLECTION="nw41" TIDREF="i2650"IDXID="w12163"BOOK="_idx" COLLECTION="nw41" TIDREF="i762"Novell's NetBIOS driver comes with default configuration settings. You might want to customize the configuration. Follow the instructions below toMARK=BULLETDetermine whether you need to change the default configuration for NetWare® NetBIOS.Change the configuration if necessary.You can change the configuration to manage such features as names, sessions, and commands. If you don't know what NetBIOS names, sessions, and commands are, see the documentation for your NetBIOS application. RENDERAS="SECT3"PrerequisiteMARK=CHECKBOXNetWare Client for OS/2 must be installed. RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED"Start the NetWare Client for OS/2 Installation program.The program might already be running if you just installed the NetBIOS driver. If it isn't running, start it by choosing the 
CLASS=MENUITEM MOREINFO="NONE"Installation icon from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop.PERFORMANCE="REQUIRED"Choose
CLASS=MENUITEM MOREINFO="NONE" This workstation... from the 
CLASS=MENUITEM MOREINFO="NONE"Configuration menu. PERFORMANCE="REQUIRED"Verify the location of NET.CFG and choose 
CLASS=MENUITEM MOREINFO="NONE"Edit.The 
CLASS=MENUITEM MOREINFO="NONE"Edit NET.CFG window appears. See 
IDREF="FM27333"Figure 15-5. You can cut and paste text from the help window at the bottom of the screen to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents window. 
PAGENUM=192 ID="BP193"Use the following keys:LABEL="15-1" PGWIDE=0 TOCENTRY="1" Key Definitions for the NET.CFG WindowCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Highlight textCOLNAME=2 ROTATE="0" MOREROWS="0"Click and drag with the mouse, or move the cursor with the arrow keys while holding down the MOREINFO="NONE"<Shift> keyCOLNAME=1 ROTATE="0" MOREROWS="0"Copy textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Cut text (text will reappear the next time you refresh the window)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Delete>COLNAME=1 ROTATE="0" MOREROWS="0"Paste textCOLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Shift>+<Insert>COLNAME=1 ROTATE="0" MOREROWS="0"Delete text (deleted text cannot be pasted)COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Press <Ctrl>+<Delete>PAGENUM=193 ID="BP194"LABEL="15-5" FLOAT="0"ID="FM27333"Editing NET.CFG for NetBIOSFILEREF="c41q68a.tif"PERFORMANCE="REQUIRED"Select "NetWare NetBIOS" from the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box on the left of your screen.
PAGENUM=194 ID="BP195"PERFORMANCE="REQUIRED"Determine whether to change the configuration for the settings under "NetWare NetBIOS."If you decide not to change the configuration for a setting, no action is required for that setting.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select one of the settings. For example, select "abort timeout."PERFORMANCE="REQUIRED"Read the help window at the bottom of the screen to determine whether to change the configuration for the setting. You can choose the CLASS=MENUITEM MOREINFO="NONE"Usage, CLASS=MENUITEM MOREINFO="NONE"Description, and CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of your screen for more about the setting you've selected.PERFORMANCE="REQUIRED"(Optional) To change the configuration, add the configuration lines (shown in the 
CLASS=MENUITEM MOREINFO="NONE"Usage help window) to the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box.You must follow the format requirements explained in the "Format of NET.CFG Options" topic. To see these requirements, select this topic from the CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box and choose CLASS=MENUITEM MOREINFO="NONE"Usage.Repeat steps 5a through 5c for each setting. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save.PERFORMANCE="REQUIRED"Exit the NetWare Client for OS/2 installation program.If your NetBIOS application will not access the IBM NetBIOS driver, use the OS/2 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature to reboot your computer. If your NetBIOS application will access the IBM NetBIOS driver, do not reboot. Instead, configure the IBM driver as instructed in one of the following sections:
MARK=BULLETIDREF="FM40784""Configuring NETBIOS.OS2 with PROTOCOL.INI" on page 195IDREF="FM30479""Configuring NETWKSTA.200 with IBMLAN.INI" on page 199If you do not know which of these two sections to read, go to 
IDREF="FM75002""Determining Which NetBIOS Drivers to Set Up" on page 184. 
PAGENUM=195 ID="BP196"RENDERAS="SECT1"ID="FM40784"Configuring NETBIOS.OS2IDXID="w12164"BOOK="_idx" COLLECTION="nw41" TIDREF="i2668"
 with PROTOCOL.INIIDXID="w12165"BOOK="_idx" COLLECTION="nw41" TIDREF="i3615"Do this section only if you were directed here from the flow chart in IDREF="FM16027"Figure 15-1 because youMARK=BULLETHave the LAPS program.Have a NetBIOS 3.0 application.As IDREF="FM52552"Figure 15-6 shows, IBM's ACSNETB.DLL interfaces with NETBIOS.OS2, also provided by IBM. NETBIOS.OS2 can be configured to pass NetBIOS requests to either of the following:MARK=BULLETNETBEUI.OS2, IBM's NetBIOS driver.NETBIOS.SYS, Novell's NetBIOS driver.This section explains how to configure NETBIOS.OS2 to support both NetBIOS drivers simultaneously or to support only Novell's driver.If you only want to use IBM's NetBIOS driver, you don't need to configure. By default, NETBIOS.OS2 communicates only to NETBEUI.OS2. LABEL="15-6" FLOAT="0"ID="FM52552"NetBIOS Requests through NETBIOS.OS2FILEREF="c41q65a.tif"PAGENUM=196 ID="BP197"RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXInstall Extended Services with NetBIOS support. Verify that you can get a NetBIOS connection.Install LAN Services (NetBIOS support is installed by default). Verify that you can get a LAN connection. Install NetWare Client for OS/2 with the Novell NetBIOS driver. RENDERAS="SECT2"ProceduresIn this procedure, you edit the PROTOCOL.INI file to define a virtual adapter for the Novell and IBM NetBIOS drivers. PERFORMANCE="REQUIRED" Open the PROTOCOL.INI file in a text editor. PROTOCOL.INI is located in the \IBMCOM directory. For example, to use the OS/2 System Editor at the command line, type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"E C:\IBMCOM\PROTOCOL.INI MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"ID="FM52020"Find the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[NETBIOS]If the [NETBIOS] line does not exist, type the line at the end of the PROTOCOL.INI file, exactly as shown.PERFORMANCE="REQUIRED"On a new line under [NETBIOS], add the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DriverName = NETBIOS$The line must be indented at least one space and must follow other formatting requirements for IBMLAN.INI. NETBIOS$ is the device name of NETBIOS.OS2. If the line already exists, go to the next step.PERFORMANCE="REQUIRED"On a new line under the DriverName line, add lines assigning adapter numbers to the IBM and Novell NetBIOS drivers. To allow NB30 NetBIOS applications to use only Novell's NetBIOS driver, add a line for Novell's NetBIOS. 
PAGENUM=197 ID="BP198"To allow NB30 applications to use both Novell and IBM drivers, add another line for IBM's NetBIOS. When you define the Novell NetBIOS network, your default definition for the IBM NetBIOS network is no longer defined. So, if you are going to use IBM NetBIOS driver, you must add a line for the IBM network. Each line you add should look similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w12166"BOOK="_idx" COLLECTION="nw41" TIDREF="i86"
ADAPTERa = b,c,sessions,commands,namesIf you have existing ADAPTER lines, leave them. Replace the variables in the line with values shown in the following chart:LABEL="15-2" PGWIDE=1 TOCENTRY="1" Parameters for Defining NetBIOS in PROTOCOL.INICOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="29*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VariableCOLNAME=2 ROTATE="0" MOREROWS="0"Meaning of variableVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ADAPTERCOLNAME=2 ROTATE="0" MOREROWS="0"Adapter is a key word for NETBIOS.OS2. It is not case-sensitive.COLNAME=1 ROTATE="0" MOREROWS="0"aCOLNAME=2 ROTATE="0" MOREROWS="0"Replace a with a number from 0 to 3. This is the adapter number used by the application. When specifying an adapter number,MARK=BULLETDo not use the same number used in any other adapter statements. Each adapter number can only be defined to one NetBIOS driver.Do not skip adapter numbers. For example, if you have an adapter statement that uses ADAPTER0, use ADAPTER1 for your next adapter statement.COLNAME=1 ROTATE="0" MOREROWS="0"bCOLNAME=2 ROTATE="0" MOREROWS="0"Replace b with the device name for the NetBIOS driver. NETBIOS.OS2 recognizes this name when determining which driver to pass NetBIOS calls to.MARK=BULLETReplace b with IPXNB$ for the Novell NetBIOS driver.Replace b with NETBEUI$ for the IBM NetBIOS driver.COLNAME=1 ROTATE="0" MOREROWS="0"cCOLNAME=2 ROTATE="0" MOREROWS="0"Replace c with a number from 0 to 3. This number is the virtual adapter number used by the target NetBIOS driver. MARK=BULLETFor Novell's NetBIOS driver, always specify 0. For IBM's NetBIOS driver, specify whichever virtual adapter you want used. See the Extended Services documentation on NETBEUI.OS2.COLNAME=1 ROTATE="0" MOREROWS="0"sessionsIDXID="w12167"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"COLNAME=2 ROTATE="0" MOREROWS="0"Replace sessions with the number of NetBIOS sessions you want allocated to NetBIOS 3.0 applications. This number specifies the maximum number of sessions that can be active between NETBIOS.OS2 and Novell's NetBIOS driver. Novell's NetBIOS driver is configured by the sessions setting in NET.CFG. The number of sessions allocated to the application is either the NET.CFG value or the value on this line of PROTOCOL.INI, whichever is lowest.For example, if you set 64 sessions in NET.CFG, and the value on this line is only 48, NetBIOS 3.0 applications can only use 48 sessions. However, if you set 30 sessions in NET.CFG and the value on this line is 50, NetBIOS 3.0 applications can only use 30 sessions.COLNAME=1 ROTATE="0" MOREROWS="0"commandsIDXID="w12168"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"COLNAME=2 ROTATE="0" MOREROWS="0"Replace commands with the number of NetBIOS commands you want allocated to the NB30 NetBIOS application. This number specifies the maximum number of commands that can be active between NETBIOS.OS2 and Novell's NetBIOS driver.Novell's NetBIOS driver is configured by the commands setting in NET.CFG. The number of commands allocated to the application is either the NET.CFG value or the value on this line of PROTOCOL.INI, whichever is lowest.For example, if you set 128 commands in NET.CFG, and the value on this line is only 100, the application can only use 100 commands. However, if you set 80 commands in NET.CFG and the value on this line is 95, the application can only use 80 commands. COLNAME=1 ROTATE="0" MOREROWS="0"namesIDXID="w12169"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"COLNAME=2 ROTATE="0" MOREROWS="0"Replace names with the number of NetBIOS names you want allocated to the NB30 application. This number specifies the maximum number of names that can be active between NETBIOS.OS2 and Novell's NetBIOS driver.Novell's NetBIOS driver is configured by the names setting in NET.CFG. The number of names allocated to the application is either the NET.CFG value or the value on this line of PROTOCOL.INI, whichever is lowest.For example, if you set 128 names in NET.CFG, and the value on this line is only 100, the application can only use 100 names. However, if you set 80 names in NET.CFG and the value on this line is 95, the application can only use 80 names. PAGENUM=198 ID="BP199"For example, to enable applications to use both the Novell or the IBM NetBIOS driver, the lines in your PROTOCOL.INI file might read:
PAGENUM=199 ID="BP200"FORMAT="LINESPECIFIC"MOREINFO="NONE"[NETBIOS]
DriverName = NETBIOS$
Adapter0 = ipxnb$,0,16,16,8
Adapter1 = netbeui$,0,32,14,8For more information about defining adapters in NETBIOS.OS2, see your Extended Services documentation. PERFORMANCE="REQUIRED"Insert a blank line at the end of the file. PERFORMANCE="REQUIRED"ID="FM68743"Save the PROTOCOL.INI file and exit your text editor.PERFORMANCE="REQUIRED"Use the 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature from the OS/2 system menu to reboot your computer. When your computer restarts, your NB30 NetBIOS applications can use each driver you defined in an adapter line. RENDERAS="SECT2"ID="FM30479"Configuring NETWKSTA.200IDXID="w12170"BOOK="_idx" COLLECTION="nw41" TIDREF="i1745"IDXID="w12171"BOOK="_idx" COLLECTION="nw41" TIDREF="i2838"
 with IBMLAN.INIDo this section only if you were directed here from the flow chart on IDREF="FM69194"Figure 15-2 because youMARK=BULLETHave a NetBIOS Submit application.Have LAN Services.As IDREF="FM98073"Figure 15-7 shows, NETAPI.DLL interfaces with IBM's NETWKSTA.200. The IDXID="w12172"BOOK="_idx" COLLECTION="nw41" TIDREF="i2642"
NETAPI.DLL file used is the one provided with LAN Services. This happens by default, since the \MUGLIB\DLL directory that stores the LAN Services NETAPI.DLL comes earlier in the path than the \NETWARE directory that contains the NetWare Client for OS/2 NETAPI.DLL. NETWKSTA.200 can be configured to pass NetBIOS requests to eitherMARK=BULLETNETBEUI.OS2, IBM's NetBIOS driver.NETBIOS.SYS, Novell's NetBIOS driver.This section explains how to configure NETWKSTA.200 to support both NetBIOS drivers simultaneously or to support only Novell's driver. PAGENUM=200 ID="BP201"If you only want to use IBM's NetBIOS driver, you do not need to configure. By default, NETWKSTA.200 talks only to NETBEUI.OS2. LABEL="15-7" FLOAT="0"ID="FM98073"NetBIOS Requests through NETWKSTA.200FILEREF="c41q64a.tif"RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXInstall Extended Services if you have it.Install LAN Services (NetBIOS support is installed by default). Verify that you can get a LAN connection. Install NetWare Client for OS/2 with the Novell NetBIOS driver. RENDERAS="SECT2"ProceduresPERFORMANCE="REQUIRED" Open the IBMLAN.INI file in a text editor.IBMLAN.INI is located in the \IBMLAN directory on your boot drive. For example, to use the OS/2 System Editor at the command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"E C:\IBMLAN\IBMLAN.INI MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Find the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[networks]
PAGENUM=201 ID="BP202"Underneath the [networks] line, you should see a line, similar to the following, that defines a network as the one using IBM's NetBIOS driver, NETBEUI.OS2:
FORMAT="LINESPECIFIC"MOREINFO="NONE"net1 = NETBEUI$,1,LM10,32,50,14In this case, the line defines net1 as the network using the IBM NetBIOS driver. PERFORMANCE="REQUIRED"If the IBM driver is defined to net1, change the 1 to a 2. The line should be similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"net2 = NETBEUI$,1,LM10,32,50,14You must change the IBM driver because the Novell driver must be defined to net1 for dual NetBIOS to work.PERFORMANCE="REQUIRED"Underneath any existing net statements, add a line assigning network number 1 to the Novell NetBIOS driver.A network for IBM NetBIOS is defined by default in both LAN Requester and LAN Server. If you want NetBIOS Submit applications to only use Novell's NetBIOS driver, comment out the line for the IBM driver with a semicolon.The line must be indented at least one space and must follow other formatting requirements for IBMLAN.INI. The Novell line you add should look similar to the following
FORMAT="LINESPECIFIC"MOREINFO="NONE"neta = b,c,LM10,sessions,commands,namesReplace the variables in the line with values shown in the following table:LABEL="15-3" PGWIDE=1 TOCENTRY="1" Parameters for Defining Dual NetBIOS in IBMLAN.INICOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="29*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VariableCOLNAME=2 ROTATE="0" MOREROWS="0"Meaning of variableVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NETCOLNAME=2 ROTATE="0" MOREROWS="0"NET is a standard key word for NETWKSTA.200. It is not case-sensitive.COLNAME=1 ROTATE="0" MOREROWS="0"aCOLNAME=2 ROTATE="0" MOREROWS="0"Replace a with a number from 1 to 4. This is the number of the network you want NETBIOS.OS2 to use when sending NetBIOS requests to a NETBIOS driver. Each NetBIOS driver must have its own network number. When specifying a network number,MARK=BULLETUse 1 for the Novell NetBIOS driver and 2 for the IBM NetBIOS driver.Do not use the same number used in other net statements. Each network number can only be defined to one NetBIOS driver.Do not skip numbers. For example, if you have a net statement that uses NET1, use NET2 for your next statement. COLNAME=1 ROTATE="0" MOREROWS="0"bCOLNAME=2 ROTATE="0" MOREROWS="0"Replace b with the device name for the NetBIOS driver. NETWKSTA.200 recognizes this name when determining which driver to pass NetBIOS calls to. Replace b with IPXNB$ for the Novell NetBIOS driver. (NETBEUI$ is the device name for the IBM NetBIOS driver.)COLNAME=1 ROTATE="0" MOREROWS="0"LM10IDXID="w12173"BOOK="_idx" COLLECTION="nw41" TIDREF="i2135"COLNAME=2 ROTATE="0" MOREROWS="0"LM10 is the name of the protocol that enables NETWKSTA.200 to communicate with more than one NetBIOS driver. Type it exactly as it appears. COLNAME=1 ROTATE="0" MOREROWS="0"cCOLNAME=2 ROTATE="0" MOREROWS="0"Replace c with a number from 0 to 3. This number is the virtual adapter number used by the target NetBIOS driver to receive NetBIOS requests from NETWKSTA.200. MARK=BULLETFor Novell's NetBIOS driver, always specify 0. For IBM's NetBIOS driver, specify whichever virtual adapter you want used. See the Extended Services documentation on NETBEUI.OS2.COLNAME=1 ROTATE="0" MOREROWS="0"sessionsIDXID="w12174"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"COLNAME=2 ROTATE="0" MOREROWS="0"Replace sessions with the number of NetBIOS sessions you want allocated to the NetBIOS Submit application. This number specifies the maximum number of sessions that can be active between NETWKSTA.200 and Novell's NetBIOS driver. Novell's NetBIOS driver is configured from the sessions setting in NET.CFG. The number of sessions allocated to the application is either the NET.CFG value or the value on this line of IBMLAN.INI, whichever is lowest.For example, if you set 64 sessions in NET.CFG, and the value on this line is only 48, the application can only use 48 sessions. However, if you set 30 sessions in NET.CFG and the value on this line is 50, the application can only use 30 sessions. COLNAME=1 ROTATE="0" MOREROWS="0"commandsIDXID="w12175"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"COLNAME=2 ROTATE="0" MOREROWS="0"Replace commands with the number of NetBIOS commands you want allocated to the NetBIOS Submit application. This number specifies the maximum number of commands that can be active between NETWKSTA.200 and Novell's NetBIOS driver. Novell's NetBIOS driver is configured from the names setting in NET.CFG. The number of names actually allocated to the application is either the NET.CFG value or the value on this line of IBMLAN.INI, whichever is lowest. For example, if you set 128 commands in NET.CFG, and the value on this line is only 100, the application can only use 100 commands. However, if you set 80 commands in NET.CFG and the value on this line is 95, the application can only use 80 commands. COLNAME=1 ROTATE="0" MOREROWS="0"namesIDXID="w12176"BOOK="_idx" COLLECTION="nw41" TIDREF="i2655"COLNAME=2 ROTATE="0" MOREROWS="0"Replace names with the number of NetBIOS names you want allocated to the NetBIOS Submit application. This number specifies the maximum number of names that can be active between NETWKSTA.200 and Novell's NetBIOS driver. Novell's NetBIOS driver is configured from the names setting in NET.CFG. The number of names actually allocated to the application is either the NET.CFG value or the value on this line of IBMLAN.INI, whichever is lowest. For example, if you set 128 names in NET.CFG, and the value on this line is only 100, the application can only use 100 names.However, if you set 80 names in NET.CFG and the value on this line is 95, the application can only use 80 names. PAGENUM=203 ID="BP203"For example, to enable applications to use both the Novell and IBM NetBIOS drivers, the lines in your IBMLAN.INI file might read:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[networks]
net1 = IPXNB$,1,LM10,32,16,8
net2 = NETBEUI$,1,LM10,16,16,8For more about defining networks for NETWKSTA.200, see your LAN Services documentation.PERFORMANCE="REQUIRED"If your computer is a LAN Server
IDXID="w12177"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
, do the following:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Find the [server] line in your IBMLAN.INI file.PERFORMANCE="REQUIRED"ID="FM51429"At the end of the [server] section, find the following line:
PAGENUM=204 ID="BP204"FORMAT="LINESPECIFIC"MOREINFO="NONE"srvnets = netaPERFORMANCE="REQUIRED"Add the Novell NetBIOS network to the line.Separate the Novell net from any existing nets with a comma. For example, if Novell's NetBIOS driver was net2:FORMAT="LINESPECIFIC"MOREINFO="NONE"srvnets = NET1,NET2The line must be indented at least one space and must follow other formatting requirements for IBMLAN.INI.This line tells LAN Services the network to send NetBIOS calls for servers on. PERFORMANCE="REQUIRED"If your computer is a LAN Requester
IDXID="w12178"BOOK="_idx" COLLECTION="nw41" TIDREF="i2040"
, do the following:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Find the [requester] line in your IBMLAN.INI file.PERFORMANCE="REQUIRED"At the end of the [requester] section, find the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"wrknets = netaPERFORMANCE="REQUIRED"Add the Novell NetBIOS network to the line. Separate the Novell net from any existing nets with a comma. For example,FORMAT="LINESPECIFIC"MOREINFO="NONE"wrknets = NET1,NET2The line must be indented at least one space and must follow other formatting requirements for IBMLAN.INI. This line tells LAN Services the network to send NetBIOS calls for workstations on. PERFORMANCE="REQUIRED"Save the IBMLAN.INI file and exit your text editor.PERFORMANCE="REQUIRED"Use the 
CLASS=MENUITEM MOREINFO="NONE"Shutdown feature from the OS/2 system menu to reboot your computer. When your computer restarts, your NetBIOS Submit applications can use both the Novell and IBM NetBIOS drivers. NETWKSTA.200IDXID="w12179"BOOK="_idx" COLLECTION="nw41" TIDREF="i2838"
 must be started before any kind of NetBIOS connection will work. You can start it automatically upon startup or with the LAN Services NETSTARTIDXID="w12180"BOOK="_idx" COLLECTION="nw41" TIDREF="i2673"
 command at a command line. See your LAN Services documentation.PAGENUM=205 ID="BP205"LABEL="16"PAGENUM=207 ID="BP206"ID="FM99600"Using ODINSUPCOLS=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="FM97282"How Board Sharing Is Possible COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM97282"207COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62336"Setting Up ODINSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62336"208IDXID="w12181"BOOK="_idx" COLLECTION="nw41" TIDREF="i2040"IDXID="w12182"BOOK="_idx" COLLECTION="nw41" TIDREF="i1740"
Use this chapter if you want NetWare ClientTM for OS/2* to share a network IDXID="w12183"BOOK="_idx" COLLECTION="nw41" TIDREF="i2850"
board with one or more of the following IBM* software products:TYPE="VERT"Extended ServicesIDXID="w12184"BOOK="_idx" COLLECTION="nw41" TIDREF="i1398"LAN Server
IDXID="w12185"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"LAN RequesterIf you have Extended Services or LAN Services, you may also want to set up the NetBIOS protocol. After doing the steps in this chapter, see IDREF="FM33934"Chapter 15, "Using NETBIOS," on page IDREF="FM33934"183. RENDERAS="SECT1"ID="FM97282"How Board Sharing Is PossibleNetWare Client for OS/2 uses protocol drivers and network drivers written to the ODITM (Open Data-Link Interface) specification. Extended Services and LAN Services use protocol drivers and network drivers written to the IDXID="w12186"BOOK="_idx" COLLECTION="nw41" TIDREF="i2629"
NDIS specification.Even though NetWare Client for OS/2 uses a different driver specification than Extended Services and LAN Services, NetWare Client for OS/2 can still share a network board with these products. This is possible because of two drivers that Novell provides:MARK=BULLETODINSUP, which lets Extended Services and LAN Services use ODI LAN drivers. PAGENUM=208 ID="BP207"Use ODINSUP when you want the ODI network driver to control the board. See IDREF="FM62336""Setting Up ODINSUP" on page 208. LANSUP, which lets NetWare Client for OS/2 use NDIS network drivers. Use LANSUP when you want the NDIS driver to control the board. See IDREF="FM87147""Setting Up LANSUP" on page 232. RENDERAS="SECT1"ID="FM62336"Setting Up ODINSUPIDXID="w12187"BOOK="_idx" COLLECTION="nw41" TIDREF="i3061"Except where noted, the instructions in this section apply whether you have Extended Services, LAN Services, or both. However, the sample configuration files differ depending on the IBM software you have. Be sure to refer to the correct sample files for your environment. ODINSUP installation can be done automatically using the CLASS=MENUITEM MOREINFO="NONE"Utilities option of the OS/2 Workstation Installation program, or by modifying the configuration files with a text editor.The following section discusses how to set up each of the three parts using a text editor. Each part sets up a different configuration file. You must complete all three parts. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StepCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33397"Part A: Binding ODI Drivers in PROTOCOL.INI  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33397"208COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM72939"Part B: Loading ODINSUP in CONFIG.SYS COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72939"212COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM17229"Part C: Configuring ODINSUP in NET.CFG COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM17229"214COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM42614"Sample Configuration Files for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM42614"220ODINSUP supports Ethernet- and token ring-compatible ODI drivers. It does not support ARCnet or PC Network II drivers. RENDERAS="SECT2"ID="FM33397"Part A: Binding ODI Drivers in IDXID="w12188"BOOK="_idx" COLLECTION="nw41" TIDREF="i3615"
PROTOCOL.INIIn this section, you edit the PROTOCOL.INI file in a text editor to do the following:MARK=BULLETBind the NDIS protocol stack to the ODI driversPAGENUM=209 ID="BP208"Remove the line binding the NDIS protocol stack to the NDIS MAC driversThese instructions are for LAN Server and LAN Requester 2.x.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXInstall Extended Services on the workstation. If you have an NDIS driver for the network board in your computer, verify that you can get a Communications Manager or Database Manager connection. See the documentation for Extended Services. Install LAN Server or LAN Requester on the workstation. If you have an NDIS driver for the network board in your computer, verify that you can get connections properly on your LAN Server network. See the documentation for LAN Services. After installing all IBM software, install NetWare Client for OS/2. Using the ODI driver for the board, verify that you can get connections properly on your NetWare network.Once you install NetWare Client for OS/2, Extended Services and LAN Services will not be able to use the network board to make connections until you have completely set up ODINSUP as instructed in this chapter. RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED" Open the PROTOCOL.INI file in a text editor. PROTOCOL.INI is located in the \IBMCOM directory on your boot drive. For example, to use the OS/2 System Editor at the command line, type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"E C:\IBMCOM\PROTOCOL.INIPERFORMANCE="REQUIRED"ID="FM50121"Find all occurrences of the lines that bind the NDIS MAC drivers. You can search for 
MOREINFO="NONE"Bindings = NDIS MAC driver. If you don't know the name of the NDIS driver to look for, see your Extended Services or LAN Services documentation.For example, to search for a token ring NDIS driver, find the following line:
PAGENUM=210 ID="BP209"FORMAT="LINESPECIFIC"MOREINFO="NONE"Bindings = IBMTOK_NIFBindings lines may be in either of the following sections, depending on whether you have Extended Services or LAN Services installed:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[NETBEUI_nif]
[LANDD_nif]PERFORMANCE="REQUIRED"Use a semicolon to comment out all Bindings lines found in 
IDREF="FM50121"Step 2. For example, your PROTOCOL.INI file for a token ring driver might look like the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[LANDD_nif]
.
.
; Bindings = IBMTOK_NIFPERFORMANCE="REQUIRED"After each commented-out Bindings line, add a line to bind the NDIS protocol to an ODI driver.Follow the same syntax as the line you commented out, using the ODI driver name instead of the NDIS driver name. For example, to add a line for the TOKEN.SYS ODI driver:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[LANDD_nif]
.
.
; Bindings = IBMTOK_NIF
Bindings = TOKENSince driver names in PROTOCOL.INI cannot start with a number, place an 
X before 3Com drivers and other drivers that start with a number (Example: 
MOREINFO="NONE"Bindings = X3C503).If you don't know which ODI driver name to use, you can restart your machine. A message will appear, displaying the name of the ODI driver that should be used. If you do this, reopen the PROTOCOL.INI file and return to this step of the procedure. PERFORMANCE="REQUIRED"(Conditional) Type an instance number to bind the NDIS protocol to a particular occurrence of a board. 
PAGENUM=211 ID="BP210"If you have two or more network boards using the same ODI driver, the NDIS protocol uses the first network board of that type. To have NDIS use a board other than the first one found, you can specify an instance number. Type the instance number at the end of the driver name, with no space between the driver name and the instance number. For example, if you have two token ring network boards, have NDIS use the second board by typing an instance number for the second board, as shown:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[LANDD_nif]
.
.
; Bindings = IBMTOK_NIF
Bindings = TOKEN2PERFORMANCE="REQUIRED"(Conditional) Bind the NDIS protocol to additional ODI drivers. To bind the NDIS protocol to more than one ODI driver, type both driver names on the same line, separated by a comma. For example, to bind to both an NE2000 driver and an NE1000 driver, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"Bindings=ne2000,ne1000PERFORMANCE="REQUIRED"Add an empty header for the ODI drivers. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Locate the MAC SECTION of the PROTOCOL.INI file. You can search for MAC SECTION.PERFORMANCE="REQUIRED"At the end of the MAC section, type a header for each ODI driver you specified in a Bindings line in Steps 4 through 6. Use the ODI driver name. For example, for a token ring ODI driver, type the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"[TOKEN]Put a blank line before and after the header section. If the driver name starts with a number, you do not need an X in front of the number for this step. PAGENUM=212 ID="BP211"This ODI driver header is a place holder so that if you configure with the LAPS program in the future, the Bindings information will not be erased.PERFORMANCE="REQUIRED"Save and exit the PROTOCOL.INI file. Do not exit the text editor. Go to 
IDREF="FM72939""Part B: Loading ODINSUP in CONFIG.SYS" on page 212. RENDERAS="SECT2"ID="FM72939"Part B: Loading ODINSUP in CONFIG.SYSIDXID="w12189"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"In this section, you edit the CONFIG.SYS file in a text editor to do the following:MARK=BULLETLoad the ODINSUP driverPrevent the NDIS network driver (MAC) from loadingRENDERAS="SECT3"PrerequisiteMARK=CHECKBOXFollow the instructions in IDREF="FM33397""Part A: Binding ODI Drivers in PROTOCOL.INI" on page 208.RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED" Open the CONFIG.SYS file in a text editor.CONFIG.SYS is located at the root of your boot drive. PERFORMANCE="REQUIRED"Find the lines that load the NDIS MAC drivers. For example, for a token driver, search for the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2If you don't know the name of your NDIS driver, see your Extended Services or LAN Services documentation. PERFORMANCE="REQUIRED"Comment out the NDIS MAC driver that is equivalent to the ODI driver you are using.For example, to comment out a token ring NDIS MAC driver, place a REM command in front of the line that loads it, as shown:
PAGENUM=213 ID="BP212"FORMAT="LINESPECIFIC"MOREINFO="NONE"REM DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2If you have network boards and NDIS drivers for other communications software, do not comment out the lines to load those drivers. PERFORMANCE="REQUIRED"In the NetWare Client for OS/2 lines, find the line loading the ODI driver. PERFORMANCE="REQUIRED"On a new line underneath the ODI driver, insert a line to load the ODINSUP protocol. ODINSUP is located in the directory where you installed the NetWare Client for OS/2 files (\NETWARE by default). For example, to load the ODINSUP protocol from the default location, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=C:\NETWARE\ODINSUP.SYSIf you have the Source-Routing driver, ROUTE.SYS, loaded after the ODI driver, put the ODINSUP line after the ROUTE.SYS line. PERFORMANCE="REQUIRED"Verify that your file meets the load order requirements shown in 
IDREF="FM31746"Table 16-1. By default, these load order requirements will be met. If you have rearranged your CONFIG.SYS file, it may violate the load order requirements
IDXID="w12190"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"
. LABEL="16-1" PGWIDE=0 TOCENTRY="1"ID="FM31746" Load Order Requirements for ODINSUP CONFIG.SYS FileCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"These componentsCOLNAME=2 ROTATE="0" MOREROWS="0"Must load before these componentsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"PROTMAN.OS2 (in OS/2 section right after path statements)COLNAME=2 ROTATE="0" MOREROWS="0"The ODINSUP protocol COLNAME=1 ROTATE="0" MOREROWS="0"LSL.SYS (in NetWare Client for OS/2 section)COLNAME=2 ROTATE="0" MOREROWS="0"The ODI driver The ODINSUP protocol COLNAME=1 ROTATE="0" MOREROWS="0"The ODI driver (in NetWare Client for OS/2 section)COLNAME=2 ROTATE="0" MOREROWS="0"The ODINSUP protocol COLNAME=1 ROTATE="0" MOREROWS="0"NWIFS.IFSIDXID="w12191"BOOK="_idx" COLLECTION="nw41" TIDREF="i3029"
 (in NetWare Client for OS/2 section)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w12192"BOOK="_idx" COLLECTION="nw41" TIDREF="i2838"
NETWKSTA.200 (only in LAN Services configurations)PAGENUM=214 ID="BP213"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If your file meets load order requirements, go to 
IDREF="FM85009"Step 8. PERFORMANCE="REQUIRED"If your file violates load order requirements, go to 
IDREF="FM82769"Step 7.PERFORMANCE="REQUIRED"ID="FM82769"Rearrange your CONFIG.SYS file to meet load order requirements for ODINSUP. We suggest you make your file match the sample file shown for your environment. See 
IDREF="FM42614""Sample Configuration Files for ODINSUP" on page 220 for a list of sample configuration files. After rearranging your CONFIG.SYS file, go on to 
IDREF="FM85009"Step 8.PERFORMANCE="REQUIRED"ID="FM85009"Save and exit the CONFIG.SYS file.Do not exit the text editor. Go to 
IDREF="FM17229""Part C: Configuring ODINSUP in NET.CFG" on page 214. RENDERAS="SECT2"ID="FM17229"IDXID="w12193"BOOK="_idx" COLLECTION="nw41" TIDREF="i3061"
Part C: Configuring ODINSUP in NET.CFGIDXID="w12194"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"A NET.CFG file is required to use ODINSUP. In this section, you edit or create a NET.CFG file that does the following:MARK=BULLETEnables frame types for ODINSUP.Specifies to ODINSUP the node address known by Extended Services and the format in which that address is transmitted.Binds ODINSUP to an ODI driver or drivers.Increases the size of the packet that can be transmitted through the Link Support LayerTM program (if necessary).RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXFollow the instructions in IDREF="FM33397""Part A: Binding ODI Drivers in PROTOCOL.INI" on page 208.Follow the instructions in IDREF="FM72939""Part B: Loading ODINSUP in CONFIG.SYS" on page 212.PAGENUM=215 ID="BP214"RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED" Open the NET.CFG text file in the text editor. NET.CFG is located in the root of your boot drive. If NET.CFG does not exist, create a new file with that name. PERFORMANCE="REQUIRED"Enable frame types for ODINSUP.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Type the following line at the top of the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver drivernameReplace drivername with the name of your ODI driver. For example, for a token ring driver, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver tokenPERFORMANCE="REQUIRED"Under the Link Driver line, add the lines to enable frame types. Enable all frame types supported by the board. Use the frame setting to do this.For example, to enable all frame types for token ring, type the following: FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver token
   frame token-ring
   frame token-ring_snapTo enable all frame types for Ethernet, type the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.3
   frame ethernet_802.2
   frame ethernet_ii
   frame ethernet_snapThe first frame defined is the only one used for the initial "Get Nearest Server" request.Therefore, if some servers are using only one frame type, such as Ethernet_802.3, put that frame type first. That way your workstation can make a default connection to those servers.PAGENUM=216 ID="BP215"Whenever you edit the NET.CFG file, you must indent settings, as well as follow the other format requirements explained in IDREF="FM45501""NET.CFG Format Requirements" on page 42. PERFORMANCE="REQUIRED"ID="FM77010"Read the following chart to determine whether you need to specify a 
IDXID="w12195"BOOK="_idx" COLLECTION="nw41" TIDREF="i2948"IDXID="w12196"BOOK="_idx" COLLECTION="nw41" TIDREF="i3061"
node address in the NET.CFG file. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you are usingCOLNAME=2 ROTATE="0" MOREROWS="0"Do thisVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Extended Services or LAN Services set up for IDXID="w12197"BOOK="_idx" COLLECTION="nw41" TIDREF="i2948"
universally administered addressesCOLNAME=2 ROTATE="0" MOREROWS="0"You do not need to specify a node address. Go to IDREF="FM61647"Step 5.COLNAME=1 ROTATE="0" MOREROWS="0"Extended Services or LAN Services set up for locally administered addressesCOLNAME=2 ROTATE="0" MOREROWS="0"You must specify a IDXID="w12198"BOOK="_idx" COLLECTION="nw41" TIDREF="i2948"
node address. Use the address shown in the "NetAddress" parameter in the PROTOCOL.INI file. Remove the T first.For example, if the PROTOCOL.INI file shows the lineMOREINFO="NONE"NetAddress = "T400000007030" the address you specify in NET.CFG is MOREINFO="NONE"400000007030Go to IDREF="FM52010"Step 4.PERFORMANCE="REQUIRED"ID="FM52010"Add a line specifying the node address.Add this line under the "Link Driver" option, above or below the lines enabling frame types. The node address must be a 6-byte hexadecimal number (12 characters). Use the address you located in 
IDREF="FM77010"Step 3.For example, to set a node address for a token ring board in an Extended Services environment, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"node address 400000007030If your board supports octet bit reversal, you can specify the address in either canonical (least significant bit first) or non-canonical (most significant bit first) format. By default, the following frames are non-canonical (MSB):
PAGENUM=217 ID="BP216"MARK=BULLETToken ring PC Network IIEthernet frames are canonical (LSB). If you specify the address in the format that is not the default, you must type an 
M (most significant bit first) or 
L (least significant bit first) at the end of the address to tell ODINSUP which format you used.For example, for a token ring environment using the default format for the node address, the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG file contents box should contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver token
  frame token-ring
  frame token-ring_snap
  node address 400000007030Note that an 
M after the node address is not needed because the address specifies most significant bit first, the default format for token ring.For a token ring environment using the non-default format for the same node address, the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG file contents box should contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver token
  frame token-ring
  frame token-ring_snap
  node address 020000000E0CLIn this case, an 
L after the node address is needed because the address is specified in least-significant-bit-first format, the format that is not the default for token ring. For an Ethernet Extended Services environment, the NET.CFG file should now contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
  frame ethernet_802.3
  frame ethernet_802.2
  frame ethernet_ii
  frame ethernet_snap
  node address 00001B1B055C
PAGENUM=218 ID="BP217"If you don't know the node address, you can type a "dummy" address and continue. When you reboot your machine, a message showing the correct address will appear. At that point you can edit the NET.CFG file again and insert the address displayed at boot time.PERFORMANCE="REQUIRED"ID="FM61647"Bind ODINSUP to one or more ODI drivers.When ODINSUP is bound to a driver, the network board for that driver is used for Extended Services and LAN Services transmissions.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Add the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
    bind drivernameReplace drivername with the name of the ODI driver you installed with NetWare Client for OS/2. For example, for a token ring ODI driver, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
    bind tokenPERFORMANCE="REQUIRED"(Conditional) Specify an instance number if you have two or more boards using the same ODI driver. If you have two or more network boards using the same ODI driver, ODINSUP searches the network board slots in order and binds only to the first board of that type it finds. To have ODINSUP bind to a board other than the first one found, you specify an instance number. ODINSUP can be bound to a maximum of four boards.For example, if you have two token ring network boards, bind ODINSUP to both boards by typing an instance number for the second board, as shown:FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
    bind token
    bind token 2PERFORMANCE="REQUIRED"ID="FM86068"(Optional) Increase the size of the packet transmitted through the Link Support Layer.
IDXID="w12199"BOOK="_idx" COLLECTION="nw41" TIDREF="i3186"Increasing the packet size may improve transmission speed if you are using a Token Ring 16/4 board.
PAGENUM=219 ID="BP218"For other kinds of board, see the board documentation to determine the maximum packet size supported by the board. If the board supports a packet size larger than 1514, (the Link Support default), transmission speed may improve if you increase the Link Support Layer default to the board's maximum allowed size.To increase the default,PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Under the Link driver lines, add the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link supportPERFORMANCE="REQUIRED"Under the Link Support line, add the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"buffers number sizeIndent the line. Replace number with a number of buffers greater than 1. Replace buffer_size with a number of bytes greater than 576. NetWare Client for OS/2 cannot use more than 64 KB of memory for communication buffers. Header information takes 5 KB. This means that the buffer number multiplied by the buffer size (plus the header information) cannot be greater than 65,536 bytes. For example, 20 buffers multiplied by 1514 bytes equals 30,280 bytes. For example, you might typeIDXID="w12200"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"FORMAT="LINESPECIFIC"MOREINFO="NONE"link support
buffers 14 4202For Token Ring 16/4 boards, NetWare Client for OS/2 will probably have maximum performance if you specify 14 buffers, each with a size of 4202 bytes, as shown in the example above. PERFORMANCE="REQUIRED"ID="FM43734"Save your changes and exit the NET.CFG file. PERFORMANCE="REQUIRED"Exit the text editor.PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Shutdown from the OS/2 System menu to reboot your machine. When your machine starts again, ODINSUP support will be completely set up. NetWare Client for OS/2 and Extended Services/LAN Services will then use the same ODI driver and board to transmit on the network. 
PAGENUM=220 ID="BP219"RENDERAS="SECT2"ID="FM42614"ID="FM83865"ID="FM91165"Sample Configuration Files for ODINSUPIDXID="w12201"BOOK="_idx" COLLECTION="nw41" TIDREF="i3061"This section contains sample CONFIG.SYS, NET.CFG, and PROTOCOL.INI files for both Extended Services and LAN Requester environments. If you follow the steps in IDREF="FM62336""Setting Up ODINSUP" on page 208, your configuration files will look like the ones shown. We recommend following the steps rather than just referring to these sample files.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="31*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Sample FilesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM12691"ODINSUP Files for an Extended Services Environment COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88259"Extended Services Token Ring PROTOCOL.INI File for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88259"221COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM38988"Extended Services Token Ring CONFIG.SYS File for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38988"222COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88268"Extended Services Token Ring NET.CFG File for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88268"224COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM52892"ODINSUP Files for a LAN Requester Environment  COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM24823"LAN Requester Token Ring PROTOCOL.INI File for ODINSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24823"225COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM44967"LAN Requester Token Ring CONFIG.SYS File for ODINSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM44967"227COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM71297"LAN Requester Token Ring NET.CFG File for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM71297"229RENDERAS="SECT3"ID="FM12691"ODINSUP Files for an Extended Services EnvironmentThese files came from a computer with the following software installed:MARK=BULLETID="FM61515"OS/2 2.1Extended Services 1.0 (locally-administered addresses)NetWare Client for OS/2 with ODINSUP. The computer used Communications Manager to make a LAN connection to an IBM host. PAGENUM=221 ID="BP220"IDREF="FM88259"Figure 16-1 illustrates a PROTOCOL.INI file for this environment.LABEL="16-1" FLOAT="0"IDXID="w12202"BOOK="_idx" COLLECTION="nw41" TIDREF="i3614"ID="FM88259"Extended Services Token Ring PROTOCOL.INI File for ODINSUPFILEREF="c41q50a.tif"IDREF="FM38988"Figure 16-2 illustrates a CONFIG.SYS file for the environment shown on IDREF="FM61515"page 220. PAGENUM=222 ID="BP221"LABEL="16-2" FLOAT="0"IDXID="w12203"BOOK="_idx" COLLECTION="nw41" TIDREF="i769"ID="FM38988"Extended Services Token Ring CONFIG.SYS File for ODINSUPFILEREF="c41q18a.tif"PAGENUM=223 ID="BP222"IDREF="FM88268"Figure 16-4 illustrates a NET.CFG file for the environment shown on IDREF="FM61515"page 220.PAGENUM=224 ID="BP223"LABEL="16-4" FLOAT="0"IDXID="w12204"BOOK="_idx" COLLECTION="nw41" TIDREF="i2902"ID="FM88268"Extended Services Token Ring NET.CFG File for ODINSUPFILEREF="c41q51a.tif"RENDERAS="SECT3"ID="FM52892"ODINSUP Files for a LAN Requester EnvironmentThese files came from a computer with the following software installed:MARK=BULLETID="FM52187"OS/2 2.1LAN Requester 2.0NetWare Client for OS/2 with ODINSUPIDREF="FM24823"Figure 16-5 illustrates a PROTOCOL.INI file for this environment. IDREF="FM44967"Figure 16-7 illustrates a CONFIG.SYS file for this environment. PAGENUM=225 ID="BP224"LABEL="16-5" FLOAT="0"IDXID="w12205"BOOK="_idx" COLLECTION="nw41" TIDREF="i3614"ID="FM24823"LAN Requester Token Ring PROTOCOL.INI File for ODINSUP FILEREF="c41q57a.tif"PAGENUM=226 ID="BP225"PAGENUM=227 ID="BP226"LABEL="16-7" FLOAT="0"IDXID="w12206"BOOK="_idx" COLLECTION="nw41" TIDREF="i769"ID="FM44967"LAN Requester Token Ring CONFIG.SYS File for ODINSUPFILEREF="c41q55a.tif"PAGENUM=228 ID="BP227"PAGENUM=229 ID="BP228"IDREF="FM71297"Figure 16-9 illustrates a NET.CFG file for the environment shown on IDREF="FM52187"page 224. LABEL="16-9" FLOAT="0"IDXID="w12207"BOOK="_idx" COLLECTION="nw41" TIDREF="i2902"ID="FM71297"LAN Requester Token Ring NET.CFG File for ODINSUPFILEREF="c41q56a.tif"LABEL="17"PAGENUM=231 ID="BP229"Using LANSUPCOLS=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="FM76540"How Board Sharing Is Possible COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76540"231COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM87147"Setting Up LANSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87147"232IDXID="w12208"BOOK="_idx" COLLECTION="nw41" TIDREF="i2040"IDXID="w12209"BOOK="_idx" COLLECTION="nw41" TIDREF="i1740"
Use this chapter if you want NetWare ClientTM for OS/2* to share a network IDXID="w12210"BOOK="_idx" COLLECTION="nw41" TIDREF="i2850"
board with one or more of the following IBM* software products:TYPE="VERT"Extended ServicesIDXID="w12211"BOOK="_idx" COLLECTION="nw41" TIDREF="i1398"LAN Server
IDXID="w12212"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"LAN RequesterIf you have Extended Services or LAN Services, you may also want to set up the NetBIOS protocol. After doing the steps in this chapter, see IDREF="FM33934"Chapter 15, "Using NETBIOS," on page IDREF="FM33934"183. RENDERAS="SECT1"ID="FM76540"How Board Sharing Is PossibleNetWare Client for OS/2 uses protocol drivers and network drivers written to the ODITM (Open Data-Link Interface) specification. Extended Services and LAN Services use protocol drivers and network drivers written to the IDXID="w12213"BOOK="_idx" COLLECTION="nw41" TIDREF="i2629"
NDIS specification.Even though NetWare Client for OS/2 uses a different driver specification than Extended Services and LAN Services, NetWare Client for OS/2 can still share a network board with these products. This is possible because of two drivers that Novell provides:MARK=BULLETODINSUP, which lets Extended Services and LAN Services use ODI LAN drivers. PAGENUM=232 ID="BP230"Use ODINSUP when you want the ODI network driver to control the board. See IDREF="FM62336""Setting Up ODINSUP" on page 208. LANSUP, which lets NetWare Client for OS/2 use NDIS network drivers. Use LANSUP when you want the NDIS driver to control the board. See IDREF="FM87147""Setting Up LANSUP" on page 232. RENDERAS="SECT1"ID="FM87147"Setting Up LANSUPIDXID="w12214"BOOK="_idx" COLLECTION="nw41" TIDREF="i2056"IDXID="w12215"BOOK="_idx" COLLECTION="nw41" TIDREF="i2629"Except where noted, the instructions in this section apply whether you have Extended Services, LAN Services, or both. However, the sample configuration files shown differ depending on what IBM software you have. Be sure to refer to the correct files for your environment. Setting up LANSUP involves three parts. The first two parts are required; the third is optional. The parts and their page numbers are shown in the following table:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PartCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11232"Part A: Loading LANSUP in CONFIG.SYS COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11232"232COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM91745"Part B: Configuring LANSUP in NET.CFG COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91745"234COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86400"Part C: Increasing Packet Size for LANSUP (Optional) COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86400"239COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM46364"Sample Configuration Files for LANSUP  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46364"241Novell's LAN Support (LANSUP) device driver replaces the CMGRLANIDXID="w12216"BOOK="_idx" COLLECTION="nw41" TIDREF="i664"
 and TOKENEEIDXID="w12217"BOOK="_idx" COLLECTION="nw41" TIDREF="i4517"
 modules used in NetWare Client for OS/2 1.3.  CMGRLAN and TOKENEE are not supported in NetWare Client for OS/2  2.1. LANSUP works with NDIS drivers for PC Network II, Ethernet, and Token-Ring network boards. RENDERAS="SECT2"ID="FM11232"Part A: Loading LANSUP in CONFIG.SYSIDXID="w12218"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"In this section, you use the NetWare Client for OS/2 Installation program to load LANSUP in the CONFIG.SYS file. PAGENUM=233 ID="BP231"If you have not yet installed NetWare Client for OS/2, you can install it at the same time as you install LANSUP. These instructions are for LAN Server and LAN Requester version 2.x.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXInstall Extended Services on the workstation. Verify that you can get a Communications Manager or Database Manager connection. See the documentation for Extended Services. Install LAN Server or LAN Requester on the workstation. Verify that you can get a connection on your LAN Server network. See the documentation for LAN Services. RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED"  Start the NetWare Client for OS/2 Installation program. If NetWare Client for OS/2 is not installed, you can start the program from your 
CLASS=DISKWSOS2_1 diskette. Type
MOREINFO="NONE" INSTALL. You can install NetWare Client for OS/2 with this procedure. If NetWare Client for OS/2 is already installed, you can start the program by choosing the 
CLASS=MENUITEM MOREINFO="NONE"Installation icon from the 
CLASS=MENUITEM MOREINFO="NONE"Novell group on your desktop. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Requester on Workstation from the 
CLASS=MENUITEM MOREINFO="NONE"Installation menu. PERFORMANCE="REQUIRED"Verify the target and source directory and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select an action from the 
CLASS=MENUITEM MOREINFO="NONE"Requester Installation screen based on whether NetWare Client for OS/2 is installed.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is not installed, select 
CLASS=MENUITEM MOREINFO="NONE"Edit CONFIG.SYS and Copy All Files . . . and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"If NetWare Client for OS/2 is installed, select 
CLASS=MENUITEM MOREINFO="NONE"Only Edit CONFIG.SYS . . . and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.PERFORMANCE="REQUIRED"Select LANSUP as the ODI LAN driver for your network board and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue. . .Selecting LANSUP inserts the following line in the correct place in your CONFIG.SYS file:
PAGENUM=234 ID="BP232"FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=drive:\NETWARE\LANSUP.SYSPERFORMANCE="REQUIRED"Select your preferences for NetWare support for DOS and Windows applications and choose 
CLASS=MENUITEM MOREINFO="NONE"Continue . . .PERFORMANCE="REQUIRED"Select your preferences for optional protocol support and choose 
CLASS=MENUITEM MOREINFO="NONE"Save . . . PERFORMANCE="REQUIRED"Verify the filename and location and choose 
CLASS=MENUITEM MOREINFO="NONE"OK.If you have not installed NetWare Client for OS/2, the 
CLASS=MENUITEM MOREINFO="NONE"Copy Requester Files screen appears. Continue with 
IDREF="FM63326"Step 9. If you have installed NetWare Client for OS/2, the main installation menu appears. Go to 
IDREF="FM91745""Part B: Configuring LANSUP in NET.CFG" on page 234. PERFORMANCE="REQUIRED"ID="FM63326"Choose 
CLASS=MENUITEM MOREINFO="NONE"Copy and follow the screens to finish installing NetWare Client for OS/2. When the main menu returns, go to 
IDREF="FM91745""Part B: Configuring LANSUP in NET.CFG" on page 234. RENDERAS="SECT2"IDXID="w12219"BOOK="_idx" COLLECTION="nw41" TIDREF="i2056"ID="FM91745"Part B: Configuring LANSUP in NET.CFGIDXID="w12220"BOOK="_idx" COLLECTION="nw41" TIDREF="i2903"IDXID="w12221"BOOK="_idx" COLLECTION="nw41" TIDREF="i762"A NET.CFG file is required to use LANSUP. In this section, you edit or create a NET.CFG file that does the following:MARK=BULLETEnables frame types for LANSUPSpecifies to LANSUP the node address used by the network board and the format that address is transmitted inIn this section, you also decide whether to increase the size of the packet that can be transmitted through LANSUP.RENDERAS="SECT3"PrerequisiteMARK=CHECKBOXInstall NetWare Client for OS/2 with LANSUP by following the instructions in IDREF="FM11232""Part A: Loading LANSUP in CONFIG.SYS" on page 232.PAGENUM=235 ID="BP233"RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED" Choose CLASS=MENUITEM MOREINFO="NONE"This workstation . . . from the CLASS=MENUITEM MOREINFO="NONE"Configuration menu of the NetWare Client for OS/2 Installation program. If the NetWare Client for OS/2 Installation program is not running, complete the steps in 
IDREF="FM11232""Part A: Loading LANSUP in CONFIG.SYS" on page 232 and then return here.PERFORMANCE="REQUIRED"Verify the location of the NET.CFG file and choose 
CLASS=MENUITEM MOREINFO="NONE"Edit.The 
CLASS=MENUITEM MOREINFO="NONE"Edit NET.CFG window appears. You can choose a topic in the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box on this screen to get information about a topic. Then read the help window at the bottom of the screen. Choose the 
CLASS=MENUITEM MOREINFO="NONE"Usage, 
CLASS=MENUITEM MOREINFO="NONE"Description, and 
CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of your screen to see more information about the topic you've selected. For example, to see what frame types are supported for token ring drivers, choose "frame" from under "Link Driver" in the 
CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box. Then read the information in the help window.PERFORMANCE="REQUIRED"In the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents box, type the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansupPERFORMANCE="REQUIRED"Under the Link Driver line, add lines to enable at least one frame type. LANSUP can be used with Ethernet, token ring, and PCNet boards. IDREF="FM86270"Table 17-1 lists the supported frame types for LANSUP:LABEL="17-1" PGWIDE=0 TOCENTRY="1"ID="FM86270" List of Frame Types Supported by LANSUPCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"BoardCOLNAME=2 ROTATE="0" MOREROWS="0"Frame types supportedVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Token ringCOLNAME=2 ROTATE="0" MOREROWS="0"TOKEN-RINGTOKEN-RING_SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"ETHERNET_802.2ETHERNET_SNAPCOLNAME=1 ROTATE="0" MOREROWS="0"PCNetCOLNAME=2 ROTATE="0" MOREROWS="0"IBM_PCN2_802.2IBM_PCN2_SNAPPAGENUM=236 ID="BP234"For example, to enable a frame type for token ring, type the following: 
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
frame token-ringTo enable both frame types for Ethernet, type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
frame ethernet_802.2
frame ethernet_snapThe first frame defined is the only one used for the initial Get Nearest Server request. Therefore, if you have some servers that are using only one frame type, such as Ethernet 802.3, put that frame type first. That way your workstation can make a default connection to those servers.Use the Space bar to indent the lines. The MOREINFO="NONE"<Tab> key moves you to the next box on the screen. Put a blank line at the end of the file. You must follow these and other format requirements explained in the "Format of NET.CFG Options" topic. To see these requirements, select this topic from the CLASS=MENUITEM MOREINFO="NONE"NET.CFG Options box and choose the CLASS=MENUITEM MOREINFO="NONE"Usage button. Then read the information in the help window at the bottom of the screen.PERFORMANCE="REQUIRED"IDXID="w12222"BOOK="_idx" COLLECTION="nw41" TIDREF="i2948"IDXID="w12223"BOOK="_idx" COLLECTION="nw41" TIDREF="i2056"
Determine what node address you should use. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you are usingCOLNAME=2 ROTATE="0" MOREROWS="0"Get the node address from hereVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Extended Services or LAN Services set up for universally administered addressesCOLNAME=2 ROTATE="0" MOREROWS="0"Use the address assigned to the board by the vendor.COLNAME=1 ROTATE="0" MOREROWS="0"Extended Services or LAN Services set up for locally administered addressesCOLNAME=2 ROTATE="0" MOREROWS="0"Use the IDXID="w12224"BOOK="_idx" COLLECTION="nw41" TIDREF="i2948"
address shown in the "NetAddress" parameter in the PROTOCOL.INI file. Remove the T first. For example, if the PROTOCOL.INI file shows the lineMOREINFO="NONE"NetAddress = "T400000007030" the address you specify in NET.CFG is MOREINFO="NONE"400000007030PAGENUM=237 ID="BP235"PERFORMANCE="REQUIRED"Type a line specifying the node address.Type this line under the "Link Driver" option, above or below the lines enabling frame types. The node address must be a 6-byte hexadecimal number (12 characters). For example, to set a node address for a token ring board in a LAN Services environment, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"node address 10005a8c62d4If your board supports octet bit reversal, you can specify the address in either canonical (least significant bit first) or non-canonical (most significant bit first) format. By default, the following frames are non-canonical (MSB):
MARK=BULLETToken ring PC Network IIEthernet frames are canonical (LSB). If you specify the address in the format that is not the default, you must type an M (most significant bit first) or L (least significant bit first) at the end of the address to tell ODINSUP which format you used.For example, for a token ring environment using the default format for the node address, the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG file contents box should contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
frame token-ring
PAGENUM=238 ID="BP236"node address 10005a8c62d4Note that an M after the node address is not needed because the address is specified as the most significant bit first, the default format for token ring.For a token ring environment using the non-default format for the same node address, the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG file contents box should contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
frame token-ring
node address 08005A31462BLIn this case, an L after the node address is needed because the address is specified in least significant bit first format, the format which is not the default for token ring. For an Ethernet environment, the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG file contents box should contain lines similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
frame ethernet_802.2
frame ethernet_snap
node address 00001B1B055CIf you don't know the node address, you can type a "dummy" address and go to the next step. When you reboot your machine, a message showing the correct address appears. At that point, edit NET.CFG again and insert the address that was displayed at boot time.PERFORMANCE="REQUIRED"Decide whether to increase the size of the packet transmitted to the NDIS driver by LANSUP. Increasing the packet size may improve transmission speed if you are using a token ring 16/4 board.For other kinds of board, see the board documentation to determine the maximum packet size supported by the board. If the board supports a packet size larger than the Link Support Layer default, transmission speed may improve if you increase the Link Support Layer default to the board's maximum allowed size.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM15948"To increase the packet size, go to 
IDREF="FM86400""Part C: Increasing Packet Size for LANSUP (Optional)" on page 239. 
PAGENUM=239 ID="BP237"PERFORMANCE="REQUIRED"If you do not want to increase the packet size, go to 
IDREF="FM68193"Step 8.PERFORMANCE="REQUIRED"ID="FM68193"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save . . .PERFORMANCE="REQUIRED"Exit the NetWare Client for OS/2 installation program. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Shutdown from the OS/2 System menu to reboot your machine. When your computer starts again, LANSUP support will be set up. NetWare Client for OS/2 and Extended Services or LAN Services will then use the same NDIS driver and board to transmit on the network. RENDERAS="SECT2"ID="FM86400"Part C: Increasing Packet Size for LANSUP (Optional)IDXID="w12225"BOOK="_idx" COLLECTION="nw41" TIDREF="i3186"Complete this section only if you were directed to come here in IDREF="FM15948"Step 7a on page 238.In this section, youMARK=BULLETEdit NET.CFG to increase the size of the packet that can be transmitted through LANSUP.Edit PROTOCOL.INI to increase the size of the packet that can be transmitted through the NDIS drivers. RENDERAS="SECT3"PrerequisiteMARK=CHECKBOXInstall NetWare Client for OS/2 with LANSUP by following the instructions in IDREF="FM33397""Part A: Binding ODI Drivers in PROTOCOL.INI" on page 208.Follow the instructions in IDREF="FM91745""Part B: Configuring LANSUP in NET.CFG" on page 234.RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED" Select "Link support" in theCLASS=MENUITEM MOREINFO="NONE" NET.CFG Options box on the left of your screen. PAGENUM=240 ID="BP238"If the NetWare Client for OS/2 Installation program is not open to the 
CLASS=MENUITEM MOREINFO="NONE"Edit NET.CFG Window, complete the steps in 
IDREF="FM91745""Part B: Configuring LANSUP in NET.CFG" on page 234. Then return to this step.PERFORMANCE="REQUIRED"Select "buffers" under "Link Support."PERFORMANCE="REQUIRED"Read the information in the help window at the bottom of the screen to see how to set the Link Support buffers. You can choose the 
CLASS=MENUITEM MOREINFO="NONE"Usage, 
CLASS=MENUITEM MOREINFO="NONE"Description, and 
CLASS=MENUITEM MOREINFO="NONE"Example buttons on the right of your screen to see more information about Link Support. PERFORMANCE="REQUIRED"ID="FM82316"In the 
CLASS=MENUITEM MOREINFO="NONE"Current NET.CFG File Contents, add lines to change the "Link Support buffers" setting. Follow the usage requirements shown in the help window. Indent the line. Replace
 number with a number of buffers greater than 1. Replace
 buffer_size with a number of bytes greater than 576. NetWare Client for OS/2 cannot use more than 64 KB of memory for communication buffers. Header information takes 5 KB of memory. This means that the buffer number multiplied by the buffer size (plus the header information) cannot be greater than 65,536 bytes. For example, 20 buffers multiplied by 1514 bytes equals 30,280 bytes. For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w12226"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"link support
buffers 14 4202For token ring 16/4 boards, NetWare Client for OS/2 will probably have maximum performance if you specify 14 buffers, each with a size of 4,202 bytes, as shown in the example above. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Save . . .PERFORMANCE="REQUIRED"Exit the NetWare Client for OS/2 Installation program. Without rebooting your machine, go to Step 7. PERFORMANCE="REQUIRED"Run the IBM LAPS program to edit PROTOCOL.INI.
IDXID="w12227"BOOK="_idx" COLLECTION="nw41" TIDREF="i3615"PERFORMANCE="REQUIRED"Change the transmit buffer size to a number 6 bytes larger than the number you set for the Link Support buffer size in 
IDREF="FM82316"Step 4. 
PAGENUM=241 ID="BP239"The value you specify must be a multiple of 8. See your LAPS documentation for more about changing the transmit buffer size. Use a transmit buffer size of 4,208 if you are using Token Ring 16/4 boards. The LAPS program inserts the following line in NDIS MAC driver section of your PROTOCOL.INI file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"XMITBUFSIZE = 4208PERFORMANCE="REQUIRED"Exit the LAPS program. PERFORMANCE="REQUIRED"Choose 
CLASS=MENUITEM MOREINFO="NONE"Shutdown from the OS/2 System menu to restart your machine. When your machine starts again, LANSUP support will be set up. NetWare Client for OS/2 and Extended Services/LAN Services will transmit to the network from the same NDIS driver and network board. RENDERAS="SECT2"ID="FM46364"IDXID="w12228"BOOK="_idx" COLLECTION="nw41" TIDREF="i2056"
Sample Configuration Files for LANSUPThis section contains sample CONFIG.SYS, NET.CFG, and PROTOCOL.INI files for both Extended Services and LAN Requester environments. If you follow the steps in IDREF="FM87147""Setting Up LANSUP" on page 232, your configuration files will look like the ones shown. We recommend following the steps rather than just referring to these sample files.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="31*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Sample FilesCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM13606"LANSUP Files for an Extended Services Environment COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM28564"Extended Services Token Ring CONFIG.SYS File for LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28564"243COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM24616"Extended Services Token Ring NET.CFG File for LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24616"245COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM12790"Extended Services Token Ring PROTOCOL.INI File for LANSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM12790"246COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM34886"LANSUP Files for a LAN Requester Environment COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80194"LAN Requester Token Ring CONFIG.SYS File for LANSUP COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80194"248COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM20866"LAN Requester Token Ring NET.CFG File for LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20866"250COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM71555"LAN Requester Token Ring PROTOCOL.INI File for LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM71555"251PAGENUM=242 ID="BP240"RENDERAS="SECT3"ID="FM13606"LANSUP Files for an Extended Services EnvironmentThese files came from a computer with the following software installed:MARK=BULLETID="FM55663"OS/2 Version 2.1Extended Services version 1.0 (locally-administered addresses)NetWare Client for OS/2 with LANSUP. The computer used Communications Manager to make a LAN connection to an IBM host. IDREF="FM28564"Figure 17-1 illustrates a CONFIG.SYS file. PAGENUM=243 ID="BP241"LABEL="17-1" FLOAT="0"IDXID="w12229"BOOK="_idx" COLLECTION="nw41" TIDREF="i769"ID="FM28564"Extended Services Token Ring CONFIG.SYS File for LANSUP FILEREF="c41q52a.tif"PAGENUM=244 ID="BP242"IDREF="FM24616"Figure 17-3 illustrates a NET.CFG file for the environment shown on IDREF="FM55663"page 242.PAGENUM=245 ID="BP243"LABEL="17-3" FLOAT="0"IDXID="w12230"BOOK="_idx" COLLECTION="nw41" TIDREF="i2902"ID="FM24616"Extended Services Token Ring NET.CFG File for LANSUPFILEREF="c41q54a.tif"IDREF="FM12790"Figure 17-4 illustrates a PROTOCOL.INI file for the environment shown on IDREF="FM55663"page 242.PAGENUM=246 ID="BP244"LABEL="17-4" FLOAT="0"IDXID="w12231"BOOK="_idx" COLLECTION="nw41" TIDREF="i3614"ID="FM12790"Extended Services Token Ring PROTOCOL.INI File for LANSUP FILEREF="c41q53a.tif"PAGENUM=247 ID="BP245"RENDERAS="SECT3"ID="FM34886"LANSUP Files for a LAN Requester EnvironmentThese files came from a computer with the following software installed:MARK=BULLETID="FM15531"OS/2 2.xLAN Requester 2.0NetWare Client for OS/2 with LANSUPIDREF="FM80194"Figure 17-6 illustrates a CONFIG.SYS file for this environment. PAGENUM=248 ID="BP246"LABEL="17-6" FLOAT="0"IDXID="w12232"BOOK="_idx" COLLECTION="nw41" TIDREF="i769"ID="FM80194"LAN Requester Token Ring CONFIG.SYS File for LANSUP FILEREF="c41q60a.tif"PAGENUM=249 ID="BP247"PAGENUM=250 ID="BP248"IDREF="FM20866"Figure 17-8 illustrates a NET.CFG file for the environment shown on IDREF="FM15531"page 247. LABEL="17-8" FLOAT="0"IDXID="w12233"BOOK="_idx" COLLECTION="nw41" TIDREF="i2902"ID="FM20866"LAN Requester Token Ring NET.CFG File for LANSUPFILEREF="c41q59a.tif"IDREF="FM71555"Figure 17-9 illustrates a PROTOCOL.INI file for the environment shown on IDREF="FM15531"page 247.PAGENUM=251 ID="BP249"LABEL="17-9" FLOAT="0"IDXID="w12234"BOOK="_idx" COLLECTION="nw41" TIDREF="i3614"ID="FM71555"LAN Requester Token Ring PROTOCOL.INI File for LANSUP FILEREF="c41q58a.tif"PAGENUM=252 ID="BP250"LABEL="18"PAGENUM=253 ID="BP251"Accessing Online DocumentationCOLS=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="FM34632"Using the Online Reference COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34632"253RENDERAS="SECT1"ID="FM34632"
Using the Online ReferenceA copy of this manual is available on line. RENDERAS="SECT2"IDXID="w12235"BOOK="_idx" COLLECTION="nw41" TIDREF="i3075"
ProcedurePERFORMANCE="REQUIRED"From the OS/2 desktop, choose the CLASS=MENUITEM MOREINFO="NONE"Novell icon.The 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window appears.PERFORMANCE="REQUIRED"From the 
CLASS=MENUITEM MOREINFO="NONE"Novell - Icon View window, choose the 
CLASS=MENUITEM MOREINFO="NONE"Reference Manual icon.The online reference manual appears.PERFORMANCE="REQUIRED"To exit the online reference, double-click the upper right hand corner of the online reference manual window.LABEL="A"PAGENUM=255 ID="BP1A"ID="FM50568"NET.CFG Options ReferenceCOLS=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="FM98722""Using the NET.CFG Reference Pages"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98722"256COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83875""Daemon Configuration"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83875"257COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM28739""Link Driver"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28739"257COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM25534""Link Support"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM30704"270COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM59417""Named Pipes"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM59417"272COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM99769""NetWare NetBIOS"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99769"276COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM57102""NetWare Requester"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57102"284COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM53606""Protocol ODINSUP"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM53606"292COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM38316""Protocol Stack IPX"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38316"293COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM73864""Protocol Stack SPX"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM73864"296COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM53519""Token Ring Source-Route Driver"COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM53519"299ID="FM37650"This appendix contains an alphabetical listing of NET.CFG options. For instructions on editing a NET.CFG file, format requirements, and reasons to configure, see IDREF="FM65037"Chapter 4, "Configuring NetWare Client for OS/2," on page IDREF="FM65037"37.All information in this appendix is also found online in the NetWare ClientTM for OS/2* installation and configuration program.PAGENUM=256 ID="BP2A"RENDERAS="SECT1"ID="FM98722"Using the NET.CFG Reference PagesIDREF="FM26840"Figure A-1 explains how to read NET.CFG reference pages in this appendix.LABEL="A-1" FLOAT="0"ID="FM26840"Format of NET.CFG Reference PagesFILEREF="c41q02a.tif"PAGENUM=257 ID="BP3A"RENDERAS="SECT1"ID="FM83875"Daemon ConfigurationIDXID="w12236"BOOK="_idx" COLLECTION="nw41" TIDREF="i910"Use this option to control the length of time network-related error messages stay on your screen. This option controls only pop-up and broadcast messages. Pop-up and broadcast messages appear in a small box on your screen and prompt you to "Press MOREINFO="NONE"<Esc> to continue . . ." RENDERAS="SECT2"SettingRENDERAS="SECT3"message timeoutIDXID="w12237"BOOK="_idx" COLLECTION="nw41" TIDREF="i2417"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"daemon configurationMOREINFO="NONE"  message timeout numberReplace number with a number of milliseconds that you want pop-up and broadcast messages to display on your screen before disappearing. Replace number with 0 (zero) to prevent pop-up and broadcast messages from displaying at all.If you leave this line out of NET.CFG, pop-ups and broadcast messages are displayed until you press MOREINFO="NONE"<Esc>. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Pop-up and broadcast messages display until you press MOREINFO="NONE"<Esc>.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To prevent pop-up and broadcast messages from displaying:MOREINFO="NONE"daemon configurationMOREINFO="NONE"  message timeout 0RENDERAS="SECT1"ID="FM28739"Link DriverIDXID="w12238"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"
Use this option to specify the hardware configuration of the LAN drivers for each network board in your workstation. PAGENUM=258 ID="BP4A"Use this option only if the network boards are not using the default settings. The settings you specify with this option should match the hardware settings for your boards. If you have more than one network board in your workstation, put this option in your NET.CFG file for each board. RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver name
MOREINFO="NONE"alternate
MOREINFO="NONE"dma [index] 
channel
MOREINFO="NONE"frame name
MOREINFO="NONE"int [index]
 irqmem [
index] 
starting_address [
size]
MOREINFO="NONE"node address number
MOREINFO="NONE"port [index] 
starting_port [
number]
MOREINFO="NONE"protocol name 
id 
frame
MOREINFO="NONE"slot numberRENDERAS="SECT2"OptionRENDERAS="SECT3"link driverUse this option to specify the name of the LAN driver whose defaults you want to modify. 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 nameReplace name with the name of the driver. IDREF="FM37012"Table A-1 lists some network boards and their driver names.LABEL="A-1" PGWIDE=0 TOCENTRY="1"ID="FM37012" List of Network Boards and DriversCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Driver nameCOLNAME=2 ROTATE="0" MOREROWS="0"Network boardVALIGN="TOP"COLNAME=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 NE/2-32COLNAME=1 ROTATE="0" MOREROWS="0"NE1000COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE1000COLNAME=1 ROTATE="0" MOREROWS="0"NE2000COLNAME=2 ROTATE="0" MOREROWS="0"Novell Ethernet NE2000COLNAME=1 ROTATE="0" MOREROWS="0"TOKENCOLNAME=2 ROTATE="0" MOREROWS="0"IBM Token Ring COLNAME=1 ROTATE="0" MOREROWS="0"LANSUPCOLNAME=2 ROTATE="0" MOREROWS="0"Boards using NDIS driversCOLNAME=1 ROTATE="0" MOREROWS="0"ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0"IBM Token Ring and Ethernet Communications ManagerCOLNAME=1 ROTATE="0" MOREROWS="0"3C501COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink series 501COLNAME=1 ROTATE="0" MOREROWS="0"3C503COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink series 503COLNAME=1 ROTATE="0" MOREROWS="0"3C505COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink series 505COLNAME=1 ROTATE="0" MOREROWS="0"3C523COLNAME=2 ROTATE="0" MOREROWS="0"3Com EtherLink/MC seriesCOLNAME=1 ROTATE="0" MOREROWS="0"PCN2COLNAME=2 ROTATE="0" MOREROWS="0"IBM PC Network II and II/A (older Novell frame format)COLNAME=1 ROTATE="0" MOREROWS="0"PCN2LCOLNAME=2 ROTATE="0" MOREROWS="0"IBM PC Network II and II/A (newer IBM frame format)PAGENUM=259 ID="BP5A"The PCN2 and PCN2L drivers cannot be used in the same workstation. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"None.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To configure an IBM Token Ring PC driver, type the following with any settings from the following pages: MOREINFO="NONE"link driver tokenRENDERAS="SECT2"PAGENUM=260 ID="BP6A"SettingsRENDERAS="SECT3"IDXID="w12239"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"
alternateIDXID="w12240"BOOK="_idx" COLLECTION="nw41" TIDREF="i168"
Specifies an alternate board. Normally, the LANSUP, IBM token ring and NTR2000, and PCN2L 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"link driver name  MOREINFO="NONE"MOREINFO="NONE"   alternateCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the LANSUP.COM driver to use an alternate board, you would place the following lines in your NET.CFG file:MOREINFO="NONE"link driver lansupMOREINFO="NONE"  alternateRENDERAS="SECT3"DMAIDXID="w12241"BOOK="_idx" COLLECTION="nw41" TIDREF="i1164"IDXID="w12242"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"Use this setting to specify which direct memory access (DMA) channel the network board uses. 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 name  MOREINFO="NONE"MOREINFO="NONE"   dma [index] channelReplace index with either #1 or #2 (optional).The driver configuration table for each board can store the DMA channel number on either of two lines. The lines are labeled #1 and #2.   Replace channel with the number of the DMA channel used by the board. The channel numbers for different network boards are recorded in the documentation from the board manufacturers. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Index: #1 Most boards use this default.Channel: Set by the driver. See the documentation for the board. You can't change the DMA setting on 3Com Etherlink 503 boards, and you do not need to change it on 3Com Etherlink 505 boards. You can change the DMA setting on 3Com Etherlink 523 boards.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the DMA channel for a 3Com Etherlink 505 board:MOREINFO="NONE"link driver 3C505MOREINFO="NONE"  dma 7PAGENUM=261 ID="BP7A"RENDERAS="SECT3"ID="FM82317"IDXID="w12243"BOOK="_idx" COLLECTION="nw41" TIDREF="i1565"
frameIDXID="w12244"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"Use this setting to specify which frame type the driver for your network board uses. Use this setting only for boards that support more than one frame type or if you want multiple networks (separate network addresses) to share the same network board and cabling.The frame type transmitted by the workstation should match the type of packets being transmitted by the servers on your 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"link driver name  MOREINFO="NONE"MOREINFO="NONE"   frame nameReplace name with the name of the frame type. The following table lists common frame types and the network board drivers that support each type. This list is not comprehensive.LABEL="A-2" PGWIDE=0 TOCENTRY="1" List of Frame Types and DriversCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Frame typeCOLNAME=2 ROTATE="0" MOREROWS="0"Network board driverVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Ethernet_802.3COLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2_32, 3C501, 3C503, 3C505, 3C523, EXOS205, EXOS215, ODINSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet_802.2COLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2_32, 3C501, 3C503, EXOS205, EXOS215, ODINSUP, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet_IICOLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2_32, 3C501, 3C503, 3C505, 3C523, EXOS205, EXOS215, ODINSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Ethernet_SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"NE1000, NE2000, NE2100, NE2, NE2_32, 3C501, 3C503, EXOS205, EXOS215, ODINSUP, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Token RingCOLNAME=2 ROTATE="0" MOREROWS="0"ODINSUP, TOKEN, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Token Ring_SNAPCOLNAME=2 ROTATE="0" MOREROWS="0"ODINSUP, TOKEN, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"IBM_pcn2_802.2COLNAME=2 ROTATE="0" MOREROWS="0"PCN2, PCN2L, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"IBM_pcn2_snapCOLNAME=2 ROTATE="0" MOREROWS="0"PCN2, PCN2L, LANSUPCOLNAME=1 ROTATE="0" MOREROWS="0"Novell_rx-netCOLNAME=2 ROTATE="0" MOREROWS="0"TRXNET, TRXNET2COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Set by the driver. See the documentation for the board. COLNAME=1 ROTATE="0" MOREROWS="0"ExamplesCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the Ethernet 802.2 frame type for an NE2000 board: MOREINFO="NONE"link driver ne2000MOREINFO="NONE"  frame ethernet_802.2To specify the Ethernet 802.2 and Ethernet 802.3 frame types for an NE1000 board (for two logical networks): MOREINFO="NONE"link driver ne1000MOREINFO="NONE"  frame ethernet_802.2MOREINFO="NONE"  frame ethernet_802.3PAGENUM=263 ID="BP8A"If you are using the ODINSUP driver, you must enable multiple frame types for each driver. For Ethernet, enable Ethernet_802.3, Ethernet_II, Ethernet_802.2, and Ethernet_SNAP.For token ring, enable token ring and token ring_SNAP. For more information about ODINSUP, see IDREF="FM99600"Chapter 16, "Using ODINSUP," on page IDREF="FM99600"207.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. You can use up to four frame types for one set of Ethernet cabling. 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. For token ring cabling, two frames types are the maximum allowed.The default frame type for Ethernet drivers has changed to Ethernet_802.2. This may conflict with the frame type used on your network. For more information about specifying frame types, see IDREF="FM59288"Chapter 5, "Using Network Boards and LAN Drivers," on page IDREF="FM59288"51.PAGENUM=264 ID="BP9A"RENDERAS="SECT3"IDXID="w12245"BOOK="_idx" COLLECTION="nw41" TIDREF="i1841"
intUse this setting to specify which interrupt line IDXID="w12246"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"
(IRQ)IDXID="w12247"BOOK="_idx" COLLECTION="nw41" TIDREF="i1986"
 the network board uses to communicate with the 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 driver name  MOREINFO="NONE"MOREINFO="NONE"   int [index] irqReplace index with either #1 or #2 (optional).The driver configuration table for each board can store the interrupt line number on either of two lines in the table. The lines are labeled #1 and #2.Replace irq with the number of the interrupt line used by the board.To determine the interrupt line number for your network board, see the documentation for the board. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Index: #1IRQ: Set by the driver. See the documentation for the board. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the interrupt line for an NE2000 board:MOREINFO="NONE"link driver ne2000MOREINFO="NONE"  int 3Before changing the interrupt setting for your board, be sure you know what interrupt settings are used on other hardware (such as monitors) that you are using. For example, interrupts 2 and 9-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. If you are using a PS/2 computer on a token ring network, do not autoconfigure with the CLASS=DISKReference diskette. Doing so may cause problems.PAGENUM=265 ID="BP10A"RENDERAS="SECT3"memIDXID="w12248"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"IDXID="w12249"BOOK="_idx" COLLECTION="nw41" TIDREF="i2375"IDXID="w12250"BOOK="_idx" COLLECTION="nw41" TIDREF="i2373"Use this setting to specify what range of memory can be used by the 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 driver name  MOREINFO="NONE"MOREINFO="NONE"   mem [index] starting_address sizeReplace index with either #1 or #2 (optional).The driver configuration table for each board can store the memory range on either of two lines in the table. The lines are labeled #1 and #2.   Replace starting_address with a hexadecimal memory address that begins the range. This address must be five digits and the same as the address designated for the board by the manufacturer. See the documentation for the board.Replace size with a hexadecimal number of paragraphs in the memory range (optional).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0""Index: #1"=ROM address  "Index: #2"=RAM address (D8000 by default by TOKEN.SYS)Starting_address: Set by the driver. See the documentation for the board. Size: Set by the driver. See the documentation for the board. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the memory range for a token ring board:MOREINFO="NONE"link driver tokenMOREINFO="NONE"  mem cc000 200Assign each board a unique memory range. PAGENUM=266 ID="BP11A"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"node addressIDXID="w12251"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"IDXID="w12252"BOOK="_idx" COLLECTION="nw41" TIDREF="i2947"Use this setting to change the node address of a network board. This setting can only be used with network boards that allow you to override the preset address. 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"link driver name  MOREINFO="NONE"MOREINFO="NONE"   node address numberReplace number with a hexadecimal address. You can specify the address with either the least significant bit first (lsb format) or the most significant bit first (msb format).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The address preset on the board. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change the address for board that uses the ODINSUP driver:MOREINFO="NONE"link driver odinsupMOREINFO="NONE"  node address 02608c861759PAGENUM=267 ID="BP12A"RENDERAS="SECT3"portIDXID="w12253"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"IDXID="w12254"BOOK="_idx" COLLECTION="nw41" TIDREF="i3337"Use this setting to specify which range of I/O ports the network board uses. 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 name  MOREINFO="NONE"MOREINFO="NONE"   port [index] starting_port [number]Replace index with either #1 or #2 (optional).The driver configuration table for each board can store information about ports on either of two lines in the table. The lines are labeled #1 and #2.Replace starting_port with a hexadecimal port number that begins the range. We recommend not using 2EO and 2FO since these port numbers are normally used by ARCnet for other functions.Replace number with the hexadecimal number of bytes in the range (optional).COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Index: #1Starting_port: Set by the driver. See the documentation for the board. Number: Set by the driver. See the documentation for the board.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the memory range for board that uses the NE2000 driver:MOREINFO="NONE"link driver ne2000MOREINFO="NONE"  port 300PAGENUM=268 ID="BP13A"RENDERAS="SECT3"protocolIDXID="w12255"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"IDXID="w12256"BOOK="_idx" COLLECTION="nw41" TIDREF="i3601"Use this setting to allow LAN drivers to use protocols that have different frame types. 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 name  MOREINFO="NONE"MOREINFO="NONE"   protocol name ID frameReplace name with the acronym of an ODI-compliant protocol. Some common protocols are:ARP  IP  IPX (the NetWare protocol)  RARPReplace ID with the hexadecimal number of the protocol that goes with the frame type you specify. The following table shows common protocols with some frame types and hexadecimal numbers they support.Replace frame with the name of the frame type used with the protocol. The following table lists some common frame types.LABEL="A-3" PGWIDE=1 TOCENTRY="1" List of Protocols, Frame Types, and Hexadecimal ID NumbersCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProtocolCOLNAME=2 ROTATE="0" MOREROWS="0"Frame typeCOLNAME=3 ROTATE="0" MOREROWS="0"Hex numberVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"Ethernet_802.3  Ethernet_802.2  Token Ring  IBM_PCN2_802.2  Ethernet_II  Ethernet_SNAP  Token Ring_SNAP  IBM_PCN2_SNAP  Novell_RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"0  e0  e0  e0  8137  8137  8137  8137  faCOLNAME=1 ROTATE="0" MOREROWS="0"IPCOLNAME=2 ROTATE="0" MOREROWS="0"Ethernet_II  Ethernet_SNAP  Token Ring_SNAP  Novell_RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"800  800  800  d4COLNAME=1 ROTATE="0" MOREROWS="0"ARPCOLNAME=2 ROTATE="0" MOREROWS="0"Ethernet_II  Ethernet_SNAP  Token Ring_SNAP  Novell_RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"806  806  806  d5COLNAME=1 ROTATE="0" MOREROWS="0"RAR PCOLNAME=2 ROTATE="0" MOREROWS="0"Ethernet_II  Ethernet_SNAP  Token Ring_SNAP  Novell_RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"8035  8035  8035  d6COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Name: IPXID: 0Frame: Ethernet_802.3COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify the ARP protocol for an Ethernet II frame:MOREINFO="NONE"link driver NE2000MOREINFO="NONE"  protocol arp 806 ethernet_iiPAGENUM=269 ID="BP14A"RENDERAS="SECT3"IDXID="w12257"BOOK="_idx" COLLECTION="nw41" TIDREF="i4171"ID="FM91351"slotIDXID="w12258"BOOK="_idx" COLLECTION="nw41" TIDREF="i2108"Use this setting to tell NetWare Client for OS/2 which expansion slot an EISA or Microchannel board is using. EISA and Microchannel boards are self-configuring, and NetWare Client for OS/2 can obtain all Link Driver information from the board itself. PAGENUM=270 ID="BP15A"You have to tell NetWare Client for OS/2 which slot the board is using or, if you only have one board of a particular type, tell NetWare Client for OS/2 to scan all slots until it finds that 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"link driver name  MOREINFO="NONE"MOREINFO="NONE"   slot numberReplace number with the number of the expansion slot the board is using or a question mark to tell NetWare Client for OS/2 to scan all slots. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To automatically configure the drivers for an NE/2 board in slot 4 and an NE/2 board in slot 2:MOREINFO="NONE"link driver ne2MOREINFO="NONE"  slot 4MOREINFO="NONE"link driver ne2MOREINFO="NONE"  slot 2This slot setting is the only Link Driver hardware-related setting you need to specify in this case. RENDERAS="SECT1"ID="FM25534"ID="FM30704"Link SupportIDXID="w12259"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"
Use this option to adjust the number and size of communication buffers used by NetWare Client for OS/2.RENDERAS="SECT2"PAGENUM=271 ID="BP16A"SettingRENDERAS="SECT3"IDXID="w12260"BOOK="_idx" COLLECTION="nw41" TIDREF="i2121"
buffersIDXID="w12261"BOOK="_idx" COLLECTION="nw41" TIDREF="i552"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 supportMOREINFO="NONE"  buffers numberMOREINFO="NONE" [buffer_size]Replace number with a number of buffers greater than 1. Replace buffer_size with a number of bytes greater than 576. NetWare Client for OS/2 cannot use more than 64 KB of memory for communication buffers. Header information takes 5 KB. This means that the buffer number multiplied by the buffer size (plus the header information) cannot be greater than 65,536 bytes. For example, 20 buffers multiplied by 1514 bytes equals 30,280 bytes.COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Number: 20 buffersBuffer_size: 1514 bytesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExamplesCOLNAME=2 ROTATE="0" MOREROWS="0"For an Ethernet configuration:MOREINFO="NONE"link supportMOREINFO="NONE"  buffers 15 1514For a token ring configuration:MOREINFO="NONE"link supportMOREINFO="NONE"  buffers 14 4210RENDERAS="SECT2"PAGENUM=272 ID="BP17A"NotesNUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Increasing efficiency. For most efficient communication, your link support buffer size should be the same size as the packets that your workstation will receive over the network. You may want to set the link support buffer size equal to the largest buffer size that the network boards in your workstation will support. Using the TRXNET.SYS driver. If your workstation experiences performance problems running with TRXNET.SYS, you may need to reconfigure the number and size of link support buffers allowed. Set the following values: FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"link supportMOREINFO="NONE"buffers 15 4202TRXNET.SYS only supports SMC100, 110, and 120 cards. RENDERAS="SECT1"ID="FM59417"Named PipesIDXID="w12262"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"Use this option to manage Named Pipes sessions. For an OS/2 workstation to function as a Named Pipes server or client, you must have selected Named Pipes when you installed NetWare Client for OS/2 on that workstation. See IDREF="FM25310""Installing Named Pipes for OS/2" on page 169.RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"named pipes
MOREINFO="NONE"advertise board board number
MOREINFO="NONE"client sessions number
MOREINFO="NONE"machine names numberRENDERAS="SECT2"PAGENUM=273 ID="BP18A"SettingsRENDERAS="SECT3"IDXID="w12263"BOOK="_idx" COLLECTION="nw41" TIDREF="i129"IDXID="w12264"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"
advertise boardUse this setting to specify a board that the Named Pipes server uses to advertise itself. You should only configure more than one of this setting when the boards specified are part of separate networks. 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 pipesMOREINFO="NONE"  advertise board board numberReplace board number with the logical board number of a network board. Board number can be a value from 1 to 16.Logical board numbers are assigned in ascending order to each frame type as they appear in your configuration. Note that logical board numbers are assigned to default frame types.The board number given must be the logical board number of a frame type used by IPX. Note: You specify IPX usage of a frame type by using the protocol setting under the link driver option.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The Named Pipes server will advertise itself over IPX's primary network board when this setting is not specified, out of range, or if the board number given does not match the logical board number of a frame type in use by IPX.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleMOREINFO="NONE" COLNAME=2 ROTATE="0" MOREROWS="0"Configure Named Pipes server as follows in order to use the logical boards defined by the NE2000 link driver and the Ethernet 802.2 and Ethernet 802.3 frame types to advertise the server:MOREINFO="NONE"Link Driver NE2MOREINFO="NONE"  Frame Ethernet_802.2;logical board 1MOREINFO="NONE"  Frame Ethernet_II;logical board 2MOREINFO="NONE"  Protocol IPX E0 Ethernet_802.2MOREINFO="NONE"  Protocol IP 800 Ethernet_IIMOREINFO="NONE"Link Driver NE2000MOREINFO="NONE"  Frame Ethernet_802.2;logical board 3MOREINFO="NONE"  Frame Ethernet_802.3;logical board 4MOREINFO="NONE"  Protocol IPX E0 Ethernet_802.2MOREINFO="NONE"  Protocol IPX 0 Ethernet_802.3MOREINFO="NONE"Named PipesMOREINFO="NONE"  Advertise Board 3MOREINFO="NONE"  Advertise Board 4PAGENUM=274 ID="BP19A"RENDERAS="SECT3"IDXID="w12265"BOOK="_idx" COLLECTION="nw41" TIDREF="i649"IDXID="w12266"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"
client sessionsUse this setting to specify the maximum number of connections a workstation can establish with all Named Pipes servers. 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 pipesMOREINFO="NONE"  client sessions numberReplace number with a number from 3 to 128.You need at least one client session for each connection from an OS/2 application to a Named Pipes server. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16 sessions.The default is usually adequate, except with applications that use many Named Pipes.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow each client thirty sessions:MOREINFO="NONE"named pipesMOREINFO="NONE"  client sessions 30PAGENUM=275 ID="BP20A"RENDERAS="SECT3"IDXID="w12267"BOOK="_idx" COLLECTION="nw41" TIDREF="i2257"IDXID="w12268"BOOK="_idx" COLLECTION="nw41" TIDREF="i2594"
machine namesUse this setting to force Named Pipes to create a local table of server names. This is used in all sessions on an OS/2 client workstation. This setting may be necessary for remote Named Pipes operations when there are no NetWare servers or IPX-compliant routers on 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"named pipesMOREINFO="NONE"  machine names numberReplace number with a number from 4 to 100. The number represents how many Named Pipes server names you want to cache.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"0 (i.e., query network for Named Pipes server names)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the number of locally cached Named Pipes server names to 5:MOREINFO="NONE"named pipesMOREINFO="NONE"  machine names 5PAGENUM=276 ID="BP21A"RENDERAS="SECT1"ID="FM99769"NetWare NetBIOSIDXID="w12269"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use this option to manage NetBIOS names and sessions or to affect the internal memory allocation for NetBIOS. LABEL="A-4" PGWIDE=0 TOCENTRY="1" Categories of NetWare NetBIOS SettingsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"SettingCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Name managementCOLNAME=2 ROTATE="0" MOREROWS="0"Broadcast count  Broadcast delay  Internet  NamesCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM60878"278  IDREF="FM30147"281281  IDREF="FM23424"282  IDREF="FM40911"282COLNAME=1 ROTATE="0" MOREROWS="0"Session creationCOLNAME=2 ROTATE="0" MOREROWS="0"Retry count  Retry delay  SessionsCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM50189"283  IDREF="FM63912"283  IDREF="FM65254"284COLNAME=1 ROTATE="0" MOREROWS="0"Session managementCOLNAME=2 ROTATE="0" MOREROWS="0"Abort timeout  Listen timeout  Verify timeoutCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM52917"277  IDREF="FM52917"277  IDREF="FM52917"277COLNAME=1 ROTATE="0" MOREROWS="0"Command managementCOLNAME=2 ROTATE="0" MOREROWS="0"CommandsCOLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM56421"281RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"netware netbios
MOREINFO="NONE"abort timeout number
MOREINFO="NONE"bind board_number
MOREINFO="NONE"broadcast count number
MOREINFO="NONE"broadcast delay number
MOREINFO="NONE"commands number
MOREINFO="NONE"internet [on|off]
MOREINFO="NONE"listen timeout number
MOREINFO="NONE"names number
MOREINFO="NONE"retry count number
MOREINFO="NONE"retry delay number
MOREINFO="NONE"sessions number
MOREINFO="NONE"verify timeout numberRENDERAS="SECT2"PAGENUM=277 ID="BP22A"SettingsRENDERAS="SECT3"ID="FM52917"abortIDXID="w12270"BOOK="_idx" COLLECTION="nw41" TIDREF="i45"
 timeoutIDXID="w12271"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"RENDERAS="SECT3"listenIDXID="w12272"BOOK="_idx" COLLECTION="nw41" TIDREF="i2131"
 timeoutIDXID="w12273"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"RENDERAS="SECT3"verifyIDXID="w12274"BOOK="_idx" COLLECTION="nw41" TIDREF="i4760"
 timeoutIDXID="w12275"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use these settings to monitor and control your NetBIOS connections. When NetBIOS sessions at a sending computer don't receive 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.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"netware netbiosMOREINFO="NONE"  abort timeout number  MOREINFO="NONE"MOREINFO="NONE"   listen timeout number  MOREINFO="NONE"MOREINFO="NONE"   verify timeout numberAbort timeout: Replace number with a number of milliseconds greater than 500. Listen timeout: Replace number with a number of milliseconds greater than 200.Verify timeout: Replace number with a number of milliseconds greater than 100. 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"Syntax continuedCOLNAME=2 ROTATE="0" MOREROWS="0"The ratio between these settings must remain the same. For example, if you double the Listen timeout value, you must also double the Abort timeout and Verify timeout values.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"Abort timeout: 30,000 milliseconds  Listen timeout: 6,000 milliseconds  Verify timeout: 3,000 millisecondsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExamplesCOLNAME=2 ROTATE="0" MOREROWS="0"To make NetBIOS wait longer before sending a request- for acknowledgment packet, sending the packet requesting immediate response, and terminating the session:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  abort timeout 45000MOREINFO="NONE"  listen timeout 8000MOREINFO="NONE"  verify timeout 4000PAGENUM=278 ID="BP23A"RENDERAS="SECT3"ID="FM60878"IDXID="w12276"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"IDXID="w12277"BOOK="_idx" COLLECTION="nw41" TIDREF="i436"
bindUse this setting to specify the primary NetBIOS network board in your workstation. PAGENUM=279 ID="BP24A"NetBIOS uses its primary board to manage NetBIOS names. You can only configure one primary NetBIOS network board.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"netware netbiosMOREINFO="NONE"  bind board_numberReplace board_number with the logical board number of a network board. Board_number can be a value from 1 to 16.Logical board numbers are assigned in ascending order to each frame type as they appear in your configuration. Note that logical board numbers are assigned to default frame types.The board_number given must be the logical board number of a frame type used by IPX. Note: You specify IPX usage of a frame type by using the protocol setting under the link driver option.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"NetBIOS uses IPX's primary board as its own primary board when the bind setting is not specified, out of range, or if the board_number given does not match the logical board number of a frame type in use by IPX.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"Configure NetBIOS as follows in order to use the logical board defined by the NE2000 link driver and the Ethernet 802.3 frame type as the NetBIOS primary network board:MOREINFO="NONE"Link Driver NE2TMOREINFO="NONE"  Frame Ethernet_802.2;logical board 1MOREINFO="NONE"  Frame Ethernet_II;logical board 2MOREINFO="NONE"  Protocol IPX 0 Ethernet_802.2MOREINFO="NONE"  Protocol IP 800 Ethernet_II  MOREINFO="NONE"Link Driver NE2000MOREINFO="NONE"  Frame Ethernet_802.3;logical board 3MOREINFO="NONE"  Protocol IPX 0 Ethernet_802.3  MOREINFO="NONE"NetWare Netbios  Bind 3PAGENUM=280 ID="BP25A"RENDERAS="SECT3"broadcast countUse this setting to specify how many times NetBIOS broadcasts a query or claim for the name being used by an application.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"netware netbiosMOREINFO="NONE"  broadcast count numberReplace number with a number of queries greater than 1. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"With internet on: 4 times.  With internet off: 2 times.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To broadcast more often:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  broadcast count 8PAGENUM=281 ID="BP26A"RENDERAS="SECT3"ID="FM30147"broadcastIDXID="w12278"BOOK="_idx" COLLECTION="nw41" TIDREF="i520"
 delayIDXID="w12279"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use this setting to specify how long NetBIOS waits between query or claim broadcasts. 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"netware netbiosMOREINFO="NONE"  broadcast delay numberReplace number with a number of milliseconds greater than 100.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultsCOLNAME=2 ROTATE="0" MOREROWS="0"With internet on: 2,000  With internet off: 1,000COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To wait longer between broadcasts:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  broadcast delay 3000RENDERAS="SECT3"ID="FM56421"commandsIDXID="w12280"BOOK="_idx" COLLECTION="nw41" TIDREF="i688"IDXID="w12281"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use this setting to specify 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"netware netbiosMOREINFO="NONE"  commands numberReplace number with a number of commands from 8 to 128. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"32 commandsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To run an application that requires a large number of outstanding commands:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  commands 128PAGENUM=282 ID="BP27A"RENDERAS="SECT3"ID="FM23424"internetIDXID="w12282"BOOK="_idx" COLLECTION="nw41" TIDREF="i1870"IDXID="w12283"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use this setting to transmit name-claim packets to and from all stations on the internet, or to and from stations on the local network only. Name-claim packets attempt to establish the uniqueness of the name of the station on which NetBIOS is running. 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"netware netbiosMOREINFO="NONE"  internet [on|off]Type on or off. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"OnCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To send and receive on the local network only:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  internet offRENDERAS="SECT3"ID="FM40911"namesIDXID="w12284"BOOK="_idx" COLLECTION="nw41" TIDREF="i2599"IDXID="w12285"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"Use this setting to specify how many names the workstation can have in its name table for remote stations. When you add a name to a station, the station broadcasts that name to all other nodes on the network.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"netware netbios  names numberReplace number with a number of names from 4 to 128. You can use a name instead of a node address to refer to a remote station.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"24 namesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow 45 names:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  names 45PAGENUM=283 ID="BP28A"RENDERAS="SECT3"ID="FM50189"retry countIDXID="w12286"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"IDXID="w12287"BOOK="_idx" COLLECTION="nw41" TIDREF="i3841"Use this setting to specify how many times NetBIOS transmits a request for connection or retransmits a failed communication. 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"netware netbios  retry count numberReplace number with a number greater than 0. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20 timesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To retransmit 50 times:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  retry count 50RENDERAS="SECT3"ID="FM63912"retry delayIDXID="w12288"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"IDXID="w12289"BOOK="_idx" COLLECTION="nw41" TIDREF="i3842"Use this setting to specify how many milliseconds NetBIOS waits between transmissions while establishing a connection or re-sending a data packet. 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"netware netbios  retry delay numberReplace number with a number of milliseconds greater than 0. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"500 millisecondsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To wait 800 milliseconds between retransmission attempts:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  retry delay 800PAGENUM=284 ID="BP29A"RENDERAS="SECT3"ID="FM65254"sessionsIDXID="w12290"BOOK="_idx" COLLECTION="nw41" TIDREF="i2770"IDXID="w12291"BOOK="_idx" COLLECTION="nw41" TIDREF="i4087"Use this setting to specify 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"netware netbios  sessions numberReplace number with a number of sessions from 4 to 64. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16 sessionsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow 100 NetBIOS sessions:MOREINFO="NONE"netware netbiosMOREINFO="NONE"  sessions 50RENDERAS="SECT1"ID="FM57102"NetWare RequesterIDXID="w12292"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"Use this option to control network requests from your workstation to a NetWare server.RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"netware requester
MOREINFO="NONE"cache buffers number
MOREINFO="NONE"default login drive drive letter
MOREINFO="NONE"display hard errors off
MOREINFO="NONE"large internet packets off
MOREINFO="NONE"name context context
MOREINFO="NONE"packet burst off
MOREINFO="NONE"preferred server servername
MOREINFO="NONE"preferred tree treename
MOREINFO="NONE"request retries number
MOREINFO="NONE"sessions number
MOREINFO="NONE"signature level numberRENDERAS="SECT2"PAGENUM=285 ID="BP30A"SettingsRENDERAS="SECT3"cacheIDXID="w12293"BOOK="_idx" COLLECTION="nw41" TIDREF="i574"
 buffersIDXID="w12294"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"Use this setting to specify how many buffers NetWare Client for OS/2 can use to cache data from open files. Cache buffers minimize read and write traffic on the network. The more buffers, the faster NetWare Client for OS/2 performs; however, more buffers use up more memory.NetWare Client for OS/2 automatically uses the maximum buffer size permitted by each server to which NetWare Client for OS/2 is connected. However, NetWare Client for OS/2 cannot use more than 64 KB of total memory for cache buffers, so if the buffer size is large, you may not be allowed as many buffers as you specify.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 requester  cache buffers numberReplace number with a number of buffers from 0 to 30. To turn off caching, specify 0.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8 buffersCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow 15 cache buffers:MOREINFO="NONE"netware requesterMOREINFO="NONE"  cache buffers 15PAGENUM=286 ID="BP31A"RENDERAS="SECT3"IDXID="w12295"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"IDXID="w12296"BOOK="_idx" COLLECTION="nw41" TIDREF="i963"
default login driveUse this option to change the default login drive from drive L: to another network drive.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 requester  default login drive drive letterReplace drive letter with the letter of another network drive. If you change the default login drive setting, you must also edit the LIBPATH, DPATH, and PATH statements in your CONFIG.SYS file from L:\OS2 to drive letter:\OS2.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"drive L:COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To change your default login drive from drive L: to drive F:MOREINFO="NONE"netware requesterMOREINFO="NONE"  default login drive fIn your CONFIG.SYS in the LIBPATH, DPATH, and PATH lines, you must change all references of L:\OS2 toMOREINFO="NONE" F:\OS2RENDERAS="SECT3"IDXID="w12297"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"
display hard errorsIDXID="w12298"BOOK="_idx" COLLECTION="nw41" TIDREF="i1144"Use this option to keep programs running without interaction when a IDXID="w12299"BOOK="_idx" COLLECTION="nw41" TIDREF="i1637"
hard error is displayed. With this option set, hard errors are automatically returned to the program that caused them rather than displayed to you for further interaction. This option is useful for sites with unattended workstations. Be careful about using it in other environments because you might turn off important messages.PAGENUM=287 ID="BP32A"Hard errors display on a screen and prompt you to choose among several actions. These error IDXID="w12300"BOOK="_idx" COLLECTION="nw41" TIDREF="i2423"
messages cause background processes to suspend until you respond to the message.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"netware requester  display hard errors drive letterType display hard errors off to keep error messages from displaying. To display error messages, leave this line out of your NET.CFG file.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Error messages are displayed. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To prevent hard error messages from displaying:MOREINFO="NONE"netware requesterMOREINFO="NONE"  display hard errors offRENDERAS="SECT3"IDXID="w12301"BOOK="_idx" COLLECTION="nw41" TIDREF="i2068"IDXID="w12302"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"
large internet packetsUse this setting to disable large internet packets transmission. IDREF="FM99776"Chapter 12, "Improving Speed and Security," on page IDREF="FM99776"155 explains more about large internet packets. 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"netware requester  large internet packets offType large internet packets off to turn off large packet transmissions.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Large internet packets are transmitted.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable large packet transmission:MOREINFO="NONE"netware requesterMOREINFO="NONE"  large internet packets offPAGENUM=288 ID="BP33A"RENDERAS="SECT3"ID="FM10812"IDXID="w12303"BOOK="_idx" COLLECTION="nw41" TIDREF="i2579"IDXID="w12304"BOOK="_idx" COLLECTION="nw41" TIDREF="i2578"
name contextIDXID="w12305"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"Use this setting to specify the workstation's name context in the directory services tree. Concepts explains more about name contexts. 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"netware requesterMOREINFO="NONE"  name context "context"Replace context with your name context in the directory tree.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"At the root of the tree.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a name context:MOREINFO="NONE"netware requesterMOREINFO="NONE"  name context "john.sales.novell us" RENDERAS="SECT3"ID="FM89210"packet burstIDXID="w12306"BOOK="_idx" COLLECTION="nw41" TIDREF="i3170"Use this setting to disable the packet burst feature. IDREF="FM81781""Improving Speed by Using Packet Burst" on page 155 explains more about Packet Burst. 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"netware requesterMOREINFO="NONE"  packet burst offCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Packet burst is enabled. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To disable packet burst:MOREINFO="NONE"netware requesterMOREINFO="NONE"  packet burst offRENDERAS="SECT3"ID="FM61797"preferred serverIDXID="w12307"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"IDXID="w12308"BOOK="_idx" COLLECTION="nw41" TIDREF="i3372"Use this setting to specify which server you want your workstation to attach to when it first accesses the network. PAGENUM=289 ID="BP34A"If the server you specify is unavailable, your workstation will attach to the first available server. 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"netware requesterMOREINFO="NONE"  preferred server servernameReplace servername with the name of a server. The server you specify should probably have the NetWare utilities for OS/2 installed. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To attach to server FINANCE:MOREINFO="NONE"netware requesterMOREINFO="NONE"  preferred server financeRENDERAS="SECT3"ID="FM68034"preferred treeIDXID="w12309"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"IDXID="w12310"BOOK="_idx" COLLECTION="nw41" TIDREF="i3375"Use this setting to specify a tree name to connect. This setting is only for sites with more than one directory tree.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"netware requesterMOREINFO="NONE"  preferred tree treenameReplace treename with the name of your tree. Tree names can have up to 32 characters.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"None.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To connect to a tree named Novell:MOREINFO="NONE"netware requesterMOREINFO="NONE"  preferred tree novellPAGENUM=290 ID="BP35A"RENDERAS="SECT3"request retriesIDXID="w12311"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"IDXID="w12312"BOOK="_idx" COLLECTION="nw41" TIDREF="i3798"Use this setting to specify how many times NetWare Client for OS/2 tries to re-send a request following a communication error. 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"netware requesterMOREINFO="NONE"  request retries numberReplace number with a number of retries greater than 5. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"20.ID="FM49382"Decrease the default if you are connected to the network over a modem and you do not want to waste phone time while NetWare Client for OS/2 keeps trying to re-send packets. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To decrease the number of times NetWare Client for OS/ 2 tries to resend a packet:MOREINFO="NONE"netware requesterMOREINFO="NONE"  request retries 10RENDERAS="SECT3"ID="FM17923"sessionsIDXID="w12313"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"IDXID="w12314"BOOK="_idx" COLLECTION="nw41" TIDREF="i4087"Use this setting to specify the number of connections NetWare Client for OS/2 can have to all servers. 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 requesterMOREINFO="NONE"  sessions numberReplace number with a number of connections from 8 to 32. You must have at least three IDXID="w12315"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"
IPX sockets for each session you allow. (See the IDREF="FM26008""sockets" setting on page 295"sockets" setting on page 295.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"8 sessionsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow more server connections:MOREINFO="NONE"netware requesterMOREINFO="NONE"  sessions 20You must also increase the sockets setting for the Protocol Stack IPX option in this case.PAGENUM=291 ID="BP36A"RENDERAS="SECT3"IDXID="w12316"BOOK="_idx" COLLECTION="nw41" TIDREF="i4153"
signature levelIDXID="w12317"BOOK="_idx" COLLECTION="nw41" TIDREF="i2786"Use this setting to assign a signature level. Signature levels help determine security on your network. IDREF="FM94412""Improving Security by Using NCP Packet Signature" on page 156 explains more about signature levels.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"NetWare RequesterMOREINFO="NONE"  signature level numberReplace number with 0, 1, 2, or 3.LABEL="A-5" PGWIDE=0 TOCENTRY="1" List of NCP Packet Signature LevelsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NumberCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Workstation does not sign packetsCOLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"Workstation signs packets only if the server requests it (server option is 2 or higher)COLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"Workstation signs packets if the server is capable of signing (server option is 1 or higher)COLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"Workstation signs packets and requires the server to sign packets (or logging in will fail)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"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1 (Workstation signs packets only if the server requests signing.)COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To prevent the workstation from signing packets:MOREINFO="NONE"netware requesterMOREINFO="NONE"  signature level 0PAGENUM=292 ID="BP37A"RENDERAS="SECT1"ID="FM53606"Protocol ODINSUPIDXID="w12318"BOOK="_idx" COLLECTION="nw41" TIDREF="i3595"Use this option to allow the NDIS protocol stack (used with Extended Services and LAN Services) to communicate using ODI token ring or Ethernet drivers.ODINSUP is designed to work only with IBM-specific protocols, such as IBM LAN Services and IBM Extended Services.See IDREF="FM99600"Chapter 16, "Using ODINSUP," on page IDREF="FM99600"207 before using this option. RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
MOREINFO="NONE"bind driver[number]RENDERAS="SECT2"SettingsRENDERAS="SECT3"IDXID="w12319"BOOK="_idx" COLLECTION="nw41" TIDREF="i3595"IDXID="w12320"BOOK="_idx" COLLECTION="nw41" TIDREF="i436"
bindUse this setting to bind the ODINSUP protocol to an ODI driver. When ODINSUP is bound to a driver, the network board for that driver is the 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"protocol odinsupMOREINFO="NONE"  bind driver [number]Replace driver with a token ring or Ethernet ODI driver name. See IDREF="FM37012"Table A-1, "List of Network Boards and Drivers," on page 258 for a list of common driver names.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Use number to bind ODINSUP to a particular occurrence of a board when you have two boards with the same name. Replace number with a number from 1 to 4.For example, if you have two NE2000 network boards in your workstation, bind ODINSUP to each board by typing a 2 for the second board.ODINSUP can be bound to a maximum of four ODI drivers.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"ODINSUP binds to the first Ethernet or token ring board it locates.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExamplesCOLNAME=2 ROTATE="0" MOREROWS="0"To bind ODINSUP to a single NE2000 board in your workstation:MOREINFO="NONE"protocol ODINSUPMOREINFO="NONE"  bind ne2000To bind ODINSUP to both the first and the second NE2000 boards in your workstation:MOREINFO="NONE"Protocol ODINSUPMOREINFO="NONE"  bind ne2000MOREINFO="NONE"  bind ne2000 2PAGENUM=293 ID="BP38A"RENDERAS="SECT1"ID="FM38316"Protocol Stack IPXIDXID="w12321"BOOK="_idx" COLLECTION="nw41" TIDREF="i1924"IDXID="w12322"BOOK="_idx" COLLECTION="nw41" TIDREF="i3604"
Use this option to adjust IPX communication between applications and the LAN drivers in your workstation.RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"protocol stack ipx
MOREINFO="NONE"bind name
MOREINFO="NONE"router mem size
MOREINFO="NONE"sockets numberRENDERAS="SECT2"PAGENUM=294 ID="BP39A"SettingsRENDERAS="SECT3"IDXID="w12323"BOOK="_idx" COLLECTION="nw41" TIDREF="i436"
bindIDXID="w12324"BOOK="_idx" COLLECTION="nw41" TIDREF="i3604"Use this setting to specify the primary network board in your workstation. By default, the primary board is the board whose driver loads first in the CONFIG.SYS file. If you specify a different board with this setting, that default is changed. See IDREF="FM59288"Chapter 5, "Using Network Boards and LAN Drivers," on page IDREF="FM59288"51COLS=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 stack ipxMOREINFO="NONE"  bind nameReplace name with the driver name for your network board. IDREF="FM37012"Table A-1, "List of Network Boards and Drivers," on page 258 lists common network boards.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"The first driver listed in your CONFIG.SYS file.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify a 3Com Etherlink 3C503 board as primary:MOREINFO="NONE"protocol stack ipxMOREINFO="NONE"  bind 3C503RENDERAS="SECT3"router memIDXID="w12325"BOOK="_idx" COLLECTION="nw41" TIDREF="i3604"IDXID="w12326"BOOK="_idx" COLLECTION="nw41" TIDREF="i3891"Use this setting to specify how many bytes in the router memory pool are allocated for routing requests to the network. 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"protocol stack ipxMOREINFO="NONE"  router mem sizeReplace size with a number of bytes. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"450 bytesSince a size of 450 bytes accommodates up to 15 network boards per workstation, you should not need to increase this default. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the default:MOREINFO="NONE"protocol stack ipxMOREINFO="NONE"  router mem 500PAGENUM=295 ID="BP40A"RENDERAS="SECT3"ID="FM26008"socketsIDXID="w12327"BOOK="_idx" COLLECTION="nw41" TIDREF="i3604"IDXID="w12328"BOOK="_idx" COLLECTION="nw41" TIDREF="i4198"Use this setting to specify how many sockets IPX can open at 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"protocol stack ipxMOREINFO="NONE"  sockets numberReplace number with a number of sockets between 9 and 128. If you are running IPX with NetWare Client for OS/ 2, do not set this value below 32. You need three sockets per server connection. The default of 64 works for the default number of server connections (see the IDREF="FM17923""sessions" setting on page 290"sessions" setting on page 290). Allow more sockets if your workstation connects to many different servers or runs protocols (such as IDXID="w12329"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"
Named Pipes) that require sockets. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"64 socketsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To set the socket limit for a workstation connected to several servers that is running Named Pipes and applications that require sockets:MOREINFO="NONE"protocol stack ipxMOREINFO="NONE"  sockets 128PAGENUM=296 ID="BP41A"RENDERAS="SECT1"ID="FM73864"Protocol Stack SPXIDXID="w12330"BOOK="_idx" COLLECTION="nw41" TIDREF="i4234"IDXID="w12331"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"
Use this option to adjust the number and characteristics of SPX connections between your workstation and other computers. RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"ID="FM94325"protocol stack spx
MOREINFO="NONE"abort timeout number
MOREINFO="NONE"listen timeout number
MOREINFO="NONE"retry count number
MOREINFO="NONE"send timeout number
MOREINFO="NONE"sessions number
MOREINFO="NONE"verify timeout numberRENDERAS="SECT2"SettingsRENDERAS="SECT3"abortIDXID="w12332"BOOK="_idx" COLLECTION="nw41" TIDREF="i45"
 timeoutIDXID="w12333"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"RENDERAS="SECT3"listenIDXID="w12334"BOOK="_idx" COLLECTION="nw41" TIDREF="i2131"
 timeoutIDXID="w12335"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"RENDERAS="SECT3"verifyIDXID="w12336"BOOK="_idx" COLLECTION="nw41" TIDREF="i4760"
 timeoutIDXID="w12337"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"Use these settings to monitor and control SPX connections. When SPX sessions at a sending computer do not receive transmissions from the receiving computer for the length of the "verify timeout" interval, SPX sends a keep-connection-alive packet to the receiving computer.   SPX then waits the length of the "listen timeout" interval to receive a response. If no response is received, SPX sends another packet requesting immediate acknowledgment. SPX then waits the length of the "abort timeout" interval to receive a response.PAGENUM=297 ID="BP42A"If no response is received, SPX aborts the session. 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"protocol stack spxMOREINFO="NONE"  abort timeout number  MOREINFO="NONE"   listen timeout number  MOREINFO="NONE"   verify timeout numberReplace number with a number of milliseconds greater than 10. The ratio between these settings must remain the same. For example, if you double the Listen timeout value, you must also double the Abort timeout and Verify timeout values.If the machine you are setting up will be a Named Pipes server, double the default timeout values.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"Abort timeout: 30,000 millisecondsListen timeout: 6,000 millisecondsVerify timeout: 3,000 millisecondsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To make SPX wait longer before sending a keep- connection-alive packet, sending the packet requesting immediate response, or aborting the session:MOREINFO="NONE"protocol stack spxMOREINFO="NONE"  abort timeout 40000MOREINFO="NONE"  listen timeout 8000MOREINFO="NONE"  verify timeout 4000RENDERAS="SECT3"retry countIDXID="w12338"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"IDXID="w12339"BOOK="_idx" COLLECTION="nw41" TIDREF="i3841"Use this setting to specify the number of times your workstation will re-send packets that weren't acknowledged by the receiving computer the first time they were sent.PAGENUM=298 ID="BP43A"Some applications may set the "retry count" value. In these cases, the application-set value is used and the NET.CFG value is ignored. 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"protocol stack spxMOREINFO="NONE"  retry count numberReplace number with a number of retries from 1 to 255. If your network traffic is heavy or if you are transmitting across routers, you may want to increase the default. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"12 retriesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the number of times packets are resent:MOREINFO="NONE"protocol stack spxMOREINFO="NONE"  retry count 30RENDERAS="SECT3"send timeoutIDXID="w12340"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"IDXID="w12341"BOOK="_idx" COLLECTION="nw41" TIDREF="i4022"Use this setting to specify how long SPX waits between attempts to send packets across the network.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"protocol stack spxMOREINFO="NONE"  send timeout numberReplace number with a number of milliseconds greater than 500. This default works well in almost all cases. Increase the default if you are using network management products with a very large network and you encounter many SPX connection errors. You may also want to increase the default for a Named Pipes client that is operating faster than the Named Pipes server to which it is connected.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"A continually calculated value based on the time it takes SPX to get a response from the server.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the wait between sends:MOREINFO="NONE"protocol stack spxMOREINFO="NONE"  send timeout 5600PAGENUM=299 ID="BP44A"RENDERAS="SECT3"ID="FM17121"sessionsIDXID="w12342"BOOK="_idx" COLLECTION="nw41" TIDREF="i3605"IDXID="w12343"BOOK="_idx" COLLECTION="nw41" TIDREF="i4087"Use this setting to specify how many SPX connections can be open simultaneously. 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"protocol stack spxMOREINFO="NONE"  sessions numberReplace number with a number of SPX connections greater than 8. Numbers higher than 1,000 may not work in all circumstances. If you run Named Pipes applications or other applications that use SPX, you may need to increase the default number of sessions.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16 sessionsCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To increase the number of SPX sessions:MOREINFO="NONE"protocol stack spxMOREINFO="NONE"  sessions 64RENDERAS="SECT1"ID="FM53519"ID="FM11885"ID="FM94488"IDXID="w12344"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"
Token Ring IDXID="w12345"BOOK="_idx" COLLECTION="nw41" TIDREF="i4218"
Source-Route DriverUse this option to configure NetWare Client for OS/2 for source-routing between token ring networks that are connected with source routers. PAGENUM=300 ID="BP45A"See IDREF="FM57010"Chapter 13, "Using Token Ring Networks," for more information.Do not use this option if your token ring networks do not use source-routing. RENDERAS="SECT2"SyntaxFORMAT="LINESPECIFIC"MOREINFO="NONE"protocol route
MOREINFO="NONE"source route def gbr mbr nodes 
n board nRENDERAS="SECT2"SettingsRENDERAS="SECT3"IDXID="w12346"BOOK="_idx" COLLECTION="nw41" TIDREF="i485"
boardIDXID="w12347"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"Use this setting to specify the logical board (frame) of a particular type that is performing source routing. 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"protocol routeMOREINFO="NONE"  source route board nReplace n with a logical board (frame) number from 1 to 16.For example, if a workstation has more than one frame type listed in the Link Driver option, by default only the first listed frame is source routed. To enable source routing on the second or other frames, you must specify the second frame as logical board 2. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"1COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To specify that logical board 2, the token ring_SNAP frame, will also be source routed:MOREINFO="NONE"link driver tokenMOREINFO="NONE"  frame token-ringMOREINFO="NONE"  frame token-ring_snap MOREINFO="NONE"protocol routeMOREINFO="NONE"  source route board 1MOREINFO="NONE"  source route board 2PAGENUM=301 ID="BP46A"RENDERAS="SECT3"DEFIDXID="w12348"BOOK="_idx" COLLECTION="nw41" TIDREF="i959"IDXID="w12349"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"Use this setting (default frame) to prevent frames that have unknown destination addresses from being sent across Single Route IBM bridges.MARK=BULLETIf this setting is specified, these frames are forwarded as All Routes Broadcast frames.If this setting is not specified, all frames that have addresses not in the workstation's Source Routing table are forwarded as Single Route Broadcast frames.If ROUTE.SYS has already been configured with the DEF setting, reloading ROUTE.SYS with this setting broadcasts all subsequent Single Route Broadcast frames as All Routes Broadcast frames. 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"protocol routeMOREINFO="NONE"  source route defType DEF to broadcast on all routes. Omit DEF to broadcast on a single route only. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"DEF is omitted (single-route broadcast only)Change this default when you are unsure of the stability of one or more routes in the network. Be aware that using DEF will substantially increase network traffic, especially on large, redundant ring networks. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To broadcast on all routes:MOREINFO="NONE"protocol routeMOREINFO="NONE"  source route defPAGENUM=302 ID="BP47A"RENDERAS="SECT3"GBRIDXID="w12350"BOOK="_idx" COLLECTION="nw41" TIDREF="i1594"
IDXID="w12351"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"Use this setting (general broadcast) to specify that all General BRoadcast frames are to be sent as All Routes Broadcast framesMOREINFO="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"protocol routeMOREINFO="NONE"  source route gbrMOREINFO="NONE" Type GBR to broadcast to all destinations, on all rings, by all routes. Omit GBR to broadcast to all destinations, on all rings, by a single route. Change the default when you want to ensure successful transmission across all possible routes. If ROUTE has already been configured with this setting, reconfiguring ROUTE with this setting broadcasts all subsequent General Broadcast frames as All Routes Broadcast frames.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"GBR is omitted (single route broadcast only)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To broadcast to all destinations, on all rings, by all routes:MOREINFO="NONE"protocol routeMOREINFO="NONE"  source route gbrPAGENUM=303 ID="BP48A"RENDERAS="SECT3"IDXID="w12352"BOOK="_idx" COLLECTION="nw41" TIDREF="i2359"
MBRIDXID="w12353"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"Use this setting (multicast) to specify that all Multicast Broadcast frames are to be sent as All Routes Broadcast frames.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"protocol routeMOREINFO="NONE"  source route mbrType MBR to transmit multicast frames simultaneously to a group of destinations by all possible routes. Omit MBR to transmit multicast frames by a single route. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"MBR is omitted (transmit by single route only)If ROUTE has already been configured with the MBR setting, reconfiguring ROUTE with this parameter broadcasts all subsequent Multicast Broadcast frames as All Routes Broadcast frames. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To broadcast multicast frames simultaneously:MOREINFO="NONE"protocol routeMOREINFO="NONE"  source route mbrRENDERAS="SECT3"nodesIDXID="w12354"BOOK="_idx" COLLECTION="nw41" TIDREF="i2957"IDXID="w12355"BOOK="_idx" COLLECTION="nw41" TIDREF="i4515"Use this setting to specify the number of table entries in the source-routing table. 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"protocol routeMOREINFO="NONE"  source route nodes nReplace n with a number of table entries from 8 to 255. If you type a number less than 8, 8 will be used. COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"DefaultCOLNAME=2 ROTATE="0" MOREROWS="0"16 entriesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"ExampleCOLNAME=2 ROTATE="0" MOREROWS="0"To allow twenty-four entries in the source-routing table:MOREINFO="NONE"protocol routeMOREINFO="NONE"  source route nodes 24PAGENUM=304 ID="BP49A"LABEL="B"PAGENUM=305 ID="BP300"System MessagesThis chapter includes system messages and explanations for all NetWare ClientTM for OS/2* drivers and daemons. Messages for the NetWare ToolsTM or the Network Printer (NPRINTER.EXE) programs are not included. For information about messages for those modules, see 
BOOK="sysmsenu" COLLECTION="nw41"System Messages manual.REQ0106: An error occurred during attempt to get shared memory. Explanation: DDAEMON.EXE attempted to access the daemon's shared memory, but failed. At this point, the program has verified that the shared memory exists, but is unable to access it. This may be an internal program error. Action: Try rebooting your system. If the problem persists, call your Novell Authorized Reseller. REQ0107: An error occurred during attempt to allocate a shared segment. Explanation: DDAEMON.EXE tried to create shared memory, but none is available. This error usually occurs when the device drivers and applications currently running on your system require more memory than your system has available. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=306 ID="BP301"REQ0108: The daemon cannot access the Link Support Layer. Error: <code>. Explanation: DDAEMON.EXE cannot find the Link Support device driver LSL.SYS. Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. Try again. If this error persists, call your Novell Authorized Reseller.REQ0109: The DDAEMON is already loaded. Explanation: DDAEMON.EXE tried to create shared memory for the first time, but the memory already exists. Another daemon is already running. The attempt to create shared memory is terminated. Action: Make sure that you are not trying to run multiple copies of the daemon. Typically the daemon is run from the CONFIG.SYS file at system startup and does not need to be executed again.REQ0204: The system does not have enough memory for socket tables. Explanation: OS/2 lacks sufficient system memory for IPX to allocate memory for its socket tables. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0205: The LAN support module could not be installed. Explanation: Either the LSL.SYS driver failed to load, or the "DEVICE=" statement is missing from the CONFIG.SYS file.Action: Either correct the problem that kept the LSL.SYS driver from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file. PAGENUM=307 ID="BP302"REQ0206: The IPX MLID could not be installed. Explanation: Either the Multiple Link Interface Driver (MLID) specified in the CONFIG.SYS failed to load, or the "DEVICE=" statement for an MLID is missing from the CONFIG.SYS file. Action: Either correct the problem that kept the MLID from loading (indicated in an error message preceding this one), or add the "DEVICE=" statement to the CONFIG.SYS file. REQ0207: The configured LAN-A driver does not support IPX. Explanation: The Multiple Link Interface Driver (MLID) to which IPX.SYS attempted to bind does not support IPX-based data transmissions. Action: Bind IPX to an MLID that supports IPX-based data transmissions.REQ0208: The IPX protocol handler cannot be registered. Explanation: IPX cannot register with the LSL.SYS driver because the LSL is servicing its maximum number of protocol stacks. Action: Remove the "DEVICE=" statements for any unnecessary protocol stacks from the CONFIG.SYS file. REQ0209: The IPX entry point cannot be initialized. Explanation: The IPX and link support layer (LSL) versions may not be compatible versions.Action: Make sure that the IPX.SYS driver and LSL.SYS driver are compatible. If they are not, obtain compatible drivers from your Novell Authorized Reseller. If this is not the problem, contact your Novell Authorized Reseller for customer assistance.REQ0210: An internal error occurred. The IPX router socket cannot be opened. Explanation: IPX was unable to open the router socket due to an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0211: An internal error occurred. A router selector cannot be allocated. Explanation: IPX was unable to allocate an OS/2 router selector due to an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=308 ID="BP303"REQ0212: The system has insufficient memory to allocate a router. Explanation: OS/2 cannot access sufficient system memory for IPX routing purposes. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0213: Router memory is exhausted. Explanation: IPX did not have enough memory previously allocated for routing purposes. Action: Increase the size of the IPX router memory in the NET.CFG "ROUTER MEM" statement.REQ0214: An internal error prevented CGroup variable initialization. Explanation: An internal program error has occurred. IPX was unable to initialize internal variables. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0215: An internal error prevented DosHlp variable initialization. Explanation: OS/2 internal variables were either incomplete or invalid. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0216: IPX cannot register with OS/2 for PDD-to-VDD communications. Explanation: This is an internal program error. IPX cannot register with OS/2 for VIPX.SYS driver support. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=309 ID="BP304"REQ0217: The IPX device driver is not running. Explanation: Either IPX.SYS encountered a fatal error during system initialization, or the "DEVICE=[path]IPX.SYS" statement was missing from the CONFIG.SYS file. If the problem is a fatal error, another message should precede this one that identifies the specific error that occurred.Action: Either resolve the fatal problem (indicated in a preceding message), or add the "DEVICE=" statement to the CONFIG.SYS file; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0231: The default protocol configuration option is not used for IPX. Explanation: IPX cannot be configured as a default protocol stack. Action: Remove this option statement from the NET.CFG file.REQ0232: The prescan protocol configuration option is not used for IPX. Explanation: IPX cannot be configured as a prescan protocol stack. Action: Remove this option statement from the NET.CFG file.REQ0233: The OS/2 version number cannot be found; OS/2 v2.0 is assumed. Explanation: IPX's query of OS/2 for the version number returned a value that did not match the value it expected to receive. Action: Make sure the OS/2 version installed on the machine is v2.0 or later.REQ0304: An LSL error occurred. NET.CFG buffers are too big for ECB pool.Explanation: The configured buffer size for the Link Support component is too large. Total available buffer space is around 60 KB, but the Link Support Layer (LSL) is unable to allocate even one buffer of the requested size in its buffer space. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Reduce the Link Support component's buffer size in the NET.CFG file. It is more important to have several smaller buffers available than one large one. It is a waste of system memory to configure buffers much larger than the communications media can support.PAGENUM=310 ID="BP305"REQ0305: The Link Support module (LSL) could not install the AES timer.Explanation: The Link Support Layer (LSL) could not register its timer handler with the operating system because the maximum number of handlers have already been installed. This timer handler is a critical component of NetWare Client for OS/2, and none of the Novell-supplied communication handlers can be expected to work properly without it. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Previously installed device drivers (those entered before LSL.SYS in the CONFIG.SYS file) have used all available timer resources. Identify those device drivers and either remove or reconfigure them. Since the Requestor's communications handlers all use a common timer service in the LSL, only one available timer handler is required for proper operation. If you are unable to resolve this problem, contact your Novell Authorized Reseller.REQ0306: The Link Support module could not initialize its call gate.Explanation: The Link Support module could not register its entry point with the operating system. This entry point is vital to most of NetWare Client for OS/2's communications components, and its absence will cause them to fail. The most likely cause of this error is a previously loaded device driver that is using too many kernel resources. Action: Try removing application device drivers installed before LSL.SYS in the CONFIG.SYS file. It is highly unlikely that a device driver from the OS/2 base system has caused this error. If the problem persists, contact your Novell Authorized Reseller.REQ0404: NetBIOS error occurred. Link Support module cannot be installed. Explanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if you are using the wrong version of the driver. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.PAGENUM=311 ID="BP306"Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. If the Link Support device driver is initializing properly, the problem is with incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller.REQ0405: NetBIOS error occurred. The IPX module is not installed. Explanation: NetBIOS could not open or communicate with the Link Support LINKSUP_ device driver. This can happen if the Link Support Layer (LSL) driver has not been properly installed or if you are using the wrong version of the driver. See "BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in Concepts for more information about LSL.Action: Make sure that the device driver LSL.SYS has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the LSL for any errors or warnings, and correct the problems indicated. If the Link Support device driver is initializing properly, the problem is with incompatible versions of the software. NetBIOS and Link Support are usually installed together from a single installation diskette. Try reinstalling them. If the problem persists, contact your Novell Authorized Reseller.REQ0406: The NetBIOS call gate cannot be initialized. Explanation: This is an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0407: NetBIOS error occurred. The program cannot initialize local NCBs. Explanation: Insufficient memory is available for the NCBs requested. Usually this error is caused by incorrect configuration information in the NET.CFG file. However, the underlying problem could also be a lack of global system resources in the OS/2 Global Descriptor Table. PAGENUM=312 ID="BP307"Action: Reduce the number of commands in the NetBIOS section of the CONFIG.SYS file. (The default number of commands is 12; the maximum allowed is 25.) You also might be able to reduce the number of node names (possible range is 0-126). Additional possibilities include adding RAM, reducing your configuration options (for example, reducing the size of DIRCACHE) or removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0408: NetBIOS emulator parameters are too large for the memory pool. Explanation: Insufficient memory is available for all of the control tables needed by the NetBIOS emulator. Action: The amount of table space available to the NetBIOS emulator cannot be increased. The only way to solve this problem is to reduce the number of NetBIOS resources you are requesting. You can do this by modifying the NETBIOS parameters in the NET.CFG file. If the problem persists, contact your Novell Authorized Reseller.REQ0409: Incompatible versions of OS/2 and NetBIOS are running. Explanation: You are attempting to run NetBIOS v2.10 on some version of OS/2 earlier than OS/2 v2.1. Action: Either install OS/2 v2.1 to run with NetBIOS v2.10, or install a different version of NetWare NetBIOS to match your OS/2 version.REQ0504: The SPX module is not installed. Explanation: The NMPIPE.SYS driver could not open or communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. PAGENUM=313 ID="BP308"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0505: The IPX module is not installed. Explanation: NMPIPE.SYS could not open or communicate with the IPX.SYS driver. Action: Make sure that the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0519: An incorrect OS/2 version is being used. Explanation: Either the DosGetVersion call failed (an internal program error), or the OS/2 version currently running is not v2.0 or later. Action: Make sure the client OS and NMPIPE.SYS driver are compatible versions. If the problem persists, contact your Novell Authorized Reseller. REQ0520: The driver cannot register the PDD for VDD-to-PDD communications. Explanation: NMPIPE.SYS could not register IPX as a PDD so that PDD to VDD communication may take place. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the OS/2 version is v2.0 or later; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0613: Invalid characters were specified in COMPUTERNAME. Explanation: The Named Pipes server name specified after NPDAEMON.EXE is invalid. Action: Make sure the server name is not more than 15 characters and is composed of letters, numbers, and these special characters: !#$%&()-.@^_\Q{}~REQ0614: An error occurred during attempt to initialize NPCALLS.DLL. Explanation: The NPDaemon could not initialize NPCALLS.DLL. PAGENUM=314 ID="BP309"Action: Make sure the NPCALLS.DLL file in the NetWare Client for OS/2 directory is included in the LIBPATH statement of the CONFIG.SYS file. If you are running Named Pipes, make sure the NMPIPE.SYS driver and NPSERVER.SYS are correctly configured in the CONFIG.SYS file.REQ0615: The Named Pipes daemon could not be registered. Error: <code>. Explanation: The NPDaemon could not open or communicate with the NMPIPE.SYS driver. Action: Make sure the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems. Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0616: An error occurred during attempt to allocate shared memory. Explanation: The NPDaemon could not allocate shared memory. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0617: An error occurred during attempt to allocate the ECB pool. Explanation: The NPDaemon could not allocate memory for the ECB pool. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=315 ID="BP310"REQ0618: An error occurred during attempt to create a system semaphore. Explanation: A DosCreateSem call failed. An internal program error may have occurred. Action: Try again. If the error persists, contact your Novell Authorized Reseller.REQ0619: An error occurred during attempt to create a thread. Explanation: A beginthread call failed. An internal program error may have occurred.Action: Try again. If the error persists, contact your Novell Authorized Reseller.REQ0620: A dynamic socket could not be opened. Error: <code>. Explanation: The NPDaemon failed to open a dynamic socket. Action: Increase the socket count specified in the NET.CFG file; then reboot the system and try again. If the problem persists, contact your Novell Authorized Reseller. REQ0621: A well-known socket could not be opened. Error: <code>. Explanation: The NPDaemon could not open Netware's registered Named Pipe socket; the socket may already be in use. Action: Increase the SPX socket count in the NET.CFG and shut down OS/2; then reboot the system.REQ0622: The NPDaemon cannot get the internet address. Error: <code>. Explanation: An IpxGetInternetworkAddress call failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; then try again. If the problem persists, notify your Novell Authorized Reseller.REQ0623: The NPDaemon cannot get the local target. Error: <code>. Explanation: An IpxGetLocalTarget call failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. PAGENUM=316 ID="BP311"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0624: The service advertising function failed. Error: <code>. Explanation: An IpxSend call to advertise this workstation as Named Pipe Server failed. Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory; the try again. If the problem persists, contact your Novell Authorized Reseller.REQ0625: The broadcast socket cannot be opened. Error: <code>. Explanation: The broadcast socket cannot be opened. This is a registered socket by which SAPs can be received. Possibly this socket has already been opened. Action: Increase the socket count in the NET.CFG file and shut down OS/2 and then reboot the system. If the problem persists, contact your Novell Authorized Reseller. REQ0626: An error occurred during attempt to get code page information. Explanation: A call to DosGetCtryInfo failed. This may be an internal program error. Action: Make sure the OS/2 is version 2.0 or later. If so, and the problem persists, contact your Novell Authorized Reseller.REQ0628: Memory cannot be allocated for turbo buffers. Explanation: The NPDaemon could not allocate memory for turbo buffers. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. PAGENUM=317 ID="BP312"If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0629: A connection thread died abnormally. Error: <code>. Explanation: The connection controller thread died unexpectedly. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure all of your Named Pipe drivers are within the same major version (for example, v2.x); then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0630: The specified computer name is already registered on the internet. Explanation: The Named Pipes server name specified in the CONFIG.SYS file has already been used on the network. Action: Use a different server name.REQ0631: The receive buffer manager died abnormally. Error: <code>. Explanation: The receive buffer manager thread died unexpectedly. Action: Make sure that your Named Pipes drivers are within the same major version (for example, v2.x). If so, try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=318 ID="BP313"REQ0635: General Service Query for Named Pipe Servers failed. Error: %1.%0Explanation: A call to IpxSend to issue a general service query for named Pipe Servers failed.Action: Make sure the IPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL file is in the NetWare Client for OS/2 directory.Try again. If the problem persists, contact your Novell authorized reseller.REQ0636: An error occurred while obtaining the IPX card table.%0Explanation: A call to the npserver.sys driver to obtain the IPX card table failed.Action: Make sure the IPX.SYS driver and the NPSERVER.SYS driver have been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the drivers for any errors or warnings, and correct the problems indicated. Also make sure the IPXCALLS.DLL and NPCALLS.DLL files are in the NetWare Client for OS/2 directory. Try again. If the problem persists, contact your Novell authorized reseller.REQ0704: The SPX module is not installed. Explanation: The Named Pipes daemon could not open or communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0705: The IPX module is not installed. Explanation: The Named Pipes daemon could not open or communicate with the IPX.SYS driver. Action: Make sure that the IPX.SYS driver has been properly entered in the CONFIG.SYS file. PAGENUM=319 ID="BP314"If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0719: An incorrect OS/2 version is being used. Explanation: The DosGetVersion call failed (which would indicate an internal program error) or the OS/2 version currently running is not v2.0 or later. Action: Make sure that the client OS and NMPIPE.SYS driver are compatible; then try again. If the problem persists, contact your Novell Authorized Reseller. REQ0806: The program cannot get code page information. Error: <code>. Explanation: The OS/2 system is not returning code page information. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0807: The Requester device driver and daemon are incompatible versions. Explanation: The most likely cause of this problem is that NWDAEMON.EXE and NWREQ.SYS driver were not installed from the same installation disk. Action: Install NetWare Client for OS/2 driver again, making sure it is from the correct installation disk.REQ0808: The worker DLL cannot be registered. Error: <code>. Explanation: The NWWORKER.DLL could not register with NetWare Client for OS/2. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0809: The broadcast handler cannot be registered. Error: <code>. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0810: The program cannot get system information. Error: <code>. Explanation: The OS/2 system is not returning system information. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=320 ID="BP315"REQ0811: The janitor thread priority cannot be set. Error: <code>. Explanation: The janitor thread is set to run at regular priority. The system had trouble setting the priority. Action: Ignore the error.REQ0812: The janitor daemon cannot be registered. Error: <code>. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0813: The program cannot get the current drive map. Error: <code>. Explanation: The OS/2 system is not returning the current drive map. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0814: The program cannot set the current drive map. Error: <code>. Explanation: The OS/2 system is not setting the current drive map. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0815: The program cannot get the connection ID. Error: <code>. Explanation: NetWare Client for OS/2 tried to locate a NetWare server when it initialized. Either no servers are currently running or a cabling problem exists. Action: Make sure the NetWare server is running and functioning properly. Also make sure the OS/2 machine has a working connection to the network; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ0816: An error occurred during attempt to initialize the cache. Explanation: The caching function is not working. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0817: The daemon could not boost the thread priority. Explanation: The thread is set to run at a greater priority. The system had trouble setting the priority. PAGENUM=321 ID="BP316"Action: Ignore the error.REQ0818: The daemon could not register the DosBox handler. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0820: Not enough memory for diagnostic daemon. Error: <code>. Explanation: The NWDaemon program tried to allocate memory from the system for the diagnostic thread to use as a stack, but the system returned an error. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0821: The diagnostic daemon cannot be started. Error: <code>. Explanation: The NWDaemon tried to start the diagnostic thread but the system encountered an error condition. The system may have too many threads already running, or this may be an internal program error. Action: Try closing other applications that are currently running. If the problem persists, contact your Novell Authorized Reseller.REQ0822: The diagnostic daemon priority cannot be changed. Error: <code>. Explanation: The diagnostic thread is set to run at regular priority. The system had trouble setting the priority. Action: Ignore the error.REQ0823: Not enough memory to start a new thread. Error: <code>. Explanation: The NWDaemon could not allocate memory from the system to create a thread for a new task. PAGENUM=322 ID="BP317"Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0824: The SPX send thread cannot be started. Error: <code>. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0825: The SPX receive thread cannot be started. Error: <code>. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0826: The SFT 3 handler cannot be registered. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0827: Packet Burst cannot be initialized. Explanation: This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ0843: Not enough memory for a network management thread (<error code>). Explanation: The NWDaemon tried to allocate memory from the system for a thread to initialize network management, but memory was not available. Network management cannot be initialized. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. PAGENUM=323 ID="BP318"If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0844: A named pipe cannot be started for network management (<error code>). Explanation: The NWDaemon could not allocate a named pipe. Network management will not be supported until the computer is rebooted. This error could result from a variety of causes. Named Pipes or SPX may not be loaded, one of your drivers may have opened too many Named Pipes already, you may not have enough memory or disk space, or it may be an internal program error. Action: Make sure that Named Pipes and SPX are loaded and that your system has enough memory. (If you suspect a memory problem, see the discussion for message 843.) After completing these actions, reboot the system and try again. If the problem persists, contact your Novell Authorized Reseller.REQ0845: Not enough memory to run network management (<error code>). Explanation: The NWDaemon program tried to allocate memory from the system to run network management, but memory is not available. Network Management will not run until memory is available and the system is rebooted. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0904: The NWREQ.SYS driver is not loaded. Explanation: NetWare Client for OS/2 cannot be initialized until the driver is loaded. PAGENUM=324 ID="BP319"Action: Load the NWREQ.SYS driver.REQ0914: The program cannot allocate selectors for the workspace table. Explanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and try again. If the problem persists, contact your Novell Authorized Reseller.REQ0915: The program cannot allocate memory for the workspace table. Explanation: All available system memory is in use. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0917: Memory is not available for the cache table. Caching is disabled. Explanation: All available system memory is in use by the system. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ0919: An incorrect OS/2 version is being used. Explanation: The major versions of NetWare Client for OS/2 and OS/2 do not match. PAGENUM=325 ID="BP320"Action: Upgrade NetWare Client for OS/2 or OS/2.REQ0937: The Requester driver version does not match the IFS version. Explanation: NWIFS.IFS and NWREQ.SYS were not installed from the same installation disk. Action: Install NetWare Client for OS/2 again. If the problem persists, contact your Novell Authorized Reseller.REQ1005: The LAN support module is not installed. Explanation: NetWare Client for OS/2 driver requires the LSL.SYS driver to be running when it loads. Either the "DEVICE=C:\NETWARE\LSL.SYS" line is missing from the CONFIG.SYS file or the LSL encountered an error while loading. Action: Check the CONFIG.SYS file for the LSL.SYS driver. If this is not the problem, contact your Novell Authorized Reseller.REQ1008: A NetWare server cannot be found. Explanation: NetWare Client for OS/2 tries to locate a NetWare server when it initializes. Either no servers are currently running or there is a cabling problem. Action: Make sure that the NetWare server is running and operating properly. Also make sure that the OS/2 machine is connected to the network.REQ1010: The program cannot allocate selectors for the connection table. Explanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file and try again. If the problem persists, contact your Novell Authorized Reseller.REQ1011: The program cannot allocate memory for the connection table. Explanation: All available system memory is in use. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. PAGENUM=326 ID="BP321"If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system.If the problem persists, contact your Novell Authorized Reseller.REQ1019: An incorrect OS/2 version is being used. Explanation: The major version of NetWare Client for OS/2 and OS/2 do not match. Action: Upgrade NetWare Client for OS/2 or OS/2.REQ1021: The config file cannot be parsed. Default parameters will be used. Explanation: NetWare Client for OS/2 driver could not read parameters in the NET.CFG file. Action: Make sure the syntax for the NetWare Client for OS/2 section of the file is correct.REQ1022: An unrecoverable error occurred. The driver was not loaded. Explanation: The driver could not load properly. This is probably an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1024: The program cannot allocate selectors for worker support. Explanation: All available memory selectors are being used by the system or by previously loaded device drivers. Action: Remove optional or unneeded device drivers from the CONFIG.SYS file. Then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1038: The program cannot allocate memory for the error message buffer. Explanation: All available system memory is in use by the system. NetWare Client for OS/2 cannot load properly. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. PAGENUM=327 ID="BP322"After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1039: The Requester could not send to NetWare server <number> as <number>. Explanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1040: The Requester timed out waiting for reply from server <number>. Explanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1041: Server <number> did not respond to a request. Explanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. This error can also occur if the server responds with an unexpected response.Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1042: Connection to NetWare server <number> as <number> is now invalid. Explanation: NetWare Client for OS/2 waits for a response from the server after each request. If the server does not respond within a certain amount of time, NetWare Client for OS/2 times out. Action: Make sure that the server is still running and functioning properly. PAGENUM=328 ID="BP323"Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1043: Routing to NetWare server <number> has been disrupted. Explanation: The network route to the server has been disrupted. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1045: Routing to NetWare server <number> has been disrupted. Explanation: The network route to the server has been disrupted. Action: Make sure that the server is still running and functioning properly. Also make sure that all routers between the workstation and the server are still running. If the problem persists, contact your Novell Authorized Reseller.REQ1106: The SPDaemon cannot get the SPX version. Error: <code>. Explanation: The SpxGetVersion call failed. This may be an internal program error. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. If the problem persists, contact your Novell Authorized Reseller.REQ1107: The SPX driver and the SPX daemon are incompatible versions. Explanation: The SPX.SYS driver and SPDAEMON.EXE versions may not match. Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE are compatible versions. If the problem persists, contact your Novell Authorized Reseller. REQ1108: The SPX driver entry cannot be obtained. Error: <code>. Explanation: The SPDaemon could not get a handle to the SPX.SYS driver. This may be an internal program error. Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE versions are compatible. If the problem persists, contact your Novell Authorized Reseller. PAGENUM=329 ID="BP324"REQ1109: The SPX daemon is already loaded. Error: <code>. Explanation: The SPDAEMON.EXE has already registered with the SPX.SYS driver, which means it is already loaded. Action: Make sure that the daemon SPDAEMON.EXE has not been entered in the CONFIG.SYS file more than once. REQ1110: The daemon cannot register with the SPX driver. Error: <code>. Explanation: The SPDaemon cannot communicate with the SPX.SYS driver. Action: Make sure that the SPX.SYS file has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions. If the problem persists, contact your Novell Authorized Reseller. REQ1111: The SPX device handle cannot be closed. Error: <code>. Explanation: The SPDeamon cannot close the device handle. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1112: The SPDaemon cannot wait on semaphore. Error: <code>. Explanation: A DosSemSetWait call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1113: System information segments cannot be obtained. Error: <code>. Explanation: The DosGetInfoSeg call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1114: Priority for the lock thread cannot be set. Error: <code>. Explanation: The DosSetPrty call failed. This may be internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.PAGENUM=330 ID="BP325"REQ1115: The SPX driver cannot be accessed. Error: <code>. Explanation: The SPDaemon was not able to access SPX.SYS through the call gate. Action: Make sure that the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Also check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1116: Priority for an AES thread cannot be set. Error: <code>. Explanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1117: Priority for a watchdog thread cannot be set. Error: <code>. Explanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1118: Priority for a session thread cannot be set. Error: <code>. Explanation: The DosSetPrty call failed. This may be an internal program error. Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1119: The SPXCALLS.DLL cannot register with the SPX driver. Explanation: The SPXCALLS.DLL cannot communicate with the SPX.SYS driver. Action: Check to see if the SPX.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1205: The driver cannot initialize the CGroup Data variables. Explanation: Normally, key data variable are stored in the driver's CGroup for easy and reliable access. However, in this instance the variables could not be initialized due to a memory-related error. PAGENUM=331 ID="BP326"Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller. REQ1206: The driver cannot configure SPX. Explanation: The driver in conjunction with the NWCONFIG.DLL failed to parse the NET.CFG file for the SPX parameters. Action: Make sure the format of the NET.CFG file is correct.REQ1207: The driver failed to get support hooks from the LSL or IPX. Explanation: SPX could not open or communicate with either the LINKSUP_ (LSL.SYS) or the IPX_ (IPX.SYS) drivers. The most likely cause of this error is that one or both of these drivers has been improperly installed. Action: Make sure that the device drivers LSL.SYS and IPX.SYS have been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1208: The OS/2 version cannot be obtained; OS/2 v2.0 is assumed. Explanation: The DosGetVersion call failed (an internal program error), or the OS\2 version currently running is not v2.0 or later. Action: Make sure that OS/2 and the SPX.SYS driver are compatible versions. If this is not the problem, contact your Novell Authorized Reseller.REQ1209: The driver cannot get OS/2 DOS variables. Explanation: The SPX.SYS driver could not obtain either the system or local information segment. This may be an internal program error. PAGENUM=332 ID="BP327"Action: Try again. If the problem persists, contact your Novell Authorized Reseller.REQ1210: The driver cannot initialize the SPX call gate. Explanation: The SPX.SYS driver could not register a call gate with the LSL.SYS driver. Action: Make sure that the LSL.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. Check for a mismatch of driver versions; then try again. If the problem persists, contact your Novell Authorized Reseller.REQ1211: The driver cannot allocate memory for SPX use. Explanation: The system does not have enough memory to run SPX. Action: Try adding RAM, reducing your configuration options in the CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing optional device drivers from the CONFIG.SYS file, and freeing up some hard disk space by deleting unnecessary programs. If you are using multiple disk partitions, consider moving the OS/2 swapper file to a larger partition. Disk compression utilities may also be available that can help resolve this problem. After completing these actions, shut down OS/2; then reboot the system. If the problem persists, contact your Novell Authorized Reseller.REQ1301: The application cannot initialize named pipes. Explanation: The application could not open or communicate with the NMPIPE.SYS driver. Most likely, the NMPIPE.SYS driver is not entered in the CONFIG.SYS file. Action: Make sure that the NMPIPE.SYS driver has been properly entered in the CONFIG.SYS file. If so, check the messages displayed by the driver for any errors or warnings, and correct the problems indicated. If the problem persists, contact your Novell Authorized Reseller.LABEL="C"PAGENUM=333 ID="BP328"ID="FM78537"Architecture DiagramsIDXID="w12356"BOOK="_idx" COLLECTION="nw41" TIDREF="i1032"IDXID="w12357"BOOK="_idx" COLLECTION="nw41" TIDREF="i274"These diagrams provide a technical overview of NetWare ClientTM for OS/2*.They can help you understand what components are used for the various functions NetWare Client for OS/2 performs (for example, which components are used to support Named Pipes). Specifically, the diagrams illustrateMARK=BULLETThe major functions of NetWare Client for OS/2 componentsThe different components of NetWare Client for OS/2The relationships between componentsYou do not need to manually load the components shown in the diagrams. Select the settings you want in the NetWare Client for OS/2 installation program, and the correct components will be loaded. To change the settings later, run the installation program again.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="31*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Topics and architecture diagramsCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78534"NetWare Requests from OS/2 Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78534"334COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM21791"NetWare Core Protocol RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM21791"335COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM69549"File System RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69549"336COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM57835"Protocol Requests from OS/2 Sessions  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57835"336COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM18520"IPX-Only RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18520"337COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55192"SPX RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55192"338COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94933"Named Pipes Server RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94933"339COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM81088"Named Pipes Client RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM81088"340COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM57835"Protocol Requests from OS/2 Sessions COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57835"336COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM56593"NetBIOS Submit Requests Using Only Novell NetBIOS DriverCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM56593"342COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM37878"NetBIOS Submit Requests Using Only Novell NetBIOS Driver with Extended Services LoadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37878"343COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM61486"NetBIOS Submit Requests Using Either Novell or IBM NetBIOS Driver with LAN Services LoadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM61486"344COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62676"NB30 NetBIOS Requests Using Either Novell or IBM NetBIOS Driver with Extended Services LoadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62676"345COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM10716"NetWare Requests from DOS/MS Windows Sessions N COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10716"345COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM15172"DOS/MS Windows NetWare Core Protocol RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15172"346COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM10180"DOS/MS Windows File System RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10180"347COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33194"Protocol Requests from DOS/MS Windows Sessions  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33194"348COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74691"DOS/MS Windows SPX- or IPX-Only RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74691"348COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM45098"DOS/MS Windows Named Pipes Client RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45098"349COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM54260"DOS/MS Windows SQL Client Get Server RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54260"350COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM67882"DOS and MS Windows NetBIOS RequestsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67882"351COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM19648"NetBIOS Submit Requests Using Only Novell NetBIOS Driver with Extended Services LoadedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37878"343COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM23686"Sharing a Network Board COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23686"352352COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86551"NetWare Client for OS/2 and IBM Software Using ODINSUP to Share a Network BoardCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86551"353COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM15783"NetWare Client for OS/2 and IBM Software Using LANSUP to Share a Network BoardCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15783"354PAGENUM=334 ID="BP329"RENDERAS="SECT1"ID="FM78534"NetWare Requests from OS/2 SessionsRENDERAS="SECT2"ID="FM35513"NetWare Core Protocol RequestsPAGENUM=335 ID="BP330"NetWare Core ProtocolTM (NCP) requests go directly to the NetWare server without going through OS/2. Some NetWare® utilities issue this kind of request. These requests are usually accompanied by file system requests, shown on page IDREF="FM49591"335.LABEL="C-1" FLOAT="0"ID="FM21791"NetWare Core Protocol RequestsFILEREF="c41q80a.tif"RENDERAS="SECT2"ID="FM49591"File System RequestsIDXID="w12358"BOOK="_idx" COLLECTION="nw41" TIDREF="i1475"File system requestsIDXID="w12359"BOOK="_idx" COLLECTION="nw41" TIDREF="i1475"
 are handled by OS/2 before being passed on to NetWare Client for OS/2. Any program which manipulates files on the network makes this kind of request. These requests are always accompanied by NetWare Core Protocol requests, shown on IDREF="FM35513"page 334.PAGENUM=336 ID="BP331"LABEL="C-2" FLOAT="0"ID="FM69549"File System RequestsFILEREF="c41q81a.tif"RENDERAS="SECT1"ID="FM57835"Protocol Requests from OS/2 SessionsRENDERAS="SECT2"IPX-Only RequestsIPX requests are issued by IPX applications, including NetWare Client for OS/2.PAGENUM=337 ID="BP332"LABEL="C-3" FLOAT="0"ID="FM18520"IPX-Only RequestsFILEREF="c41q83a.tif"RENDERAS="SECT2"SPX RequestsSPX requests are issued by SPX applications. Some NetWare print utilities and API calls use SPX.PAGENUM=338 ID="BP333"LABEL="C-4" FLOAT="0"ID="FM55192"SPX RequestsFILEREF="c41q82a.tif"RENDERAS="SECT2"ID="FM24944"Named Pipes Server RequestsIDXID="w12360"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"Named Pipes server requests are made by Named Pipes distributed application servers.PAGENUM=339 ID="BP334"LABEL="C-5" FLOAT="0"ID="FM94933"Named Pipes Server RequestsFILEREF="c41q84a.tif"RENDERAS="SECT2"ID="FM17647"Named Pipes Client RequestsIDXID="w12361"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"Named Pipes client requests are issued by Named Pipes distributed application clients.PAGENUM=340 ID="BP335"LABEL="C-6" FLOAT="0"ID="FM81088"Named Pipes Client RequestsFILEREF="c41q85a.tif"RENDERAS="SECT2"ID="FM29449"NetBIOS RequestsRENDERAS="SECT3"What is NetBIOSIDXID="w12362"BOOK="_idx" COLLECTION="nw41" TIDREF="i2643"NetBIOS is a "device-independent" protocol that lets applications use network boards without knowing the specifics of how the drivers for those boards work. NetBIOS applications issue NetBIOS commands which are routed to a specific network board driver. That driver handles the transmission of NetBIOS packets over the network. RENDERAS="SECT3"What is the Novell NetBIOS EmulatorNovell provides a NetBIOS emulator that allows applications running on an IPX-based network (such as NetWare) to communicate using NetBIOS. PAGENUM=341 ID="BP336"This NetBIOS emulator encapsulates NetBIOS packets inside of IPX packets. Then an ODI driver handles transmission of the IPX packets over the network. While your NetBIOS application communicates using NetBIOS commands, the NetBIOS emulator actually transmits IPX packets. The Novell NetBIOS emulator can only communicate with other emulators that use IPX. For example, if you have one workstation running the NetBIOS emulator and another workstation running IBM's NetBIOS, the two workstations cannot communicate. However, the NetBIOS emulator can run on the same OS/2 workstation as other NetBIOS implementations, including the NetBIOS provided with IBM Extended Services or LAN Services. Or, the NetBIOS emulator can run by itself. NetBIOS requests are issued by applications which use Novell NetBIOS emulation. If Extended Services or LAN Services is installed, requests follow a different path. See pages IDREF="FM14506"343 through IDREF="FM62676"345. PAGENUM=342 ID="BP337"LABEL="C-7" FLOAT="0"ID="FM56593"NetBIOS Submit Requests Using Only Novell NetBIOS DriverFILEREF="c41q86a.tif"PAGENUM=343 ID="BP338"LABEL="C-8" FLOAT="0"ID="FM37878"ID="FM19648"ID="FM14506"NetBIOS Submit Requests Using Only Novell NetBIOS Driver with Extended Services LoadedFILEREF="c41q96a.tif"PAGENUM=344 ID="BP339"LABEL="C-9" FLOAT="0"ID="FM61486"NetBIOS Submit Requests Using Either Novell or IBM NetBIOS Driver with LAN Services LoadedFILEREF="c41q97a.tif"PAGENUM=345 ID="BP340"LABEL="C-10" FLOAT="0"ID="FM62676"NB30 NetBIOS Requests Using Either Novell or IBM NetBIOS Driver with Extended Services LoadedFILEREF="c41q98a.tif"RENDERAS="SECT1"ID="FM10716"NetWare Requests from DOS/MS Windows SessionsWhen you select support for virtual DOS sessions in the NetWare Client for OS/2 installation program, the installation program adds lines to the CONFIG.SYS file to load the VIPX and VSHELL components.The NETWARE_RESOURCES and VIPX_ENABLED properties are also created and added to the CLASS=MENUITEM MOREINFO="NONE"DOS Settings notebook of all DOS and Windows icons. These properties allow you to choose global support, private support, or no network support for each session.MARK=BULLETIf you choose global support, VIPX and VSHELL are enabled for the session. PAGENUM=346 ID="BP341"If you choose private support, VIPX is enabled, VSHELL is not enabled, and you can manually load NETX.EXE If you don't load NETX.EXE, you receive IPX- and SPX-only support. If you choose VIPX_ENABLED OFF, then no NetWare support is loaded. VIPX must be enabled for either global (using VSHELL) or private (using NETX) sessions to work.LABEL="C-11" FLOAT="0"ID="FM15172"DOS/MS Windows NetWare Core Protocol RequestsFILEREF="c41q87a.tif"PAGENUM=347 ID="BP342"LABEL="C-12" FLOAT="0"IDXID="w12363"BOOK="_idx" COLLECTION="nw41" TIDREF="i1475"ID="FM10180"DOS/MS Windows File System RequestsFILEREF="c41q88a.tif"PAGENUM=348 ID="BP343"RENDERAS="SECT1"ID="FM33194"Protocol Requests from DOS/MS Windows SessionsLABEL="C-13" FLOAT="0"ID="FM74691"DOS/MS Windows SPX- or IPX-Only RequestsFILEREF="c41q89a.tif"PAGENUM=349 ID="BP344"LABEL="C-14" FLOAT="0"IDXID="w12364"BOOK="_idx" COLLECTION="nw41" TIDREF="i2593"ID="FM45098"DOS/MS Windows Named Pipes Client RequestsFILEREF="c41q90a.tif"PAGENUM=350 ID="BP345"LABEL="C-15" FLOAT="0"IDXID="w12365"BOOK="_idx" COLLECTION="nw41" TIDREF="i4246"ID="FM54260"DOS/MS Windows SQL Client Get Server RequestsFILEREF="c41q91a.tif"PAGENUM=351 ID="BP346"LABEL="C-16" FLOAT="0"ID="FM67882"DOS and MS Windows NetBIOS RequestsFILEREF="c41q92a.tif"PAGENUM=352 ID="BP347"LABEL="C-17" FLOAT="0"DOS and MS Windows NetBIOS Requests with Extended Services LoadedFILEREF="c41q99a.tif"RENDERAS="SECT1"ID="FM23686"Sharing a Network BoardRENDERAS="SECT2"How ODINSUP WorksIDXID="w12366"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"ODINSUP translates NDIS transmissions from Extended Services or LAN Services into a form that complies with the ODI drivers. ODINSUP also translates transmissions received from the network into a form readable by Extended Services and LAN Services. PAGENUM=353 ID="BP348"ODINSUP functions like a default protocol stack, meaning that it accepts requests from the Link Support Layer (LSL) that are not specifically marked for another registered protocol (such as IPX or TCP/IP). When it receives requests, ODINSUP passes them on to the NDIS protocol stack. ODINSUP allows IBM's Protocol Manager (found in Extended Services and LAN Services) to communicate with a network board without having to be aware of the details of transmission on that board (such as frame type). Instead, the details are handled at the ODI driver level and then transmissions are passed on to the Link Support Layer, which in turn passes them on to the correct protocol stack or to ODINSUP. ODINSUP translates the request to a form understood by Protocol Manager.IDREF="FM99600"Chapter 16, "Using ODINSUP," on page 207 explains more about using ODINSUP.ODINSUP is for using ODI drivers. LANSUP is for using NDIS drivers. LABEL="C-18" FLOAT="0"IDXID="w12367"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"ID="FM86551"NetWare Client for OS/2 and IBM Software Using ODINSUP to Share a Network BoardFILEREF="c41q93a.tif"PAGENUM=354 ID="BP349"LABEL="C-19" FLOAT="0"IDXID="w12368"BOOK="_idx" COLLECTION="nw41" TIDREF="i2056"ID="FM15783"NetWare Client for OS/2 and IBM Software UsingID="FM96569"LANSUP to Share a Network BoardFILEREF="c41q94a.tif"