#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'NetWare Client for DOS and MS Windows User GuideNetWare Client for DOS and MS Windows User GuideNovell, 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=11 ID="BP1"How to Use This ManualRENDERAS="SECT1"IntroductionIDXID="w11025"BOOK="_idx" COLLECTION="nw41" TIDREF="i1704"
NetWare® ClientTM for DOS and MS Windows User Guide has three purposes: to help you set up and install your client software, to help you set up and connect your client workstations to the network, and to introduce client User Tools for managing access and connections on a NetWare network.This manual is for users and supervisors new to NetWare client networking and for network supervisors responsible for setting up and managing NetWare client workstations.This manual covers concepts and procedures for installing and using NetWare client software on NetWare 2, 3, and 4 networks. References are made to each version of NetWare. Ignore any references which do not pertain to the version of NetWare you are connecting to.Use NetWare Client for DOS and MS Windows Technical Reference for advanced setup and troubleshooting of your NetWare client workstations.RENDERAS="SECT1"Documentation IDXID="w11026"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
ConventionsThis manual uses the following Novell® conventions:RENDERAS="SECT2"Asterisk ( * )An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, TM, etc.).An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a "Trademarks" section at the back of printed manuals. A trademarks list is also available in the DynaText* online documentation.PAGENUM=12 ID="BP2"RENDERAS="SECT2"CommandsBoldface characters indicate items that you type, such as IDXID="w11027"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
commands and options. You can use any combination of uppercase and lowercase letters.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\A INSTALLRENDERAS="SECT2"Delimiter Bar ( | )In IDXID="w11028"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
syntax examples, a delimiter bar separating two command options indicates that you can choose one of the options.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"-S | -RDo not type the bar.RENDERAS="SECT2"IDXID="w11029"BOOK="_idx" COLLECTION="nw41" TIDREF="i1186"
DOS IDXID="w11030"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
CommandsDOS commands and command option letters are shown in uppercase letters. For example: FTPD.Because DOS is not case-sensitive, you can type DOS commands in uppercase or lowercase letters.RENDERAS="SECT2"IDXID="w11031"BOOK="_idx" COLLECTION="nw41" TIDREF="i1479"
DOS IDXID="w11032"BOOK="_idx" COLLECTION="nw41" TIDREF="i1186"
Filenames, Directory Names, and PathnamesDOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT.Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters.RENDERAS="SECT2"EllipsesEllipses in syntax examples indicate that parameters, options, or settings can be repeated.For example, in the commandPAGENUM=13 ID="BP3"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SERVER1/SUPERVISOR /option...you could replace option with any number of available options.RENDERAS="SECT2"EmphasisItalic type 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.Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text. RENDERAS="SECT2"Key IDXID="w11033"BOOK="_idx" COLLECTION="nw41" TIDREF="i2009"
NamesAngle brackets surround the name of a key. For example, MOREINFO="NONE"<Enter> corresponds to the MOREINFO="NONE"Enter key on your keyboard. MOREINFO="NONE"<Ctrl>+<c> means hold down the MOREINFO="NONE"Ctrl key and simultaneously type the letter MOREINFO="NONE"c (in lowercase, in this case).PAGENUM=14 ID="BP4"RENDERAS="SECT2"NET.CFG IDXID="w11034"BOOK="_idx" COLLECTION="nw41" TIDREF="i831"
File Section Headings and Parameter SettingsIDXID="w11035"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG section headings and parameter settings are shown in uppercase when used as a reference item and lower case when used in syntax or working examples.For example:[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"netbios  netbios verify timeout 1350[End example]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}
PAGENUM=15 ID="BP5"RENDERAS="SECT2"Square BracketsIn syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP [ -D ] [ -F ]RENDERAS="SECT2"System ResponseMonospace type shows system-generated responses that appear on your workstation screen. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"TNVT220>RENDERAS="SECT2"UNIX IDXID="w11036"BOOK="_idx" COLLECTION="nw41" TIDREF="i684"
CommandsIDXID="w11037"BOOK="_idx" COLLECTION="nw41" TIDREF="i4655"
UNIX® commands are shown in boldface letters. For example, MOREINFO="NONE"vi. Because UNIX is case-sensitive, these commands are usually lowercase. Type UNIX commands exactly as shown.RENDERAS="SECT2"UNIX IDXID="w11038"BOOK="_idx" COLLECTION="nw41" TIDREF="i1479"
Filenames, Directory Names, and PathnamesIDXID="w11039"BOOK="_idx" COLLECTION="nw41" TIDREF="i4655"
UNIX filenames, directory names, and pathnames are shown in italics. For example, /etc/hosts.Because UNIX is case-sensitive, these names usually are in lowercase letters. Type UNIX filenames exactly as shown.RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_hostyou type the name of a computer on your network in place of remote_host.PAGENUM=16 ID="BP6"RENDERAS="SECT1"Supplemental DocumentationThe following publications provide supplemental information specifically related to the NetWare Client for DOS and MS Windows technology and software:MARK=BULLET"The Functions and Operations of the NetWare DOS Requester 1.1," Novell Application Notes, May 94, Vol. 5, No. 5 (Novell part no. 164-000031-005)"Installing and Configuring Novell's Token-Ring Source Routing Drivers," NetWare Application Notes, Oct 91 (Novell part no. 164-000030-010)"Logging In to IBM LAN Server and NetWare from a DOS Workstation," NetWare Application Notes, Nov 91 (Novell part no. 164-000030-011)"Managing Memory in a DOS Workstation: Part 1," NetWare Application Notes, Aug 92 (Novell part no. 164-000031-008)"Managing Memory in a DOS Workstation: Part 2," NetWare Application Notes, Oct 92 (Novell part no. 164-000031-010)"Managing Memory in a DOS Workstation: Using Novell DOS 7," NetWare Application Notes, Oct 93 (Novell part no. 164-000032-010)"Migrating Ethernet Frame Types from 802.3 Raw to IEEE 802.2," NetWare Application Notes, Sep 93 (Novell part no. 164-000032-009)"Multilingual PC Setup with DR DOS," NetWare Application Notes, Sep 93 (Novell part no. 164-000032-009)"NET.CFG Parameters for the NetWare DOS Requester 1.1," Novell Application Notes, Jun 94, Vol. 5, No. 6 (Novell part no. 164-000036-006)"NetWare and LAN Server Client Interoperability via ODINSUP: Part 1," NetWare Application Notes, Sep 92 (Novell part no. 164-000031-009)"NetWare and LAN Server Client Interoperability via ODINSUP: Part 2," NetWare Application Notes, Nov 92 (Novell part no. 164-000031-011)"NetWare and Windows for Workgroups 3.1 Interoperability," NetWare Application Notes, Mar 93 (Novell part no. 164-000032-003)PAGENUM=17 ID="BP7""ODINSUP Interoperability Configurations for DOS Workstations," NetWare Application Notes, Feb 93 (Novell part no. 164-000032-002)"Using the DOS Requester with NetWare 4.0," NetWare Application Notes, Apr 93 (Novell part no. 164-000032-004)"Understanding Token-Ring Source Routing," NetWare Application Notes, May 91 (Novell part no. 164-000030-005)"Workstation Memory Management: Using QEMM386, 386 To The Max, and MS-DOS 6," NetWare Application Notes, Dec 93 (Novell part no. 164-000032-012)RENDERAS="SECT1"Online 
HelpIDXID="w11040"BOOK="_idx" COLLECTION="nw41" TIDREF="i4460"MARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press MOREINFO="NONE"<F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For example, for help with the RIGHTS command, type "RIGHTS /?".Online MS Windows help. The Microsoft* (MS) Windows help viewer allows you to read NetWare help developed for the MS Windows environment. To access the NetWare help screens within MS Windows, press <MOREINFO="NONE"F1> or the "?" button.DynaText online documentation. The DynaText viewer allows you to read NetWare documentation from your DOS, MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4TM and 3.12 documentation except the Quick Access Guide are available on the NetWare Online Documentation CD-ROM.RENDERAS="SECT1"IDXID="w11041"BOOK="_idx" COLLECTION="nw41" TIDREF="i4460"
Additional 
Help ResourcesMARK=BULLETCustomer service. You can contact your Novell Authorized Reseller CLM representative for technical assistance.Most Novell Authorized Resellers have Certified NetWare EngineerSM representatives on their staffs ready to assist users with their networking problems.PAGENUM=18 ID="BP8"Novell Authorized Service CenterSM (NASC) locations. NASCSM facilities are local support providers authorized and supported by Novell. They provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, in the U.S. and Canada call 1-800-338-NASC.Hardware documentation. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS) services. NMSTM services helps you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized Reseller.Other Novell publications. Novell Application Notes and the Novell Research ReportsTM publications cover technical aspects of NetWare based system design, implementation, and management.Application Notes is a collection of technical articles published monthly. Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications from within the United States or Canada, call the Novell Research Order Desk at 1-800-UPDATE1. From other locations, call 801-429-5380.Third-party books and periodicals. Books on NetWare, including books published by Novell PressTM publishing, are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWire® forum on the CompuServe* bulletin board. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers and ask for "Representative 200"MARK=BULLETIn the United States or Canada: 1-800-524-3388PAGENUM=19 ID="BP9"In the United Kingdom: 0800-289-378In Germany: 0130-37-32In other European countries: 44-272-255-111In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.Technical Support Database and NetWire forum on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems. Over 9,000 documents exist on the WWW system for providing technical hints and information.To access the Novell Internet sites, log in as ANONYMOUS and use your E-mail address as your password.   Contact one of the following site addresses:TYPE="VERT"In the United States: ftp.novell.comIn Germany: ftp.novell.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.PAGENUM=20 ID="BP10"Network Support Encyclopedia Professional VolumeSM (NSE Pro) package. This encyclopedia gives customers access to regularly updated information on products and services---plus patches, fixes, and more---from Novell and other vendors.The NSE ProSM package is distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. More information is available on NetWire or from your Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as the Novell LANalyzer® software, are available to help you isolate network problems.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=""PAGENUM=1 ID="BP11"Basic EssentialsRENDERAS="SECT1"OverviewThe NetWare® ClientTM software for DOS and Microsoft* (MS) Windows provides basic connectivity and access to network resources for all of your DOS and MS Windows workstations. In addition, it provides advanced networking services such as rapid data transfer, file and print management, and access to NetWare Directory ServicesTM software to effectively share and produce information.The NetWare Client software has been redesigned to better support the increasing need for greater functionality and performance at the workstation for DOS and MS Windows environments. The new design introduces a software component to the DOS environment known as the NetWare DOS RequesterTM program. The NetWare DOS Requester replaces the NetWare shell files such as NETX.COM. The NetWare User Tools program has also been redesigned to provide you with better access to and management of NetWare services for DOS and MS Windows client workstations.RENDERAS="SECT1"ContentsThis section is divided into three chapters, with the following information discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"ChapterCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"To learn more about basic networks and connections. There is a brief discussion about network resources, users, security, and the file system. You are also introduced to the NetWare Directory ServicesTM technology and the NetWare 4TM network file systemCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15167"Chapter 1, "Understanding Networking Basics"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM15167"3COLNAME=1 ROTATE="0" MOREROWS="0"To learn about the new NetWare DOS RequesterTM, which replaces NETX and other NetWare shell files, and other NetWare Client softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM14751"Chapter 2, "Understanding the NetWare Client Software"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM14751"21COLNAME=1 ROTATE="0" MOREROWS="0"For an overview of how to access and use the features included in the NetWare Tools for your client workstations. There are NetWare Tools for both DOS and MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM26869"Chapter 3, "Understanding Client Tools"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM26869"41LABEL="1"PAGENUM=3 ID="BP12"ID="FM15167"Understanding Networking BasicsRENDERAS="SECT1"OverviewThis chapter provides a IDXID="w11042"BOOK="_idx" COLLECTION="nw41" TIDREF="i416"
basic IDXID="w11043"BOOK="_idx" COLLECTION="nw41" TIDREF="i2889"
overview of the concepts for adding a 
client workstation to your network and for using the workstation. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageCOLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM66585"Network Types COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM66585"4COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94455"Network Connections COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94455"4COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM93094"Network Resources COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93094"6COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM99871"The Structure of the File System COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99871"9COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM27356"Network Users COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27356"11COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM34303"Login  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34303"13COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM22830"Network Security  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM22830"14COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM16389"Network Printing COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16389"17RENDERAS="SECT1"IntroductionIn order to take advantage of your NetWare® client workstations, you need to understand how your client workstations relate to the NetWare operating system they are connecting to and to review basic networking concepts.Users connecting to NetWare 2 and NetWare 3TM need to understand how their client workstations relate to NetWare bindery server networks.Users connecting to a NetWare 4TM network need to understand the NetWare Directory ServicesTM (NDS) architecture and how it affects their environment. PAGENUM=4 ID="BP13"RENDERAS="SECT1"ID="FM66585"Network TypesA network links two or more computers together to share resources and peripherals (such as disk drives, printers, and data). There are two categories of networks: peer-to-peer and client-server.RENDERAS="SECT2"Peer-to-Peer NetworksThe simplest IDXID="w11044"BOOK="_idx" COLLECTION="nw41" TIDREF="i3288"
peer-to-peer IDXID="w11045"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
network has two workstations connected together, each able to use the resources of the other. All workstations on a peer-to-peer network are (or can be) equal. No one workstation is designated as the main computer or central point of control. RENDERAS="SECT2"Client-Server NetworksThe IDXID="w11046"BOOK="_idx" COLLECTION="nw41" TIDREF="i660"
client-server network has at least one workstation configured as a NetWare server. As shown in IDREF="FM31837"Figure 1-1 on page 4, the server is a computer running the network operating system. The server controls communication and shared network resources. The client workstations are the individual computers connected to the network.LABEL="1-1" FLOAT="0"ID="FM31837"A Simple Client-Server NetworkFILEREF="c41ug01a.tif"RENDERAS="SECT1"ID="FM94455"Network ConnectionsYou must make two types of connections to use shared network resources:MARK=BULLETA physical connectionPAGENUM=5 ID="BP14"A logical connectionRENDERAS="SECT2"IDXID="w11047"BOOK="_idx" COLLECTION="nw41" TIDREF="i3308"
Physical ConnectionIn order for resources and information to be shared on a network, servers, client workstations, and other network devices must be physically connected.Each device on the network must have a network board. A cable attached to the network board provides the communication pathway, as shown in IDREF="FM40142"Figure 1-2 on page 5. LABEL="1-2" FLOAT="0"ID="FM40142"Network Board and CablingFILEREF="c41ug02a.tif"The physical connection determines the kind of cable used, the way the cable is configured (called the IDXID="w11048"BOOK="_idx" COLLECTION="nw41" TIDREF="i4533"topology of the network), and the way information is transmitted over the cable (called the IDXID="w11049"BOOK="_idx" COLLECTION="nw41" TIDREF="i3611"protocol).RENDERAS="SECT2"IDXID="w11050"BOOK="_idx" COLLECTION="nw41" TIDREF="i2201"
Logical ConnectionAfter the physical connection to the network is made, you must make a logical connection to access the network services.To make the logical connection on a NetWare network, you must prove that you are an authorized user. This is done when you log in to the network and provide the NetWare operating system your user identification and a valid password. By logging in to a network or attaching to a server, you make a logical connection.PAGENUM=6 ID="BP15"RENDERAS="SECT1"ID="FM93094"Network ResourcesAfter connecting to a NetWare network, you have access to physical and logical resources across the network. A definition for each resource is maintained in a database used by the NetWare operating system.An example of this is a print queue or group name. How you interact with the resource database depends greatly on which version of the NetWare operating system you are running.RENDERAS="SECT2"Resources for NetWare 2 and NetWare 3The NetWare 2 and NetWare 3 operating systems use a flat database structure called a bindery for managing network resource definitions. A definition for each network resource is maintained in the bindery.For example, a definition exists for your user information, such as your username and password. A bindery exists for each server in the network and is independent of resource definitions created on other servers.The bindery structure for each server is flat, with a single location for accessing and managing network resources. Therefore, when you use network resources in a multiple server network, you must be aware of their physical and logical locations in order to use them. RENDERAS="SECT2"Resources for NetWare 4NetWare 4 uses a global database structure called IDXID="w11051"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"NetWare Directory Services (NDSTM) for managing network resource definitions. NDS treats all network resources as objects in a distributed database known as the IDXID="w11052"BOOK="_idx" COLLECTION="nw41" TIDREF="i2716"Directory database. This database organizes resources in a hierarchical tree structure, independent of their physical location.The Directory database supports an entire network of servers. Instead of storing all information on each individual server as in NetWare 2 and 3, information is distributed over a global database and can be accessed by all NetWare servers.Users can access any network service, such as file services or print services, without having to know the physical location of the server that provides the service.PAGENUM=7 ID="BP16"RENDERAS="SECT3"Components of a Directory TreeIDXID="w11053"BOOK="_idx" COLLECTION="nw41" TIDREF="i2731"
NetWare Directory Services operates in a logical organization called the Directory tree. It is called a Directory tree because objects are stored in a hierarchical tree structure, starting with the root object and branching out.Three IDXID="w11054"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
types of 
objects make up the 
Directory tree:MARK=BULLETRoot objectThe root object is placed at the top of the Directory tree by the installation program.Container objectsA branch of the Directory tree consists of a container object and all the objects it holds, which can include other container objects. Leaf objectsLeaf objects are at the end of branches and do not contain any other objects. Volume, User, and NetWare Server objects are some examples of leaf objects.The following figure shows how container objects and leaf objects make up the IDXID="w11055"BOOK="_idx" COLLECTION="nw41" TIDREF="i2731"
NetWare Directory tree.PAGENUM=8 ID="BP17"LABEL="1-3" FLOAT="0"Example of a Directory TreeFILEREF="c41ug03a.tif"To refer to where an object is in the Directory tree, the term IDXID="w11056"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"context is used. The position of the object within its container is its context. For example, in the previous figure, the context of User object Jody is Jody.Development.MedTech. To identify a particular object, you must know its context. To make it easy for users to locate the objects that they work with on a regular basis, you can set up configuration files to specify the context of each object. This gives the users a more manageable view of the tree; they do not have to know exactly where each object is located in the tree.PAGENUM=9 ID="BP18"RENDERAS="SECT1"ID="FM99871"The Structure of the File SystemThe bindery and NetWare Directory Services help you manage network resources such as NetWare servers and printers, but they do not provide control over the file system (volumes, directories, and files). Graphical and text utilities help you manage both network resources and the file system.The file system structure is separate from the bindery or NetWare Directory Services structure. Physically, all network information is stored on hard disks that are controlled by a server. But logically, the file system is represented in NetWare 2 and 3 as a volume and in NetWare 4 as a Volume object. This volume is managed under Bindery emulation provided in NetWare 4.Three types of structures make up the file system: volumes, directories, and files.RENDERAS="SECT2"The File Structure for NetWare 2 and NetWare 3The file IDXID="w11057"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
structure in NetWare 2 and NetWare 3 begins with the file server. The physical hard disks in a file server are divided into volumes, much like a set of books. A volume can contain several physical hard disks, or a single hard disk can be divided into multiple volumes.A volume marks the base of each directory structure. It appears and acts like a DOS root directory or disk drive. Directories are stored at the volume level and subdirectory levels. Files are stored within directories and subdirectories in the same manner as the DOS operating system stores files.The following figure shows how the file structure of NetWare 2 and 3 networks works.PAGENUM=10 ID="BP19"LABEL="1-4" FLOAT="0"IDXID="w11058"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"ID="FM60415"NetWare 2 and 3 File System Structure and Directory PathFILEREF="c41ug04a.tif"RENDERAS="SECT2"The File Structure for NetWare 4The file structure in NetWare 4 begins with the Volume object. A IDXID="w11059"BOOK="_idx" COLLECTION="nw41" TIDREF="i4797"
Volume object is one type of leaf object. It refers to a physical volume where files are stored and allows NetWare Directory Services to locate files. The root directory of a physical volume is also represented as part of a Volume object. It is the highest level of the file system structure. The Volume object provides a link between NetWare Directory Services and each physical volume's file system.IDXID="w11060"BOOK="_idx" COLLECTION="nw41" TIDREF="i1040"
Directories and files are not objects in the Directory tree. They are only a part of the file system. Accessing directories and files within the Directory tree is done by opening a Volume object or setting up Directory Map objects. You can make it easier for users to find files by setting up Directory Map objects that point to a particular location in a volume's file system structure.The following figure shows how these structures make up the file system for a NetWare 4 network.PAGENUM=11 ID="BP20"LABEL="1-5" FLOAT="0"NetWare 4 File System Structure and Directory PathFILEREF="c41ug05a.tif"The position of a 
file within the file system is its IDXID="w11061"BOOK="_idx" COLLECTION="nw41" TIDREF="i1095"directory path.To identify a file, you must know the context of the Volume object representing the physical volume that contains the file and the directory path through the file system structure, including the name of the file. RENDERAS="SECT1"ID="FM27356"Network UsersAccess to a NetWare network is possible only if you are identified to the NetWare operating system as a network IDXID="w11062"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
user. RENDERAS="SECT2"NetWare 2 and NetWare 3 UsersNetWare 2 and NetWare 3 allow for four types of network users, which have varying levels of responsibility on the network:Regular network users are the people who work on the network. They can run applications and work with files according to the rights assigned to them.PAGENUM=12 ID="BP21"Operators are regular network users who have been assigned additional privileges. For example, a file server console operator is a network user who is given specific rights to use the FCONSOLE utility.Managers are users who have been given responsibility for creating or managing other users. Workgroup managers can create and manage users; user account managers can manage, but not create, users. Managers function as supervisors over a particular group, but they do not have supervisor equivalence. Network supervisors are responsible for the operation of the whole network. Network supervisors maintain the system, restructuring and updating it as needed. RENDERAS="SECT2"NetWare 4 UsersNetWare Directory Services identifies the same network users as NetWare 2 and 3 do. In addition, NetWare 4 identifies a User object named ADMIN.The first time the network supervisor logs in, it is as User object ADMIN, which is created by default during NetWare 4 installation. The term network supervisor in NetWare 4 merely refers to the person responsible for setting up the network. NetWare 4 allows for multiple users to have supervisory rights---unlike the single supervisor required by NetWare 2 and 3.When User ADMIN is created on the first NetWare 4 server installed, it can manage all objects because it has the Supervisor right to every object. Initially, ADMIN can also manage all directories and files on every volume in the Directory tree.User ADMIN does not have any special significance like the user SUPERVISOR did in previous versions of NetWare. It is merely the first User object created and, therefore, is granted rights to create and manage all objects.To use the network, every user must be assigned a IDXID="w11063"BOOK="_idx" COLLECTION="nw41" TIDREF="i4718"
User object in the Directory tree. The User object represents the individual and keeps track of the person's use of the network.PAGENUM=13 ID="BP22"RENDERAS="SECT1"ID="FM34303"
LoginBefore you can use any of the network services, you must attach to and log in to the network. Bindery users log in to or attach to individual servers. Therefore, they need a password for each server they are logging in to.IDXID="w11064"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
NetWare Directory Services users log in to the network. Therefore, they need only one password to gain access to all network resources that they have the right to use.Starting up and logging in from a client workstation always consists of the same tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Booting the client workstation.This loads the NetWare Client operating system and is done automatically when you either turn on the power or reboot by pressingMOREINFO="NONE" <Ctrl>+<Alt>+<Del>.Loading the network software and drivers.Changing the default drive to a network drive.Logging in with a username and (usually) a password.NetWare prompts you for your username and password and then completes the network connection.The way users actually perform these steps depends on how the network supervisor has set up the network and the client workstation.All four steps can be accomplished automatically so that the only thing users do is type their passwords. For more information, IDREF="FM41619"see Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161.For example, users can log in to the network by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN ESAYERS MOREINFO="NONE"<Enter>orFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN servername/ESAYERS MOREINFO="NONE"<Enter>
PAGENUM=14 ID="BP23"LOGIN is usually executed from the AUTOEXEC.BAT or another batch file. There is some difference in the command line syntax for the particular NetWare versions.If you are using NetWare 3.12, see BOOK="utilref" COLLECTION="nw312"NetWare 3.12 Utilities Reference for a complete description of the utility. If you are using NetWare 4, see BOOK="utlrfenu" COLLECTION="nw41"NetWare 4 Utilities Reference for a complete description of the utility.When users access resources on the network, background 
authentication IDXID="w11065"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
processes in NetWare 4 verify that the users are who they say they are.Once users 
log in to the network, their trustee rights in the bindery or Directory allow them access in the network.RENDERAS="SECT1"ID="FM22830"Network SecuritySecurity is vital in maintaining a productive network environment. NetWare provides an extensive security system to protect the data on the network.RENDERAS="SECT2"Network Security LevelsNetWare 2, 3, and 4 have three levels of security that can be used separately or in various combinations.RENDERAS="SECT3"File System IDXID="w11066"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
SecurityIDXID="w11067"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
File system security consists of rights security and attributes security.IDXID="w11068"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
Rights security controls what the user is allowed to access in and do to network directories and files. Rights can be granted at either the directory or file level.Rights security is administered by granting trustee assignments to objects and by acquiring effective rights through inheritance and security equivalence.PAGENUM=15 ID="BP24"IDXID="w11069"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
Attribute IDXID="w11070"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
security assigns various characteristics to individual 
directories and files. Directory and 
file attributes have priority over rights security and can prevent tasks that effective rights would allow. Attributes can be used to prevent users fromMARK=BULLETDeleting a file or directoryCopying a fileViewing a file or directoryModifying a fileCreating a new fileIDXID="w11071"BOOK="_idx" COLLECTION="nw41" TIDREF="i334"
Attributes can also be used toMARK=BULLETIDXID="w11072"BOOK="_idx" COLLECTION="nw41" TIDREF="i334"
Mark a file for single-user or multiple-user accessMark a file as modified so that a backup program can select it and leave unmodified files aloneIDXID="w11073"BOOK="_idx" COLLECTION="nw41" TIDREF="i334"
Protect a 
file from corruption by ensuring that either all changes are made or no changes are made when a file is modifiedRENDERAS="SECT3"Login and Password SecurityLogin and password IDXID="w11074"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
security controls who can access the network. The network supervisor uses 
login and password security toMARK=BULLETAssign usernames to users of the networkIDXID="w11075"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
Require passwordsAdditional password restrictions include a minimum password length, periodic password changes, unique passwords, and a number of grace logins after password expiration.Control the use of network resources by restricting where and when users can log inPAGENUM=16 ID="BP25"Detect intruders who attempt to access an account without the correct passwordPrevent unauthorized access to the server consoleRENDERAS="SECT3"Server SecurityIDXID="w11076"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
Server IDXID="w11077"BOOK="_idx" COLLECTION="nw41" TIDREF="i4063"
security controls access to the server console. Access is controlled in three ways:MARK=BULLETIDXID="w11078"BOOK="_idx" COLLECTION="nw41" TIDREF="i4336"
Supervisor rights to the server are granted to give specific users rights to use a console.Directory IDXID="w11079"BOOK="_idx" COLLECTION="nw41" TIDREF="i1095"
rights are granted so that only specific users have access to the SYS:SYSTEM directory, where key server files are stored.Server utilities such as MONITOR and SECURE CONSOLE are used to prevent unauthorized access to the server console.RENDERAS="SECT2"IDXID="w11080"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
Additional Network Security in NetWare 4NetWare 4 also provides IDXID="w11081"BOOK="_idx" COLLECTION="nw41" TIDREF="i3856"
NetWare Directory Services IDXID="w11082"BOOK="_idx" COLLECTION="nw41" TIDREF="i3994"
security to the network security it shares with NetWare 2 and 3.NetWare Directory Services security controls what objects and properties the user is allowed to access. Object IDXID="w11083"BOOK="_idx" COLLECTION="nw41" TIDREF="i2720"
rights control what a trustee can do with an object. These rights control the object as a single piece in the Directory tree, but they don't allow access to information stored within that object---unless the Supervisor object right or property rights are granted.IDXID="w11084"BOOK="_idx" COLLECTION="nw41" TIDREF="i3581"
Property rights control a trustee's access to information stored within the object---that is, the information stored in the object's properties. Each object has several properties to which access is controlled separately.Rights security is administered by granting trustee assignments to objects and by acquiring effective rights through inheritance and security equivalence.PAGENUM=17 ID="BP26"RENDERAS="SECT1"ID="FM16389"Network PrintingRENDERAS="SECT2"Non-Networked PrintingA IDXID="w11085"BOOK="_idx" COLLECTION="nw41" TIDREF="i4251"
standalone workstation can only print to a printer attached to one of its ports. Print jobs are sent directly to the attached printer.As IDXID="w11086"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"
shown in the following figure, a printer connected to a standalone workstation allows print jobs from only that workstation to access the printer.LABEL="1-6" FLOAT="0"IDXID="w11087"BOOK="_idx" COLLECTION="nw41" TIDREF="i4251"Standalone PrintingFILEREF="c41ug07a.tif"RENDERAS="SECT2"Network PrintingIn network printing, printers are often shared and several intervening steps must take place: storage, intermediate processing, and transmission between various processing locations. These steps can greatly affect the complexity of the print job's journey and the time taken before a print job arrives at the printer.NetWare uses a print queue, print server, and print driver to allow several network workstations to print to a network printer. The print server takes print jobs from the print queue and sends them to the printer as shown in IDXID="w11088"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"
the following figure.PAGENUM=18 ID="BP27"LABEL="1-7" FLOAT="0"Network PrintingFILEREF="c41ug08a.tif"If you are using NetWare 3.12, see BOOK="print" COLLECTION="nw312"NetWare 3.12 Print Server for more information on network printing. If you are using NetWare 4, see BOOK="printenu" COLLECTION="nw41"NetWare 4 Print Services for a complete description of the process.RENDERAS="SECT1"Where to Go from HereWith a basic understanding of networking and NetWare network functions, you are ready to upgrade or install your NetWare client workstation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Get more information about some of the topics discussed in this chapterCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74800""Additional Information" on page 19COLNAME=1 ROTATE="0" MOREROWS="0"Set up client workstation hardwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50775""Setting Up Workstation Hardware" on page 70COLNAME=1 ROTATE="0" MOREROWS="0"Prepare your NetWare Client software for a NetWare client workstation installationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM73852""Preparing Client Workstations" on page 70COLNAME=1 ROTATE="0" MOREROWS="0"Prepare the installation softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74874""Preparing the NetWare Client Installation Software" on page 76PAGENUM=19 ID="BP28"RENDERAS="SECT1"ID="FM74800"Additional InformationRENDERAS="SECT2"For NetWare 2.2, NetWare 3.11, and NetWare 3.12COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Topic  COLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare binderyCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Bindery" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare file system (directory structure)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Directory structure" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Drive mapping" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare volumesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Volume" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network printingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="print" COLLECTION="nw312"Printing" in NetWare 3.12 Print ServerCOLNAME=1 ROTATE="0" MOREROWS="0"Print queuesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Print queue" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print serversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Print server" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"PrintersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Printers" in NetWare 3.12 ConceptsRENDERAS="SECT2"For NetWare 4COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in NetWare 4 ConceptsChapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," in Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare Directory ServicesCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," in Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Drive mapping" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare file system (directory structure)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory structure" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare volumesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Volume" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network printingCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="printenu" COLLECTION="nw41"NetWare 4 Print ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"Print queuesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print queue" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print serversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print server" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"PrintersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Printer" in NetWare 4 ConceptsLABEL="2"PAGENUM=21 ID="BP29"ID="FM14751"Understanding the NetWare Client SoftwareRENDERAS="SECT1"OverviewThis chapter introduces and describes the NetWare® DOS RequesterTM and other NetWare ClientTM software that provides the interface between the network and your DOS and Microsoft (MS) Windows 
client workstations.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM32549"The NetWare DOS Requester Architecture  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM32549" 23 COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80509"The NetWare Protocols and Transports COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80509" 28 COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM17754"The Link Support Layer Interface COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM17754" 32 COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM14328"The ODI LAN Driver  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM14328" 32 COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78931"The NET.CFG File COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78931" 33 COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM87390"Novell MS Windows Support  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM87390" 33 PAGENUM=22 ID="BP30"RENDERAS="SECT1"IntroductionThe core components of the NetWare DOS and MS Windows environment are four terminate-and stay-resident (TSR) programs, listed and described in the following table.LABEL="2-1" PGWIDE=1 TOCENTRY="1" Core Components of the NetWare Client for DOS and MS WindowsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TSR ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Link Support LayerTM  (LSL)COLNAME=2 ROTATE="0" MOREROWS="0"Puts the packaged requests from the IPXODI driver into the proper format for transmission on the particular physical network that the client workstations are running on.Also takes replies for the various client workstations from the network (via the network LAN driver), removes the network-specific information it has added, and passes the reply to IPXODI.COLNAME=1 ROTATE="0" MOREROWS="0"NetWare DOS RequesterCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w11089"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
DOS-based client software that provides the interface between DOS and the network. It consists of individual modules that provide various network services.It is loaded when you run the file STARTNET.BAT. This file also loads drivers that the NetWare DOS Requester needs in order to communicate with the network hardware.COLNAME=1 ROTATE="0" MOREROWS="0"ODITM LAN driver (MLID)  (example: NE2000TM)COLNAME=2 ROTATE="0" MOREROWS="0"Takes requests from the LSLTM and sends them to the network. It also receives replies from the network and passes them to the LSL software. This LAN driver is specific to the network board installed in your client workstations.COLNAME=1 ROTATE="0" MOREROWS="0"Transport ProtocolIPXODI  (Internetwork Packet ExchangeTM Open Data-Link InterfaceTM)SPXTM  (Sequenced Packet Exchange)TCP/IP  (Transmission Control Protocol/ Internet Protocol)COLNAME=2 ROTATE="0" MOREROWS="0"Delivers requests and replies between client workstations and the network.Also handles packet sequencing and acknowledgment for the client- server connection.Takes requests that the NetWare DOS Requester has determined are for the network, "packages" them with transmission information (such as their destination), and hands them to the LSL.PAGENUM=23 ID="BP31"When the NetWare Client components are loaded, each component uses a file called NET.CFG to determine the specific software settings it should use. See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for information.RENDERAS="SECT1"ID="FM32549"The NetWare DOS Requester ArchitectureIDXID="w11090"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
The NetWare 
DOS 
Requester consists of a group of 
files that provide 
NetWare support for DOS and MS Windows client workstations. These files consist of a number of Virtual Loadable ModuleTM (VLM) files and a single executable file (VLM.EXE) which manages operation of the .VLM files.Full understanding of the NetWare DOS Requester architecture requires you to understand these components, as discussed in the following sections:MARK=BULLETIDREF="FM84475"Three-Layer Structure IDREF="FM40760"VLM Manager IDREF="FM74975"Connection Table Manager IDREF="FM49529"Backwards Compatibility with NETX Applications IDREF="FM62461"File and Print Services IDREF="FM47764"Memory Usage See "NetWare DOS Requester Option" in Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for information on configuring this option for optimizing your client workstations.RENDERAS="SECT2"ID="FM84475"Three-Layer StructureThe .VLM files are IDXID="w11091"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
grouped into the following three layers:MARK=BULLETIDREF="FM15358"DOS Redirection Layer IDREF="FM14116"Service Protocol Layer IDREF="FM37357"Transport Protocol Layer PAGENUM=24 ID="BP32"The following figure shows how these layers and modules fit together. Individual pieces are discussed in further detail in the sections that follow.LABEL="2-1" FLOAT="0"IDXID="w11092"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"NetWare DOS Requester Layers and ModulesFILEREF="c41ug50a.tif"RENDERAS="SECT3"ID="FM15358"DOS IDXID="w11093"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Redirection 
LayerThis layer provides 
DOS file services through the 
DOS redirector; its VLMTM program is REDIR.VLM. REDIR performs all the DOS-specific callouts.Previously, NETX provided its own file services; the NetWare DOS Requester uses the DOS redirector for most file services.PAGENUM=25 ID="BP33"RENDERAS="SECT3"ID="FM14116"Service IDXID="w11094"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Protocol 
LayerThis layer consists of the following parallel services.LABEL="2-2" PGWIDE=1 TOCENTRY="1" Key Components of the NetWare DOS RequesterCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Protocol Layer Service and ModuleCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Services  NWP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"NWP, the NetWare protocol multiplexor, handles each particular network implementation through these child VLM programs:MARK=BULLETBIND.VLM for NetWare 2 and NetWare 3TM bindery serversNDS.VLM for NetWare 4TM NetWare Directory ServicesTM serversPNW.VLM for Personal NetWareTM (NetWare desktop) serversThe NWP services also include logins and logouts, broadcast messages, and establishing and destroying connections.COLNAME=1 ROTATE="0" MOREROWS="0"Security Services  RSA.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"RSA (Rivest, Shamir, and Adleman, developers of this particular public key encryption system) provides system-level background authentication for the workstation.NetWare uses this encryption system to strengthen user authentication and access control functions.COLNAME=1 ROTATE="0" MOREROWS="0"File Services  FIO.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"FIO, the file input/output module, is a separate-but-parallel piece that implements a basic file-transfer protocol. This includes cached or noncached read/write, burst mode-based read/write, and large internet packet read/write.The Packet BurstTM protocol in FIO.VLM is based on Open Data-Link Interface interconnectivity strategy and is referred to as PBODI. This functionality allows users to choose performance over memory use and vice versa.COLNAME=1 ROTATE="0" MOREROWS="0"Print Services  PRINT.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The PRINT module provides printing services using the FIO module for its file writes. Print redirection is handled in the following ways, depending on entries in the NET.CFG file:MARK=BULLETNoncachedCachedVia Packet Burst protocol to the serverVia File Services (FIO)PAGENUM=26 ID="BP34"RENDERAS="SECT3"ID="FM37357"Transport IDXID="w11095"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
Protocol 
LayerThis layer is responsible for maintaining connections, providing packet transmissions between connections and performing other transport-specific functions.The IPXNCP module uses the IPXTM protocol as a transport mechanism.The IDXID="w11096"BOOK="_idx" COLLECTION="nw41" TIDREF="i382"
AUTO.VLM module reconnects a client workstation to a server and rebuilds the workstation's environment---excluding file-specific items---to its original state prior to losing connection.RENDERAS="SECT2"Communication and Connection Management The NetWare DOS Requester contains communication and connection management for controlling the NetWare client software.RENDERAS="SECT3"ID="FM40760"VLM ManagerThe VLM Manager (VLM.EXE) controls communication and memory issues between the individual VLM software programs. It is responsible for loading the required modules and disbursing requests to individual modules.Therefore, instead of loading NETX, EMSNETX, XMSNETX, or BNETX, the user loads only the VLM.EXE program.IDXID="w11097"BOOK="_idx" COLLECTION="nw41" TIDREF="i4770"
The VLM Manager decides whether a given VLM program uses expanded memory, extended memory, conventional memory, or any other memory type supported, without affecting the individual VLM programs.RENDERAS="SECT3"ID="FM74975"Connection Table IDXID="w11098"BOOK="_idx" COLLECTION="nw41" TIDREF="i788"
ManagerThe Connection Table Manager (CONN.VLM) spans all the layers of the NetWare DOS Requester architecture.CONN allows client workstations running the NetWare DOS Requester to establish a configurable number of connections with multiple NetWare servers.PAGENUM=27 ID="BP35"RENDERAS="SECT2"ID="FM49529"Backwards IDXID="w11099"BOOK="_idx" COLLECTION="nw41" TIDREF="i2895"
Compatibility with IDXID="w11100"BOOK="_idx" COLLECTION="nw41" TIDREF="i2895"
NETX ApplicationsIDXID="w11101"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"
The NETX.VLM program provides backwards compatibility with NETX and other older versions of the shell. Therefore, you do not need to run NETX or other versions of the shell with the NetWare DOS Requester.Nevertheless, because the NetWare DOS Requester is a redirector on the back end of DOS, it performs differently than the NetWare Shell software under specific conditions. See "BOOK="ws_d2enu" COLLECTION="nw41"Compatibility with NetWare Shell Parameters" under "NetWare DOS Requester Option," in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.The following figure shows a comparison of the NETX and the NetWare DOS Requester architectures.LABEL="2-2" FLOAT="0"Comparison of NETX and NetWare DOS Requester ArchitectureFILEREF="c41ug09a.tif"The NetWare DOS Requester offers several improvements over NETX:MARK=BULLETProvides a modular architecture that has advantages for current and future applications.PAGENUM=28 ID="BP36"Takes advantage of memory-swapping technology and DOS redirection capability.Includes the Packet Burst protocol and Large Internet Packet (LIP) support.Supports the installed base of NetWare users by providing backward compatibility with NETX.Supports the NetWare Directory Services architecture in NetWare 4 software.RENDERAS="SECT2"ID="FM62461"File and Print ServicesIDXID="w11102"BOOK="_idx" COLLECTION="nw41" TIDREF="i2896"
Previously, the NetWare Client shell for DOS intercepted requests for DOS services. At the client workstations, the NetWare shell (NETX) software hooked interrupts in front of DOS and provided network services for files and printing.The NetWare IDXID="w11103"BOOK="_idx" COLLECTION="nw41" TIDREF="i2895"
DOS Requester takes advantage of DOS redirection to provide file and print services. It also uses NetWare shell technology to add features to DOS and provide compatibility with applications that run on the NetWare shell software.RENDERAS="SECT2"ID="FM47764"Memory UsageIDXID="w11104"BOOK="_idx" COLLECTION="nw41" TIDREF="i2736"IDXID="w11105"BOOK="_idx" COLLECTION="nw41" TIDREF="i2390"
The NetWare DOS Requester works with extended memory, expanded memory, and conventional memory. When loading in extended memory, the Requester loads in LIM XMS 2.0 memory, not in the High Memory Area (HMA), meaning that extended memory can coexist with DOS loaded high.The VLM.EXE program automatically selects the best possible memory use: extended memory first, expanded memory second, and conventional memory only in the absence of enhanced memory options. RENDERAS="SECT1"ID="FM80509"The NetWare Protocols and TransportsThe IDXID="w11106"BOOK="_idx" COLLECTION="nw41" TIDREF="i650"
NetWare software that allows client workstations to communicate and be understood on the network is separated into two components, consisting of a protocol, which manages data, and a transport, which manages application messages. This can be provided by one piece of software or by many.PAGENUM=29 ID="BP37"In order for client workstations to communicate on a network, they must use a protocol that is identical to what is being used on the network.Sometimes client workstations are configured to use multiple protocols. In this case, workstations can communicate with different networks simultaneously.For example, a client workstation using both IPX and TCP/IP protocols can communicate with servers configured for IPX or TCP/IP protocols only.The NetWare client protocols support Level 3 (the network layer) through Level 4 (the transport layer) of the Open Systems Interconnection (OSI) networking reference model from the International Organization for Standardization (ISO).The NetWare client software provides the following standard protocols:MARK=BULLETARP (Address Resolution Protocol)BOOTP (provides TCP/IP configuration information)ICMP (Internet Control Message Protocol) IP (Internet Protocol)IPX/SPXTM (Internetwork Packet Exchange/Sequenced Packet ExchangeTM)MIB (Management Information Base)NetBIOS (NetBIOS Service Interface)RARP (Reverse Address Resolution Protocol)RPL (Remote Program Load)SNA (System Network Architecture)SNMP (Simple Network Management Protocol)TCP (Transmission Control Protocol)UDP (User Datagram Protocol)XNS (Xerox* Network System)PAGENUM=30 ID="BP38"For information on optimizing your client workstations for using NetWare transport protocols, see Chapter 2, "NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference.RENDERAS="SECT2"ID="FM41112"IPXODI ProtocolIDXID="w11107"BOOK="_idx" COLLECTION="nw41" TIDREF="i1966"
Although the NetWare DOS Requester intercepts and prepares IDXID="w11108"BOOK="_idx" COLLECTION="nw41" TIDREF="i3193"
requests for network transmission, the actual delivery is made by IDXID="w11109"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
the IPX protocol, The NetWare client software supports this through the Internetwork Exchange Open Data-Link Interface (IPXODI.COM program). IPXODI attaches a header to each data packet. The header specifies necessary information for targeted network delivery, announcing where the packet came from, where it's going, and what happens after its delivery.The targeting ability of IPXODI is important but, by itself, does not guarantee successful delivery of a data transmission.IPXODI transmits data packets as datagrams (self-contained packages that move independently from source to destination) and, therefore, can deliver the packets only on a best-effort basis. Delivery is guaranteed only when using the SPX protocol.RENDERAS="SECT2"SPX ProtocolIDXID="w11110"BOOK="_idx" COLLECTION="nw41" TIDREF="i4242"
SPX (Sequenced Packet Exchange) is a protocol within IPXODI that is derived from the Novell IPX protocol using the Xerox Sequenced Packet protocol. It enhances IPX by supervising data sent out across the network.SPX verifies and acknowledges successful packet delivery to any network destination by requesting a verification that the data was received.Within this verification must be a value that matches the value calculated from the data before transmission. So SPX ensures not only that the data packet arrived, but that it arrived intact.SPX can track a single data transmission or data transmissions consisting of a series of separate packets. If an acknowledgment request brings no response within a specified time, SPX retransmits it.PAGENUM=31 ID="BP39"After a reasonable number of retransmissions fail to return a positive acknowledgment, SPX assumes the connection has failed and warns the operator of the failure.RENDERAS="SECT2"ID="FM12836"TCP/IP ProtocolThe Novell Transmission Control Protocol/Internet Protocol (TCP/IP) software (the TCP/IP.EXE file) provides communication between NetWare (IPX) networks across an IP internet that does not directly support IPX. This is known as IPX/IP tunneling. NetWare TCP/IP also provides a transport interface for higher-level networking services. This interface provides client workstations data-communication services to the Network File System (NFS), and third-party applications supporting the 4.3 BSD UNIX® socket interface, the AT&T* Streams Transport Layer Interface (TLI), MS Windows Sockets, and NetBIOS interface using the RFC-1001/1002 compliant B-node (broadcast) type of the NetBIOS protocol. NetWare TCP/IP supports ODI LAN drivers for the following frame types:MARK=BULLETEthernet DIXEthernet 802.2 and SNAPToken-ring 802.2 and SNAPARCnet*IBM* PCN2FDDISLIP and PPP asynchronous serial linePAGENUM=32 ID="BP40"RENDERAS="SECT1"ID="FM17754"The Link Support Layer InterfaceIDXID="w11111"BOOK="_idx" COLLECTION="nw41" TIDREF="i2120"
The Link Support Layer (LSL) interface is an implementation of the Open Data-Link Interface specification. The LSL program serves as an intermediary between the ODI LAN drivers and communication protocols like IPXODI, ARP, and TCP/IP.The LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.RENDERAS="SECT1"ID="FM14328"The ODI LAN DriverEvery transmission prepared by the NetWare DOS Requester must pass through the network board connecting the workstation to the network. The LAN 
driver, often referred to as a Multiple Link Interface DriverTM (MLIDTM), makes the connection between the physical network board and the logical routines and programs that use it.A LAN driver is linked both to the specific network board and to the network protocol.In 1989, Novell and Apple* jointly developed the Open Data-Link Interface (ODI) specification to provide seamless network integration at the transport, network, and data-link levels.ODI simplified the development of LAN drivers for a wide variety of network boards and network transport protocol stacks by providing the following functionality:MARK=BULLETSupports multiple network boards and protocols in a single client workstationSupports multiple protocols on a single network board and topologySupports multiple frame formats over a single network board and topologyProvides transport supportThis allows a UNIX workstation (using the TCP/IP protocol), for example, to use a NetWare server to queue and print documents and save data files that are shareable with IPX client workstations.PAGENUM=33 ID="BP41"The result is easier access to a wide variety of networked resources without requiring multiple network connections or additional investments in hardware and software.RENDERAS="SECT1"ID="FM78931"The NET.CFG FileIDXID="w11112"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG is a specialized text file that you create with any ASCII text editor and include on a workstation boot diskette with any other necessary boot files. The NET.CFG file replaces the SHELL.CFG file.Like the DOS CONFIG.SYS file, the 
NET.CFG file contains configuration values of the LAN drivers and NetWare DOS Requester that are read and interpreted when your client workstation starts up. These values adjust the operating parameters of the NetWare DOS Requester, IPX, and other NetWare Client software.You might want to change the values of certain NetWare DOS Requester parameters to modify the client software's reaction in certain routines and processes.Applications such as database, multitasking, or NetBIOS (involved in peer-to-peer communications or distributed processing) might require parameter values different from the default values to function properly on the network.You might also find that printing, file retrieval, and other network problems can be solved by adjusting client software parameters.To find out which parameters you might need to modify, consult the setup reference for each application used on your network.To create a NET.CFG file and modify the various parameters, see Chapter 2, "NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for information.RENDERAS="SECT1"ID="FM87390"Novell MS Windows SupportThe following sections explain the integration of 
MS Windows with the NetWare client software:MARK=BULLETIDREF="FM94944"Accessing the Network from an MS Windows ApplicationPAGENUM=34 ID="BP42"IDREF="FM55058"Running DOS Applications in Real or Standard ModeIDREF="FM52815"Running DOS Applications in Enhanced ModeIDREF="FM71860"Receiving Broadcast MessagesIDREF="FM78307"Printing to Network QueuesRENDERAS="SECT2"ID="FM94944"Accessing the IDXID="w11113"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
Network from an 
MS 
Windows ApplicationIn addition to the core IDXID="w11114"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
NetWare client software---which consists of the NetWare DOS Requester, IPX protocol, and Link Support Layer support---there are some additional NetWare support files necessary for NetWare client workstations to work properly in an MS Windows environment:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Support FileCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NETWARE.DRV NETWARE.HLPCOLNAME=2 ROTATE="0" MOREROWS="0"The MS Windows network driver and associated help file to provide access to network redirector functionality from MS Windows File Manager.COLNAME=1 ROTATE="0" MOREROWS="0"NWPOPUP.EXECOLNAME=2 ROTATE="0" MOREROWS="0"NetWare messaging utility. Used to receive messages and alerts from a NetWare server.COLNAME=1 ROTATE="0" MOREROWS="0"VIPX.386COLNAME=2 ROTATE="0" MOREROWS="0"Virtual device driver providing virtualization services for NetWare IPX protocol for MS Windows environment and across DOS virtual machines.COLNAME=1 ROTATE="0" MOREROWS="0"VNETWARE.386COLNAME=2 ROTATE="0" MOREROWS="0"Virtual device driver providing virtualization services for NetWare redirector for MS Windows environment and across DOS virtual machines.The following figure illustrates the MS Windows driver, NETWARE.DRV, which translates between MS Windows and DOS.PAGENUM=35 ID="BP43"LABEL="2-3" FLOAT="0"Accessing the Network from an MS Windows ApplicationFILEREF="c41ug35a.tif"For example, when you use the NetWare User Tools "NetWare Drives Connections" to connect to a network drive, your client workstation uses this driver.PAGENUM=36 ID="BP44"RENDERAS="SECT2"ID="FM55058"Running DOS IDXID="w11115"BOOK="_idx" COLLECTION="nw41" TIDREF="i1204"
Applications in 
Real or Standard ModeThe following figure illustrates the IDXID="w11116"BOOK="_idx" COLLECTION="nw41" TIDREF="i1182"
NetWare task-switching file for real or standard mode, TBMI2.COM, which synchronizes network calls and responses for DOS sessions.LABEL="2-4" FLOAT="0"Running a DOS Application in Real or Standard ModeFILEREF="c41ug36a.tif"For example, if you are running MS Windows on a 286 machine and you choose the DOS prompt icon to go to a DOS window and check your email, your client workstation uses this file.PAGENUM=37 ID="BP45"RENDERAS="SECT2"ID="FM52815"Running 
DOS IDXID="w11117"BOOK="_idx" COLLECTION="nw41" TIDREF="i1204"
Applications in 
Enhanced ModeThe following figure illustrates the IDXID="w11118"BOOK="_idx" COLLECTION="nw41" TIDREF="i1182"
NetWare task-switching file for enhanced mode, VIPX.386, which synchronizes network calls and responses for DOS sessions.LABEL="2-5" FLOAT="0"Running a DOS Application in Enhanced ModeFILEREF="c41ug38a.tif"For example, if you are running MS Windows in enhanced mode and you choose the DOS prompt icon to go to a DOS window and check your email, your client workstation uses this file.PAGENUM=38 ID="BP46"RENDERAS="SECT2"ID="FM71860"Receiving Broadcast IDXID="w11119"BOOK="_idx" COLLECTION="nw41" TIDREF="i2424"
MessagesThe following figure illustrates the virtual device driver, VNETWARE.386, which works with the NETWARE.DRV driver and NWPOPUP.EXE program to coordinate and display message dialogs.LABEL="2-6" FLOAT="0"Receiving a Broadcast MessageFILEREF="c41ug37a.tif"For example, if the secretary sends a message informing you that paychecks have arrived, your client workstation uses this driver.PAGENUM=39 ID="BP47"RENDERAS="SECT2"ID="FM78307"Printing to 
Network IDXID="w11120"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"
QueuesThe following figure illustrates the process used when you print to a network queue from an MS Windows application.LABEL="2-7" FLOAT="0"Printing to a Network QueueFILEREF="c41ug34a.tif"For example, if you print a text file from the MS Windows Notepad application, your client workstation uses these components.RENDERAS="SECT1"Where to Go from HereWith a basic understanding of the NetWare Client software, you are ready to prepare for upgrading or installing your NetWare client.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Get more information about some of the topics discussed in this chapterCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20405""Additional Information" on page 40COLNAME=1 ROTATE="0" MOREROWS="0"Set up client workstation hardwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50775""Setting Up Workstation Hardware" on page 70COLNAME=1 ROTATE="0" MOREROWS="0"Prepare your client software for a NetWare client workstation installationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM18804""Setting Up Workstation Software" on page 75COLNAME=1 ROTATE="0" MOREROWS="0"Prepare the installation softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74874""Preparing the NetWare Client Installation Software" on page 76PAGENUM=40 ID="BP48"RENDERAS="SECT1"ID="FM20405"Additional InformationRENDERAS="SECT2"For NetWare 2 and NetWare 3COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXODICOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"IPXODI.COM" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Link Support Layer (LSL)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Link Support Layer" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network board driversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"LAN driver" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NETXCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="overview" COLLECTION="nw312"NetWare Shell Files" in NetWare 3.12 OverviewRENDERAS="SECT2"For NetWare 4COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXODICOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"IPXODI" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Link Support Layer (LSL)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Link Support Layer" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare DOS RequesterCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Virtual Loadable Module Software" in ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network board driversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"LAN driver" in NetWare 4 ConceptsLABEL="3"PAGENUM=41 ID="BP49"ID="FM26869"Understanding Client ToolsRENDERAS="SECT1"OverviewThis chapter briefly explains how you can use the NetWare®
 User 
Tools to perform common network tasks.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM76103"Starting NetWare User Tools for DOS (NETUSER)COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76103"42COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM76102"Using NetWare User Tools for DOS (NETUSER)COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM76102"44COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88084"Exiting NetWare User Tools for DOS (NETUSER)COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88084"46COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM32927"Starting NetWare User Tools for MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM32927"46COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78034"Using NetWare User Tools for MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78034"47COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM17027"Exiting NetWare User Tools for MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM17027"64RENDERAS="SECT1"IntroductionUse the NetWare 
User Tools to display and modify the current status of your client workstation, drive mappings, servers, printers, queues, volumes, and other necessary information.NetWare User Tools are compatible with NetWare 2, NetWare 3TM, and NetWare 4TM networks.NetWare User Tools are available for both DOS and Microsoft (MS) Windows.PAGENUM=42 ID="BP50"RENDERAS="SECT1"PrerequisitesBefore you start using the NetWare User Tools, you should complete these tasks:MARK=CHECKBOXInstall or upgrade your client softwareComplete the procedures in IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89.If you are using NetWare 4, you should be familiar with the following topics inBOOK="cncptenu" COLLECTION="nw41" Concepts:ContextNetWare Directory ServicesObjectsPrint queuePropertiesIf you are using NetWare 2 or 3, you should be familiar with the following topics inBOOK="cncptenu" COLLECTION="nw41"  Concepts:BinderyObjectPrintingPropertyRENDERAS="SECT1"ID="FM76103"Starting NetWare User Tools for DOS (NETUSER)The 
NetWare User Tools for 
DOS are found in the 
NETUSER utility. This utility is available only in NetWare 4 packages. It is not included in the NetWare Client Kit or other versions of NetWare.Because NETUSER is a NetWare 4 utility, you need to already have a connection to the network and be logged in to a NetWare 4 network. The utility files are found in the SYS:PUBLIC directory. For more information, see IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169.PAGENUM=43 ID="BP51"RENDERAS="SECT2"PrerequisitesIDXID="w11121"BOOK="_idx" COLLECTION="nw41" TIDREF="i2686"
Before you can start NETUSER, your client workstation requires the following:MARK=CHECKBOXA physical connection to the networkDR DOS®
, Novell DOS®
, PC-DOS, or MS-DOS* loaded and runningClient software installed or upgradedComplete the procedures in IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89.An authenticated connection to the networkFor more information, see IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Map the next network drive to SYS:PUBLIC by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:PUBLICMOREINFO="NONE" <Enter>This mapping might already be set up as a search drive in a login script for your client workstation. Use the MAP utility to view a list of existing drive mappings. If a drive mapping already exists for the SYS:PUBLIC directory, then proceed to Step 2.PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G: to PUBLIC, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G:MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Start NETUSER by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETUSERMOREINFO="NONE" <Enter>
PAGENUM=44 ID="BP52"RENDERAS="SECT1"ID="FM76102"Using NetWare User Tools for DOS (IDXID="w11122"BOOK="_idx" COLLECTION="nw41" TIDREF="i2686"
NETUSER)The NetWare User Tools for DOS provides you with a 
graphical way of accessing IDXID="w11123"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
network resources, such as volumes, directories, printers, and users.The following figure shows an example of the IDXID="w11124"BOOK="_idx" COLLECTION="nw41" TIDREF="i4738"
NETUSER utility screen.LABEL="3-1" FLOAT="0"Menu Options for NETUSERFILEREF="c41ug11a.tif"RENDERAS="SECT2"AccessingIDXID="w11125"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
 Online IDXID="w11126"BOOK="_idx" COLLECTION="nw41" TIDREF="i3077"
HelpTo see a list of commands and the procedures you can perform with 
NETUSER, access online help by pressing MOREINFO="NONE"<F1> at any time.RENDERAS="SECT2"Using NetWare User Tools for DOS (NETUSER) OptionsRENDERAS="SECT3"PrintingIDXID="w11127"BOOK="_idx" COLLECTION="nw41" TIDREF="i3540"
Use "Printing" toMARK=BULLETSet up print queuesControl 
network 
printingView information about network printingRedirect a printer port to the networkPAGENUM=45 ID="BP53"RENDERAS="SECT3"MessagesIDXID="w11128"BOOK="_idx" COLLECTION="nw41" TIDREF="i2424"
Use "
Messages" toMARK=BULLETSend a brief message from your 
client workstation to one or more users or groups on the networkDisable or enable incoming messages sent from other clientsRENDERAS="SECT3"DrivesIDXID="w11129"BOOK="_idx" COLLECTION="nw41" TIDREF="i1222"
Use "
Drives" toMARK=BULLETView current 
drive mappingsCreate or 
change 
network drive mappingsMap a drive to a fake root directoryMap the next available driveRENDERAS="SECT3"AttachmentsUse "
Attachments" IDXID="w11130"BOOK="_idx" COLLECTION="nw41" TIDREF="i1203"
to MARK=BULLETCreate or delete IDXID="w11131"BOOK="_idx" COLLECTION="nw41" TIDREF="i793"
network a
ttachmentsIDXID="w11132"BOOK="_idx" COLLECTION="nw41" TIDREF="i2323"IDXID="w11133"BOOK="_idx" COLLECTION="nw41" TIDREF="i3250"
Change 
your 
passwordView server informationModify login scriptsRENDERAS="SECT3"Change ContextUse "
Change IDXID="w11134"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
Context" toMARK=BULLETBrowse the Directory treeChange your current contextPAGENUM=46 ID="BP54"This option is not available when you are logged in to a NetWare 4 server in bindery mode. For more information, see IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169.RENDERAS="SECT1"ID="FM88084"Exiting NetWare User Tools for DOS (NETUSER)You exit NETUSER through the "Exit?" confirmation prompt. You can display this prompt in two ways:MARK=BULLETPressMOREINFO="NONE" <Esc> until the "Exit?" confirmation prompt appears.Press MOREINFO="NONE"<Alt>+<F10> anywhere within NETUSER to display the "Exit?" confirmation prompt.To exit NETUSER, choose "Yes" when prompted. RENDERAS="SECT1"ID="FM32927"Starting IDXID="w11135"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
NetWare User Tools for MS WindowsThe NetWare User Tools for 
MS Windows are found in the NETWARE.DRV file. These tools are available in NetWare 3.12, NetWare 4, and NetWare Client Kits for DOS and MS Windows packages.This version of the NETWARE.DRV (3.01 or later) is compatible only with the NetWare DOS Requester. For MS Windows support of NetWare Shell files, such as NETX, use version 2.02 of the NETWARE.DRV.RENDERAS="SECT2"PrerequisitesIDXID="w11136"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
Before you can start NetWare User Tools for MS Windows, your client workstation requires the following:MARK=CHECKBOXA physical connection to the networkDR DOS, PC-DOS, Novell DOS, or MS-DOS loaded and runningClient software installed or upgradedComplete the procedures in IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89.A copy of MS Windows 3.x installed on your client workstationPAGENUM=47 ID="BP55"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Start MS Windows.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F6> or select the "NetWare User Tools" icon in the NetWare program group.If the "NetWare User Tools" icon is not displayed, you can also access NetWare User Tools for MS Windows by creating a Program object in the MS Windows Program Manager with NWUSER.EXE. The NWUSER.EXE file is in the MS Windows SYSTEM directory for the NetWare Client software installation. RENDERAS="SECT1"ID="FM78034"Using NetWare User Tools for MS WindowsThe IDXID="w11137"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
NetWare User Tools for MS Windows provides you with graphical access to IDXID="w11138"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
network resources and allows you to configure and customize your client workstation connections.You can do the following with the NetWare User Tools for MS Windows:MARK=BULLETManage drive mappingsManage printer connections and setupManage server connectionsSend messagesModify client workstation settingsSet the NetWare User Tools hotkeyChange directory and file propertiesPAGENUM=48 ID="BP56"RENDERAS="SECT2"Using Quick KeysIDXID="w11139"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
Each Tool in the NetWare User Tools for MS Windows can be accessed by using quick keys. The available quick keys are listed in the following table.LABEL="3-1" PGWIDE=0 TOCENTRY="1" Quick KeysCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Tool COLNAME=2 ROTATE="0" MOREROWS="0"Quick Key VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"Exit COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<X>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare Drive Connections COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<D>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare Printer Connections COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<P>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare Connections COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<C> COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare Send Messages COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<M>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare Settings COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<S>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"NetWare User Tools for MS Windows Help COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<H>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"User-Defined Button 1COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<1>COLNAME=1 ROTATE="0" MOREROWS="0"MOREINFO="NONE"User-Defined Button 2COLNAME=2 ROTATE="0" MOREROWS="0"MOREINFO="NONE"<Alt>+<2>RENDERAS="SECT2"Using the Menu BarIDXID="w11140"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
The menu bar (see IDREF="FM38294"Figure 3-2) shows menu options you can use. To complete a task, first choose the button that corresponds with the task or connection you are performing. PAGENUM=49 ID="BP57"LABEL="3-2" FLOAT="0"ID="FM38294"Menu Bar for NetWare User Tools for MS WindowsFILEREF="c41ug13a.tif"Each time you select a menu option, the corresponding button depresses or a dialog box appears. If an option is grayed, that option is not active or available.RENDERAS="SECT2"Accessing IDXID="w11141"BOOK="_idx" COLLECTION="nw41" TIDREF="i56"
Online IDXID="w11142"BOOK="_idx" COLLECTION="nw41" TIDREF="i3077"
HelpTo see a list of commands and the procedures you can perform with NetWare User Tools for MS Windows, choose the "Help" button from the menu bar.PAGENUM=50 ID="BP58"RENDERAS="SECT2"Using NetWare User Tools for MS Windows 
OptionsRENDERAS="SECT3"NetWare Drive ConnectionsUse the "NetWare 
Drive 
Connections" window (see IDREF="FM34787"Figure 3-3) to map 
network resources in the Directory tree and file system to your client workstation drives. Select the resource you want to connect to in the "Resources" list, and then choose a client workstation drive. Now, choose the "Map" button at the bottom of the window.If you are using keyboard entry, type in the full path for the drive mapping inside the "Path" field and then choose "Map."For example, the following figure illustrates the drive mapping REPORTS\SYS\WORD to the client workstation drive P: using the "NetWare Drive Connections" option.LABEL="3-3" FLOAT="0"ID="FM34787""NetWare Drive Connections" WindowFILEREF="c41ug14a.tif"RENDERAS="SECT4"Using the "NetWare Drive Connections" WindowWhen using this window, rememberPAGENUM=51 ID="BP59"MARK=BULLETBefore using "NetWare Drive Connections," you must first log in to a Directory Services tree or server that contains the object you want to connect to.NetWare User Tools for MS Windows recognizes all drive mappings that existed before MS Windows was started. However, when you are using a DOS Box inside MS Windows, your previous search drives are disabled unless the "Global Drives & Paths" box is checked in the "NetWare Setting" window.NetWare User Tools supports universal naming conventions (UNC) redirection for network volumes and directories. IDREF="FM91120"See "Using Universal Naming Convention (UNC) Paths in MS Windows" on page 188 for more information.The "Permanent" button allows you to specify a drive to reconnect at the startup of MS Windows.RENDERAS="SECT4"Viewing the "Resources" ListThis list within the "NetWare Drive Connections" window contains the following:MARK=BULLETVolumesDirectoriesNetWare Directory Services objectsNetWare Directory Services containersThe volumes and directories are listed in a hierarchical structure. Choose the "Volume" icon in the "Resources" list to display subdirectories. PAGENUM=52 ID="BP60"RENDERAS="SECT3"NetWare 
Printer 
ConnectionsIDXID="w11143"BOOK="_idx" COLLECTION="nw41" TIDREF="i3541"
Use this window (see IDREF="FM88191"Figure 3-4) to capture network print queues to your client printing ports. Select the resource you want to connect to in the "Resources" list, and then choose a client workstation port. Now, choose the "Capture" button at the bottom of the window. If you are using keyboard entry, type in the full queue name for the port capture inside the "Queue" field and then choose "Capture."LABEL="3-4" FLOAT="0"ID="FM88191""NetWare Printer Connections" WindowFILEREF="c41ug15a.tif"RENDERAS="SECT4"Using the "NetWare Printer Connections" WindowWhen using this window, rememberMARK=BULLETBefore using "NetWare Printer Connections," you must first log in to a server or Directory tree that contains the object you want to connect to.NetWare User Tools for MS Windows recognizes all print queue captures that existed before MS Windows was started. PAGENUM=53 ID="BP61"NetWare User Tools supports universal naming conventions (UNC) redirection for network print queues. IDREF="FM74015"See "Using Universal Naming Convention (UNC) Port Redirection in MS Windows" on page 204 for more information.The "Permanent" button allows you to specify a print queue to reconnect at the startup of MS Windows.RENDERAS="SECT4"Viewing the "Resources" ListThis list within the "NetWare Printer Connections" window contains the following:MARK=BULLETPrinter objectsPrint queue objectsRENDERAS="SECT4"Setting LPT OptionsIDXID="w11144"BOOK="_idx" COLLECTION="nw41" TIDREF="i3541"
Choose the "LPT Settings" button at the bottom of the "NetWare Printer Connections" window to access the "Printer 
Options for LPT" 
window.The following table lists and explains the setting options that you can assign.LABEL="3-2" PGWIDE=0 TOCENTRY="1" LPT Setting OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NotifyCOLNAME=2 ROTATE="0" MOREROWS="0"Provides a confirmation of print job completion.COLNAME=1 ROTATE="0" MOREROWS="0"FormfeedCOLNAME=2 ROTATE="0" MOREROWS="0"Places a page break between print jobs.COLNAME=1 ROTATE="0" MOREROWS="0"CopiesCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of copies to print.COLNAME=1 ROTATE="0" MOREROWS="0"Enable TabsCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the number of characters in a tab stop.COLNAME=1 ROTATE="0" MOREROWS="0"Enable TimeoutCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies the amount of time before the print buffer is closed and the job is sent to a printer.COLNAME=1 ROTATE="0" MOREROWS="0"Enable BannerCOLNAME=2 ROTATE="0" MOREROWS="0"Allows for a banner page to be printed at the front of your print job.COLNAME=1 ROTATE="0" MOREROWS="0"Form NameCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to select a defined print form.COLNAME=1 ROTATE="0" MOREROWS="0"Auto EndcapCOLNAME=2 ROTATE="0" MOREROWS="0"Specifies that the captured printing jobs be closed COLNAME=1 ROTATE="0" MOREROWS="0"DirectCOLNAME=2 ROTATE="0" MOREROWS="0"(Personal NetWare only) Lets your print job bypass the print queue if there are no jobs resident.COLNAME=1 ROTATE="0" MOREROWS="0"HoldCOLNAME=2 ROTATE="0" MOREROWS="0"Stops a print file from being sent to a queue.PAGENUM=54 ID="BP62"To allow for more than three printer connections, IDREF="FM14065"see "Setting the Number of Available Printer Connections" on page 203 for more information.If you are connecting to a NetWare 3 network, see 
BOOK="print" COLLECTION="nw312"Print Server for more information about each option. If you are connecting to a NetWare 4 network, see 
BOOK="printenu" COLLECTION="nw41"Print Services for more information about each option.PAGENUM=55 ID="BP63"RENDERAS="SECT3"NetWare IDXID="w11145"BOOK="_idx" COLLECTION="nw41" TIDREF="i794"
ConnectionsIDXID="w11146"BOOK="_idx" COLLECTION="nw41" TIDREF="i2323"
Use the "
NetWare IDXID="w11147"BOOK="_idx" COLLECTION="nw41" TIDREF="i2537"
Connections" 
window (see IDREF="FM6861A"Figure 3-5) to connect to Directory trees and network servers.Select the resource you want to connect to in the "Resources" list, and then choose the "Login" button at the bottom of the window. LABEL="3-5" FLOAT="0"ID="FM6861A""NetWare Connections" WindowFILEREF="c41ug16a.tif"RENDERAS="SECT4"Using the "NetWare Connections" WindowWhen using this window, rememberMARK=BULLET"NetWare Connections" can be used for connecting to Directory trees, to NetWare Server objects, or to bindery-based servers.The "Login" option is the same as the LOGIN /NS command line parameter, which does not run a login script for your client workstation. Use the "Permanent" option in the "NetWare Drive Connections" window to set up your client workstation drive mappings.  If you want to run a login script, your initial login should be done at the command line with the LOGIN utility. IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169 for details.PAGENUM=56 ID="BP64"To attach to more than eight servers, you should add the CONNECTIONS parameter to the NetWare DOS Requester section in your NET.CFG file. See "CONNECTIONS=number" under "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option," in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.If you are connected to a NetWare 4 network, log out of one Directory tree before logging in to another one.RENDERAS="SECT4"Viewing the "Resources" ListThe resources displayed in this list within the "NetWare Connections" window depend on the type of network you are connected to. Your IDXID="w11148"BOOK="_idx" COLLECTION="nw41" TIDREF="i2532"
context within a Directory tree in NetWare 4 also influences what is being displayed.The following are some of the possible resources that you can log in to:MARK=BULLETAn OrganizationAn Organizational UnitA NetWare Server ObjectA bindery serverUse the NET.CFG file to set or change your starting context for NetWare 4 networks. See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for more information.RENDERAS="SECT4"Setting a New PasswordIDXID="w11149"BOOK="_idx" COLLECTION="nw41" TIDREF="i3242"
You can 
modify your existing 
password by using the "Set Pass" option in the "NetWare Connection" window. Choosing the "Set Pass" button displays a dialog similar to the one in the following figure.LABEL="3-6" FLOAT="0""NetWare Set Password" DialogFILEREF="c41ug17a.tif"PAGENUM=57 ID="BP65"RENDERAS="SECT3"NetWare Send MessageIDXID="w11150"BOOK="_idx" COLLECTION="nw41" TIDREF="i2424"
Use the "
NetWare 
Send Message" window (see IDREF="FM82650"Figure 3-7) to send a message to a user or group of users on the network.Select the resource you want to send a message to from the "Resources" list, type your message in the "Message" field, and then choose the "Send" button at the bottom of the window. LABEL="3-7" FLOAT="0"ID="FM82650""NetWare Send Message" WindowFILEREF="c41ug18a.tif"RENDERAS="SECT4"Using the "NetWare Send Message" WindowWhen using this window, remember that you must first log in to a Directory Services tree or server that contains the object that you want to send a message to.RENDERAS="SECT4"Viewing the "Resources" ListThis list within the "NetWare Send Message" window contains users and groups.Use the show or hide features (the buttons at the bottom of the window) to control the displayed resources in the "Resources" list.PAGENUM=58 ID="BP66"RENDERAS="SECT3"NetWare SettingsUse the "NetWare Settings" window (see IDREF="FM60498"Figure 3-8) to modify display options, message reception, and access to NetWare User Tools for MS Windows. Select the option you want to modify and choose "OK."LABEL="3-8" FLOAT="0"ID="FM60498""NetWare Settings" WindowFILEREF="c41ug19a.tif"RENDERAS="SECT4"Using the "NetWare Settings" WindowWhen using this window, rememberMARK=BULLETThe settings you choose in this window take effect each time you start MS Windows. These settings are retained in your NETWARE.INI, WIN.INI, and SYSTEM.INI files.NetWare User Tools for MS Windows recognizes the previous settings each time you start MS Windows.RENDERAS="SECT4"Using "NetWare Settings"Use this window toMARK=BULLETAllow or block incoming messagesSet display optionsPAGENUM=59 ID="BP67"Change the hotkey value for NetWare User Tools for MS WindowsAllow for persistent connectionsThe following table lists and explains the IDXID="w11151"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
setting IDXID="w11152"BOOK="_idx" COLLECTION="nw41" TIDREF="i4103"
options that you can assign.LABEL="3-3" PGWIDE=0 TOCENTRY="1""NetWare Settings" OptionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="25*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"OptionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11153"BOOK="_idx" COLLECTION="nw41" TIDREF="i2421"
Messages 
ReceptionIDXID="w11154"BOOK="_idx" COLLECTION="nw41" TIDREF="i2424"COLNAME=2 ROTATE="0" MOREROWS="0""Broadcasts" allows you to block or receive messages sent to your client by other network stations and servers.By default, this box is checked so that you receive broadcast messages.If you block broadcast messages, all messages sent to your station are lost. You cannot retrieve them later."Network Warnings" alerts you to the following network problems:MARK=BULLETThe NetWare VLM is not loaded.Your DOS Requester configuration is not set up correctly.Memory is insufficient to load network support.By default, this box is checked so you are notified of network problems. COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11155"BOOK="_idx" COLLECTION="nw41" TIDREF="i3438"
Print Manager DisplayCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to configure the look and content of your MS Windows Print Manager display. The following option settings are available:"Maximum Jobs" allows you to set the number of print jobs that can be stored in the Print Manager queue. MARK=BULLETDefault: 50Maximum: 250Minimum: 1"Update Seconds" allows you to select how often (in seconds) the Print Manager updates the Print Manager queue. Default: 30 Maximum: 65 Minimum: 1COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11156"BOOK="_idx" COLLECTION="nw41" TIDREF="i3300"
Permanent IDXID="w11157"BOOK="_idx" COLLECTION="nw41" TIDREF="i2323"
ConnectionsCOLNAME=2 ROTATE="0" MOREROWS="0"Prompts you to reconnect any network connection made in the previous session of MS Windows. MARK=BULLET"Restore During Startup" allows you to restore resource connections made permanent the next time you load MS Windows. Marking this option makes the "NetWare Restore Connections" window appear each time you load MS Windows."Disable Conflict Warnings" allows you to restore resource connections that conflict with current connections made before loading MS WIndows. Marking this option makes the "NetWare Restore Connections" window appear each time you load MS Windows."Restore Now" allows you to restore resource connections after MS Windows is loaded and running.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11158"BOOK="_idx" COLLECTION="nw41" TIDREF="i2745"
NetWare HotkeyCOLNAME=2 ROTATE="0" MOREROWS="0"Mark the "Enable IDXID="w11159"BOOK="_idx" COLLECTION="nw41" TIDREF="i1701"
Hotkey" checkbox to activate the "Hotkey Value" field for editing.Specifies any hotkey value you want. The default hotkey is <F6>. The hotkey value for NetWare User Tools for MS Windows takes priority over any other system setting with the same value.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11160"BOOK="_idx" COLLECTION="nw41" TIDREF="i3"
386 Enhanced DOS SessionsCOLNAME=2 ROTATE="0" MOREROWS="0""Global Drives and Paths" enables MS Windows to support global drive mappings and paths across multiple DOS box sessions. To enable global drive mapping support, add the following heading and command in the MS Windows SYSTEM.INI file: MOREINFO="NONE"[NETWARE]  NWSharehandles=trueCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11161"BOOK="_idx" COLLECTION="nw41" TIDREF="i3817"
Resource DisplayCOLNAME=2 ROTATE="0" MOREROWS="0"MARK=BULLET"Bindery" displays available bindery servers in the "Resources" list."Personal" displays available Personal NetWare servers in the "Resources" list."DS Object" displays available NetWare Directory Services objects in the "Resources" list."DS Containers" displays available NetWare Directory Services containers in the "Resources" list."Name Sort" displays resources sorted by their name."Type Sort" displays resources sorted by their type.PAGENUM=61 ID="BP68"RENDERAS="SECT3"User-Defined 
Buttons 1 and 2IDXID="w11162"BOOK="_idx" COLLECTION="nw41" TIDREF="i4731"
The 1 and 2 buttons on the right side of the menu bar allow you to load additional programs within NetWare IDXID="w11163"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
User Tools for MS Windows. This can be very useful for accessing the MS Windows File Manager and Print Manager IDXID="w11164"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
applications.IDXID="w11165"BOOK="_idx" COLLECTION="nw41" TIDREF="i4108"RENDERAS="SECT4"Setting the User-Defined ButtonsTo define the user-defined buttons, complete the following steps.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Open the "User Defined Path" dialog.You can open this dialog in either of the following two ways:
MARK=BULLETIf no previous path is defined, choose the 1 or 2 button or pressMOREINFO="NONE" <Alt>+<1> or MOREINFO="NONE"<Alt>+<2>.If a previous path is defined, pressMOREINFO="NONE" <Alt>+<1> or MOREINFO="NONE"<Alt>+<2>.PERFORMANCE="REQUIRED"Type the path and program filename in the "Command Line" field.For example, to define the MS Windows File Manager to load from NetWare User Tools, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\windows\winfile.exePERFORMANCE="REQUIRED"Choose "OK."An icon for the particular application appears in the button bar. RENDERAS="SECT4"Changing the User-Defined PathIDXID="w11166"BOOK="_idx" COLLECTION="nw41" TIDREF="i4731"
Once a path is set, you need to use the quick key to access the "User Defined Path" dialog.MOREINFO="NONE" (Press <Alt>+<1> or MOREINFO="NONE"<Alt>+<2>.)RENDERAS="SECT2"Accessing and Changing Directory and File AttributesIDXID="w11167"BOOK="_idx" COLLECTION="nw41" TIDREF="i334"
Follow these IDXID="w11168"BOOK="_idx" COLLECTION="nw41" TIDREF="i4103"
steps to access and change network file and directory attributes.PAGENUM=62 ID="BP69"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Open the MS Windows File Manager.PERFORMANCE="REQUIRED"Select the file that you want to set attributes for.PERFORMANCE="REQUIRED"From the "File" menu, choose "Properties."PERFORMANCE="REQUIRED"From the "Properties" window, choose "NetWare."The following figure shows the "Properties" window.LABEL="3-9" FLOAT="0"File and Directory "Properties" WindowFILEREF="c41ug20a.tif"PERFORMANCE="REQUIRED"Select the appropriate check box to enable or disable an attribute.RENDERAS="SECT3"Using the "File and Directories Property" windowWhen using the "IDXID="w11169"BOOK="_idx" COLLECTION="nw41" TIDREF="i1468"
Properties" option, remember that you can set IDXID="w11170"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
properties for network files and directories only. IDXID="w11171"BOOK="_idx" COLLECTION="nw41" TIDREF="i3577"
Properties for directories and files on local drives are set within the MS Windows File Manager.The following table lists the IDXID="w11172"BOOK="_idx" COLLECTION="nw41" TIDREF="i334"
attributes that you can assign.LABEL="3-4" PGWIDE=0 TOCENTRY="1" File and Directory Property AttributesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"AttributeCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11173"BOOK="_idx" COLLECTION="nw41" TIDREF="i842"
Copy InhibitCOLNAME=2 ROTATE="0" MOREROWS="0"(Macintosh clients only) Prevents users from copying a file.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11174"BOOK="_idx" COLLECTION="nw41" TIDREF="i977"
Delete InhibitCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents users from deleting a file.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11175"BOOK="_idx" COLLECTION="nw41" TIDREF="i3642"
Purge ImmediateCOLNAME=2 ROTATE="0" MOREROWS="0"Notifies NetWare to purge a file when it is deleted.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11176"BOOK="_idx" COLLECTION="nw41" TIDREF="i3775"
Rename InhibitCOLNAME=2 ROTATE="0" MOREROWS="0"Prevents users from renaming a file.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11177"BOOK="_idx" COLLECTION="nw41" TIDREF="i4130"
ShareableCOLNAME=2 ROTATE="0" MOREROWS="0"Allows users simultaneous access to a file.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w11178"BOOK="_idx" COLLECTION="nw41" TIDREF="i4550"
TransactionalCOLNAME=2 ROTATE="0" MOREROWS="0"Indicates that a file is protected by the Transaction Tracking SystemTM software.PAGENUM=63 ID="BP70"RENDERAS="SECT2"Optimizing the NetWare Client Software for MS WindowsYou can optimize the NetWare Client software for MS Windows under specific conditions by following a few simple procedures discussed in the following table:LABEL="3-5" PGWIDE=1 TOCENTRY="1" Optimizing the NetWare Client Software for MS WindowsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="21*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ConditionCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Specifying to display parent dots in list boxes for file and directory navigationCOLNAME=2 ROTATE="0" MOREROWS="0"The NetWare server doesn't have directory entries for "." and ".." as DOS does.To see "." and ".." in directory listings, set the value for this parameter to "on." For example:MOREINFO="NONE"SHOW DOTS=ONThis parameter is supported only by NetWare 2.11 and later.COLNAME=1 ROTATE="0" MOREROWS="0"Disabling the NetWare logo at MS Windows startupCOLNAME=2 ROTATE="0" MOREROWS="0"Add the following line to the NETWARE.INI file in the MS Windows directory:MOREINFO="NONE" DISABLELOGO=ONCOLNAME=1 ROTATE="0" MOREROWS="0"Minimizing the NetWare User Tools window when not in useCOLNAME=2 ROTATE="0" MOREROWS="0"Use the following procedure to set up NetWare User Tools for minimizing when not in use:1. Select the "NetWare User Tools" icon.2. From the Program Manager "File" menu, choose "Properties."3. Check the "Run Minimized" box and then choose "OK."4. Open the "NetWare User Tools" window. 5. To minimize, choose the "Close" option from the "Control- menu" box.PAGENUM=64 ID="BP71"RENDERAS="SECT1"ID="FM17027"Exiting NetWare User Tools for MS WindowsTo exit the NetWare User Tools for MS Windows, do one of the following:MARK=BULLETChoose the "Exit" button from the menu bar.Press MOREINFO="NONE"<Alt>+<X> or <Alt>+<F4>.Choose the "System Menu" box (the box in the upper-left corner of NetWare User Tools for MS Windows). Choose "Close" from the menu that appears.PAGENUM=65 ID="BP72"RENDERAS="SECT1"Additional InformationRENDERAS="SECT2"For NetWare 2 and NetWare 3COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare binderyCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Bindery" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Network Drive Mapping" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare file system (directory structure)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Directory Structure" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare volumesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Volume" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network printingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Printing" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print queuesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Print queue" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print serversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Print server" in NetWare 3.12 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"PrintersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="concepts" COLLECTION="nw312"Printers" in NetWare 3.12 ConceptsRENDERAS="SECT2"For NetWare 4COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory tree" in NetWare 4 ConceptsChapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," in Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare Directory ServicesCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," in Introduction to NetWare Directory ServicesCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Drive mapping" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare file system (directory structure)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory structure" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare volumesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Volume" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Network printingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Printing" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print queuesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print queue" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Print serversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print server" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"PrintersCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Printer" in NetWare 4 ConceptsPAGENUM=66 ID="BP73"LABEL=""PAGENUM=67 ID="BP74"Installation, Login, and SetupRENDERAS="SECT1"OverviewThe NetWare® ClientTM software allows you to connect to NetWare networks and servers running the NetWare 2, NetWare 3TM, and NetWare 4TM families of network operating systems as well as Personal NetWareTM workgroups.After you install a NetWare server, you can begin installing the NetWare Client software on client workstations. You need to install the NetWare client software on at least one client workstation to connect to the network or a server before you can begin creating users accounts, network directories, print queues, etc.RENDERAS="SECT1"ContentsThis section is divided into seven chapters, with the following information discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"ChapterCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"To help prepare the hardware, determine your network board settings, and prepare the client workstation software for installation of the NetWare Client softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50081"Chapter 4, "Preparing to Install or Upgrade the NetWare Client Software" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM50081"69COLNAME=1 ROTATE="0" MOREROWS="0"To guide you through the steps for installing the NetWare Client software for DOS and MS Windows workstations. Also provides information about what happens during installationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM93380"89COLNAME=1 ROTATE="0" MOREROWS="0"To help prepare the hardware and software necessary for installing diskless workstations on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33961"Chapter 6, "Setting Up Remote Client Workstations"  COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM33961"133COLNAME=1 ROTATE="0" MOREROWS="0"To guide you through basic steps for modifying your NET.CFG file to simplify login to a NetWare networkCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41619"Chapter 7, "Setting Up NetWare Client Workstations to Log In" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM41619"161COLNAME=1 ROTATE="0" MOREROWS="0"To provide procedures for logging in to the network from DOS and MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM57667"169COLNAME=1 ROTATE="0" MOREROWS="0"To set up files and network directories on client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86864"Chapter 9, "Setting Up and Managing Network Drives" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM86864"177COLNAME=1 ROTATE="0" MOREROWS="0"To set up printing on client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94060"Chapter 10, "Setting Up Client Workstation Printing" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM94060"193LABEL="4"PAGENUM=69 ID="BP75"ID="FM50081"Preparing to Install or Upgrade the NetWare Client SoftwareRENDERAS="SECT1"OverviewThis chapter explains the task you need to complete before running the NetWare® ClientTM installation program or manually installing the NetWare Client software.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM73852"Preparing Client Workstations COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM73852"70COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74874"Preparing the NetWare Client Installation Software  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74874"76COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55035"Creating Client Installation Diskettes from CD-ROM  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55035"76COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31237"Setting Up for Installation from a Network Directory COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM31237"78COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM70549"Editing the INSTALL.CFG File COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM70549"84COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78877"Using a Third-Party ODI LAN Driver COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78877"86COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM48065"Upgrading Your IPX Driver to ODI COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM48065"86RENDERAS="SECT1"IntroductionProper 
preparation is important to the ease and success of your installation or upgrade. Preparation ensures that your hardware and software are configured properly and that you have the necessary information to successfully complete all of your client workstation installations or upgrades.The complete hardware and software setup for client workstations might require you to complete one or more of the following tasks:MARK=BULLETIDREF="FM73852"Preparing Client Workstations PAGENUM=70 ID="BP76"IDREF="FM74874"Preparing the NetWare Client Installation Software IDREF="FM55035"Creating Client Installation Diskettes from CD-ROM IDREF="FM31237"Setting Up for Installation from a Network Directory IDREF="FM70549"Editing the INSTALL.CFG File RENDERAS="SECT1"ID="FM73852"Preparing 
Client 
WorkstationsPreparing 
client workstations for installing or upgrading the NetWare Client software requires hardware and software setup on each client workstation that you want to use on the network.The complete setup for preparing workstations requires the following:MARK=BULLETIDREF="FM50775"Setting Up Workstation Hardware IDREF="FM35122"Setting Up the Network Board IDREF="FM18804"Setting Up Workstation Software If you are upgrading from a previous version of the NetWare Client software, your current workstation hardware and software configuration should be sufficient. IDREF="FM74874"See "Preparing the NetWare Client Installation Software" on page 76 to continue preparing for installation.Otherwise, continue with the next section.RENDERAS="SECT2"ID="FM50775"Setting Up Workstation 
HardwareThe following IDXID="w11179"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
checklist can help you determine what hardware setup you need for installing the NetWare Client software.MARK=CHECKBOXAn IBM PC (or compatible) with an XT*, AT*
, 8088, 286, 386, or 486 (SX, SLC, DX, etc.) processorIDXID="w11180"BOOK="_idx" COLLECTION="nw41" TIDREF="i2383"
A hard drive or a floppy drive and diskette with the following amount of available 
disk space:MARK=BULLETDOS only:1.2 MB DOS and MS Windows: 4 MBPAGENUM=71 ID="BP77"The NetWare Client installation program sends an error message warning you that you have insufficient disk space if the total available disk space is below 5 MB when installing files for both DOS and MS Windows.A network board installed in your client workstationMARK=BULLETRecord the board settings to use during installation. IDREF="FM35122"See "Setting Up the Network Board" on page 71 for more information on how to determine and set the board settings. For information on installing the network board, see the manufacturer's documentation.IDXID="w11181"BOOK="_idx" COLLECTION="nw41" TIDREF="i562"
Network 
cablingMARK=BULLETEach type of network board requires unique cabling. See the manufacturer's documentation packaged with your network board for requirements.Token ring network boards require a cable connection to the MAU before installing the NetWare Client software. Otherwise, the NTR2000 driver will not load.(Optional) If you are installing a remote boot client workstation, a Novell®
 (or compatible) Remote Reset PROM inserted in each network board in all client workstations that will boot remotely.IDREF="FM33961"See Chapter 6, "Setting Up Remote Client Workstations," on page 133 for more information.RENDERAS="SECT2"ID="FM35122"Setting Up the 
Network BoardWhen 
you install the 
network board, it must be configured. Configuring the network board involves assigning particular values to certain settings on the board. These settings allow the network board to communicate with the workstation hardware and networking software.In most cases, you should leave your network board set to the factory default settings. If you need to change the default settings, see the manufacturer's documentation.Some network boards require you to configure the board by setting switches on the board manually, before you place it in the bus slot located in the motherboard of your workstation.Other boards have a software program that allows you to configure the board after you have placed it inside your workstation.PAGENUM=72 ID="BP78"See the manufacturer's documentation for information about configuring your particular network boards.IDXID="w11182"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
You can obtain setting information for your network board by using the following procedures.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"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 workstation's setup or reference program. This program lists the values for your network board settings.COLNAME=1 ROTATE="0" MOREROWS="0"ISA network boardsCOLNAME=2 ROTATE="0" MOREROWS="0"Look at the network board itself to obtain the specific settings. The documentation provided with your network board will direct you where to find each setting value.COLNAME=1 ROTATE="0" MOREROWS="0"PCI Local Bus network boardsCOLNAME=2 ROTATE="0" MOREROWS="0"Run the workstation's setup or reference program. This program lists the values for your network board settings.If you have a network connection already, type "NVER" in the PUBLIC directory at the command line to view board settings.It is important that you keep a record of the settings you use to configure the network boards, because the NetWare Client installation program requires specific information about the network board installed in each client workstation.IDXID="w11183"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
Before loading the client installation program, record the values for the following settings:MARK=BULLETIDXID="w11184"BOOK="_idx" COLLECTION="nw41" TIDREF="i1638"
Hardware interruptIn most cases, you can use IRQ3 or IRQ5 for your network board if these are not already used by COM2 and LPT2. If neither IRQ3 nor IRQ5 is available, see the manufacturer's documentation.The following table shows the IRQ settings that are commonly used by other devices, and the settings that might be available.COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IRQCOLNAME=2 ROTATE="0" MOREROWS="0"DeviceCOLNAME=3 ROTATE="0" MOREROWS="0"IRQCOLNAME=4 ROTATE="0" MOREROWS="0"DeviceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0COLNAME=2 ROTATE="0" MOREROWS="0"Timer output 0COLNAME=3 ROTATE="0" MOREROWS="0"8COLNAME=4 ROTATE="0" MOREROWS="0"Real time clockCOLNAME=1 ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"KeyboardCOLNAME=3 ROTATE="0" MOREROWS="0"9COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"EGA/VGACOLNAME=3 ROTATE="0" MOREROWS="0"10COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"COM2COLNAME=3 ROTATE="0" MOREROWS="0"11COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"COM1COLNAME=3 ROTATE="0" MOREROWS="0"12COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"LPT2COLNAME=3 ROTATE="0" MOREROWS="0"13COLNAME=4 ROTATE="0" MOREROWS="0"Co-processorCOLNAME=1 ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"DisketteCOLNAME=3 ROTATE="0" MOREROWS="0"14COLNAME=4 ROTATE="0" MOREROWS="0"Hard diskCOLNAME=1 ROTATE="0" MOREROWS="0"7COLNAME=2 ROTATE="0" MOREROWS="0"LPT1COLNAME=3 ROTATE="0" MOREROWS="0"15COLNAME=4 ROTATE="0" MOREROWS="0"AvailablePAGENUM=73 ID="BP79"If you specify an interrupt for the network board that is already being used by another device, you can still install the network board but the network software will not run successfully. IDXID="w11185"BOOK="_idx" COLLECTION="nw41" TIDREF="i413"
Base I/O portIDXID="w11186"BOOK="_idx" COLLECTION="nw41" TIDREF="i1998"
The base input/output port is a channel used by the network board to transfer information to the CPU. Each hardware device included in your client workstation must have a different base I/O port setting. For more information, see the manufacturer's documentation.The following table shows a list of standard I/O ports and the devices that commonly use them. If a workstation does not have any one of these devices, the I/O port given in the table for that device might be available for other use.COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="4*"COLNAME=4 COLWIDTH="9*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"I/O PortCOLNAME=2 ROTATE="0" MOREROWS="0"DeviceCOLNAME=3 ROTATE="0" MOREROWS="0"I/O PortCOLNAME=4 ROTATE="0" MOREROWS="0"DeviceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"1F0COLNAME=2 ROTATE="0" MOREROWS="0"AT disk controllerCOLNAME=3 ROTATE="0" MOREROWS="0"300COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"200COLNAME=2 ROTATE="0" MOREROWS="0"Game controller/joystick (200-20F)COLNAME=3 ROTATE="0" MOREROWS="0"320COLNAME=4 ROTATE="0" MOREROWS="0"XT hard disk interfaceCOLNAME=1 ROTATE="0" MOREROWS="0"220COLNAME=2 ROTATE="0" MOREROWS="0"Novell network keycardCOLNAME=3 ROTATE="0" MOREROWS="0"340COLNAME=4 ROTATE="0" MOREROWS="0"AvailableCOLNAME=1 ROTATE="0" MOREROWS="0"240COLNAME=2 ROTATE="0" MOREROWS="0"AvailableCOLNAME=3 ROTATE="0" MOREROWS="0"360COLNAME=4 ROTATE="0" MOREROWS="0"LPT1 (378-37F)COLNAME=1 ROTATE="0" MOREROWS="0"260COLNAME=2 ROTATE="0" MOREROWS="0"LPT2 (278-27F)COLNAME=3 ROTATE="0" MOREROWS="0"380COLNAME=4 ROTATE="0" MOREROWS="0"SLDC/Sec Bi-Sync interface (380-38C)COLNAME=1 ROTATE="0" MOREROWS="0"280COLNAME=2 ROTATE="0" MOREROWS="0"LCD display on WYSE* 2108 PCCOLNAME=3 ROTATE="0" MOREROWS="0"3A0COLNAME=4 ROTATE="0" MOREROWS="0"Primary Bi-Sync interface (3A0-3A9);  Monochrome display (3B0-3BB)COLNAME=1 ROTATE="0" MOREROWS="0"2A0COLNAME=2 ROTATE="0" MOREROWS="0"AvailableCOLNAME=3 ROTATE="0" MOREROWS="0"3C0COLNAME=4 ROTATE="0" MOREROWS="0"EGA display control (3C0-3CF);  CGA display control (3D0-3DF)COLNAME=1 ROTATE="0" MOREROWS="0"2C0COLNAME=2 ROTATE="0" MOREROWS="0"AvailableCOLNAME=3 ROTATE="0" MOREROWS="0"3E0COLNAME=4 ROTATE="0" MOREROWS="0"COM3 (3E8-3EF);  Diskette controller (3F0-3F7);  COM1 (3F8-3FF)COLNAME=1 ROTATE="0" MOREROWS="0"2E0COLNAME=2 ROTATE="0" MOREROWS="0"COM4 GPIB-Adapter 0 (2E1);  COM2 Information collection from external devicesCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"PAGENUM=74 ID="BP80"IDXID="w11187"BOOK="_idx" COLLECTION="nw41" TIDREF="i414"
Base IDXID="w11188"BOOK="_idx" COLLECTION="nw41" TIDREF="i112"
Memory AddressThe base memory address specifies the location in memory that the network board uses to exchange information across the network. It is also known as the RAM start address.Some network boards do not use RAM; if your network board is one of these, you do not need to specify a value for this setting. The base memory address often available for the network board is D800 (sometimes written as D8000). If you use a memory manager (for example, EMM386 or QEMM*), you might need to exclude this base memory address if the memory manager cannot detect automatically that the memory address is used by the network board.IDXID="w11189"BOOK="_idx" COLLECTION="nw41" TIDREF="i2363"
Media frame typeAll client workstations and servers using a single network address must use the same frame type. If you have a network connection already, read the frame type parameter for the LINK DRIVER option in your NET.CFG file.PAGENUM=75 ID="BP81"In NetWare 2 and NetWare 3TM, Novell Ethernet LAN drivers defaulted to the Ethernet 802.3 frame type. In NetWare 4TM, the default frame type is 802.2 for Ethernet ODI LAN drivers.  If you use the Ethernet 802.2 frame type on client workstations, the workstations cannot connect to a network expecting the Ethernet 802.3 frame type. Place the frame types (Ethernet 802.2 and Ethernet 802.3) in the same order on both the server and client workstations to eliminate a potential conflict.For information on frame types supported by common network board drivers, see "FRAME frame_type" under "BOOK="ws_d2enu" COLLECTION="nw41"Link Driver Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference.Other settingsThere are other parameters unique to the network board installed in your client workstation. See the documentation provided with your network board for more information.For information on ODI LAN driver parameters for your network boards, see "BOOK="ws_d2enu" COLLECTION="nw41"Link Driver Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference.RENDERAS="SECT2"ID="FM18804"Setting Up IDXID="w11190"BOOK="_idx" COLLECTION="nw41" TIDREF="i4841"
Workstation 
Software Preparing 
workstation software requires 
setup on each client workstation that you want to use on the network. If you are upgrading your client software from a previous version of the NetWare Client software, your current workstation hardware and software configuration should be sufficient. In this case, go to IDREF="FM74874""Preparing the NetWare Client Installation Software" on page 76 to continue preparing for installation.The following checklist can help you determine what preparations you need to make for installing the NetWare Client software.MARK=CHECKBOXA running IDXID="w11191"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
copy of Novell DOSTM 7 or later, DR DOS® 5 or later, MS-DOS 3 or later, or PC-DOS 3 or later.(Conditional: if using MS Windows) A copy of IDXID="w11192"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
MS Windows 3.x or Windows for Workgroups (WFWG) 3.11 installed on your client workstation.(Optional) If you have DOS and MS Windows client workstations running an IPX.COM file generated by DOSGEN or SHGEN, upgrade your dedicated IPX driver to ODI. IDREF="FM48065"See "Upgrading Your IPX Driver to ODI" on page 86 for instructions.PAGENUM=76 ID="BP82"RENDERAS="SECT1"ID="FM74874"Preparing the 
NetWare Client Installation SoftwarePreparing the IDXID="w11193"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
NetWare Client 
installation software depends greatly on the current state and condition of your client workstations and NetWare Client software packaging.Complete one or more of the following IDXID="w11194"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
tasks for IDXID="w11195"BOOK="_idx" COLLECTION="nw41" TIDREF="i650"
preparing the installation software:MARK=BULLETIf your client software is on CD-ROM, go to one of the following sections:MARK=BULLETTo prepare for installing a new client workstation from diskettes, IDREF="FM55035"see "Creating Client Installation Diskettes from CD-ROM" on page 76 for more information.To prepare for installing existing client workstations from a network directory, IDREF="FM31237"see "Setting Up for Installation from a Network Directory" on page 78 for more information.If your client software is on diskette, IDREF="FM31237"see "Setting Up for Installation from a Network Directory" on page 78 to prepare for installing from a network directory.If your workstation is new and does not have any NetWare Client software installed, IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 to install to a new workstation.If you need to modify the installation configuration file for your particular network, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.If you are using a current copy of compatible third-party ODI LAN drivers, IDREF="FM78877"see "Using a Third-Party ODI LAN Driver" on page 86 for more information.RENDERAS="SECT1"ID="FM55035"Creating Client Installation IDXID="w11196"BOOK="_idx" COLLECTION="nw41" TIDREF="i876"
Diskettes from IDXID="w11197"BOOK="_idx" COLLECTION="nw41" TIDREF="i608"
CD-ROMIDXID="w11198"BOOK="_idx" COLLECTION="nw41" TIDREF="i1136"IDXID="w11199"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"You can create client diskettes from a workstation either by using a CD-ROM drive connected directly to the workstation as a DOS device, or by mapping a drive to a server with the NetWare 4 Operating System CD-ROM mounted as a NetWare volume.PAGENUM=77 ID="BP83"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Format four high-density diskettes using the DOS FORMAT command.PERFORMANCE="REQUIRED"(Local workstation) Install the CD-ROM drive as a DOS device according to manufacturer's instructions.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Go to the drive corresponding to the CD-ROM.PERFORMANCE="REQUIRED"Change to the CLIENT\DOSWIN directory.PERFORMANCE="REQUIRED"Go to Step 4.PERFORMANCE="REQUIRED"(NetWare volume) If you set up the CD-ROM as a network device, complete the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Map a drive to 
CD-ROM_volume:PUBLIC\CLIENT\DOSWIN.PERFORMANCE="REQUIRED"Change to the drive letter mapped to 
CD-ROM_volume:PUBLIC\CLIENT\DOSWIN.PERFORMANCE="REQUIRED"Continue with Step 4.PERFORMANCE="REQUIRED"(Conditional: For NetWare 3.12 and 4 only. If you are installing for any other version, skip to Step 6.) Set the "nwlanguage" 
IDXID="w11200"BOOK="_idx" COLLECTION="nw41" TIDREF="i4103"
environment variable by typing the following at the command line: 
FORMAT="LINESPECIFIC"MOREINFO="NONE"set nwlanguage=language MOREINFO="NONE"<Enter>Replace 
language with the appropriate language found in the NLS subdirectory under CLIENT\DOSWIN. PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"makedisk drive_letterMOREINFO="NONE": <Enter>Replace 
drive_letter with the diskette drive letter into which you are inserting the empty formatted diskettes. For example, type either
FORMAT="LINESPECIFIC"MOREINFO="NONE"makedisk a: MOREINFO="NONE"<Enter>
PAGENUM=78 ID="BP84"or
FORMAT="LINESPECIFIC"MOREINFO="NONE"makedisk b: MOREINFO="NONE"<Enter>The MAKEDISK utility copies the NetWare Client installation files from the CD-ROM directory to the diskettes. It prompts you to insert new formatted diskettes as necessary.PERFORMANCE="REQUIRED"Label each diskette with one of the following names:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="18*"COLNAME=2 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"Volume LabelVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK2COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_2COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_3COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK4COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_4COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCOLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_5PERFORMANCE="REQUIRED"Either use the diskettes to install the NetWare Client software on your workstation or continue preparing the installation software by going to one of the following sections:
MARK=BULLETTo prepare for installing from a network directory, IDREF="FM31237"see "Setting Up for Installation from a Network Directory" on page 78 for more information.To modify the installation configuration file for your particular setup, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.To use the NetWare Client installation program, IDREF="FM93380"see Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for information.RENDERAS="SECT1"ID="FM31237"Setting Up for 
Installation from a Network DirectorySetting up a NetWare server for running the installation program from a IDXID="w11201"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
network directory requires setup on an existing NetWare server and each client workstation you want to use on the network.PAGENUM=79 ID="BP85"This section applies only to client workstations that already have a previous version of the NetWare Client software installed. If you are installing a new DOS or MS Windows client workstation, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.The complete network setup for the client installation requires you to complete the following tasks:MARK=BULLETIDREF="FM27434"Copying NetWare Client Files to a Network Directory IDREF="FM28913"Mapping a Network Drive for Installation RENDERAS="SECT2"PrerequisitesThe following checklist can help you set up a network server and your client workstation for installing the NetWare Client software from a network directory. It is the quickest and easiest way to upgrade your NetWare Client software. MARK=CHECKBOXA previous version of the NetWare Client software must be running on your client workstations.A copy of the NetWare Client software for DOS and MS Windows must exist on a network server.The NetWare server installation program has features to copy these files, which should be copied to the PUBLIC\CLIENT\DOSWIN directory on volume SYS:.IDREF="FM27434"See "Copying NetWare Client Files to a Network Directory" on page 80 for more information.You must be logged in to a NetWare server.IDREF="FM57667"see Chapter 8, "Logging In from a NetWare Client Workstation," on page 169 for more information.Your client workstation must have a drive mapped to the PUBLIC\CLIENT\DOSWIN directory on volume SYS:.IDREF="FM28913"See "Mapping a Network Drive for Installation" on page 83 for more information.PAGENUM=80 ID="BP86"RENDERAS="SECT2"ID="FM27434"Copying NetWare 
Client 
Files to a Network DirectoryDepending on the media available, you can IDXID="w11202"BOOK="_idx" COLLECTION="nw41" TIDREF="i846"
copy the NetWare Client software to a 
network directory in one of the following ways:MARK=BULLETIDREF="FM40693"Using the INSTALL.NLM at the NetWare Server IDREF="FM73518"Copying Directly from the CD-ROM IDREF="FM90881"Copying Directly from Diskettes RENDERAS="SECT3"ID="FM40693"Using the INSTALL.NLM at the NetWare ServerThe NetWare Client software for DOS and MS Windows is usually copied to the PUBLIC directory during installation of NetWare 3.12 and NetWare 4TM servers. IDREF="FM73518"See "Copying Directly from the CD-ROM" on page 80 for other NetWare versions.If you are connecting to a NetWare 3.12 server, see BOOK="install" COLLECTION="nw312"Installation and Upgrade for details on using the server installation program.If you are connecting to a NetWare 4 network, see BOOK="instlenu" COLLECTION="nw41"Installation for details on using the server installation program.RENDERAS="SECT3"ID="FM73518"Copying Directly from the CD-ROMPERFORMANCE="REQUIRED"Make a subdirectory named CLIENT\DOSWIN under SYS:PUBLIC for the client files.PERFORMANCE="REQUIRED"Install the CD-ROM drive as a DOS device according to manufacturer's instructions.PERFORMANCE="REQUIRED"Copy files from the CLIENT\DOSWIN directory on the CD-ROM to SYS:PUBLIC by typing either
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY source_drive:path destination_drive:path /s /e /c MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY source_drive:path destination_drive:path /s /e MOREINFO="NONE"<Enter>
PAGENUM=81 ID="BP87"Do not use the DOS COPY command for this procedure. It is important that the directory structure within each subdirectory is maintained. Use the DOS XCOPY or NetWare NCOPY command to complete this procedure.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY D:CLIENT\DOSWIN\ H:\PUBLIC\CLIENT\DOSWIN /s /e /c MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY D:CLIENT\DOSWIN\ H:\PUBLIC\CLIENT\DOSWIN /s /e MOREINFO="NONE"<Enter>You can also set up your CD-ROM drive as a volume on your network. This allows you to run the client installation programs directly from the subdirectories under CLIENT on the CD-ROM.  If you are connecting to a NetWare 3TM network, see 
BOOK="install" COLLECTION="nw312"Installation and Upgrade for information.  If you are connecting to a NetWare 4 network, see BOOK="superenu" COLLECTION="nw41"Supervising the Network for information.PERFORMANCE="REQUIRED"Continue preparing the installation program by going to one of the following sections:
MARK=BULLETTo prepare for installing from a network directory, IDREF="FM28913"see "Mapping a Network Drive for Installation" on page 83 for more information.To modify the installation configuration file for your particular setup, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.RENDERAS="SECT3"ID="FM90881"Copying Directly from DiskettesPERFORMANCE="REQUIRED"Make a subdirectory called CLIENT\DOSWIN under SYS:PUBLIC for the client files.PERFORMANCE="REQUIRED"Copy the files from the following client diskettes to the CLIENT\DOSWIN directory:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="18*"COLNAME=2 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"Volume LabelVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK2COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_2COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_3COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK4COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_4COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCOLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_5PAGENUM=82 ID="BP88"PERFORMANCE="REQUIRED"Type either
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY source_drive:path destination_drive:path /s /e /c MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY source_drive:path destination_drive:path /s /e MOREINFO="NONE"<Enter>Do not use the DOS COPY command for this procedure. It is important that the directory structure within each subdirectory is maintained. Use the DOS XCOPY or NetWare NCOPY command to complete this procedure.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY A: H:\PUBLIC\CLIENT\DOSWIN /s /e /cMOREINFO="NONE" <Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY A: H:\PUBLIC\CLIENT\DOSWIN /s /e MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Continue preparing the installation program by going to one of the following sections:
MARK=BULLETTo prepare for installing from a network directory, IDREF="FM28913"see "Mapping a Network Drive for Installation" on page 83 for more information.To modify the installation configuration file for your particular setup, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.PAGENUM=83 ID="BP89"RENDERAS="SECT2"ID="FM28913"Mapping a 
Network 
Drive for InstallationMap a drive to the volume and directory containing the NetWare Client files on each client workstation that you want to run the installation program on.The volume and directory are SYS:PUBLIC\CLIENT\DOSWIN for DOS and MS Windows.The following procedure shows you how to map a drive to the appropriate volume and directory.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Map the next network drive to SYS:PUBLIC by typing FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:PUBLICMOREINFO="NONE" <Enter>This mapping might already be set up as a search drive in a login script for your client workstation. Use the MAP utility to view a list of existing drive mappings. If a drive mapping already exists for the SYS:PUBLIC directory, then proceed to Step 2.PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G:MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Change to the CLIENT\DOSWIN directory under SYS:PUBLIC for the client files by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD CLIENT\DOSWIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Either continue preparing the installation program or begin installing the client software by going to one of the following sections:
MARK=BULLETTo modify the installation configuration file for your particular setup, IDREF="FM70549"see "Editing the INSTALL.CFG File" on page 84 for more information.To use the NetWare Client installation program, IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.PAGENUM=84 ID="BP90"RENDERAS="SECT1"ID="FM70549"Editing the IDXID="w11203"BOOK="_idx" COLLECTION="nw41" TIDREF="i1837"
INSTALL.CFG FileYou can customize the installation program software for DOS and MS Windows to suit your particular networking environment. You should edit the [REQUESTER] section of the INSTALL.CFG file before installing the NetWare Client software on multiple client workstations with similar NET.CFG files.The NET.CFG file is a configuration file that contains section headings and options that deviate from the established defaults of the NetWare Client software. Use entries in the NET.CFG file to change the client workstation's network environment or configuration.For more details on how to edit or create a NET.CFG file, see Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference.RENDERAS="SECT2"Modifying the [REQUESTER] section in the INSTALL.CFG FileThe INSTALL.CFG file is found on CLASS=DISKNetWare Client for DOS and MS Windows Disk 1 at the root. The default configuration for the [REQUESTER] section includes a line for the FIRST NETWORK DRIVE and NETWARE PROTOCOL parameters only.You need to edit the INSTALL.CFG file to add lines for other settings under the NetWare DOS RequesterTM option heading. A sample of the [REQUESTER] section in the INSTALL.CFG file is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"[REQUESTER]
  first network drive = f
  netware protocol = nds bindRENDERAS="SECT2"Suggested Modifications to the [REQUESTER] SectionMake the following modifications for your particular network environment when applicable.PAGENUM=85 ID="BP91"RENDERAS="SECT3"Change in First Network DriveIn previous versions of the NetWare ClientTM software, the first network drive was always the first drive letter not reserved for local use. This setting was made with the DOS LASTDRIVE parameter in the CONFIG.SYS file. Because the NetWare DOS RequesterTM software is a redirector on the back end of DOS, it requires that the LASTDRIVE=Z parameter be added to the CONFIG.SYS file. The first network drive is now set in the NET.CFG file.See "FIRST NETWORK DRIVE" under "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.The NetWare DOS Requester uses the first available DOS drive after the FIRST NETWORK DRIVE parameter set in the NET.CFG file.Consequently, client workstations which accessed, for example, a LASTDRIVE=G parameter setting in their CONFIG.SYS are used to seeing drive H: as the first network drive rather than the first drive letter.To maintain compatibility with existing batch files, you might want to add the FIRST NETWORK DRIVE = drive_letter  parameter setting under the NetWare DOS Requester heading in the NET.CFG file by typing the following lines in your INSTALL.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"[REQUESTER]
   first network drive=drive_letter
   netware protocol=nds bindOtherwise, pre-existing batch files assuming a specific first drive letter, such as drive H:, must be altered.RENDERAS="SECT3"Upgrade of the NetWare DOS RequesterThe NetWare Client installation program uses overlay files (.OVL) which are compliant to specific machine types using the %MACHINE variable. Most PC- based workstations already support this variable. Nevertheless, if overlay files are unavailable for your machine type (such as many Japanese workstations), add a line for the "SHORT MACHINE TYPE" parameter for your type of client workstation.PAGENUM=86 ID="BP92"For example, to specify the machine type for an IBM, you would place the following lines in your INSTALL.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"[REQUESTER]
  short machine type=ibmThe maximum characters allowed in the name is four. See your hardware manufacturer for information about the short name for your hardware.RENDERAS="SECT1"ID="FM78877"Using a Third-Party IDXID="w11204"BOOK="_idx" COLLECTION="nw41" TIDREF="i3059"
ODI LAN DriverThe NetWare Client installation software includes drivers for most network boards. If an Open Data-Link InterfaceTM (ODI) LAN driver is not included for your network board, check the network board packaging for a diskette with a copy of the correct driver. Or contact the network board manufacturer to obtain a driver compatible with NetWare.IDXID="w11205"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
You will need a third-party ODITM LAN driver for the network board installed in your client workstation if an MLIDTM file is not provided with the NetWare Client installation software.If you want to update the LAN driver list to include the third-party driver, you should copy any LAN drivers not currently available from Novell to the CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN Drivers diskette. Copy both the .COM and .INS files for each driver.RENDERAS="SECT1"ID="FM48065"Upgrading Your IDXID="w11206"BOOK="_idx" COLLECTION="nw41" TIDREF="i1938"
IPX Driver to IDXID="w11207"BOOK="_idx" COLLECTION="nw41" TIDREF="i3059"
ODIIf your client workstations are using a IDXID="w11208"BOOK="_idx" COLLECTION="nw41" TIDREF="i958"
dedicated IPXTM driver, you should upgrade to an IDXID="w11209"BOOK="_idx" COLLECTION="nw41" TIDREF="i3084"
Open Data-Link Interface (ODI) specification version.An ODI version of IPX gives your client workstations greater functionality by supporting multiple communication protocols.You can upgrade in two ways:MARK=BULLETUse the client installation program to upgrade during installation.If you have a copy of the NetWare 4 software package, use the WSUPGRD utility to upgrade your version of IPX prior to using the installation program. IDREF="FM28103"See Appendix B, "Using the WSUPGRD Utility," on page 307 for more information.PAGENUM=87 ID="BP93"Upgrading prior to installation makes a NetWare Client installation virtually automatic. The installation program recognizes network board settings from loaded LAN drivers which support ODI and prompts you to use the driver and settings it recognizes.When you use WSUPGRD, your versions of IPX and LAN driver are updated automatically. The virtual IPX driver for MS Windows (VIPX.386), does not fully support dedicated IPX in an MS Windows DOS box. If you want to run the NetWare Client software for MS Windows, you must upgrade to an ODI LAN driver and other software files compliant with ODI.RENDERAS="SECT1"Where to Go from HereAfter your hardware and software are prepared, you are ready to begin installation. IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 to continue.LABEL="5"PAGENUM=89 ID="BP94"ID="FM93380"Installing or Upgrading NetWare Client SoftwareRENDERAS="SECT1"OverviewThis chapter explains the procedures for installing or 
upgrading the NetWare® ClientTM software and gives a brief summary of what happens during installation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11014"Running the NetWare Client Installation ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11014"90COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM68617"What Happens during InstallationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68617"106COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29800"Installing for MS Windows for WorkgroupsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29800"111COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80903"Setting Up an MS Windows Shared Network Directory for NETX and VLM Client WorkstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80903"113COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM35338"Installing Client Workstation Files ManuallyCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM35338"116COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM45160"Loading the NetWare Client SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM45160"124COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM68406"Using Two Network BoardsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68406"125RENDERAS="SECT1"IntroductionThe NetWare Client installation program copies the 
NetWare 
DOS RequesterTM and other NetWare Client software for DOS and Microsoft (MS) Windows to specified directories on each client workstation. 
It also provides procedures for IDXID="w11210"BOOK="_idx" COLLECTION="nw41" TIDREF="i1005"IDXID="w11211"BOOK="_idx" COLLECTION="nw41" TIDREF="i1486"IDXID="w11212"BOOK="_idx" COLLECTION="nw41" TIDREF="i2061"IDXID="w11213"BOOK="_idx" COLLECTION="nw41" TIDREF="i2497" editing configuration files for your operating environment to run on NetWare.The NetWare DOS Requester and other core components of the PAGENUM=90 ID="BP95"NetWare Client software direct network requests from the client workstations to the network. After you install the NetWare Client software on your workstation, you can connect to a NetWare network and perform basic network tasks.IDREF="FM14751"See Chapter 2, "Understanding the NetWare Client Software," on page 21 to learn more about how the NetWare DOS Requester and other NetWare Client software works. Installing or upgrading the NetWare Client software requires set up on each client workstation that you want to connect to and use with NetWare networks and servers. The complete setup for client workstations that you want to upgrade or install as new requires you to complete the following tasks:MARK=BULLETIDREF="FM11014"Running the NetWare Client Installation Program(Conditional) IDREF="FM29800"Installing for MS Windows for Workgroups(Optional) IDREF="FM80903"Setting Up an MS Windows Shared Network Directory for NETX and VLM Client WorkstationsRENDERAS="SECT1"ID="FM11014"Running the NetWare Client Installation ProgramDOS and 
MS Windows 
client workstations share the same installation program. To provide for this, the installation program runs within the 
DOS environment.RENDERAS="SECT2"PrerequisitesReview the following checklist to make sure you are prepared to install NetWare Client software. MARK=CHECKBOXClose MS Windows before loading the installation program.The client installation program modifies some MS Windows files that are used when in MS Windows. Do not install from an MS Windows DOS Box.If you are installing from a network directory, make sure you have a drive mapped to SYS:PUBLIC.IDREF="FM28913"See "Mapping a Network Drive for Installation" on page 83 for details.PAGENUM=91 ID="BP96"If you are installing from diskettes, make sure you have working copies of the NetWare Client install disks.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"Volume LabelVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK2COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_2COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_3COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk CLASS=DISK4COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_4COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCOLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_5(Conditional) If you want the installation program to display in a language other than English (the default), set a DOS environment variable for NWLANGUAGE=preferred_language.Replace preferred_language with one of the following languages:MARK=BULLETDEUTSCHESPANOLFRANCAISITALIANOFor example, to specify Spanish as your preferred language, you would set NWLANGUAGE=ESPANOL.RENDERAS="SECT2"ID="FM50816"Loading the Installation ProgramFor 
brief instructions, see the Quick Reference Cards for DOS and MS Windows and the screen instructions to complete the installation.For more detailed information, continue with this section, which explains the following installation tasks:MARK=BULLETIDREF="FM22389"Selecting a Destination Directory for the NetWare Client FilesIDREF="FM61299"Updating System Files on Your WorkstationIDREF="FM11182"Installing Support for MS WindowsPAGENUM=92 ID="BP97"IDREF="FM17982"Configuring the Target Service Agent (TSA) Software for a Storage Management Services (SMS) ProgramIDREF="FM19783"Installing LAN DriversIDREF="FM59935"Copying FilesTake advantage of the useful hints about the installation program that are provided at the bottom of the screen.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Follow the appropriate set of steps to load the installation program:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Installing from DiskettesCOLNAME=2 ROTATE="0" MOREROWS="0"Installing from a Network DirectoryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"1. InsertCLASS=DISK NetWare Client for DOS and MS Windows Disk CLASS=DISK1 into a disk drive.2. Change to the letter of the floppy drive that contains the diskette.    For example, type  MOREINFO="NONE"  A: MOREINFO="NONE"<Enter>3. Type  MOREINFO="NONE"  INSTALL MOREINFO="NONE"<Enter>4. Follow the instructions on your screen.COLNAME=2 ROTATE="0" MOREROWS="0"1. From the SYS:PUBLIC directory, change to the CLIENT\DOSWIN subdirectory.    For example, type  MOREINFO="NONE"  MOREINFO="NONE"CD CLIENT\DOSWINMOREINFO="NONE" <Enter>2. Type    MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>3. Follow the instructions on your screen.The following figure shows an example of the opening screen in the installation program.
PAGENUM=93 ID="BP98"LABEL="5-1" FLOAT="0"ID="FM67195"Installation Program Opening ScreenFILEREF="c41ug39a.tif"RENDERAS="SECT2"ID="FM22389"Selecting a Destination Directory for the 
NetWare Client FilesThe 
installation program searches for the path to any existing copy of the VLM.EXE file. If the VLM.EXE file does not exist, the 
installation program automatically assigns the default path C:\NWCLIENT.If another version of the NetWare Client software is running in a different directory, replace the default with the path to that directory (see the following procedure). Otherwise, accept the default path.The client software included with this installation program is universal to all versions of NetWare.  You will not damage any previous installation of the NetWare Client software by installing this software to the default directory, even if the software already exists in another directory.RENDERAS="SECT3"ProcedureTo change the directory path of the new NetWare Client software, follow these steps:PERFORMANCE="REQUIRED"Select the directory path field in Step 1 on the installation program opening screen and press MOREINFO="NONE"<Enter>.A blinking cursor appears at the end of the path statement in the field.PERFORMANCE="REQUIRED"Edit the field for your specific target directory and press 
MOREINFO="NONE"<Enter>.
PAGENUM=94 ID="BP99"The installation program automatically jumps to Step 2 on the screen 
IDREF="FM61299"(which is explained in the procedure on page 94).RENDERAS="SECT2"ID="FM61299"Updating
 System Files on Your WorkstationTo 
allow for changes to be IDXID="w11214"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
made to your AUTOEXEC.BAT and CONFIG.SYS files, follow these steps:PERFORMANCE="REQUIRED"Select the "Allow Changes? (Y/N)" field in Step 2 on the installation program opening screen and press MOREINFO="NONE"<Enter>.A blinking cursor appears at the end of the path statement in the field.PERFORMANCE="REQUIRED"To continue type "Y" or "N" and then press 
MOREINFO="NONE"<Enter>.The installation program automatically jumps to Step 3 on the screen (which is explained on pages 
IDREF="FM18520"96 and 
IDREF="FM60777"97).If you allow for changes, the original system files are saved as AUTOEXEC.BNW and CONFIG.BNW.If you do not allow for automatic changes to these files during installation, a copy of the necessary changes is saved to the destination directory (NetWare Client directory). The files are named CONFIG.NEW and AUTOEXEC.NEW.You will be required to make these changes manually after the installation. (
IDREF="FM44545"See "Creating or Modifying Configuration Files" on page 121 for more information.)If previous versions of CONFIG.NEW and AUTOEXEC.NEW exist, the installation program overwrites them with the newer information.  You are prompted before any system files set as read-only are copied over. If you choose not to write over the read-only files, the installation program tries to save the files as CONFIG.NEW and AUTOEXEC.NEW files. If these .NEW files already exist and are set as read-only, then the installation program does not save changes to any file.RENDERAS="SECT3"Changes Made to Your AUTOEXEC.BAT FileYour path statement is modified to add the NetWare Client directory and a line is added to call the start-network batch file from the same directory.For example, if your NetWare Client directory is NWCLIENT, the modification appears as follows:PAGENUM=95 ID="BP100"FORMAT="LINESPECIFIC"MOREINFO="NONE"@CALL C:\NWCLIENT\STARTNET.BAT
PATH=C:\NWCLIENT;%PATH%RENDERAS="SECT3"Changes Made to Your CONFIG.SYS FileTwo line are added to your client workstation's CONFIG.SYS file to set the LASTDRIVE and FILES setting. The modification appears as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"FILES = 40
LASTDRIVE = ZThe FILES command is added only if the FILES setting is lower that 40 or does not previously exist.RENDERAS="SECT2"ID="FM11182"Installing Support for MS WindowsThe 
installation program copies the necessary files for running IDXID="w11215"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
Microsoft (MS) Windows on your client workstation. The default path is set to C:\WINDOWS unless the WIN.COM file is found in the DOS PATH. If the WIN.COM file is not found in the PATH, then the default setting is no MS Windows support.Accept the default path unless you are running one of the following:MARK=BULLETMS Windows from a different local directoryIDREF="FM18520"See "Modifying MS Windows Configuration Files on a Local Directory" on page 96 for more information.MS Windows from a shared network directoryThis option is available to network supervisors only.IDREF="FM60777"See "Modifying MS Windows Configuration Files on a Network Directory" on page 97 for more information.IDREF="FM80903"See "Setting Up an MS Windows Shared Network Directory for NETX and VLM Client Workstations" on page 113 for more information.MS Windows from a network directoryThis option is for updating users' personal areas.IDREF="FM60777"See "Modifying MS Windows Configuration Files on a Network Directory" on page 97 for more information.PAGENUM=96 ID="BP101"MS Windows for WorkgroupsIDREF="FM29800"See "Installing for MS Windows for Workgroups" on page 111 for more information.The NetWare Client software for MS Windows is not compatible with the client software for NetWare provided by Microsoft.  If you install MS Windows after installing the NetWare Client software, make sure to neither copy over any NetWare Client software files nor to install the NetWare networking software provided by MS Windows.RENDERAS="SECT3"ID="FM18520"Modifying MS Windows Configuration Files on a Local DirectoryTo change the directory path of your 
MS Windows directory for the new NetWare Client software, follow these steps:RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Select the "Do you wish to install support for MS Windows? (Y/N)" field in Step 3 on the installation program opening screen and press MOREINFO="NONE"<Enter>.You must type "Y" before pressing 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the "Windows Subdirectory" field in Step 3 on the screen and press 
MOREINFO="NONE"<Enter>.A blinking cursor appears at the end of the path statement in the field.PERFORMANCE="REQUIRED"Edit the field by entering your specific MS Windows directory name and press 
MOREINFO="NONE"<Enter>.
PAGENUM=97 ID="BP102"LABEL="5-2" FLOAT="0"ID="FM37805""Customize Support for MS Windows" ScreenFILEREF="c41ug45a.tif"The installation program jumps to the customize option for MS Windows. Press 
MOREINFO="NONE"<Enter> if you want to install multiple country codes for determining the date, time, and locale of client workstations other than the locale you currently have loaded.The installation program queries the system to determine which locale and country is active and copies only the necessary Unicode* tables.PERFORMANCE="REQUIRED"To continue type "Y" or "N" and then press 
MOREINFO="NONE"<Enter>.If you type "Y," the "Customize Support for MS Windows" screen appears.RENDERAS="SECT3"ID="FM60777"Modifying MS Windows Configuration Files on a Network DirectoryYou must have appropriate rights to the network directory for MS Windows. To modify MS Windows configuration files on a network directory, follow these steps:RENDERAS="SECT4"ID="FM61825"ProcedurePERFORMANCE="REQUIRED"Select the "Do you wish to install support for MS Windows? (Y/N)" field in Step 3 on the installation program opening screen and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Edit the field by typing "Y" and press 
MOREINFO="NONE"<Enter>.
PAGENUM=98 ID="BP103"The installation program jumps to the "Enter MS Windows directory" field. Skip this option and continue unless you also want to update a personal network copy of MS Windows.PERFORMANCE="REQUIRED"Select the "Highlight here and press <Enter> to customize" option and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Select the "For the Network Administrator only: Do you want to set the shared MS Windows path? (Y/N)" field on the screen and press 
MOREINFO="NONE"<Enter>.A blinking cursor appears at the end of the path statement in the field.PERFORMANCE="REQUIRED"To continue type "Y" or "N" and then press 
MOREINFO="NONE"<Enter>.If you type "Y,"
 the "Enter the path to the shared directory:" screen appears.You must have network supervisor rights and a drive mapped to the location of the shared MS Windows directory to install for a shared copy.PERFORMANCE="REQUIRED"Edit the field by entering the specific network MS Windows directory name and press 
MOREINFO="NONE"<Enter>.Because of the architectural differences between the current NetWare DOS Requester and the previous NetWare Shell software (NETX), the NETWARE.DRV and NETWARE.HLP files for both client software types are incompatible.  Before installing the NetWare Client software for MS Windows to a shared directory, create a new directory, such as "NETXDRV," in the shared MS Windows System directory. Then, copy the previous NETWARE.DRV and NETWARE.HLP files that support the NetWare Shell software (NETX) to the NETXDRV subdirectory.  Following installation of the NetWare Client software to a shared MS Windows directory, add or make the following modification to the [boot] heading in the SYSTEM.INI file for each individual client workstation running the NetWare Shell software (NETX):  Replace the line MOREINFO="NONE"network.drv=netware.drv  with MOREINFO="NONE" network.drv=*shared_MS_Windows_directoryMOREINFO="NONE"\netxdrv\ netware.drvPAGENUM=99 ID="BP104"  For example:  MOREINFO="NONE"network.drv=*f:apps\winsys\netxdrv\netware.drv  Ensure that the necessary changes to the MS Windows .INI files were made (IDREF="FM79655"See "MS Windows Configuration Files Are Modified" on page 108 for more information).  For details on where the SYSTEM directory and .INI files are located, see "BOOK="superenu" COLLECTION="nw41"Loading MS Windows onto the Network," in Chapter2 of NetWare 4 Supervising the Network.RENDERAS="SECT2"ID="FM17982"Configuring the Target Service Agent (TSA) Software for a Storage Management Services (SMS) ProgramConfiguring the 
TSA software on client workstations allows SMSTM architecture-based utilities (such as the NetWare SBACKUP utility or the NetWare NavigatorTM utility) access to workstation resources for centralized control on the network.RENDERAS="SECT3"Target Service Agent (TSA)This is a program that processes data moving between a specific target and Storage Management ServicesTM (SMS) applications, such as SBACKUP or NetWare Navigator.The SMS application, running on the host, sends requests to the TSA, whichMARK=BULLETReceives commands from the SMS application and processes them so that the target operating system can handle the request for data processingPasses the data request from the SMS application to the targetReceives the requested data from the target and returns it to the SMS application in standard SMS formatServers and client workstations running different software releases, or using different operating systems, require TSAs that are compatible with NetWare in order to communicate with SMS applications approved to work with NetWare.IDREF="FM43744"See Chapter 17, "Setting Up the Target Service Agent (TSA) Software," on page 273 for a complete description of Target Service Agents.PAGENUM=100 ID="BP105"RENDERAS="SECT3"Storage Management Services (SMS)These are services that allow data to be backed up and restored. SMS is independent of backup/restore hardware and file systems (such as DOS, OS/2*, Macintosh, MS Windows, or UNIX®).RENDERAS="SECT3"ProcedureTo configure a TSA for SMS on your client workstations, follow these steps:PERFORMANCE="REQUIRED"Select the "Configure your workstation for backup by a NetWare server running software such as SBackup? (Y/N):" field in Step 4 on the installation program opening screen and press MOREINFO="NONE"<Enter>.A blinking cursor appears at the end of the path statement in the field. TPERFORMANCE="REQUIRED"To continue type "Y" or "N" and then press 
MOREINFO="NONE"<Enter>.If you type "Y," the "Configure Target Service Agent for Storage Management Services" window appears.LABEL="5-3" FLOAT="0""Configuring TSA for SMS" ScreenFILEREF="c41ug40a.tif"PERFORMANCE="REQUIRED"Make any of the following modifications:
MARK=BULLETEntering the SMS Server NameSpecifies the name of the server you want a client workstation to connect to for management by an SMS application.MARK=BULLETEntering a Name for Your WorkstationPAGENUM=101 ID="BP106"Sets the client workstation's unique name. The maximum is 48 characters and the minimum is one. You need to specify this option only after the NetWare Directory ServicesTM software for NetWare 4TM networks has been initialized (or reinitialized) on a server.Entering an Optional PasswordSets a password for the client workstation. If you use this option, it must be unique and the network supervisor managing the client workstation backup must know it.Setting the Number of Buffers Available for FIle TransferSets the TSA 1KB buffers (number = 2 through 30). The default is 1. Increasing the number increases throughput speed, but requires more RAM on the client workstation.Selecting a Drive LetterIndicates the DOS hard drives where data resides that you want to back up, or the drives where you want to restore data to.A list of available drives appears when you choose this option. Select the hard drives you want backed up.For specific details about setting up the TSA software, 
IDREF="FM43744"see Chapter 17, "Setting Up the Target Service Agent (TSA) Software," on page 273.PERFORMANCE="REQUIRED"Do one of the following:
MARK=BULLETSave changes and exit by pressing MOREINFO="NONE"<F10>.Return to the main menu by pressing MOREINFO="NONE"<Esc>.If changes were made to any field within the TSA configuration window, you are prompted to save or abandon them.The installation program automatically jumps to Step 5 on the installation program opening screen IDREF="FM28272"(which is explained in the procedure on page 103).RENDERAS="SECT2"ID="FM19783"Installing LAN 
DriversLAN driver
software serves as the link between workstations' operating systems and the network.PAGENUM=102 ID="BP107"A network board in your client workstation allows it to communicate with the NetWare server.The NetWare Client software can support additional network boards and LAN drivers in a client workstation. IDREF="FM68406"See "Using Two Network Boards" on page 125 for information and procedures.All communication on the network consists of packets of information being sent between client workstations and servers through network boards and cabling. 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 a frame type.Servers and client workstations must be configured to use the same frame types in order to communicate with each other.Routers must also support the same frame types as the servers and workstations, or packets will not be routed correctly. This will disrupt communication---and if your client workstation does get a connection, it will likely fail.In NetWare 2 and NetWare 3TM software, Ethernet drivers default to the old Ethernet 802.3 frame type. In NetWare 4 and NetWare Client Kits for DOS and MS Windows, they default to the new Ethernet 802.2 frame type.Some routers on your network might not support the new Ethernet 802.2 frame type. Your client workstation cannot connect to a network expecting the old Ethernet 802.3 default if you are using the new Ethernet 802.2 default.To eliminate problems due to conflicting default frame settings, you can define both Ethernet 802.2 and Ethernet 802.3 on your workstation or server.Define frame types for your client workstation in the NET.CFG file. Include lines similar to the following, replacing ne2000 with the name of your specific ODITM LAN driver:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.3
   frame ethernet_802.2
PAGENUM=103 ID="BP108"The first frame type defined is the only one used for the initial "Get Nearest Server" request.Therefore, if you have any servers using only one frame type, list that frame type first. This allows your client workstation to make a default connection to those servers.For information on ODI LAN driver parameters for your network boards, see "BOOK="ws_d2enu" COLLECTION="nw41"Link Driver Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference.RENDERAS="SECT3"PrerequisiteMARK=CHECKBOXMake sure that the network board you installed is supported by NetWare or includes a driver compatible with NetWare.The NetWare Client installation software supports a majority of network boards. IDXID="w11216"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
The following procedure table can help you with installing your particular network board LAN driver.RENDERAS="SECT3"ID="FM28272"ProcedurePERFORMANCE="REQUIRED"Complete the appropriate procedure to install a driver for the particular type of network board you are using.PAGENUM=104 ID="BP109"These procedures correspond with Step 5 on the installation program opening screen (
IDREF="FM67195"see Figure 5-1 on page 93).COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Network Board TypeCOLNAME=2 ROTATE="0" MOREROWS="0"ProcedureVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Supported by NetWare and displayed in the list(ODI LAN drivers only. Use an existing LAN driver for network boards with dedicated IPXTM drivers only.Select the "Other drivers" option in the "Network Board" menu and direct the installation program to the path where the driver is located.)COLNAME=2 ROTATE="0" MOREROWS="0"1. Press <Enter> to select a LAN driver from the CLASS=DISKNetWare Client for DOS and MS Windows Disk 1.    If prompted, replace the current diskette with the CLASS=DISKNetWare Client for DOS and MS Windows Disk 5 ODI LAN Drivers. 2. Display the list by pressing MOREINFO="NONE"<Enter> again.3. Move through the list by using the arrow keys or the MOREINFO="NONE"PgDn key.4. Select the driver you want to install and press MOREINFO="NONE"<Enter>.COLNAME=1 ROTATE="0" MOREROWS="0"Supported by NetWare but not displayed in the list(If you are using dedicated IPX LAN drivers, replace with the appropriate ODI LAN driver for your network board.Select the "Other drivers" option in the "Network Board" menu and direct the installation program to the path where the driver is located.)COLNAME=2 ROTATE="0" MOREROWS="0"1. Press MOREINFO="NONE"<Enter> and then replace CLASS=DISKNetWare Client for DOS and MS Windows Disk 1 with the driver diskette that was included in your network board kit.2. Display the list by pressing MOREINFO="NONE"<Enter> again.3. Move through the list by using the arrow keys or the MOREINFO="NONE"PgDn key.4. Select the driver you want to install and press MOREINFO="NONE"<Enter>.A box appears, prompting you to modify the value settings for your network board. The following are some of the main options available:
MARK=BULLETBase I/O portHardware interruptsMedia frame typePAGENUM=105 ID="BP110"There are numerous other options available, depending on your network board type and driver.Refer to the help at the bottom of the installation program screen for information about an appropriate value setting for each option.If you are unsure of your client workstation's network board settings, refer to your records or accept the default settings.  If your LAN driver does not load at startup, ensure that the parameter settings for the Link Driver section of the NET.CFG file match the network board hardware settings. RENDERAS="SECT2"ID="FM59935"Copying FilesThe installation IDXID="w11217"BOOK="_idx" COLLECTION="nw41" TIDREF="i846"
program 
copies the core NetWare Client software and other files to the destination directory you selected in Step 1 on the installation program opening screen.RENDERAS="SECT3"Swapping DiskettesWhen installing the LAN Drivers from a floppy diskette in the same drive as the destination drive (such as drive A: to A:), enter a different drive (such as drive B:) when the program prompts you to enter the letter for the source drive where the LAN drivers are copied from.This causes DOS to recognize drive A: as drive B: and to prompt you to insert the driver diskette without disrupting the process of the installation program.RENDERAS="SECT3"Replacing Older FilesRENDERAS="SECT4"Existing FilesThe installation program might prompt you to make decisions about replacing or not replacing existing files.If you choose to not replace an existing file, your installation might not be successful.RENDERAS="SECT4"Read-Only FilesThe installation program might prompt you to make decisions about replacing or not replacing read-only configuration files.PAGENUM=106 ID="BP111"If you do not allow for automatic changes to these files during installation, a copy of the necessary changes is saved to the files with a .NEW extension (for example, C:\WINDOWS\SYSTEM.NEW).You will be required to make these changes manually after the installation. (IDREF="FM44545"See "Creating or Modifying Configuration Files" on page 121 for more information.)If a read-only .NEW file by that name already exists and you do not chose the allow the installation program to write over it, the installation program does not save the changes to a file.RENDERAS="SECT1"ID="FM68617"What Happens 
during 
InstallationThe following events IDXID="w11218"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
happen when you install the NetWare Client software.RENDERAS="SECT2"A Directory Is CreatedA directory is created for the DOS client files according to the target directory specified during installation.If you are installing for Microsoft (MS) Windows, the MS Windows client files are copied to the specified MS Windows directory. (The default is C:\NWCLIENT for DOS and C:\WINDOWS for MS Windows unless the installation program finds a copy of the VLM.EXE and WIN.COM files in a different location.)RENDERAS="SECT2"Files Are CopiedAll NetWare Client files for DOS and MS Windows are copied to the directories specified during installation.Five kinds of files are copied:MARK=BULLETNetWare User Tools for DOS and MS WindowsVirtual Loadable ModuleTM (VLM) program filesVLMTM ManagerLAN driversPAGENUM=107 ID="BP112"Unicode tables with corresponding code pages and country codesMS Windows Dynamic Link Library (DLL) filesRENDERAS="SECT2"DOS and NetWare Configuration Files Are Created or ModifiedRENDERAS="SECT3"CONFIG.SYS and 
AUTOEXEC.BATIf you allowed the installation program to modify your 
system configuration files, then the previous version of your client workstation's 
CONFIG.SYS and AUTOEXEC.BAT files are automatically saved as CONFIG.BNW and AUTOEXEC.BNW. If these specific .BNW files already exist, then they are overwritten.If no previous versions of the AUTOEXEC.BAT and CONFIG.SYS files existed, new files are created for you.The lines MOREINFO="NONE"LASTDRIVE=Z andMOREINFO="NONE" FILES=40 are added to the CONFIG.SYS file.IDXID="w11219"BOOK="_idx" COLLECTION="nw41" TIDREF="i358"
The linesMOREINFO="NONE" @CALL drive:MOREINFO="NONE"\NetWare_Client_directoryMOREINFO="NONE"\STARTNET and MOREINFO="NONE"PATH=NetWare_Client_directoryMOREINFO="NONE"/%PATH% are added to the AUTOEXEC.BAT file.RENDERAS="SECT3"STARTNET.BATIDXID="w11220"BOOK="_idx" COLLECTION="nw41" TIDREF="i4261"
The installation program creates a file called STARTNET.BAT in the target directory you specified.The file contains the following lines, which load the core NetWare Client software:FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NWLANGUAGE=preferred_language
C:\NetWare_Client_directory\LSL.COM 
C:\NetWare_Client_directory\LAN_driver.COM 
C:\NetWare_Client_directory\IPXODI.COM
C:\NetWare_Client_directory\VLM.EXEIf you installed the TSA software for allowing the client workstation to be backed up from a server, a line for the TSASMS.COM file would be added after the line that loads the VLM.EXE file.PAGENUM=108 ID="BP113"RENDERAS="SECT3"NET.CFGThe installation program reads the existing IDXID="w11221"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NET.CFG file or creates a new one if one does not exist in order to set a configuration for the network board installed in your client workstation. Your old NET.CFG file is saved as NET.BNW.The following is an example of a IDXID="w11222"BOOK="_idx" COLLECTION="nw41" TIDREF="i878"
NET.CFG file for a Novell®
 NE2000TM Ethernet board:FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER NE2000
   PORT 300
   INT 3
   FRAME ETHERNET_802.2FORMAT="LINESPECIFIC"MOREINFO="NONE"NETWARE DOS REQUESTER
   NETWARE PROTOCOL = NDS BIND
   FIRST NETWORK DRIVE = FRENDERAS="SECT2"ID="FM79655"MS Windows Configuration Files Are ModifiedWhen you select "Install Support for MS Windows" in Step 3 of the NetWare Client installation program (illustrated in IDREF="FM67195"Figure 5-1 on page 93), the installation program makes changes to your SYSTEM.INI, WIN.INI, and PROGMAN.INI files.RENDERAS="SECT3"ID="FM94080"
SYSTEM.INIIDXID="w11223"BOOK="_idx" COLLECTION="nw41" TIDREF="i4392"
The installation program adds or makes the following modifications to the SYSTEM.INI file:RENDERAS="SECT4"[boot]MARK=BULLETThe line MOREINFO="NONE"network.drv= is replaced by MOREINFO="NONE"network.drv=netware.drv.If you are installing for Windows for Workgroups (WFWG), the following modification is made:The line MOREINFO="NONE"secondnet.drv= is replaced byMOREINFO="NONE" secondnet.drv=netware.drv.PAGENUM=109 ID="BP114"This loads NetWare User Tools driver when MS Windows is loaded. The user interface for the NETWARE.DRV file is the NWUSER.EXE file. RENDERAS="SECT4"[boot.description]MARK=BULLETThe line MOREINFO="NONE"network.drv= is replaced by MOREINFO="NONE"network.drv=NetWare (vxMOREINFO="NONE".xMOREINFO="NONE").If you are installing for Windows for Workgroups (WFWG), the following modification is made:The line MOREINFO="NONE"secondnet.drv= is replaced by MOREINFO="NONE"secondnet.drv=Novell NetWare (workstation shell 4.0 and above).This notifies MS Windows Setup of the NetWare device version you are using. RENDERAS="SECT4"[Network]MARK=BULLETIf you are installing for Windows for Workgroups (WFWG), the following modification is made:The line MOREINFO="NONE"winnet= is replaced by MOREINFO="NONE"winnet=novell/00040000.This specifies the type of network and version used with WFWG.The line MOREINFO="NONE"multinet= is appended to appear as MOREINFO="NONE"multinet=NetWare4.This identifies other network operating systems running on the network.RENDERAS="SECT4"[386Enh]MARK=BULLETThe line MOREINFO="NONE"network=dosnet is replaced by MOREINFO="NONE"network=*vnetbios;vipx.386;vnetware.386.This specifies the type of network used with MS Windows 386 enhanced mode.The line MOREINFO="NONE"TimerCriticalSection= is replaced by MOREINFO="NONE"TimerCriticalSection=1000.NetWare uses this setting to ensure that network traffic on your client runs smoothly.PAGENUM=110 ID="BP115"The line MOREINFO="NONE"OverlappedIO= is replaced by MOREINFO="NONE"OverlappedIO=OFF.This specifies that virtual machines cannot issue a request to read or write to a disk until any previous read and write requests have been completed.The line MOREINFO="NONE"PSPIncrement= is replaced by MOREINFO="NONE"PSPIncrement=5.This specifies the amount of additional memory, in 16-byte increments, that MS Windows should reserve in each successive virtual machine.This setting requires that MOREINFO="NONE"UniqueDOSPSP=ON.The line MOREINFO="NONE"ReflectDOSInt2A= is replaced by MOREINFO="NONE"ReflectDOSInt2A=True.This specifies that MS Windows will pass on INT 2A signals to the NetWare Client software.The line MOREINFO="NONE"UniqueDOSPSP= is replaced by MOREINFO="NONE"UniqueDOSPSP=True.This specifies MS Windows should start every application at a new memory address.RENDERAS="SECT3"ID="FM99730"
WIN.INIIDXID="w11224"BOOK="_idx" COLLECTION="nw41" TIDREF="i4828"
The installation program adds or makes the following modifications to the WIN.INI file:RENDERAS="SECT4"[windows]The line MOREINFO="NONE"load= is replaced by MOREINFO="NONE"load=nwpopup.exe.This causes MS Windows to run the NetWare User Tools application as an icon when MS Windows is loaded.RENDERAS="SECT3"ID="FM96214"
PROGMAN.INIThe installation program adds or makes the following modifications to the IDXID="w11225"BOOK="_idx" COLLECTION="nw41" TIDREF="i3570"
PROGMAN.INI file:RENDERAS="SECT4"[Groups]The line MOREINFO="NONE"GroupxMOREINFO="NONE"=C:\MS_Windows_directoryMOREINFO="NONE"\NW.GRP is added to the list of group files if the NW.GRP file does not exist.PAGENUM=111 ID="BP116"This causes MS Windows to run the NetWare User Tools application as an icon when MS Windows is loaded.RENDERAS="SECT2"Icon in NetWare Tools Group Is CreatedThe installation program adds an icon to the NetWare Tools group if one does not exist already.If you have a previous installation of the NetWare Client for MS Windows installed on your workstation, the installation program configures the existing icon for this installation and does not create a new icon or a new group.RENDERAS="SECT1"ID="FM29800"Installing for MS Windows for WorkgroupsIf you are 
running the NetWare Client software on client workstations running IDXID="w11226"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
MS 
Windows for 
Workgroups (WFWG), you should complete this additional setup before loading the NetWare Client software.The additional setup required for MS Windows for Workgroups is notifying the WFWG software of the LAN driver type you want to use. You can use either ODI LAN drivers provided in this kit or NDIS drivers provided with WFWG. If you want to use the NDIS drivers or connect to the MS network software in WGWG, you need to install the ODINSUP driver from Novell. IDREF="FM13108"See Chapter 12, "Setting Up the NetWare ODI Support Interface for NDIS Protocols," on page 221 for more information.RENDERAS="SECT2"PrerequisitesEnsure the following before running the MS Windows for Workgroups software:MARK=CHECKBOXA working copy of the MS Windows for Workgroups software is installed on each workstation you want to run with the NetWare Client softwareThe NetWare Client software is installed or upgraded on each client workstation running the MS Windows for Workgroups softwarePAGENUM=112 ID="BP117"If you install the NetWare Client software on top of a copy of MS Windows for Workgroups that has the "Microsoft Windows Network" disabled, the Network Setup program within MS Windows for Workgroups will not recognize the NetWare Client software.  Ensure that the WINNET= and MULTINET= settings in the [Network] section of the SYSTEM.INI file are set to WINNET=NOVELL/00040000 and MULTINET=NETWARE4 for running the NetWare DOS Requester software.The NetWare Client software is loaded and running, with a successful connection in DOS to the network or a NetWare serverRENDERAS="SECT2"ProcedureTo set up and run the NetWare Client software on client workstations running MS Windows for Workgroups, complete the following steps:PERFORMANCE="REQUIRED"Load the MS Windows for Workgroups software.The following error message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE""Networking functionality will not be available. Your network adapter or protocols may not be configured properly. Run Network Setup to check adapter and protocol settings."PERFORMANCE="REQUIRED"To continue, choose "OK."PERFORMANCE="REQUIRED"In the "Network" group, choose the "Network Setup" icon.PERFORMANCE="REQUIRED"From the "Network Setup" dialog box, choose "Drivers."The "Network Drivers" dialog box appears. MS Windows for Workgroups requires you to select a LAN driver compatible with ODI for your network board.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Remove any existing LAN drivers from the dialog box by selecting a LAN driver and choosing "Remove."When prompted to make sure you want to remove the selected LAN drivers, choose "Yes."PERFORMANCE="REQUIRED"Choose "Add Adapter."PERFORMANCE="REQUIRED"From the "Add Network Adapter" dialog box, select the appropriate ODI LAN driver for your network board.
PAGENUM=113 ID="BP118"The Setup program might prompt you to direct it to the location of the correct ODI LAN driver. The correct LAN driver should exist in the NetWare Client directory you selected during installation of the NetWare Client software.PERFORMANCE="REQUIRED"Setup the appropriate frame type for your network.The NWLINK.386 file is a 32-bit IPX/SPXTM compatible transport Vxd used by MS Windows for Workgroups. It defaults to the Ethernet_802.3 frame type.  Software such as the RCONSOLE utility and other utilities that run in an MS Windows DOS box might fail if the frame type setting is incorrect for your network.  To change the default frame type for the NWLINK.386 file, select "IPX/SPX Compatible Transport" or "IPX/SPX Compatible Transport with NetBIOS," and then choose "Setup." Then, select "Frame Type" and change the value to the desired frame type.PERFORMANCE="REQUIRED"Exit the "Network Drivers" dialog box, by choosing "OK" and then "Exit."Your NetWare Client software installation is now completed.To modify any client workstations files, continue with the next section.To load the client software, reboot your client workstation and then go to IDREF="FM45160""Loading the NetWare Client Software" on page 124.RENDERAS="SECT1"ID="FM80903"Setting Up an MS Windows Shared Network Directory for NETX and VLM Client WorkstationsTo set up a network copy of MS Windows to support individual users that operate multiple client workstations running the current NetWare DOS Requester (VLM) or the NetWare Shell (NETX) software, you need to complete the following procedures. MARK=BULLETIDREF="FM10789"Setting Up Network Directories and FilesIDREF="FM28598"Setting Up Individual Client Workstations and User DirectoriesPAGENUM=114 ID="BP119"RENDERAS="SECT2"ID="FM10789"Setting Up Network Directories and FilesRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running Novell DOSTM 7 or later, DR DOS® 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM48779"Install MS Windows using the SETUP /A option and create a shared network directory for the MS Windows System files.For example, you could create a directory such as
FORMAT="LINESPECIFIC"MOREINFO="NONE" F:\APPS\WINSYSPERFORMANCE="REQUIRED"Create a directory for NetWare Shell versions of the NETWARE.DRV and NETWARE.HLP files.For example, you could create a directory such as
FORMAT="LINESPECIFIC"MOREINFO="NONE" F:\APPS\WINSYS\NETXDRVPERFORMANCE="REQUIRED"Copy the previous NETWARE.DRV and NETWARE.HLP files that support the NetWare Shell software (NETX) to the NETXDRV subdirectory.PERFORMANCE="REQUIRED"Run the NetWare Client installation program for DOS and MS Windows and install to the network copy of MS Windows created in 
IDREF="FM48779"Step 1.IDREF="FM60777"See "Modifying MS Windows Configuration Files on a Network Directory" on page 97 for procedures.PERFORMANCE="REQUIRED"Create a NetWare group called "NETXUSERS."PERFORMANCE="REQUIRED"Add each user that uses a client workstation running the NetWare Shell (NETX) software to the "NETXUSER" group.
PAGENUM=115 ID="BP120"PERFORMANCE="REQUIRED"Modify the system login script or container login script to include the following IF...THEN statement:
FORMAT="LINESPECIFIC"MOREINFO="NONE"IF MEMBER OF "NETXUSER" AND %LOGIN_NAME <> SUPERVISOR THEN #C:\COMMAND /C SYS_SET.BATEnsure that the information within the quotes is in the proper upper or lower case for the user group you specified.PERFORMANCE="REQUIRED"ID="FM97807"Create the following batch file and save it as SYS_SET.BAT in the SYS:PUBLIC directory:
FORMAT="LINESPECIFIC"MOREINFO="NONE"@echo OFF
IF "%NETDRV%"=="NETX" goto NETX >nul
NCOPY F:SYSTEM.NET F:SYSTEM.INI >NUL
GOTO END
NETX
NCOPY F:SYSTEM.NTX F:SYSTEM.INI >NUL
:ENDRENDERAS="SECT2"ID="FM28598"Setting Up Individual Client Workstations and User DirectoriesRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running Novell DOS 7 or later, DR DOS 5 or later, MS-DOS 3 or later, or PC-DOS 3 or later.Rights to access user's home directoriesRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Use the SETUP /N option to install a copy of MS Windows for each user that uses both client types-the NetWare DOS Requester and NetWare Shell.The /N parameter creates individual .INI and .GRP files for the each user.Ensure that you are installing to a unique MS Windows directory for each user that accesses the shared MS Windows System directory.Allow the software to update the AUTOEXEC.BAT and CONFIG.SYS and files on each client workstation.
PAGENUM=116 ID="BP121"PERFORMANCE="REQUIRED"Add the following environment variable to the STARTNET.BAT file on each client workstation running the NetWare Shell software:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET NETDRV=NETXPERFORMANCE="REQUIRED"Create two versions of the SYSTEM.INI file, one for each type of client software, and save them in each user's individual home directory. The SYS_SET.BAT file created in 
IDREF="FM97807"Step 8 in the previous procedure (
IDREF="FM97807"see page 115) automatically uses the appropriate SYSTEM.INI for the client software running on a particular client workstation.For example, you could create a SYSTEM.INI file called SYSTEM.NET that has the following lines in it:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[boot]
network.drv=netware.drv
FORMAT="LINESPECIFIC"MOREINFO="NONE"[386Enh]
network=*vnetbios,vnetware.386,vipx.386And create another file called SYSTEM.NTX:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[boot]
network.drv=f:\apps\winsys\netxdrv\netware.drv
FORMAT="LINESPECIFIC"MOREINFO="NONE"[386Enh]
network=*vnetbios,vnetware.386,vipx.386RENDERAS="SECT1"ID="FM35338"Installing Client Workstation Files ManuallyIt is recommended that you use the installation program to install new and upgrade existing client workstations in order to ensure that all files are copied into their correct location and that configuration files are modified correctly.However, you can install the NetWare Client software for DOS and MS Windows IDXID="w11227"BOOK="_idx" COLLECTION="nw41" TIDREF="i651"
manually to suit your particular networking environment.You might also want to refer to this section if you did not allow the installation program to modify your DOS configuration files. You should ensure that the proper modifications are made before restarting the client workstation.PAGENUM=117 ID="BP122"RENDERAS="SECT2"Copying and Expanding FilesTo manually copy the NetWare Client software files from the NetWare Client for DOS and MS Windows diskettes to the appropriate directories (the default is C:\NWCLIENT), complete the following steps.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"On each client workstation, create any of the following directories that are appropriate for your environment:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="16*"COLNAME=2 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Type of NetWare Client SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"Default DirectoryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Core DOS software  Language software for DOSCOLNAME=2 ROTATE="0" MOREROWS="0"C:\NWCLIENT  C:\NWCLIENT\NLSCOLNAME=1 ROTATE="0" MOREROWS="0"MS Windows directory software  Language software for MS Windows  MS Windows SYSTEM directory softwareCOLNAME=2 ROTATE="0" MOREROWS="0"C:\WINDOWS  C:\WINDOWS\NLS  C:\WINDOWS\SYSTEMCOLNAME=1 ROTATE="0" MOREROWS="0"Optional DOS softwareCOLNAME=2 ROTATE="0" MOREROWS="0"C:\NWCLIENTPERFORMANCE="REQUIRED"Copy the files and directories you need from the NetWare Client for DOS and MS Windows diskettes to the appropriate directoriesType either
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY source_drive:path destination_drive:path /s /e /c MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY source_drive:path destination_drive:path /s /e MOREINFO="NONE"<Enter>Do not use the DOS COPY command for this procedure. It is important that the directory structure within each subdirectory is maintained. Use the DOS XCOPY or NetWare NCOPY command to complete this procedure.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY A:NLS\*.* C:\NWCLIENT /s /e /c MOREINFO="NONE"<Enter>or
PAGENUM=118 ID="BP123"FORMAT="LINESPECIFIC"MOREINFO="NONE"XCOPY A:NLS\*.* C:\NWCLIENT /s /e MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"ID="FM79548"To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:filename destination_drive:filename MOREINFO="NONE"<Enter>For example, to expand the ODINSUP.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:ODINSUP.CO_ C:\NWCLIENT\ODINSUP.COM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM79548"Step 3 until all of the NetWare Client files exist in the appropriate directories.Following is a complete list of the NetWare Client software files included in this Client kit and NetWare packages.LABEL="5-1" PGWIDE=0 TOCENTRY="1"ID="FM41041" NetWare Client Kit SoftwareCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Software TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=3 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=4 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Core DOS softwareCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"AUTO.VL_  BIND.VL_  CONN.VL_  FIO.VL_  GENERAL.VL_  IPXNCP.VL_  IPXODI.CO_  LSL.CO_  NDS.VL_  NETX.VL_  NWP.VLM_  PRINT.VL_  REDIR.VL_  SECURITY.VL_  TRAN.VL_  VLM.EX_COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN Drivers or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=3 ROTATE="0" MOREROWS="0"\DOSCOLNAME=4 ROTATE="0" MOREROWS="0"ODI LAN Drivers .CO_ and .IN_COLNAME=1 ROTATE="0" MOREROWS="0"Language software for DOSCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=3 ROTATE="0" MOREROWS="0"\NLS\languageCOLNAME=4 ROTATE="0" MOREROWS="0"DOSRQSTR.MS_  IPXODI.MS_  LSL.MS_  NESL.MS_  NMR.MS_  README.TX_  READVLM.TX_  RSMONSTK.MS_COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=3 ROTATE="0" MOREROWS="0"\NLS\languageCOLNAME=4 ROTATE="0" MOREROWS="0"MIB2IF.MS_  MIB2PROT.MS_  STPIPX.MS_  STPUDP.MS_  WSASN1.MS_  WSDRVPRN.MS_  WSREG.MS_  WSSNMP.MS_  WSTRAP.MS_COLNAME=1 ROTATE="0" MOREROWS="0"MS Windows directory softwareCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"NOVELL.BM_  NOVLOGO1.BM_  NWADMIN.IN_  NWRCON.PI_COLNAME=1 ROTATE="0" MOREROWS="0"Language software for MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 4COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"Unicode TablesCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 4COLNAME=3 ROTATE="0" MOREROWS="0"\NLS\languageCOLNAME=4 ROTATE="0" MOREROWS="0"NETWARE.HL_COLNAME=1 ROTATE="0" MOREROWS="0"MS Windows SYSTEM directory softwareCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"NETWARE.DR_  NWCALLS.DL_  NWGDI.DL_  NWIPXSPX.DL_  NWNET.DL_  NWPOPUP.EX_  NWUSER.EX_  PNW.DL_  TLI_SPX.DL_  TLI_TCP.DL_  TLI_WIN.DL_  VIPX.38_  VNETWARE.38_COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 4COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"NWLOCALE.DL_  NWPSRV.DL_COLNAME=1 ROTATE="0" MOREROWS="0"Optional DOS SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=3 ROTATE="0" MOREROWS="0"\COLNAME=4 ROTATE="0" MOREROWS="0"DOSNP.EX_  HRMIB.EX_  HRMIB.IN_  MIB2IF.VL_  MIB2PROT.VL_  NESL.CO_  NETBIOS.EX_  ODINSUP.CO_  PNW.VL_  ROUTE.CO_  RPL.CO_  RSA.VL_  RSMONSTK.CO_  STPIPX.CO_  STPUDP.CO_  TSASMS.CO_  WSASN1.VL_  WSDRVPRN.VL_  WSREG.VL_  WSSNMP.VL_  WSTRAP.VL_PAGENUM=121 ID="BP124"RENDERAS="SECT2"ID="FM44545"Creating or Modifying Configuration FilesIt is necessary to modify the following system files and configuration files with an ASCII text editor:MARK=BULLETIDREF="FM94863"AUTOEXEC.BATIDREF="FM67548"CONFIG.SYSIDREF="FM90208"STARTNET.BATIDREF="FM90661"NET.CFGIDREF="FM90691"MS Windows Configuration FilesRENDERAS="SECT3"ID="FM94863"AUTOEXEC.BATIDXID="w11228"BOOK="_idx" COLLECTION="nw41" TIDREF="i361"
In previous client versions, the software was loaded from the AUTOEXEC.BAT file. The current client version now uses a STARTNET.BAT file, which loads the NetWare DOS Requester and LAN driver when the AUTOEXEC.BAT file is run.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"ID="FM35440"Insert the line MOREINFO="NONE"@CALL drive:MOREINFO="NONE"\client_directoryMOREINFO="NONE"\STARTNET at the beginning of your client workstation's AUTOEXEC.BAT file.PERFORMANCE="REQUIRED"Delete or disable any previous NetWare shell or LAN driver commands in each client workstation's AUTOEXEC.BAT file that might conflict with the newly installed software.If any of the following files exist in the AUTOEXEC.BAT file, delete or disable them:
TYPE="VERT"LSL.COMLAN Driver (for example, NE2000.COM)IPXODI.COMNET
x.COM (or other NetWare Shell files)IPX.COMPAGENUM=122 ID="BP32A"If you are modifying the AUTOEXEC.BAT after running the installation program, your original AUTOEXEC.BAT file is saved as AUTOEXEC.BNW in the same directory. This happens only if you allowed the installation program to modify your DOS configuration files.RENDERAS="SECT3"ID="FM67548"CONFIG.SYSIn previous client versions, the software set the first network drive after the DOS LASTDRIVE setting in the IDXID="w11229"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS file. The current software requires that the LASTDRIVE setting be set to drive Z:.Add or modify the MOREINFO="NONE"LASTDRIVE=Z line at the end of the CONFIG.SYS file. If you are modifying the CONFIG.SYS file after running the installation program, your original CONFIG.SYS file is saved as CONFIG.BNW in the same directory. This happens only if you allowed the installation program to modify your DOS configuration files.RENDERAS="SECT3"ID="FM90208"STARTNET.BATPERFORMANCE="REQUIRED"Create a IDXID="w11230"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT file in the NetWare Client directory or modify the existing STARTNET.BAT file.The default is C:\NWCLIENT.PERFORMANCE="REQUIRED"Add the necessary line to load the STARTNET.BAT in your AUTOEXEC.BAT file or load the STARTNET.BAT file manually each time you want to connect to the network or a server.PERFORMANCE="REQUIRED"(Conditional) If you are running MS Windows for Workgroups 3.11, you must add a line for the ODIHLP.EXE file.Ensure that the ODIHLP.EXE file is loaded in the STARTNET.BAT file after loading the transport protocol (The default the IPXODI.COM file). If you currently load the ODIHLP.EXE file in the AUTOEXEC.BAT file, move the line to the STARTNET.BAT file.The STARTNET.BAT file should appear as follows. If you are creating a new STARTNET.BAT file, add the following lines in the given order:FORMAT="LINESPECIFIC"MOREINFO="NONE"set nwlanguage=preferred_language
c:\client directory\lsl.com
c:\client directory\odi_lan_driver
c:\client directory\ipxodi.com
c:\MS Windows directory\odihlp.exe
c:\client directory\vlm.exe
PAGENUM=123 ID="BP33A"Include the line for the MS Windows directory only if you are running MS Windows for Workgroup.Replace preferred_language with one of the following languages:TYPE="VERT"ENGLISHDEUTSCHESPANOLFRANCAISITALIANOReplace client directory with the directory where the NetWare Client files are found.Replace odi_lan_driver with name of the ODI LAN driver that your workstation is using.Replace MS Windows directory with the directory where the MS Windows for Workgroup files are found.RENDERAS="SECT3"ID="FM90661"NET.CFGIDXID="w11231"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
Create or modify the NET.CFG file in your NetWare Client directory to configure for login, desktop management, and system integration. Refer to the sections below for more information about additional set up made in the NET.CFG file for NetWare client workstations:MARK=BULLETIDREF="FM41619"Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161.(Optional) IDREF="FM13108"Chapter 12, "Setting Up the NetWare ODI Support Interface for NDIS Protocols," on page 221.(Optional) IDREF="FM88338"Chapter 13, "Setting Up the NetWare for IBM LAN Support Program Modules," on page 235.(Optional) IDREF="FM35822"Chapter 14, "Setting Up NetBIOS Protocol Support," on page 245.(Optional) IDREF="FM39829"Chapter 15, "Setting Up Source Routing Support for a Token-Ring Network," on page 253.PAGENUM=124 ID="BP34A"(Optional) IDREF="FM13494"Chapter 16, "Setting Up Named Pipes Protocol Support," on page 261.(Optional) IDREF="FM43744"Chapter 17, "Setting Up the Target Service Agent (TSA) Software," on page 273.(Optional) IDREF="FM54735"Chapter 18, "Configuring Client Workstations for Desktop SNMP Services," on page 281.RENDERAS="SECT3"ID="FM90691"MS Windows Configuration FilesEdit the following files in the MS Windows directory:MARK=BULLETIDREF="FM94080"SYSTEM.INIIDREF="FM99730"WIN.INIIDREF="FM96214"PROGMAN.INIIDREF="FM79655"See "MS Windows Configuration Files Are Modified" on page 108 for more information.RENDERAS="SECT1"ID="FM45160"Loading the NetWare Client SoftwareLoading the NetWare Client software for DOS and MS Windows client workstations requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that a copy of DOS or MS Windows is set up on each client workstation.IDREF="FM18804"See "Setting Up Workstation Software" on page 75.PERFORMANCE="REQUIRED"Ensure that the NetWare Client software files are installed on each client workstation that you want to run DOS or MS Windows.IDREF="FM11014"See "Running the NetWare Client Installation Program" on page 90 or 
IDREF="FM35338""Installing Client Workstation Files Manually" on page 116 for more information.
PAGENUM=125 ID="BP35A"PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM35338"See "Installing Client Workstation Files Manually" on page 116 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation. (The STARTNET.BAT file loads the necessary files.)If you decide to downgrade the NetWare Client software from version 1.2 to an earlier version, you must delete the LSL.MSG file (version 1.18 or later) that was copied to the NetWare Client directory during installation of the 1.2 files.  The LSL.MSG file is new to the NetWare Client Kit 1.2. The LSL.COM file that shipped with earlier versions of the NetWare Client Kit for DOS and MS Windows does not support the LSL.MSG file.RENDERAS="SECT1"ID="FM68406"Using Two Network BoardsIn 
most cases the ODI (or compatible) LAN drivers provided with the NetWare Client software can share a network board with other communication packages so you do not need to purchase two network boards.This section describesMARK=BULLETIDREF="FM70522"Reasons for Having Two Network BoardsIDREF="FM83365"Modifying Client Workstation Files for Two Network BoardsRENDERAS="SECT2"ID="FM70522"Reasons for Having Two Network BoardsWhen using the NetWare Client software, there are two conditions where you might benefit from having more than one network board installed in your client workstations:MARK=BULLETIDREF="FM61916"Different Communication Software PackageIDREF="FM85893"Physically Separated NetworksIf you have two network boards, be aware of the configuration issues in the following sections.PAGENUM=126 ID="BP36A"Additional network boards (those after the second defined network board) are ignored by the NetWare Client software.RENDERAS="SECT3"ID="FM61916"Different Communication Software PackageYou might want to use two network boards when each board is supported by its own communication software package.For example, you might want to have MS Windows for Workgroups use one network board for NDIS protocol stacks and NetWare Client software use another network board for IPX protocol stacks. However, this is not necessary if you install the ODINSUP.COM file. IDREF="FM13108"See Chapter 12, "Setting Up the NetWare ODI Support Interface for NDIS Protocols," on page 221 for more information.If you use a separate network board for each communication package that you use then here are no additional steps to set up the second network board under NetWare. This is because the network board is controlled by the other communications package. It might need to be configured under the other communication package.RENDERAS="SECT3"ID="FM85893"Physically Separated 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.This means that, although both networks are connected to the same physical machine, there is no communication between the two networks.RENDERAS="SECT2"ID="FM83365"Modifying Client Workstation Files for Two Network BoardsModifying client workstations system and 
configuration files for two network boards requires you to edit the following files in an ASCII text editor:MARK=BULLETIDREF="FM14932"STARTNET.BATIDREF="FM10618"NET.CFGPAGENUM=127 ID="BP37A"RENDERAS="SECT3"ID="FM14932"STARTNET.BATThe NetWare Client installation program allows you to select a single ODI LAN driver. This driver is loaded in the STARTNET.BAT file.You need to load an additional ODI LAN driver in the STARTNET.BAT file if you have two network boards installed in your client workstation.The STARTNET.BAT file should appears as follows. If you are creating a new STARTNET.BAT, add the following lines in the given order:FORMAT="LINESPECIFIC"MOREINFO="NONE"set nwlanguage=preferred_language
c:\client directory\lsl.com
c:\client directory\primary_lan_driver
c:\client directory\secondary_lan_driver
c:\client directory\ipxodi.com
c:\client directory\vlm.exe
c:\MS Windows directory\odihlp.comInclude the line for MS Windows directory only if you are running MS Windows for Workgroup.Replace preferred_language with one of the following languages:TYPE="VERT"ENGLISHDEUTSCHESPANOLFRANCAISITALIANOReplace client directory with the directory where the NetWare Client files are found.Replace primary_lan_driver with name of the ODI LAN driver that your workstation binds to first.Replace secondary_lan_driver with name of the ODI LAN driver that your workstation binds to second.Replace MS Windows directory with the directory where the MS Windows for Workgroup files are found.PAGENUM=128 ID="BP38A"RENDERAS="SECT3"ID="FM10618"NET.CFGRENDERAS="SECT4"Two Different DriversIf you have IDXID="w11232"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
two network boards using different types of ODI LAN drivers, you must load the LAN drivers separately by adding a Link Driver section for each network board.For example, if you have and NE2000 network board (the primary board) and a token ring network board, you might include the following lines in the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   int 5
   port 360
   frame ethernet_802.2
   frame ethernet_802.3FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ntr2000
   int 5
   port a20
   mem cc000
   frame token-ring
   frame token-ring_snapRENDERAS="SECT4"Two Identical DriversIf you have two network boards using the same type of ODI LAN driver, do not load the same driver twice in the NET.CFG file and do not specify a "Protocol Stack" option.Instead, use the Link Driver option in NET.CFG to specify that the same driver is used twice.Do this by placing two Link Driver sections in the NET.CFG file, 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 modified, because you cannot have two network boards of the same type with both using default hardware settings.PAGENUM=129 ID="BP39A"For example, if you have two NE2000 LAN drivers, you might include the following lines in the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   int 5
   port 360
   frame ethernet_802.2
   frame ethernet_802.3FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   int 4
   port 320
   frame ethernet_802.2
   frame ethernet_802.3Putting two occurrences of "link driver ne2000" loads the NE200 driver twice.With two network boards of the same type, the network board which is listed first in the NET.CFG file is the one that IPX uses as primary.  Also, if you do not specify two Link Driver sections, a driver will not be loaded for the second network board, and that board will be ignored.  See "BOOK="ws_d2enu" COLLECTION="nw41"Link Driver Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for information.If you use two Micro Channel* or EISA network boards that use the same driver (such as two NE3200TM or two 3C523 LAN drivers), you must still specify a Link Driver section in the NET.CFG file 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 does not indicate the load order. It tells the driver where the network board is located. The driver then scans the network board and determines what hardware settings are in use.For example, for two NE32000 LAN drivers, you might include the following lines in the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
   slot 2
   frame ethernet_802.2
   frame ethernet_802.3
PAGENUM=130 ID="BP40A"FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
   slot 1
   frame ethernet_802.2
   frame ethernet_802.3In this example, the network board in slot 2 becomes the primary board because the driver for it is 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, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
   slot 1
   frame ethernet_802.2
   frame ethernet_802.3FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne3200
   slot 2
   frame ethernet_802.2
   frame ethernet_802.3
PAGENUM=131 ID="BP41A"RENDERAS="SECT1"ID="FM87757"Where to Go from HereAfter installation of your NetWare Client software is completed, you can log in to the network. You can also begin setting up your client workstation for additional networking support. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Prepare to log in to the network by doing any of the following:COLNAME=2 ROTATE="0" MOREROWS="0" COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETLearn more about logging in to NDSCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98317""Understanding Logging In to NetWare Directory Services" on page 165COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETSet up your client workstation to log inCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41619"See Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETModify your NET.CFG file to simplify login for NetWare 2 and 3 client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM51968""Modifying the NET.CFG File for Logging In to NetWare 2 and NetWare 3" on page 162COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETModify your NET.CFG file to simplify login for NetWare 4 client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94978""Modifying the NET.CFG File for Logging In to NetWare 4" on page 163COLNAME=1 ROTATE="0" MOREROWS="0"Begin setting up for additional support by doing any of the following:COLNAME=2 ROTATE="0" MOREROWS="0" COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETSet up network drives and directoriesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86864"See Chapter 9, "Setting Up and Managing Network Drives," on page 177COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETSet up and modify your NET.CFG fileCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETSet up printing for a client workstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94060"See Chapter 10, "Setting Up Client Workstation Printing," on page 193COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETSet up your client workstation to support applications running in a task-switching environmentCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85167"See Chapter 11, "Setting Up Network Support for Task-Switching Environments," on page 211LABEL="6"PAGENUM=133 ID="BP125"ID="FM33961"Setting Up Remote Client WorkstationsRENDERAS="SECT1"OverviewThis chapter explains how to set up the network so that client workstations (mostly diskless workstations) can boot from the remote
 boot disk image files stored on a NetWare® server's hard disk.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80906"Installing a Remote Boot PROM Chip Certified by NovellCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80906"135COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM89703"Setting Up RPL SupportCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM89703"137COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM34560"Making a Boot Image File DisketteCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34560"142COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM57991"Creating Remote Boot Disk Image FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57991"145COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88057"Booting Remote WorkstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88057"156COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM22898"Using the RPLFIX.COM UtilityCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM22898"157COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83814"Troubleshooting RPL with Older Remote Boot PROMsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83814"159COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM24030"Configuring the BOOTCONF.SYS FileCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM24030"154RENDERAS="SECT1"IntroductionThe NetWare software for remote client workstations includes support for remote booting and the IBM architected Remote Program Load (RPL) frames as defined in the IBM Remote Program Load User's Guide.PAGENUM=134 ID="BP126"Remote booting is based on the concept of storing the image of a bootable floppy disk on a NetWare volume. Remote boot workstations use this image to boot up and attach to a server.The RPL technology is based on the same concept of storing an image file of a bootable floppy disk on a NetWare volume. However, RPL relies on a bootstrap program which is downloaded to each remote workstation for attaching to a server.MARK=BULLETUse more than one disk image file name per node addressSupport the IBM LAN Support Program softwareCompatibility with ODITM LAN drivers and DOS 5.0 and laterSupport booting a remote client workstations across a source routing bridgeThese client workstations do not need a floppy or hard drive to function on the network and are, therefore, called diskless workstations. A diskless workstation relies on a Programmable Read-Only Memory (PROM) chip installed in its network board to communicate with the boot server.When the workstation is powered on, it uses the boot image stored on a server to load the necessary DOS system and NetWare ClientTM software files used for connecting to the network. The image file can include any files you would normally load from a boot diskette before loading the NetWare DOS RequesterTM software (the VLM.EXE file).NetWare allows you to use a default image file for all diskless workstations on the network, or use customized image files unique to each workstation's particular system and network environment.Setting up remote booting or RPL on NetWare client workstations requires setup on a NetWare server or RPL server, hardware setup on each remote client workstation, and software setup from a client workstation with a connection to the NetWare server you want the remote workstations to boot from. The complete setup for a remote boot client workstation requires you to complete the following tasks:PAGENUM=135 ID="BP127"MARK=BULLETIDREF="FM34560"Making a Boot Image File DisketteIDREF="FM89703"Setting Up RPL Support IDREF="FM34560"Making a Boot Image File DisketteIDREF="FM57991"Creating Remote Boot Disk Image FilesIDREF="FM88057"Booting Remote WorkstationsRENDERAS="SECT1"ID="FM80906"Installing a Remote Boot PROM Chip Certified by NovellInstalling a Remote Boot PROM certified by Novell® requires you to complete the following tasks:MARK=BULLETInsert a Remote Boot PROM in every workstation that you want to boot from the network.Determine the type of Remote Boot PROM that you are using.RENDERAS="SECT2"Installing a Remote Boot PROM Chip Certified by Novell on Your Network BoardFor information on how to complete this procedure, refer to the documentation provided with your Remote Boot PROM Kit certified by Novell.RENDERAS="SECT2"ID="FM44901"Determining the Remote Boot PROM TypeThere are three kinds of Remote Boot PROMs used with NetWare networks. The three types are referred to as follows:MARK=BULLETOld (Novell IPXTM Remote Boot PROM)At initialization, the Novell IPX Remote Boot PROM sends an IPX GET NEAREST SERVER protocol frame onto the wire. This frame is positive identification that this PROM is a Novell IPX Remote Boot PROM.This type of Remote Boot PROM supports remote booting and does not require setup for RPL support. IDREF="FM34560"See "Making a Boot Image File Diskette" on page 142 to continue.IDXID="w11233"BOOK="_idx" COLLECTION="nw41" TIDREF="i3758"
Enhanced (Novell Enhanced Remote Boot PROM)PAGENUM=136 ID="BP128"At initialization, the Novell Enhanced Remote Boot PROM sends an 802.2 FIND protocol frame onto the wire. This frame is positive identification that this  PROM is a Novell Enhance Remote Boot PROM that uses the  802.2 FIND-FOUND protocol to attach to a server and download a bootstrap file. Do not use the RPLODI.COM file with this type of PROM. The RBOOT.RPL has the ability to interface with ODI LAN drivers loading from boot image files.This type of Remote Boot PROM supports RPL and requires setup for RPL support. IDREF="FM89703"See "Setting Up RPL Support" on page 137 to continue.IBM RPL PROM (IBM Remote Program Load PROM)At initialization the IBM RPL PROM sends an 802.2 FIND protocol frame onto the wire. This frame is positive identification that this PROM uses the 802.2 FIND-FOUND protocol to attach to a server and download a bootstrap file. Do not use the RPLODI.COM file with this IBM RPL PROM. The ability to interface with ODI LAN drivers loading from boot image files is provided in the following files: TOKEN.RPL, ETHER.RPL, PCN2L.RPL, F1ETH.RPL, RBOOT.RPL. This type of Remote Boot PROM supports RPL and requires setup for RPL support. IDREF="FM89703"See "Setting Up RPL Support" on page 137 to continue.The old type of Remote Boot PROMs support only the raw 802.3 and E-II frame types. The enhanced type support the 802.2 frame type only.Therefore, it is important to know what frame types your server supports to determine whether the type of Remote Boot PROM you are using is supported.If your server supports the Ethernet frame type E-II, you can then use either type of Remote Boot PROM.Some procedures for setting up remote booting on your client workstation are specific to the type of Remote Boot PROM you are using. For information on the type of Remote Reset PROM you are using, refer to the manufacturer's documentation.PAGENUM=137 ID="BP129"RENDERAS="SECT1"ID="FM89703"Setting Up RPL SupportSetting up RPL support on the network is necessary only for remote workstations using the Novell Enhanced or IBM RPL PROMs. Remote workstations using the "old" or Novell IPX Remote Boot PROM do not need to set up RPL support. IDREF="FM34560"See "Making a Boot Image File Diskette" on page 142 for more information.Setting up RPL support requires you to do the following:MARK=BULLETLoad the RPL.NLM program on the NetWare Server and bind it to the server's LAN driver.Load the RPL.COM file on a local client workstation, if you need to boot from a NetWare server across a source routing bridge.Ensure that the required files are copied to the appropriate directories.Copy newer RPL files to the appropriate directories if existing files are not current.All of the files necessary for setting up a NetWare remote boot client workstation are located in the RPL directory on CLASS=DISKNetWare Client for DOS and MS Windows Disk 2.RENDERAS="SECT2"ID="FM28422"Loading the IDXID="w11234"BOOK="_idx" COLLECTION="nw41" TIDREF="i3756"
RPL.NLM ProgramThe RPL.NLM file is a NetWare Loadable ModuleTM (NLM) program that acts as a protocol stack. It responds to the IBM architected Remote Program Load (RPL) frames as defined in the IBM Remote Program Load User's Guide.The IDXID="w11235"BOOK="_idx" COLLECTION="nw41" TIDREF="i3756"
RPL.NLM program is used in networks that have diskless workstations installed with the RPL BIOS module known as a Remote Boot PROM. Currently, RPL is supported on the following network boards:MARK=BULLETIBM Ethernet boards (MCA and Model 25SX)IBM PC network boardsIBM token-ring network boardsNovell (or compatible) and third-party network boards with an Enhanced Remote Boot PROM installedPAGENUM=138 ID="BP130"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"At the server console, load the RPL.NLM program by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD RPLMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Bind the RPL.NLM program to the network board in the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"bind rpl to network_board [parameter]For example, to bind RPL to an NE2000 LAN driver with the Ethernet_802.2 frame type, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"bind rpl to ne2000 frame=ethernet_802.2For details on how to use the BIND parameter for RPL at the command line, see "
BOOK="ws_d2enu" COLLECTION="nw41"RPL BIND Parameters" under "Command Line Parameters Reference" in Chapter 3 of 
NetWare Client for DOS and MS Windows Technical Reference.When the RPL.NLM program loads, it searches the SYS:LOGIN directory for a BOOTCONF.SYS file. If it finds one, the RPL.NLM program reads the BOOTCONF.SYS file into memory in order to make the file information available when a FIND frame is received from a client workstation. IDREF="FM24030"See "Configuring the BOOTCONF.SYS File" on page 154 for more information.RENDERAS="SECT2"ID="FM20042"Loading the RPL.COM FileThe RPL.COM file is a Terminate-and-Stay-Resident (TSR) program loaded at a client workstation. It responds to the IBM architected Remote Program Load (RPL) frames as defined in the IBM Remote Program Load User's Guide.The RPL.COM file allows a client workstation to function as an RPL Server for downloading the bootstrap file to remote workstations. It is used in networks that have diskless remote workstations that need to attach to a NetWare server across a source routing bridge with the RPL BIOS module known as a Remote Boot PROM. Currently, RPL is supported on the following network boards:MARK=BULLETIBM Ethernet boards (MCA and Model 25SX)IBM PC network boardsPAGENUM=139 ID="BP131"IBM token-ring network boardsNovell (or compatible) and third-party network boards with an Enhanced Remote Boot PROM installedRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that a Novell Enhanced Remote Boot PROM is installed in the network board at the client workstation you want to set up as an RPL server. PERFORMANCE="REQUIRED"Create a LOGIN directory at the root of the client workstation by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MD LOGIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Expand and copy the RPL.COM file and bootstrap programs to the LOGIN directory.IDREF="FM32745"See "Copying Newer RPL and Boot Files to the Server" on page 142 for more information.PERFORMANCE="REQUIRED"At a client workstation within the same LAN segment as the remote workstations, load the RPL.COM file by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"RPLMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Bind the RPL.COM program to the network board by adding the following line to the NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol rpl
   bind network_board 
[parameter]For example, to bind RPL to an NE2000 LAN driver with the Ethernet_802.2 frame type, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol rpl
   bind ne2000
   frame ethernet_802.2You must set the PS=servername or GNS optional BIND parameter to direct remote workstations to the NetWare server that contains the boot disk image file for each workstation.PAGENUM=140 ID="BP132"See "
BOOK="ws_d2enu" COLLECTION="nw41"Protocol RPL" in Chapter 2 of 
NetWare Client for DOS and MS Windows Technical Reference for more information and a list of optional BIND parameters for RPL.RENDERAS="SECT2"ID="FM16110"Ensuring That the Required Files Are in the Appropriate DirectoriesTo boot remote workstations from a NetWare server, the following files must exist on a NetWare server. These files are automatically copied to the appropriate directories when you install the NetWare server software.If any of these files do not exist in the LOGIN directory or you assume that the existing files are out of date, IDREF="FM32745"see "Copying Newer RPL and Boot Files to the Server" on page 142 for more information.RENDERAS="SECT3"Remote Boot Support ProgramsIf any of your remote booting client workstations are using the older type of Remote Boot PROM, the following RPL support programs should be copied to the SYS:LOGIN directory of the NetWare server (IDREF="FM44901"See "Determining the Remote Boot PROM Type" on page 135 for more information):COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"RPLFIX.COMCOLNAME=2 ROTATE="0" MOREROWS="0"Allows computers to Remote Program Load correctly with DOS 5 and later.The current version of the DOSGEN utility also provides the same functionality as the RPLFIX utility.COLNAME=1 ROTATE="0" MOREROWS="0"RPLODI.COMCOLNAME=2 ROTATE="0" MOREROWS="0"The DOS TSR acts as an interface between the older type of Remote Boot PROM and Novell ODI LAN drivers. Use this file only if the following conditions exist:MARK=BULLETYou are loading the LSLTM, ODI LAN driver, IPXODI, and NETX or VLMTM software from the boot image file. You are using the older type of Remote Boot PROM.It is not necessary for these programs to reside in the SYS:LOGIN directory. However, it recommended for ease of use and access during setup. PAGENUM=141 ID="BP133"Certain IBM Micro Channel* workstations, such as the new 386SLC, have a BIOS image file associated with them. These files are provided by the manufacturer and have a file extension of .IML.  You must create a directory called SYS:\LOGIN\IBMLAN\DCDB\IMAGES on the server and copy all of the.IML files to this directory.RENDERAS="SECT3"Bootstrap ProgramsIf any of your remote booting client workstations are using the Enhanced or IBM RPL type of Remote Boot PROM, the following bootstrap programs should reside in the SYS:LOGIN directory of the NetWare server:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"Adapter TypeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ETHER.RPLCOLNAME=2 ROTATE="0" MOREROWS="0"IBM MCA EthernetCOLNAME=1 ROTATE="0" MOREROWS="0"F1ETH.RPLCOLNAME=2 ROTATE="0" MOREROWS="0"IBM Model 25SX EthernetCOLNAME=1 ROTATE="0" MOREROWS="0"PCN2L.RPLCOLNAME=2 ROTATE="0" MOREROWS="0"IBM PC Baseband NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"RBOOT.RPLCOLNAME=2 ROTATE="0" MOREROWS="0"Adapters using Novell Boot ROM KitCOLNAME=1 ROTATE="0" MOREROWS="0"TOKEN.RPLCOLNAME=2 ROTATE="0" MOREROWS="0"IBM Token-Ring NetworkThe appropriate bootstrap program (.RPL) is downloaded to the workstation in response to a SEND.FILE.REQUEST call from the Remote Boot PROM.Together, these files offer the following features and fixes:MARK=BULLETThe ability to use BOOTCONF.SYS wildcard characters (* and ?) in specifying node addressesAlso, more than one disk image filename is allowed per node address. BOOTCONF.SYS is parsed by RPL.NLM at the NetWare server to minimize the amount of network traffic.IDREF="FM24030"See "Configuring the BOOTCONF.SYS File" on page 154 for details on how to configure for bootstrap.The ability to boot across a source routing bridgePAGENUM=142 ID="BP134"RENDERAS="SECT2"ID="FM32745"Copying Newer RPL and Boot Files to the ServerA current version of the RPL and Boot files are stored in the RPL directory on CLASS=DISKNetWare Client for DOS and Windows Disk 2.Copy these files to the LOGIN directory on a server by completing the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Expand and copy the contents of the RPL directory from CLASS=DISKNetWare Client for DOS and Windows Disk CLASS=DISK2 to the LOGIN directory on a NetWare or RPL server.To expand a set of files, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:\path\ *.* destination_drive:\path MOREINFO="NONE"<Enter>For example, to expand and copy the files within the RPL directory on 
CLASS=DISKNetWare Client for DOS and Windows Disk 2 to the SYS:LOGIN or LOGIN directory, you could type the following for a NetWare server:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:RPL\*.* F:\LOGIN MOREINFO="NONE"<Enter>or type the following for an RPL server:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:RPL\*.* C:\LOGIN MOREINFO="NONE"<Enter>RENDERAS="SECT1"ID="FM34560"Making a Boot Image File 
DisketteMaking a IDXID="w11236"BOOK="_idx" COLLECTION="nw41" TIDREF="i876"
boot image file IDXID="w11237"BOOK="_idx" COLLECTION="nw41" TIDREF="i1136"
diskette requires you to do the following:MARK=BULLETFormat a bootable diskette.Create or copy required files to the bootable diskette.RENDERAS="SECT2"Formatting a Bootable DisketteYou need to make a DOS bootable diskette that is used to create an image file on the server.PAGENUM=143 ID="BP135"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Format a floppy diskette using the DOS FORMAT /S command by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"FORMAT A:/S MOREINFO="NONE"<Enter>This copies DOS system files to the diskette for booting.PERFORMANCE="REQUIRED"Ensure that the COMMAND.COM file was copied to the floppy diskette by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DIR A:*.* MOREINFO="NONE"<Enter>A list of all the files on the floppy diskette appears.RENDERAS="SECT2"Creating or Copying 
Required FilesThe following 
files are IDXID="w11238"BOOK="_idx" COLLECTION="nw41" TIDREF="i878"
required for each boot image file diskette:MARK=CHECKBOXAUTOEXEC.BATThe IDXID="w11239"BOOK="_idx" COLLECTION="nw41" TIDREF="i358"
AUTOEXEC.BAT file should include the following lines:FORMAT="LINESPECIFIC"MOREINFO="NONE"@echo off
set comspec = f:\command.com
lsl
rplodi.com [Required for "older" type PROM only.]
LAN_driver.com
ipxodi
vlmIf you are using an "older" type of Remote Boot PROM, you must load the RPLODI.COM file after the LSL.COM file and before the LAN driver.  If you are creating more than one boot image file diskette, rename the AUTOEXEC.BAT file on the bootable diskette for each remote workstation to a unique filename, such as DOS1.BAT. IDREF="FM11113"See "Creating Multiple Remote Boot Disk Image Files" on page 148 for more information.COMMAND.COMEnsure that the correct COMMAND.COM file exists on the bootable diskette for the particular DOS version you want running on the remote workstations.PAGENUM=144 ID="BP136"To check the version, check the file date or boot a workstation with the boot image file diskette and then run the DOS VER command.CONFIG.SYSCreate aIDXID="w11240"BOOK="_idx" COLLECTION="nw41" TIDREF="i768"
 system configuration file. Include the following line in the file:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"lastdrive = zMARK=CHECKBOXNET.CFGCreate a IDXID="w11241"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
network configuration file. The following is an example of a NET.CFG file for a Novell NE2000TM Ethernet board:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   port 300
   int 3
   frame ethernet_802.2FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   netware protocols = nds,bind,pnw
   preferred server = server_name
   first network drive = f
   show dots = onYou can copy the NET.CFG file directly from a client workstation directory (the default is C:\NWCLIENT) to your boot diskette.You might need to modify the Link Driver section to match your board settings if they differ from the settings used on the client workstation.  After the LAN driver is loaded into memory, you can use any frame type available for your type of network. Place a line after the primary frame type for any other frame types.NetWare Client and DOS system filesThe following files must exist on the boot image file diskette. You must create the AUTOEXEC.BAT and CONFIG.SYS files, and copy or create the NET.CFG file, manually.PAGENUM=145 ID="BP137"AUTOEXEC.BAT BIND.VLM (For NetWare 2 and NetWare 3TM networks only) COMMAND.COM CONFIG.SYS CONN.VLM FIO.VLM GENERAL.VLM IPXNCP.VLM IPXODI.COM LSL.COM NDS.VLM (For NetWare 4TM networks only) NET.CFG network_board_driver.COM NETX.VLM NWP.VLM PNW.VLM PRINT.VLM REDIR.VLM RPLODI.COM (Use with "old" PROM type only) TRAN.VLM SECURITY.VLM VLM.EXEYou can copy the NetWare Client and DOS system files directly from a client workstation directory (the default is C:\NWCLIENT) to your boot diskette.After you have made a boot image file diskette, you need to create a remote boot disk image file on a server by running the DOSGEN utility from a connected workstation.IDREF="FM11113"See "Creating Multiple Remote Boot Disk Image Files" on page 148 for more information.RENDERAS="SECT1"ID="FM57991"Creating Remote Boot Disk Image FilesYou need to IDXID="w11242"BOOK="_idx" COLLECTION="nw41" TIDREF="i878"
create a remote boot disk image file on a NetWare server for the client workstation you want to remote boot.PAGENUM=146 ID="BP138"RENDERAS="SECT2"PrerequisitesBefore you create boot disk image files on the server, you should have the following:MARK=CHECKBOXA client workstation logged in to the server you will create the disk images onA drive mapped to SYS:LOGINA search drive mapped to SYS:SYSTEMRights to the LOGIN and SYSTEM directories(Conditional: if you are using an enhanced Boot PROM) A current copy of the .RPL files located in the LOGIN directory on the serverIDREF="FM16110"See "Ensuring That the Required Files Are in the Appropriate Directories" on page 140.A copy of the remote boot image file diskette inserted into a floppy drive on the workstation you will do the setup onIf all of the remote boot workstations use the same boot configuration, create a single boot image file for all the workstations. IDREF="FM86870"See "Creating a Single Remote Boot Disk Image File" on page 146.If you have remote boot workstations that require unique boot configurations, create multiple boot image files for each workstation that has special requirements. IDREF="FM11113"See "Creating Multiple Remote Boot Disk Image Files" on page 148.RENDERAS="SECT2"ID="FM86870"Creating a Single Remote Boot 
Disk Image FileYou must create a IDXID="w11243"BOOK="_idx" COLLECTION="nw41" TIDREF="i878"
boot image file on the NetWare server in order for a remote boot or RPL remote workstation to boot from a network server.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Load the NetWare Client software.PERFORMANCE="REQUIRED"Log in.
PAGENUM=147 ID="BP139"MARK=BULLETIf you are logging in to a NetWare 2 or NetWare 3 server, use the name SUPERVISOR.If you are logging in to a NetWare 4 network, use the name ADMIN or a username with ADMIN equivalency.PERFORMANCE="REQUIRED"Enter a password (if needed).PERFORMANCE="REQUIRED"Map the next drive to SYS:LOGIN by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:LOGIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Map the next search drive to SYS:SYSTEM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=SYS:SYSTEM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the LOGIN directory. For example, if you mapped network drive G: to LOGIN, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Insert the prepared bootable diskette into a floppy disk drive on the workstation.IDREF="FM34560"See "Making a Boot Image File Diskette" on page 142 for information and procedures on preparing a bootable diskette.PERFORMANCE="REQUIRED"Run the 
IDXID="w11244"BOOK="_idx" COLLECTION="nw41" TIDREF="i1199"
DOSGEN program.For example, if you inserted the bootable diskette into drive A:, you would type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSGEN A:MOREINFO="NONE" <Enter>Your screen should show a listing similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Floppy Type: 3.1/2 inch 1.44 MB
MOREINFO="NONE"Total Floppy Space 2880 Sectors
MOREINFO="NONE"Transferring Data (2880 Sectors) to "NET$DOS.SYS"The DOSGEN utility creates a disk image file called NET$DOS.SYS (a copy of the files on the boot diskette) in the LOGIN directory. 
PAGENUM=148 ID="BP140"PERFORMANCE="REQUIRED"Copy the AUTOEXEC.BAT file from the boot diskette to the LOGIN directory on volume SYS: and all programs you want to run after the VLM.EXE file.You might get a "Batch file missing" error when you log in if the AUTOEXEC.BAT file is not copied to 
both the LOGIN directory and the user's login directory.PERFORMANCE="REQUIRED"Flag the NET$DOS.SYS file in the SYS:LOGIN directory as Shareable by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG NET$DOS.SYS SH MOREINFO="NONE"<Enter>Flagging the NET$DOS.SYS file as Shareable ensures that the file is not locked by another workstation when booting. PERFORMANCE="REQUIRED"Boot the remote workstations.IDREF="FM88057"See "Booting Remote Workstations" on page 156 for more information.RENDERAS="SECT2"ID="FM11113"Creating Multiple 
Remote Boot Disk Image FilesYou must create different IDXID="w11245"BOOK="_idx" COLLECTION="nw41" TIDREF="i878"
boot image files on the NetWare server for each RPL remote workstation that requires a unique boot file. The "old" or Novell IPX Remote Boot PROM does not support multiple boot disk image files.This requires you to create an individual remote boot image file diskette for each unique configuration.. IDREF="FM86870"See "Creating a Single Remote Boot Disk Image File" on page 146 for details and procedures.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Load the NetWare Client software.PERFORMANCE="REQUIRED"Log in.
MARK=BULLETIf you are logging in to a NetWare 2 or NetWare 3 server, use the name SUPERVISOR.If you are logging in to a NetWare 4 network, use the name ADMIN or a username with ADMIN equivalency.PERFORMANCE="REQUIRED"Enter a password (if needed).PERFORMANCE="REQUIRED"Map the next drive to SYS:LOGIN by typing
PAGENUM=149 ID="BP141"FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:LOGIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Map the next search drive to SYS:SYSTEM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=SYS:SYSTEM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the system LOGIN directory. For example, if you mapped network drive G: to LOGIN, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Create an AUTOEXEC.BAT file in the system LOGIN directory that contains only a line with twelve spaces in it (use the 
MOREINFO="NONE"<Spacebar>).Create this file with an ASCII text editor and save the file in the LOGIN directory on your server.PERFORMANCE="REQUIRED"Create a subdirectory in the system LOGIN directory for each DOS version that you want to create a boot image file for.PERFORMANCE="REQUIRED"Copy the operating system files for each DOS version to the appropriate subdirectory using the DOS COPY command.Do not use the install program to copy the DOS files to the server.PERFORMANCE="REQUIRED"Insert one of the prepared bootable diskettes into a floppy disk drive on the workstation.IDREF="FM34560"See "Making a Boot Image File Diskette" on page 142 for information and procedures on preparing a bootable diskette.PERFORMANCE="REQUIRED"Use the DOS REN command to rename the AUTOEXEC.BAT file on the bootable diskette to a unique name for a bootable diskette in drive A: by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"REN A:\AUTOEXEC.BAT unique_name.BAT MOREINFO="NONE"<Enter>For example, you could rename the AUTOEXEC.BAT file for the first workstation to DOS1.BAT by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"REN A:\AUTOEXEC.BAT DOS1.BAT MOREINFO="NONE"<Enter>The following figure illustrates this process.
PAGENUM=150 ID="BP142"LABEL="1-1" FLOAT="0"Renaming the AUTOEXEC.BAT File for Multiple Remote Boot Image FilesFILEREF="c41ug28a.tif"PERFORMANCE="REQUIRED"Copy the renamed .BAT file (DOS1.BAT, in this example) from the bootable diskette to the system LOGIN directory and home directory for each user that will use the workstation with this configuration.The following figure illustrates this process.LABEL="1-2" FLOAT="0"Copying the Renamed .BAT File for Multiple Remote Boot Image FilesFILEREF="c41ug29a.tif"PERFORMANCE="REQUIRED"Create a new AUTOEXEC.BAT file on each boot diskette to run the renamed batch file.Create this file with an ASCII text editor and save the file on the bootable diskette.The following figure illustrates this process.
PAGENUM=151 ID="BP143"LABEL="1-3" FLOAT="0"Creating a New AUTOEXEC.BAT File for Multiple Remote Boot Image FilesFILEREF="c41ug30a.tif"PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the system LOGIN directory. For example, if you mapped network drive G: to LOGIN, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Use the 
IDXID="w11246"BOOK="_idx" COLLECTION="nw41" TIDREF="i1199"
DOSGEN utility to create a uniquely named .SYS file in the system LOGIN directory for each bootable diskette.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM18785"From the SYS:LOGIN directory (and with the bootable diskette in the disk drive), run the DOSGEN utility by typing the following for each boot diskette:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSGEN drive_letter:unique.SYS_file MOREINFO="NONE"<Enter>For example, if you inserted the boot diskette into drive A: and created a unique .SYS file named DOS1.SYS, you would type the following command:FORMAT="LINESPECIFIC"MOREINFO="NONE"DOSGEN A:DOS1.SYS MOREINFO="NONE"<Enter>Your screen should show a listing similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"Floppy Type: 3.1/2 inch 1.44 MB
MOREINFO="NONE"Total Floppy Space 2880 Sectors
MOREINFO="NONE"Transferring Data (2880 Sectors) to "DOS1.SYS"PERFORMANCE="REQUIRED"ID="FM34177"Record the network number and node address of the workstation that will use the disk image file you just created.You need the information to create the BOOTCONF.SYS file.PAGENUM=152 ID="BP144"When you have finished running the DOSGEN utility for two boot diskettes, a list of the image files should look similar to the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"DOS1.SYS Network#=DOC20 Node=5a003b77DOS2.SYS Network#=DOC20 Node=1b0276a3PERFORMANCE="REQUIRED"Repeat Steps 
IDREF="FM18785"15a and 
IDREF="FM34177"15b for each boot diskette.PERFORMANCE="REQUIRED"Create a new, or modify the existing, BOOTCONF.SYS file in the SYS:LOGIN directory.The BOOTCONF.SYS file indicates to the client workstations which of the multiple boot image files to use. Create this file with an ASCII text editor and save the file to the SYS:LOGIN directory.The following figure illustrates this process.LABEL="1-4" FLOAT="0"Creating a BOOTCONF.SYS file for Multiple Remote Boot Image FilesFILEREF="c41ug33a.tif"The BOOTCONF.SYS file must have the following to function properly:
MARK=BULLETAll custom remote boot disk image filenames (do not include the default NET$DOS.SYS file)The network address and node address of each workstation that uses the customized boot image filesPERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Change to the SYS:LOGIN directory.PERFORMANCE="REQUIRED"Create or modify the BOOTCONF.SYS file to add information for each new remote boot image file.
PAGENUM=153 ID="BP145"Include a line for each remote boot image file you created, using an entry format containing the following information:MARK=BULLETThe number zero and the letter x (0x)The network address (the address must be 8 character in length. Use zeros as leader.)A comma (,)The node or station address the address must be 12 character in length. Use zeros as leader.)An equal sign (=)The boot disk image filename An example for two boot diskettes follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"00xDOC20,00005a003b77=dos1.sys,gns
00xDOC20,00001b0276a3=dos2.sys,gnsYou can use wildcard characters in the BOOTCONF.SYS file to specify one disk image file for multiple node addresses and allow for multiple lines per node address. IDREF="FM24030"See "Configuring the BOOTCONF.SYS File" on page 154 for more information.PERFORMANCE="REQUIRED"Copy the AUTOEXEC.BAT file from the boot diskette to the login directory specified in each user's login script.You might get a "Batch file missing" error when you log in if the AUTOEXEC.BAT file is not copied to the user's login directory.PERFORMANCE="REQUIRED"Flag the .SYS and .BAT files in the SYS:LOGIN directory as Shareable by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"FLG *.SYS SH MOREINFO="NONE"<Enter>
FLAG *.BAT SH MOREINFO="NONE"<Enter>Flagging the .SYS and .BAT files as Shareable ensures that the files are not locked by another workstation when booting. PERFORMANCE="REQUIRED"Boot the remote workstations.IDREF="FM88057"See "Booting Remote Workstations" on page 156 for details.
PAGENUM=154 ID="BP146"RENDERAS="SECT1"ID="FM24030"Configuring the BOOTCONF.SYS IDXID="w11247"BOOK="_idx" COLLECTION="nw41" TIDREF="i3756"
FileWhen RPL loads, it searches the LOGIN directory of a NetWare server for a BOOTCONF.SYS file. If it finds the file, it reads the file into a memory buffer so that it can parse the file when a FIND frame is received from a workstation.BOOTCONF.SYS parsing is done by the RPL utility, not by the bootstrap program, to minimize the amount of traffic on the network during the RPL process. RENDERAS="SECT2"Using Wildcard Characters in BOOTCONF.SYSWildcard characters (* and ?) are allowed in the line specifying the node address of the client workstation. This allows the network supervisor more flexibility in building the BOOTCONF.SYS file. The rules for these wildcard characters are as follows:MARK=BULLETUse the asterisk (*) character to specify a range of digits in the node address.For example, if the node address of the client workstation is 10005A123456, it can be specified as 0x*123456 in BOOTCONF.SYS. In this example, RPL matches the node address with any node address that ends in 123456.Only one asterisk (*) is allowed in the node address.Use the question mark character to specify any single digit in the node address.Using the previous example, the node address could be specified as 0x??????123456, which is equivalent to 0x*123456.You can use wildcard characters to specify a default disk image file for all client workstations on the network that do not have a specific disk image file.You do this by placing one of these lines as the last line in the BOOTCONF.SYS file:FORMAT="LINESPECIFIC"MOREINFO="NONE"0x* = DEFAULT.SYS FORMAT="LINESPECIFIC"MOREINFO="NONE"0x???????????? = DEFAULT.SYS
PAGENUM=155 ID="BP147"Either one of these lines matches all client workstation node addresses. The DEFAULT.SYS (or any name you choose) disk image file is generated by DOSGEN, like any disk image file.RENDERAS="SECT2"Specifying Additional 
Multiple Disk Image Files per Node AddressEach line in the BOOTCONF.SYS file that contains a node address can specify more than one disk image filename, which should be separated by one or more blank characters and which must all fit on one line.You can enter up to ten disk image filenames for each node address in BOOTCONF.SYS file.This option is for Enhanced Boot PROMs only. When the client workstation is started, the bootstrap program prompts you for the disk image file to boot.For example, if a client workstation's node address is 10005A123456, the lineFORMAT="LINESPECIFIC"MOREINFO="NONE"0x10005a123456 = ONE.SYS TWO.SYS THREE.DOSin the BOOTCONF.SYS file causes the bootstrap program to display the following on the screen:FORMAT="LINESPECIFIC"MOREINFO="NONE"ONE.SYS TWO.SYS THREE.DOSThe bootstrap program then uses NetWare Core ProtocolTM calls to open the selected disk image files.If any of the filenames do not exist, the screen displays the following:FORMAT="LINESPECIFIC"MOREINFO="NONE"Unable to OPEN Disk Image FileThen the bootstrap program retries the operation.RENDERAS="SECT2"Allowing Multiple Lines per Node AddressThis feature is convenient for specifying multiple parameters on the node address line.PAGENUM=156 ID="BP148"To use this feature, place an ASCII colon (:) at the end of the line. It must be preceded by at least one ASCII blank. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"0x10005a460025 = NET$DOS.SYS DOS1.SYS :
DOS2.SYSRENDERAS="SECT1"ID="FM88057"Booting Remote WorkstationsBoot a remote workstation by completing the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Ensure that the remote booting hardware is installed according to manufacturer's instructions.IDREF="FM80906"See "Installing a Remote Boot PROM Chip Certified by Novell" on page 135 for more information.PERFORMANCE="REQUIRED"Ensure that the boot server is turned on and has the RPL.NLM or RLP.COM program loaded. IDREF="FM28422"See "Loading the RPL.NLM Program" on page 137 or 
IDREF="FM20042""Loading the RPL.COM File" on page 138 for more information.PERFORMANCE="REQUIRED"(Conditional) If you are attaching to a NetWare server across a source routing bridge, ensure that the RPL server is turned on and the RPL.COM file is loaded.IDREF="FM20042"See "Loading the RPL.COM File" on page 138 for more information.PERFORMANCE="REQUIRED"Turn on the diskless workstation.PERFORMANCE="REQUIRED"Log in to the network or server.IDREF="FM57667"See "Logging In from a NetWare Client Workstation" on page 169 for details.If you are using older Remote Boot PROMs, IDREF="FM44901"see "Determining the Remote Boot PROM Type" on page 135 for information.If you experience any problems booting, IDREF="FM83814"see "Troubleshooting RPL with Older Remote Boot PROMs" on page 159 for more information. PAGENUM=157 ID="BP149"RENDERAS="SECT1"ID="FM22898"Using the RPLFIX.COM UtilityThe IDXID="w11248"BOOK="_idx" COLLECTION="nw41" TIDREF="i3758"
RPLFIX
 utility allows workstations using the older IDXID="w11249"BOOK="_idx" COLLECTION="nw41" TIDREF="i3758"
Remote Boot PROM to boot properly with DOS 5.0 or later. Earlier versions of DOS do not require you to run this utility. The RPLFIX utility modifies the boot image files, so you need to run it only once per image file.Do not use the RPLFIX.COM utility with IBM RPL PROMs. The .RPL bootstrap programs are already RPLFIX aware.Run the RPLFIX utility on the image files if the workstation hangs during the boot process or if you are using DOS 5.0 or later. IDREF="FM83814"See "Troubleshooting RPL with Older Remote Boot PROMs" on page 159 for more information on troubleshooting diskless workstations.RENDERAS="SECT2"PrerequisitesBefore you run the RPLFIX utility, you should have the following:MARK=CHECKBOXA client workstation logged in to the server you will create the disk images onA drive mapped to SYS:LOGINRights to the SYS:LOGIN directoryA copy of the RPLFIX.COM file located in the SYS:LOGIN directory.IDREF="FM32745"See "Copying Newer RPL and Boot Files to the Server" on page 142 for more information.Boot image files for the diskless workstations already created in the SYS:LOGIN directory.IDREF="FM57991"See "Creating Remote Boot Disk Image Files" on page 145 for more information.RENDERAS="SECT2"ProcedureYou must run the RPLFIX utility on each boot image file used by a workstation using an older Remote Boot PROM or DOS 5.0 or later.PAGENUM=158 ID="BP150"PERFORMANCE="REQUIRED" Load the NetWare Client software.PERFORMANCE="REQUIRED"Log in.
MARK=BULLETIf you are logging in to a NetWare 2 or 3 server, use the name SUPERVISOR.If you are logging in to a NetWare 4 network, use the name ADMIN or a username with ADMIN equivalency.PERFORMANCE="REQUIRED"Enter a password (if needed).PERFORMANCE="REQUIRED"Map the next drive to SYS:LOGIN by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N SYS:LOGIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the LOGIN directory. For example, if you mapped network drive G: to LOGIN, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the LOGIN directory where the boot image files are located.PERFORMANCE="REQUIRED"Run the RPLFIX utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"RPLFIX [drive_letterMOREINFO="NONE":] boot_image_file MOREINFO="NONE"<Enter>Replace 
drive_letter with the drive letter where the image file is located. Replace
 boot_image_file with the name of the file created with the DOSGEN program.If you created a single boot image file, the file is named NET$DOS.SYS. If you created multiple boot image files, look for all the files in the SYS:LOGIN directory with a .SYS extension. Therefore, for example, if you created a single boot image file in the SYS:LOGIN directory on drive G:, you would type the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"RPLFIX G:NET$DOS.SYS MOREINFO="NONE"<Enter>
PAGENUM=159 ID="BP151"PERFORMANCE="REQUIRED"Flag the boot image files you used the RPLFIX utility on as Shareable by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG *.SYS SH MOREINFO="NONE"<Enter>Flagging the boot files as Shareable ensures that the files are not locked by another workstation when booting. PERFORMANCE="REQUIRED"Boot the remote workstations.IDREF="FM88057"See "Booting Remote Workstations" on page 156 for more information.RENDERAS="SECT1"ID="FM83814"Troubleshooting IDXID="w11250"BOOK="_idx" COLLECTION="nw41" TIDREF="i3756"
RPL with Older IDXID="w11251"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
Remote Boot PROMsMARK=BULLETIf you get the error message "MOREINFO="NONE"Error opening boot disk image file," you should do one or all of the following:MARK=BULLETPlace a copy of the disk image file on the other server that your workstation is logging in to. You are probably attaching to another server that does not contain the remote boot disk image file.Run the RPLFIX utility. IDREF="FM22898"See "Using the RPLFIX.COM Utility" on page 157 for more information.Ensure that the BOOTCONF.SYS file is configured correctly. IDREF="FM24030"See "Configuring the BOOTCONF.SYS File" on page 154 for more information.If you get the error message "MOREINFO="NONE"Batch file missing," make sure the AUTOEXEC.BAT or unique .BAT file is in both the SYS:LOGIN directory and the user's login directory for each user using a remote boot workstation.If a client workstation using a Remote Boot PROM doesn't boot, test the boot image file diskette (bootable diskette) for that workstation.Insert the bootable diskette in a floppy drive on the remote boot client workstation or another workstation with a floppy disk drive.Ensure that the client workstation you test the diskette on has the same hardware and software configurations as the remote boot workstation does.Run the DOSGEN /V parameter to ensure that the disk image file is not corrupt.PAGENUM=160 ID="BP152"If a client workstation using a Remote Boot PROM doesn't boot, ensure that the type of Remote Boot PROM used supports the frame type used on your network.The "old" type of Remote Boot PROM does not support the default 802.2 used with current Ethernet networks.IDREF="FM44901"See "Determining the Remote Boot PROM Type" on page 135 for information about what frame types are supported.If a client workstation hangs after loading the LAN driver, replace the current LAN driver with a copy of the RPLODI.COM file and modify the change in the STARTNET.BAT file.If a client workstation hangs while loading DOS, run the RPLFIX utility.If you get the error message "MOREINFO="NONE"Insert disk with \COMMAND.COM in drive A:," set the DOS COMSPEC parameter to drive F: (the default LOGIN directory) and copy the COMMAND.COM file to the LOGIN directory.RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for RPL COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Options," in NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using command line options RPLCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference," in NetWare Client for DOS and MS Windows Technical ReferenceLABEL="7"PAGENUM=161 ID="BP153"ID="FM41619"Setting Up NetWare Client Workstations to Log InRENDERAS="SECT1"OverviewThis chapter explains how to modify your NET.CFG file to simplify logging in to a NetWare® network.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM51968"Modifying the NET.CFG File for Logging In to NetWare 2 and NetWare 3 COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM51968"162COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94978"Modifying the NET.CFG File for Logging In to NetWare 4 COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94978"163COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM98317"Understanding Logging In to NetWare Directory Services COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98317"165RENDERAS="SECT1"IntroductionProper client workstation setup can make 
logging in to the network virtually transparent. This chapter assumes that the following tasks are completed:MARK=BULLETA User object or user account is created for each userNetWare ClientTM software is installedA home directory is created for each userUsers with NetWare 2 or 3 client workstation connections to a Netware 4 network must have a User object created in the container where the bindery-based server's context is set. (Bindery services is set by default for every NetWare 4 server that is installed.) NetWare 2 or 3 users do not need to know their context because they log in to the server rather than to the Directory tree.PAGENUM=162 ID="BP154"RENDERAS="SECT1"ID="FM51968"Modifying the NET.CFG File for 
Logging In to NetWare 2 and NetWare 3IDXID="w11252"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
When logging in to a NetWare 2 or NetWare 3TM network, you attach to an 
individual server. Then you make additional attachments to other servers that you have a user account on.RENDERAS="SECT2"Using the Preferred Server ParameterIDXID="w11253"BOOK="_idx" COLLECTION="nw41" TIDREF="i3371"
Use the Preferred Server parameter in the NET.CFG file to direct the client software to the server where your user information is located.For networks with multiple servers, this parameter is very useful for speeding up logging in to the network. This parameter also allows you to log in with only your username.The parameter is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"preferred server = server_nameDo not use both the Preferred Server and Preferred Tree parameters simultaneously. The second parameter will override the first.RENDERAS="SECT3"Adding the Preferred Server Parameter to the NET.CFG FilePERFORMANCE="REQUIRED"Open your NET.CFG file in a text editor.Your client's NET.CFG file was copied to the target directory for DOS files specified during software installation.PERFORMANCE="REQUIRED"Under the NetWare DOS RequesterTM heading, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred server=server_nameFor example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred server=mktsalesRENDERAS="SECT3"Example of the IDXID="w11254"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NetWare DOS 
Requester SectionFORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w11255"BOOK="_idx" COLLECTION="nw41" TIDREF="i2735"
NetWare DOS Requester
   Preferred Server=mktsales
PAGENUM=163 ID="BP155"   First Network Drive=fRENDERAS="SECT1"ID="FM94978"Modifying
 the NET.CFG File for Logging In to NetWare 4IDXID="w11256"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
When IDXID="w11257"BOOK="_idx" COLLECTION="nw41" TIDREF="i2498"
logging in to NetWare 4TM, you don't attach to 
individual servers as with previous versions of NetWare, but you log in to the entire network.With your IDXID="w11258"BOOK="_idx" COLLECTION="nw41" TIDREF="i1156"
Distinguished Name (DN), you can 
simplify the login process by adding information to your client workstation's 
NET.CFG file. To do this, you need to add lines under the NetWare DOS Requester heading in the NET.CFG file.If you add lines for the following parameters, you will not need to type your IDXID="w11259"BOOK="_idx" COLLECTION="nw41" TIDREF="i1156"
Distinguished Name each time you log in to the network after booting your client workstation:MARK=BULLETName ContextPreferred TreeYou must know your name context before making these modifications, or you cannot add entries for the parameters. For information about setting your client workstation's name context, IDREF="FM98317"see "Understanding Logging In to NetWare Directory Services" on page 165.RENDERAS="SECT2"Using the Name Context 
ParameterBy using the name context parameter in the IDXID="w11260"BOOK="_idx" COLLECTION="nw41" TIDREF="i2577"
NET.CFG file, you inform the NetWare DOS Requester of your name context within the Directory tree. The LOGIN utility can then locate your User object and connect you to the network. The parameter is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"name context="name_context"The default for this parameter is at the root, which might cause confusion if duplicate usernames exist within a Directory tree. PAGENUM=164 ID="BP156"If you are using an earlier version of the NetWare shell on your client workstation, the Name Context parameter is invalid. NetWare 4 creates a User object for client workstations using NetWare shell files in the same container as the NetWare Server object that you will log in to.  Bindery services is set by default for every NetWare Server object that is installed. Therefore, users log in directly to a server rather than to the Directory tree.RENDERAS="SECT2"Using the Preferred Tree ParameterIDXID="w11261"BOOK="_idx" COLLECTION="nw41" TIDREF="i3374"
By using the Preferred Tree parameter in the NET.CFG file, you direct the NetWare DOS Requester to the Directory tree where your name context is set. The LOGIN utility can then save time by searching only the preferred Directory tree.Add this parameter to your NET.CFG file if you are using NetWare 4 on a network with multiple Directory trees. The parameter is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"preferred tree=tree_nameThe default for this parameter is at the root. Because of this, it is important that this parameter is used to avoid confusion if duplicate usernames exist within separate Directory trees.Do not use both the Preferred Server and Preferred Tree parameters simultaneously. The second parameter will override the first.RENDERAS="SECT2"ID="FM49232"Modifying
 the 
NetWare DOS Requester OptionIDXID="w11262"BOOK="_idx" COLLECTION="nw41" TIDREF="i2735"
The Netware DOS Requester option allows you to configure the way your client workstation software interacts with the network.To modify this option's section in your NET.CFG file, complete these steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with a text editor.The NET.CFG file is located in your client workstation directory. This is the destination directory specified during client software installation.PERFORMANCE="REQUIRED"Under the NetWare 

DOS Requester heading, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    name context="complete_name"
PAGENUM=165 ID="BP157"For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    name context="esayers.sales.novell us"PERFORMANCE="REQUIRED"(Conditional) If your network has multiple Directory trees, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred tree=preferred_tree_nameFor example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"    preferred tree=novell usRENDERAS="SECT2"Example of the IDXID="w11263"BOOK="_idx" COLLECTION="nw41" TIDREF="i2900"
NetWare DOS Requester SectionFORMAT="LINESPECIFIC"MOREINFO="NONE"NetWare DOS Requester
   name context "Esayers.sales.novell us"
   preferred tree=novell us
   first network drive=fRENDERAS="SECT1"ID="FM98317"Understanding Logging In to NetWare Directory ServicesNetWare Directory ServicesTM architecture makes 
logging in to the network convenient.User information resides in a global database. Each user is assigned a position, or context, within the global database that informs the network where the user's User object is located in relationship to the entire network.In the NET.CFG file, the IDXID="w11264"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
context of your User object is referred to as your name context.Your User object is given a name called its common name. When you log in to the network, the LOGIN utility must know where your particular User object is located---its context.Your User object's context also forms its IDXID="w11265"BOOK="_idx" COLLECTION="nw41" TIDREF="i719"Distinguished Name. The path from the object to the root of the tree constitutes the object's Distinguished Name, which is unique---different from all other objects' Distinguished Name.Your User object's Distinguished Name is a IDXID="w11266"BOOK="_idx" COLLECTION="nw41" TIDREF="i1156"
bottom-up traversal of the tree, from the object up to the root.PAGENUM=166 ID="BP158"RENDERAS="SECT2"Using the Correct Format of Your Distinguished Name for Logging In to the NetworkIDXID="w11267"BOOK="_idx" COLLECTION="nw41" TIDREF="i1157"
When you use a IDXID="w11268"BOOK="_idx" COLLECTION="nw41" TIDREF="i1156"
Distinguished Name of a User object, its common name is listed first, followed by a period (.); then the name of the Organizational Unit (a container object), also followed by a period; and on up through the Organization object name (and the Country object name, if used). So your User object's Distinguished Name could be represented byTYPE="VERT"Common name.Organizational Unit name.Organization object name.Country object nameThe actual structure of your Distinguished Name depends on the way your network is defined.RENDERAS="SECT2"Specifying the Name Type of an ObjectIDXID="w11269"BOOK="_idx" COLLECTION="nw41" TIDREF="i2591"
A name type distinguishes the class of object that you are referring to, such as a User object or an Organizational Unit object.For example, you could expressIDXID="w11270"BOOK="_idx" COLLECTION="nw41" TIDREF="i1157"
ESAYERS.SALES.NOVELL US asIDXID="w11271"BOOK="_idx" COLLECTION="nw41" TIDREF="i1157"
CN=ESAYERS.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.When you move from one container object to another, you must always include the name type of an object when typing out its Distinguished Name or context.You also must always include the name types of the objects in Distinguished Names or contexts when you include the Country object in your Directory tree. Therefore, even when you refer to objects located in the same container object, you must designate their name types (CN, OU, or O).PAGENUM=167 ID="BP159"RENDERAS="SECT2"Changing Your ContextWhen you move from one container object to 
another, youIDXID="w11272"BOOK="_idx" COLLECTION="nw41" TIDREF="i611"change contexts. Whenever you IDXID="w11273"BOOK="_idx" COLLECTION="nw41" TIDREF="i2577"
change IDXID="w11274"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
contexts, you might need to indicate the Distinguished Name of the object you are changing context to.For example, in the following figure, if the User object named Brent located in Test.MedTec wants information from the Server object called SERVER1 that is located in the context Development.MedTec, then Brent must refer to the context of the Server object when changing context to access SERVER1.FILEREF="c41ug22a.tif"Once you are logged in, use the following utilities to change the context of your User object within the Directory tree:MARK=BULLETThe CX utility at the DOS command lineThe "Change Context" option in the NETUSER utility for DOSThe "Drive Connections" window in NetWare User Tools for MS Windows RENDERAS="SECT2"Logging In to Your 
ContextPERFORMANCE="REQUIRED"TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN context MOREINFO="NONE"<Enter>
PAGENUM=168 ID="BP160"Replace 
context with your 

Distinguished Name. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN ESAYERS.SALES.NOVELL US MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enter your user password (if required).RENDERAS="SECT1"Additional InformationFor more details, see Chapter 1, "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services," in Introduction to NetWare Directory Services.LABEL="8"PAGENUM=169 ID="BP161"ID="FM57667"Logging In from a NetWare Client WorkstationRENDERAS="SECT1"OverviewThis chapter explains how to log in to a NetWare®
 server or network from a NetWare client workstation in the following ways.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM79231"Logging In from the DOS Prompt COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM79231"170COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74516"Logging In to a NetWare 2 or NetWare 3 Network  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74516"171COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM91951"Logging In to a NetWare 4 Network COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91951"172COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM68818"Logging In to NetWare 4 with a NetWare Bindery Connection COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM68818"172COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM96378"Logging In from MS Windows COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96378"173COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM62132"Logging Out of a NetWare Server or Network  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM62132"174RENDERAS="SECT1"IntroductionLogging in to a NetWare server or network is the procedure that provides your client workstation 
access to network resources such as network directories, printers, and applications.When you initiate a login request, the NetWare operating system looks for your specific security rights and then prompts you to enter a password.All security information is placed into the NetWare server's connection list and your client workstation is logged in.At this point, the LOGIN utility executes one or more login scripts (which initialize environment variables, maps network drives, etc.).PAGENUM=170 ID="BP162"With the necessary modifications made to your NET.CFG file, you need only your username and password to log in to a preferred server for NetWare 2 and NetWare 3TM networks, or a preferred tree and name context for NetWare 4TM networks.RENDERAS="SECT1"PrerequisitesEnsure the following before logging in:MARK=CHECKBOXThe NetWare ClientTM software is loadedMARK=BULLETIf your client workstation can use an Open Data-Link InterfaceTM (ODI) network board driver, load the following software:  LSL.COM Network board driver (for example, NE2000.COM) IPXODI.COM VLM.EXEIf your client uses only a dedicated IPXTM driver (not an ODITM driver), load the following programs:  IPX.COM VLM.EXE(Conditional: if using MS Windows) The NetWare Client software has been loaded before MS Windows was loaded(Recommended) The NET.CFG file is modified for loginMARK=BULLETIf you do not modify the NET.CFG file, the Distinguished Name (complete name) for each login is required.  IDREF="FM41619"See Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161 for information.RENDERAS="SECT1"ID="FM79231"Logging In from the DOS PromptThe login program IDXID="w11275"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
connects your client workstation to a server or the network. The NetWare Client software automatically maps the first network drive of your client workstation.See the following sections for specific login procedures:PAGENUM=171 ID="BP163"MARK=BULLETIDREF="FM74516"Logging In to a NetWare 2 or NetWare 3 Network (page 171)IDREF="FM91951"Logging In to a NetWare 4 Network (page 172)IDREF="FM68818"Logging In to NetWare 4 with a NetWare Bindery Connection (page 172)RENDERAS="SECT2"ID="FM74516"Logging In to a NetWare 2 or NetWare 3 NetworkPERFORMANCE="REQUIRED"Change to the first network drive by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"F: MOREINFO="NONE"<Enter>The NetWare DOS RequesterTM software automatically maps the first network drive for your client workstation.The default drive is F:. To change the default, edit the FIRST NETWORK DRIVE parameter in your NET.CFG file.See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option," in 
NetWare Client for DOS and MS Windows Technical Reference for procedures.PERFORMANCE="REQUIRED"Log in to the network in one of the following ways:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If a default (preferred) server is set in your NET.CFG file, you can log in using only your username by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN username MOREINFO="NONE"<Enter>For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN ESAYERS MOREINFO="NONE"<Enter>IDREF="FM41619"See Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161 for more details.PERFORMANCE="REQUIRED"If a default (preferred) server is not set in your NET.CFG file, or if you want to log in to a server other than the default, 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"Enter your password (if required).
PAGENUM=172 ID="BP164"RENDERAS="SECT2"ID="FM91951"Logging In to a 
NetWare 4 
NetworkPERFORMANCE="REQUIRED"Change to the first network drive by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"F: MOREINFO="NONE"<Enter>The NetWare DOS Requester software automatically maps the first network drive for your client workstation.The default drive is F:. To change the default, edit the FIRST NETWORK DRIVE parameter in your NET.CFG file.See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option," in 
NetWare Client for DOS and MS Windows Technical Reference for procedures.PERFORMANCE="REQUIRED"Log in to the network in one of the following ways:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If your name c

ontext is set in your NET.CFG file, log in to the Directory tree using only your username by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN username MOREINFO="NONE"<Enter>For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN ESAYERS MOREINFO="NONE"<Enter>IDREF="FM41619"See Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161 for more details.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"Enter your password (if required).RENDERAS="SECT2"ID="FM68818"Logging In to NetWare 4 with a IDXID="w11276"BOOK="_idx" COLLECTION="nw41" TIDREF="i456"
NetWare 
Bindery ConnectionPERFORMANCE="REQUIRED"TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN server/username /B MOREINFO="NONE"<Enter>
PAGENUM=173 ID="BP165"Replace 
server with the name of the 

bindery server. Replace 
username with your username.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN TSMKT/ESAYERS /B MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enter your password (if required).RENDERAS="SECT1"ID="FM96378"Logging In from MS WindowsYou can use the NetWare User Tools in 
MS 
Windows to log in to NetWare 2, NetWare 3, and NetWare 4 by completing these steps.The "Login" option under NetWare User Tools for MS Windows authenticates you to NetWare Directory ServicesTM in NetWare 4 or to a NetWare server in NetWare 2 and NetWare 3 networks. It does not run a login script for your client workstation.  If you want to run a login script, your initial login should be done at the DOS command line with the LOGIN utility before loading MS Windows.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Load the NetWare User Tools (NWUSER.EXE) by choosing the "NetWare User Tools" icon from the NetWare group.The "NetWare User Tools" interface screen appears.PERFORMANCE="REQUIRED"From the menu bar, choose the "NetWare Connections" icon.The "NetWare Connections" window displays available resources.PERFORMANCE="REQUIRED"From the "Resources" list, choose the resource that you want to log in to.PERFORMANCE="REQUIRED"Choose "Login."You might be prompted to enter a password before login is completed. Choose the "Guest" radial button if you do not have an account established on the server or network that you want to connect to.
PAGENUM=174 ID="BP166"If you prefer logging in directly from MS Windows, you can simulate some login script functionality by using the "Permanent" option in the "NetWare Drive Connections" window to set up your client workstation drive mappings.RENDERAS="SECT1"ID="FM62132"Logging Out of a NetWare Server or NetworkLogging out of a NetWare server or network is the procedure that breaks the network connections and deletes drive mappings and printer port captures that were made to the network.If you log out without specifying a NetWare server name in the LOGOUT command, the client workstation's resource connections to all servers or to the network are terminated.Therefore, to log out from one server and remain attached to the other servers, specify the server name in the LOGOUT command.Also, make sure at least one of the remaining drives is mapped to the PUBLIC directory of a NetWare server that you are still attached to. Otherwise, you can't access NetWare utilities.RENDERAS="SECT2"Logging Out from DOSLog out in one of the following ways:MARK=BULLETIf you want to log out from the network or all connected servers, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGOUT MOREINFO="NONE"<Enter>If you want to log out from a specific server, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGOUT servername MOREINFO="NONE"<Enter>Replace servername with the name of the server you want to disconnect from. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGOUT TSMKT MOREINFO="NONE"<Enter>RENDERAS="SECT2"Logging Out from MS WindowsYou can use the NetWare User Tools in MS Windows to log out from NetWare 2, 3, and 4 servers or networks by completing these steps.PAGENUM=175 ID="BP167"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Load the NetWare User Tools by choosing the "NetWare User Tools" icon from the NetWare group.The "NetWare User Tools" interface screen appears.PERFORMANCE="REQUIRED"From the menu bar, choose the "NetWare Connections" icon.The "NetWare Connections" window displays available resources.PERFORMANCE="REQUIRED"Choose the resource that you want to log out from.PERFORMANCE="REQUIRED"Choose "Logout."RENDERAS="SECT1"Where to Go from HereAfter logging in, you can begin setting up your client workstation for additional networking supportCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Modify your NET.CFG file to simplify loginCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM41619"Chapter 7, "Setting Up NetWare Client Workstations to Log In," on page 161COLNAME=1 ROTATE="0" MOREROWS="0"Set up and modify your NET.CFG fileCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Improve client workstation performanceCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 1, "BOOK="ws_d2enu" COLLECTION="nw41"Optimizing the NetWare Client Software," in NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Set up network drives and directoriesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86864"Chapter 9, "Setting Up and Managing Network Drives," on page 177COLNAME=1 ROTATE="0" MOREROWS="0"Set up printing for a client workstationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94060"Chapter 10, "Setting Up Client Workstation Printing," on page 193COLNAME=1 ROTATE="0" MOREROWS="0"Set up your client workstation to support applications running in a task-switching environmentCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85167"Chapter 11, "Setting Up Network Support for Task-Switching Environments," on page 211LABEL="9"PAGENUM=177 ID="BP168"ID="FM86864"Setting Up and Managing Network DrivesRENDERAS="SECT1"OverviewThis chapter explains how to set up and manage network drives on your NetWare® client workstations.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM47043"Using NetWare Utilities to Set Up and Manage Drive MappingsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM47043"179COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM97717"The MAP UtilityCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM97717"180COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM19658"The NetWare User Tools for DOS (the NETUSER Utility) COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM19658"184COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80619"The NetWare User Tools for MS Windows (the NWUSER.EXE Program) COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80619"185COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM91120"Using Universal Naming Convention (UNC) Paths in MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM91120"188RENDERAS="SECT1"IntroductionNetWare allows you to set up and manage network drives on each client workstation. This gives client workstations the ability to store and access files and applications in a central file system. This ability is provided through drive mappings which specify particular locations within volumes and directories on the network.These drive mappings permit easier navigation of the directory structure and access to hard disks on NetWare servers and other storage media, such as, CD-ROM devices and tape drives.There are three types of drive mappings in a NetWare environment:PAGENUM=178 ID="BP169"MARK=BULLETLocal drivesPoint to disk drives installed in a client workstation. DOS reserves the first five letters (A-E) as local drive mappings.Network drivesPoint to specific volumes or directories on a network. The number of network drives you have available depends on the setting for the DOS LASTDRIVE parameter in the CONFIG.SYS file. In previous versions of the NetWare ClientTM software, the first network drive was always the first drive letter not reserved for local use. This setting was made with the DOS LASTDRIVE parameter in the CONFIG.SYS file. Because the NetWare DOS RequesterTM software is a redirector on the back end of DOS, it requires that the LASTDRIVE=Z parameter be added to the CONFIG.SYS file. The first network drive is now set in the NET.CFG file.See "FIRST NETWORK DRIVE" under "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.The NetWare DOS Requester uses the first available DOS drive after the FIRST NETWORK DRIVE parameter set in the NET.CFG.  Consequently, client workstations which accessed, for example, a LASTDRIVE = G parameter setting in their CONFIG.SYS are used to seeing drive H: as the first network drive and not the first drive letter after the last local drive letter.  To maintain compatibility with existing batch files, you might want to add, for example, the FIRST NETWORK DRIVE = H parameter setting under the NetWare DOS Requester heading in the NET.CFG file.  Otherwise, batch files assuming drive H: as the first drive must be altered.MARK=BULLETSearch drivesPoint to specific volumes or directories on a network and add the network volumes or directories to the DOS path.PAGENUM=179 ID="BP170"RENDERAS="SECT1"ID="FM47043"Using NetWare Utilities to Set Up and Manage Drive MappingsNetWare provides you with the following three utilities to set up and manage network drives and search drives for each client workstation in your network:MARK=BULLETIDREF="FM97717"The MAP UtilityA DOS text utility available in all version of NetWare.IDREF="FM19658"The NetWare User Tools for DOS (the NETUSER Utility)A DOS menu utility available only in NetWare 4 software.IDREF="FM80619"The NetWare User Tools for MS Windows (the NWUSER.EXE Program)An MS Windows graphical utility available in the NetWare Client Kits for DOS and MS Windows, and in NetWare 3.12 and NetWare 4TM software.For online help and information on available options, use the /? or /H parameter with text utilities and the MOREINFO="NONE"F1 key with menu and graphical utilities.RENDERAS="SECT2"PrerequisitesBefore you can use any of the drive mapping utilities, your client workstation requires the following:MARK=CHECKBOXA physical connection to the networkNovell DOSTM, DR DOS®, PC-DOS, or MS-DOS loaded and running(Conditional: if using MS Windows) A copy of MS Windows 3.x or Windows for Workgroups 3.11 installed and runningThe NetWare Client files loaded and runningIDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.A connection to the networkIDREF="FM57667"See Chapter 8, "Logging In from a NetWare Client Workstation," on page 169 for more information.PAGENUM=180 ID="BP171"RENDERAS="SECT2"ID="FM97717"The MAP UtilityMAP allows you to assign IDXID="w11277"BOOK="_idx" COLLECTION="nw41" TIDREF="i877"
drives to 
network directories. Use MAP toMARK=BULLETIDXID="w11278"BOOK="_idx" COLLECTION="nw41" TIDREF="i1222"
View IDXID="w11279"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
drive mappingsIDXID="w11280"BOOK="_idx" COLLECTION="nw41" TIDREF="i1222"
Create or change network or search drive mappingsIDXID="w11281"BOOK="_idx" COLLECTION="nw41" TIDREF="i612"Assign a drive to a fake root directory (for applications that must use a root directory)MAP is a NetWare workstation utility located in the SYS:PUBLIC directory. A default drive mapping should exist for the SYS:PUBLIC directory (the default is drive Z:).To use the MAP utility, you would specify the type of drive mapping and assignment you want by using the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP [option...] drive:= [volume:| path]For example, if your username is MARIA and you want to map drive F: to your home directory on file server SALES, you would type FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP F:= SALES\SYS:HOME\MARIA MOREINFO="NONE"<Enter> See the following references for more information about the MAP utility:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 2COLNAME=2 ROTATE="0" MOREROWS="0""MAP" in Using the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 3COLNAME=2 ROTATE="0" MOREROWS="0""MAP" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 4COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities ReferencePAGENUM=181 ID="BP172"RENDERAS="SECT3"Assigning Drive Mappings in a Specific OrderIn many cases, you might find it useful to map network drives in the following order:MARK=BULLETMap the first network drive to the user's home directory.If users are running MS Windows from the network, map a drive to each user's directory that contains user-specific files.Map remaining drives to any directories that users work in frequently, such as project directories or network applications.RENDERAS="SECT3"Assigning Drive Mappings for Diverse EnvironmentsInstead of specifying drive letters such as H or G, it can be useful to use an asterisk followed by a number n to represent the nth network drive.For example, if your first network drive is F: and you use "MAP *3:=", then that drive is assigned as H: (because MAP *1:=F:, MAP*2:=G:, MAP*3:=H:, etc.). Or, if your first network drive is D: and you use "MAP *4:=", that drive is assigned as G:.This allows drive letters to reorder themselves automatically when local drives are removed or added or when the first network drive is changed.This also allows users to log in from workstations with a different number of local drives than their regular workstations.You can map a local drive (usually A: through C:) to a network directory, but you cannot access the local drive until you remove the network drive mapping.You cannot map a redirected drive, such as a CD-ROM drive, to a network drive.RENDERAS="SECT3"Assigning Search DrivesYou can add network volumes or directories to the DOS path by using the SEARCH drive option in the MAP utility. This is useful for network applications and files that you want access to regardless of the current directory you are working in.PAGENUM=182 ID="BP173"There is a maximum of 16 NetWare search drives allowed. When you map a search drive, you use a search drive number (an S followed by a number). This search drive number assigns the next available drive letter to the mapping, starting with Z and working backwards through the English alphabet.The letter is put into the DOS path statement. If you already have drives in the path statement, MAP S1 will overwrite the first one in the path.To prevent search drive assignments from overriding existing DOS PATH letters, use the INSERT option when assigning search drives. For example, type "MAP INS S16:=path".To ensure that you can access NetWare utilities, DOS directories, and applications, you should map search drives to the following directories IDXID="w11282"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"in the 
order 
given:MARK=BULLETMap the first search 
drive (S1:) to the SYS:PUBLIC IDXID="w11283"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
directory, which contains the NetWare utilities for DOS and MS Windows client workstations.Map the second search drive (S2:) to the DOS directory if you access DOS from the network.Map the third and subsequent search drives (S3:, S4:, etc.) to directories containing network applications, project files and frequently used data directories.If you are running 
MS Windows from the network, map a search drive to the IDXID="w11284"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
MS Windows directory for the 
MS Windows group.To avoid inadvertently changing the order of any search drives that must be mapped to a specific drive letter, you can map all remaining search drives with the number S16: or use INS to insert a drive mapping.If you have an application that requires a particular drive letter, you can use the following command to map the search drive:FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S16:=drive:=pathIf you map a search drive using a number already assigned to a search drive, NetWare makes the old search drive a network drive.PAGENUM=183 ID="BP174"RENDERAS="SECT3"Assigning Drives to Directory Map Objects (NetWare 4 only)Another way to map a drive to a directory is to 
create a IDXID="w11285"BOOK="_idx" COLLECTION="nw41" TIDREF="i1060"
Directory Map object that points to the directory. Then, if you move the directory, you need to change only the IDXID="w11286"BOOK="_idx" COLLECTION="nw41" TIDREF="i1061"
Directory Map object rather than all assignments to that directory.For example, to map a search drive to a Directory Map object whose Distinguished Name is APPL.SALES_LA.NOVELL_US, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=.APPL.SALES_LA.NOVELL_US MOREINFO="NONE"<Enter>In the above example, the Directory Map object's name begins with a period, which indicates that the drive is mapped to the drive root.If your User object exists in the same context as the Directory Map object, such as the example SALES_LA.NOVELL_US, the MAP command does not have to specify the Distinguished Name for the Directory Map object.Instead, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP S2:=APPL MOREINFO="NONE"<Enter>It is best to use Map objects in your current context. Don't use Distinguished Names that point to other contexts. If your map is in another context, you should create an alias that points to the real Directory Map object. See "BOOK="cncptenu" COLLECTION="nw41"Alias object" in Concepts for more information.See Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," in Supervising the Network for more information about Directory Map objects.RENDERAS="SECT3"Using 
Login Scripts or IDXID="w11287"BOOK="_idx" COLLECTION="nw41" TIDREF="i2218"
Profiles to Make 
Drive Mappings PermanentIDXID="w11288"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
You can use 
login scripts or IDXID="w11289"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
profiles to automatically set up drive mappings when you log in to the network. IDXID="w11290"BOOK="_idx" COLLECTION="nw41" TIDREF="i1063"
Login scripts and 
profiles are similar to configurable batch files and are executed by the LOGIN utility.You can use login scripts and profiles toMARK=BULLETMap drives and search drives to directoriesDisplay messagesSet environment variablesPAGENUM=184 ID="BP175"Execute programs or menusLogin scripts and profiles work the same way for both DOS and MS Windows workstations. However, you must run a login script or profile before loading MS Windows. You cannot run them from an MS Windows session or DOS box.See the following references for more information about login scripts and profiles:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 2COLNAME=2 ROTATE="0" MOREROWS="0""Plan and Create Login Scripts," in "Logging in and out" of Using the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 3COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 4, "BOOK="install" COLLECTION="nw312"Creating Login Scripts," in Installation and UpgradeCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 4COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," in Supervising the NetworkRENDERAS="SECT2"ID="FM19658"The NetWare User Tools for DOS (the NETUSER Utility)NETUSER allows you to assign IDXID="w11291"BOOK="_idx" COLLECTION="nw41" TIDREF="i877"
drives to IDXID="w11292"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
network directories. Use NETUSER toMARK=BULLETIDXID="w11293"BOOK="_idx" COLLECTION="nw41" TIDREF="i1222"
View IDXID="w11294"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
drive mappingsIDXID="w11295"BOOK="_idx" COLLECTION="nw41" TIDREF="i1222"
Create or change network or search drive mappingsIDXID="w11296"BOOK="_idx" COLLECTION="nw41" TIDREF="i612"Assign a drive to a fake root directory (for applications that must use a root directory)NETUSER is a NetWare workstation utility located in the SYS:PUBLIC directory. A default drive mapping should exist for the SYS:PUBLIC directory (the default is drive Z:). The NETUSER utility is available in NetWare 4 networks only. Specify the type of drive mapping and assignment you want by completing the following procedure.PAGENUM=185 ID="BP176"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Change to the SYS:PUBLIC directory.PERFORMANCE="REQUIRED"Load NetWare User Tools for DOS by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETUSER MOREINFO="NONE"<Enter>The NETUSER utility menu appears. PERFORMANCE="REQUIRED"Choose "Drives."The "Available Options" window appears.PERFORMANCE="REQUIRED"Choose "Drive Mapping" or "Search Mapping" from the list.Either the "Current Drive Mappings" or the "Current Search Mappings" window appears.PERFORMANCE="REQUIRED"To add a network or search drive mapping, press 
MOREINFO="NONE"<Ins> and follow the screen prompts.PERFORMANCE="REQUIRED"Exit NETUSER.Press
MOREINFO="NONE" <Esc> until the "Exit?" menu box appears. Then select "Yes" and press 
MOREINFO="NONE"<Enter>.Or press 
MOREINFO="NONE"<Alt>+<F10> anywhere within NETUSER to display the "Exit?" menu box. Then select "Yes" and press 
MOREINFO="NONE"<Enter>.RENDERAS="SECT2"ID="FM80619"The NetWare User Tools for MS Windows (the NWUSER.EXE Program)The NetWare User Tools for MS Windows program allows you to assign IDXID="w11297"BOOK="_idx" COLLECTION="nw41" TIDREF="i877"
drives to IDXID="w11298"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
network directories using the "Drive Connections" window. Use this window toMARK=BULLETIDXID="w11299"BOOK="_idx" COLLECTION="nw41" TIDREF="i1223"
View IDXID="w11300"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
drive IDXID="w11301"BOOK="_idx" COLLECTION="nw41" TIDREF="i2814"
mappingsIDXID="w11302"BOOK="_idx" COLLECTION="nw41" TIDREF="i1223"
Create or 
change network drive mappingsIDXID="w11303"BOOK="_idx" COLLECTION="nw41" TIDREF="i612"Assign a drive to a fake root directory (for applications that must use a root directory)PAGENUM=186 ID="BP177"The NETWARE.DRV file provides the drive mapping function for the NetWare User Tools for MS Windows. It resides in the SYSTEM subdirectory of your MS Windows directory (the default is C:\WINDOWS\SYSTEM).The NetWare User Tools for MS Windows program is available in NetWare 3.12 and NetWare 4, and in NetWare Client Kits for DOS and MS Windows packages.Specify the type of drive mapping and assignment you want by completing the following procedure.RENDERAS="SECT3"IDXID="w11304"BOOK="_idx" COLLECTION="nw41" TIDREF="i1223"
ProcedurePERFORMANCE="REQUIRED"Run MS Windows.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F6> or select the "NetWare User Tools" icon in the NetWare program group.If the icon is not displayed, you can also access NetWare User Tools for MS Windows by creating a Program object in the MS Windows Program Manager with NWUSER.EXE. (The NWUSER.EXE file is in your target directory for the client installation.)PERFORMANCE="REQUIRED"Choose "NetWare Drive Connections."PERFORMANCE="REQUIRED"From the "Resources" list, select the resource you want to connect to, and then choose a client workstation drive.PERFORMANCE="REQUIRED" Choose "Map" at the bottom of the window. If you are using keyboard entry, first type in the full path for the drive mapping inside the "Path" field, and then choose "Map."For example, the following figure illustrates the drive mapping REPORTS\SYS\WORD to the client workstation drive P: using the "NetWare Drive Connections" window.PAGENUM=187 ID="BP178"LABEL="9-1" FLOAT="0""NetWare Drive Connections" WindowFILEREF="c41ug14a.tif"RENDERAS="SECT3"Using the "NetWare Drive Connections" WindowRemember the following:MARK=BULLETBefore using "NetWare Drive Connections," you must first log in to a Directory tree or a server that contains the object you want to connect to.NetWare User Tools for MS Windows recognizes all drive mappings that existed before MS Windows was started. However, when you are using a DOS Box inside MS Windows, your previous search drives are disabled.RENDERAS="SECT3"Viewing the "Resources" ListThe "Resources" list contains the following:MARK=BULLETVolumesDirectoriesNetWare Directory ServicesTM objectsNetWare Directory Services containersThe volumes and directories are listed in a hierarchical structure. To display subdirectories, choose the "Volume" icon from the "Resources" list.PAGENUM=188 ID="BP179"RENDERAS="SECT3"Making Drive Mappings IDXID="w11305"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
PermanentYou can use the "Permanent" setting in the "NetWare Drive Connections" window much like a login or profile script in DOS.After creating a drive mapping, make it permanent by opening the "NetWare Settings" window and marking the "Restore During Startup" box. (The "NetWare Setting" button is on the upper button bar, represented by a icon with a key, a check box, and a screen.)Each time you load MS Windows, the NetWare User Tools automatically restores the drive mappings you made permanent in a previous session.RENDERAS="SECT1"ID="FM91120"Using 
Universal Naming Convention (UNC) Paths in MS WindowsNetWare supports the use of IDXID="w11306"BOOK="_idx" COLLECTION="nw41" TIDREF="i4651"
Universal IDXID="w11307"BOOK="_idx" COLLECTION="nw41" TIDREF="i4649"
Naming Convention (UNC) redirection for 
path statements in dialog boxes within the following MS Windows conventions:TYPE="VERT"IDREF="FM95432"Program Group (.GRP) FilesIDREF="FM17021"Program Items FilesIDREF="FM52409"Program Information Files (PIFs)IDREF="FM69306"Referencing FilesUNC paths provide you withMARK=BULLETThe ability to use a network resource without formally mapping to itThe use of applications and programs within MS Windows to access network volumes and directoriesThe ability to assign network applications, volumes, and directories to icons within MS WindowsRENDERAS="SECT2"ID="FM95432"Program Group (.GRP) FilesTo have access to program groups located on a network server without formally mapping to the resource, use UNC redirection in the "Program Group Properties" dialog boxes as follows.PAGENUM=189 ID="BP180"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the Program Manager "File" menu, choose "New."PERFORMANCE="REQUIRED"Select "Program Group" and then choose "OK."PERFORMANCE="REQUIRED"In the "Group File" text box, enter the UNC path for the .GRP file.To assign a path, enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\servername\volume\path\groupname.GRPFor example, to assign the DATABASE.GRP file on the server ACCOUNTING, you could enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\ACCOUNTING\SYS\APPS\DATABASE.GRPIf you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername.RENDERAS="SECT2"ID="FM17021"Program Items FilesTo have access to program items located on a network server without formally mapping to the resource, use UNC redirection in the "Program Item Properties" dialog boxes as follows.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the Program Manager "File" menu, choose "New."PERFORMANCE="REQUIRED"Select "Program Item" and then choose "OK."PERFORMANCE="REQUIRED"In the "Command Line" text box, enter the UNC path for the application.To assign a path, enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\servername\volume\path\filenameFor example, to assign a path to an MS Windows word processing application called WRDPRC.EXE on the server MARKETING, you could enter
PAGENUM=190 ID="BP181"FORMAT="LINESPECIFIC"MOREINFO="NONE"\\MARKETING\SYS\APPS\WRDPRC.EXEIf you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername.When using UNC paths for programs, you might receive the following message:
FORMAT="LINESPECIFIC"MOREINFO="NONE"The specified path points to a file that may not be available during later Windows sessions. Do you want to continue?If you choose "Yes," then the icon for the program item is built.UNC redirection for programs is dependent upon the modules or parts that the program uses, where they are located, and how they are loaded. UNC might not function for all applications.UNC redirection can work even if the executable file relies on another file to run. For example, if the MS-DOS 5.0 EDIT.COM and QBASIC.EXE files (the latter is needed to run the former) are both copied onto the network share, UNC redirection works properly.RENDERAS="SECT2"ID="FM52409"Program Information Files (PIFs)To have access to a DOS application located on a network server without formally connecting to the resource, use UNC redirection in the PIF command line as follows.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Run the PIF Editor.PERFORMANCE="REQUIRED"In the "Program Filename" text box, enter the UNC path for the application.To assign a path, enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\servername\volume\path\filenameFor example, to assign a path to an DOS word processing application called WRDPRC.EXE on the server MARKETING, you could enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\MARKETING\SYS\APPS\WRDPRC.EXE
PAGENUM=191 ID="BP182"If you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername.UNC redirection for programs is dependent upon the modules or parts that the program uses, where they are located, and how they are loaded. UNC redirection might not function for all applications.UNC redirection can work even if the executable file relies on another file to run. For example, if the MS-DOS 5.0 EDIT.COM and QBASIC.EXE files (the latter is needed to run the former) are both copied onto the network share, UNC redirection works properly.RENDERAS="SECT2"ID="FM69306"Referencing FilesTo copy or move files and directories to a network volume or directory, or to open a file or save it as another filename, without formally mapping to the resource, you can use UNC redirection as follows.RENDERAS="SECT3"Referencing Files and Directories in the "File" or "Move" Text BoxPERFORMANCE="REQUIRED"Run File Manager.PERFORMANCE="REQUIRED"Select the file you want to copy or move.PERFORMANCE="REQUIRED"From the "File" menu, choose "Move" or "Copy."PERFORMANCE="REQUIRED"In the "To" text box, enter the UNC path.To assign a path, enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\servername\volume\path\For example, to assign a path in order to move or copy a file to the SYS:CONTACT directory on the server SALES, you would enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\SALES\SYS\CONTACTS\If you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername.RENDERAS="SECT3"Referencing a File in the "Open" or "Save As" Text BoxPERFORMANCE="REQUIRED"Run File Manager.PAGENUM=192 ID="BP183"PERFORMANCE="REQUIRED"From the "File" menu, select "Open" or "Save As."PERFORMANCE="REQUIRED"In the "File Name" text box, enter the UNC path including the filename.Enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\servername\volume\path\filenameFor example, to assign a path to open the REPORTS.TXT file in the SYS:CONTACT directory on the server SALES, you would enter
FORMAT="LINESPECIFIC"MOREINFO="NONE"\\SALES\SYS\CONTACTS\REPORTS.TXTIf you are redirecting a resource that is a NetWare Directory Services object in NetWare 4, you must specify three backslashes (\\\) before the servername.RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Drive mapping" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare file system (directory structure)COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Directory structure" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare volumesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Volume" in NetWare 4 ConceptsLABEL="10"PAGENUM=193 ID="BP184"ID="FM94060"Setting Up Client Workstation PrintingRENDERAS="SECT1"OverviewThis chapter explains how to set up network printing on your NetWare® client workstation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM42517"Using NetWare Utilities to Set Up Network PrintingCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM42517"194COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74162"The CAPTURE UtilityCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74162"195COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88795"The NetWare User Tools for DOS (the NETUSER Utility)COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88795"197COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29169"The NetWare User Tools for MS Windows (the NWUSER.EXE Program)COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29169"199COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74015"Using Universal Naming Convention (UNC) Port Redirection in MS Windows COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74015"204RENDERAS="SECT1"IntroductionNetWare uses a print queue, a print server, and often a print driver to allow several network client workstations to print to a network printer.The print server takes print jobs from the print queue and sends them to the printer. A print driver is used in cases where the application that the print job is being sent from is not 
NetWare AwareTM (not developed using NetWare APIs) and, therefore, it requires specific setup so that communication from the application to the printer is in a language that the printer understands.Printing from DOS and MS Windows client workstations is usually accomplished through applications. Many applications require you to install print drivers that are specific to that program.PAGENUM=194 ID="BP185"If you are logged in to the network and your application supports direct printing through NetWare, you do not have to perform any setup.If you want to print from an IDXID="w11308"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
application which is not NetWare Aware, or print directly from the screen, you must set up and IDXID="w11309"BOOK="_idx" COLLECTION="nw41" TIDREF="i2242"
configure your local printerport (LPT1) to send print jobs to a print queue.RENDERAS="SECT1"ID="FM42517"Using NetWare Utilities to  
Set Up Network PrintingNetWare provides you with the following three utilities to set up printing for client workstations in your network:MARK=BULLETIDREF="FM74162"The CAPTURE UtilityA DOS IDXID="w11310"BOOK="_idx" COLLECTION="nw41" TIDREF="i3540"
text utility available in all version of NetWare.IDREF="FM88795"The NetWare User Tools for DOS (the NETUSER Utility)A DOS menu utility available in NetWare 4TM only.IDREF="FM29169"The NetWare User Tools for MS Windows (the NWUSER.EXE Program)An MS Windows graphical utility available in the NetWare ClientTM Kits for DOS and MS Windows, and in NetWare 3.12 and NetWare 4 software.For online help and information on available options, use the /? or /H parameter with text utilities and the MOREINFO="NONE"F1 key with menu and graphical utilities.RENDERAS="SECT2"PrerequisitesBefore you can use any of the print setup utilities, your client workstation requires the following:MARK=CHECKBOXA physical connection to the networkNovell® DOSTM, DR DOS®, PC-DOS, or MS-DOS loaded and running(Conditional: if you are using MS Windows) A copy of MS Windows 3.x or MS Windows for Workgroups 3.11 installed and runningThe NetWare ClientTM files loaded and runningPAGENUM=195 ID="BP186"See IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.A connection to the networkSee IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169 for more information.Access to network printing resourcesRENDERAS="SECT2"ID="FM74162"The CAPTURE UtilityUse CAPTURE toMARK=BULLETSet up connection to print queuesControl network printingIDXID="w11311"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
View information about network printingRedirect a printer port to the networkRENDERAS="SECT3"Using CAPTURE at the Command LineUse CAPTURE at the command line to set up printing by completing the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Type the following command at a DOS prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"CAPTURE [option] MOREINFO="NONE"<Enter>See Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Reference," in NetWare Client for DOS and MS Windows Technical Reference for a listing of available options and descriptions.PERFORMANCE="REQUIRED"(Conditional) If you are running applications that print to a port, such as LPT1, set up the correct print driver within each application for the printer you are sending jobs to.See the manufacturer's documentation for information about print drivers.
PAGENUM=196 ID="BP187"Once you have captured a port to a network printer or print queue, all printing from the screen or applications to LPT1 will be redirected to the designated server and queue.You can't use CAPTURE with COM ports (you can use it only with LPT ports). However, the DOS MODE command allows you to redirect COM ports to LPT ports. For more information, see your DOS manual or the documentation that came with your printer.RENDERAS="SECT3"ExampleIDXID="w11312"BOOK="_idx" COLLECTION="nw41" TIDREF="i590"
An example of a common command line statement for the CAPTURE utility is as follows:FORMAT="LINESPECIFIC"MOREINFO="NONE"CAPTURE /Q=LASERJET4 /S=SALES /P=P1 /TI=5This command indicates the following:MARK=BULLETCapture to print queue LaserJet4The server connection is to SalesCapture to network printer P1Timeout in 5 secondsRENDERAS="SECT3"Using CAPTURE Login Scripts or ProfilesIDXID="w11313"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
You can use IDXID="w11314"BOOK="_idx" COLLECTION="nw41" TIDREF="i3519"
login scripts or profiles to automatically set up port captures when you log in to the network. Login scripts and profiles are similar to configurable batch files and are executed by the LOGIN utility.You can use login scripts and profiles toMARK=BULLETCapture ports to network printer and queuesDisplay messagesSet environment variablesExecute programs or menusPAGENUM=197 ID="BP188"Login scripts and profiles work the same way for both DOS and MS Windows workstations. However, you must run the login script or profile before loading MS Windows. You cannot run them from an MS Windows session or DOS box.See the following references for more information about login scripts and profilesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"VersionCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 2COLNAME=2 ROTATE="0" MOREROWS="0""Plan and Create Login Scripts," in Using the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 3COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 4, "BOOK="install" COLLECTION="nw312"Creating Login Scripts," in Installation and UpgradeCOLNAME=1 ROTATE="0" MOREROWS="0"NetWare 4COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," in Supervising the NetworkRENDERAS="SECT3"ID="FM29720"Setting the Number of Available Printer ConnectionsPERFORMANCE="REQUIRED"Edit the NetWare Client configuration (NET.CFG) file with an ASCII text editor.PERFORMANCE="REQUIRED"Add the following lines to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NetWare DOS Requester
   network printers = numberReplace number with the number of printer connections.
TYPE="VERT"Maximum = 9Default = 3For example, to allow for the maximum number of printer connections, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NetWare DOS Requester
   network printers = 9PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"ID="FM88795"The NetWare User Tools for DOS (the NETUSER Utility)NETUSER allows you to assign LPT ports to network printers and queues.PAGENUM=198 ID="BP189"Use NETUSER toMARK=BULLETSet up print queuesIDXID="w11315"BOOK="_idx" COLLECTION="nw41" TIDREF="i3540"
Control network printingIDXID="w11316"BOOK="_idx" COLLECTION="nw41" TIDREF="i3540"
ViewIDXID="w11317"BOOK="_idx" COLLECTION="nw41" TIDREF="i4766"
 information about network printingRedirect a printer port to the networkThe NETUSER utility is a NetWare workstation utility located in the SYS:PUBLIC directory. A default drive mapping should exist for the SYS:PUBLIC directory (the default is drive Z:). The NETUSER utility is available in NetWare 4 networks only. Specify the port assignment you want by completing the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Change to the SYS:PUBLIC directory.PERFORMANCE="REQUIRED"Load NetWare User Tools for DOS by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETUSER MOREINFO="NONE"<Enter>The NETUSER utility menu appears. PERFORMANCE="REQUIRED"Choose "Printing."The "Available Ports" window appears.PERFORMANCE="REQUIRED"Choose a port from the list.The "Available Options" window appears.PERFORMANCE="REQUIRED"Choose "Change Printers."The "Printer/Print Queues" window appears. If the print queue you want to capture is not listed, make sure that you chose the correct server containing this print queue.PERFORMANCE="REQUIRED"Select a print queue name from the list.
PAGENUM=199 ID="BP190"If you don't know the queue name, use the arrow keys to scan the list of available print queues.PERFORMANCE="REQUIRED"To capture the print queue to the port you specified, press 
MOREINFO="NONE"<Enter>.Your screen then returns to the previous window, and your current client workstation information in the top portion of the screen is updated.PERFORMANCE="REQUIRED"Exit NETUSER.Press
MOREINFO="NONE" <Esc> until the "Exit?" menu box appears. Then select "Yes" and press 
MOREINFO="NONE"<Enter>.Or press 
MOREINFO="NONE"<Alt>+<F10> anywhere within NETUSER to display the "Exit?" menu box. Then select "Yes" and press 
MOREINFO="NONE"<Enter>.If you are running applications that print to a port, such as LPT1, see the manufacturer's documentation for information about print drivers.RENDERAS="SECT2"ID="FM29169"The NetWare User Tools for MS Windows (the NWUSER.EXE Program)IDXID="w11318"BOOK="_idx" COLLECTION="nw41" TIDREF="i3541"
Setting up client workstation printing in 
MS Windows requires you to first set up the Print Manager in MS Windows, and then access the "NetWare Printer Connections" option in NetWare User Tools for MS Windows.The NETWARE.DRV file provides the port capturing function for the NetWare User Tools for MS Windows. It resides in the SYSTEM directory of your MS Windows directory (The default is C:\WINDOWS\SYSTEM).The NetWare User Tools program is available in NetWare 3.12 and NetWare 4 software, and in NetWare Client Kits for DOS and MS Windows packages.Specify the port assignment you want by completing the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Run MS Windows.PERFORMANCE="REQUIRED"Open the Print Manager.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM44173"In the MS Windows Control Panel, choose the "Printer" icon.The "Printers" dialog appears.PAGENUM=200 ID="BP191"LABEL="10-1" FLOAT="0""Printers" DialogFILEREF="c41ug23a.tif"PERFORMANCE="REQUIRED"Mark the "Use Print Manager" box.The Print Manager is activated.PERFORMANCE="REQUIRED"From the "Installed Printers" list, select a printer.If the printer you want is not listed: 
MARK=BULLETChoose "Add" to display the list of available printers.Select the printer you want from the "List of Printers."Choose "Install."MS Windows prompts you to insert an MS Windows diskette and then copies the print driver for the selected printer to the MS Windows directory.PERFORMANCE="REQUIRED"Assign printing ports to network print queues.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM69101"From the "Printers" dialog, choose "Connect."The "Connect" dialog appears.PAGENUM=201 ID="BP192"LABEL="10-2" FLOAT="0""Connect" DialogFILEREF="c41ug24a.tif"PERFORMANCE="REQUIRED"ID="FM26874"Select a port from the "Ports" list.If you have a local printer, we recommend that you leave it assigned to the port that it is already connected to.PERFORMANCE="REQUIRED"Choose "Network."The "NetWare Printer Connections" window appears.LABEL="10-3" FLOAT="0""NetWare Printer Connections" WindowFILEREF="c41ug15a.tif"PAGENUM=202 ID="BP193"PERFORMANCE="REQUIRED"Choose the same port from the "Ports" list that you selected in 
IDREF="FM26874"Step 4b on page 201.PERFORMANCE="REQUIRED"Choose a print queue name from the "Resources" list.If you don't know the queue name, use the browser to see available print queues.PERFORMANCE="REQUIRED"Choose "Capture."PERFORMANCE="REQUIRED"Exit the "NetWare Printer Connections" window by choosing the "Exit" button (the left-most button of the upper menu bar).You return to the "Connect" dialog you were in at IDREF="FM69101"Step 4a.PERFORMANCE="REQUIRED"Choose "OK."You return to the "Printers" dialog you were in at IDREF="FM44173"Step 2a.PERFORMANCE="REQUIRED"Choose "Close" to exit the "Printer" dialog.You return to the Control Panel.PERFORMANCE="REQUIRED"Close the "Control Panel" window.PERFORMANCE="REQUIRED"Choose the "Print Manager" icon.PERFORMANCE="REQUIRED"From the "Print Manager" window, select "Options."PERFORMANCE="REQUIRED"From the "Options" menu, choose "Network Settings."The "Network Options" dialog appears.LABEL="10-4" FLOAT="0""Network Options" DialogFILEREF="c41ug25a.tif"PERFORMANCE="REQUIRED"Mark the "Print Net Jobs Direct" checkbox.
PAGENUM=203 ID="BP194"With this option marked, MS Windows bypasses the Print Manager and prints directly to the network print queue, giving you optimal printing performance.PERFORMANCE="REQUIRED"Exit the "Network Options" dialog box by choosing "OK."If you are running applications that print to a port, such as LPT1, see the manufacturer's documentation for information about print drivers.RENDERAS="SECT3"Using a Local Printer on the NetworkTo access a parallel or serial printer through the network that is cabled to a workstation running MS Windows 3.0 or 3.1, do only one of the following:MARK=BULLETConfigure the printers to use polled mode instead of a specific interrupt number.Set the workstation to use a specific interrupt.Add the following lines to the SYSTEM.INI file under the [386Enh] section:FORMAT="LINESPECIFIC"MOREINFO="NONE"lpt1autoassign=0
lpt1irq=-1Replace 
lpt1 with the port that the printer is cabled to (LPT2, COM1, COM2, etc.).RENDERAS="SECT3"ID="FM14065"Setting the Number of Available Printer ConnectionsPERFORMANCE="REQUIRED"Open the Netware Client configuration (NET.CFG) file in an ASCII text editor.PERFORMANCE="REQUIRED"Add the following lines to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NetWare DOS Requester
   network printers = numberReplace 
number with the number of printer connections.
TYPE="VERT"Maximum = 9Default = 3PAGENUM=204 ID="BP195"For example, to allow for the maximum number of printer connections, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NetWare DOS Requester
   network printers = 9PERFORMANCE="REQUIRED"Save the changes and then close the NET.CFG file.PERFORMANCE="REQUIRED"Open the MS Windows WIN.INI file in an ASCII text editor.PERFORMANCE="REQUIRED"Add as many lines as you need under the [port] section.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[port]
lp1:=
lp2:=
lp3:=
lp4:=
net1:=
record.prn=Add a filename to a line under the [ports] option to have print files print directly to this file. The filename should have a .PRN file extension followed by an equal sign.This causes the named file to appear in the Control Panel "Printer Configuration" dialog box. Any print jobs sent to this file direct their output to it.RENDERAS="SECT1"ID="FM74015"Using Universal Naming Convention (UNC) Port Redirection in MS WindowsNetWare supports the IDXID="w11319"BOOK="_idx" COLLECTION="nw41" TIDREF="i4651"
use of IDXID="w11320"BOOK="_idx" COLLECTION="nw41" TIDREF="i4649"
Universal Naming Convention 
(UNC) redirection for entries in the [ports] section of the WIN.INI file.UNC port IDXID="w11321"BOOK="_idx" COLLECTION="nw41" TIDREF="i3538"
redirection provides you with the ability to use a network print resource without formally capturing a port to it.PAGENUM=205 ID="BP196"RENDERAS="SECT2"PrerequisitesBefore setting up UNC redirection for network printers and queues, your client workstation requires the following:MARK=CHECKBOXThe NetWare User Tools and NetWare Client files for MS Windows loaded and runningSee IDREF="FM93380"Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.A connection to the networkSee IDREF="FM57667"Chapter 8, "Logging In from a NetWare Client Workstation," on page 169 for more information.Access to network printing resourcesAny necessary modifications to the NET.CFG file made for the number of network printer connection allowedIDREF="FM14065"See "Setting the Number of Available Printer Connections" on page 203 for more information.To print to a network resource without formally capturing a port to it, use UNC port redirection as explained in the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open the MS Windows WIN.INI file in an ASCII text editor.PERFORMANCE="REQUIRED"Add the necessary lines under the [ports] section for the printers or queues you want to set up.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[ports]
lpt1:=
lpt2:=
\\servername\queuename=For example, to set up a UNC port redirection for the print queue LASERJET4 on server MARKETING, you would add the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[ports]
PAGENUM=206 ID="BP197"lpt1:=
lpt2:=
\\marketing\laserjet4=If you are redirecting a resource that is a NetWare Directory ServicesTM object in NetWare 4, you must specify three backslashes (\\\) before the servername.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.PERFORMANCE="REQUIRED"Run MS Windows.PERFORMANCE="REQUIRED"Open the Control Panel.PERFORMANCE="REQUIRED"Choose the "Printers" icon.PERFORMANCE="REQUIRED"Choose "Connect."PERFORMANCE="REQUIRED"Select the new port.PERFORMANCE="REQUIRED"Exit the Control Panel.PERFORMANCE="REQUIRED"Send a print job from any application to the new port.When you print to this printer, the output is redirected to the network printer defined by the UNC entry in the [ports] section.When this port is selected in the "Printers Connect" dialog box in Control Panel, the "Network" button will be dimmed (unavailable). When a standard LPT port is selected, the "Network" button is available again.UNC redirection for programs is dependent upon the modules or parts that the program uses, where they are located, and how they are loaded. UNC redirection might not function for all applications.PAGENUM=207 ID="BP198"RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up printing functionality in the NET.CFG fileCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option," in NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Setting up print queuesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print queue" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Setting up print serversCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Print server" in NetWare 4 ConceptsCOLNAME=1 ROTATE="0" MOREROWS="0"Setting up network printingCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 2, "BOOK="printenu" COLLECTION="nw41"Planning and Setting Up NetWare Print Services" in Print Services (NetWare 4 only)LABEL=""PAGENUM=209 ID="BP199"Integration with Other SystemsRENDERAS="SECT1"OverviewNovell® has a scalable, modular family of networking services to support your range of information-sharing needs.The NetWare® ClientTM software was designed to integrate with many of the industry standard networking services to provide heterogeneous connectivity and client-server solutions for your client workstations.RENDERAS="SECT1"ContentsThis section is divided into six chapters, with the following information discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"ChapterCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"To set up your client workstations to support applications running in a task-switching environment using TBMI2COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85167"Chapter 11, "Setting Up Network Support for Task-Switching Environments"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM85167"211COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to connect between two network driver interfaces: Network Driver Interface Specification (NDIS) and the Open Data-link InterfaceTM SpecificationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM13108"Chapter 12, "Setting Up the NetWare ODI Support Interface for NDIS Protocols"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM13108"221COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to set up the NetWare IBM LAN Support program softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88338"Chapter 13, "Setting Up the NetWare for IBM LAN Support Program Modules"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM88338"235COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to set up the NetWare NetBIOS emulatorCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM35822"Chapter 14, "Setting Up NetBIOS Protocol Support"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM35822"245COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to use the Source Routing driverCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39829"Chapter 15, "Setting Up Source Routing Support for a Token-Ring Network"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM39829"253COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to set up Named Pipes extendersCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM13494"Chapter 16, "Setting Up Named Pipes Protocol Support"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM13494"261LABEL="11"PAGENUM=211 ID="BP200"ID="FM85167"Setting Up Network Support for Task-Switching EnvironmentsRENDERAS="SECT1"OverviewThis chapter describes how to use the NetWare® task-switching files and gives advice about which parameters to review in the NET.CFG file if problems arise while you are using these files. The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM95725"Installing a Task-Switching EnvironmentCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM95725"212COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM66667"Installing the Task-Switching Support Software and NetWare Client FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM66667"213COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM58333"Modifying the DOS System and NetWare Client Configuration FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM58333"214COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11835"Loading the Task-Switching Support SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11835"217COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM59889"Unloading the Task-Switching Support SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM59889"218COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM60776"Troubleshooting TBMI2COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM60776"219RENDERAS="SECT1"IntroductionIDXID="w11322"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"
The 
task-switching
 support software for NetWare, the TBMI2.COM and TASKID.COM files, acts as a buffer and manager between IDXID="w11323"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
IPXTM and SPXTM requests and an application's calling process during task switching.IDXID="w11324"BOOK="_idx" COLLECTION="nw41" TIDREF="i1977"
When a task switch is made during an application's call process, the NetWare task-switching support software ensures that IPX and SPX transport protocols send the call to the proper network resource. This prevents any communication breakdown between IPX and software processes when a task switch is made.PAGENUM=212 ID="BP201"You might need this support if you use a DOS task switcher or if you switch DOS sessions within MS Windows in standard or real mode. If your application does require the NetWare task-switching support software and you do not use it, your client workstation might hang or experience session failure.If the only IPX/SPXTMIDXID="w11325"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
application you are using is NetWare DOS RequesterTM, you don't need to load the task-switching files. If you are not sure whether your application needs task-switching support, go ahead and run the task-switching files; they use only a small amount of memory.  After running the application, enter the /D command line parameter and look at the number in the "Far Call Usage" field. If this number is zero, your application has not used the task-switching files, so you can run it without them.You must use the NetWare task-switching support files if your environment has any of the following characteristics:MARK=BULLETYou plan to switch between applications in DOS or 
DOS sessions in MS WindowsYour application bypasses the NetWare DOS Requester software and accesses IDXID="w11326"BOOK="_idx" COLLECTION="nw41" TIDREF="i1977"
IPX or IDXID="w11327"BOOK="_idx" COLLECTION="nw41" TIDREF="i1977"
SPX 
directlyYou are running MS Windows in standard or real modeSetting 
up the IDXID="w11328"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"
task-switching support requires setup on each client workstation that you want to use in task-switching environments.The complete setup for client workstations using the task-switching support software requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM95725"Installing a Task-Switching Environment IDREF="FM66667"Installing the Task-Switching Support Software and NetWare Client Files IDREF="FM58333"Modifying the DOS System and NetWare Client Configuration Files RENDERAS="SECT1"ID="FM95725"Installing a Task-Switching EnvironmentSome well known task-switching environments are Microsoft (MS) Windows, the MS-DOS 5.0 task switcher, DESQview*, and the Novell DOS Task Manager.PAGENUM=213 ID="BP202"You need to install and load the task-switching software before setting up and configuring client workstations for a task-switching environment. See the documentation provided with the software for information on installation and setup.RENDERAS="SECT1"ID="FM66667"Installing the IDXID="w11329"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"
Task-Switching Support Software and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyThe task-switching support software files (TASKID.COM and TBMI2.COM) are automatically copied to the NetWare Client directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the task-switching support software files and other client files to the NetWare Client directory.To manually copy the TASKID.COM and TBMI2.COM files and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM47880"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"TASKID.CO_  TBMI2.CO_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCLASS=DISK or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1CLASS=DISKCOLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_PAGENUM=214 ID="BP203"To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the TBMI2.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:TBMI2.CO_ C:\NWCLIENT\TBMI2.COM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM47880"Step 1 until the TASKID.COM, TBMI2.COM, and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM58333"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11330"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11331"BOOK="_idx" COLLECTION="nw41" TIDREF="i4437"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS Requester software.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open the CONFIG.SYS file in an ASCII text editor.For example, to use the Novell DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>
PAGENUM=215 ID="BP204"PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11332"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11333"BOOK="_idx" COLLECTION="nw41" TIDREF="i4437"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the ODITM LAN driver, the task-switching support software (the TBMI2.COM file), and the NetWare DOS Requester software.Ensure that the TBMI2.COM file is loaded in the STARTNET.BAT file before loading a task-switching environment. If you are currently loading task-switching software in your AUTOEXEC.BAT file, move the line to the STARTNET.BAT file.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load one of the task-switching support software files and the NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driveripxodi
vlm
tbmi2Replace 
path with the directory where the TBMI2.COM and NET.CFG files are found. The TBMI2.COM file cannot execute unless it can access the NET.CFG file in the proper directory path.Replace 
odi_lan_driver with the name of the ODI LAN driver that your workstation is using.To automatically unload the TBMI2.COM file after closing that task-switching environment, use the /U command line parameter after the command that loads a task-switching environment.For example, to unload the TBMI2.COM file after closing the Novell DOS TASKMGR.EXE file, add the following lines:
PAGENUM=216 ID="BP205"FORMAT="LINESPECIFIC"MOREINFO="NONE"tbmi2
c:\nwdos\ askmgr
tmbi2 /uPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.You can also use command line parameters to override NET.CFG parameters at the command line. See Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference," in NetWare Client for DOS and MS Windows Technical Reference for more information.RENDERAS="SECT2"Modifying the IDXID="w11334"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11335"BOOK="_idx" COLLECTION="nw41" TIDREF="i4437"
FileThe task-switching support software (the TBMI2.COM and TASKID.COM files) allows you to specify variables for the following parameters in your NET.CFG file:TYPE="VERT"DATA ECB COUNTECB COUNTINT64INT7AUSE MAX PACKETSUSING WINDOWS 3.0See "BOOK="ws_d2enu" COLLECTION="nw41"TBMI2 Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for details on how to configure your client workstation for task-switching environments.If you want to set parameters in a batch file or override NET.CFG settings at the command line, see Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters," in NetWare Client for DOS and MS Windows Technical Reference for details on how to use command line parameters for the TBMI2 and TASKID softwareTo configure the parameters for the task-switching support software, complete the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with an ASCII text editor.PAGENUM=217 ID="BP206"For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Make the necessary configurations for your particular task-switching software.See the manufacturer's documentation for information.PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file.You can also use command line parameters to override NET.CFG parameters at the command line. See Chapter 3, "BOOK="ws_d1enu" COLLECTION="nw41"Command Line Parameters Reference," in NetWare Client for DOS and MS Windows Technical Reference for more information.RENDERAS="SECT1"ID="FM11835"Loading the IDXID="w11336"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"
Task-Switching  
Support SoftwareIf you are running MS Windows in enhanced mode or not switching between DOS sessions within MS Windows, then do not use the TBMI2 software.Loading the TBMI2.COM file for task-switching environments requires you to complete the following procedures.RENDERAS="SECT2"ID="FM21593"For DOS and MS Windows 3.1 and LaterPERFORMANCE="REQUIRED"Ensure that your task-switching environment is setup and running.IDREF="FM95725"See "Installing a Task-Switching Environment" on page 212 for more information.PERFORMANCE="REQUIRED"Ensure that the TBMI2.COM and NetWare Client software files are installed on each client workstation that you want to run in a task-switching environment.IDREF="FM66667"See "Installing the Task-Switching Support Software and NetWare Client Files" on page 213 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.
PAGENUM=218 ID="BP207"IDREF="FM58333"See "Modifying the DOS System and NetWare Client Configuration Files" on page 214 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the TBMI2.COM and NetWare Client software files.RENDERAS="SECT2"For IDXID="w11337"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
MS 
Windows 3.0PERFORMANCE="REQUIRED"Complete the previous procedure, IDREF="FM21593""For DOS and MS Windows 3.1 and Later."PERFORMANCE="REQUIRED"Run MS Windows.PERFORMANCE="REQUIRED"Open a DOS session.PERFORMANCE="REQUIRED"ID="FM87581"At the new system prompt, load TASKID by typing 
FORMAT="LINESPECIFIC"MOREINFO="NONE"TASKID MOREINFO="NONE"<Enter>For each DOS session you open, repeat 
IDREF="FM87581"Step 4 before running an 
IDXID="w11338"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
application from the system prompt within that session.RENDERAS="SECT1"ID="FM59889"Unloading the IDXID="w11339"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"
Task-Switching 
Support SoftwarePERFORMANCE="REQUIRED"Before closing a DOS session with the EXIT command in MS Windows 3.0, unload the TASKID.COM file by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"TASKID /U MOREINFO="NONE"<Enter>If you do not unload TASKID 
before you close a DOS session in MS Windows 3.0, your computer might hang.PERFORMANCE="REQUIRED"Unload the TBMI2.COM file by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"TBMI2 /U MOREINFO="NONE"<Enter>You do not need to unload TBMI2 after you exit MS Windows unless you want to free memory.
PAGENUM=219 ID="BP208"RENDERAS="SECT1"ID="FM60776"Troubleshooting IDXID="w11340"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
TBMI2IDXID="w11341"BOOK="_idx" COLLECTION="nw41" TIDREF="i4436"If you have problems while using the TBMI2.COM file, you might need to change configuration parameters in the NET.CFG file.See "BOOK="ws_d2enu" COLLECTION="nw41"TBMI2 Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for details on how to configure your client workstation for task-switching environments.View configuration parameters by typing "TBMI2 /D" at the command line. Check the values associated with the following:MARK=BULLET"Configured Data ECBs," which tells you how many buffers are available"Max Buffers Used," which tells you how many buffers are usedIf the number of buffers used approaches or equals the number of buffers available, increase the number of buffers available using the ECB Count and Data ECB Count parameters in the NET.CFG file."Unavail Buffer Count," which tells you how many buffers are unavailableIf the count is more than zero, increase the number of buffers available using the ECB Count and Data ECB Count parameters in the NET.CFG file.The COMCHECK and RCONSOLE utilities use too many buffers that need to be allocated for TBMI2.  To use either of these utilities under MS Windows, do not load the TBMI2.COM file and do not switch out of the DOS session running either the COMCHECK or RCONSOLE utility before exiting either of the utilities.PAGENUM=220 ID="BP209"RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for TBMI2COLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"TBMI2 Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using command line parametersCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference" of NetWare Client for DOS and MS Windows Technical ReferenceLABEL="12"PAGENUM=221 ID="BP210"ID="FM13108"Setting Up the NetWare ODI Support Interface for NDIS ProtocolsRENDERAS="SECT1"OverviewThis chapter explains how to set up client workstations to support connections to IDXID="w11342"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
other networks that use the 
Network Driver Interface Specification (NDIS) protocolIDXID="w11343"BOOK="_idx" COLLECTION="nw41" TIDREF="i654"
, and to access network resources as if they were available from just one network.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM92965"Installing MAC Drivers and an NDIS Protocol Manager on Client WorkstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92965"223COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM77543"Installing the ODINSUP.COM and NetWare Client FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM77543"223COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM99590"Binding ODI LAN Drivers to the NDIS Protocol StackCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM99590"224COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM84916"Modifying the DOS System and NetWare Client Configuration FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM84916"227COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM85837"Loading the ODINSUP SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85837"232COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM46361"Unloading the ODINSUP SoftwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46361"233RENDERAS="SECT1"IntroductionIDXID="w11344"BOOK="_idx" COLLECTION="nw41" TIDREF="i3063"The ODITM NDIS support module (ODINSUP) is an Open Data-Link InterfaceTM (ODI) protocol stack that interfaces between NDIS and NetWare® ClientTM LAN drivers.ODINSUP translates NDIS transmissions from NDIS-based applications into a form that complies with the ODI drivers.PAGENUM=222 ID="BP211"ODINSUP also translates transmissions received from the network into a form understood by the NDIS Protocol Manager (PROTMAN).NDIS specifies two type of drivers: one for hardware manipulation, and one for protocol handling. Hardware-related drivers are also called NDIS MAC (Media Access Control) drivers. Protocol handling drivers are called NDIS PROTMAN drivers.By separating these functions, NDIS allows you to have multiple protocols with the same physical adapter, or to use only one driver per physical adapter. The NDIS Protocol Manager regulates transactions between hardware and protocol drivers.ODINSUP provides an NDIS MAC interface for each physical adapter in the system. ODINSUP can be bound with a NET.CFG option to a maximum of four adapters and can generate a separate and distinct MAC interface for each one. This is the equivalent of having the corresponding NDIS-compliant drivers loaded, plus having a full ODI interface.ODINSUP provides the following benefits:MARK=BULLETNo reconfiguration or rebooting necessary to switch between NDIS-based networks and NetWare networksCompatibility between applications written to NDIS and ODI (or compliant) driversODI protocol stacks and NDIS protocol stacks can share the same adapter when the ODINSUP module is usedIDXID="w11345"BOOK="_idx" COLLECTION="nw41" TIDREF="i3063"
Setting 
up the IDXID="w11346"BOOK="_idx" COLLECTION="nw41" TIDREF="i3063"
ODI support interface for NDIS protocols requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM92965"Installing MAC Drivers and an NDIS Protocol Manager on Client WorkstationsIDREF="FM77543"Installing the ODINSUP.COM and NetWare Client FilesIDREF="FM99590"Binding ODI LAN Drivers to the NDIS Protocol StackIDREF="FM84916"Modifying the DOS System and NetWare Client Configuration FilesPAGENUM=223 ID="BP212"RENDERAS="SECT1"ID="FM92965"Installing MAC Drivers and an NDIS Protocol Manager on Client WorkstationsODINSUP is designed for NetWare users that want to use NDIS-based networks such 3+Share* or LAN Manager* and to also log in to a NetWare network. See the manufacturers' documentation for instruction on installation and setup of NDIS MAC and PROTMAN drivers.If you are upgrading client workstations using NDIS MAC drivers, verify first that the client workstations can connect to the NDIS-based network to ensure that the hardware connection is good. Once you install the NetWare Client for DOS and MS Windows files, the NDIS protocol cannot use the network board to make connections until you have completely set up ODINSUP as instructed in this chapter. RENDERAS="SECT1"ID="FM77543"Installing 
the ODINSUP.COM and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyODINSUP.COM and the other client files are automatically copied to the NetWare Client directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the ODINSUP.COM and other client files to the NetWare Client directory.To manually copy the ODINSUP.COM file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.PAGENUM=224 ID="BP213"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM41827"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"ODINSUP.CO_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCLASS=DISK or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1CLASS=DISKCOLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the ODINSUP.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:ODINSUP.CO_ C:\NWCLIENT\ODINSUP.COM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM41827"Step 1 until the ODINSUP.COM and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM99590"Binding ODI LAN Drivers to the NDIS Protocol StackThe IDXID="w11347"BOOK="_idx" COLLECTION="nw41" TIDREF="i2630"
NDIS PROTOCOL.INI file is necessary to tell the NDIS protocols which MAC to bind to and use.Normally all PROTOCOL.INI information for NDIS MAC drivers can be removed if you are using one NDIS MAC driver and protocol stack only. No ODINSUP-specific information is necessary in the PROTOCOL.INI file.PAGENUM=225 ID="BP214"IDXID="w11348"BOOK="_idx" COLLECTION="nw41" TIDREF="i466"
Binding ODI LAN drivers to the NDIS protocol stack requires you to edit the IDXID="w11349"BOOK="_idx" COLLECTION="nw41" TIDREF="i3065"
PROTOCOL.INI file with a text editor to do the following:MARK=BULLETBind the NDIS protocol stack to the ODI LAN driversRemove the line binding the NDIS protocol stack to the NDIS MAC driversRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the IDXID="w11350"BOOK="_idx" COLLECTION="nw41" TIDREF="i3064"
PROTOCOL.INI file with an ASCII text editor. For example, to use the Novell
® DOSTM 7 System Editor at the command line to edit the PROTOCOL.INI file in the BOOT directory, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\BOOT\PROTOCOL.INI MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"ID="FM77133"Find all occurrences of the lines that bind the NDIS MAC drivers. You can search for
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"Bindings = NDIS_MAC_driverFor example, to search for an NDIS driver for the 3Com* EtherLink II* board, find the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Bindings = elkinii.dosIf you don't know the name of the NDIS driver to search for, see the documentation included with your network board.PERFORMANCE="REQUIRED"Comment out (with a semicolon) all bindings lines found.For example, your PROTOCOL.INI file for a 3Com EtherLink II LAN driver might look like the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[ETHERNET]
   .
   .
   ; Bindings = elkinii.dosPERFORMANCE="REQUIRED"After each disabled binding line, add a line to bind the NDIS protocol to an ODI LAN driver.
PAGENUM=226 ID="BP215"Follow the same syntax as the line you disable by a comment, using the ODI LAN driver name instead of the NDIS driver name. For example, to add a line for the 3Com EtherLink II ODI LAN driver 3C503.COM, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"[ETHERNET]
   .
   .
   ; Bindings = elkinii.dos
   Bindings = x3c503Driver names in PROTOCOL.INI cannot start with a number. Therefore, place an 
x before 3Com drivers and other drivers that start with a number (for example: 
MOREINFO="NONE"Bindings = x3C503.)PERFORMANCE="REQUIRED"(Conditional) If you have two or more network boards using the same ODI LAN driver, type an instance number to bind the NDIS protocol to a particular occurrence of a board.By default, 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 network boards, direct NDIS to use the sec-ond board by typing an instance number for the second board at the end of its name, as shown:
FORMAT="LINESPECIFIC"MOREINFO="NONE"[ETHERNET]
   .
   .
   ; Bindings = elkinii.dos
   Bindings = ne20002PERFORMANCE="REQUIRED"(Conditional) If you have additional ODI drivers, bind the NDIS protocol to them. To bind the NDIS protocol to more than one ODI LAN 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
PAGENUM=227 ID="BP216"FORMAT="LINESPECIFIC"MOREINFO="NONE"Bindings = ne2000,ne1000PERFORMANCE="REQUIRED"Save and exit the PROTOCOL.INI file. RENDERAS="SECT1"ID="FM84916"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11351"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11352"BOOK="_idx" COLLECTION="nw41" TIDREF="i3065"
FileModify the CONFIG.SYS file with an ASCII text editor toMARK=BULLETSet the LASTDRIVE variable to Z for the NetWare DOS RequesterTM softwareLoad the NDIS Protocol ManagerRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. For example, to use the Novell DOS 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Load the NDIS Protocol Manager by adding a line similar to the following to the CONFIG.SYS file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"device = path protman.dos /i:pathReplace both
 path variables with the directory location of the PROTOCOL.INI file.
PAGENUM=228 ID="BP217"/I: directs the CONFIG.SYS file to search for the PROTOCOL.INI file in the specified pathname.The name and path of the NDIS Protocol Manager depends on the NDIS-based operating system you are running. See the manufacturer's documentation for information.PERFORMANCE="REQUIRED"Remove all references to the NDIS LAN drivers from the CONFIG.SYS file.For example, if your CONFIG.SYS file had a 
MOREINFO="NONE"device=pathMOREINFO="NONE" elnkii.dos statement to load an ELNKII.DOS NDIS driver, you would remove it from the file.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11353"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11354"BOOK="_idx" COLLECTION="nw41" TIDREF="i3065"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the ODI LAN driver, the ODINSUP protocol, the protocol stacks, and the NetWare DOS Requester software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load the ODI components:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driver
odinsup
netbind
ipxodi
vlmReplace path with the directory where the ODINSUP.COM and NET.CFG files are found. The ODINSUP protocol cannot execute unless it can access the NET.CFG file in the proper directory path.Replace odi_lan_driver with the name of the ODI LAN driver that your workstation is using.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.
PAGENUM=229 ID="BP218"RENDERAS="SECT2"ID="FM77502"Modifying the IDXID="w11355"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11356"BOOK="_idx" COLLECTION="nw41" TIDREF="i3065"
FileModify the NET.CFG file with an ASCII text editor toMARK=BULLETEnable the required Ethernet and token ring frame typesBind the ODINSUP protocol to a particular ODI LAN driverIncrease the size of the packet that can be transmitted through the Link Support Layer program (if necessary)RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the NET.CFG file with an ASCII text editor. For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enable the appropriate frame types for the ODINSUP software. The following table lists the supported frame types for the ODINSUP software.LABEL="12-1" PGWIDE=0 TOCENTRY="1" Frame Types Supported by ODINSUPCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"BoardCOLNAME=2 ROTATE="0" MOREROWS="0"Frame TypesVALIGN="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_802.3ETHERNET_SNAPETHERNET_IIPERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Enter the following line at the top of the NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"link driver odi_lan_driver
PAGENUM=230 ID="BP219"Replace odi_lan_driver with the name of your ODI LAN driver. For example, for a token ring LAN driver, enterFORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"link driver ntr2000PERFORMANCE="REQUIRED"Under the Link Driver heading, add the lines to enable all frame types supported by the ODI LAN driver.For example, to enable all frame types for token ring, add the following lines:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ntr2000
   frame token-ring
   frame token-ring_snapOr, to enable all frame types for an Ethernet, add the following lines:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   frame ethernet_802.2
   frame ethernet_802.3
   frame ethernet_ii
   frame ethernet_snapThe first frame defined is the only one used for the initial "Get Nearest Server" request.Therefore, if you have any servers using only one frame type, list that frame type first. This allows your client workstation to make a default connection to those servers.Whenever you edit the NET.CFG file, you must indent settings, as well as follow the other format requirements.  See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for information.PERFORMANCE="REQUIRED"Bind ODINSUP to one or more ODI LAN drivers.Do this by adding the Protocol ODINSUP option to your NET.CFG file: 
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
   bind odi_lan_driverReplace odi_lan_driver with the name of your ODI LAN driver.ODINSUP can be bound to a maximum of four ODI LAN drivers for each network board in your client workstation.
PAGENUM=231 ID="BP220"When ODINSUP is bound to an ODI LAN driver, the network board for that driver is used for the NDIS-based network transmissions.For example, for a token-ring ODI LAN driver, add the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
   bind ntr2000If you have multiple network boards using the same ODI LAN driver, specify an instance number.By default, ODINSUP searches the network board slots in order and binds only to the first board of that type that it finds. To have ODINSUP bind to ODI LAN drivers additional to the first one found, you must specify an instance number. For example, if you have two token-ring network boards, bind ODINSUP to both boards by typing an instance number for the second one, as shown:
FORMAT="LINESPECIFIC"MOREINFO="NONE"protocol odinsup
   bind ntr2000
   bind ntr2000 2See "BOOK="ws_d2enu" COLLECTION="nw41"Protocol ODINSUP Option" in Chapter 2 of 
NetWare Client for DOS and MS Windows Technical Reference for more information.PERFORMANCE="REQUIRED"(Optional) Increase the 
IDXID="w11357"BOOK="_idx" COLLECTION="nw41" TIDREF="i3186"
size of the packet transmitted through the Link Support Layer (LSL)Increasing the packet size might improve transmission speed if you are using a Token Ring 16/4 board.For other boards, see the board documentation to determine the maximum packet size supported. If the board supports a packet size larger than 1514 (the Link Support Layer default), transmission speed might improve if you increase the LSLTM default to the board's maximum allowed size.To increase the default, add the following lines to the NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"link support
   buffers number buffer_sizeReplace
 number with a number of buffers greater than 1.
PAGENUM=232 ID="BP221"Replace
 buffer_size with a number of bytes greater than 576. The NetWare Client files for DOS and MS Windows 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, 14 buffers multiplied by 4222 bytes equals 58,828 bytes. Therefore, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"link support
   buffers 14 4222For Token Ring 16/4 boards, NetWare Client files will probably have maximum performance if you specify 14 buffers, each with a size of 4222 bytes, as shown in the previous example.  For NDIS protocol stacks requiring a RECEIVE LOOK AHEAD data size larger than the maximum size supported by the LAN driver (MLID), you should use the BUFFERED parameter in the "Protocol ODINSUP" section of the NET.CFG file. This allocates a double buffer size in memory to satisfy the necessary data size needed for the NDIS protocol stack.PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file. RENDERAS="SECT1"ID="FM85837"Loading the IDXID="w11358"BOOK="_idx" COLLECTION="nw41" TIDREF="i3063"
ODINSUP 
SoftwareLoading the ODINSUP.COM file requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that your NDIS-based network and NDIS board drivers are setup and running.IDREF="FM92965"See "Installing MAC Drivers and an NDIS Protocol Manager on Client Workstations" on page 223 for more information.PERFORMANCE="REQUIRED"Ensure that the ODINSUP.COM and NetWare Client software files are installed on each client workstation that you want to connect to both NetWare and NDIS-based networks.
PAGENUM=233 ID="BP222"IDREF="FM77543"See "Installing the ODINSUP.COM and NetWare Client Files" on page 223 and 
IDREF="FM99590""Binding ODI LAN Drivers to the NDIS Protocol Stack" on page 224 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM84916"See "Modifying the DOS System and NetWare Client Configuration Files" on page 227 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the ODINSUP.COM and NetWare Client software files.RENDERAS="SECT1"ID="FM46361"Unloading the 
ODINSUPIDXID="w11359"BOOK="_idx" COLLECTION="nw41" TIDREF="i3063"
 SoftwarePERFORMANCE="REQUIRED"Unload all VLMTM files by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload IPXODI by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXODI /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload ODINSUP by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"ODINSUP /U MOREINFO="NONE"<Enter>Always unload the files in reverse order from the order in which you loaded them. Unloading the files in any order other than reverse order is impossible.RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for ODINSUPCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"Protocol ODINSUP Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference COLNAME=1 ROTATE="0" MOREROWS="0"Setting up ODINSUP with other operating systemsCOLNAME=2 ROTATE="0" MOREROWS="0""ODINSUP Interoperability Configurations for DOS Workstations," NetWare Application Notes, Feb 93 (Novell part # 164-000032-002)"NetWare and LAN Server Client Interoperability via ODINSUP: Part 1," NetWare Application Notes, Sep 92 (Novell part # 164-000031-009)"NetWare and LAN Server Client Interoperability via ODINSUP: Part 2," NetWare Application Notes, Nov 92 (Novell part # 164-000031-011)LABEL="13"PAGENUM=235 ID="BP223"ID="FM88338"Setting Up the NetWare for IBM LAN Support Program ModulesRENDERAS="SECT1"OverviewThis chapter explains how to set up IDXID="w11360"BOOK="_idx" COLLECTION="nw41" TIDREF="i654"
client workstations to support using an 
IBM 
LAN Support programs that contain network boards which do not support ODITM (or compliant) LAN drivers for connecting to NetWare® networks.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM46633"Installing an IBM LAN Support Program COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM46633"236COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM94575"Installing the LANSUP.COM and NetWare Client Files  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94575"236COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM33333"Modifying the DOS System and NetWare Client Configuration Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM33333"238COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM50702"Loading the LANSUP.COM File COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50702"241COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM11596"Unloading the LANSUP.COM File COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11596"242RENDERAS="SECT1"IntroductionIDXID="w11361"BOOK="_idx" COLLECTION="nw41" TIDREF="i2058"The NetWare DOS RequesterTM software uses protocol drivers and network drivers written to the Open Data-Link InterfaceTM (ODI) specification. The IBM LAN Support programs, except for PCNet Support, can use protocol drivers written to the NDIS specification.The IBM LAN Support module (the LANSUP.COM file) acts as an interface between the NetWare ClientTM software and the IBM LAN Support programs. This interface allows IBM LAN Support programs to communicate with NetWare Client through NDIS network drivers.PAGENUM=236 ID="BP224"LANSUP.COM is necessary only when you want the NDIS driver to control the network board while accessing one of the IBM LAN Support programs, or when you do not have an ODI (or compliant) LAN driver for your network board.NetWare Client support for NDIS protocols must be 
set up on each client workstation that you want to access the IBM LAN Support programs from.The complete IDXID="w11362"BOOK="_idx" COLLECTION="nw41" TIDREF="i2058"
setup for client workstations using LANSUP.COM requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM46633"Installing an IBM LAN Support Program IDREF="FM94575"Installing the LANSUP.COM and NetWare Client Files IDREF="FM33333"Modifying the DOS System and NetWare Client Configuration Files RENDERAS="SECT1"ID="FM46633"Installing an IBM LAN Support ProgramLANSUP.COM is an interface for the following IBM LAN Support programs:TYPE="VERT"Extended IDXID="w11363"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
ServicesIDXID="w11364"BOOK="_idx" COLLECTION="nw41" TIDREF="i1399"LAN Server
IDXID="w11365"BOOK="_idx" COLLECTION="nw41" TIDREF="i2042"You need to install and load one of these programs before setting up and configuring client workstations for a NetWare connection. See the documentation provided with these programs for information on installation and setup.If you have Extended Services or LAN Services, you might also want to set up the NetBIOS protocol. After completing the procedures in this chapter, IDREF="FM35822"See Chapter 14, "Setting Up NetBIOS Protocol Support," on page 245.RENDERAS="SECT1"ID="FM94575"Installing the IDXID="w11366"BOOK="_idx" COLLECTION="nw41" TIDREF="i2058"
LANSUP.COM and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyThe LANSUP.COM file is automatically copied to the NetWare Client directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.PAGENUM=237 ID="BP225"Once you install the NetWare Client for DOS and MS Windows, the Extended Services and LAN Services programs cannot use the network board to make connections until you have completely set up the LANSUP.COM file as instructed in this chapter. RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the LANSUP.COM and other client files to the NetWare Client directory.To manually copy the LANSUP.COM file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM22479"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCLASS=DISK or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1CLASS=DISKCOLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"LANSUP.CO_  lan_driver.CO_To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the LANSUP.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:LANSUP.CO_ C:\NWCLIENT\LANSUP.COM MOREINFO="NONE"<Enter>
PAGENUM=238 ID="BP226"PERFORMANCE="REQUIRED"Repeat 
IDREF="FM22479"Step 1 until the LANSUP.COM and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM33333"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11367"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11368"BOOK="_idx" COLLECTION="nw41" TIDREF="i2059"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS Requester software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. For example, to use the Novell
® DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.
PAGENUM=239 ID="BP227"RENDERAS="SECT2"Modifying the IDXID="w11369"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11370"BOOK="_idx" COLLECTION="nw41" TIDREF="i2059"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the LANSUP.COM file, the protocol stacks, and the NetWare DOS Requester software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load LANSUP.COM and NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
lansup
ipxodi
vlmReplace 
path with the directory where the LANSUP.COM and NET.CFG files are found. The LANSUP.COM file cannot execute unless it can access the NET.CFG file in the proper directory path.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11371"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11372"BOOK="_idx" COLLECTION="nw41" TIDREF="i2059"
FileThe IBM LAN support module (the LANSUP.COM file) requires you to make the following modifications to your NET.CFG file:MARK=BULLETSpecify the frame type for each client workstationSee the following procedure for details on how to configure this parameter for LANSUP.COM.(Optional) Specify variables for the following parameters:TYPE="VERT"ALTERNATELINK STATIONSMAX FRAME SIZENODE ADDRESSOPENPROTOCOLPAGENUM=240RPLSAPSSee Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for details on how to configure these parameters for LANSUP.Configure the frame type for LANSUP.COM by completing the following procedure.RENDERAS="SECT2"ID="FM55125"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with an ASCII text editor.For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enable the appropriate frame types for LAN.COM.Because the LANSUP.COM driver uses the Token-Ring Topology Support Module (TSM), LANSUP.COM supports only the following boards and frame types:LABEL="13-1" PGWIDE=0 TOCENTRY="1" Frame Types Supported by LANSUPCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"BoardsCOLNAME=2 ROTATE="0" MOREROWS="0"Frame TypesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Ethernet  PCNet  Token ring COLNAME=2 ROTATE="0" MOREROWS="0"TOKEN-RING  TOKEN-RING_SNAPPAGENUM=241 ID="BP229"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Enter the following line at the top of the NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"link driver lansupPERFORMANCE="REQUIRED"Under the Link Driver heading, add the lines to enable frame types.For example, to enable a frame type for token ring, add the following lines to the file:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver lansup
    frame token-ringTo enable both frame types for Ethernet, add the following lines: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 any servers using only one frame type, list that frame type first. This allows your client workstation to make a default connection to those servers.Whenever you edit the NET.CFG file, you must indent settings, as well as follow the other format requirements.  See Chapter 2, "BOOK="ws_d2enu" COLLECTION="nw41"NET.CFG Options Reference," in NetWare Client for DOS and MS Windows Technical Reference for information.PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file. RENDERAS="SECT1"ID="FM50702"Loading the IDXID="w11373"BOOK="_idx" COLLECTION="nw41" TIDREF="i2058"
LANSUP.COM FileLoading the LANSUP.COM file for the IBM LAN Support programs requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that your IBM LAN Support programs are set up properly.IDREF="FM46633"see "Installing an IBM LAN Support Program" on page 236 for more information.
PAGENUM=242 ID="BP230"PERFORMANCE="REQUIRED"Ensure that the LANSUP.COM and NetWare Client software files are installed on each client workstation that you want to connect to both NetWare and IBM LAN Support programs.IDREF="FM94575"see "Installing the LANSUP.COM and NetWare Client Files" on page 236 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM33333"see "Modifying the DOS System and NetWare Client Configuration Files" on page 238 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the LANSUP.COM and NetWare Client software files.RENDERAS="SECT1"ID="FM11596"Unloading
 the IDXID="w11374"BOOK="_idx" COLLECTION="nw41" TIDREF="i2058"
LANSUP.COM FilePERFORMANCE="REQUIRED"Unload all VLMTM files by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload IPXODI by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXODI /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload LANSUP.COM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LANSUP /U MOREINFO="NONE"<Enter>Always unload the files in reverse order from the order in which you loaded them. Unloading the files in any order other than reverse order is impossible.PAGENUM=243 ID="BP231"RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for LAN Support programsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"Link Driver Option" and "BOOK="ws_d2enu" COLLECTION="nw41"Link Support Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference LABEL="14"PAGENUM=245 ID="BP232"ID="FM35822"Setting Up NetBIOS Protocol SupportRENDERAS="SECT1"OverviewThis chapter explains how to set up and configure the Novell® NetBIOS protocol emulator for NetBIOS applications running on networks based on the Internet Protocol ExchangeTM (IPX) architecture.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM72202"Installing a NetBIOS Application COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72202"246COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM69872"Installing the NETBIOS.EXE and NetWare Client Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69872"247COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM78852"Modifying the DOS System and NetWare Client Configuration Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM78852"248COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM84580"Loading the NetBIOS Emulator  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM84580"250COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM17638"Unloading the NetBIOS Emulator COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM17638"251RENDERAS="SECT1"IntroductionIDXID="w11375"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"NetBIOS (Network Basic Input/Output System) is the IBM standard protocol for applications developed to run peer-to-peer communications on the IBM PC Network and the IBM Token-Ring Network. NetBIOS has become widely accepted as a standard for network interfacing.The 
NetWare® ClientTM for DOS and MS Windows provides a NetBIOS driver that emulates the NetBIOS protocol. This emulator allows the NetWare IPXTM to interface with the NetBIOS Interrupt 5Ch and an alternate interface, Interrupt 2Ah. PAGENUM=246 ID="BP233"The NetBIOS provided by Novell is an emulator because it does not transmit NetBIOS packets. Instead, NetBIOS packets are encapsulated in IPX packets, and the IPX packets are transmitted.The NetBIOS protocol was designed for small-scale networks. While Novell has added functionality to the original specification, the NetBIOS emulation still works most effectively with small-scale networks.Therefore, if your network contains several thousand workstations and your LAN segments are interconnected with more than one router, use SPXTM instead of NetBIOS if your applications support SPX.NetWare CLient support for the IDXID="w11376"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"
NetBIOS emulator must be 
set up on each client workstation that you want to access NetBIOS applications from.The complete setup for client workstations using NetBIOS requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM72202"Installing a NetBIOS Application IDREF="FM69872"Installing the NETBIOS.EXE and NetWare Client Files IDREF="FM78852"Modifying the DOS System and NetWare Client Configuration Files RENDERAS="SECT1"ID="FM72202"Installing a IDXID="w11377"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"
NetBIOS IDXID="w11378"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
ApplicationNetBIOS is the IBM standard protocol for applications developed to run peer-to-peer communications on the IBM PC Network and the IBM Token-Ring Network.You need to install and load a NetBIOS application on a server before setting up and configuring client workstations for a NetBIOS connection.See the documentation provided with the application for information on installation and setup.PAGENUM=247 ID="BP234"RENDERAS="SECT1"ID="FM69872"Installing the IDXID="w11379"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"
NETBIOS.EXE and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyNETBIOS.EXE and the other client files are automatically copied to the NetWare Client directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the NETBIOS.EXE and other client files to the NetWare Client directory.To manually copy the NETBIOS.EXE file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM30027"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"NETBIOS.CO_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN DriversCLASS=DISK or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1CLASS=DISKCOLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_To expand a file, type
PAGENUM=248 ID="BP235"FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the NETBIOS.EXE file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:NETBIOS.EX_ C:\NWCLIENT\NETBIOS.EXE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM30027"Step 1 until the NETBIOS.EXE and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM78852"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11380"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11381"BOOK="_idx" COLLECTION="nw41" TIDREF="i2663"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS RequesterTM software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. For example, to use the Novell DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.
PAGENUM=249 ID="BP236"RENDERAS="SECT2"Modifying the IDXID="w11382"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11383"BOOK="_idx" COLLECTION="nw41" TIDREF="i2663"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the ODITM LAN driver, the NetBIOS emulator (the NETBIOS.EXE file), and the NetWare DOS Requester software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load the NETBIOS.EXE and NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driver
ipxodi
netbios
vlmReplace path with the directory where the NETBIOS.EXE and NET.CFG files are found. The NETBIOS.EXE file cannot execute unless it can access the NET.CFG file in the proper directory path.Replace odi_lan_driver with the name of the ODI LAN driver that your workstation is using.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11384"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11385"BOOK="_idx" COLLECTION="nw41" TIDREF="i2663"
FileThe NetBIOS emulator (the NETBIOS.EXE file) allows you to specify variables for the following parameters in your NET.CFG file:TYPE="VERT"NETBIOS ABORT TIMEOUTNETBIOS BROADCAST COUNTNETBIOS BROADCAST DELAYNETBIOS COMMANDSNETBIOS INTERNETNETBIOS LISTEN TIMEOUTNETBIOS RECEIVE BUFFERSNETBIOS RETRY COUNTPAGENUM=250NETBIOS RETRY DELAYNETBIOS SEND BUFFERSNETBIOS SESSIONNETBIOS VERIFY TIMEOUTNPATCHSee "BOOK="ws_d2enu" COLLECTION="nw41"NetBIOS Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for details on how to configure for NetBIOS support.Configure the parameters for the Novell NetBIOS software by completing the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with an ASCII text editor.For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Make the necessary configurations for your particular NetBIOS application.See the manufacturer's documentation for information.PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file. RENDERAS="SECT1"ID="FM84580"Loading the IDXID="w11386"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"
NetBIOS EmulatorLoading the 
NETBIOS.EXE file for NetBIOS applications requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that your NetBIOS applications are set up properly.IDREF="FM72202"See "Installing a NetBIOS Application" on page 246 for more information.
PAGENUM=251 ID="BP238"PERFORMANCE="REQUIRED"Ensure that the NETBIOS.EXE and NetWare Client software files are installed on each client workstation that you want to run NetBIOS applications.IDREF="FM69872"See "Installing the NETBIOS.EXE and NetWare Client Files" on page 247 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM78852"See "Modifying the DOS System and NetWare Client Configuration Files" on page 248 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the NETBIOS.EXE and NetWare Client software files.Your DOS or MS Windows client workstation might require up to a minute after you load the NetWare NetBIOS protocol before it is ready to run a NetBIOS application.RENDERAS="SECT1"ID="FM17638"Unloading the IDXID="w11387"BOOK="_idx" COLLECTION="nw41" TIDREF="i2662"
NetBIOS
 EmulatorThe following commands, issued in the order given, unload the NETBIOS.EXE file.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Unload all VLMTM files by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload NetBIOS by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETBIOS /U MOREINFO="NONE"<Enter>Always unload the files in reverse order from the order in which you loaded them. Unloading the files in any order other than reverse order is impossible.PAGENUM=252 ID="BP239"RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for NetBIOSCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"NetBIOS Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference LABEL="15"PAGENUM=253 ID="BP240"ID="FM39829"Setting Up Source Routing Support for a Token-Ring NetworkRENDERAS="SECT1"OverviewThis chapter explains how to use and install the NetWare® source routing driver for token-ring networks.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM21679"Installing Source Routing on the ServerCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM21679"255COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM10775"Installing the ROUTE.COM and NetWare Client FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10775"256COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29954"Modifying the DOS System and NetWare Client Configuration FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29954"257COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM85479"Loading the Source Routing DriverCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85479"259COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM20452"Unloading the Source Routing DriverCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM20452"260RENDERAS="SECT1"IntroductionIDXID="w11388"BOOK="_idx" COLLECTION="nw41" TIDREF="i4211"
The NetWare source routing driver (the ROUTE.COM file) enables communication across IBM token-ring network bridges. Any type of IDXID="w11389"BOOK="_idx" COLLECTION="nw41" TIDREF="i1193"
DOS ODITM protocol stack can use this source routing functionality.The following figure shows an IDXID="w11390"BOOK="_idx" COLLECTION="nw41" TIDREF="i514"
example of a network configuration using IBM source routing bridges.PAGENUM=254 ID="BP241"LABEL="15-1" FLOAT="0"Network Configuration Using Source Routing BridgesFILEREF="c41ug26a.tif"The NetWare source routing software can route only IPX packets.  PAGENUM=255 ID="BP242"NetWare Client support for the source routing IDXID="w11391"BOOK="_idx" COLLECTION="nw41" TIDREF="i4211"
driver (the ROUTE.COM file) must be 
set up on each client workstation that you want to use on a token-ring network.The complete setup for client workstations using the ROUTE.COM file requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM21679"Installing Source Routing on the Server IDREF="FM10775"Installing the ROUTE.COM and NetWare Client Files IDREF="FM29954"Modifying the DOS System and NetWare Client Configuration Files RENDERAS="SECT1"ID="FM21679"Installing IDXID="w11392"BOOK="_idx" COLLECTION="nw41" TIDREF="i4211"
Source IDXID="w11393"BOOK="_idx" COLLECTION="nw41" TIDREF="i4514"
Routing on the ServerPERFORMANCE="REQUIRED"At the server console, load ROUTE.NLM by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ROUTE MOREINFO="NONE"<Enter>You can also load ROUTE.NLM in a startup file. ROUTE.NLM is located in the SYS:SYSTEM directory. You can load it with command line parameters. See 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference for more information about the parameters.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, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ROUTE BOARD=02 MOREINFO="NONE"<Enter>You can change any source routing parameter after ROUTE is loaded. Type the LOAD ROUTE command followed by the parameter you want to change. PAGENUM=256 ID="BP243"RENDERAS="SECT1"ID="FM10775"Installing the 
ROUTE.COM and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyIDXID="w11394"BOOK="_idx" COLLECTION="nw41" TIDREF="i3895"
ROUTE.COM and the other client files are automatically copied to the NetWare ClientTM directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the ROUTE.COM and other client files to the NetWare Client directory.To manually copy the ROUTE.COM file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM33757"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"ROUTE.CO_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN Drivers or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1CLASS=DISKCOLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_  NTR2000.CO_  LANSUP.CO_To expand a file, type
PAGENUM=257 ID="BP244"FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the ROUTE.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:ROUTE.CO_ C:\NWCLIENT\ROUTE.COM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Install a token-ring ODI LAN driver. The ROUTE.COM file requires this.Novell
® provides the NTR2000.COM file, which replaces the previously used TOKEN.COM file.See the manufacturer's documentation for information about what token-ring ODI LAN driver to use with your network board.PERFORMANCE="REQUIRED"(Conditional) If you want to connect to both NetWare and an IBM LAN Support program, such as LAN Manager, you should also expand and copy the LANSUP.COM file to the NetWare Client directory on each workstation.IDREF="FM88338"See Chapter 13, "Setting Up the NetWare for IBM LAN Support Program Modules," on page 235 for information.PERFORMANCE="REQUIRED"Repeat 
IDREF="FM33757"Step 1 until the ROUTE.COM and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM29954"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS and STARTNET.BAT files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11395"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11396"BOOK="_idx" COLLECTION="nw41" TIDREF="i4212"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS RequesterTM software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. PAGENUM=258 ID="BP245"For example, to use the Novell
® DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11397"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11398"BOOK="_idx" COLLECTION="nw41" TIDREF="i4212"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the ODITM LAN driver, the source routing driver (the ROUTE.COM file), and the NetWare DOS Requester software.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load the ROUTE.COM and NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driverroute
ipxodi
vlmReplace 
path with the directory where the ROUTE.COM and NET.CFG files are found. The ROUTE.COM file cannot execute unless it can access the NET.CFG file in the proper directory path.Replace 
odi_lan_driver with the name of the ODI LAN driver that your workstation is using. For example, Novell provides the NTR2000.COM file or the LANSUP.COM file.The command to load the ROUTE.COM file should be added after the odi_lan_driverPAGENUM=259 ID="BP246" file, but before the protocol stack you are using, such as the IPXODI.COM file.  Add any necessary command line parameters after the route statement.Use the following parameters for configuring the ROUTE.COM driver:
FORMAT="LINESPECIFIC"MOREINFO="NONE"BOARD=number
CLEAR
DEF
GBR
MBR
NODES=number
REMOVE=numberIf two frame type are used on your network, load the ROUTE.COM file twice in the STARTNET.BAT file. You must load ROUTE.COM once for each MOREINFO="NONE"BOARD=number statement used.See Chapter 3, "
BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference," in 
NetWare Client for DOS and MS Windows Technical Reference for descriptions and details on how to use command line parameters for ROUTE.COM.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT1"ID="FM85479"Loading the IDXID="w11399"BOOK="_idx" COLLECTION="nw41" TIDREF="i4211"
Source Routing DriverLoading the 
ROUTE.COM file requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that the ROUTE.NLM program is loaded on the server you are connecting to.IDREF="FM21679"See "Installing Source Routing on the Server" on page 255 for more information.PERFORMANCE="REQUIRED"Ensure that the ROUTE.COM and NetWare Client software files are installed on each client workstation that you want to connect to a token-ring network.IDREF="FM10775"See "Installing the ROUTE.COM and NetWare Client Files" on page 256 for more information.
PAGENUM=260 ID="BP247"PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM29954"See "Modifying the DOS System and NetWare Client Configuration Files" on page 257 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the ROUTE.COM and NetWare Client software files.RENDERAS="SECT1"ID="FM20452"Unloading the IDXID="w11400"BOOK="_idx" COLLECTION="nw41" TIDREF="i4211"
Source 
Routing DriverPERFORMANCE="REQUIRED"Unload all VLMTM files by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload ROUTE.COM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"ROUTE /U MOREINFO="NONE"<Enter>Always unload the files in reverse order from the order in which you loaded them. Unloading the files in any order other than reverse order in impossible.RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Understanding more about source routingCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="cncptenu" COLLECTION="nw41"Source routing" in Concepts"Understanding Token-Ring Source Routing," NetWare Application Notes, May 91 (Novell part # 164-000030-005)IBM Token-Ring Network Architecture ReferenceLABEL="16"PAGENUM=261 ID="BP1B"ID="FM13494"Setting Up Named Pipes Protocol SupportRENDERAS="SECT1"OverviewThis chapter explains how to set up client workstations to use the Named Pipes protocol.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM92934"Installing a Named Pipes Server and Client-Server ApplicationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92934"263COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM35865"Installing the Named Pipes Extender and NetWare Client FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM35865"263COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM80977"Modifying the DOS System and NetWare Client Configuration FilesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80977"264COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM88660"Loading the Named Pipes ExtenderCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM88660"268COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM98884"Unloading the Named Pipes ExtenderrCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98884"269RENDERAS="SECT1"IntroductionIDXID="w11401"BOOK="_idx" COLLECTION="nw41" TIDREF="i3606"Named Pipes are the basis for communication between the client and advanced client-server applications such as Microsoft SQL Server and Microsoft Comm Server software.Client-server computing provides a mode of distributed network computing in which an IDXID="w11402"BOOK="_idx" COLLECTION="nw41" TIDREF="i260"
application is executed cooperatively by two client workstations.The client component of the application (the front end) executes on one client workstation, while the server component (the back end) runs on a second client workstation. PAGENUM=262 ID="BP2B"Client-server computing allows more effective use of computing resources, higher performance, greater flexibility, simpler upgrades, and (for some applications) greater reliability and data integrity.For NetWare® client workstations, communication between client-server applications is implemented most frequently using the Named Pipes interprocess communication (IPC) protocol. A Named Pipes client workstation can be configured to operate in default mode or peer mode. In default mode, Named Pipes client workstations obtain names for Named Pipes servers by querying an IPXTM (or compatible) router table. In this mode, Named Pipes client workstations request specific server names on an as needed basis.In peer mode, Named Pipes client workstations maintain their own Named Pipes server table. When the Named Pipes Extender is loaded in peer mode, a General Service Query is issued and the query responses from Named Pipes servers are compiled into a table at each client workstation. To configure for peer mode, see "BOOK="ws_d2enu" COLLECTION="nw41"Named Pipes Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.NetWare Client support for the IDXID="w11403"BOOK="_idx" COLLECTION="nw41" TIDREF="i2595"
Named 
Pipes protocol (the DOSNP.EXE file) must be set up on each client workstation that you want to access Named Pipes client-server applications from.In most cases, you must also set configuration options for the Link Support LayerTM (LSL) software. The complete setup for client workstations using the Named Pipes protocol requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM92934"Installing a Named Pipes Server and Client-Server Application IDREF="FM35865"Installing the Named Pipes Extender and NetWare Client Files IDREF="FM80977"Modifying the DOS System and NetWare Client Configuration Files PAGENUM=263 ID="BP3B"RENDERAS="SECT1"ID="FM92934"Installing a Named Pipes Server and Client-Server ApplicationThe NetWare ClientTM for OS/2 software allows a Named Pipes server such as an SQL server to function on a Novell® network.You need to set up a NetWare OS/2 client workstation and configure it for Named Pipes services before setting up and configuring DOS and MS Windows client workstations for a Named Pipes connection. See NetWare Client for OS/2 User Guide for information about installation and setup.You also need to install the client and server portion of the client-server software that you want to run. See the manufacturer's documentation for information.RENDERAS="SECT1"ID="FM35865"Installing the Named Pipes IDXID="w11404"BOOK="_idx" COLLECTION="nw41" TIDREF="i2595"
Extender and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyThe Named Pipes Extender and other client files are automatically copied to the NetWare Client directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the DOSNP.EXE and other client files to the NetWare Client directory.To manually copy the DOSNP.EXE file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.PAGENUM=264 ID="BP4B"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM14030"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"DOSNP.EX_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN Drivers or CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the DOSNP.EXE file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:DOSNP.EX_ C:\NWCLIENT\DOSNP.EXE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Conditional) If you are running DOSNP.EXE within MS Windows, expand and copy the NETAPI.DL_ file from the WINDOWS directory on the 
CLASS=DISKWSDOS2_2 diskette
 for NetWare Client for OS/2 the SYSTEM directory for MS Windows.PERFORMANCE="REQUIRED"Repeat 
IDREF="FM14030"Step 1 until the DOSNP.EXE and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM80977"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.PAGENUM=265 ID="BP5B"RENDERAS="SECT2"Modifying the IDXID="w11405"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11406"BOOK="_idx" COLLECTION="nw41" TIDREF="i2596"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS RequesterTM software.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. For example, to use the Novell
® DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11407"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11408"BOOK="_idx" COLLECTION="nw41" TIDREF="i2596"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support Layer (the LSL.COM file), the ODITM LAN driver, the DOS Named Pipes Extender (the DOSNP.EXE file), and the NetWare DOS Requester software.PAGENUM=266 ID="BP6B"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load the DOSNP.EXE and NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driver
ipxodi
vlm
dosnpReplace 
path with the directory where the DOSNP.EXE and NET.CFG files are found. The DOSNP.EXE file cannot execute unless it can access the NET.CFG file in the proper directory path.Replace 
odi_lan_driver with the name of the ODI LAN driver that your client workstation is using.When a Named Pipes client workstation is configured for default mode, DOSNP.EXE uses the NetWare DOS Requester to search for the table of Named Pipes servers. This requires that the BIND.VLM file be loaded.  If a Named Pipes client workstation is configured for peer mode, then the NetWare DOS Requester is not required to establish a connection to a Named Pipes server.PERFORMANCE="REQUIRED"(Conditional) If you are running an SQL server program, add the following line for the Microsoft Named Pipe Net Library file after the entry for the VLM.EXE file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"dbmmpipeEnsure that this file is loading only in the STARTNET.BAT file. If you are running DOSNP on an MS Windows client workstation, do not load the IPXODI or DOSNP files into high memory.  Also, you do not need to load the DBNMPIPE file. The DBNMP3.DLL file supports the function in MS Windows. If you need to run an MS-DOS SQL server program from an MS Windows MS-DOS session, load the DBNMPIPE file in that session.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.
PAGENUM=267 ID="BP7B"RENDERAS="SECT2"Modifying the IDXID="w11409"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11410"BOOK="_idx" COLLECTION="nw41" TIDREF="i2596"
FileThe DOS Named Pipes Extender (the DOSNP.EXE file) allows you to specify variables for the following parameters in your NET.CFG file:TYPE="VERT"NP MAX COMM BUFFERSNP MAX MACHINE NAMESNP MAX OPEN NAMED PIPESNP MAX SESSIONS BUFFERSSee "BOOK="ws_d2enu" COLLECTION="nw41"Named Pipes Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for details on how to configure for Named Pipes support.The Named Pipes parameters in the NET.CFG file should be left-justified. Configure parameters for the DOSNP software by following the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with an ASCII text editor.For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Make the necessary configuration changes for your particular client-server application.See the manufacturer's documentation for information.
MARK=BULLETIf you need more than the default four simultaneous Named Pipes connections on a client workstation, add the following line to the file:FORMAT="LINESPECIFIC"MOREINFO="NONE" np max open named pipes numberReplace number with the total number of Named Pipes that can be opened. The range is 4 through 128.If you need other than the default six communication buffers that the Named Pipes Extender uses, add the following line to the file:PAGENUM=268 ID="BP8B"FORMAT="LINESPECIFIC"MOREINFO="NONE" np max com buffers numberReplace number with the maximum number of buffers that can be used. The range is 4 through 40.If you need to configure client workstations for the Named Pipes peer mode, add the following line to the file:FORMAT="LINESPECIFIC"MOREINFO="NONE" np max machine names numberReplace number with the total number of Named Pipes servers that are maintained in a table at each client workstation. The range is 4 through 50.This parameter is disabled by deleting the line in the NET.CFG file.If you need more than the default ten sessions open to a Named Pipes servers at one time, add the following line to the file:FORMAT="LINESPECIFIC"MOREINFO="NONE" np max sessions numberReplace number with the total number of Named Pipes servers that can be communicated with at one time. The range is 4 through 50. PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file.RENDERAS="SECT1"ID="FM88660"Loading the IDXID="w11411"BOOK="_idx" COLLECTION="nw41" TIDREF="i2595"
Named Pipes ExtenderLoading the DOSNP.EXE file for a NetWare connection to a Named Pipes server requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that your Named Pipes server and client-server applications are set up properly.IDREF="FM92934"See "Installing a Named Pipes Server and Client-Server Application" on page 263for more information.PERFORMANCE="REQUIRED"Ensure that the DOSNP.EXE and NetWare Client software files are installed on each client workstation that you want to connect to a Named Pipes server.IDREF="FM35865"See "Installing the Named Pipes Extender and NetWare Client Files" on page 263 for more information.
PAGENUM=269 ID="BP9B"PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM80977"See "Modifying the DOS System and NetWare Client Configuration Files" on page 264 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the DOSNP.EXE and NetWare Client software files.RENDERAS="SECT1"ID="FM98884"Unloading the IDXID="w11412"BOOK="_idx" COLLECTION="nw41" TIDREF="i2595"
Named 
Pipes ExtenderUnload DOSNP.EXE by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOSNP /U MOREINFO="NONE"<Enter>RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for Named PipesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"Named Pipes Options" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference LABEL=""PAGENUM=271 ID="BP256"Management ServicesRENDERAS="SECT1"OverviewThe Novell® system management technology provides advanced solutions to centrally manage and control your corporate computing environment.These solutions are standards-based, modular, and scalable---suitable for simple, standalone LANs as well as large, multi-site computing enterprises.Novell provides a comprehensive list of system management services that allow you to select the components you need and integrate the appropriate functionality into a customized management package. The NetWare® ClientTM for DOS and MS Windows software provides you with the following management agents:MARK=BULLETTarget Service Agent (TSA) softwareProvides support for programs that processes data moving between a specific target and Storage Management ServicesTM (SMS) applications, such as the NetWare SBACKUP utility or the NetWare NavigatorTM program, or other third-party management systems. SNMP Services, hosting MIB II, and Host MIB softwareProvides support for client workstations to be managed from the Novell NetWare Management SystemTM (NMS) software, from other industry-standard SNMP management consoles, or from other third-party management systems.PAGENUM=272 ID="BP257"RENDERAS="SECT1"ContentsThis section is divided into two chapters, with the following information discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"ChapterCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to set up the DOS client Target Service Agent to give SMSTM applications the ability to back up information on your client workstations or distribute filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM43744"Chapter 17, "Setting Up the Target Service Agent (TSA) Software"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM43744"273COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to set up the NetWare Desktop Small Network Management Protocol (SNMP) agent to give NMSTM services and other SNMP-based management systems the ability to access resources on client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54735"Chapter 18, "Configuring Client Workstations for Desktop SNMP Services"COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM54735"281LABEL="17"PAGENUM=273 ID="BP258"ID="FM43744"Setting Up the Target Service Agent (TSA) SoftwareRENDERAS="SECT1"OverviewThis chapter describes how to set up the Novell® Target Service AgentTM (TSA) software for network management through Storage Management ServicesTM (SMS) applications. The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM30205"Installing an SMS Application COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM30205"274COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55847"Installing the TSASMS.COM and NetWare Client Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55847"275COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM93792"Modifying the DOS System and NetWare Client Configuration Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM93792"276COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM48204"Loading the TSA Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM48204"278COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM97749"Unloading the TSA Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM97749"279RENDERAS="SECT1"IntroductionThe Novell IDXID="w11413"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
Target 
Service Agent (TSA) 
software (the TSASMS.COM file) is a program that processes data moving between a specific target and Storage IDXID="w11414"BOOK="_idx" COLLECTION="nw41" TIDREF="i4296"
Management Services 
(SMS) applications such as the 
NetWare 
SBACKUP utility or the NetWare NavigatorTM program. An SMSTM architecture-based application running on the server sends requests to the TSA software. The TSA software performs the following functions:MARK=BULLETReceives commands from the SMS application and translates those commands into data requests for the local operating system to handlePAGENUM=274 ID="BP259"Transfers the data requests to the local operating systemRetrieves the requested data from the local operating system and returns it to the SMS application in standard SMS formatThe Novell TSA software has the IDXID="w11415"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
following features:MARK=BULLETOperates as a terminate-and-stay-resident (TSR) programOccupies less than 7 KB of memory (using default settings)Supports MS DOS (3.3 and later), DR DOS® (5 and later), and Novell DOSTM (7 and later)Provides several levels of securityProvides adjustable read buffers size for increased performanceProvides adjustable stack size to reduce the overall memory usageNetWare Client support for the IDXID="w11416"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
TSA software (the TSASMS.COM file) must be set 
up on each 
client workstation that you want managed by an SMS application.The complete setup for client workstations using TSA software requires you to complete the following tasks:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"IDREF="FM30205"Installing an SMS Application IDREF="FM55847"Installing the TSASMS.COM and NetWare Client Files IDREF="FM93792"Modifying the DOS System and NetWare Client Configuration Files RENDERAS="SECT1"ID="FM30205"Installing an IDXID="w11417"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
SMS 
ApplicationYou need to IDXID="w11418"BOOK="_idx" COLLECTION="nw41" TIDREF="i4296"
install 
and load an SMS application on a server or host before setting up and configuring client workstations to be managed.See the documentation provided with the application for information on installation and setup.PAGENUM=275 ID="BP260"RENDERAS="SECT1"ID="FM55847"InstallingIDXID="w11419"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
 the TSASMS.COM and NetWare Client FilesRENDERAS="SECT2"Copying the Files to the NetWare Client Directory AutomaticallyThe 
TSASMS.COM file is 
automatically copied to the NetWare® ClientTM directory when you run the NetWare Client installation software.IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.RENDERAS="SECT2"Copying the Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation software, you must manually copy the TSASMS.COM and other client files to the NetWare Client directory.To manually copy the 
TSASMS.COM file and other client files from the NetWare Client for DOS and MS Windows diskettes, complete the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM64180"Expand and copy the following files from the NetWare Client for DOS and MS Windows diskettes to the NetWare Client directory (the default is C:\NWCLIENT).COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="15*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"DirectoryCOLNAME=3 ROTATE="0" MOREROWS="0"FilenameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\  \  \  \COLNAME=3 ROTATE="0" MOREROWS="0"IPXODI.CO_  LSL.CO_  VLM.EX_  filename.VL_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"\COLNAME=3 ROTATE="0" MOREROWS="0"TSASMS.CO_COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODICLASS=DISK CLASS=DISKLAN Drivers CLASS=DISKor CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"\DOSCOLNAME=3 ROTATE="0" MOREROWS="0"lan_driver.CO_To expand a file, type
PAGENUM=276 ID="BP261"FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the TSASMS.COM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:TSASMS.CO_ C:\NWCLIENT\TSASMS.COM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM64180"Step 1 until the TSASMS.COM and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM93792"Modifying the DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11420"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11421"BOOK="_idx" COLLECTION="nw41" TIDREF="i4428"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS RequesterTM software.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file with an ASCII text editor. For example, to use the Novell DOS 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.
PAGENUM=277 ID="BP262"RENDERAS="SECT2"ID="FM59978"Modifying the IDXID="w11422"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11423"BOOK="_idx" COLLECTION="nw41" TIDREF="i4428"
FileModify the STARTNET.BAT file with an ASCII text editor to load the Link Support LayerTM (the LSL.COM file), the ODITM LAN driver, the TSA software (the TSASMS.COM file), and the NetWare DOS Requester software.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Add the following lines, in the given order, to the STARTNET.BAT file to load the TSASMS.COM and NetWare Client files:FORMAT="LINESPECIFIC"MOREINFO="NONE"cd path
lsl
odi_lan_driver
ipxodi
vlm
tsasmsReplace 
path with the directory where the TSASMS.COM and NET.CFG files are found. The TSASMS.COM file cannot execute unless it can access the NET.CFG file in the proper directory path.Replace 
odi_lan_driver with the name of the ODI LAN driver that your workstation is using.You can use command line parameters in the STARTNET.BAT file to override NET.CFG parameters. See Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference," in NetWare Client for DOS and MS Windows Technical Reference for more information.PERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editorRENDERAS="SECT2"Modifying the IDXID="w11424"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11425"BOOK="_idx" COLLECTION="nw41" TIDREF="i4428"
FileThe TSA software (the TSASMS.COM file) allows you to specify variables for the following parameters in your NET.CFG file:TYPE="VERT"DISK BUFFERSDRIVESPASSWORDSTACK SIZEPAGENUM=278TSA SERVER NAMEWORKSTATION NAMESee "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS TSA Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for details on how to configure for the TSA software.Configure the parameters for the Novell TSA software by completing the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open your NET.CFG file with an ASCII text editor.For example, to use the Novell DOS 7 System Editor at the command line to edit the NET.CFG file in the NetWare Client directory (the default is C:\NWCLIENT), you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\NWCLIENT\NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Make the necessary configurations for your particular SMS application.See the manufacturer's documentation for information.PERFORMANCE="REQUIRED"Save your changes and exit the NET.CFG file.You can use command line parameters in place of NET.CFG parameters to configure settings for your client workstations. See Chapter 3, "BOOK="ws_d2enu" COLLECTION="nw41"Command Line Parameters Reference," in NetWare Client for DOS and MS Windows Technical Reference for more information.RENDERAS="SECT1"ID="FM48204"Loading the IDXID="w11426"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
TSA SoftwareLoading the TSASMS.COM file for SMS applications requires you to complete the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that your SMS application is set up and running.IDREF="FM30205"See "Installing an SMS Application" on page 274 for more information.
PAGENUM=279 ID="BP264"PERFORMANCE="REQUIRED"Ensure that the TSASMS.COM and NetWare Client software files are installed on each client workstation that you want managed by your SMS application.IDREF="FM55847"See "Installing the TSASMS.COM and NetWare Client Files" on page 275 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM93792"See "Modifying the DOS System and NetWare Client Configuration Files" on page 276 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The STARTNET.BAT file loads the TSASMS.COM and NetWare Client software files.RENDERAS="SECT1"ID="FM97749"Unloading the IDXID="w11427"BOOK="_idx" COLLECTION="nw41" TIDREF="i4427"
TSA 
SoftwareUnload the TSASMS.COM file.FORMAT="LINESPECIFIC"MOREINFO="NONE"TSASMS /U MOREINFO="NONE"<Enter>RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for TSACOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS TSA Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference LABEL="18"PAGENUM=281 ID="BP265"ID="FM54735"Configuring Client Workstations for Desktop SNMP ServicesRENDERAS="SECT1"OverviewThis chapter explains how to enable 
desktop SNMP services on your client workstation and how to modify the NET.CFG file to implement additional SNMP options. This section is primarily for network supervisors who administer SNMP-based network management systems.The following topics are covered in this chapter.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM61789"Installing an SNMP Management System Console  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM61789"282COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM85061"Installing the Desktop SNMP Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85061"282COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM50462"Modifying DOS System and NetWare Client Configuration Files COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50462"285COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM98422"Loading the Desktop SNMP Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98422"291COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM39396"Unloading the Desktop SNMP Software COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39396"292COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM79636"Configuring Client Workstations for Better Performance COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM79636"292RENDERAS="SECT1"IntroductionIDXID="w11428"BOOK="_idx" COLLECTION="nw41" TIDREF="i4159"IDXID="w11429"BOOK="_idx" COLLECTION="nw41" TIDREF="i4190"
Simple Network Management Protocol (SNMP) is an industry-standard protocol that specifies a format for collecting network management data.With the Novell® IDXID="w11430"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
Desktop SNMP services, NetWare 
client workstations are able to send status information to an 
SNMP management program running on an IPXTM or TCP/IP network.PAGENUM=282 ID="BP266"Desktop SNMP services can be managed from the Novell IDXID="w11431"BOOK="_idx" COLLECTION="nw41" TIDREF="i2763"
NetWare 
Management SystemTM (NMS) software, from other industry-standard SNMP management consoles, or from other third-party management systems.NetWare Client support for IDXID="w11432"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
Desktop SNMP on NetWare client workstations must be 
set up on each client workstation that you want managed by an SNMP-based management system.The complete setup for a Desktop SNMP client workstation requires you to complete the following tasks:MARK=BULLETIDREF="FM61789"Installing an SNMP Management System Console IDREF="FM85061"Installing the Desktop SNMP Software IDREF="FM50462"Modifying DOS System and NetWare Client Configuration Files IDREF="FM80147"Configuring the HRMIB.INI File RENDERAS="SECT1"ID="FM61789"Installing an SNMP Management System ConsoleIDXID="w11433"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
The Desktop SNMP services provided with the NetWare ClientTM for DOS and MS Windows supports the Novell IDXID="w11434"BOOK="_idx" COLLECTION="nw41" TIDREF="i2763"
NetWare 
Management 
System software (NMS), other industry-standard SNMP management consoles, or other third-party management systems.See the documentation provided with these managements systems for information on installation and setup.RENDERAS="SECT1"ID="FM85061"Installing the Desktop SNMP SoftwareThe 
Desktop SNMP software includes a collection of files that support the Simple Network Management Protocol (SNMP) using the NetWare Virtual Loadable ModuleTM (VLM) technology. Support for the Internet Packet ExchangeTM (IPX) transport and User Datagram Protocol (UDP) transports is also provided.MARK=BULLETDesktop SNMP and Management Information Base (MIB) Support FilesPAGENUM=283 ID="BP267"The Desktop SNMP VLMTM programs let remote network management systems monitor the IPXTM or UDP/IP protocol stack running on client workstations.Desktop SNMP also allows remote and local SNMP client workstations complete access to the Management Information Base (MIB) for managing workstation resources.Desktop SNMP supports the following three MIB-II groups:MARK=BULLETSystem and SNMP groupsInterfaces groupsTCP/IP groupsThe following files must exist in the NetWare Client directory for each client workstation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FileCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HRMIB.EXECOLNAME=2 ROTATE="0" MOREROWS="0"The Host Resources manager, which collects information about client workstations that are running DOS on the networkCOLNAME=1 ROTATE="0" MOREROWS="0"HRMIB.INICOLNAME=2 ROTATE="0" MOREROWS="0"The configuration file for the HRMIB.EXE fileCOLNAME=1 ROTATE="0" MOREROWS="0"MIB2IF.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The MIB-II interfaces groups supportCOLNAME=1 ROTATE="0" MOREROWS="0"MIB2PROT.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The MIB-II TCP/IP groups supportCOLNAME=1 ROTATE="0" MOREROWS="0"WSASN1.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The ASN.1 translation moduleCOLNAME=1 ROTATE="0" MOREROWS="0"WSDRVPRN.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The print information collection file for gathering information about print mappings and captured printersCOLNAME=1 ROTATE="0" MOREROWS="0"WSREG.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The registration moduleCOLNAME=1 ROTATE="0" MOREROWS="0"WSSNMP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The Desktop SNMP module, which includes MIB-II System and SNMP groups supportCOLNAME=1 ROTATE="0" MOREROWS="0"WSTRAP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"The trap moduleThese files are automatically copied to the NetWare directory when you run the NetWare Client installation program.PAGENUM=284 ID="BP268"IDREF="FM93380"See Chapter 5, "Installing or Upgrading NetWare Client Software," on page 89 for more information.The files with a .VLM extension are loaded by the VLM manager (the VLM.EXE file) using the VLM= parameter in the NET.CFG file. The files with an .EXE extension are loaded from the command line or from a DOS batch file.Transport ProvidersThe Novell Desktop SNMP requires one of the following two files in the NetWare Client directory to manage your client workstation address for the IPX transport protocol or for the UDP/IP transport protocol:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FileCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"STPUDP.COMCOLNAME=2 ROTATE="0" MOREROWS="0"The transport provider module for the UDP/IP protocolCOLNAME=1 ROTATE="0" MOREROWS="0"STPIPX.COMCOLNAME=2 ROTATE="0" MOREROWS="0"The transport provider module for the IPX protocolThese files are loaded from the command line or from a DOS batch file. Both files can be loaded into memory at the same time.RENDERAS="SECT2"Copying the Necessary Files to the NetWare Client Directory ManuallyIf you choose to not run the NetWare Client installation program, you must manually copy the appropriate files to the NetWare Client directory.To manually copy the files from the NetWare Client for DOS and MS Windows diskettes, complete the following procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM75252"Expand and copy the following files from the CLASS=DISKNetWare Client for DOS and MS Windows Disk 2 to the NetWare Client directory (the default is C:\NWCLIENT).COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"HRMIB.EXECOLNAME=2 ROTATE="0" MOREROWS="0"HRMIB.INICOLNAME=1 ROTATE="0" MOREROWS="0"MIB2IF.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"MIB2PROT.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"STPIPX.COMCOLNAME=2 ROTATE="0" MOREROWS="0"STPUDP.COMCOLNAME=1 ROTATE="0" MOREROWS="0"WSASN1.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"WSDRVPRN.MIBCOLNAME=1 ROTATE="0" MOREROWS="0"WSDRVPRN.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"WSREG.VLMCOLNAME=1 ROTATE="0" MOREROWS="0"WSSNMP.VLMCOLNAME=2 ROTATE="0" MOREROWS="0"WSTRAP.VLMPAGENUM=285 ID="BP269"To expand a file, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK source_drive:path\filename destination_drive:path\filename MOREINFO="NONE"<Enter>For example, to expand the WSSNMP.VLM file, you could type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWUNPACK A:WSSNMP.VL_ C:\NWCLIENT\WSSNMP.VLM MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Repeat 
IDREF="FM75252"Step 1 until all the Desktop SNMP and NetWare Client files exist in the NetWare Client directory.RENDERAS="SECT1"ID="FM50462"Modifying DOS System and NetWare Client Configuration FilesModifying the DOS system and NetWare Client configuration files requires you to edit the CONFIG.SYS, STARTNET.BAT, and NET.CFG files with an ASCII text editor.RENDERAS="SECT2"Modifying the IDXID="w11435"BOOK="_idx" COLLECTION="nw41" TIDREF="i770"
CONFIG.SYS IDXID="w11436"BOOK="_idx" COLLECTION="nw41" TIDREF="i1005"
FileModify the CONFIG.SYS file with an ASCII text editor to set the LASTDRIVE variable to Z for the NetWare DOS RequesterTM software.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED" Open the CONFIG.SYS file in an ASCII text editor. For example, to use the Novell DOSTM 7 System Editor at the command line to edit the CONFIG.SYS file in the root directory, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EDIT C:\CONFIG.SYS MOREINFO="NONE"<Enter>
PAGENUM=286 ID="BP270"PERFORMANCE="REQUIRED"Set the LASTDRIVE variable to 
Z by adding the following line to the file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LASTDRIVE = ZPERFORMANCE="REQUIRED"Save your changes and exit the ASCII text editor.RENDERAS="SECT2"ID="FM22604"Modifying the IDXID="w11437"BOOK="_idx" COLLECTION="nw41" TIDREF="i4262"
STARTNET.BAT IDXID="w11438"BOOK="_idx" COLLECTION="nw41" TIDREF="i1005"
FileThe following modifications to the STARTNET.BAT file are required for each client workstation that you want to load the Desktop SNMP software on.MARK=BULLETModify the STARTNET.BAT file to load either one or both of the STPIPX.COM and STPUDP.COM files.Modify the STARTNET.BAT file to load the HRMIB.EXE file.You must have either the IPX or UDP/IP protocol installed on your system to support the transport providers. You can use both types of transport on a single client workstation.By default, Desktop SNMP services are not enabled when you install the NetWare Client software. To enable Desktop SNMP services, complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Modify the C:\NWCLIENT\STARTNET.BAT file to load the Desktop SNMP transport files.Add the following commands in the STARTNET.BAT file 
after the line that loads the VLM.EXE file:
MARK=BULLETIf you are using IPX transport, addFORMAT="LINESPECIFIC"MOREINFO="NONE"stpipxIf you are using UDP/IP transport, addFORMAT="LINESPECIFIC"MOREINFO="NONE"stpudpYou can add both commands if you use  both IPX and UDP/IP transport. PAGENUM=287 ID="BP271"PERFORMANCE="REQUIRED"Modify the C:\NWCLIENT\STARTNET.BAT file to load the MIB file.Add the following command  in the STARTNET.BAT file 
after the line that loads the VLM.EXE file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"hrmib.exePERFORMANCE="REQUIRED"Ensure that the HRMIB.INI file exists  in the same directory as the HRMIB.EXE file does.If you are running LAN Workplace, make sure you do not load the SNMP.EXE file provided with the LAN Workplace package.  The installation program for LAN Workplace creates a file called LANWP.BAT that loads the LAN Workplace software. Check this file for a line reading MOREINFO="NONE"SNMP. It would be listed directly following the line MOREINFO="NONE"TCPIP.  If the MOREINFO="NONE"SNMP line is present, delete it or comment it out.PERFORMANCE="REQUIRED"Add the following DOS SET command in the STARTNET.BAT file to set the correct time zone for your area:
FORMAT="LINESPECIFIC"MOREINFO="NONE"set tz = time_zoneRefer to your DOS manual for the exact syntax for your particular time zone.If the time zone is not set in your workstation's environment, traps for SNMP might report an incorrect time.PERFORMANCE="REQUIRED"Save and exit.RENDERAS="SECT2"Modifying the IDXID="w11439"BOOK="_idx" COLLECTION="nw41" TIDREF="i2905"
NET.CFG IDXID="w11440"BOOK="_idx" COLLECTION="nw41" TIDREF="i1005"
FileThe following modifications to the NET.CFG file are required for each client workstation that you want to load the Desktop SNMP software on.MARK=BULLETAdd the necessary lines in the NET.CFG file to load and support the Desktop SNMP software.Set the "TRAP TARGET" address of the NetWare Services Management (NSM) consoles or other SNMP-based managers.PAGENUM=288 ID="BP272"IDREF="FM79095"See "Sample NET.CFG File for Desktop SNMP Services " on page 289 for an example.By default, Desktop SNMP services are not enabled when you install the NetWare Client software. To enable Desktop SNMP services, complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that the Desktop SNMP files are copied to the NetWare Client directory (the default is C:\NWCLIENT).PERFORMANCE="REQUIRED"Modify the NET.CFG file to load the Desktop SNMP .VLM files. To load the Desktop SNMP .VLM file suite, modify the NET.CFG file on your client workstation in either of the following two ways:
MARK=BULLETTo load the Desktop SNMP and the NetWare DOS Requester software, add the following lines to the NET.CFG file in the order given:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm = wssnmp.vlm
   vlm = wstrap.vlm
   vlm = wsreg.vlm
   vlm = wsasn1.vlm
   vlm = mib2if.vlm
   vlm = wsdrvprn.vlm
   vlm = mib2prot.vlmTo load only Desktop SNMP, without the NetWare DOS Requester modules, add the following lines to the NET.CFG file in the order given:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   use defaults = off
   vlm = wssnmp.vlm
   vlm = wstrap.vlm
   vlm = wsreg.vlm
   vlm = wsasn1.vlm
   vlm = mib2if.vlm
   vlm = wsdrvprn.vlm
   vlm = mib2prot.vlm
PAGENUM=289 ID="BP273"See the following sections in Chapter 2, "
BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option," in 
NetWare Client for DOS and MS Windows Technical Reference for details on how to configure for Desktop SNMP:
TYPE="VERT""BOOK="ws_d2enu" COLLECTION="nw41"Asynchronous timeout""
BOOK="ws_d2enu" COLLECTION="nw41"Community names""
BOOK="ws_d2enu" COLLECTION="nw41"MIB-II support""
BOOK="ws_d2enu" COLLECTION="nw41"Transport providers"After you have completed the initial configuration of the Desktop SNMP agent, you can further modify the Desktop SNMP options in the NET.CFG file to meet your specific network requirements.RENDERAS="SECT2"ID="FM79095"Sample IDXID="w11441"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
NET.CFG File for Desktop SNMP Services Following is a sample of the NET.CFG for Desktop SNMP services:FORMAT="LINESPECIFIC"MOREINFO="NONE"link driver ne2000
   port 300
   int 3
   frame ethernet_802.2
   mem d0000FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm = wssnmp.vlm
   vlm = wstrap.vlm
   vlm = wsreg.vlm
   vlm = wsasn1.vlm
   vlm = mib2if.vlm
   vlm = wsdrvprn.vlm
   vlm = mib2prot.vlmFORMAT="LINESPECIFIC"MOREINFO="NONE"desktop snmp
   enable monitor community = any
   monitor community = "public"
   enable control community = specific
   control community = "public"
   enable trap community = specific
   trap community = "public"
   sysname = "Suzanne Morley x893"
PAGENUM=290 ID="BP274"   syslocation = "Building 2"
   syscontact = "suzanne@acompany.com"
   snmpenableauthentraps = onFORMAT="LINESPECIFIC"MOREINFO="NONE"transport provider ipx
   trap target = ab123456:0123456789ab
   trap target = cd654321:ba9876543210FORMAT="LINESPECIFIC"MOREINFO="NONE"transport provider udp
   trap target = 999.88.77.66
   trap target = 888.11.22.33RENDERAS="SECT2"ID="FM80147"Configuring the 
HRMIB.INI FileThe IDXID="w11442"BOOK="_idx" COLLECTION="nw41" TIDREF="i1694"
Host Resources MIB does not return information about devices attached to the host workstation, such as printers, modems, and tape drives.If the network management console is to view details of such devices, you must list them in the HRMIB.INI file. Use a ASCII text editor to enter a short description of each device.The IDXID="w11443"BOOK="_idx" COLLECTION="nw41" TIDREF="i1732"
HRMIB.INI file is located in the NetWare Client directory (the default is C:\NWCLIENT).RENDERAS="SECT2"Sample IDXID="w11444"BOOK="_idx" COLLECTION="nw41" TIDREF="i1732"
Configuration File (HRMIB.INI) for the HRMIB.EXE FileThe following is a sample of the HRMIB.INI configuration file for HRMIB.EXE:FORMAT="LINESPECIFIC"MOREINFO="NONE"# List of all printers connected to host
[printers]
HP LaserJet IIIp on LPT1:
NEC P20 on LPT2:
# List of all modems connected to host
[modems]
Hayes Optima 144 on COM1:
# List of all tape drives connected to host
[tapes]
PAGENUM=291 ID="BP275"Colorado DJ10
HP 35480A SCSI DAT (4-8 GB)
# other devices obtained via DOS APIsRENDERAS="SECT1"ID="FM98422"Loading the IDXID="w11445"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
Desktop SNMP SoftwareLoading the Desktop SNMP software requires you to complete the following procedure.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Ensure that the SNMP management system is set up and running.IDREF="FM61789"See "Installing an SNMP Management System Console" on page 282 for more information.PERFORMANCE="REQUIRED" Ensure that the Desktop SNMP software is installed on each client workstation that you want managed from the management console.IDREF="FM85061"See "Installing the Desktop SNMP Software" on page 282 for more information.PERFORMANCE="REQUIRED"Ensure that all necessary modifications are made to the client workstation configuration files.IDREF="FM50462"See "Modifying DOS System and NetWare Client Configuration Files" on page 285 for more information.PERFORMANCE="REQUIRED"Ensure that the HRMIB.INI is configured properly for each client workstation to include the necessary devices you want managed.IDREF="FM80147"See "Configuring the HRMIB.INI File" on page 290 for more information.PERFORMANCE="REQUIRED"Reboot each client workstation.The VLM manager loads the Desktop SNMP .VLM files along with any other .VLM files your client workstations are configured to load.
PAGENUM=292 ID="BP276"RENDERAS="SECT1"ID="FM39396"Unloading the IDXID="w11446"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
Desktop 
SNMP SoftwarePERFORMANCE="REQUIRED"(Conditional) If UDP/IP support has been loaded, unload STPUDP by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"STPUDP /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Conditional) If IPX support has been loaded, unload STPIPX by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"STPIPX /U MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Unload all VLM files by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"VLM /U MOREINFO="NONE"<Enter>The VLM /U command unloads all VLM files, not just the Desktop SNMP files.Always unload the modules in reverse order from the order in which you loaded them. Unloading the modules in any order other than reverse order is impossible.RENDERAS="SECT1"ID="FM79636"Configuring IDXID="w11447"BOOK="_idx" COLLECTION="nw41" TIDREF="i1004"
Client Workstations for Better PerformanceTo improve performance of the 
Desktop SNMP software, you can configure your client workstation to load one or more Desktop SNMP .VLM files in conventional memory.To load all .VLM files in conventional memory, use the VLM /MC switch when running the VLM manager. See "BOOK="ws_d2enu" COLLECTION="nw41"NetWare DOS Requester Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference for more information.To load a Desktop SNMP .VLM files in conventional memory, add lines with the following syntax to the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm = vlm_name.vlm
   load low vlm_name = on
PAGENUM=293 ID="BP277"For example, to load Desktop SNMP while loading the WSASN1.VLM and WSREG.VLM files in conventional memory, add the following lines to the NET.CFG file:FORMAT="LINESPECIFIC"MOREINFO="NONE"netware dos requester
   vlm = wssnmp.vlm
   vlm = wstrap.vlm
   vlm = wsreg.vlm
   vlm = wsasn1.vlm
   vlm = wsdrvprn.vlm
   load low wsreg = on
   load low wsasn1 = onRENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Setting up and modifying your NET.CFG file for SNMPCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="ws_d2enu" COLLECTION="nw41"Desktop SNMP Option" in Chapter 2 of NetWare Client for DOS and MS Windows Technical Reference LABEL=""PAGENUM=295 ID="BP278"AppendixesRENDERAS="SECT1"OverviewThe NetWare® ClientTM installation program provides a complete installation or upgrade of the NetWare Client software for each DOS and MS Windows client workstation on your network.If you are installing the NetWare Client software on a new workstation, running the installation program helps to ensure that the workstation is well prepared for connecting to the network or server. If you are updating NetWare Client files only, you can use the WSUPDATE utility to automate and centralize the process for all client workstations running DOS and MS Windows on your network.If you are upgrading your client workstations, the WSUGRD utility helps to upgrade dedicated IPXTM drivers to ODITM drivers before running the installation program. Upgrading these drivers enables the installation to auto-detect software settings for the client workstation hardware and the network frame type. This utility is available in NetWare 4TM software only.RENDERAS="SECT1"ContentsThis section is divided into two chapters, with the following information discussed on the indicated pages:COLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="12*"COLNAME=3 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"PurposeCOLNAME=2 ROTATE="0" MOREROWS="0"ChapterCOLNAME=3 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to use the WSUPDATE utility for updating client workstations with the most current softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM89689"Appendix  A, "Using the WSUPDATE Utility" COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM89689"297COLNAME=1 ROTATE="0" MOREROWS="0"To learn how to use the WSUPGRD utility for upgrading client workstations with the most current ODI-based NetWare Client softwareCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28103"Appendix  B, "Using the WSUPGRD Utility"  COLNAME=3 ROTATE="0" MOREROWS="0"IDREF="FM28103"307LABEL="A"PAGENUM=297 ID="BP279"ID="FM89689"Using the WSUPDATE UtilityRENDERAS="SECT1"OverviewThis appendix contains information about using the WSUPDATE utility for updating client files automatically.The following topics are covered in this appendix.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM67987"Updating Files from the Command Line  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67987"298COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55477"Updating Files from a Login Script or Profile  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55477"299RENDERAS="SECT1"IntroductionThe WSUPDATE utility allows you to copy updates of client files automatically. Use WSUPDATE toMARK=BULLETCopy new revisions of filesReinstall NetWare Client filesCopy updates of your own filesThis utility is not recommended for first-time installation of NetWare® ClientTM files. WSUPDATE can update only files that exist on the workstation. Use the client installation program for first-time installations.  WSUPDATE also cannot be used for updating RPL client workstations. RPL workstations must be updated through the DOSGEN utility. See "BOOK="utlrfenu" COLLECTION="nw41"DOSGEN" in NetWare 4 Utilities Reference.PAGENUM=298 ID="BP280"RENDERAS="SECT1"Using WSUPDATE to Update Files on Client WorkstationsThe IDXID="w11448"BOOK="_idx" COLLECTION="nw41" TIDREF="i4858"
WSUPDATE utility allows you to copy updates of files to client workstations automatically, either at the command line or from a login script or profile.RENDERAS="SECT2"ID="FM67987"Updating Files from the IDXID="w11449"BOOK="_idx" COLLECTION="nw41" TIDREF="i4860"
Command LineRENDERAS="SECT3"PrerequisitesIDXID="w11450"BOOK="_idx" COLLECTION="nw41" TIDREF="i4858"
Before you load WSUPDATE, ensure thatMARK=CHECKBOXThe files that are copied to the workstation reside in the same directory as the WSUPDATE utility (the default is SYS:PUBLIC)Each workstation you want to update files on has a drive mapped to SYS:PUBLICRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Copy the new files to the SYS:PUBLIC directory.PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G: to PUBLIC, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load WSUPDATE and specify the file and path you want updated.For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPDATE /F=C:\NE2000.COM MOREINFO="NONE"<Enter>The /F option lets you specify the file location.
PAGENUM=299 ID="BP281"RENDERAS="SECT2"ID="FM55477"Updating Files from a IDXID="w11451"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login 
Script or ProfileIDXID="w11452"BOOK="_idx" COLLECTION="nw41" TIDREF="i4860"
You can add the WSUPDATE command to a system 
login IDXID="w11453"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
script or container profile for updating files on client workstations. Use SYSCON for NetWare 2 and NetWare 3TM workstations. Use the NetWare Administrator graphical utility or the NETADMIN text utility for NetWare 4TM workstations. All three procedures are documented in this section. RENDERAS="SECT3"ID="FM58702"Using SYSCONIDXID="w11454"BOOK="_idx" COLLECTION="nw41" TIDREF="i4860"
This utility is used only with NetWare 2 and 3 networks. For NetWare 4 networks, use the NWADMIN or NetWare Administrator utility to edit a specific container profile. IDREF="FM79564"See "Using NetWare Administrator" on page 300 or IDREF="FM87584""Using NETADMIN" on page 303 for information.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of Novell DOSTM 7 or later, DR DOS® 5 or later, MS-DOS* 3 or later, or PC-DOS* 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Log in to a server as SUPERVISOR by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SUPERVISOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enter a password (if required).PERFORMANCE="REQUIRED"Load SYSCON by typing 
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYSCON MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Available Topics" menu, choose "Supervisor Options."PERFORMANCE="REQUIRED"Choose "System Login Script." 
PAGENUM=300 ID="BP282"A window appears that allows you to edit or create a login script.PERFORMANCE="REQUIRED"ID="FM22118"In the login script, map a drive to the network file you want copied to the client workstations.For example, if you want to copy the NE2000.COM file from the \DRIVERS directory to drive J: on the workstations, add a drive mapping similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP J:=VOL2:DRIVERS\PERFORMANCE="REQUIRED"Insert the WSUPDATE command after the drive mapping into the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: filenameFor example, if you mapped drive J: as shown in 
IDREF="FM22118"Step 6, add the following command after the drive mapping:
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: NE2000.COMThis command searches all local drives of the client workstations and replaces the NE2000.COM file with its newer version on drive J:.It renames any old NE2000.COM file on the local drives to NE2000.OLD.PERFORMANCE="REQUIRED"To exit the system login script, press 
MOREINFO="NONE"<Esc>. PERFORMANCE="REQUIRED"Confirm and save changes you made in the login script.RENDERAS="SECT3"ID="FM79564"Using IDXID="w11455"BOOK="_idx" COLLECTION="nw41" TIDREF="i4860"
NetWare AdministratorThis utility is used only with NetWare 4 networks. For NetWare 2 and 3 networks, use the SYSCON utility to edit the system login script. IDREF="FM58702"See "Using SYSCON" on page 299 for information.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of MS Windows 3.1 or later and Novell DOS 7 or later, DR DOS 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a Profile container objectPAGENUM=301 ID="BP283"A search drive mapped to SYS:PUBLIC.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load the NetWare Client software and then start MS Windows.PERFORMANCE="REQUIRED"Load the NetWare User Tools by choosing the "NetWare User Tools" icon from the NetWare group.The "NetWare User Tools" main screen appears.PERFORMANCE="REQUIRED"From the menu bar, choose the "NetWare Connections" icon.The "NetWare Connections" window displays available resources.PERFORMANCE="REQUIRED"From the "Resources" list, choose the resource that you want to log in to.PERFORMANCE="REQUIRED"Choose "Login."The "Log In to NetWare" dialog box appears.PERFORMANCE="REQUIRED"Enter the name "ADMIN" or a username with ADMIN equivalency into the "User Name" field.PERFORMANCE="REQUIRED"Enter a password (if needed).PERFORMANCE="REQUIRED"Exit the NetWare User Tools.PERFORMANCE="REQUIRED"Load NetWare Administrator by choosing the "NWADMIN" icon from the NetWare group.The "NetWare Administrator" main screen appears.PERFORMANCE="REQUIRED"From the browser, select the object whose container profile you want to edit.
MARK=BULLETTo modify the login script for a container, select the "Organizational Unit" icon.To modify the login script for a particular User object, select the "User" icon.A login script can be a property of a container, Profile, or User object.
PAGENUM=302 ID="BP284"You might have to browse through the Directory tree to get to the object you want. For information about moving around in the browser and selecting objects, choose "Help" from the menu bar at the top of the "NetWare Administrator" screen.PERFORMANCE="REQUIRED"From the NetWare Administrator menu bar, choose "Object."PERFORMANCE="REQUIRED"Choose "Details."PERFORMANCE="REQUIRED"Choose the "Login Script" page button.PERFORMANCE="REQUIRED"In the login script, map a drive to the network file that you want copied to the client workstations.For example, if you want to copy the NE2000.COM file from the \DRIVERS directory to drive J: on the workstations, add a drive mapping similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP J:=VOL2:DRIVERS\PERFORMANCE="REQUIRED"Insert the WSUPDATE command after the drive mapping in the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: filenameFor example, if you mapped drive J: as shown in Step 15, add the following command after the drive mapping:
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: NE2000.COMThis command searches all local drives of the client workstations and replaces the NE2000.COM file with its newer version on drive J:.It renames any old NE2000.COM file on the local drives to NE2000.OLD.PERFORMANCE="REQUIRED"Choose "OK" and then save your changes.The "NetWare Administrator" main screen appears.PERFORMANCE="REQUIRED"Log in all of the client workstations that you have modified the login scripts for.If the workstations are already logged in, log them in to the network again.This runs the WSUPDATE program and updates the files on all those client workstations.
PAGENUM=303 ID="BP285"RENDERAS="SECT3"ID="FM87584"Using IDXID="w11456"BOOK="_idx" COLLECTION="nw41" TIDREF="i4860"
NETADMINThis utility is used only with NetWare 4 networks. For NetWare 2 and NetWare 3 networks, use the SYSCON utility to edit your login script. IDREF="FM58702"See "Using SYSCON" on page 299 for information.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of Novell DOS 7 or later, DR DOS 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Load the NetWare Client software.PERFORMANCE="REQUIRED"Log in to the network with the name "ADMIN" or a username with ADMIN equivalency.PERFORMANCE="REQUIRED"Enter a password (if required).PERFORMANCE="REQUIRED"Load NETADMIN by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Options" menu, choose "Manage Objects."PERFORMANCE="REQUIRED"Select the object whose login script you want to edit.
MARK=BULLETIf the object you want appears on the list, select it and press MOREINFO="NONE"<F10>.If the object is not on the list, browse the Directory tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.A login script can be a property of a container, Profile, or User object.PERFORMANCE="REQUIRED"Choose "View or Edit Object Properties."
PAGENUM=304 ID="BP286"PERFORMANCE="REQUIRED"Choose "Login Script."PERFORMANCE="REQUIRED"ID="FM48756"In the login script, map a drive to the file on the network you want copied to the client workstations.For example, if you want to copy the NE2000.COM file from the \DRIVERS directory to drive J: on the workstations, add a drive mapping similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP J:=VOL2:DRIVERS\PERFORMANCE="REQUIRED"Insert the WSUPDATE command after the drive mapping in the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: filenameFor example, if you mapped drive J: as shown in 
IDREF="FM48756"Step 9, add the following command after the drive mapping:
FORMAT="LINESPECIFIC"MOREINFO="NONE"#WSUPDATE J: NE2000.COMThis command searches all local drives of the client workstations and replaces the NE2000.COM file with its newer version on drive J:.It renames any old NE2000.COM file on the local drives to NE2000.OLD.PERFORMANCE="REQUIRED"To save the login script, press
MOREINFO="NONE" <F10>.PERFORMANCE="REQUIRED"To exit, press
MOREINFO="NONE" <Esc>.PERFORMANCE="REQUIRED"Log in all of the client workstations that you have modified the login scripts for.If the workstations are already logged in, log them in to the network again.This runs the WSUPDATE program and updates the files on all those client workstations.
PAGENUM=305 ID="BP287"RENDERAS="SECT1"Additional InformationRENDERAS="SECT2"For NetWare 2 and NetWare 3COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utilref" COLLECTION="nw312"SYSCON" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Mapping network drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utilref" COLLECTION="nw312"MAP" in Utilities ReferenceRENDERAS="SECT2"For NetWare 4COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"Mapping network drivesCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using WSUPDATECOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"WSUPDATE" in Utilities ReferenceLABEL="B"PAGENUM=307 ID="BP288"ID="FM28103"Using the WSUPGRD UtilityRENDERAS="SECT1"OverviewThis appendix contains information about using the 
WSUPGRD utility for upgrading dedicated IPXTM LAN drivers to ODITM LAN drivers. This utility is available in NetWare® 4TM software only.The following topics are covered in this appendix.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM31701"Upgrading IPX LAN Drivers from the Command LineCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM31701"310COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM72789"Upgrading IPX LAN Drivers from a Login Script or ProfileCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72789"310RENDERAS="SECT1"IntroductionIDXID="w11457"BOOK="_idx" COLLECTION="nw41" TIDREF="i4861"
The WSUPGRD utility 
upgrades the IDXID="w11458"BOOK="_idx" COLLECTION="nw41" TIDREF="i1938"
IPX LAN drivers on your client workstation to the corresponding IDXID="w11459"BOOK="_idx" COLLECTION="nw41" TIDREF="i3059"
ODI LAN driver.If client workstations in your network are running one of the NetWare ClientTM shells (NETx), they are running an IPX LAN driver or a corresponding ODI LAN driver.This utility is recommended for large installations with similar hardware and software configurations. If your network has a variety of network boards and LAN driver types, you need to manually upgrade each client workstation.  WSUPGRD cannot be used for upgrading remote boot workstations.The current NetWare Client installation program provides you with a Novell®PAGENUM=308 ID="BP289" ODI LAN driver for network boards. However, the installation program cannot detect board settings from an IPX LAN driver. Therefore, you must know the type of network board and the hardware settings for each client workstation on the network. The WSUPGRD utility was designed to automate the upgrade process from IPX to ODI LAN drivers and make the installation of the NetWare Client software easier by providing auto-detection of the LAN driver settings.If you are running an IPX LAN driver on any client workstations, you should upgrade the LAN drivers on those client workstations to ODI before using the NetWare Client installation program.The NetWare Client installation program automatically detects if an ODI LAN driver is loaded on the client workstations and sets the driver settings for you. This will make upgrading client workstations from a previous version of NetWare with the installation program automatic.RENDERAS="SECT2"PrerequisitesIDXID="w11460"BOOK="_idx" COLLECTION="nw41" TIDREF="i4861"
A typical upgrade requires the following files in SYS:PUBLIC:MARK=CHECKBOXWSUPGRD.EXELSL.COM IPXODI.COMAppropriate ODI LAN drivers (for example, NE2000.COM)Auxiliary filesThe auxiliary files are optional but can make upgrading a complex network easier.MARK=BULLETIDXID="w11461"BOOK="_idx" COLLECTION="nw41" TIDREF="i1488"IDXID="w11462"BOOK="_idx" COLLECTION="nw41" TIDREF="i1239"PAGENUM=309 ID="BP290"DRVRXLAT.TXT  This file is in SYS:PUBLIC. It contains one line for each ODI LAN driver type in use on the network.  Each line has the hexadecimal hardware identification of the IPX LAN driver, the path to the files, and the name of the corresponding ODI LAN driver.  If no DRVRXLAT.TXT file exists or if no line with the correct hardware identification is found in the DRVRXLAT.TXT file, then WSUPGRD looks in the PUBLIC directory for an ODI LAN driver with the same name as the existing IPX LAN driver.  If it fails to find an ODI driver, no upgrade is performed.driver_name.LDC  The .LDC files are in the same directory as the ODI LAN drivers of the same name (driver_name.COM).  These files contain lines that are to be copied to the NET.CFG file in addition to any lines the utility creates normally.RENDERAS="SECT1"ID="FM84650"Using the WSUPGRD /I OptionIDXID="w11463"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
The /I option in WSUPGRD lets you print out the hardware identification for your dedicated IPX LAN driver.The DRVRXLAT.TXT file contains a master configuration table. Check the master configuration table to make sure that your dedicated-IPX LAN driver identification matches a registered driver. The table lists the driver name, the company name, and the hardware identification. If the listing in the table does not match the LAN drivers and network boards used in your client workstations, you should not use this utility.If the dedicated IPX LAN driver is not registered, the identification that the IPX LAN driver uses might be registered for a different type of network board. You cannot use the WSUPGRD /I option with any other WSUPGRD options.RENDERAS="SECT1"Using WSUPGRDE to Upgrade Network Board 
DriversThe WSUPGRD utility upgrades the IPX LAN drivers on the client workstations to the corresponding ODI LAN drivers, either at the IDXID="w11464"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
command line or from a login script.PAGENUM=310 ID="BP291"RENDERAS="SECT2"ID="FM31701"Upgrading IPX LAN Drivers from the IDXID="w11465"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
Command IDXID="w11466"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
LineRENDERAS="SECT3"PrerequisitesIDXID="w11467"BOOK="_idx" COLLECTION="nw41" TIDREF="i4861"
Before you load WSUPGRD, ensure thatMARK=CHECKBOXThe files that are copied to the client workstation reside in the same directory as the WSUPGRD utility (the default is SYS:PUBLIC)Each client workstation you want to upgrade files on has a drive mapped to SYS:PUBLICRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Copy the new files to the SYS:PUBLIC directory.PERFORMANCE="REQUIRED"Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G: to PUBLIC, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"G: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Change to the drive and directory that the client workstation boots from.For example, if the client workstation boots from drive C:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"C: MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load WSUPGRD and specify the type of LAN driver.For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD NE2000 MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM72789"Upgrading IPX LAN Drivers from a IDXID="w11468"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login Script or ProfileIDXID="w11469"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
You can add the IDXID="w11470"BOOK="_idx" COLLECTION="nw41" TIDREF="i957"
WSUPGRD command to a system IDXID="w11471"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
login script or container profile for upgrading LAN drivers. PAGENUM=311 ID="BP292"Use SYSCON for NetWare 2 and NetWare 3 workstations. Use the NetWare Administrator graphical utility or the NETADMIN text utility for NetWare 4 workstations. All three procedures are documented in this section. If this utility is loaded from a system login script, all of the client workstations that log in to this server must have drivers with the same name.  If this is not the case, users have to run WSUPGRD from the DOS command line supplying the path to and the name of the IPX driver on their respective client workstations.RENDERAS="SECT3"ID="FM51655"Using SYSCONIDXID="w11472"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
This utility is used only with NetWare 2 and NetWare 3 networks. For NetWare 4 networks, use the NetWare Administrator or NETADMIN utility to edit your login script. IDREF="FM83241"See "Using NetWare Administrator" on page 312 or IDREF="FM30795""Using NETADMIN" on page 315 for information.RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of Novell DOSTM 7 or later, DR DOS® 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Log in to a server as SUPERVISOR by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SUPERVISOR MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Enter a password (if required).PERFORMANCE="REQUIRED"At the command line, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYSCON MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Available Topics" menu, choose "Supervisor Options."
PAGENUM=312 ID="BP293"PERFORMANCE="REQUIRED"Choose "System Login Script."A window appears that allows you to edit or create a login script.PERFORMANCE="REQUIRED"Insert the WSUPGRD command into the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD odi_lan_driver [option]For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD NE2000 /NThis command upgrades your IPX LAN driver with an NE2000.COM ODI LAN driver without deleting your IPX LAN driver.PERFORMANCE="REQUIRED"To exit the system login script, press 
MOREINFO="NONE"<Esc>. PERFORMANCE="REQUIRED"Confirm and save changes you made in the login script.PERFORMANCE="REQUIRED"Modify any batch files used to load the NetWare Client software for each client workstation.The batch file should contain at least the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL
odi_lan_driver.COM
IPXODI
NETx [if using NetWare 3 or earlier] 
VLM [if using NetWare 4]PERFORMANCE="REQUIRED"Log in all of the client workstations you have modified the login scripts for.If the workstations are already logged in, log them in to the network again.PERFORMANCE="REQUIRED"Run the WSUPGRD program and update the LAN driver.RENDERAS="SECT3"ID="FM83241"Using IDXID="w11473"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
NetWare AdministratorThis utility is used only with NetWare 4 networks. For NetWare 2 and NetWare 3 networks, use the SYSCON utility to edit your login script. IDREF="FM51655"See "Using SYSCON" on page 311 for information.PAGENUM=313 ID="BP294"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of MS Windows 3.1 or later and Novell DOS 7 or later, DR DOS 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load the NetWare Client software and then start MS Windows.PERFORMANCE="REQUIRED"Load the NetWare User Tools by choosing the "NetWare User Tools" icon from the NetWare group.The "NetWare User Tools" main screen appears.PERFORMANCE="REQUIRED"From the menu bar, choose the "NetWare Connections" icon.The "NetWare Connections" window displays available resources.PERFORMANCE="REQUIRED"From the "Resources" list, choose the resource that you want to log in to.PERFORMANCE="REQUIRED"Choose "Login."The "Log In to NetWare" dialog box appears.PERFORMANCE="REQUIRED"Enter the name "ADMIN" or a username with ADMIN equivalency into the "User Name" field.PERFORMANCE="REQUIRED"Enter a password (if required).PERFORMANCE="REQUIRED"Exit the NetWare User Tools.PERFORMANCE="REQUIRED"Load NetWare Administrator by choosing the "NWADMIN" icon from the NetWare group.The "NetWare Administrator" main screen appears.PERFORMANCE="REQUIRED"From the browser, select the object whose login script you want to edit.
PAGENUM=314 ID="BP295"MARK=BULLETTo modify the system login script for a container, select the "Organizational Unit" icon.To modify the login script for a particular User object, select the "User" icon.A login script can be a property of a container, Profile, or User object.You might have to browse through the Directory tree to get to the object you want. For information about moving around in the browser and selecting objects, choose "Help" from the menu bar at the top of the "NetWare Administrator" screen.PERFORMANCE="REQUIRED"From the NetWare Administrator menu bar, choose "Object."PERFORMANCE="REQUIRED"Choose "Details."PERFORMANCE="REQUIRED"Choose the "Login Script" page button.PERFORMANCE="REQUIRED"Insert the WSUPGRD command into the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD odi_driver [option]For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD NE2000 /NThis command upgrades your IPX LAN driver with an NE2000.COM ODI LAN driver without deleting your IPX LAN driver.PERFORMANCE="REQUIRED"Choose "OK."The "NetWare Administrator" main screen appears.PERFORMANCE="REQUIRED"Modify any batch files used to load the NetWare Client software for each client workstation.The batch file should contain at least the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL
network_board_driver.COM
IPXODI
NETx [if using NetWare 3 or earlier]
VLM [if using NetWare 4]
PAGENUM=315 ID="BP296"PERFORMANCE="REQUIRED"Log in all of the client workstations you have modified the login scripts for.If the workstations are already logged in, log they in again to the network.This runs the WSUPGRD program and updates the LAN driver on all those client workstations.RENDERAS="SECT3"ID="FM30795"Using IDXID="w11474"BOOK="_idx" COLLECTION="nw41" TIDREF="i4862"
NETADMINThis tool is used only with NetWare 4 networks. For NetWare 2 and NetWare 3 networks, use the SYSCON utility to edit your login script. IDREF="FM51655"See "Using SYSCON" on page 311 for information.RENDERAS="SECT4"PrerequisitesMARK=CHECKBOXA client workstation logged in to the network, running a copy of Novell DOS 7 or later, DR DOS 5 or later, MS-DOS 3 or later, or PC-DOS 3 or laterRights to modify a system login scriptA search drive mapped to SYS:PUBLICRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Load the NetWare Client software.PERFORMANCE="REQUIRED"Log in to the network with the name ADMIN or a username with ADMIN equivalency.PERFORMANCE="REQUIRED"Enter a password (if required).PERFORMANCE="REQUIRED"Load NETADMIN by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"NETADMIN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the "Options" menu, choose "Manage Objects."PERFORMANCE="REQUIRED"Select the object whose login script you want to edit.
MARK=BULLETIf the object you want appears on the list, select it and press MOREINFO="NONE"<F10>.PAGENUM=316 ID="BP297"If the object is not on the list, browse the Directory tree by selecting objects and pressing MOREINFO="NONE"<Enter> until you see the object you want. Select it and press MOREINFO="NONE"<F10>.A login script can be a property of a container, Profile, or User object.PERFORMANCE="REQUIRED"Choose "View or Edit Object Properties."PERFORMANCE="REQUIRED"Choose "Login Script."PERFORMANCE="REQUIRED"Insert the WSUPGRD command into the login script by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD odi_driver [option]For example, you might type
FORMAT="LINESPECIFIC"MOREINFO="NONE"WSUPGRD NE2000 /NPERFORMANCE="REQUIRED"To save the login script, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"To exit, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"Modify any batch files used to load the NetWare Client software for each workstation.The batch file should contain at least the following lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL
network_board_driver.COM
IPXODI
NETx [if using NetWare 3 or earlier]
VLM [if using NetWare 4] PERFORMANCE="REQUIRED"Log in all of the client workstations that you have modified the login scripts for.If the workstations are already logged in, log them in to the network again.This runs the WSUPGRD program and updates the LAN driver on all those client workstations.
PAGENUM=317 ID="BP298"RENDERAS="SECT1"Additional InformationCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Creating login scriptsCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts" in Supervising the NetworkCOLNAME=1 ROTATE="0" MOREROWS="0"Mapping network drivesCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="utlrfenu" COLLECTION="nw41"MAP" in Utilities ReferenceCOLNAME=1 ROTATE="0" MOREROWS="0"Using WSUPGRDCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"WSUPGRD" in Utilities Reference