#EDIR DATA#
NetWare 3.12 Installation and UpgradeDisclaimerNovell®, 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.TrademarksBtrieve, DR DOS, EXOS, LANalyzer, NetWare, OnLan/PC, Novell, and the N design are registered trademarks of Novell, Inc.Advanced NetWare, Boot Support Module, BSM, ElectroText, Hardware Specific Module, Hot Fix, HSM, Internetwork Packet Exchange, LAN Service, Link Support Layer, LSL, Media Support Module, MSM, Multiple Link Interface, MLI, Multiple Link Interface Driver, MLID, Multiple Protocol Interface, MPI, NetWare Access Server, NetWare Access Services, NetWare Core Protocol, NCP, NetWare Directory Services, NDS, NetWare DOS Requester, NDR, NetWare Express, NetWare Loadable Module, NLM, NetWare Management Agent, NetWare MultiProtocol Router, NetWare NFS, NetWare Requester, NetWare RPC, NetWare Runtime, Network Support Encyclopedia, NetWare 3270 LAN Workstation, NetWare 3270 LAN Workstation for DOS, NetWare 3270 LAN Workstation for Windows, NLM, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, Novell Labs, Novell Virtual Terminal, NVT, NTR2000, Open Data-Link Interface, ODI, Packet Burst, RX-Net/2, SFT, Topology Specific Module, TSM, TSA, Transaction Tracking System, TTS, Turbo RX-Net, Virtual Loadable Module, and VLM are trademarks of Novell, Inc.NetWire is a service mark of Novell, Inc.Novell Authorized Reseller is a collective mark of Novell, Inc.3Com and 3+Share are registered trademarks of 3Com Corporation.ARCnet is a registered trademark of Datapoint Corporation.AT&T is a registered trademark of AT&T.Apple, AppleShare, AppleTalk, ImageWriter, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.COMPAQ is a registered trademark of Compaq Computer Corporation.CompuServe is a registered trademark of CompuServe, Inc.DDS is a trademark of Sony Corporation.DEC is a trademark of Digital Equipment Corporation.Epson is a registered trademark of Seiko Epson Corporation.GE Information Services is a trademark of General Electric Company, USA, which is not connected with the General Electric Company p.l.c. of England.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.Hewlett-Packard, Deskjet, HP, Laserjet, PCL, and Vectra are registered trademarks of Hewlett-Packard Company.IBM, AT, Micro Channel, NetView, OS/2, ProPrinter, and PS/2 are registered trademarks of International Business Machines Corporation.IBM Operating System/2 Local Area Network Server (LAN Server), Presentation Manager, SAA, and XT are trademarks of International Business Machines Corporation.Intel is a registered trademark of Intel Corporation.LAN Manager and LAN Manager Server are trademarks of Microsoft Corporation.Lotus is a registered trademark of Lotus Development Corporation.Microsoft and MS-DOS are registered trademarks of Microsoft Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and Microline are registered trademarks of Oki Electric Industry Co., Ltd.Panasonic is a registered trademark of Panasonic Office Automation.Pinwriter, Spinwriter, and NEC are registered trademarks of NEC Corporation.PostScript is a registered trademark of Adobe Systems Incorporated.SDI is a registered trademark of Systems Data, Inc.SQL Server is a trademark of Sybase, Inc.Unicode is a registered trademark of Transoft Ltd.UNIX is a registered trademark of UNIX System Laboratories, Inc., a subsidiary of AT&T.WordPerfect is a registered trademark of WordPerfect Corporation.Xerox Diablo is a registered trademark of Xerox Corporation.Copyright Notices© Copyright 1983-1993 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.Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.Portions of Concepts and Supervising the Network are copyrighted © 1993 Imagery Software, Inc.lbl="0"How to Use this ManualWhich Part of this Manual You Should UseThis manual is divided into three sections:For all networks: Learn NetWare v3.12 features and enhancements by reading IDREF="FM54065""F eatures," beginning on page xvii.For new networks: Learn how to perform a first-time NetWare network installation by reading IDREF="FM95872""Install a New NetWare Server," beginning on page 1.For existing networks: Learn how to upgrade to NetWare v3.12 from NetWare v2.x or v3.x or other network operating systems by reading IDREF="FM29133""Upgrade an Existing File Server," beginning on page 193.Other Technical SupportContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press <F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For instance, for help with the RIGHTS command, type RIGHTS /?.Hardware manuals. 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.Novell ElectroText(tm). The NetWare Communication Services(tm) viewer allows you to read NetWare manuals from your Windows or OS/2® workstation.All NetWare v3.12 manuals except the Quick Access Guide are available on the NetWare v3.12 CD-ROM.NetWare Management System(tm) (NMS(tm)). This product 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.NetWare Application Notesand Research Reports. These documents 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 (800) UPDATE1. From outside the United States or Canada, call (801) 429-5380.Third-party books and periodicals. A number of books on NetWare, including books published by Novell Press(tm), are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWireSMon CompuServe®. A fairly inexpensive way to getup-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers:In the United States or Canada: (800) 524-3388.In the United Kingdom: 0800-289-378.In Germany: 0130-37-32.In other European countries: 44-272-255-111.In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call (614) 457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.NetWare Support Encyclopedia. This encyclopedia gives customers access to regularly-updated information from Novell and other vendors on products and services.In addition, a Professional Volume is available that provides customers with additional information such as patches, fixes, and more.Both versions are distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. (For more information, contact your Novell Authorized Reseller.)Troubleshooting hardware and software. Specialized hardware and software packages, such as Novell's LANalyzer®, are available to help you isolate network problems.NetWare training. Many Novell courses are available to help you learn about NetWare.In addition, you can pursue the title of Certified NetWare EngineerCLM (CNECLM), Enterprise Certified NetWare EngineerCLM (ECNECLM), Certified NetWare AdministratorCLM (CNACLM), or Certified NetWare InstructorCLM (CNICLM) by taking classes and passing tests.For more information on the CNE, ECNE, CNA, and CNI programs, contact Novell's NetWare Technical Institute (NTI) at (512) 794-1795.Customer service. You may want to contact your Novell Authorized Reseller for technical assistance.Most Novell Authorized Resellers have Certified NetWare Engineers on their staffs ready to assist users with their networking problems.User CommentsWe are continually looking for ways to make our products and our manuals as easy to use as possible.You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you and about inaccuracies or information gaps they may contain.Submit your comments either by filling out the "User Comments" form at the end of this manual or by writing to us directly at the following address:Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LBL="0"ID="FM54065"FeaturesHigh PerformanceNetWare v3.12 takes full advantage of 386 and 486 processors, increasing network capacity and performance.NetWare v3.12 supports up to idxid="w3276"book="_idx" docset="nw312" tidref="i996"idxid="w3277"book="_idx" docset="nw312" tidref="i7173"250 concurrent users while providing the fastest performance of any network operating system on the market.Unlike general-purpose operating systems, NetWare v3.12 is designed specifically to provide the performance necessary for network computing.SecurityNetWare's security features make sure you control access to network resources and data. These features includeLogin securityRights securityAttribute securityFile server securityNCP authenticationData ProtectionRead-after-write verification, Hot Fix, disk mirroring, disk duplexing, resource management, and UPS monitoring increase network dependability by safeguarding data against failure in critical parts of the network hardware.idxid="w3278"book="_idx" docset="nw312" tidref="i4468"idxid="w3279"book="_idx" docset="nw312" tidref="i178"idxid="w3280"book="_idx" docset="nw312" tidref="i3720"Network Management and Administration ToolsA NetWare Loadable Module(tm) ( idxid="w3281"book="_idx" docset="nw312" tidref="i4310"NLM(tm)) is a software module that links dynamically to the operating system.NLMs simplify network installation and enable the addition of server-based applications while the server is running.Remote console services enable you to enter any server command from your workstation.The MONITOR utility displays resource usage statistics tracked by the operating system.Network ApplicationsNovell provides third-party developers with Application Programming Interfaces (APIs) and development tools to help them design products to run on a NetWare network.This ensures that you can easily find off-the-shelf applications that meet your needs.Modular DesignWith an open network server platform, you can add services and enhancements and communicate with a variety of file server and workstation types.You can also add customized modules or tools that can be loaded or unloaded from the file server while it is running.idxid="w3282"book="_idx" docset="nw312" tidref="i1833"idxid="w3283"book="_idx" docset="nw312" tidref="i985"idxid="w3284"book="_idx" docset="nw312" tidref="i7493"Support for Multiple EnvironmentsCross Platform Consistency allows DOS, UNIX®, Macintosh®, and OS/2 workstations to connect to the same server and share a consistent set of network resources.Open Data-Link Interface(tm) (ODI(tm)) makes NetWare v3.12 an open server platform upon which a Multiple Link Interface Driver(tm)(MLID(tm)), a unique kind of NLM, is built.These specifications allow multiple protocols such as IPX/SPX, TCP/IP, and AppleTalk® filing protocol to share the same driver and network board.STREAMS allows multiple protocols to exist in a single file server.EnhancementsIDREF="FM51051"Table 1 shows some important changes to NetWare since v2.2.LBL="1" INLINE="F"ID="FM51051"NetWare v3.12 compared to NetWare v2.2WIDTH="168"SpecificationWIDTH="120"NetWare v2.2WIDTH="120"NetWare v3.12WIDTH="168"Hard disks per volumeWIDTH="120"1WIDTH="120"32 (or 16 if mirrored)Volumes per server3264Volumes per hard disk168Directory entries per volume32,0002,097,152Maximum volume size255 MB32 TBMaximum file size255 MB4 GBMaximum addressable disk storage2 GB32 TBMaximum addressable RAM12 MB4 GBMaximum volume name length15 characters15 charactersMaximum directory/file name length14 characters12 characters (DOS format)Name space supportDOS, MacintoshDOS & Windows,  Macintosh, UNIX, FTAM,  OS/2Disk block sizes4 KB4 KB, 8 KB, 16 KB, 32 KB,  64 KBLBL="0"ID="FM95872"Install a New NetWare ServerFirst-Time Installation OverviewWhat you'll do:Prepare your site and equipment. See IDREF="FM54040""Ensure Proper Power and Power Conditions" on page 6.Set up file server hardware. See IDREF="FM37822"Chapter 1, "Prepare Your Site and Equipment," on page 5.Install file server software. See IDREF="FM92799"Chapter 2, "Install the File Server Software," on page 17.Plan your network environment, create the directory structure, install applications, load files, define users, and set up security. See IDREF="FM34304"Chapter 3, "Set up the Network," on page 67.Customize your network operating environment. See IDREF="FM34948"Chapter 4, "Create Login Scripts," on page 135.(Optional) Bring your servers up to peak performance. See IDREF="FM82264"Appendix  A, "Optimizing Network Performance," on page 313.(Optional) Install Novell ElectroText. See IDREF="FM87545""Installing and Using Novell ElectroText" on page 335.Prepare and install workstation equipment. See the followingbook="ws_get" docset="nw312"Workstation Basics and Installation.book="ws_dos" docset="nw312"NetWare Workstation for DOS and Windows.book="ws_os2" docset="nw312"NetWare Workstation for OS/2.Set up your network printing environment. Seebook="print" docset="nw312"Print Server.LBL="1"ID="FM37822"Prepare Your Site and EquipmentIf your network hardware is already installed and meets site and power conditioning requirements, go to IDREF="FM92799"Chapter 2, "Install the File Server Software," on page 17.What You NeedTo prepare your network idxid="w3285"book="_idx" docset="nw312" tidref="i6347"location, you mustFulfill the hardware requirementsEnsure proper power and power conditionsSet up computer hardwareMake working copies of NetWare diskettesidxid="w3286"book="_idx" docset="nw312" tidref="i2640"idxid="w3287"book="_idx" docset="nw312" tidref="i4371"Hardware RequirementsYou need the following hardware for installing a NetWare v3.12 file server.A PC (or PC compatible) with a 386 or 486 (SX or DX) processor.A minimum of 4MB of RAM.A hard disk with sufficient storage for your network. The idxid="w3288"book="_idx" docset="nw312" tidref="i2599"minimum required is 50 MB: 5 MB for a DOS partition plus 45 MB for a NetWare disk partition containing volume SYS:.If you plan on installing idxid="w3289"book="_idx" docset="nw312" tidref="i4676"idxid="w3290"book="_idx" docset="nw312" tidref="i2599"Novell ElectroText (the NetWare v3.12 documentation in electronic form) on the server, add another 30 MB of disk space.One network board. Network cabling (Ethernet, ARCnet®, 10BaseT, Token ring, etc.).(If installing from CD-ROM) A CD-ROM reader.ID="FM54040"idxid="w3291"book="_idx" docset="nw312" tidref="i5148"Ensure Proper Power and Power ConditionsProcedureCheck the operating environment and power requirements for your equipment.Consult the documentation provided with your computer for specific requirements in the following areas:Temperature/humidityMaximum altitudePower sourcePower frequencyPower requirementsPower consumptionHeat dissipationUse dedicated power lines and grounded outlets.Use dedicated power lines for all hardware components on your NetWare network (file servers, workstations, printers, etc.). Connect only network components to these lines.Electrical outlets should be standard 3-wire (NEMA 5-15R) grounded outlets, with the ground wire connected to an earth ground. (If you connect the ground wire to conduit ground, be sure that the conduit ground is an earth ground.)Install idxid="w3292"book="_idx" docset="nw312" tidref="i5130"power conditioning equipment.Because network hardware components are sensitive to power fluctuations, use some kind of power conditioning equipment on all power lines connected to components:Uninterruptible power supplies (UPS). These protect server hardware from power fluctuations with a regulating uninterruptible power supply.In addition to protecting server hardware from damage caused by power surges and voltage spikes, a UPS protects data held in RAM during a power failure.We strongly recommend that you also use UPS protection for network workstations and other peripherals.Other power conditioning devices. If using a UPS is not feasible, try to equip your network hardware with power conditioning devices.Many devices are available that protect equipment from various irregularities, such as electrical noise and voltage spikes.These devices include line-surge suppressors (also called power conditioners and line filters) and ferro-resonant isolation transformers.Connect network hardware through at least one of these devices to protect them from minor power surges such as those resulting from common electrical power fluctuations.These devices offer some protection and are inexpensive, although they have the following disadvantages:They do not protect hardware components from large power surges such as lightning strikes.Data held in RAM is lost if there is a power failure.Network maintenance costs are higher with line-surge suppressors and ferro-resonant isolation transformers than with uninterruptible power supplies. However, network maintenance costs are lower with suppressors and transformers than with no power conditioning devices at all.For more information on power conditioning devices, seeConcepts.Protect network equipment from idxid="w3293"book="_idx" docset="nw312" tidref="i6508"static electricity.Take the following protective measures:Treat carpets with anti-static chemicals (available in spray form from most computer stores).Use protective covers for carpets, such as the anti-static type or conductive covers connected to an earth ground. Don't use plastic or other synthetic carpet protectors near network equipment because such protectors generate large amounts of static electricity.Ground equipment through a one megaohm resistor to bleed off the static slowly and avoid a static discharge from conductive surfaces.Make sure that personnel working on open equipment chassis take precautionary measures, such as wearing grounded wrist straps.ID="FM43321"Set Up Hardware idxid="w3294"book="_idx" docset="nw312" tidref="i4371"idxid="w3295"book="_idx" docset="nw312" tidref="i6310"NetWare v3.12 file servers can operate on many kinds of hardware. To ensure that there are no conflicts, use unique interrupt request idxid="w3296"book="_idx" docset="nw312" tidref="i3030"(IRQ) settings on file server boards.NetWare prompts you to enter your board settings, gives you available alternate settings, and determines if your settings are valid. (If you don't need the prompts, see "Load Disk Drivers" and "Load LAN Drivers" inSystem Administration.)ID="FM58132"Calculate Necessary Server RAM idxid="w3297"book="_idx" docset="nw312" tidref="i5740"idxid="w3298"book="_idx" docset="nw312" tidref="i899"To calculate your file server's total RAM requirements, perform the following steps. (NetWare v3.12 can support up to idxid="w3299"book="_idx" docset="nw312" tidref="i5740"4GB of RAM and up to idxid="w3300"book="_idx" docset="nw312" tidref="i2599"32TB of disk storage space.)ProcedureID="FM43477"Make sure that you have a minimum of 4 MB of RAM for loading the operating system, disk and LAN drivers, and INSTALL.NLM.ID="FM80755"Add 2 MB to install one or more of the following:Additional NetWare products (such as NetWare for Macintosh, NetWare for NFS, etc.).A print server on this server (PSERVER.NLM).Any of the following NetWare loadable modules: CLIB.NLM, STREAMS.NLM, BTRIEVE.NLM. (Many systems need these NLMs.)Multiply the amount of your system's disk space (in megabytes) by 0.008 and add this number to the number arrived at in IDREF="FM43477"Steps 1 and IDREF="FM80755"2.For example, multiplying 200 MB by 0.008 results in 1.6 MB.Add 1 to 4 MB for additional idxid="w3301"book="_idx" docset="nw312" tidref="i875"idxid="w3302"book="_idx" docset="nw312" tidref="i5740"cache buffer RAM to optimize performance.The more RAM you can allot to cache buffers, the better your system's performance will be.If you have an idxid="w3303"book="_idx" docset="nw312" tidref="i5740"EISA file server that contains more than 16 MB of RAM, donot use 8-or 16-bit AT busmastering or idxid="w3304"book="_idx" docset="nw312" tidref="i1634"DMA boards in the server. For more information, contact the manufacturer.If you have a idxid="w3305"book="_idx" docset="nw312" tidref="i5588"386 computer manufactured in 1987, it may not carry out some 32-bit instructions. This could adversely affect the functioning of NetWare.If a problem exists, NetWare displays a message. You may be able to correct the problem by replacing a ROM chip on the board. For more information, see your computer reseller.idxid="w3306"book="_idx" docset="nw312" tidref="i2869"idxid="w3307"book="_idx" docset="nw312" tidref="i1188"idxid="w3308"book="_idx" docset="nw312" tidref="i2640"Install and Configure Your HardwareProcedureRecord the following hardware information on the File Server Worksheet found at the end of this manual.File server: name, make, and model.Memory size.Non-network boards: type and settings (Optional).Network Boards: associated LAN drivers, network number,I/O address, memory address, interrupt, or station address. Some NetWare drivers and default settings are listed in the tables that follow. For more information about settings, see the documentation that came with your network board.LBL="1-1" INLINE="F"idxid="w3309"book="_idx" docset="nw312" tidref="i3032"idxid="w3310"book="_idx" docset="nw312" tidref="i3085"Default LAN driver settings for ISA network boards idxid="w3311"book="_idx" docset="nw312" tidref="i3085"WIDTH="84"LAN driverWIDTH="48"I/O AddressWIDTH="72"Memory AddressWIDTH="48"InterruptWIDTH="84"TRXNETWIDTH="48"2E0WIDTH="72"D000WIDTH="48"2NE10003003NE20003003PCN2 (primary)620CC00 (RAM)2PCN2 (alternate)628CC00 (RAM)2TokenA20D800 (RAM)3C503300C800033C5053005 (DMA)3For microchannel file servers, use the Reference diskette to set the disk coprocessor boards.Defaults for the following idxid="w3312"book="_idx" docset="nw312" tidref="i3895"microchannel network boards are set by the Reference diskette. NetWare may ask for the slot number.TOKENDMANE/2(tm)TOKENNE/2-32(tm)3C523Options for the NE3200(tm) EISA network board are set by the computer's configuration utility. NetWare needs the slot number and frame type.For details, see the documentation that came with your network board.Floppy diskette drives: diskette size and storage size.Internal disks: make, model, and storage size.Disk coprocessor boards: idxid="w3313"book="_idx" docset="nw312" tidref="i1552"DCB drivers and I/O address.Default settings for disk coprocessor boards ( idxid="w3314"book="_idx" docset="nw312" tidref="i1553"DCBs) for standard architecture file servers are based on the type of PAL chip installed at position U3.11 and U4.11 on the board. Jumper settings must also match the PAL, which controls the interrupt I/O address. The defaults are listed in IDREF="FM24892"Table 1-2. (For alternate settings, see the DCB supplement.)LBL="1-2" INLINE="F"ID="FM24892"Default settings for DCBsWIDTH="72"U3.11WIDTH="72"U4.11WIDTH="60"I/O AddressWIDTH="60"InterruptWIDTH="72"814-198-001WIDTH="72"814-197-001WIDTH="60"340WIDTH="60"B814-198-001814-197-002348C814-198-002814-197-001320A814-198-002814-197-002328FDisk subsystems: number of drives, drive types, storage size, number of heads and cylinders.Mirrored disks.Install hard disks and network boards.If necessary, set switches or jumpers on hard disks and network boards.Set each address and interrupt according to the worksheet you completed in Step 1.Install internal hard disks and check for proper jumper settings and termination.See your hard disk documentation, or see "book="concepts" docset="nw312"SCSI Bus" in Concepts.Place each board in a slot in the file server.If you install idxid="w3315"book="_idx" docset="nw312" tidref="i6827"Token-Ring boards, cable the boards in the file server to the MAU before installing the operating system. Otherwise, the TOKEN driver will not load.Connect peripheral equipment to the file server and check jumper settings and termination.See the documentation for each peripheral, or see "book="concepts" docset="nw312"SCSI Bus" in Concepts.Configure the hardware by using the hardware's setup (reference or configuration) program.For details on the setup or reference program, see the documentation that came with your computer.If your hardware supports it, use a power-on password to secure the file server from unauthorized use.Do not select "Set network server mode" if your hardware has it listed in its setup program. This mode idxid="w3316"book="_idx" docset="nw312" tidref="i2640"disables keyboard input after DOS executes an AUTOEXEC.BAT file. As a result, you could not use the keyboard after the file server booted.Instead, use the keyboard protection feature in MONITOR. See "book="sysadmin" docset="nw312"MONITOR" inSystem Administration.Do not change the arbitration level of the idxid="w3317"book="_idx" docset="nw312" tidref="i1561"MFM or ESDI fixed-disk driver from the factory default setting. NetWare requires the default setting.(Conditional) Install the CD-ROM either as a network device or as a DOS device, according to manufacturer's instructions.idxid="w3318"book="_idx" docset="nw312" tidref="i5654"idxid="w3319"book="_idx" docset="nw312" tidref="i6238"(Conditional) If you are using an IBM® PS/2® computer, do not set it to SERVER mode.Record the setup information on the File Server Worksheet.For microchannel machines: make sure you record the type of controller in microchannel machines. You need this information when you load disk drivers later.When installing two or more of the same type of network board, check your network board documentation to avoid idxid="w3320"book="_idx" docset="nw312" tidref="i4494"address conflicts.If you have problems getting your hardware to run, see "book="sysadmin" docset="nw312"Troubleshooting Guide" in System Administration.(Conditional) If you will be using a idxid="w3321"book="_idx" docset="nw312" tidref="i1553"DCB disk driver for a disk subsystem, run idxid="w3322"book="_idx" docset="nw312" tidref="i1610"idxid="w3323"book="_idx" docset="nw312" tidref="i7237"DISKSET.EXE before installing your NetWare server.Install your NetWare v3.12 file server by following the procedures under IDREF="FM87752""Install Server Software" on page 18.During installation, you are advised of optional procedures that you can perform, such as disk mirroring, disk duplexing, partitioning, etc.ID="FM15526"Make Working Copies of the NetWare Diskettes idxid="w3324"book="_idx" docset="nw312" tidref="i7478"Before you install software, make working copies of the NetWare diskettes. Use only the working copies.ProcedureTo make working copies of the NetWare diskettes,Boot a personal computer with DOS.Use the DOS DISKCOPY command to format and copy each NetWare diskette to a high-capacity diskette.Label each copied diskette with the same name that appears on the original diskette.After making working copies, store the original NetWare diskettes in a secure place.Throughout the installation, when you are instructed to insert a specific diskette, use the working copy.ID="FM19542"Making 5.25-Inch Working Copies idxid="w3325"book="_idx" docset="nw312" tidref="i7478"For 5.25-inch diskettes, use XCOPY to copy the files to a hard disk and then copy them to 5.25-inch diskettes. You must have a PC or existing NetWare file server with idxid="w3326"book="_idx" docset="nw312" tidref="i2599"30 MB of available disk space.ProcedureCreate a network directory called NETWARE.Change to the newly-created directory.ID="FM34573"Insert theInstall diskette into a disk drive and type XCOPY A: /S/E <Enter>Repeat IDREF="FM34573"Step 3 for each diskette.When all NetWare diskettes have been copied to the NETWARE directory, format a 5.25-inch, high-density diskette and make it bootable by typing FORMAT A:/SLabel the diskette Install.ID="FM71878"For the remaining diskettes, insert each 5.25-inch, high-density diskette into the disk drive and type FORMAT A:/VLabel each diskette with the disk name that corresponds to the 3.5-inch diskette.ID="FM48606"Change to the directory that corresponds to the appropriate diskette label.ID="FM97961"Insert a diskette and type XCOPY *.* A: /S/ERepeat IDREF="FM71878"Steps 7, 8, and 9 until all diskettes in the NetWare directory are copied.LBL="2"ID="FM92799"Install the File Server SoftwareIf you are doing a first-time installation, complete the tasks explained in IDREF="FM37822"Chapter 1, "Prepare Your Site and Equipment" on page 5 before beginning.Necessary ResourcesThe file server Installation quick path card to get an overview of the process.A copy of the File Server Worksheet to be completed during installation.Working copies of NetWare v3.12 diskettes.Working copies of third-party disk drivers, LAN drivers, or NLMs (optional).ID="FM87752"Install Server Software idxid="w3327"book="_idx" docset="nw312" tidref="i2891"idxid="w3328"book="_idx" docset="nw312" tidref="i6408"Install your NetWare v3.12 idxid="w3329"book="_idx" docset="nw312" tidref="i4371"file server software by following the procedures under the headings that follow.During installation you are advised of optional installation procedures (disk mirroring, disk duplexing, partitioning, etc.).idxid="w3330"book="_idx" docset="nw312" tidref="i973"idxid="w3331"book="_idx" docset="nw312" tidref="i2891"Choose Your Installation MediumYou can install NetWare v3.12 from floppy diskettes, from CD-ROM, or from a network directory. Instructions for installing from each medium are found in the following sections.idxid="w3332"book="_idx" docset="nw312" tidref="i2891"idxid="w3333"book="_idx" docset="nw312" tidref="i2450"Installing from Floppy DiskettesProcedureMake working copies of all NetWare v3.12 diskettes.IDREF="FM15526"See "Make Working Copies of the NetWare Diskettes" on page 14 for instructions.ID="FM56061"Determine the method you will use to boot your file server by reading IDREF="FM34899""Determine File Server Boot Method" on page 21.Based on your decision in IDREF="FM56061"Step 2, follow the procedures under IDREF="FM67215""Install Server Software for Use with a DOS Boot Diskette" on page 22, or continue with IDREF="FM73230"Step 1 under IDREF="FM89978""Install Server Software for Use with a DOS Partition on the Hard Disk" on IDREF="FM89978"page 24.ID="FM75772"Installing from CD-ROM idxid="w3334"book="_idx" docset="nw312" tidref="i2891"idxid="w3335"book="_idx" docset="nw312" tidref="i930"If you have a CD-ROM device that shares a SCSI bus with a disk subsystem and contains volumes to which NetWare installation files are copied (typically volume SYS:), your keyboard may lock up while copying.Possible SolutionsIf the CD-ROM device has a parallel-to-SCSI adapter, reconfigure the CD-ROM under DOS to use this adapter, instead of the shared SCSI bus.Obtain a separate SCSI board for the CD-ROM device and repeat the installation. Load the NetWare SCSI driver for the subsystem SCSI board only.Recreate volume SYS: on the internal hard disk of the server, rather than on the subsystem drive. Do not load the NetWare SCSI driver until after installation.ProcedureID="FM95411"Install CD-ROM drivers according to manufacturer's instructions.Usually, the installation program updates the CONFIG.SYS and AUTOEXEC.BAT files to add the CD-ROM device driver.You may, however, need to update these files yourself. Follow the manufacturer's instructions.Insert the NetWare v3.12 CD-ROM into the CD-ROM reader.Turn on the CD-ROM reader.Reboot the computer.By rebooting, the computer executes the CONFIG.SYS and AUTOEXEC.BAT files.Change to the drive letter corresponding to the CD-ROM and type INSTALL <Enter>ID="FM18159"Continue with IDREF="FM44920"Step 2 under IDREF="FM89978""Install Server Software for Use with a DOS Partition on the Hard Disk." on IDREF="FM89978"page 24.ID="FM83900"Installing from Network Directory idxid="w3336"book="_idx" docset="nw312" tidref="i2891"idxid="w3337"book="_idx" docset="nw312" tidref="i4468"You can install from a network directory only if you already have a NetWare server (of any version) installed on your network.ProcedureID="FM34345"Copy the following Install andSystem_x diskettes to a directory on an existing NetWare server. Type NCOPY source_drive:destination_drive: /s /e /cor XCOPY source_drive:destination_drive: /s /eReplace source_drive with the disk drive letter containing the NetWare diskette. Replace destination_drive with the network drive letter you are copying to.For example, type NCOPY A: H: /S /E /Cor XCOPY B: G: /s /eOn every computer you want to make a NetWare v3.12 server, install NetWare DOS workstation software. Create a DOS partition of at least 5 MB.On every computer you want to make a NetWare v3.12 server, map a drive to the network server directory that contains the NetWare v3.12 files.ID="FM44346"Change to the INSTALL directory and type INSTALL <Enter>Continue with IDREF="FM44920"Step 2a on page 24.ID="FM34899"Determine File Server Boot Method idxid="w3338"book="_idx" docset="nw312" tidref="i4389"idxid="w3339"book="_idx" docset="nw312" tidref="i736"If you install from diskette, before you install the idxid="w3340"book="_idx" docset="nw312" tidref="i4371"server software, determine whether you want to boot your file server from a boot diskette or from a small DOS partition on the file server's hard disk.Use IDREF="FM63567"Table 2-1 to determine which method.LBL="2-1" INLINE="F"ID="FM63567"File server boot options idxid="w3341"book="_idx" docset="nw312" tidref="i4389"idxid="w3342"book="_idx" docset="nw312" tidref="i725"WIDTH="108"Boot optionWIDTH="168"AdvantagesWIDTH="144"DisadvantagesWIDTH="108"Boot DOS from a  disketteWIDTH="168"Creating boot diskettes is faster than  creating DOS partitions on the hard  disk.The entire internal hard drive can be  used for a NetWare partition.Boot diskettes can be stored  separately from the file server to  prevent tampering.WIDTH="144"Booting from diskette is  significantly slower.Boot DOS from a  partition on the hard  diskAfter installation, booting the file  server is significantly faster.Risk of media failure is much less.If you want space for  troubleshooting NLMs (such as  INSTALL and VREPAIR), in addition to  a large number of disk drivers and  the operating system (SERVER.EXE),  the DOS partition size can be made  large enough for all of these.The DOS partition (if you  follow our recommendation)  takes at least 5 MB of disk  space.Machines that do not have an idxid="w3343"book="_idx" docset="nw312" tidref="i4389"idxid="w3344"book="_idx" docset="nw312" tidref="i736"internal (channel 0) controller must boot with a boot diskette. Only hard disks attached to a standard bus internal controller can boot from a DOS partition.After you choose a boot method, go to IDREF="FM67215""Install Server Software for Use with a DOS Boot Diskette" or IDREF="FM89978""Install Server Software for Use with a DOS Partition on the Hard Disk" on page 24.ID="FM67215"Install Server Software for Use with a DOS Boot Diskette idxid="w3345"book="_idx" docset="nw312" tidref="i2891"idxid="w3346"book="_idx" docset="nw312" tidref="i1661"This installation option is available only when installing from floppy diskette.To determine whether to boot from a boot diskette or from a DOS partition, see IDREF="FM63567"Table 2-1 on page 21.ProcedureBoot DOS on the designated file server.For a standard architecture file server, use idxid="w3347"book="_idx" docset="nw312" tidref="i1661"idxid="w3348"book="_idx" docset="nw312" tidref="i1638"DOS 3.1 or later. For a microchannel file server, use DOS 3.3 or later.Create the server boot diskette.Format a high-capacity diskette as a system diskette using the /s parameter.Copy the following files from the System_1 diskette to the designated boot diskette:SERVER.EXENUT.NLMNWSNUT.NLMCopy the disk driver for your system from the System_2 diskette.To determine which disk driver, use IDREF="FM89861"Table 2-3 on page 30.(Optional) Copy the files in IDREF="FM22122"Table 2-2 that apply.LBL="2-2" INLINE="F"ID="FM22122"Optional boot diskette files idxid="w3349"book="_idx" docset="nw312" tidref="i1661"idxid="w3350"book="_idx" docset="nw312" tidref="i2300"WIDTH="108"CopyWIDTH="300"IfWIDTH="108"LAN_driverWIDTH="300"You want a copy in case your LAN driver located on volume SYS: becomes  corrupted.VREPAIRYou want a utility for repairing volume SYS:.Name space supportYou added name spaces to volumes.VREPAIR ModuleYou added name spaces to volumes and want a way for VREPAIR to repair  those volumes.Create an AUTOEXEC.BAT file on the boot diskette that includes the following command: SERVERFor information on creating an AUTOEXEC.BAT file, see your DOS manual.You can set a speed switch in most file servers to enable them to boot faster. With some file servers (such as COMPAQ), you can also use the idxid="w3351"book="_idx" docset="nw312" tidref="i3921"MODE.COM command to set the boot speed to High.Find MODE.COM on one of the diskettes that came with your computer and copy MODE.COM to your boot diskette. Include the following command in the AUTOEXEC.BAT file: MODE SPEED=HIGHChange to drive A: and type SERVERContinue with the software installation by following the procedures under IDREF="FM92108""Load Disk Driver Loadable Modules" on page 30.ID="FM89978"Install Server Software for Use with a DOS Partition on the Hard Disk idxid="w3352"book="_idx" docset="nw312" tidref="i2891"idxid="w3353"book="_idx" docset="nw312" tidref="i1684"To determine whether to boot from a boot diskette or from a DOS partition, see IDREF="FM63567"Table 2-1 on page 21.ProcedureID="FM73230"Insert the Install diskette in drive A: and reboot your computer, or change to drive A: and type A:INSTALL <Enter>ID="FM44920"Select "Install new NetWare v3.12" from the "Select an Installation Option" menu.Determine your DOS disk partition requirements.We strongly recommend that you create a DOS partition.However, if your file server doesn't have an internal hard disk or can't have one for security reasons, you must boot from diskette. If so, see IDREF="FM67215"See "Install Server Software for Use with a DOS Boot Diskette" on page 22.Your bootable DOS partition must have at least idxid="w3354"book="_idx" docset="nw312" tidref="i1684"2 MB of free (usable) space, though we recommend that you allocate a minimum of 5 MB.ID="FM72333"Select "Create a new DOS partition."If your hard disk contains a previous DOS partition, continuing with the next step will erase that partition and destroy all data. Be sure you have backup copies of those files before continuing.You can exit INSTALL to make backup copies by selecting "Exit to save files" from the "Disk Partition Options" menu.Select "Create a DOS partition."Enter the size (in MB) of the new partition.Be sure to leave plenty of available disk space for your NetWare partition.idxid="w3355"book="_idx" docset="nw312" tidref="i2599"To mirror two internal hard disks and boot from the DOS partition on drive 0, create the same-sized DOS partition on both hard disks. If drive 0 should ever go bad, you can use the DOS partition on drive 1 to boot from.Press any key to restart INSTALL.You must reboot your server so that DOS recognizes the new partition. Pressing any key automatically reboots the server. Be sure the Install diskette is in drive A:.Format the newly created DOS partition.When INSTALL starts again, it recognizes that an unformatted DOS partition exists on your hard disk and prompts you to begin formatting.Press <Enter> to continue.INSTALL now loads FORMAT.COM.A warning similar to the following appears: WARNING All existing data on non-removable disk C: will be destroyed!--Continue (Y/N)?This message is generated by FORMAT.COM. The partition table has already been created and previous data is unrecoverable at this point.Type "Y" to continue.After the format is complete, total disk space and available disk space are displayed.Press any key to continue.ID="FM41930"Name the file server. idxid="w3356"book="_idx" docset="nw312" tidref="i4030"Give the file server a unique name using these guidelines:The name can be from 47 to 298 characters.Valid characters include alphanumeric characters, hyphens, and underscores (you must use a number or letter for the first character in the name).The name cannot contain a period (.).Spaces are not allowed.ID="FM40511"Assign an idxid="w3357"book="_idx" docset="nw312" tidref="i3018"IPX idxid="w3358"book="_idx" docset="nw312" tidref="i2936"idxid="w3359"book="_idx" docset="nw312" tidref="i4555"internal network number.An internal network idxid="w3360"book="_idx" docset="nw312" tidref="i3017"number is generated randomly by INSTALL. Accept this number or enter one of your own. To enter a number of your own, the number must be unique and it must beA hexadecimal number (base 16: using numbers 0 through 9 and letters A through F).One to eight digits.You can't assign an IPX internal network number of "0" or "FFFFFFFF."For more on internal network numbers, see "book="concepts" docset="nw312"IPX internal network number" in Concepts.WIDTH="120"ToWIDTH="192"Do thisWIDTH="120"Accept the default  number.WIDTH="192"Press <Enter>.Assign a new number.Use the <Delete> key to erase each  unwanted digit.Type the new number.(If you make a mistake, press <Esc>, then <Enter>, and type the number again.)Press <Enter>.For more information on the IPX internal network number or network addressing, see "book="concepts" docset="nw312"Network Numbering" inConcepts.Press <Enter> to copy the server boot files to the hard disk.idxid="w3361"book="_idx" docset="nw312" tidref="i4384"idxid="w3362"book="_idx" docset="nw312" tidref="i730"Server boot files are copied from the System_1 diskette to a directory in the DOS partition on the hard disk.Server boot files include SERVER.EXE (the NetWare operating system), INSTALL.NLM, disk drivers, name spaces and LAN drivers.Accept or change the default source path.WIDTH="132"ToWIDTH="168"Do thisWIDTH="132"Copy the files from drive A:.WIDTH="168"Continue with IDREF="FM95781"Step 7c.Copy the files from a source  other than the default.Press <F2>.Type the new source drive and path.Press <Enter>.ID="FM15900"WIDTH="120"ToWIDTH="192"Do thisWIDTH="120"Copy the files to the  default destination  directory created for you  (SERVER.312).WIDTH="192"Continue with IDREF="FM95781"Step 7c.Copy the files to a  destination directory  other than the default.Press <F4>.Press <Backspace> to erase the unwanted  portions of the default path.Type the new destination path.Press <Enter>.Select "Yes" and press <Enter> again.ID="FM95781"Press <Enter> to begin copying.During the copy process, insert the NetWare diskettes you are prompted for into the source drive and press <Enter>.A bar graph indicates the status of the copy process:LBL="2-1"Copy process bar graphFILE="n312i77a.pbm"Once all files are copied, the language screen appears:LBL="2-2"Language Configuration Screen idxid="w3363"book="_idx" docset="nw312" tidref="i3152"FILE="n312i125.pbm"ID="FM92806"Enter your Country Code, Code Page, and Keyboard Mapping setting and press <F10>.For a list of settings for each field, highlight a field and press <Enter>, or refer to your DOS manual.The following screen appears.LBL="2-3"Select a filename formatFILE="n312i126.pbm"Select the format for your DOS files and press <Enter>.Selecting "NetWare Filename Format" leaves previously-saved DOS files with non-standard DOS characters as they are.Selecting "DOS Filename Format" replaces all non-standard DOS characters with standard DOS characters.If you select "DOS Filename Format," and your selection in IDREF="FM92806"Step 8 is unchanged, press <F9> to view the character changes that will be made.You are asked if you want to specify startup set commands.Select "Yes" or "No."Selecting "Yes" brings up a blank screen for entering the startup commands. This screen is used mainly for changing the default setting of SET AUTO REGISTER MEMORY to OFF.Turning off SET AUTO REGISTER MEMORY allows you to load disk drivers that can't be loaded in the memory area above 16 MB.Changing the SET AUTO REGISTER MEMORY setting to OFF disables all memory above 16 MB. For optimal use of RAM, install a disk driver that can be loaded in the memory area above 16 MB.The documentation that accompanied your disk driver indicates the RAM required for loading.Press <F10> to save the startup commands.(Optional) Add SERVER.EXE to your AUTOEXEC.BAT file.When the copy process is complete, INSTALL prompts you to add SERVER.EXE to your AUTOEXEC.BAT file. idxid="w3364"book="_idx" docset="nw312" tidref="i6243"SERVER.EXE contains the NetWare v3.12 operating system.WIDTH="60"If you chooseWIDTH="228"This happensWIDTH="60"YesWIDTH="228"SERVER.EXE loads automatically when you reboot the  file server.(If you're operating from a floppy disk, you'll be asked  to insert the floppy disk containing the SERVER.EXE file)NoThe DOS prompt appears whenever you reboot the file  server and you must type "SERVER" to load NetWare.Insert the Install diskette into drive A: and press <Enter>.The INSTALL utility automatically executes SERVER.EXE.(Optional) Use the idxid="w3365"book="_idx" docset="nw312" tidref="i5780"REGISTER MEMORY command to add additional memory.If your file server is incapable of addressing memory over 16MB, find the hexadecimal address where the memory begins and the hexadecimal length of the memory. For example, for a machine with 32MB of RAM, type REGISTER MEMORY 1000000 1000000 <Enter>Continue with IDREF="FM92108""Load Disk Driver Loadable Modules" on page 30.ID="FM92108"Load Disk Driver idxid="w3366"book="_idx" docset="nw312" tidref="i4310"Loadable Modules idxid="w3367"book="_idx" docset="nw312" tidref="i1561"idxid="w3368"book="_idx" docset="nw312" tidref="i4310"After you create a boot diskette or a bootable disk partition for the file server, you must load the disk drivers.Your computer system, disk drive, and controller combination determine which NetWare disk driver to load.ProcedureLoad the disk drivers for the controller board in your file server by typing LOAD disk_driver<Enter>Replace disk_driver with one of the drivers shown in the "Disk Driver" column in IDREF="FM89861"Table 2-3.For example, if you have an AT-type controller board, type LOAD ISADISK <Enter>If you load the idxid="w3369"book="_idx" docset="nw312" tidref="i1561"idxid="w3370"book="_idx" docset="nw312" tidref="i1553"DCB driver for a DCB that has been used previously, you can add an option to the command line (/s=0) to make the driver load more quickly. The /s=0 option disables the EEPROM test for non-existent devices.LBL="2-3" INLINE="F"ID="FM89861"Disk driver determination idxid="w3371"book="_idx" docset="nw312" tidref="i1561"WIDTH="96"Type of ArchitectureWIDTH="96"Controller TypeWIDTH="96"Add-On BoardWIDTH="96"Disk DriverWIDTH="96"Industry Standard  Architecture (ISA)WIDTH="96"AT, MFM, RLL, ARLLWIDTH="96"Built inWIDTH="96"ISADISKThird-party  secondary adapterISADISKESDIISADISK /BIDEIDENovell SCSIDCBDCBMFMBuilt inPS2MFMIBM SCSIIBM SCSIPS2OPTBuilt inPS2OPTExtended Industry  Standard  Architecture (EISA)AT classBuilt inISADISKSee vendorISADISKEISA vendor proprietaryBuilt inSee vendorSee vendorSee vendorIf you install more than one idxid="w3372"book="_idx" docset="nw312" tidref="i1549"disk controller board, load the disk drivers in the order of the controller boards. Load the driver for the internal controller first, the driver for the first disk controller board second, and so forth.For more information, see "book="concepts" docset="nw312"Device Numbering" inConcepts. If you do not follow the correct order, system messages about your hard disks will be incorrect.On ISA and IDE file servers, answer the prompt for the I/O port address.On microchannel or EISA file servers, confirm the slot number for the network board.If you have external disk subsystems that use the DCB disk driver or other disk drivers that require DISKSET, go to IDREF="FM90724""Run DISKSET (Optional)" on page 32. If you do not need to run DISKSET, go to IDREF="FM44373""Create NetWare Disk Partition Tables" on page 35.ID="FM90724"Run DISKSET (Optional) idxid="w3373"book="_idx" docset="nw312" tidref="i1607"Use DISKSET only with ADIC/Novell's DCB disk driver or with a third-party driver if the manufacturer requires you to use DISKSET. idxid="w3374"book="_idx" docset="nw312" tidref="i1607"DISKSET places identification information about external hard disks on the EEPROM of a Disk Coprocessor Board (DCB) or its third-party equivalent.The ID information on the EEPROM allows the disks to communicate through the DCB to the file server.ProcedureTo run DISKSET, type DISKSET <Enter>Select "Disk Coprocessor Board Setup" from the "Diskset Options" menu.Select the disk driver and settings that match external harddisk 0 (physical device 0 attached to the controller) on the "Select Desired Driver" list:LBL="2-4"Select Desired DriverFILE="n312i13a.pbm"ID="FM31882"On the "EEPROM Config" screen, highlight the text "***>>--none" under the "Device 0" heading next to the appropriate controller address:LBL="2-5"EEPROM Config ScreenFILE="n312i14a.pbm"Press <Ins>.Scroll through the "Select Disks and Controller Type" list and select the name of the hard disk you are setting up:LBL="2-6"Select Disks and Controller TypeFILE="n312i15a.pbm"If you have a NetWare-ready hard disk, select "NetWare Ready/Embedded SCSI."After you select the hard disk, the "EEPROM Configuration" screen looks similar to the following:LBL="2-7"EEPROM ScreenFILE="n312i16a.pbm"(Conditional) If you have a second hard disk attached to the same controller, move to the "/ ***>>__none" text under the "Device 1" heading (for physical device 1), and press <Ins>.Scroll through the "Select Disk(s) and Controller Type" list, and select the name of the hard disk.After you select the hard disk, the "EEPROM Configuration" screen looks similar to the following:LBL="2-8"EEPROM ScreenFILE="n312i17a.pbm"ID="FM27325"Save the information by pressing <Esc> and answering "Yes" at the prompt.To configure the remaining hard disks for your file server, repeat IDREF="FM31882"Steps 4 through IDREF="FM27325"9.For more information, see "book="sysadmin" docset="nw312"DISKSET" inSystem Administration.Continue with IDREF="FM44373""Create NetWare Disk Partition Tables" on page 35.ID="FM44373"Create NetWare Disk Partition Tables idxid="w3375"book="_idx" docset="nw312" tidref="i4244"idxid="w3376"book="_idx" docset="nw312" tidref="i1594"idxid="w3377"book="_idx" docset="nw312" tidref="i2599"Once the disk drivers have been loaded, use idxid="w3378"book="_idx" docset="nw312" tidref="i2836"idxid="w3379"book="_idx" docset="nw312" tidref="i7237"INSTALL.NLM to create a NetWare partition on the hard disk.One internal hard disk can contain an active DOS partition and a NetWare partition. External hard disks can have only NetWare partitions. Network volumes are created on NetWare partitions.IDREF="FM72572"Figure 2-9 illustrates hard disk partitions:LBL="2-9"ID="FM72572"Hard disk partitionsFILE="n312i18a.pbm"ProcedureLoad INSTALL by typing LOAD path INSTALL <Enter>Replace path with the directory path to INSTALL.NLM.From the "Installation Options" menu, select "Disk Options."From the "Available Disk Options" menu, select "Partition Tables."If you have more than one disk, select the disk you need to partition from those listed on the "Available Disk Drives" menu.You may have other DOS or NetWare partitions on your hard disk (apart from the primary DOS boot partition created earlier).If you want NetWare to use the space, delete the old partitions before creating a new NetWare v3.12 partition. To complete the task, select idxid="w3380"book="_idx" docset="nw312" tidref="i2599"idxid="w3381"book="_idx" docset="nw312" tidref="i1544""Delete Partition" from the "Partition Options" menu.Deleting a partition deletes all data. To delete existing partitions, (don't delete the DOS partition you created in IDREF="FM72333"Step 3a on page 24) make sure you have a backup of the data prior to following these procedures.From the "Partition Options" menu, select "Create NetWare Partition."idxid="w3382"book="_idx" docset="nw312" tidref="i4244"idxid="w3383"book="_idx" docset="nw312" tidref="i1594"idxid="w3384"book="_idx" docset="nw312" tidref="i2599"NetWare allows only one NetWare partition per disk. Therefore, if the disk has more than one free partition area, select an area for the NetWare partition. NetWare allocatesThe marked free partition area as a NetWare partition.98% of the space available as a data area.2% of the space for the idxid="w3385"book="_idx" docset="nw312" tidref="i2689"Hot Fix redirection area.This information is displayed on the "Partition Information" screen. The screen shows the space on the NetWare partition, the blocks allocated to the data area, and the redirection area:LBL="2-10"Partition InformationFILE="n312i19a.pbm"ID="FM52221"Accept or decrease the NetWare partition size and press <Enter>.If you don't want to use the whole partition for NetWare, idxid="w3386"book="_idx" docset="nw312" tidref="i4244"idxid="w3387"book="_idx" docset="nw312" tidref="i2599"idxid="w3388"book="_idx" docset="nw312" tidref="i1594"decrease the partition size by entering a smaller number of cylinders in the "Partition Size" field.To determine the number of cylinders to decrease, divide available cylinders by available disk space; then multiply that number by the number of megabytes of memory you want in the partition:LBL="2-11"Formula for decreasing the number of cylinders idxid="w3389"book="_idx" docset="nw312" tidref="i2493"FILE="n312i116.pbm"Accept or change the size of the data area or the Hot Fix redirection area and press <Enter>.Move the cursor to one of the fields and enter the number of new blocks in that field. NetWare calculates the remaining space in the other field.You can enter a fixed percentage of the disk partition as a redirection area by multiplying the percentage by the partition size, dividing that sum by 100, multiplying that by 1000, and then dividing it by the block size (the default block size is 4 KB).For example, if you had a 178.2MB partition and wanted to set aside 5% as a redirection area, you would calculate it as follows:LBL="2-12"Formula for determining a fixed percentage of disk space idxid="w3390"book="_idx" docset="nw312" tidref="i2493"FILE="n312i117.pbm"If you have a NetWare-ready hard disk, ignore the free space left on the hard disk and continue with IDREF="FM88675"Step 8.ID="FM88675"Press <Esc> and select "Yes" at the prompt to create the partition.ID="FM31146"If you have more than one disk, press <Esc> to return to the "Available Disk Drives" menu. Select the next disk to partition.Repeat IDREF="FM52221"Steps 6 through IDREF="FM31146"9 for each disk.Press <Esc> to return to the "Available Disk Options" menu.To mirror or duplex your file server's NetWare partitions, go to IDREF="FM81548""Mirror or Duplex the Disk (Optional)" on page 39. Otherwise, press <Esc> and go to IDREF="FM23263""Create Volume SYS:" on page 42.(Optional) You may want to conduct a surface test to check for bad blocks (select "Surface Test" on the "Available Disk Options" menu). The idxid="w3391"book="_idx" docset="nw312" tidref="i6602"surface test runs in the background so you can do work on other disks while the test is running. In most cases, Hot Fix redirects bad blocks as it finds them if you choose not to run the surface test.ID="FM81548"Mirror or Duplex the Disk (Optional) idxid="w3392"book="_idx" docset="nw312" tidref="i2599"idxid="w3393"book="_idx" docset="nw312" tidref="i3916"idxid="w3394"book="_idx" docset="nw312" tidref="i1753"To protect data against the failure of a hard disk or a hard disk controller, NetWare can make exact duplicates of the same NetWare partition on two separate hard disks.If hard disks are connected to the same hard disk controller, the process is called mirroring. However, mirroring doesn't protect against the failure of a hard disk controller. IDREF="FM19342"Figure 2-13 illustrates disk mirroring:LBL="2-13"ID="FM19342"Disk mirroringFILE="n312i31a.pbm"If NetWare partitions are duplicated over two or more hard disk controllers, the process is called duplexing and is the most effective way to protect data.IDREF="FM64815"Figure 2-14 on page 40 illustrates disk duplexing.LBL="2-14"ID="FM64815"Disk duplexingFILE="n312i20a.pbm"For more information, see "book="concepts" docset="nw312"Disk Duplexing" or "book="concepts" docset="nw312"Disk Mirroring" inConcepts.Even though your hard disks may be mirrored or duplexed, perform a regular backup of your hard disks at least once a week.ProcedureTo mirror or duplex partitions on two or more hard disks, select "Mirroring" from the "Available Disk Options" menu.Secondary partitions (up to 15 hard disks that can be mirrored or duplexed to the first, or primary hard disk) must have partition sizes greater than or equal to the primary partition.Select the primary logical partition to be mirrored or duplexed on the "Partition Mirroring Status" screen:LBL="2-15"Partition Mirroring StatusFILE="n312i21a.pbm"For more information on logical partitions, see "book="concepts" docset="nw312"Device Numbering" in Concepts.Press <Ins> on the "Mirrored NetWare Partitions" screen:LBL="2-16"Mirrored NetWare PartitionsFILE="n312i22a.pbm"Select the secondary partition to be mirrored or duplexed with the primary partition on the "Available Partitions" screen:LBL="2-17"Available PartitionsFILE="n312i23a.pbm"If the secondary partition is larger than the primary partition, a screen appears to warn you that the mirrored or duplexed partition will be the size of the smaller partition.Press <Esc> to remove the warning screen and select "Yes" at the prompt to make the NetWare partitions equal.The mirrored or duplexed partitions look similar to the following:LBL="2-18"Mirrored NetWare PartitionsFILE="n312i24a.pbm"Press <Ins> to mirror or duplex additional hard disks to the primary hard disk.Go to IDREF="FM23263""Create Volume SYS:" on page 42.ID="FM23263"Create Volume SYS: idxid="w3395"book="_idx" docset="nw312" tidref="i1269"idxid="w3396"book="_idx" docset="nw312" tidref="i7365"idxid="w3397"book="_idx" docset="nw312" tidref="i7364"With NetWare v3.12, your file server can have from idxid="w3398"book="_idx" docset="nw312" tidref="i7340"1 to 64 volumes. Your NetWare partition must have a SYS: volume for storing the idxid="w3399"book="_idx" docset="nw312" tidref="i7365"SYSTEM, PUBLIC, LOGIN, and MAIL directories.You may also want to create a volume for applications and data. If the bindery on volume SYS: becomes corrupted and can't be fixed with BINDFIX, you can rename the corrupted volume and create a new volume SYS:. Then you can go into the renamed volume and delete the old bindery files.The highest performance configuration spans a single volume over many hard disks that supports DOS name spaces only.idxid="w3400"book="_idx" docset="nw312" tidref="i7340"When spanning single volumes over hard disks, we strongly recommend that you duplex every hard disk. See "book="concepts" docset="nw312"Disk Duplexing" inConcepts.If your network includes workstations using an operating system that allows long filenames (such as Macintosh workstations), idxid="w3401"book="_idx" docset="nw312" tidref="i7340"idxid="w3402"book="_idx" docset="nw312" tidref="i1269"create a separate volume for each name space.Long filenames take up more disk space than DOS filenames. This helps optimize disk space use and isolates network problems more easily.ProcedureFrom the "Installation Options" menu, choose "Volume Options."ID="FM44005"Press <Ins> on the "Volumes" screen.If you have more than one hard disk (listed as a "Logical Partition"), select one to place the first volume on from those listed on the "Free Space Available For Volume Segments" screen.NetWare automatically enters volume SYS: as the first volume on the "New Volume Information" screen. Its default size is the entire partition.(Optional) To idxid="w3403"book="_idx" docset="nw312" tidref="i7340"idxid="w3404"book="_idx" docset="nw312" tidref="i1269"create more than one volume, enter the size of volume SYS: in the "Initial Segment Size" field.The hard disk space not allocated for volume SYS: is then available for additional volumes.ID="FM22449"Press <Esc> and answer "Yes" at the "Create Volume?" prompt to create volume SYS:.(Optional) Create additional volumes by repeating IDREF="FM44005"Steps 2 through IDREF="FM22449"4.When creating volumes other than SYS:, you are required to enter a volume name.(Optional) To change the block size, continue with IDREF="FM93315""Changing the Block Size (Optional)." Otherwise, press the Down-arrow key and determine whether you want to create additional volumes on external hard disks by reading IDREF="FM41579""Creating Additional Volumes on External Disk Subsystems (Optional)" on page 46.ID="FM93315"Changing the Block Size (Optional) idxid="w3405"book="_idx" docset="nw312" tidref="i7340"idxid="w3406"book="_idx" docset="nw312" tidref="i947"idxid="w3407"book="_idx" docset="nw312" tidref="i707"In NetWare v3.12, the default block size is idxid="w3408"book="_idx" docset="nw312" tidref="i707"4 KB, or 4096 bytes of data. While creating volume SYS:, you can change the block size to 8, 16, 32, or 64 KB. Block size is the same on all segments of a volume.There are advantages to using small or large block sizes.Small block sizes need more file server memory to track the FAT and Directory tables; however, if you have many small files, less hard disk space is wasted by partially filled blocks.Larger block sizes are best for large database records. ProcedureWith volume SYS: displayed in the "Volumes" screen, press <Enter> to get the "Volume Block Size" screen.Press the Down-arrow key to advance to the "Volume Block Size" field; then press <Enter> for a list of block size options.IDREF="FM43256"Figure 2-19 shows available block sizes.LBL="2-19"ID="FM43256"Available block sizesFILE="n312i25a.pbm"Selecting large block sizes (32 KB or 64 KB) can cause some DOS utilities to calculate the amount of free hard disk space incorrectly.(Optional) Press <Enter> to make changes to the initial segment size.To have more than idxid="w3409"book="_idx" docset="nw312" tidref="i7340"idxid="w3410"book="_idx" docset="nw312" tidref="i1269"one volume on a hard disk, enter a lower number for the idxid="w3411"book="_idx" docset="nw312" tidref="i2825"idxid="w3412"book="_idx" docset="nw312" tidref="i6216""Initial Segment Size" to accommodate other volumes.Initially, NetWare assigns the entire partition as one volume segment.If a volume is contained entirely on one hard disk, the file server can only perform a certain number of reads and writes to that volume per second.However, if the volume spans two, three, or four hard disks, the file server can perform two, three, or four times as many reads and writes to the volume per second.Use these idxid="w3413"book="_idx" docset="nw312" tidref="i707"rules to determine whether to make changes:One hard disk can have up to 8 volume segments (non-contiguous storage spaces) per disk.A volume can have up to 32 volume segments.One volume can span 32 hard disks if each disk contains one volume segment.Volume size can be increased but never decreased.If you add hard disks to a disk subsystem, you can increase the volume size without bringing down the file server.To add an internal hard disk to increase the volume, bring down the server to add another internal hard disk.On a volume spanning several hard disks, if one hard disk goes down, the entire volume goes down (unless that hard disk is mirrored or duplexed).Determine the size of the volume segment by dividing 1024 by the block size. The result is blocks per megabyte:LBL="2-20"Formula for determining blocks per megabyte idxid="w3414"book="_idx" docset="nw312" tidref="i2493"FILE="n312i114.pbm"Multiply the number of blocks per megabyte by the available disk space (in megabytes) you want to allocate. The result is the necessary block segment size:LBL="2-21"Formula for determining block segment size idxid="w3415"book="_idx" docset="nw312" tidref="i2493"idxid="w3416"book="_idx" docset="nw312" tidref="i707"FILE="n312i119.pbm"Set the size of volume SYS: between idxid="w3417"book="_idx" docset="nw312" tidref="i7365"30 and 40 MB, depending on your needs and your hardware configuration.Press <Esc> and answer "Yes" at the "Create Volume?" prompt to change the block size.To create additional volumes on an external disk subsystem, go to IDREF="FM41579""Creating Additional Volumes on External Disk Subsystems (Optional)" Otherwise, go to IDREF="FM45710""Mount Volumes" on page 47.ID="FM41579"Creating Additional Volumes on External Disk Subsystems (Optional) idxid="w3418"book="_idx" docset="nw312" tidref="i7340"idxid="w3419"book="_idx" docset="nw312" tidref="i1269"If your NetWare v3.12 file server uses external hard disks you can choose to make the additional hard disks separate volumes.ProcedureFrom the "New Volume Information" screen, press <Esc> until the <Ins> option is enabled.ID="FM89357"Press <Ins> on the "Volumes" screen.If you have more than one hard disk (listed as a "Logical Partition"), select one to place the first volume on from those listed on the "Free Space Available For Volume Segments" screen.(Optional) To have more than one volume on the external hard disk, enter the volume size in the "Volume Segments" field.Hard disk space not allocated for the new volume is available for additional volumes.ID="FM58951"Press <Esc> and answer "Yes" at the "Create Volume?" prompt to create the new volume.(Optional) Create additional volumes on the hard disk by repeating IDREF="FM89357"Steps 2 through IDREF="FM58951"4.Continue with IDREF="FM45710""Mount Volumes" on page 47.ID="FM45710"Mount Volumes idxid="w3420"book="_idx" docset="nw312" tidref="i7340"idxid="w3421"book="_idx" docset="nw312" tidref="i3967"Once you create volumes, you must mount them, one at a time.ProcedureID="FM51754"Select the volume to mount from the "Volumes" list.Since volume SYS: was created first, it is highlighted.Press the Down-arrow key to highlight the "Status" field.ID="FM63542"Press <Enter> and select "Mount Volume."To mount other volumes, press <Esc> and repeat IDREF="FM51754"Steps 1 through IDREF="FM63542"3.Press <Esc> twice to return to the "Installation Options" menu.Continue with IDREF="FM88320""Copy SYSTEM and PUBLIC Files."ID="FM88320"Copy SYSTEM and PUBLIC Files idxid="w3422"book="_idx" docset="nw312" tidref="i1251"idxid="w3423"book="_idx" docset="nw312" tidref="i6656"idxid="w3424"book="_idx" docset="nw312" tidref="i5696"INSTALL loads the NetWare operating system and utility files into the file server's SYS:PUBLIC and SYS:SYSTEM directories.WIDTH="132"ToWIDTH="180"Do thisWIDTH="132"Install the SYSTEM and  PUBLIC files from drive A:.WIDTH="180"Continue with IDREF="FM37095"Step 1.Install the SYSTEM and  PUBLIC files from a source other than drive A:.Follow the procedures under IDREF="FM96614""Copy  SYSTEM and PUBLIC Files from a  Network Directory" on page 48.ProcedureID="FM37095"Return to the "Installation Options" menu.Select "System Options."Select "Copy System and Public Files" from the "Available System Options" menu.Insert the System_2 diskette and press <Enter>.Follow the prompts for the other diskettes.Press <F5> to skip a diskette. For more information, see "book="sysadmin" docset="nw312"Install" inSystem Administration.Continue with IDREF="FM96249""Load LAN Drivers and Frame Types" on page 49.ID="FM96614"Copy SYSTEM and PUBLIC Files from a Network Directory idxid="w3425"book="_idx" docset="nw312" tidref="i6656"idxid="w3426"book="_idx" docset="nw312" tidref="i5696"ProcedureFrom the "Installation Options" menu, select "System Options."From the "Available System Options" menu, select "Copy System and Public Files."Press <F6>.Specify the drive (or directory) that contains the files. For example, type G:\DOWNLOAD <Enter>This download directory contains directories that correspond to the NetWare v3.12 diskettes.Continue with IDREF="FM96249""Load LAN Drivers and Frame Types" on page 49.ID="FM96249"Load LAN Drivers and Frame Types idxid="w3427"book="_idx" docset="nw312" tidref="i3085"Once the SYSTEM and PUBLIC files are copied, continue the installation process by loading LAN drivers.Select LAN drivers for the cabling system and the network boards you use.The idxid="w3428"book="_idx" docset="nw312" tidref="i2504"default Ethernet frame type for NetWare v3.12 is idxid="w3429"book="_idx" docset="nw312" tidref="i2504"802.2.If you have a idxid="w3430"book="_idx" docset="nw312" tidref="i2504"mixed environment where you have v3.11 or earlier versions of NetWare that use the 802.3 frame type, you may need to specify both 802.2 and idxid="w3431"book="_idx" docset="nw312" tidref="i2504"802.3 frame types. To do this, load the LAN driver twice and specify a different frame type for each LAN driver.A workstation running the 802.3 frame type can't view the v3.12 server (which defaults to 802.2) until both frame types are loaded.Loading both 802.2 and 802.3 frame types can affect network speed and performance. Do not load both frame types unless it is necessary.ProcedureLoad the drivers with the 802.2 frame type. Type LOAD LAN_driver<Enter>IDREF="FM14495"Table 2-4 on page 50 lists the drivers supported by Novell, Inc.Third-party drivers are also included with NetWare v3.12, including drivers from 3COM®, Cabletron, Datacom, Hewlett Packard®, IBM, Intel®, Madge, Proteon®, Racal, Standard Microsystems, Thomas-Conrad, and Ungermann-Bass®.(Conditional) If you are loading a Novell-supplied LAN driver, replace LAN_driver with the driver listed in IDREF="FM14495"Table 2-4 on page 50 for your cabling system and network board.(Conditional) If you are loading a third-party LAN driver, load the driver from either the System_4 diskette or the diskette that came with the network board.LBL="2-4" INLINE="F"ID="FM14495"LAN driver identification idxid="w3432"book="_idx" docset="nw312" tidref="i3085"WIDTH="120"Cabling SystemWIDTH="168"Network BoardWIDTH="120"DriverWIDTH="120"ARCnetWIDTH="168"RX-NetRX-Net IIRX-Net/2WIDTH="120"TRXNETEthernetNE/2NE/2TNE2NE2-32NE2_32 (replaces NE2-32)NE1000 - ASSY 950-054401NE1000 - ASSY 810-160-001NE1000NE2000 - ASSY 810-149NE2000T - ASSY 810-000220NE2000NE2100 - ASSY 810-000209NE2100NE1500TNE1500TNE3200NE3200NE32HUBNE32HUBToken-RingNTR2000NTR2000For example, if you have an Ethernet cabling system and an NE2000 network board, type LOAD NE2000 FRAME = ETHERNET_802.2 <Enter>If you need to load the 802.3 frame type as well, repeat the command this time substituting 802.3 for the frame type.Answer the prompts for addresses and interrupts according to the information you entered on the File Server Worksheet.(Conditional) Load the drivers with the idxid="w3433"book="_idx" docset="nw312" tidref="i2504"802.3 frame type. Type LOAD LAN_driver FRAME=frame_type<Enter>Replace frame_type with the frame type listed in IDREF="FM65843"Table 2-5 for your cabling system and network board.LBL="2-5" INLINE="F"ID="FM65843"Frame type idxid="w3434"book="_idx" docset="nw312" tidref="i2504"WIDTH="96"Cabling SystemWIDTH="120"Frame TypeWIDTH="204"ExplanationWIDTH="96"ARCnetWIDTH="120"Novell_RX-NETWIDTH="204"Default. Use on networks connected by  ARCnet cabling.EthernetETHERNET_802.2Default. Assigns the IEEE and OSI standard  frame type. Required for networks using NCP  security signature.ETHERNET_IIAssigns a unique packet header (type code).  Use on networks connected to DEC  computers or to computers using the TCP/IP  protocol.ETHERNET_802.3Assigns the Novell IPX frame. Use on an  existing network that only uses the NetWare  802.3 frame type.ETHERNET_SNAPUse when the 802.2 SNAP extension is  required.Token ringTOKEN-RINGDefault. Assigns the standard packet header  802.2. Use only with protocols that require  802.2 encapsulation (such as the OSI protocol  suite).TOKEN-RING_SNAPAssigns the 802.2 with SNAP header. Use with  networks that need to communicate with  protocols such as AppleTalk and TCP/IP.IBM PC NetworkIBM_PCN2_802.2Default. Use on networks connected by PC  network cabling.IBM_PC2N2_SNAPUse when the 802.2 SNAP extension is  required.For example, if you have an Ethernet cabling system and an NE2000 network board, type LOAD NE2000 FRAME=ETHERNET_802.3<Enter>A message similar to the following appears: Do you want to add another frame type for a previously loaded board? nType "Y" to continue.Select the correct frame type from the confirmation list.The following message appears: Previously loaded module was used re-entrantlyFor more information, see "book="sysadmin" docset= "nw312"Load LAN Driver" in System Administration.Bind the Protocol to the LAN Driver idxid="w3435"book="_idx" docset="nw312" tidref="i700"idxid="w3436"book="_idx" docset="nw312" tidref="i3020"The final installation step is to bind the protocol to the LAN driver.NetWare v3.12 allows protocols other than IPX to function on the network. The steps below use IPX as an example protocol to bind each LAN driver in the file server.ProcedureBind IPX to the LAN driver.To bind IPX to each LAN driver, type BIND IPX TO LAN_driverIf you use idxid="w3437"book="_idx" docset="nw312" tidref="i3085"multiple frame types on the same network board, NetWare v3.12 lists the idxid="w3438"book="_idx" docset="nw312" tidref="i2504"frame types that are loaded and asks you to select the board you want to bind IPX to.You can bind IPX to all those frame types, as long as you give a different network address to each frame type.For more on network numbers, see "book="concepts" docset="nw312"Network numbering" in Concepts.If you have loaded the same LAN driver several times (for several network boards of the same type), select the board to be bound to the protocol.To bind multiple frame types, see "book="sysadmin" docset="nw312"BIND" inSystem Administration.Assign the idxid="w3439"book="_idx" docset="nw312" tidref="i4481"idxid="w3440"book="_idx" docset="nw312" tidref="i159"network address.Each LAN driver must be assigned the network address that identifies the cabling system it uses to communicate with similar LAN drivers on the network.This network address is not the same as the internal IPX network number you assigned to the file server in IDREF="FM40511"Step 6a on page 26.At the prompt, type the number that enables the LAN driver and network board in the file server to communicate with the network. The address must beidxid="w3441"book="_idx" docset="nw312" tidref="i4481"A hexadecimal number (base 16: using numbers 0 through 9 and letters A through F).One to eight digits.If you use idxid="w3442"book="_idx" docset="nw312" tidref="i4481"multiple frame types with your LAN drivers, assign a network address for each frame type.For more on internal network numbers, see "book="concepts" docset="nw312"Network numbering" inConcepts.NetWare v3.12 is now installed. However, you must still create STARTUP.NCF and AUTOEXEC.NCF files. These files are necessary to boot the file server.Continue with IDREF="FM58382""Create File Server Boot Files" on page 54 to create the STARTUP.NCF and AUTOEXEC.NCF files.ID="FM58382"Create File Server Boot Files idxid="w3443"book="_idx" docset="nw312" tidref="i1269"Create a STARTUP.NCF file idxid="w3444"book="_idx" docset="nw312" tidref="i6489"idxid="w3445"book="_idx" docset="nw312" tidref="i1269"idxid="w3446"book="_idx" docset="nw312" tidref="i4384"A idxid="w3447"book="_idx" docset="nw312" tidref="i6489"STARTUP.NCF file contains commands to load disk drivers and name space support for your file server.This file is executed after SERVER.EXE and is stored on the disk you boot from (hard disk or diskette).Once this file loads disk drivers and name space support and mounts volume SYS:, it turns control over to AUTOEXEC.NCF to complete the boot process.Procedure(Conditional) If you use a boot diskette to boot your file server, make sure the boot diskette is in drive A:.From the "Available System Options" menu, select "Create STARTUP.NCF File." On the "Path For STARTUP.NCF File" screen, enter the proper drive letter.Use <Backspace> to make sure the drive is set toC: if you boot from hard disk.A: if you boot from drive A:.Press <Enter>.A screen similar to the following appears:LBL="2-22"A sample STARTUP.NCF file idxid="w3448"book="_idx" docset="nw312" tidref="i6489"FILE="n312i28a.pbm"The operating system reads the information you previously entered for disk drivers and name space support.Determine your system configuration and, from the following table, decide which idxid="w3449"book="_idx" docset="nw312" tidref="i6489"idxid="w3450"book="_idx" docset="nw312" tidref="i1052"additional commands you would like added to the STARTUP.NCF file. Type one command per line.WIDTH="84"To WIDTH="216"Add these or other commandsWIDTH="84"Load name  spaces for  Macintosh,  OS/2, UNIX, or  FTAMWIDTH="216"LOAD MAC.NAMLOAD OS/2.NAMLOAD NFS.NAMLOAD FTAM.NAM(These commands must precede the command to  mount the volume that stores the files using the  name space.)Set server  parameters(You can add the following seven commands to  the STARTUP.NCF file only. You can add other SET  commands to the STARTUP.NCF and to the  AUTOEXEC.NCF file.)SET Maximum Physical Receive Packet SizeSET Cache Buffer SizeSET Reserved Buffers Below 16 MegSET Maximum Subdirectory Tree DepthSET Concurrent Remirror RequestsSET Auto TTS Backout FlagSET Minimum Packet Receive Buffers(For more on these and other SET parameters, see  "book="sysadmin" docset="nw312"SET" in System Administration, or type "SET" at  the server console.Pause after each  command.PAUSEPress <Esc> to save the file.WIDTH="120"To unload INSTALL utilityWIDTH="192"Press <Esc> until you get the exit prompt.Select "Yes."To keep INSTALL loadedPress <Alt><Esc> to move to a different  console screen.Create an AUTOEXEC.NCF File idxid="w3451"book="_idx" docset="nw312" tidref="i595"idxid="w3452"book="_idx" docset="nw312" tidref="i1269"idxid="w3453"book="_idx" docset="nw312" tidref="i4384"An idxid="w3454"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF file contains commands to complete the boot process after SERVER.EXE and STARTUP.NCF executes.Because AUTOEXEC.NCF is saved in and runs from SYS:SYSTEM, place most boot commands (except the disk driver and name space support commands) in AUTOEXEC.NCF.idxid="w3455"book="_idx" docset="nw312" tidref="i595"idxid="w3456"book="_idx" docset="nw312" tidref="i1052"Commands you can use in AUTOEXEC.NCF do the following:Name the file server.Assign the server's internal network number.Load LAN drivers for the server and assign the network number.Bind LAN drivers to the server's registered protocol.Load other modules you want loaded when the server boots. (See "book="sysadmin" docset="nw312"LOAD" inSystem Administration.)Execute other console commands (such as TRACK ON or VOLUMES) during the boot process.Set other parameters for the server. (See "book="sysadmin" docset="nw312"SET" inSystem Administration.)Mount volumes.ProcedureFrom the "Available System Options" menu, select "Create AUTOEXEC.NCF File."The operating system gathers information you have previously entered at the console prompt for the file.A screen similar to the following appears, showing the commands that are automatically placed in AUTOEXEC.NCF.LBL="2-23"A sample AUTOEXEC.NCF file idxid="w3457"book="_idx" docset="nw312" tidref="i595"FILE="n312i27a.pbm"When using the idxid="w3458"book="_idx" docset="nw312" tidref="i2504"802.3 frame type, rather than the 802.2 default, the screen shown above displays the frame type number.If you load multiple LAN drivers, your AUTOEXEC.NCF file is different. See "book="sysadmin" docset="nw312"INSTALL" inSystem Administration.(Optional) From the table below, choose which of the more common idxid="w3459"book="_idx" docset="nw312" tidref="i4310"idxid="w3460"book="_idx" docset="nw312" tidref="i595"loadable modules to include in AUTOEXEC.NCF.WIDTH="120"ToWIDTH="192"Add these modulesWIDTH="120"Create disk partitions,  create volumes, format a  hard disk, etc.WIDTH="192"LOAD INSTALLLock the file server  console, view network  operation information.LOAD MONITORLoad the print server on  the file server and  establish print services.LOAD PSERVER finance_printCorrect volume  problems or remove  name space entries from  File Allocation and  directory tables.LOAD VREPAIRTo delete or modify commands, backspace to erase the command.(Optional) From your system configuration, choose additional loadable modules to include in AUTOEXEC.NCF.Additional module types are shown in the table below.WIDTH="168"Module TypeWIDTH="144"Module NameWIDTH="168"EquipmentWIDTH="144"UPS.NLMRemote ConsoleREMOTE.NLMRSPX.NLMRemote Boot for Token-RingTOKENRPL.NLMRemote boot for IBM and Western  Digital on EthernetETHERRPL.NLMThird-party loadable modules(See third-party  documentation)If you use an uninterruptible power supply, see "book="sysadmin" docset="nw312"UPS" inSystem Administration for troubleshooting tips.Some loadable modules need other loadable modules to function. If the prerequisite module is not loaded first, the operating system looks at your default drive and then at SYS:SYSTEM and automatically loads the necessary module.From the table below, decide if you want any of the following more common idxid="w3461"book="_idx" docset="nw312" tidref="i595"idxid="w3462"book="_idx" docset="nw312" tidref="i1222"console idxid="w3463"book="_idx" docset="nw312" tidref="i1052"commands to include in AUTOEXEC.NCF.WIDTH="120"ToWIDTH="192"Add these console commandsWIDTH="120"Implement security  measuresWIDTH="192"SECURE CONSOLEDisplay the processor  speedSPEEDFrom the table below, choose idxid="w3464"book="_idx" docset="nw312" tidref="i595"idxid="w3465"book="_idx" docset="nw312" tidref="i1052"idxid="w3466"book="_idx" docset="nw312" tidref="i149"additional commands you would like included in AUTOEXEC.NCF.WIDTH="120"To WIDTH="192"Add these or other commandsWIDTH="120"Mount VolumesWIDTH="192"MOUNT VOL1 (or other volume name)MOUNT ALLNote: Volume SYS: is mounted  automatically when its disk driver is loaded  during the STARTUP.NCF file's execution.Bind protocols other  than IPX to the LAN  drivers.BIND IP to...Set server parameters.SET commands (see "book="sysadmin" docset="nw312"SET" in Utilities  Reference).Pause after each  command.PAUSE(Optional) Decide whether to allow idxid="w3467"book="_idx" docset="nw312" tidref="i4980"idxid="w3468"book="_idx" docset="nw312" tidref="i7071"unencrypted passwords.Use the table on the next page to help you decide.WIDTH="120"ForWIDTH="192"UseWIDTH="120"A new installation with  one file server on the  network.WIDTH="192"Encrypted passwords.Upgrading from  NetWare v2.x operating  system.Encrypted passwords temporarily.NetWare v3.12 file  server running on the  same network as  NetWare v2.11 or earlier.Encrypted passwords permanently.NetWare v3.12 file  server running on the  same network as  NetWare v2.11 or v2.15.Encrypted passwords. Use SET in  AUTOEXEC.NCF until utilities on other file  servers are upgraded.Copy NetWare v3.12 utilities to all  NetWare v2.12 or v2.15 file servers to allow  all servers to use encrypted passwords. (See  "book="sysadmin" docset="nw312"SET" in System Administration.)Type the following command at the console prompt to allow unencrypted passwords: ID="FM43895"SET ALLOW UNENCRYPTED PASSWORDS=ON <Enter>For more information on AUTOEXEC.NCF files or on any of the commands listed above, seebook="sysadmin" docset="nw312"System Administration. Also, see "book="concepts" docset="nw312"Boot Files" inConcepts.Press <Esc> to save the file.Go to IDREF="FM22052""Follow Up After File Server Software Installation" on page 61.ID="FM22052"Follow Up After File Server Software InstallationOnce the STARTUP.NCF and AUTOEXEC.NCF files have been created, complete the following tasks that apply to your network configuration.ProcedureAdd idxid="w3469"book="_idx" docset="nw312" tidref="i3061"idxid="w3470"book="_idx" docset="nw312" tidref="i2640"idxid="w3471"book="_idx" docset="nw312" tidref="i3661"idxid="w3472"book="_idx" docset="nw312" tidref="i149"idxid="w3473"book="_idx" docset="nw312" tidref="i3992"idxid="w3474"book="_idx" docset="nw312" tidref="i149"idxid="w3475"book="_idx" docset="nw312" tidref="i7340"name space support to the volume.If your network includes workstations that use an operating system that supports long filenames, use the ADD NAME SPACE command to add the name space to the volume. At the console prompt, type ADD NAME SPACE name_support TO VOLUME volume_name<Enter>For example, if you have a volume named MAC for Macintosh files, type ADD NAME SPACE MACINTOSH TO VOLUME MAC <Enter>Use this command for every volume that stores files using non-DOS naming conventions.Add Macintosh support.To store Macintosh files and folders on a NetWare v3.12 file server, complete one of the following:Install NetWare for Macintosh (a separate Novell product) on your file server. This product provides native-mode support for Macintosh workstations that connect to the server.Configure your NetWare v3.12 file server as a target server for a NetWare v2.15 server that has NetWare for Macintosh installed. (For more information, see your NetWare for Macintosh documentation.)Lock your file server keyboard.To prevent others from tampering with the file server, load idxid="w3476"book="_idx" docset="nw312" tidref="i3956"MONITOR and select "Lock file server console" from the "Available Options" menu.For additional security tips, see "book="sysadmin" docset="nw312"Secure Console" inSystem Administration.Prepare for idxid="w3477"book="_idx" docset="nw312" tidref="i5127"power fluctuations.If you do not have a idxid="w3478"book="_idx" docset="nw312" tidref="i7097"UPS attached to your file server, be prepared toRun idxid="w3479"book="_idx" docset="nw312" tidref="i7417"idxid="w3480"book="_idx" docset="nw312" tidref="i7237"VREPAIR from either the DOS partition on the hard disk or diskette. Power outages can corrupt the File Allocation and directory tables.Make at least daily backups to protect your data. Power outages can destroy a volume. Make an additional backup of the bindery on a diskette. Sometimes third-party backup devices do not back up the bindery. Run idxid="w3481"book="_idx" docset="nw312" tidref="i697"idxid="w3482"book="_idx" docset="nw312" tidref="i7237"BINDFIX. Power outages can corrupt the bindery. Restore the bindery from a backup if BINDFIX doesn't work.Further customize the configuration.Read about the following commands inSystem Administration:WIDTH="84""book="sysadmin" docset="nw312"INSTALL"WIDTH="228"Performs installation tasks, including creating disk  partitions, creating volumes, formatting a hard disk,  etc."book="sysadmin" docset="nw312"MONITOR"Locks the file server console and shows how  efficiently your network is operating."book="sysadmin" docset="nw312"SET"Displays operating system parameters and  configures the operating system to fit your situation."book="sysadmin" docset="nw312"SPEED"Displays the speed at which the processor is  running."book="sysadmin" docset="nw312"SPOOL"Creates, changes, or displays spooler mappings.Copy NetWare v3.12 Utilities to v2.x Servers idxid="w3483"book="_idx" docset="nw312" tidref="i1251"idxid="w3484"book="_idx" docset="nw312" tidref="i7237"idxid="w3485"book="_idx" docset="nw312" tidref="i4444"This ensures compatibility between NetWare v3.12 servers and v2.1x servers on the same network.Copy NetWare v3.12 utilities to NetWare v2.x servers on your network by following the procedures below.ProcedureLog in to the NetWare v2.x file server.Flag the NetWare v2.x utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, type FLAG *.* N <Enter>Map a drive to volume SYS: on the NetWare v3.12 file server by typing MAP Q:=fileserver/SYS:PUBLIC <Enter>Replace Q with a letter not being used and fileserver with the name of the NetWare v3.12 file server.Enter your username and password for the NetWare v3.12 file server.Make the drive mapped to the NetWare v3.12 file server your default drive.Determine the drive letter for SYS:PUBLIC on the NetWare v2.x file server by typing MAP <Enter>Copy the NetWare v3.12 utilities from the SYS:PUBLIC and SYS:LOGIN directories to the same directories on the NetWare v2.x file server.Flag the NetWare v3.12 utilities on the NetWare 2.x file server Shareable, Read Only by typing FLAG *.* S RO <Enter>Troubleshootingidxid="w3486"book="_idx" docset="nw312" tidref="i6976"idxid="w3487"book="_idx" docset="nw312" tidref="i2599"Hard diskIf you cannot access a hard disk, checkThe cables between the hard disks and the controllers. Ensure Pin 1 of each cable is attached to Pin 1 of each connector.The power cables to make sure they are properly attached.The DCB jumper settings.The addresses of the controllers to ensure that each is valid.Volume errors idxid="w3488"book="_idx" docset="nw312" tidref="i6976"idxid="w3489"book="_idx" docset="nw312" tidref="i7340"If you get disk errors when mounting a volume, check the memory in the file server by loading MONITOR. You should have 20% or more available cache buffers.Communication problems idxid="w3490"book="_idx" docset="nw312" tidref="i6976"idxid="w3491"book="_idx" docset="nw312" tidref="i1064"If the file server can't communicate with the rest of the network, check to see thatEach network board is properly seated.The cable is properly connected.All cabling is properly terminated.The internal network number of the file server does not conflict with other file server internal network numbers or other network addresses.For more help, see "book="sysadmin" docset="nw312"Troubleshooting Guide" inSystem Administration.Where to Go from HereWIDTH="132"ToWIDTH="180"SeeContinue installingIDREF="FM34304"Chapter 3, "Set up the Network" on  page 67.Install cablingThe documentation that comes with  your network boards.Install a print serverbook="print" docset="nw312"Print ServerSet up workstations to run a  remote file server console"book="sysadmin" docset="nw312"Remote Management" in System  Administration.Set up diskless workstationsThe related client manual:book="ws_dos" docset="nw312"Workstation for DOS and Windowsbook="ws_get" docset="nw312"Workstation Basics and Installationbook="ws_os2" docset="nw312"Workstation for OS/2Run NetWare v3.12 Utilities  on a NetWare v2.x serverbook="utilref" docset="nw312"Utilities ReferenceInstall a DOS workstationbook="ws_get" docset="nw312"Workstation Basics and InstallationInstall a Windows  workstationbook="ws_dos" docset="nw312"Workstation for DOS and WindowsInstall an OS/2 workstationbook="ws_os2" docset="nw312"Workstation for OS/2LBL="3"ID="FM34304"Set up the NetworkThis section provides guidelines for planning and creating your network environment, creating your directory structure, setting up users, and providing network security. Make your initial setup simple. Your network will evolve as you find solutions specific to your needs.Record the planning decisions you make on the worksheet found in the back of the manual.Necessary Resources idxid="w3492"book="_idx" docset="nw312" tidref="i4468"To plan and create your network environment, you need the following:A workstation to which you are logged in as SUPERVISOR to create directories and users (see book="ws_get" docset="nw312"Workstation Basics and Installation).Copies of the following worksheets found in the back of the manual:UsersGroupUser DefaultsTrustee Directory SecurityTrustee File SecurityPlan the Directory Structure idxid="w3493"book="_idx" docset="nw312" tidref="i1505"idxid="w3494"book="_idx" docset="nw312" tidref="i5090"Use the "Directory Structure" portion of the Directories Worksheet as you complete this section.The four directories listed on the worksheet (LOGIN, MAIL, SYSTEM, and PUBLIC) are created as a part of installation.As network supervisor, you create additional directories. Some directories, such as idxid="w3495"book="_idx" docset="nw312" tidref="i1638"idxid="w3496"book="_idx" docset="nw312" tidref="i1450"DOS directories, are essential. Others are optional, based on your needs. (See "book="concepts" docset="nw312"Directory Structure" inConcepts.)Planning directory structure is easier when you use a diagram similar to IDREF="FM94098"Figure 3-1.In addition to the four system-created directories in the figure, the tree structure shows directories (in italics) that are created independently.LBL="3-1"ID="FM94098"Directory structure idxid="w3497"book="_idx" docset="nw312" tidref="i1505"FILE="n312i29a.pbm"Plan for System-Created DirectoriesPlan for the following system-created directories (created during installation).idxid="w3498"book="_idx" docset="nw312" tidref="i6614"SYS:LOGIN. Contains programs necessary for logging in.idxid="w3499"book="_idx" docset="nw312" tidref="i6615"SYS:MAIL. Used by mail programs compatible with NetWare.Also contains a subdirectory for each user where user login scripts and print job configurations are stored.User subdirectories are created when you create user login scripts and print job configurations.idxid="w3500"book="_idx" docset="nw312" tidref="i6626"SYS:SYSTEM. Contains operating system files as well as NetWare utilities and programs reserved for the network supervisor.idxid="w3501"book="_idx" docset="nw312" tidref="i6618"idxid="w3502"book="_idx" docset="nw312" tidref="i6683"SYS:PUBLIC. Contains NetWare utilities and programs for users.Plan idxid="w3503"book="_idx" docset="nw312" tidref="i5090"idxid="w3504"book="_idx" docset="nw312" tidref="i1450"Additional DirectoriesDecide which of the following types of directories fit your needs.idxid="w3505"book="_idx" docset="nw312" tidref="i1638"idxid="w3506"book="_idx" docset="nw312" tidref="i1505"DOS directories. Store DOS program files.The number of DOS directories you create depends on the number of workstation brands and DOS versions on your network. (See "book="concepts" docset="nw312"DOS Directories" inConcepts.)idxid="w3507"book="_idx" docset="nw312" tidref="i420"idxid="w3508"book="_idx" docset="nw312" tidref="i1505"Application directories. Store application program files. See your application's documentation. Typically, you plan a directory for each application and other directories to keep data files.If you have two or more volumes, install your applications on a different volume than the data files. You can simplify your daily backups by backing up only on the data volume.You can install an application that must be installed at the root directory level in a subdirectory by mapping a search drive to a fake root. (See "book="utilref" docset="nw312"MAP" inUtilities Reference.)idxid="w3509"book="_idx" docset="nw312" tidref="i7166"idxid="w3510"book="_idx" docset="nw312" tidref="i1505"Username directories. Provide personal work space for users.Plan a parent directory for username subdirectories and private username directories for all users. You may want to limit directory size for these directories.idxid="w3511"book="_idx" docset="nw312" tidref="i7462"idxid="w3512"book="_idx" docset="nw312" tidref="i1505"Work directories. Provide group work space for users rather than using their username directory. Plan a separate directory for each major project.If you have two volumes, we suggest that you install your work directories on the second volume to simplify system backup.idxid="w3513"book="_idx" docset="nw312" tidref="i1063"idxid="w3514"book="_idx" docset="nw312" tidref="i6329"idxid="w3515"book="_idx" docset="nw312" tidref="i1505"Common or shareable directories. Serve as a transfer point for copying files to and from other directories (without having to consider rights).idxid="w3516"book="_idx" docset="nw312" tidref="i665"idxid="w3517"book="_idx" docset="nw312" tidref="i1505"Batch file directories. Store batch files. Use file trustee assignments and file attributes to adjust security.When you have decided on the directory structure you want, record the directory names on the Directories Worksheet. (You may want to sketch a tree structure first to help you visualize the directories. IDREF="FM73266"See Figure 3-2 on page 71.)You complete the rest of this worksheet when you plan security for your directories and files.Directory Structure Example idxid="w3518"book="_idx" docset="nw312" tidref="i1505"File server UNICORN has one volume. The network has both IBM and COMPAQ workstations.The IBM workstations run three versions of DOS, and the COMPAQs run one version of COMPAQ DOS. Four DOS directories are required. The network has word processing, electronic mail, spreadsheet, and database applications. A parent directory, APPS, is planned, along with a subdirectory for each application's program files.The electronic mail program creates its own directory structure.The HOME directory provides personal work space for users in username subdirectories (but disk space is limited since the workstations have hard disks).The ACCTNG directory contains data files for all applications used by the accountants.The PAYROLL directory contains data record files for the payroll database.The network supervisor first diagrammed the directory structure (see IDREF="FM73266"Figure 3-2) and then recorded the directories on the Directories Worksheet (IDREF="FM97489"Figure 3-3).LBL="3-2"ID="FM73266"Directory structure exampleFILE="n312i30a.pbm"LBL="3-3"ID="FM97489"Directories Worksheet idxid="w3519"book="_idx" docset="nw312" tidref="i1505"idxid="w3520"book="_idx" docset="nw312" tidref="i7487"FILE="n312i73a.pbm"Plan Users and Groups idxid="w3521"book="_idx" docset="nw312" tidref="i7193"idxid="w3522"book="_idx" docset="nw312" tidref="i5090"idxid="w3523"book="_idx" docset="nw312" tidref="i2575"Use the Users Worksheet and copies of the Group Worksheet found at the end of the manual as you complete this section.The network supervisor allows people to work on the network by defining them on the file server as users. A user has a username and a user account.To simplify network administration, the network supervisor can define groups of users who use the same applications, perform similar tasks, or who have similar needs for information or printing.When the file server is first brought up, the idxid="w3524"book="_idx" docset="nw312" tidref="i695"idxid="w3525"book="_idx" docset="nw312" tidref="i7173"bindery already contains users SUPERVISOR and GUEST and group EVERYONE.As network supervisor, you define all other users and groups, unless you delegate those responsibilities to a Workgroup Manager. To delegate that responsibility, you can organize workgroups, or you can delegate account management to a User Account Manager without creating a workgroup.For more information, see "book="concepts" docset="nw312"User," "book="concepts" docset="nw312"Group," "book="concepts" docset="nw312"Workgroup Manager," and "book="concepts" docset="nw312"User Account Manager" inConcepts.Plan idxid="w3526"book="_idx" docset="nw312" tidref="i7166"idxid="w3527"book="_idx" docset="nw312" tidref="i5090"UsernamesMake a list of everyone who will work on the network. Decide the username format you will use, such asGiven names (for example, GEORGE or JANENE).Initials and surnames (for example, GELIOT or JGRADY).Surnames (for example, ELIOT or GRADY).If you assign initials and surnames, you are less likely to have problems with duplicate names.idxid="w3528"book="_idx" docset="nw312" tidref="i7166"Usernames can use any valid DOS characters and can be up to 47 characters. However, keep in mind that username directories are still limited to the 8 characters that DOS displays.ID="FM35574"Plan Workgroups (Optional) idxid="w3529"book="_idx" docset="nw312" tidref="i7477"idxid="w3530"book="_idx" docset="nw312" tidref="i5090"Form workgroups (perhaps by organizational divisions) and delegate the tasks of managing accounts or creating users and groups.Each workgroup can be assigned a separate volume or directory. Workgroups can be managed byA Workgroup Manager, who can create new users and manage user accounts within a workgroup.A User Account Manager, who can manage only assigned users' accounts.As IDREF="FM99047"Figure 3-4 on page 75 illustrates, idxid="w3531"book="_idx" docset="nw312" tidref="i6581"SUPERVISOR has all rights to the file server.A idxid="w3532"book="_idx" docset="nw312" tidref="i7470"Workgroup Manager shares those rights but is restricted to a specific area on the file server (a volume or directory, for example).A idxid="w3533"book="_idx" docset="nw312" tidref="i7120"User Account Manager has supervisory rights over only those user accounts assigned by the network supervisor.LBL="3-4"ID="FM99047"Comparing SUPERVISOR and Manager rights idxid="w3534"book="_idx" docset="nw312" tidref="i5944"FILE="n312i32a.pbm"The system is flexible, and you can delegate as much responsibility as seems appropriate.For example, you do not need to create a workgroup to delegate account management. Just assign one or more users to a User Account Manager to manage.Only existing users and groups can be designated managers.For idxid="w3535"book="_idx" docset="nw312" tidref="i3712"idxid="w3536"book="_idx" docset="nw312" tidref="i6980"managers to make trustee assignments, assign them the Supervisory right [S] in a volume or a directory reserved for the workgroup, or in other directories the users need access to.For users created by Workgroup Managers to belong to group EVERYONE, Workgroup Managers must also manage group EVERYONE.If you designate a Workgroup Manager for a workgroup, you must create a user (or a group), designate that user (or group) as Workgroup Manager, and then assign the Workgroup Manager the Supervisory right [S] or all rights to a volume or a directory reserved for the workgroup.The idxid="w3537"book="_idx" docset="nw312" tidref="i5944"Workgroup Manager can then create users and groups for the workgroup. The Workgroup Manager can also manage user accounts and create new workgroup members when needed.Or, to set up the network without assistance, create the users and groups and assign a designated Workgroup Manager to manage those users and groups.The effect is the same as if users and groups had been created by Workgroup Managers, since Workgroup Managers can manage their accounts.Workgroup Managers can create additional users and groups as needed.If you prefer not to delegate the right to create users, create all users and groups and then assign them to User Account Managers (with or without workgroups).To allow the idxid="w3538"book="_idx" docset="nw312" tidref="i7120"idxid="w3539"book="_idx" docset="nw312" tidref="i7120"idxid="w3540"book="_idx" docset="nw312" tidref="i6980"User Account Manager to make trustee assignments, assign the Supervisory right [S] in the volume or directory reserved for the workgroup.For more information, see "book="concepts" docset="nw312"Workgroup Manager" and "book="concepts" docset="nw312"User Account Manager" inConcepts.ID="FM86134"Plan idxid="w3541"book="_idx" docset="nw312" tidref="i2575"idxid="w3542"book="_idx" docset="nw312" tidref="i5090"Groups (Optional)Regular network groups are organized within the pool of users (or within workgroups) to simplify system administration. Groups are created as empty sets, and then members are added. A user can belong to up to 32 groups. Decide which groups to create by considering the following criteria:Applications used. You can plan a group for each application; for example, WPUSERS for a word processing application.Job responsibilities. You can plan groups for shared job responsibilities; for example, PAYCLERK for payroll data entry clerks.Information needs. You can plan groups for shared information and access needs; for example, PAYREAD for users who need to view payroll records but shouldn't modify them.Printing needs. You can plan a group based on the print server, printer, or print queue used; for example, PRIORITY for users assigned to a priority print queue. For more information, see "book="concepts" docset="nw312"Group," "book="concepts" docset="nw312"User," and "book="concepts" docset="nw312"Workgroup Manager" inConcepts.When you have decided who will use the network, the username form you will use, and the groups you need to create, record your planning decisions on the Users Worksheet and the appropriate copies of the Group Worksheet.If you have workgroups, use a separate copy of the Users Worksheet for each workgroup.Select a User Definition UtilityThree utilities allow you to define users: idxid="w3543"book="_idx" docset="nw312" tidref="i6629"idxid="w3544"book="_idx" docset="nw312" tidref="i7237"SYSCON. Use to create users and groups, specify workgroup and user account managers, and to designate trustee assignments.idxid="w3545"book="_idx" docset="nw312" tidref="i3711"idxid="w3546"book="_idx" docset="nw312" tidref="i7237"MAKEUSER. Use to create large groups of users. MAKEUSER is particularly useful if you must regularly create and delete large groups of users.idxid="w3547"book="_idx" docset="nw312" tidref="i7157"idxid="w3548"book="_idx" docset="nw312" tidref="i7237"USERDEF. Use to create a template and then create large groups of users from the template. USERDEF works in conjunction with MAKEUSER.You can create users one at a time in SYSCON after system defaults are set.You can create multiple users by creating and executing a MAKEUSER file (similar to a batch file) or by creating a USERDEF template that defines the parameters for multiple usernames you enter for processing. For the advantages and disadvantages of each utility, see "book="concepts" docset="nw312"Utilities for Creating Users" under "User Account" inConcepts.The setup procedure in this manual is based on creating users with SYSCON. (See IDREF="FM27092""Set Up Users with SYSCON" on page 116.)The User Defaults Worksheet is designed to be used with SYSCON, but can also be used with MAKEUSER and USERDEF.To use " book="utilref" docset="nw312"MAKEUSER" or " book="utilref" docset="nw312"USERDEF," see Utilities Reference to help you plan a MAKEUSER file or a USERDEF template.Users and Groups Example idxid="w3549"book="_idx" docset="nw312" tidref="i7193"idxid="w3550"book="_idx" docset="nw312" tidref="i2575"The network supervisor for file server UNICORN started with a list of users and their job titles, including the following:Susan R. Leiter, vice presidentMary Lynn Graviet, payroll managerGeorge Eliot, supervisor, payroll clerksDarius P. Miner, payroll clerkJudith L. Burns, payroll clerkHoward C. Rask, accounting supervisorJanene M. Grady, accountantJ. S. Bach, accountantGamal H. Beltagi, accountantMarvin O. Ellsworth, accountantThe network supervisor plans to use a combination of initials and surnames for usernames, such as SRLEITERMLGRAVIETGELIOTDPMINERJLBURNSHCRASKJMGRADYJSBACHGHBELTAGIMOELLSWORTHThe following groups will be created, based on applications used, job responsibilities, and information needs.WIDTH="108"SPREADSHEETWIDTH="192"For accountants using a spreadsheet  applicationWPUSERSFor the vice president, manager,  supervisors, and accountantsPAYROLLFor the manager and payroll  supervisorPAYREADFor the vice president and GUEST  (who will be assigned a password)PAYCLERKFor payroll clerks who enter dataThe network supervisor plans to assign the payroll manager as the User Account Manager for all payroll clerks after they are created as users.The entry on the Users Worksheet for Darius P. Miner records the following decisions (directories required for application-based groups are not listed).WIDTH="108"Username:WIDTH="192"DPMINERApplication Used:DatabaseGroups:PAYCLERKAccess to Directories:SYS:HOME\DPMINERSYS:PAYROLLTime Restrictions:M-F 7am-6pmSAT 7am-1pmStation Restrictions:[00001B02757A][32]Managed by:MLGRAVIETOperator or Manager:n/aThe Group Worksheet for WPUSERS records the following decisions.WIDTH="108"Group Name:WIDTH="192"WPUSERSBasis of Group:word processingFull Name:word processing usersManaged by:MLGRAVIETAccess to Directories:SYS:APPS\WPSYS:APPS\WP\SETUPTrustee Directory  Assignments: SYS:APPS\WP [RF]SYS:APPS\WP\SETUP [RWCEMF]Access to Files:n/aTrustee File  Assignments:n/aUsernames of  Members:SRLEITERMLGRAVIETGELIOTHCRASKJMGRADYJSBACHGHBELTAGIMOELLSWORTHDecide Whether to Install Accounting idxid="w3551"book="_idx" docset="nw312" tidref="i106"idxid="w3552"book="_idx" docset="nw312" tidref="i2869"Use the User Defaults Worksheet as you complete this section. Record your decisions about the Accounting feature.You can select Accounting as an option in SYSCON. We suggest that for your initial setup you make only the following decisions: Whether to install Accounting.The initial account balance for users (if you install Accounting).idxid="w3553"book="_idx" docset="nw312" tidref="i106"By installing Accounting, you can automatically use Auditing utilities to tracks how often users log in and out. You can track users without assigning account balances.You can also use Accounting to compute charges for file server services.To determine a charge rate, monitor your file server for two or three weeks. Then set a charge rate based on your costs and the amount you must recover over a fixed period.For suggestions on account balances for users, see "Account Balance" on IDREF="FM64700"page 85.For more information, see "book="utilref" docset="nw312"Accounting" under "SYSCON" inUtilities Reference; see also "book="concepts" docset="nw312"Accounting" inConcepts. On the User Defaults Worksheet, record whether you want to install Accounting. If you do, you can also assign an initial account balance for system defaults.Accounting Example idxid="w3554"book="_idx" docset="nw312" tidref="i106"The network supervisor for file server UNICORN plans to install Accounting to monitor how often users log in and out. No account balance or limits will be assigned.However, after monitoring the file server, the supervisor will also use Accounting to apportion network costs between the accounting and payroll departments.ID="FM47912"Plan Defaults for Users idxid="w3555"book="_idx" docset="nw312" tidref="i106"idxid="w3556"book="_idx" docset="nw312" tidref="i7173"idxid="w3557"book="_idx" docset="nw312" tidref="i5090"Use the Users Worksheet, the User Defaults Worksheet, and copies of the Group Worksheet as you complete this section.You can set system defaults in "Supervisor Options" of SYSCON before you create users and user accounts.You can setDefault Account Balance/Restrictions.Default Time Restrictions.Intruder Detection/Lockout.Users created after the defaults are set have the same user characteristics.You can change account balances and restrictions by resetting defaults when you create additional users, or you can modify individual user accounts after users are created.Even if you define users by creating a MAKEUSER file or a USERDEF template, you can still incorporate the planning decisions you make in SYSCON.Some features, such as station restrictions, must be assigned individually after users are created.Determine Default Account Balance/Restrictions idxid="w3558"book="_idx" docset="nw312" tidref="i106"idxid="w3559"book="_idx" docset="nw312" tidref="i84"idxid="w3560"book="_idx" docset="nw312" tidref="i89""Default Account Balance/Restrictions" in SYSCON displays the following initial settings:LBL="3-5"Default Account Balance/Restrictionsscreen idxid="w3561"book="_idx" docset="nw312" tidref="i84"FILE="n312i33a.pbm"The defaults set no restrictions. For greater security, change the default settings. Each field is explained below.Account Has Expiration Date. To set up temporary accounts, set this to "Yes."Date Account Expires is set by accepting the default (the first day of the next month) or by entering a new date. The account is disabled on the expiration date at 12:01 a.m.Limit Concurrent Connections. To make users log out of one workstation before logging in to another, set this to "Yes." To limit the number of workstations a user can be logged in to, set the Maximum Connections by typing the number of workstations.Create Home Directory for User. To have NetWare create a home directory for users as you create them, set this to "Yes."idxid="w3562"book="_idx" docset="nw312" tidref="i4980"Require Password. We recommend that you require passwords, and that you accept the following defaults which appear when you set this to "Yes":WIDTH="192"Password elementsWIDTH="120"DefaultWIDTH="192"Minimum Password LengthWIDTH="120"5 charactersForce Periodic Password ChangesYesDays Between Forced Changes40Limit Grace Logins (the number of times a  user can log in with an expired password)YesGrace Logins Allowed6Require Unique Passwords (prevents users  from recycling favorite passwords)YesIf you do not want to accept the default on a parameter, enter a new value.ID="FM64700"Account Balance. (Appears only if you install Accounting.) Leave the balance at the default if you do not plan to monitor or charge for file server resources.If no charge rates are set, the account balance is irrelevant. However, when a charge rate is set, the account balance is reduced when the network resource is used.To charge for network resources, assign an initial account balance. We suggest you start with 1,000 units of credit.Determine how much you will charge per month based on connect time, blocks read, or blocks written.When the user works on the network, the balance is reduced according to the charge rate you set for the resource.You can set credit limits before you establish charge rates. The limits do not restrict user accounts until the charge rates are in effect.Allow Unlimited. Credit. The default setting for Allow Unlimited Credit is "No." If charge rates are established, users cannot continue to charge once the balance is depleted. To allow unlimited credit, change the setting to "Yes."If you plan to charge for file server services, you can limit how low the account balance can go by entering a new number (even a negative number) for the "Low Balance Limit."ID="FM32799"Determine idxid="w3563"book="_idx" docset="nw312" tidref="i6777"Default Time RestrictionsFor increased security, specify the hours that users can log in. Time restrictions are set by days of the week in half-hour blocks.LBL="3-6"Default Time Restrictions screenFILE="n312i34a.pbm"For all users to have the same restrictions, assign "Default Time Restrictions" in SYSCON.For individual user restrictions, set time restrictions when you set up each user's account.ID="FM13663"Determine idxid="w3564"book="_idx" docset="nw312" tidref="i2960"Intruder Detection/Lockout idxid="w3565"book="_idx" docset="nw312" tidref="i3375"CapabilitiesFor maximum security, activate "Intruder Detection/Lockout."After an intruder makes several unsuccessful attempts to log in using an incorrect password, the file server locks the intruder out.LBL="3-7"Intruder Detection/ Lockout screenFILE="n312i35a.pbm"Detect Intruders. To activate "Intruder Detection/Lockout," set this field to "Yes."Intruder Detection Threshold. Set the threshold by specifying the number of "Incorrect Login Attempts" the file server accepts before disabling the account. (Default: 7.)"Bad Login Count Retention Time" is the amount of time the file server monitors incorrect login attempts after the last incorrect login attempt was detected. (Default: 30 minutes.)Lock Accounts after Detection. When "Intruder Detection/Lockout" is activated and the threshold for incorrect login attempts is exceeded, the account is locked.The default for " idxid="w3566"book="_idx" docset="nw312" tidref="i80"Length of Account Lockout" is 15 minutes, but you can specify a longer period.SUPERVISOR can unlock disabled accounts. However, the network supervisor needs a back door into the system in case an intruder locks the SUPERVISOR account.See "book="concepts" docset="nw312"SUPERVISOR" inConcepts.After you decide the settings you want to make for "Default Account Balance/Restrictions," "Default Time Restrictions," and "Intruder Detection/Lockout," record your settings on the User Defaults Worksheet.To create users in separate groups or workgroups with different default settings, use a separate copy of the worksheet for each group or workgroup.ID="FM63986"Plan Individual idxid="w3567"book="_idx" docset="nw312" tidref="i80"idxid="w3568"book="_idx" docset="nw312" tidref="i5090"Account FeaturesUse the Users Worksheet and your Group Worksheets as you complete this section.You must set options and restrictions that have no system default. Account restrictions that can be assigned with system defaults can also be assigned individually. You may prefer to add or remove restrictions set with system defaults.When you select a user from the list of existing users, the following menu appears. Each option is explained below.LBL="3-8"User Information screen idxid="w3569"book="_idx" docset="nw312" tidref="i80"FILE="n312i36a.pbm"Account Balance. Appears if you have installed Accounting. If you did not assign a default initial account balance, you can assign account balances and credit limits to users individually.idxid="w3570"book="_idx" docset="nw312" tidref="i89"Account Restrictions. Allows you to set account restrictions if you do not set them as defaults.Or you can define users with system defaults; then after the users have been created, you can modify particular user accounts by adding or removing restrictions.The following form appears when you select "Account Restrictions."LBL="3-9"Account Restrictions screen idxid="w3571"book="_idx" docset="nw312" tidref="i89"FILE="n312i37a.pbm"To set individual user restrictions, modify the default settings shown above. (Disable an account by changing "Account Disabled" to "Yes.")idxid="w3572"book="_idx" docset="nw312" tidref="i89"idxid="w3573"book="_idx" docset="nw312" tidref="i4980"idxid="w3574"book="_idx" docset="nw312" tidref="i947"Change Password. Allows you to assign a password to a user.If you are upgrading or creating multiple users, you can assign the same password to all users in a workgroup and they will be prompted to change their passwords the first time they log in. (Your system is secure only until users know the initial password or the password pattern.)If you assign passwords and require periodic changes to the password, the users are prompted to change their password the first time they log in, once the limits set in the "Account Restrictions" screen have expired.Full Name. Allows you to record a user's full name as it appears on the Users Worksheet.Groups Belonged To. Allows you to assign a user to groups. However, initial network setup is easier if you access the groupname and then assign users as members. (See IDREF="FM27092""Set Up Users with SYSCON" on page 116.)Intruder Lockout Status. (No input is necessary.) Appears only if you activate "Intruder Detection/Lockout" (see IDREF="FM13663"page 87). No input is necessary. Allows you to view a record of unauthorized attempts to log in to a user account.Login Script. After you create users, this allows you to access a user's login script. You can create a login script or copy and modify an existing login script.Managed Users and Groups. Allows you to assign users and their accounts to a User Account Manager. Indicate this in the "Operator or Manager" column of the Users Worksheet.Managers. Allows you to designate a User Account Manager. Record the User Account Manager's username in the "Managed by" column of the Users Worksheet.Other Information. (No input is necessary). Allows you to view the user's ID number, the date and time of the user's last login, and whether the user is designated as a console operator.Security Equivalences. (Optional) Allows you to assign security equivalences to a user. Use caution: A security equivalence gives a user access to the directories and files of another user, so this option is best used to assign rights temporarily.idxid="w3575"book="_idx" docset="nw312" tidref="i6516"idxid="w3576"book="_idx" docset="nw312" tidref="i89"idxid="w3577"book="_idx" docset="nw312" tidref="i89"Station Restrictions. Allows you to restrict the physical locations that a user can log in from.To restrict a user to a particular workstation, you need the network and node (station) addresses for each workstation.For a list of these addresses, see the Workstation Configuration Worksheet. Record the addresses in the "Station Restrictions" column of the Users Worksheet.idxid="w3578"book="_idx" docset="nw312" tidref="i6777"idxid="w3579"book="_idx" docset="nw312" tidref="i89"Time Restrictions. Allows you to set time restrictions for a user in the same way that "Default Time Restrictions" are set (see IDREF="FM32799"page 86).If you restrict time for some users, record the allowable times in the "Time Restrictions column" of the Users Worksheet.idxid="w3580"book="_idx" docset="nw312" tidref="i6980"idxid="w3581"book="_idx" docset="nw312" tidref="i89"Trustee Directory Assignments. Allows you to assign a user as a trustee of a directory.If you specify a directory that does not exist, SYSCON creates the directory. (When possible, make trustee assignments to groups rather than to individual users.)Trustee File Assignments. Allows you to control a user's access to files. (When possible, make trustee assignments in directories rather than to files.)idxid="w3582"book="_idx" docset="nw312" tidref="i7340"idxid="w3583"book="_idx" docset="nw312" tidref="i89"Volume Disk Restrictions. Allows you to limit a user's disk space (in kilobytes) in a volume.LBL="3-10"User Disk Volume Restrictions screenFILE="n312i38a.pbm"When you have decided the settings you want for individual users, record your planning decisions in the appropriate spaces on the Users Worksheet.User Definition Defaults Example idxid="w3584"book="_idx" docset="nw312" tidref="i7173"idxid="w3585"book="_idx" docset="nw312" tidref="i7173"idxid="w3586"book="_idx" docset="nw312" tidref="i7173"The network supervisor for file server UNICORN recorded the following decisions on the User Defaults Worksheet and the Users Worksheet:User accounts have no expiration date.The initial account balance is set to 1,000 units. Unlimited credit is allowed while network use is monitored.Concurrent connections are limited to two workstations."Intruder Detection/Lockout" is activated. The threshold default is accepted; bad login count retention time is set to one hour; and after intruders are detected, user accounts are locked for 12 hours.Passwords are required. Password defaults are accepted.Time restrictions are set individually for payroll clerks and are limited to the hours between 7 a.m. and 6 p.m., Monday through Friday.Station restrictions are set to limit management users to two workstations. Other users are limited to their own workstations.Plan Network Security idxid="w3587"book="_idx" docset="nw312" tidref="i6207"idxid="w3588"book="_idx" docset="nw312" tidref="i5090"idxid="w3589"book="_idx" docset="nw312" tidref="i6207"Use the Directories Worksheet, the Trustee Directory Security Worksheet, and the Trustee File Security Worksheet as you complete this section.Although NetWare security is flexible and can be used in complex ways, we recommend a simple security setup with appropriate security for different kinds of directories and files.You can implement more complex solutions as your network evolves. For a sample security setup, see IDREF="FM46452"page 100.Security for directories and files is controlled by rights and attributes:idxid="w3590"book="_idx" docset="nw312" tidref="i5978"idxid="w3591"book="_idx" docset="nw312" tidref="i6207"Rights security. Applies to users and controls which directories, subdirectories, and files a user can access and what work the user is allowed to do with those directories, subdirectories, and files.idxid="w3592"book="_idx" docset="nw312" tidref="i552"idxid="w3593"book="_idx" docset="nw312" tidref="i6207"Attribute security. Applies to directories, subdirectories, and files and determines whether they can be viewed, modified, shared, renamed, or deleted. Attributes take precedence over rights.Plan Rights Security for Users and Groups idxid="w3594"book="_idx" docset="nw312" tidref="i5978"idxid="w3595"book="_idx" docset="nw312" tidref="i5090"Rights security is controlled by Inherited Rights Masks and trustee assignments.idxid="w3596"book="_idx" docset="nw312" tidref="i2824"idxid="w3597"book="_idx" docset="nw312" tidref="i5978"Inherited Rights Masks. An Inherited Rights Mask is automatically assigned to each directory or file when it is created.For a basic security setup, you do not need to modify the Inherited Rights Mask. For information on the effects of modifying the mask, see "book="concepts" docset="nw312"Security" inConcepts.idxid="w3598"book="_idx" docset="nw312" tidref="i6980"idxid="w3599"book="_idx" docset="nw312" tidref="i5978"Trustee Assignments. When users or groups are granted rights to specific directories or files, the users or groups become trustees of those directories or files.The sum of the rights becomes the trustee assignment.A trustee assignment allows a user or group to use the directory or file in a particular way; for example, only for reading.The network supervisor selects the rights to assign to users or groups in each directory or file.idxid="w3600"book="_idx" docset="nw312" tidref="i6990"idxid="w3601"book="_idx" docset="nw312" tidref="i5978"Trustee Rights. The same trustee rights control access to directories and files in both trustee assignments and Inherited Rights Masks.Each right is represented by an initial letter, and the letters are enclosed in brackets: [SRWCEMFA].Trustee rights are outlined below:LBL="3-1" INLINE="F"Trustee Rights idxid="w3602"book="_idx" docset="nw312" tidref="i6990"WIDTH="84"LetterWIDTH="204"RightWIDTH="84"SWIDTH="204"SupervisoryRReadWWriteCCreateEEraseMModifyFFile scanAAccess controlAs you determine your security needs, consider the following:System-created directories and files. The system automatically makes the trustee assignments and assigns the following to group EVERYONE:PUBLIC [RF]MAIL [C]DOS directories. For DOS directories in SYS:PUBLIC, the system automatically assigns Read and File Scan rights [RF] to group EVERYONE.Application directories. If you create application directories in SYS:PUBLIC, EVERYONE already has Read and File Scan rights [RF] in that directory. If you create a parent directory for applications, assign the File Scan right [F] to group EVERYONE.To the application directories themselves, whether in the parent directory or in volume SYS:, assign Read and File Scan rights [RF] to group EVERYONE or to the groups you formed for application use.If you have an application that creates extra files (such as backup files), assign each user the Create right [C] in the directory where the application creates those files.Home or username directories. Each user needs all rights to personal work space. Assign each user (except GUEST) the Supervisory right [S] in their username directory.To provide personal work space for temporary users in a GUEST directory, assign GUEST the Read, Write, Create, Erase, and Modify rights [RWCEM].Since the GUEST directory provides personal work space, assign the Modify right [M]. (Use caution in assigning GUEST the Access Control [A], Supervisory [S], or Modify [M] rights.)Database directories for data files. If you plan groups based on job responsibilities, make trustee assignments of at least the Read, Write, Create, Erase, and Modify rights [RWCEM] to groups that need to modify data files in database applications.Some database programs require all rights except Supervisory [S]. For groups that need to view information, assign the Read right [R].Work directories. Assign the Read, Write, Create, Erase, and Modify rights [RWCEM] to groups that need to modify data files. For groups that need to view information, assign the Read right [R].Batch file directories. Assign Read and File Scan rights [RF] to group EVERYONE.Examine each directory you listed on the Directories Worksheet. Then follow the decision process below for each directory.Planning Rights Security for Users and GroupsProcedureDecide which groups or users need access to the directory.Decide whether the groups or users need to view the files in the directory for information.Decide whether the groups or users need to modify the files in the directory.Decide what else the groups or users need to do.If you have files you want to make a separate trustee assignment for, repeat the decision process for those files. After you determine rights and trustee assignments, record trustee assignments on the Trustee Directory Security Worksheet.If you assign trustee rights for particular files, record those assignments on the Trustee File Security Worksheet.For more information, see "book="concepts" docset="nw312"Rights Security" and "book="concepts" docset="nw312"Effective Rights" under "Security" inConcepts.Plan Attribute Security for Directories and Files. idxid="w3603"book="_idx" docset="nw312" tidref="i552"idxid="w3604"book="_idx" docset="nw312" tidref="i5090"Attribute security assigns properties to individual directories or files. Some attributes can be assigned to both directories and files, and others only to files.Each attribute is represented by its initial letters, enclosed in brackets.LBL="3-2" INLINE="F"Attribute security properties idxid="w3605"book="_idx" docset="nw312" tidref="i552"WIDTH="84"AttributesWIDTH="36"LetterWIDTH="60"Directory/FileWIDTH="228"DescriptionWIDTH="84"Archive neededWIDTH="36"AWIDTH="60"FWIDTH="228"Identifies files modified after last backup. Assigned  automatically.Copy InhibitCFPrevents Macintosh users from copying a file.  Overrides Read and File Scan rights. Modify right  required to remove this attribute.Delete InhibitDPrevents users from erasing directories or files.  Overrides Erase right. Modify right required to  remove this attribute.Execute OnlyXFPrevents copying or backing up files.Attribute cannot be removed. Assign only to files with  an .EXE or .COM extension (program files).Keep a duplicate of these files in case they become  corrupted and need to be replaced.CAUTION: Some programs do not execute properly  if flagged Execute Only.HiddenHHides directories and files from DOS DIR scans and  prevents them from being deleted or copied. Directories and files appear in NetWare NDIR scan if  user has the File Scan right.IndexedIFAllows large files to be accessed quickly. Automatically  assigned to files with over 64 regular FAT entries. Can  be set, but has no effect.PurgePPurges a file as soon as it is deleted if the file is flagged  with this attribute or if the file resides in a directory  flagged with this attribute.CAUTION: Purged files cannot be recovered with  SALVAGE.Read AuditRaFNot currently used. Can be set, but has no effect.Read  Only/Read  WriteRo/ RwFIndicates whether a file can be modified.All files are automatically flagged Read Write when  they are created and can be modified unless the Read  Only attribute is set.Assigning Ro automatically activates Delete Inhibit  and Rename Inhibit. Modify right required to remove  the Ro attribute.Rename InhibitRPrevents users from renaming directories or files.  Modify right required to remove this attribute.ShareableSFAllows several users to access a file simultaneously.  Usually used in combination with the Read Only  attribute.SystemSyAssign to system files and their directories.Hides these directories and files from DOS DIR scans  and prevents them from being deleted or copied.Directories and files appear in NetWare NDIR scans if  a user has the File Scan right.TransactionalTFActivates the Transaction Tracking System (TTS). Prevents data corruption by ensuring that all changes  are made to files being modified or that none are.  Especially helpful for database files.Write AuditWaFNot currently used. Can be set, but has no effect.Consider the following conditions and recommendations for your idxid="w3606"book="_idx" docset="nw312" tidref="i1523"idxid="w3607"book="_idx" docset="nw312" tidref="i6980"directory trustee assignments.ID="FM13497"idxid="w3608"book="_idx" docset="nw312" tidref="i6683"System-created idxid="w3609"book="_idx" docset="nw312" tidref="i1523"directories and files. These files are flagged Read Only [Ro], Delete Inhibit [D], and Rename Inhibit [R] by the system. No additional attributes are necessary.idxid="w3610"book="_idx" docset="nw312" tidref="i1523"DOS directories. Flag DOS files Read Only/Shareable [RoS]. The system adds the Delete Inhibit [D] and Rename Inhibit [R] flags.Do not confuse [RoS] with [ROS] rights in earlier versions of NetWare.idxid="w3611"book="_idx" docset="nw312" tidref="i1523"Application directories. Flag application program files Read Only/Shareable [RoS].To prevent anyone from copying software illegally, flag the principal executable file of each application Shareable/Execute Only [SX].Not even SUPERVISOR can copy files flagged Execute Only [X]. Files flagged with this attribute can only be deleted. Do not use this file attribute unless you have a backup copy of your application program files.Be sure that neither your license nor the installation program for your application restricts the number of times you can copy the files to the network.idxid="w3612"book="_idx" docset="nw312" tidref="i1523"Database directories for data files. Files to be modified should be flagged Read Write/Shareable [RwS]. (Modify rights are required for files flagged Shareable [S] or Delete Inhibit [D].)If your database contains highly sensitive information that you do not want remaining on the hard disk after it has been deleted, flag the directory Purge [P] so that files in that directory are purged upon deletion. Purged files cannot be recovered.idxid="w3613"book="_idx" docset="nw312" tidref="i1523"Work directories. Files to be read but not modified should be flagged Read Only/Shareable [RoS].ID="FM60533"idxid="w3614"book="_idx" docset="nw312" tidref="i665"Batch idxid="w3615"book="_idx" docset="nw312" tidref="i1523"file directories. Flag the files Read Only/Shareable [RoS]. After you determine file attributes, record those settings on the Directories Worksheet. For more information, see "book="concepts" docset="nw312"Attribute Security" under "Security" inConcepts.ID="FM46452"Security Example idxid="w3616"book="_idx" docset="nw312" tidref="i6207"idxid="w3617"book="_idx" docset="nw312" tidref="i1523"The network supervisor for file server UNICORN planned the following directory trustee assignments:WIDTH="96"User/GroupWIDTH="132"DirectoryWIDTH="72"RightsWIDTH="96"EVERYONEWIDTH="132"SYS:APPSSYS:HOME\GUESTWIDTH="72"[F][RWCSMF]Each userSYS:HOME\username[S]GUESTSYS:HOME\GUEST[RWCEMF]SPREADSHEETSYS:APPS\SPREADSYS:ACCTNG[RF][RWCEMF]WPUSERSSYS:APPS\WPSYS:APP\WP\SETUP[RF][RF]PAYROLLSYS:APPS\DB_APPSYS:PAYROLL[RF][RWCEMF]PAYREADSYS:APPS\DB_APPSYS:PAYROLL[RF][RF]PAYCLERKSYS:APPS\DB_APP[RF]RWCEMF]MJONESSYS:APPS\DB_APPSYS:PAYROLL[S][S]All files are flagged as recommended above.ID="FM59163"Create the Directory Structure idxid="w3618"book="_idx" docset="nw312" tidref="i1505"idxid="w3619"book="_idx" docset="nw312" tidref="i1269"Once the directory structure has been planned, create the directory structure by using either the DOS CD (Change Directory) and MD (Make Directory) commands, or by using the NetWare FILER utility. A brief overview of each option follows.idxid="w3620"book="_idx" docset="nw312" tidref="i1505"idxid="w3621"book="_idx" docset="nw312" tidref="i1638"DOS. For supervisors with DOS experience, the MD and CD commands are direct and efficient.idxid="w3622"book="_idx" docset="nw312" tidref="i2291"idxid="w3623"book="_idx" docset="nw312" tidref="i7237"FILER. FILER is menu-driven so you can select from lists or insert new directory names to create directory structure level by level. See "book="utilref" docset="nw312"FILER" inUtilities Reference.You can use either SYSCON or USERDEF to create user home directories while creating users. A brief overview of each utility follows.idxid="w3624"book="_idx" docset="nw312" tidref="i6629"SYSCON. When you create users and set up user accounts with SYSCON, you can create username directories too.If you specify a directory that does not exist, SYSCON creates the directory. (See IDREF="FM27092""Set Up Users with SYSCON" on page 116.)idxid="w3625"book="_idx" docset="nw312" tidref="i7157"USERDEF. If you create users with USERDEF, USERDEF creates your DOS directories and username directories. (See "book="utilref" docset="nw312"USERDEF" inUtilities Reference.)Install Applications on the NetworkYou can install DOS, Windows, and various types of network applications, such as word processing or spreadsheet programs, and make them available to users.Install DOS and Windows before installing DOS and Windows applications.Install DOS idxid="w3626"book="_idx" docset="nw312" tidref="i1638"idxid="w3627"book="_idx" docset="nw312" tidref="i2869"You can create all DOS directories and load all DOS files from one workstation on the network.If you completed the planning worksheets, you recorded the required DOS directories on the Directories Worksheet. See also "book="concepts" docset="nw312"DOS Directories" inConcepts.As you create DOS directories and copy DOS files onto the network, make sure you comply with all copyright laws. Each workstation must boot with its own licensed copy of DOS or other client operating system.You must have a workstation logged in to the network, running DOS 3.30 or later.ProcedureBoot a workstation.Turn on the workstation. (The file server should be up and running with volume SYS: mounted.) If you have not prepared boot files, create a DOS boot diskette.Log in as SUPERVISOR by typing  LOGIN fileserver\SUPERVISOR <Enter>Replace fileserver with your file server's name.Information from the default login script, similar to the following, appears:LBL="3-11"Default login script example idxid="w3628"book="_idx" docset="nw312" tidref="i3477"FILE="n312i39a.pbm"When you first log in as SUPERVISOR, no password is required. For increased security, assign SUPERVISOR a password in SYSCON when you create users and set up user accounts.For more information on SUPERVISOR account security, see "book="concepts" docset="nw312"SUPERVISOR" inConcepts.Set the idxid="w3629"book="_idx" docset="nw312" tidref="i5599"idxid="w3630"book="_idx" docset="nw312" tidref="i1499"prompt.You are in the SYS:LOGIN directory. If your prompt does not display the directory path, type  PROMPT $P$G <Enter>Change to the SYS:PUBLIC directory.Create a directory in SYS:PUBLIC for each workstation type and each version of DOS users will need.Name your directories according to the following convention:  SYS:PUBLIC\machine\os_type\os_versionFor each directory, replace machine with the six-letter machine name of the workstation (such as IBM_PC or COMPAQ).Replace os_type with the type of DOS you are using (such as MSDOS or DRDOS). Replace os_version with the DOS version number.These variables correspond to login script variables that you can use for mapping drives in login scripts (IDREF="FM84335"see Step 9).For example, to install MSDOS 5.0 on an IBM PC, go to SYS:PUBLIC to create the DOS subdirectory. To use the DOS MD command, type the commands shown below (in order):  MD IBM_PC <Enter>  CD IBM_PC <Enter>  MD MSDOS <Enter>  CD MSDOS <Enter>  MD 50 <Enter>  CD 50 <Enter>ID="FM35348"Load DOS.Follow the instructions in the DOS documentation to load the DOS software into the directories you created.ID="FM56704"Flag DOS files Read Only/Shareable idxid="w3631"book="_idx" docset="nw312" tidref="i1638"You must flag all DOS files to prevent users from corrupting the command files.  FLAG *.* RO S <Enter>Repeat IDREF="FM35348"Steps 6 and IDREF="FM56704"7 for each DOS directory you create.ID="FM84335"In the system login script, map the second search drive to the DOS directory.For an explanation of login scripts, see IDREF="FM34948"Chapter 4, "Create Login Scripts," on page 135.The first search drive should be mapped to the PUBLIC directory so that users can access NetWare utilities.If all users have the same types of computers and are using the same version of DOS, you probably only need one DOS directory.In this case, add a line similar to the following, substituting the correct directory names:  MAP S2:=SYS:PUBLIC\%MACHINE\%)S_VERSIONFor the %MACHINE variable to work, make sure the long machine type is set in each station's NET.CFG file. For example, a station might have the following line in its NET.CFG file:  LONG MACHINE TYPE = IBM-PCAdd idxid="w3632"book="_idx" docset="nw312" tidref="i1104"COMSPEC to the system login script.Following is the proper syntax for the COMSPEC command:  COMSPEC=Y:COMMAND.COMThis command tells the workstation where to find the command processor.WIDTH="120"For more information aboutWIDTH="192"SeeWIDTH="120"Loading DOS on the  networkWIDTH="192"The DOS manual that came with your  software.Login scriptsIDREF="FM34948"Chapter 4, "Create Login Scripts," on  page 135.Mapping search drivesIDREF="FM99801""MAP" on page 166.Running DOS on a  workstationbook="ws_dos" docset="nw312"Workstation for DOS and Windows.Install Microsoft Windows (Optional) idxid="w3633"book="_idx" docset="nw312" tidref="i7443"idxid="w3634"book="_idx" docset="nw312" tidref="i2869"You can install Windows onto a network in several ways:Install all Windows files on a user's local hard drive.Install Windows program files on the server, and user files on local hard drives.Install all Windows program and user files on the server.In most cases, this installation provides the easiest maintenance and most efficient use of resources.Instructions for the first two options are included in the documentation that came with your Windows software. Instructions for installing program and user files on the server are included in this section.The following table points out some of the advantages and disadvantages of having Windows files installed on the server.WIDTH="156"AdvantagesWIDTH="156"DisadvantagesWIDTH="156"Program and configuration files  are backed up and secure.WIDTH="156"Causes more network traffic.No hard disk is required on the  user workstation..INI and driver files for all users  can be updated from one  location.Configuration files always match  hardware.Files Needed for NetWare to Function with Windows idxid="w3635"book="_idx" docset="nw312" tidref="i7443"The following files are needed for NetWare to function with Windows. These files are shipped with Windows.WIDTH="96"FileWIDTH="216"FunctionWIDTH="96"NETWARE.DRVWIDTH="216"NetWare device driver. Contains executable code  for NetWare-related functions.NETWARE.HLPHelp file for NETWARE.DRV.NETWARE.INIInitialization file for NETWARE.DRV and other  NetWare Windows utilities. Automatically created  by NETWARE.DRV.NWPOPUP.EXEHandler for broadcast messages.VNETWARE.386Virtual NetWare device driver. Performs  virtualization among sessions when Windows is in  386 Enhanced mode.VIPX.386Virtual IPX device driver. Virtualizes IPX  communications among sessions when Windows  is in 386 Enhanced mode.These files allow you to connect network drives through the File Manager and to connect network printers through the Printers icon in the Control Panel.To provide users with a single point of access to networking functionality, install the NetWare User Tools as explained in "book="ws_get" docset="nw312"Using Workstation Tools," Chapter 6 in book="ws_get" docset="nw312"Workstation Basics and Installation.Guidelines for Running Windows from the Network idxid="w3636"book="_idx" docset="nw312" tidref="i7443"Use a permanent swap file on a local hard drive if possible; do not use network directories for swap files. If a local swap file is not possible, consider increasing RAM to a minimum of 8 MB.RAM plus swap file size should be a minimum of 10 MB.Remove Windows search drives from the workstation AUTOEXEC.BAT file.If users are running DR DOS, make sure DR DOS files are dated 07 April 1992 or later.If users are running DR DOS, make sure their CONFIG.SYS files install EMM386.SYS and configure it for use with Windows.For configuration information, see your DR DOS manual or DR DOS online help.Installing and Setting Up Microsoft Windows idxid="w3637"book="_idx" docset="nw312" tidref="i7443"idxid="w3638"book="_idx" docset="nw312" tidref="i2869"idxid="w3639"book="_idx" docset="nw312" tidref="i6310"PrerequisitesA workstation logged in to the network, running DOS 3.30 or later.The Supervisor or Create right to the directory where you are loading Windows.A licensed network copy of Windows 3.1 or later.16 MB of available disk space.A NetWare Workstation for DOS/Windows kit.ProcedureInstall Windows server softwareUse SETUP /A option. For information about Windows SETUP options and installation, see the documentation that came with your Windows software.Create a group for users who will run Windows.For instructions on creating groups, IDREF="FM45524"see Step 4 on page 119.Make the Windows Group a trustee of the Windows directory.For instructions on granting trustee assignments, IDREF="FM28388"see Step 6 on page 122.Create a directory for each user to store user-specific Windows files.WIN.COM and files such as .GRP and .INI files are stored here.Add the following information to the idxid="w3640"book="_idx" docset="nw312" tidref="i3513"system login script.For an explanation of login scripts, see IDREF="FM34948"Chapter 4, "Create Login Scripts," on page 135.An example of the syntax used for these login script entries appears at the end of this step.Map a drive to the user-specific directories for the Windows group.Map a search drive to the Windows directory for the Windows group.Set the Windows TEMP directory to a subdirectory of the user directory.The following example shows the system login script entries you add to set up Windows on the network:  IF MEMBER OF "WIN31" THEN  MAP INS P:=SYS:USERS\%LOGIN_NAME\WIN31  MAP INS S16:=SYS:APPS\WINAPPS\WIN31  SET TEMP = "P:\USERS\%LOGIN_NAME\WIN31\TEMP"  ENDSet up the workstations by completing the following:Change to the search drive mapped to the Windows directory.Enter the drive letter only.Modify the user idxid="w3641"book="_idx" docset="nw312" tidref="i593"AUTOEXEC.BAT and idxid="w3642"book="_idx" docset="nw312" tidref="i1130"CONFIG.SYS files by typing:  SETUP /N <Enter>Select the "Custom" option to make sure environmental variables are correct. When Windows prompts for a path during setup, enter the drive letter instead of the path.Install NetWare Tools.idxid="w3643"book="_idx" docset="nw312" tidref="i4203"idxid="w3644"book="_idx" docset="nw312" tidref="i6851"NetWare Tools provide a single point of access for common network tasks such as mapping drives, connecting printers, and sending messages.To install NetWare User Tools and update NetWare-specific files in the Windows directory, follow the procedures in "book="ws_get" docset="nw312"Preparing to Install Workstation Software," Chapter 2 in Workstation Basics and Installation.WIDTH="120"ToWIDTH="192"SeeWIDTH="120"Create login scriptsWIDTH="192"IDREF="FM34948"Chapter 4, "Create Login Scripts," on  page 135.Install Windows on the  networkThe Windows manual that came with your  software.Map search drivesIDREF="FM99801""MAP" on page 166.Run Windows on a  workstationbook="ws_dos" docset="nw312"NetWare Workstation for DOS and Windows.Install Other Applications idxid="w3645"book="_idx" docset="nw312" tidref="i424"idxid="w3646"book="_idx" docset="nw312" tidref="i2869"When loading applications, keep the following in mind:You need the Create right in the directory where you install the application.Make sure the application is designed for network (multi-user) use, and that you observe licensing restrictions on the number of users who can access the application.To allow users to access network-based applications, map search drives to the directories that contain these applications.To make sure these search drives are permanent, place them in login scripts, which are executed when users log in.If the application requires that it be installed at the root of a volume, but you would rather install it in a subdirectory for security reasons, map the directory to a fake root. (See IDREF="FM99801""MAP" on page 166.)ProcedureInstall application program files and set file attributes.To use third-party applications (such as word processing, spreadsheet, and database programs), install the program files into the directories you created for them.Refer to the documentation for each application.After files are installed into their directories, set file attribute security.For applications with network versions. If the third-party documentation includes instructions for loading the application on a network, follow those instructions. Then skip to IDREF="FM24202"Step 2 on page 112.For non-network applications. If the documentation does not contain instructions for loading the application on a network, try the instructions for loading the application on a local hard disk. Some hard disk load commands don't work on network drives. If this is the case, consult the dealer who sold you the application.Some applications have an install program that requires the program to be installed in a root directory (represented by the volume name in NetWare). NetWare allows you to map a fake root.For more information, see "book="utilref" docset="nw312"MAP" inUtilities Reference.idxid="w3647"book="_idx" docset="nw312" tidref="i3731"Map the drive letter that normally corresponds to a local hard disk to the directory you created for the application.If you use local hard disk instructions, check to see whether the program requires the hard disk drive letter to be C: or D:.For example, suppose you created a directory for an application in SYS:PUBLIC.If the third-party documentation instructs you to copy the files to C:, type the following at the DOS prompt:  MAP ROOT C:=SYS:PUBLIC\directory<Enter>The following message appears:LBL="3-12"MAP messageFILE="n312i40a.pbm"Press <Enter> to confirm.Continue with the instructions in the third-party documentation for installing files on a hard disk, or insert each third-party diskette into drive A: and type  COPY A:*.* C: <Enter>idxid="w3648"book="_idx" docset="nw312" tidref="i2446"idxid="w3649"book="_idx" docset="nw312" tidref="i5753"idxid="w3650"book="_idx" docset="nw312" tidref="i6329"Flag the application program files Read Only/Shareable.The default file attribute is Read Write. Use FLAG or FILER to change the file attributes of application files to Read Only/Shareable [RoS].This prevents users from deleting or corrupting the program files (.EXE or .COM files).When you flag a file Read Only, NetWare assigns the Delete Inhibit and Rename Inhibit attributes. (See "book="concepts" docset="nw312"Attribute Security" under "Security" inConcepts.) Type  FLAG *.* RO S <Enter>ID="FM24202"Copy necessary files onto the workstation boot diskettes.Check the third-party documentation to see if the application modifies or creates a CONFIG.SYS or an AUTOEXEC.BAT file. If so, put those files on each user's boot diskette.Copy data files into directories.Load data files into the directories you created for them.To copy data files, insert each diskette into drive A: and type  NCOPY A:*.* pathReplace path with the directory path to the application directory (or if you mapped the directory to a drive, the drive letter).(Optional) Use idxid="w3651"book="_idx" docset="nw312" tidref="i2440"idxid="w3652"book="_idx" docset="nw312" tidref="i2291"idxid="w3653"book="_idx" docset="nw312" tidref="i556"FLAG or idxid="w3654"book="_idx" docset="nw312" tidref="i7237"FILER to assign file attribute security.For more information, see "book="utilref" docset="nw312"FLAG" or "book="utilref" docset="nw312"FILER" inUtilities Reference.(Optional) ID="FM34103"Restrict disk space in directories. idxid="w3655"book="_idx" docset="nw312" tidref="i2599"idxid="w3656"book="_idx" docset="nw312" tidref="i1450"Some DOS applications do not function well if they are in a large volume. Use idxid="w3657"book="_idx" docset="nw312" tidref="i1751"DSPACE to limit the application directory's size.You may also want to limit user space on the file server. With limited space, users may not be tempted to keep copies of applications in their own directories.ID="FM35799"Determine the directory size by typing  CHKDIR path<Enter>Replace path with the path of the directory you want to check. (You do not need to specify a path if the directory is your current directory.)For example, if you specify SYS:PUBLIC, information similar to the following appears:LBL="3-13"Directory Space Limitation screenFILE="n312i46a.pbm"In this example, SYS:PUBLIC uses less than 3,500 kilobytes of disk space.At the prompt, type  DSPACE <Enter>Select "Directory Restrictions" from the "Available Topics" menu.The current directory appears in the entry box for "Directory for Space Restriction Information."LBL="3-14"Directory for Space Restriction screenFILE="n312i47a.pbm"Enter the directory path for the directory you want to restrict.If you know the directory path. Type the directory path in the entry box, or use the <Backspace> key to delete the current directory path and type the directory path you want.If you do notknow the directory path. Press <Ins> and select the directory path one level at a time beginning with the list of "Network Directories." When you have selected the directory path, press <Esc>.Press <Enter> to access a "Directory Disk Space Limitation Information" form similar to the following.LBL="3-15"Directory Disk Space Limitation screenFILE="n312i48a.pbm"Change the "Limit Space" field to "Yes"; then press <Enter>.The default limitation for disk space is 1,024 kilobytes.If this amount is satisfactory, press <Esc> and skip to IDREF="FM13703"Steps 5h.To change the amount, use the Down-arrow key to move to the "Directory Space Limit" field. ID="FM60424"Specify the maximum disk space in kilobytes by typing in a number; then press <Enter>.For an application directory. When you have loaded the application files, add a comfortable margin to the number in use for the directory.Use the sum as the upper limit (in kilobytes) for the directory to use.For a username directory. Determine the total amount of disk space (in kilobytes) you can allow users for personal work space.Divide this number by the total number of users; the result is the amount of disk space you can allow for each user.Limit each username directory to that amount. (Otherwise, the volume will run out of disk space before all users use up their allocations.)ID="FM13703"Repeat IDREF="FM35799"Steps 5a through IDREF="FM60424"5g for every directory you want to restrict.Press <Esc> to exit DSPACE.WIDTH="120"ToWIDTH="192"SeeWIDTH="120"Create login scriptsWIDTH="192"IDREF="FM34948"Chapter 4, "Create Login Scripts," on  page 135.Map search drives and  fake roots in login scriptsIDREF="FM99801""MAP" on page 166.ID="FM27092"Set Up Users with SYSCON idxid="w3658"book="_idx" docset="nw312" tidref="i6629"idxid="w3659"book="_idx" docset="nw312" tidref="i6310"The procedures below outline the steps to setting up users and groups using SYSCON.At the prompt, type  SYSCON <Enter>idxid="w3660"book="_idx" docset="nw312" tidref="i6647"idxid="w3661"book="_idx" docset="nw312" tidref="i6310"idxid="w3662"book="_idx" docset="nw312" tidref="i6629"idxid="w3663"book="_idx" docset="nw312" tidref="i7173"idxid="w3664"book="_idx" docset="nw312" tidref="i106"idxid="w3665"book="_idx" docset="nw312" tidref="i2869"idxid="w3666"book="_idx" docset="nw312" tidref="i6629"(Optional) Install Accounting.Accounting is optional. However, you must install Accounting to assign an account balance to users when you set system defaults. You can also use Auditing utilities to monitor how often users log in and out. Later you can choose which additional Accounting functions are suitable for your network.To help determine whether to install Accounting, see "book="utilref" docset="nw312"Accounting" under "SYSCON" inUtilities Reference; see also "book="concepts" docset="nw312"Accounting" inConcepts.Select "Accounting."The first time you select "Accounting" from the "Available Topics" menu, the "Install Accounting" box appears. Select "Yes."idxid="w3667"book="_idx" docset="nw312" tidref="i6629"Set system defaults for users.Use the User Defaults Worksheet as your guide in setting up system default restrictions in SYSCON.If you did not complete the planning worksheets and need help determining the value to set for each parameter, IDREF="FM47912"see "Plan Defaults for Users" on page 83; see also "book="concepts" docset="nw312"Users" inConcepts.System default restrictions are assigned to users as they are created. However, default restrictions are set up initially so that no password or time restrictions apply.Unless you change the default restrictions, users will have no password, login, account restrictions, or time restrictions.Changes to system defaults affect only user accounts created after the changes are made. Existing user accounts are not affected.There are no default station restrictions. These must be established individually because users are restricted to specific workstations.Select "Supervisor Options" from the "Available Topics" menu.The "Supervisor Options" menu appears.Select idxid="w3668"book="_idx" docset="nw312" tidref="i84"idxid="w3669"book="_idx" docset="nw312" tidref="i89""Default Account Balance/Restrictions."If you installed the Accounting feature, the "Account Balance" field appears.LBL="3-16"Default Account Balance/RestrictionsscreenFILE="n312i33a.pbm"Enter the restrictions for your network.Select "Default idxid="w3670"book="_idx" docset="nw312" tidref="i6777"Time Restrictions" in the "Supervisor Options" menu.Time is specified in half-hour blocks. To prevent users from logging in during a time block, delete the corresponding asterisk.LBL="3-17"Default Time Restrictions screenFILE="n312i34a.pbm"Select "Intruder idxid="w3671"book="_idx" docset="nw312" tidref="i2960"idxid="w3672"book="_idx" docset="nw312" tidref="i3375"idxid="w3673"book="_idx" docset="nw312" tidref="i947"idxid="w3674"book="_idx" docset="nw312" tidref="i947"Detection/Lockout" in the "Supervisor Options" menu and change the setting so the system detects intruders.You must also set the threshold for intruder detection and specify the length of time an account should be locked after an intruder is detected.LBL="3-18"Intruder Detection/ Lockout screenFILE="n312i35a.pbm"For more information on setting these restrictions, see "book="utilref" docset="nw312"SYSCON" inUtilities Reference.Press <Esc> to go to the "Available Topics" menu.ID="FM45524"Create groups idxid="w3675"book="_idx" docset="nw312" tidref="i2575"idxid="w3676"book="_idx" docset="nw312" tidref="i1269"idxid="w3677"book="_idx" docset="nw312" tidref="i6629"Use the Trustee Directory Security Worksheet, Trustee File Security Worksheet, and Group Worksheet when creating groups. (Users can be added to a group only after both the users and the group have been created.)If you did not complete the planning worksheets and need help determining the groups to create, IDREF="FM86134"see "Plan Groups (Optional)" on page 77; see also "book="concepts" docset="nw312"Groups" and "book="concepts" docset="nw312"Users" inConcepts.If you plan to designate a Workgroup Manager to create users and groups for the workgroup, consider creating only those groups that apply across workgroup boundaries (for example, a group based on an application used by more than one workgroup).On the other hand, if you plan to designate a group as Workgroup Manager to create users and groups for the workgroup, create the Workgroup Manager group when you create system-wide groups.In this case, assign the Supervisory right [S] in a volume or a directory reserved for the workgroup to the Workgroup Manager group.Select "Group Information" from the "Available Topics" menu.A list of existing groups appears. If no groups have been created, group EVERYONE is the only group on the list.Press <Ins>, type the name of the new group in the entry box, and press <Enter>.LBL="3-19"Create a Group screenFILE="n312i49a.pbm"Select the group you just created.Select "Full Name" from the "Group Information" menu. Type the full name of the group in the entry box and press <Enter>.LBL="3-20"Group Full Name screenFILE="n312i50a.pbm"You are returned to the "Group Information" menu.ID="FM79141"Assign idxid="w3678"book="_idx" docset="nw312" tidref="i6990"idxid="w3679"book="_idx" docset="nw312" tidref="i6629"trustee rights.To assign trustee rights for the group in a particular directory, select "Trustee Directory Assignments" from the "Group Information" menu.The "Trustee Directory Assignments" list appears. Press <Ins>.An entry box appears.LBL="3-21"Directory Trustee Assignment screenFILE="n312i51a.pbm"Enter the complete directory path.If you know the complete directory path. Type the name of the directory you want the group to have trustee rights in. (Type the complete directory path.) Then press <Enter>.If you do notknow the directory path. You can specify the directory path one level at a time.Press <Ins> and then select volume, directory, subdirectory, and so on. When the directory path appears in the box, press <Esc> and then <Enter>.The directory appears in the list of "Trustee Directory Assignments" with the default trustee rights, Read and File Scan [RF].To add rights, press <Enter>.The "Trustee Rights Granted" list appears.LBL="3-22"Trustee Rights Granted screenFILE="n312i52a.pbm"Press <Ins> to view the list of trustee rights not granted.Select the rights you want to grant from this list.LBL="3-23"Trustee Rights Not Granted screenFILE="n312i53a.pbm"To add a trustee right, select the trustee right you want. To add more than one trustee right, mark each right using the Mark key (<F5> on most machines). Then press <Enter>.The trustee directory right or rights you granted now appears on the list of "Trustee Rights Granted." Press <Esc>.Repeat IDREF="FM45524"Steps 4 through IDREF="FM79141"5 to create additional groups and assign their trustee directory rights.ID="FM28388"Assign trustee file rights. idxid="w3680"book="_idx" docset="nw312" tidref="i6990"idxid="w3681"book="_idx" docset="nw312" tidref="i6629"Use the Trustee File Security Worksheet to remind you what trustee file rights you planned to assign to each group.ID="FM80205"To assign trustee rights for the group in a particular file, select "Trustee File Assignments" in the "Group Information" menu.The "Trustee File Assignments" list appears.Press <Ins>.An entry box appears.LBL="3-24"Select a Directory screenFILE="n312i54a.pbm"Enter the directory path.If you know the directory path. Type the name of the directory that contains the file you want the group to have trustee rights in. (Type each level of the directory path.) Then press <Enter>.If you do notknow the directory path. You can specify the directory path one level at a time.Press <Ins> and then select volume, directory, subdirectory, and so on. When the directory path appears in the box, press <Esc> and then <Enter>.Select the filename.LBL="3-25"Select a File screenFILE="n312i55a.pbm"If you know the filename. Type the filename you want the group to have trustee rights to. Then press <Enter>.If you do notknow the filename. Press <Ins> and select the filename from the list that appears. Press <Enter> again.The filename appears in the list of "Trustee File Assignments" with the default trustee rights, Read and File Scan [RF].To grant additional rights, press <Enter>.The "Trustee Rights Granted" list appears.LBL="3-26"Trustee Rights Granted screenFILE="n312i52a.pbm"Press <Ins> to view the trustee rights not granted.ID="FM41937"Select additional rights to grant from this list.LBL="3-27"Trustee Rights Not Granted screenFILE="n312i53a.pbm"To add a trustee right, select a trustee right from the list. To add more than one trustee right, mark the rights you want to add using the Mark key (<F5> on most machines). Then press <Enter>.The trustee file rights you grant appear on the "Trustee Rights Granted" list. Press <Esc>.Repeat IDREF="FM80205"Steps 6a through IDREF="FM41937"6g for each file to which you want to assign trustee rights for a particular group.idxid="w3682"book="_idx" docset="nw312" tidref="i7173"idxid="w3683"book="_idx" docset="nw312" tidref="i7173"idxid="w3684"book="_idx" docset="nw312" tidref="i1269"idxid="w3685"book="_idx" docset="nw312" tidref="i6310"Create users and set up user accounts.Use the Users Worksheet as a guide for creating users and setting up their accounts.You can also use the Trustee Directory Security Worksheet and the Trustee File Security Worksheet to help you make trustee assignments to users.See the Group Worksheets you completed to assign users to their respective groups.To delegate the responsibility of creating users and groups to Workgroup Managers, first create Workgroup Managers.To designate a user as a idxid="w3686"book="_idx" docset="nw312" tidref="i7470"Workgroup Manager. Create the user and assign the Supervisory right [S] in a volume or a directory reserved for the workgroup. Then skip to IDREF="FM75130"Step 11 on page 131.The Workgroup Manager can create users and groups for the workgroup.To designate a group as a idxid="w3687"book="_idx" docset="nw312" tidref="i7470"Workgroup Manager. Create the group and the users you plan to assign to the group. Assign the users as members of the group.Assign the group the Supervisory right [S] in a volume or a directory reserved for the workgroup. Then skip to IDREF="FM75130"Step 11 on page 131.The members of the group can now create users and groups for the workgroup.Select "User Information" from the "Available Topics" menu.A "User Names" list appears, similar to the following. (If no users are created, the list contains GUEST and SUPERVISOR.)LBL="3-28"User Names screenFILE="n312i56a.pbm"ID="FM12818"Press <Ins> to add a name to the list.Type a username from the list of users you plan to create.LBL="3-29"Create a User screenFILE="n312i57a.pbm"Press <Enter>.The username appears in the "User Name" list.ID="FM11351"If you have set the system to create a home directory for each user, enter the directory path where all home directories are stored (SYS:HOME, for example).LBL="3-30"Create User's Home Directory screenFILE="n312i58a.pbm"If you did not set the system to create a home directory, the screen above does not appear.Repeat IDREF="FM12818"Steps 7b through IDREF="FM11351"7e for each user.ID="FM75943"idxid="w3688"book="_idx" docset="nw312" tidref="i89"idxid="w3689"book="_idx" docset="nw312" tidref="i4980"idxid="w3690"book="_idx" docset="nw312" tidref="i6516"idxid="w3691"book="_idx" docset="nw312" tidref="i6777"Assign password, station, and time restrictions to users.You must set those options and restrictions for which no system default applies.If you did not set restrictions at the system level (such as time restrictions), you can set them to apply to particular users.If you set system defaults, you can remove or assign them for users by selecting options on the "User Information" menu:LBL="3-31"User Information menu idxid="w3692"book="_idx" docset="nw312" tidref="i80"FILE="n312i36a.pbm"ID="FM56537"Select the new username in the "User Names" list.Highlight an option and enter the necessary information.Refer to the User Defaults Worksheet to make the settings you planned.A brief explanation of the options in the "User Information" menu, IDREF="FM63986"see "Plan Individual Account Features" on page 88.ID="FM65300"After you set the options on the "User Information" menu, press <Esc> to return to the "User Names" list.Repeat IDREF="FM56537"Steps 8a through IDREF="FM65300"8c for each user.Create a idxid="w3693"book="_idx" docset="nw312" tidref="i7166"idxid="w3694"book="_idx" docset="nw312" tidref="i1269"username directory for each user.If you have not created user directories, follow these instructions to create a directory for each user and assign all trustee rights in that directory.You can also use these steps to give directory trustee assignments to users in directories other than their home directories.To limit disk space after you create the directories, follow the instructions under IDREF="FM34103"Step 5 on page 113.ID="FM98291"Select the user in the "User Names" list.Select "Trustee Directory Assignments" from the "User Information" menu.The "Trustee Directory Assignments" window appears.Press <Ins>.The following entry box appears:LBL="3-32"Directory Trustee Assignment screenFILE="n312i51a.pbm"For the user you selected, type the complete directory path of the username directory (or directory to make the assignments in). Then press <Enter>.For example, to create the user's username directory in SYS:HOME, type  SYS:HOME\username<Enter>The following box appears:LBL="3-33"Verify Creation of New Directory screenFILE="n312i59a.pbm"Select "Yes."Press <Enter> to display the "Trustee Rights Granted" in the directory.LBL="3-34"Trustee Rights Granted screenFILE="n312i52a.pbm"Default trustee rights are Read and File Scan [RF].Press <Ins> to display the trustee rights not granted.LBL="3-35"Trustee Rights Not Granted screenFILE="n312i53a.pbm"Select "Supervisory" to assign the user all rights in the username directory.The Supervisory right is now displayed in the "Trustee Rights Granted" list.ID="FM35194"Press <Esc> until you return to the "User Names" list.Repeat IDREF="FM98291"Steps 9a through IDREF="FM35194"9i to create a username directory for each user and to assign the Supervisory right.ID="FM79236"Add idxid="w3695"book="_idx" docset="nw312" tidref="i7173"idxid="w3696"book="_idx" docset="nw312" tidref="i149"users to groups.Use the Group Worksheet you completed for each group as a guide when assigning users to a group. Remember that a user can be assigned to a maximum of 32 groups.Press <Esc> until you return to the "Available Topics" menu.Select "Group Information." A "Group Names" list similar to the following contains the names of the groups you created:LBL="3-36"Group Names screenFILE="n312i60a.pbm"ID="FM11591"Select the group you want to add members to.A "Group Information" menu appears for that group.LBL="3-37"Group Information screenFILE="n312i61a.pbm"Select "Member List." The "Group Members" list appears.LBL="3-38"Group Members screenFILE="n312i62a.pbm"Press <Ins> to view a list of users who are not members of the group.LBL="3-39"Non-Group Member users screenFILE="n312i63a.pbm"ID="FM43979"From the list, select the users you want as members of the group.To add a member, select the user you want.To add more than one member, mark each user with the Mark key (<F5> on most machines). Then press <Enter>.The users you added to the group appear in the "Group Members" list.If you have more groups to fill, press <Esc> to return to the "Group Names" menu.Repeat IDREF="FM11591"Steps 10c through IDREF="FM43979"10f for each group you created. To designate Workgroup Managers or User Account Managers, press <Esc> to return to the "Available Topics" menu.To designate a Workgroup Manager, continue with IDREF="FM75130"Step 11; to designate a User Account Manager, skip to IDREF="FM89085"Step 12.(Optional) ID="FM75130"Designate a Workgroup Manager.For planning information, IDREF="FM35574"see "Plan Workgroups (Optional)" on page 74.Select "Supervisor Options" from the "Available Topics" menu.Select "Workgroup Managers" from the "Supervisor Options" menu.LBL="3-40"Supervisor Options screenFILE="n312i64a.pbm"A list of existing Workgroup Managers appears.Press <Ins> to view a list of "Other Users and Groups."LBL="3-41"Other Users and Groups screenFILE="n312i65a.pbm"Select the user or group you want to designate as Workgroup Manager.The user or group you selected is now a Workgroup Manager and appears on the "Workgroup Managers" list.Press <Esc> until you can select "User Information" from the "Available Topics" menu.Select a Workgroup Manager.Select "Managed Users and Groups" from the "User Information" menu.The Workgroup Manager will manage group EVERYONE if the users to be managed are part of group EVERYONE.Press <Ins> and select the users or groups for the Workgroup Manager to manage.ID="FM89085"(Optional) Designate User Account Managers.For planning information, IDREF="FM35574"see "Plan Workgroups (Optional)" on page 74.Select a User Account Manager.If you are a user. Select "User Information" from the "Available Topics" menu. A list of existing users appears. Select a user.If you are a member of a group. Select "Group Information" from the "Available Topics" menu. A list of existing groups appears. Select a group.Assign users or groups to the User Account Manager.Select "Managed Users and Groups" from either the "User Information" or "Group Information" menu.The list for "Managed Users and Groups" appears.Press <Ins> to view a list of "Other Users and Groups." Select the users or groups you want to assign to the User Account Manager.You can assign groups if all group members are assigned to the same User Account Manager.Where to Go From HereWIDTH="120"ToWIDTH="192"SeeWIDTH="120"Continue the installationWIDTH="192"IDREF="FM34948"Chapter 4, "Create Login Scripts," on  page 135.Install a print serverbook="print" docset="nw312"Print ServerSet up workstations to  do file server commands"book="sysadmin" docset="nw312"Remote Management" inSystem  AdministrationRun NetWare v3.x  utilities on a NetWare  v2.x file serverbook="utilref" docset="nw312"Utilities ReferenceCustomize directory  structure, user, or group  informationThese commands inUtilities Reference:"book="utilref" docset="nw312"ENABLE TTS""book="utilref" docset="nw312"FILER""book="utilref" docset="nw312"FLAG""book="utilref" docset="nw312"FLAGDIR""book="utilref" docset="nw312"GRANT""book="utilref" docset="nw312"MAKEUSER""book="utilref" docset="nw312"RIGHTS""book="utilref" docset="nw312"SETTTS""book="utilref" docset="nw312"SYSCON""book="utilref" docset="nw312"USERDEF"LBL="4"ID="FM34948"Create Login Scriptsidxid="w3697"book="_idx" docset="nw312" tidref="i3442"Login scripts set up workstation environments when users log in. Login scripts are similar to configurable batch files and are executed by the LOGIN utility.You can use login scripts toMap drives and search drives to directories.Display messages.Set environment variables.Execute programs or menus.Some login script commands that apply to DOS workstations don't apply to OS/2 workstations. These differences are indicated in the description of each command in this chapter.ID="FM32355"Plan Login ScriptsWhen a user logs in, LOGIN executes login scripts, similar to an AUTOEXEC.BAT file. Three types of login scripts are available:idxid="w3698"book="_idx" docset="nw312" tidref="i3504"idxid="w3699"book="_idx" docset="nw312" tidref="i3513"System login script.idxid="w3700"book="_idx" docset="nw312" tidref="i3513"Sets general environments for all users. This script executes first.idxid="w3701"book="_idx" docset="nw312" tidref="i3504"idxid="w3702"book="_idx" docset="nw312" tidref="i3537"User login script idxid="w3703"book="_idx" docset="nw312" tidref="i3537". Sets environments for a user, such as menu options or a username for electronic mail. This script executes after the system login script.idxid="w3704"book="_idx" docset="nw312" tidref="i3504"idxid="w3705"book="_idx" docset="nw312" tidref="i3477"Default login script.idxid="w3706"book="_idx" docset="nw312" tidref="i3477"(Part of LOGIN.) This script executes the first time you log in as user SUPERVISOR. It contains essential commands such as a drive mapping to NetWare utilities.To see the commands in this default script, IDREF="FM58770"see "Default Login Script" on page 185.The idxid="w3707"book="_idx" docset="nw312" tidref="i3504"idxid="w3708"book="_idx" docset="nw312" tidref="i3477"default login script also executes for a user who doesn't have a user login script. We recommend using the default login script only temporarily.An example of a system login script appears on IDREF="FM73754"page 188, and a user login script example appears on IDREF="FM31371"page 190.Decide Which Login Scripts to Create idxid="w3709"book="_idx" docset="nw312" tidref="i3504"Maintaining many user login scripts is time consuming. Therefore, include as much customizing information as possible in the system login script, which is easier to maintain.For example, if all users need access to NetWare utilities in the same volume, place the search drive mapping to that volume in a single system script rather than in every user script. In user login scripts, include only those items that can't be included in system scripts.Since two login scripts can execute when a user logs in, conflicts can occur.Because the system login script executes first, if you map the same drive letter or number in both login scripts, the mapping in the user login script overwrites the mapping in the system login script. Therefore, create a system login script before you create the user login script, so you know which drives are available.Plan idxid="w3710"book="_idx" docset="nw312" tidref="i3504"Login Script ConventionsLogin scripts require the command formats specified later in IDREF="FM22217""Hints" on page 144. A command format provides patterns for using key words, options, variables, spacing, delimiters or other characters, and punctuation.Any identifier variables enclosed in quotation marks must be uppercase and must be preceded by a percent (%) sign.Command lines cannot exceed 150 characters.Press <Enter> at the end of each command and start the next command on a new line. Each command must be on its own line.For additional information and examples, see "book="concepts" docset="nw312"Login Script" inConcepts.Plan a idxid="w3711"book="_idx" docset="nw312" tidref="i3504"idxid="w3712"book="_idx" docset="nw312" tidref="i3513"System Login ScriptYou can use the following categories to organize your system login script. The commands are listed and explained on IDREF="FM27425"page 148 and sample scripts are listed in IDREF="FM50259"Table 4-6 on page 190.idxid="w3713"book="_idx" docset="nw312" tidref="i3513"Preliminary commands. To use either of the following commands, place them at the beginning of a login script (commands that can be set to ON or OFF can be used more than once in a script):  DOS BREAK ON|OFF  MAP DISPLAY ON|OFFidxid="w3714"book="_idx" docset="nw312" tidref="i3513"Greetings. Display brief messages on user screens with   WRITE "message"idxid="w3715"book="_idx" docset="nw312" tidref="i3504"Display login messages. Use the following commands with the filename to display text files:  FDISPLAY filename  DISPLAY filenameWhen you display text files, type "PAUSE" on the next line so users can read the text at their own pace.idxid="w3716"book="_idx" docset="nw312" tidref="i3513"Attach to other file servers. For all users to attach to another file server, include ATTACH with the file server name.  ATTACH serverIf you form groups on the basis of which file servers users need to attach to, you can use the conditional IF ... THEN with ATTACH.  IF MEMBER OF "groupname" THEN  ATTACH server  ENDidxid="w3717"book="_idx" docset="nw312" tidref="i3513"NetWare utilities mapping. Include at least the following drive mapping to access NetWare utilities:  MAP S1:=SYS:PUBLICidxid="w3718"book="_idx" docset="nw312" tidref="i3513"DOS directory mapping and idxid="w3719"book="_idx" docset="nw312" tidref="i3504"idxid="w3720"book="_idx" docset="nw312" tidref="i1104"COMSPEC. Include the following commands if users need to run DOS from the network:  MAP INS S2:= DOS directory  COMSPEC =S2:COMMAND.COMCOMSPEC should specify the same search drive that is mapped to the DOS directory.For examples, see "book="concepts" docset="nw312"DOS Directories" inConcepts.idxid="w3721"book="_idx" docset="nw312" tidref="i3513"Application directory mappings. Map a search drive to each application directory that users or groups need access to.   MAP S16:=SYS:APPL\WORDPROC  MAP S16:=SYS:APPL\SPREADSHIf you formed groups on the basis of application use, use the IF ... THEN conditional to provide only that group with the mapping.If you use IF ... THEN to provide a group with two or more mappings, you must also use BEGIN ... END.  IF MEMBER OF "groupname" THEN BEGIN  MAP S16:=SYS:APPL\WORDPROC  MAP S16:=SYS:APPL\SPREADSH  ENDPut the series of mappings in the order of frequent use. List the most frequently used application group first and the least frequently used application group last.idxid="w3722"book="_idx" docset="nw312" tidref="i3513"Miscellaneous search drive mappings. Use the MAP command (with or without the conditionalIF ... THEN) to include a search drive mapping to any directory where batch files or third-party utilities are stored.idxid="w3723"book="_idx" docset="nw312" tidref="i3513"Supervisor mappings. To provide mappings to SYS:SYSTEM and other supervisor directories, complete the following IF ... THEN conditional:  IF LOGIN_NAME="SUPERVISOR" THEN  MAP S16:=SYS:SYSTEM  [commands]  ENDidxid="w3724"book="_idx" docset="nw312" tidref="i3513"idxid="w3725"book="_idx" docset="nw312" tidref="i3513"Home or username directory mapping. Include a generic mapping (using the identifier variable, %LOGIN_NAME for the directory name) to the home or username directory. We suggest that you map the first network drive to the home or username directory.The first network drive is usually F:, but if you have workstations that require some other drive letter as the first network drive, use *1 as a generic first network drive.  MAP *1:=SYS:HOME\%LOGIN_NAMEIf you want users at a drive other than the default drive when they exit the login script, use the DRIVE command:  DRIVE drive: | *n:idxid="w3726"book="_idx" docset="nw312" tidref="i3513"idxid="w3727"book="_idx" docset="nw312" tidref="i3513"Data or work directory mapping. Include mappings to data or work directories.If you formed groups on the basis of job responsibilities or information needs, use the IF ... THEN conditional to provide only that group with the mapping.idxid="w3728"book="_idx" docset="nw312" tidref="i3513"idxid="w3729"book="_idx" docset="nw312" tidref="i3513"Default printer mappings or printing batch files. If you formed groups on the basis of print queues, you can use the IF ... THEN conditional with #CAPTURE and a queue specification.   If MEMBER of "groupname" THEN  #CAPTURE S=server Q=printqueueOr you can call up batch files to provide printer or print queue routing.idxid="w3730"book="_idx" docset="nw312" tidref="i3513"idxid="w3731"book="_idx" docset="nw312" tidref="i1499"Display directory path at prompt. To display the directory path at the prompt, include the DOS PROMPT command (or include the command in your AUTOEXEC.BAT file).  SET PROMPT="$P$G"idxid="w3732"book="_idx" docset="nw312" tidref="i3513"Display drive settings. If you want drive mappings displayed for users, include the following commands:  MAP DISPLAY ON  MAPidxid="w3733"book="_idx" docset="nw312" tidref="i3513"idxid="w3734"book="_idx" docset="nw312" tidref="i5597"Run miscellaneous programs. To execute an external program (a filename with a .BAT, .COM, or .EXE extension), use the pound (#) sign preceding the name of the executable file.The pound sign (#) allows both external execution and then a return to continue the login script. #COMMAND /C filename will also execute a DOS batch file. You can also run an executable file from an EXIT command. (However, if you use an EXIT command in a system login script, the user login script will not run.)For a sample system login script, IDREF="FM73754"see "System Login Script" on page 188.Plan User idxid="w3735"book="_idx" docset="nw312" tidref="i3504"idxid="w3736"book="_idx" docset="nw312" tidref="i3537"Login ScriptsA user login script contains commands thatMap network drives used only by an individual user.Initialize environmental variables for the individual user.Exit to or call up menus (optional).A user's login script executes after the system login script and customizes the environment for that user.If you have accomplished your main purposes in the system login script, you need only minimal user login scripts.Users can modify their own login scripts in SYSCON if you allow them to change their own passwords.Using SYSCON, you can copy login scripts from one user to another and then modify the copied login script to customize it.A user idxid="w3737"book="_idx" docset="nw312" tidref="i3537"login script contains the same kinds of commands that are used in the system login script, but a user login script contains commands that apply only to an individual user.You can map drives to directories individuals frequently use. Don't use the same numbered search drives as the system login script.If you do, search mappings created by the system login script are overwritten, and the COMSPEC command (which requires the same search drive mapped to DOS directories) won't work. Use the idxid="w3738"book="_idx" docset="nw312" tidref="i3730"MAP INS command to prevent overwriting mappings.Use the idxid="w3739"book="_idx" docset="nw312" tidref="i1701"DOS SET command to set application environment variables that apply to individual users.Whatever can be set in the AUTOEXEC.BAT file can be set in the user login script. For more information and examples, see "book="concepts" docset="nw312"Login Script" inConcepts.If you create a idxid="w3740"book="_idx" docset="nw312" tidref="i3537"menu for users to access applications and programs, you can call up the menu from the user login script. For more about menus, see "book="utilref" docset="nw312"NMENU" inUtilities Reference.If you use the idxid="w3741"book="_idx" docset="nw312" tidref="i1928"EXIT command in the system login script, user login scripts will not execute.idxid="w3742"book="_idx" docset="nw312" tidref="i420"Application environment variables. Consult the documentation that accompanies the applications you plan to install on the network.Determine which user variables can be set with the DOS SET command and how they should appear in the login script.Individual idxid="w3743"book="_idx" docset="nw312" tidref="i1730"idxid="w3744"book="_idx" docset="nw312" tidref="i3537"search drive mappings. If a user uses a directory containing executable files, and the mapping isn't in the system login script, include a search drive mapping for that user to the directory. Example:  MAP S16:=SYS:APPL\SPREADSHIndividual drive mappings. If a directory is frequently used by only one user, plan a drive mapping for that user to the directory. Example:  MAP g:=SYS:PROJECTS\CURRENTExecute a idxid="w3745"book="_idx" docset="nw312" tidref="i3806"menu. You can exit to a menu from the login script using EXIT as the last command in the user login script. (To create menus, see "book="utilref" docset="nw312"NMENU" inUtilities Reference.)The string that follows an EXIT command must be 14 characters or fewer.The menu script file (for example, ACCOUNT.MNU or PAYCLERK.MNU) must be stored in a directory to which a search drive has been mapped. You can include commands similar to the following:  idxid="w3746"book="_idx" docset="nw312" tidref="i3806"EXIT "MENU account"or  IF MEMBER OF "PAYCLERK" THEN  EXIT "MENU payclerk"Or you can also exit to a batch file:  EXIT "COMMAND /C GO"In the GO.BAT file, type  MENU payclerk  ^ZThe GO.BAT file should also be stored in a directory to which a search drive has been mapped.For a sample user login script, IDREF="FM50259"see Table 4-6,  "Sample user login script," on page 190.Creating, Modifying, and Copying Login ScriptsUse SYSCON to create or modify login scripts and to copy one user's login script to another.ID="FM22217"HintsSystem and user login scripts use the same conventions, commands, and variables. The following hints will help you plan effective login scripts. For a description of the commands you can use in a login script, see IDREF="FM27425""Login Script Commands and Variables" on page 148. For variable information, IDREF="FM38017"see Table 4-3,  "Identifier Variables," on page 182.LBL="4-1" INLINE="F"idxid="w3747"book="_idx" docset="nw312" tidref="i3442"Login script conventionsWIDTH="120"SubjectWIDTH="300"ConventionWIDTH="120"idxid="w3748"book="_idx" docset="nw312" tidref="i704"Blank linesWIDTH="300"Blank lines don't affect script execution. Use them to visually separate  groups of commands.idxid="w3749"book="_idx" docset="nw312" tidref="i926"CaseEither uppercase or lowercase is accepted. Exception: identifier  variables enclosed in quotation marks must be preceded by a percent  sign (%) and must be uppercase.IDREF="FM58742""Identifier Variables" on page 180.idxid="w3750"book="_idx" docset="nw312" tidref="i953"Characters per line150 characters per line maximum; 78 (common screen width) is  recommended for readability.idxid="w3751"book="_idx" docset="nw312" tidref="i1052"Commands per lineUse only one command per line. Start each command on a new line  and press <Enter> at the end of each command.Lines that wrap automatically are considered one command.WRITE commands display better if the command WRITE is repeated at  the beginning of each line.idxid="w3752"book="_idx" docset="nw312" tidref="i2759"Identifier variablesType identifier variables exactly as shown.Identifier variables that you want displayed on the workstation's screen  as part of a WRITE command should be enclosed in quotation marks,  preceded by a percent sign (%), and typed in uppercase letters. IDREF="FM58742""Identifier Variables" on page 180.Minimum scriptNo minimum. Both types of scripts are optional. Scripts can have one  line or many. There are no required commands for scripts.Punctuation and  symbolsType symbols (#, %, ", _) and punctuation exactly as shown in  examples and syntax.idxid="w3753"book="_idx" docset="nw312" tidref="i5783"Remarks (REMARK, REM,  asterisks, and  semicolons)Lines beginning with REMARK, REM, an asterisk, or a semicolon are  comments and do not display when the script executes.Use remarks to record the purpose of each command or group of  commands. (See IDREF="FM63873"page 172.)idxid="w3754"book="_idx" docset="nw312" tidref="i1051"Sequence of commandsGenerally, enter commands in the order you want them to execute,  with the following restrictions:Enter commands with ON|OFF switches at the beginning of the script.ATTACH commands must precede related MAP commands.If you use "#" to execute an external program, it must follow necessary  MAP commands.If sequence is not important, group similar commands, such as MAP  and WRITE commands, together to make the script easier to read.Create the System idxid="w3755"book="_idx" docset="nw312" tidref="i3513"idxid="w3756"book="_idx" docset="nw312" tidref="i6629"Login ScriptProcedureAt the command line type  SYSCON <Enter>Select "Supervisor Options" from the "Available Topics" menu.Select "System Login Scripts" from the "Supervisor Options" menu.An empty "System Login Script" box appears.LBL="4-1"System Login Script screenFILE="n312i66a.pbm"Type the login script commands for your system login script (see IDREF="FM32355""Plan Login Scripts" on page 135).When you finish entering the commands, press <Esc> and then <Enter> to save your changes.Press <Esc> again to return to the "Available Topics" menu.Create User idxid="w3757"book="_idx" docset="nw312" tidref="i3537"idxid="w3758"book="_idx" docset="nw312" tidref="i6629"Login ScriptProcedureAt the prompt, type  SYSCON <Enter>ID="FM69141"Select "User Information" from the "Available Topics" menu.The "User Names" list appears.Select a username.Select "Login Script" from the "User Information" menu.The following screen appears:LBL="4-2"Create or copy a login script screenFILE="n312i113.pbm"To copy a login script from another user, type the name of the user whose login script you want to copy or press <Insert> to select the user from the list.The login script appears in the screen.To create a new login script, press <Enter>.A user login script box appears.LBL="4-3"User Login Script screenFILE="n312i112.pbm"Enter the drive mappings, environment variables, and other login script commands you want for the user (excluding those in the system login script).ID="FM46492"When you finish entering the commands, press <Esc>. Press <Enter> to save the login script changes. Then press <Esc> again to return to the "User Names" list.Repeat IDREF="FM69141"Steps 2 through IDREF="FM46492"6 to create a login script for each user.ID="FM27425"Login Script Commands and VariablesThe following login script commands are described in alphabetical order on the following pages:WIDTH="156"#WIDTH="156"GOTOATTACHIF ... THENBREAKINCLUDECOMSPECMACHINEDISPLAYMAPDOS BREAKPAUSEDOS VERIFYPCCOMPATIBLEDRIVEREMARKEXITSETFDISPLAYSHIFTFIRE PHASERSWRITEidxid="w3759"book="_idx" docset="nw312" tidref="i3481"Syntax conventions for login script commands are the same as those for workstation text utilities. The following is an example of the syntax for the MAP login script command:  MAP [option] drive:=[drive:|path]For a table of command syntax conventions, see IDREF="FM57172"page 149.LBL="4-2" INLINE="F"ID="FM57172"idxid="w3760"book="_idx" docset="nw312" tidref="i3442"Command syntax conventionsWIDTH="120"ConventionWIDTH="300"ExplanationWIDTH="120"MAPWIDTH="300"Words in uppercase letters are keywords that must be included in the  command and spelled exactly as shown. However, you can type them  in uppercase or lowercase letters.[ ]Square brackets indicate that the enclosed item is optional.|A vertical bar means you can use either the item to the left of the bar,  or the item to the right, but not both. In the MAP example, you can  enter either the drive letter or a complete path.drive:Words in italics are variables. Replace variables with information  specific to your task.[option]Options for each command are listed with the command. Options can  often be abbreviated.<Enter>Angle brackets indicate a key you should press.[[ ]]Nested square brackets indicate that all enclosed items are optional.  However, if you use the items within the inner brackets, you must also  use the items within the outer brackets.\A backslash is used to separate filenames in a path statement.Although the backslash is the convention, it doesn't matter if you use  a forward slash; either is accepted. However, if you use a command line  option (/s, for example) the forward slash must be used.idxid="w3761"book="_idx" docset="nw312" tidref="i7"idxid="w3762"book="_idx" docset="nw312" tidref="i3452"# (Execute External Program)Use this command to execute a program that is external to the login script.Command Format  # [path] filename [parameter]Replace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with an executable file (files that end in .EXE, .COM, or .BAT, for example), excluding the extension.Replace parameter with parameters that must accompany the executable file.Using #Enter the # command after MAP assignments, so that the program executes using the correct drive mappings.The login script is held in memory when the # command is run. The script is not released until you return to the login script and either complete it or exit it.idxid="w3763"book="_idx" docset="nw312" tidref="i3481"ExamplesTo print from an application not designed to print on a network, include CAPTURE in your login script, which allows you to send print jobs to a network print queue (QUEUE1 in this example):  #CAPTURE Q=QUEUE1 NB TI=10 NFFYou do not need to enter a path in this case because CAPTURE is located in SYS:PUBLIC, and the system login script should have a search drive mapped there.If you do not have a search drive mapped to a directory, you must include the path to that directory in the command.For example, to run a batch file named BATCH.BAT in the ACCOUNTS directory, use the following command:  #SYS:ACCOUNTS\BATCHidxid="w3764"book="_idx" docset="nw312" tidref="i546"idxid="w3765"book="_idx" docset="nw312" tidref="i3452"ATTACHUse ATTACH to connect to NetWare servers while the login script is running.Command Format  ATTACH [server[\username]]Using ATTACHReplace server with the name of the server you want to attach to.Replace username with the login name.If you do not include the username, the system assumes the username on the current server. To log in with a different username, include it in the ATTACH command as in the following example.idxid="w3766"book="_idx" docset="nw312" tidref="i3481"ExampleTo attach to a server called REPORTS as user MRICHARD, add the following line to your login script:  ATTACH REPORTS\MRICHARDID="FM94944"idxid="w3767"book="_idx" docset="nw312" tidref="i756"idxid="w3768"book="_idx" docset="nw312" tidref="i3452"BREAKUse BREAK ON to allow you to terminate the execution of your login script. The default is BREAK OFF.Command Format  BREAK ON|OFFUsing BREAKIf BREAK ON is in your login script, you can press <Ctrl><C> or <Ctrl><Break> to abort the normal execution of your login script.Including BREAK ON in your login script does not affect the DOS <Ctrl><Break> check. For more details, IDREF="FM70330"see "DOS BREAK" on page 155.When the BREAK option is ON, type-ahead keyboard input is not saved in the buffer.idxid="w3769"book="_idx" docset="nw312" tidref="i1104"idxid="w3770"book="_idx" docset="nw312" tidref="i3452"COMSPECIf users run DOS from the network, use COMSPEC in the login script to specify the directory where DOS and the command processor (COMMAND.COM) are loaded.Users running OS/2 should not use this command in the login script (see IDREF="FM31624""Using COMSPEC with OS/2" on page 153).Command Format  COMSPEC = [path]COMMAND.COMReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.Using COMSPEC If users run DOS from a network directory, first map a search drive in the login script to that directory, then add the COMSPEC command to the script. You may want to map a fake root to the DOS directory. (See "book="concepts" docset="nw312"Fake root" in Concepts, or "book="utilref" docset="nw312"MAP" in Utilities Reference.)If all users use the same version of DOS from the network, add the COMSPEC command to the system login script.If more than one version of DOS is available on your network, a network directory should exist for each DOS version.In this case, put COMSPEC commands in user login scripts to make sure each workstation accesses the version of DOS it needs.If users run DOS from their local drives, do not add COMSPEC to login scripts. Instead, users add COMSPEC to their AUTOEXEC.BAT files.ID="FM31624"Using idxid="w3771"book="_idx" docset="nw312" tidref="i1104"COMSPEC with OS/2If all users are running OS/2, do not include the COMSPEC variable in a login script.A user running a DOS session from an OS/2 workstation must include a COMSPEC statement in his or her CONFIG.SYS file (instead of the login script) to point to COMMAND.COM on a local hard disk.If you have both DOS and OS/2 users that execute the same login script, include the COMSPEC command in the script.However, OS/2 users must then reset the COMSPEC variable after they log in (from the command line or in a batch file).ExampleIf you mapped a search drive to the DOS directory on the network, you can use the search drive number or drive letter in the COMSPEC command.For example, if the second search drive (S2:, which maps to drive letter Y:) in the login script is mapped to the DOS directory, either of the following COMSPEC commands will work in the login script:  COMSPEC=S2:\COMMAND.COM  COMSPEC=Y:\COMMAND.COMFor more about OS/2 workstations, see book="ws_os2" docset="nw312"Workstation for OS/2.ID="FM16630"idxid="w3772"book="_idx" docset="nw312" tidref="i1615"idxid="w3773"book="_idx" docset="nw312" tidref="i3452"DISPLAYUse DISPLAY to show the contents of a text file on a workstation's screen when the user logs in. This command works best with an ASCII file.If you use DISPLAY with a word-processed file, printer and word-processing codes are displayed with the text. To display a word-processed file, IDREF="FM96761"see "FDISPLAY" on page 158.Command Format  DISPLAY [path] filenameReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with the complete name of the file you want to display.idxid="w3774"book="_idx" docset="nw312" tidref="i3481"ExampleYou put messages in a file called SYSNEWS.TXT, in the directory SYS:PUBLIC\MESSAGES, and you want your users to see this file on their screens when they log in on Mondays.Add the following lines to the system login script:  IF DAY_OF_WEEK = "Monday" THEN  DISPLAY SYS:PUBLIC\MESSAGES\SYSNEWS.TXTID="FM70330"DOS BREAKUse idxid="w3775"book="_idx" docset="nw312" tidref="i1665"idxid="w3776"book="_idx" docset="nw312" tidref="i3452"DOS BREAK to set the <Ctrl><Break> checking level for DOS. If the DOS BREAK command is set to ON, you can terminate a program (other than the login script) by pressing <Ctrl><Break>. This command does not apply to OS/2 workstations.This command is different from the BREAK command that terminates the login script. IDREF="FM94944""BREAK" on page 151 for more details.Command Format  DOS BREAK [ON|OFF]Using DOS BREAKEnter the following command in the login script:  DOS BREAK ONThe default is DOS BREAK OFF.DOS VERIFYUse idxid="w3777"book="_idx" docset="nw312" tidref="i1703"idxid="w3778"book="_idx" docset="nw312" tidref="i3452"DOS VERIFY to verify that data copied by the DOS COPY command to a local drive can be read without an error.If you do not use DOS's COPY command (for example, if you use NetWare's NCOPY utility instead), you do not need to use this login script command.Command Format  DOS VERIFY [ON|OFF]Using DOS VERIFYThe DOS COPY command, unlike the NetWare NCOPY utility, does not automatically verify that data copied to a local drive can be read after the copy.To make COPY verify success the same way NCOPY does, add the DOS VERIFY ON command to the login script.This command may not work with some software that is copy protected.The default is DOS VERIFY OFF.DRIVEUse idxid="w3779"book="_idx" docset="nw312" tidref="i1722"idxid="w3780"book="_idx" docset="nw312" tidref="i3452"DRIVE to specify your default drive.Command Format  DRIVE [drive:|*n:]Replace drive with a local or network drive letter, or replace n with a drive number.Using DRIVEUnless this command is in your login script, your default drive is set to the first network drive, which is often assigned to your home directory when you log in.If you do not want your default drive to be the first network drive, map a drive in your login script to the directory you want to be your default.After that MAP command, enter the DRIVE command in your login script.You can specify drive letters such as F: or G:, or you can use an asterisk followed by a number n to represent the nth network drive (for example, *3).This allows drive letters to reorder themselves automatically if previous drive mappings are deleted or added.idxid="w3781"book="_idx" docset="nw312" tidref="i3481"ExampleYou expect to work on only one project for several days and the files for that project are located on drive S:.You can use the DRIVE command to set your default drive to S: so you won't have to change your default drive every time you log in.First, make sure you've mapped drive S: to the correct directory in your login script. Then enter the following command in the script:  DRIVE S:ID="FM89141"EXITUse idxid="w3782"book="_idx" docset="nw312" tidref="i1928"idxid="w3783"book="_idx" docset="nw312" tidref="i3452"EXIT to terminate execution of the LOGIN utility and execute an external program.Command Format   EXIT ["filename"]Using EXITYou can also use EXIT in an IF...THEN statement, so that the script stops and exits to an external program if a certain condition exists. If the condition doesn't exist, the script skips the EXIT command and continues executing.If you add EXIT at the end of a system login script, it prevents user login scripts from running.EXIT only works on IBM PCs and compatibles, and on workstations running OS/2.Therefore, if you use DOS and your workstation doesn't have the IBM_PC machine name, add the PCCOMPATIBLE login script command to the script.You can change the workstation's machine name in the NET.CFG file.idxid="w3784"book="_idx" docset="nw312" tidref="i3481"ExamplesYou are running DOS and your long machine name is IBM_PC. You want to execute a menu program called TRAINING when the login script is finished. Add the following at the end of the login script:  EXIT "MENU TRAINING"You are running DOS on a Hewlett Packard computer and you have changed the long machine name to HE_PAC in the NET.CFG file. Add the following lines at the end of the login script:  PCCOMPATIBLE  EXIT "MENU TRAINING"You want your login script to exit to WordPerfect when you log in on Mondays, but not on other days. Add the following IF...THEN statement to your login script:  IF DAY_OF_WEEK = "MONDAY" THEN EXIT "WP"ID="FM96761"FDISPLAYUse idxid="w3785"book="_idx" docset="nw312" tidref="i1981"idxid="w3786"book="_idx" docset="nw312" tidref="i3452"FDISPLAY to show the text of a word-processed file on a workstation's screen when the user logs in. To display both the text and the printer and wordprocessing codes of a file, or to display an ASCII file, IDREF="FM16630"see "DISPLAY" on page 154.Command Format  FDISPLAY [path] filenameReplace path with either a drive letter or a full directory path beginning with the NetWare volume name.Replace filename with the complete name of the file you want to display.Using FDISPLAYWhen you use FDISPLAY to display the contents of a word-processed file on the screen when a user logs in, the text in the file is filtered and formatted so that only the text itself is displayed. FDISPLAY will not display tabs.If the given directory does not exist or if the file is not found, no error message appears on the screen when the user logs in.idxid="w3787"book="_idx" docset="nw312" tidref="i3481"ExampleYou put messages in a file called SYSNEWS.TXT, in the directory SYS:PUBLIC\MESSAGES, and you want your users to see this file on their screens when they log in on Mondays.Add the following lines to the system login script:  IF DAY_OF_WEEK = "Monday" THEN  FDISPLAY SYS:PUBLIC\MESSAGES\SYSNEWS.TXTFIRE PHASERSUse idxid="w3788"book="_idx" docset="nw312" tidref="i2429"idxid="w3789"book="_idx" docset="nw312" tidref="i3452"FIRE PHASERS to emit a phaser sound when certain conditions exist.Command Format  FIRE PHASERS n TIMESReplace n with the number of times (up to nine) that you want to hear this sound.Using FIRE PHASERSUse this command by itself to hear the phaser sound whenever a user logs in.Use FIRE PHASERS with the IF...THEN command to make the sound execute a different number of times depending on the circumstances of the login.idxid="w3790"book="_idx" docset="nw312" tidref="i3481"ExamplesThe following will execute the phaser sound four times when you log in:  FIRE PHASERS 4 TIMESThe following lines will fire the phasers five times on Thursdays:  IF DAY_OF_WEEK = "Thursday" THEN  FIRE PHASERS 5 TIMESFor more information about using identifier variables such as DAY_OF_WEEK, IDREF="FM58742"see "Identifier Variables" on page 180.GOTOUse idxid="w3791"book="_idx" docset="nw312" tidref="i2559"idxid="w3792"book="_idx" docset="nw312" tidref="i3452"GOTO to execute a portion of the login script out of the regular sequence.Command Format  GOTO labelUse label to indicate where you want to continue executing the login script.Using GOTOSet BREAK ON in your login script before experimenting with GOTO loops so that you can break out of a script if necessary.For more about BREAK, IDREF="FM94944"see "BREAK" on page 151.Do not use GOTO from within a nested IF...THEN statement.idxid="w3793"book="_idx" docset="nw312" tidref="i3481"ExampleTo execute a loop of commands, include the following lines in your script. In this case, the commands to be executed are labeled LOOP (indicated on the second line).  SET X = "1"  LOOP:  SET X = <X> + "1"  ;see compound strings for this  WRITE <X>  IF <X> < "10" THEN GOTO LOOP<X> is a DOS environment variable that is incremented with each loop. Remember to allow IF...THEN commands to wrap to the next line if there is not enough room on one line.IF...THENUse idxid="w3794"book="_idx" docset="nw312" tidref="i2768"idxid="w3795"book="_idx" docset="nw312" tidref="i3452"IF...THEN when you want the login script to perform an action only under certain conditions.Command Format  IF conditional [AND|OR [conditional]] THEN   command  [ELSE command]  [END]Replace conditional with identifier variables (IDREF="FM58742"see "Identifier Variables" on page 180).Replace command with login script commands you want to execute if the specified condition is true.Using IF...THENUse IF...THEN to execute commands only under certain conditions.For example, if you want special messages to appear on the screen on certain days of the week, use IF...THEN to accomplish this. When using IF...THEN, be aware of the following syntax rules:Use "AND" or "OR" to include two or more conditionals in an IF...THEN statement.Enclose values of conditional statements in quotation marks.The ELSE statement is optional.IF, ELSE, and END must be on separate lines. THEN does not need to be on a separate line.If you include a WRITE command as part of an IF...THEN command, the WRITE command must be on a separate line.IF...THEN statements can be nested (up to 10 levels).If your IF...THEN statement consists of only one line, even if that line wraps, you do not need to include END.If your IF...THEN statement must be on more than one line (for example, you used ELSE or WRITE, which must be on separate lines), you must include END.If your IF ... THEN statement contains two or more consecutive commands, you must use END.Use only one END statement per IF...THEN. Once an END statement is encountered, evaluation of the current IF...THEN is terminated, regardless of what follows.An example of a conditional statement:  IF MEMBER OF "CLERKS"In this statement, some action will be performed if the user who logged in belongs to the group named CLERKS.The following is a different type of conditional statement:  IF DAY_OF_WEEK = "MONDAY"In this statement, the equals sign (=) indicates the relationship between the variable (DAY_OF_WEEK) and its value (Monday). Note that the value (Monday) is inside quotation marks.Six relationships are possible between the information contained in an IF...THEN statement. You can represent these relationships using the following symbols:WIDTH="108"ID="FM24522"SymbolWIDTH="204"DefinitionWIDTH="108"=WIDTH="204"Equals<>Does not equal>Is greater than>=Is greater than or equal to<Is less than<=Is less than or equal toidxid="w3796"book="_idx" docset="nw312" tidref="i3481"ExamplesIf you have the following command in your login script, you see "Status report is due today" when you log in on Monday and "Have a nice day!" on other days.  IF DAY_OF_WEEK = "MONDAY" THEN  WRITE "Status report is due today"  ELSE  WRITE "Have a nice day!"  ENDThe following line means "If the hour (on a 24-hour scale) is greater than or equal to 12, then write `afternoon'."  IF HOUR24 >= "12" THEN  WRITE "afternoon"  ENDThe following command executes the CAPTURE utility on the fourth day of the week (Wednesday):   IF NDAY_OF_WEEK = "4" THEN  #CAPTURE Q=FAST_Q NB TI=10 NFFThe following example shows nested IF...THEN statements. Notice that there are two IF statements, so each one must have its own END statement.  IF DAY_OF_WEEK = "MONDAY" THEN  IF MEMBER OF "CLERKS" THEN  WRITE "Your report is due immediately!"  END  ENDConditionals can be joined with commas, the word AND, and the word OR to form compound conditionals.The first line of the following IF...THEN statement is a compound conditional that means "If it is the morning of the first day of the month":   IF GREETING_TIME="MORNING" AND DAY="01" THEN  WRITE "The system will be backed up tonight."  ENDThe following line is a compound conditional that means "If it is 11:59:59 p.m.":  IF HOUR24="23", MINUTE="59", AND SECOND="59"An IF...THEN statement can include several commands that must be executed if the conditional is true. The following example shows two commands that are executed on Tuesdays: a WRITE command that displays a message about a staff meeting, and an INCLUDE command that tells the login script to process any commands or messages contained in the file SYS:PUBLIC\UPDATE.  IF DAY_OF_WEEK = "TUESDAY" THEN  WRITE "Staff meeting today at 10 a.m."  INCLUDE SYS:PUBLIC\UPDATE  ENDFor more information about identifier variables, IDREF="FM58742"see "Identifier Variables" on page 180.ID="FM64707"INCLUDEUse idxid="w3797"book="_idx" docset="nw312" tidref="i2796"idxid="w3798"book="_idx" docset="nw312" tidref="i3452"INCLUDE to execute a subscript as a part of the login script. Subscripts can be text files that contain any of the commands explained in this section. A subscript can also be a login script that belongs to a different object.Command Format  INCLUDE [path]filenameTo use a text file as a subscript, replace path with either a drive letter or a full directory path beginning with the NetWare volume name. Replace filename with the complete text file name.Using INCLUDEYou can create and edit text-file subscripts using any text editor or word processor. Subscripts do not need any particular filenames or extensions.INCLUDE nesting is limited only by memory. This means that one script file can include another script file, which can include yet another script file, and so on.You must have at least File Scan and Read rights in the directory containing a subscript you want to use.idxid="w3799"book="_idx" docset="nw312" tidref="i3481"ExamplesTo execute a text file called SCRIPT.NEW (located in volume VOL1:) as a subscript, add the following line to your main login script:  INCLUDE VOL1:ADMIN\USERS\SCRIPT.NEWMACHINEUse idxid="w3800"book="_idx" docset="nw312" tidref="i3605"idxid="w3801"book="_idx" docset="nw312" tidref="i3452"MACHINE to set the DOS machine name (such as IBM_PC or HE_PC) of the workstation. This command does not apply to OS/2 workstations.Command Format  MACHINE = nameUsing MACHINEThe machine name can be up to 15 characters. (Longer machine names are truncated to 15 characters.)MACHINE is necessary for some programs (such as NETBIOS) written to run under PC DOS. The name can include such identifier variables as STATION.For information about setting machine names in the NET.CFG file, see "book="ws_dos" docset="nw312"Appendix B" in Workstation for DOS and Windows. For information about using identifier variables, see IDREF="FM58742""Identifier Variables" on page 180.ID="FM99801"MAPUse idxid="w3802"book="_idx" docset="nw312" tidref="i3729"idxid="w3803"book="_idx" docset="nw312" tidref="i3452"MAP to map drives and search drives to network directories.Command Format  MAP [option] drive:=[drive:|path]Replace drive with a valid network drive letter, local drive letter, or search drive number.Replace path with either a drive letter or a full directory path.When mapping a drive to a directory on your current server, begin the path with the volume name.When mapping to a directory on a server that isn't your current server, begin the path with the server's name.Replace option with one of the following:DISPLAY ON/OFF: Determines whether drive mappings are displayed on the screen when the user logs in. The default setting is ON. (Valid only in login scripts.)ERRORS ON/OFF: Determines whether MAP error messages are displayed when the user logs in.MAP ERROR OFF must be placed before MAP commands in the login script. The default setting is ON. (Valid only in login scripts.)INS: Inserts a drive mapping between existing mappings. (Valid only in login scripts and at the command line.)DEL: Deletes a drive mapping, making that drive letter available for other mapping assignments. (Valid only in login scripts and at the command line.)ROOT: Maps a fake root. Some applications require their executable files to be located in a root directory.Since you may not want users to have rights at the root directory, you can map a fake root to a subdirectory instead. (Valid only in login scripts and at the command line.)N (Next): When used without specifying a drive number or letter, maps the next available drive. (Valid only in login scripts and at the command line.)Using MAPUse MAP to save drive mappings in a login script so that users don't have to remap drives to directories every time they log in.Specify drive mappings in a login script by entering the same commands that you would enter if you were using MAP at the command line.These mappings are displayed when you log in, unless you put MAP DISPLAY OFF in your login script. You can specify drive letters such as F: or G:, or use an asterisk followed by a number n to represent the nth network drive (for example, MAP *3:=).This allows drive letters to reorder themselves automatically if previous drive mappings are deleted or added.This also allows users to log in from workstations with a different number of local drives than their regular workstation.You can map a local drive (usually A: through E:) to a network directory, but you cannot access the local drive until you remove the network drive mapping.Mapping Search DrivesFor DOS and Windows workstations, you can map search drives to directories that contain applications, executable files, etc.Then DOS and Windows users can execute those applications regardless of the directory they are working in.OS/2 workstations cannot use search drives. Instead, OS/2 users use the OS/2 commands PATH, DPATH, and LIBPATH in their CONFIG.SYS files.When you map a search drive, 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.You can map search drives in the following order:Map the first search drive (S1:) to SYS:PUBLIC, which contains NetWare utilities for DOS and Windows workstations.Map the second search drive (S2:) to the DOS directory if users access DOS from the network.Map the third and subsequent search drives (S3:, S4:, etc.) to directories containing applications.To avoid inadvertently changing the order of these crucial search drives, map all remaining search drives with the number S16.This will assign each search drive the next available drive letter, without displacing the previous drives.If you have an application that requires a particular drive letter, use the following command to map the search drive, replacing drive: with the drive letter:  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.idxid="w3804"book="_idx" docset="nw312" tidref="i3481"ExamplesTo map the first search drive to SYS:PUBLIC (which contains NetWare utilities for DOS and Windows workstations) add the following line to the login script:  MAP S1:=SYS:PUBLICMap the second search drive to the DOS directory if users run DOS from the network.If all users have the same types of computers and use the same version of DOS, you probably only have one DOS directory.In this case, add a line similar to the following, substituting the correct directory names:  MAP S2:=SYS:PUBLIC\IBM_PC\MSDOS\50If your network has more than one DOS directory, use variables to indicate the directory path.These variables are replaced by the correct information from the workstation software when each user logs in.To use variables for the DOS directory path, enter the following command in the login script:  MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSIONTo map the next available search drive to the SYS:APPL\WORDPROC directory, add the following line to the login script:  MAP S16:=SYS:APPL\WORDPROCTo map Richard's first four regular drive mappings to his home directory, SYS:PUBLIC\OS2 (which contains the NetWare utilities for OS/2), REPORTS, and PROJECTS, add the following to Richard's user login script:  MAP *1:=VOL1:HOME\RICHARD  MAP *2:=SYS:PUBLIC\OS2  MAP *3:=VOL1:ACCOUNTS\REPORTS  MAP *4:=VOL1:UPDATES\PROJECTSTo map a drive to the PUBLIC directory on a NetWare v3.12 server named FS1, you need to include the server name in the MAP command. Use the following line in your login script:  MAP *5:=FS1\SYS:PUBLICFor more information about drive mappings, see "book="concepts" docset="nw312"Drive Mapping" in Concepts. For more information about setting paths for OS/2 workstations, seebook="ws_os2" docset="nw312"NetWare Workstation for OS/2.PAUSEUse idxid="w3805"book="_idx" docset="nw312" tidref="i5030"idxid="w3806"book="_idx" docset="nw312" tidref="i3452"PAUSE to pause the execution of the login script.Command Format  PAUSEUsing PAUSEEnter this command in your login script at any point you want a pause to occur.For example, add PAUSE following a message so the user has time to read the message before it scrolls off the screen.If you include PAUSE, the message "Strike any key when ready..." appears on the screen. LOGIN then waits for a key to be pressed before it executes the rest of the login script.PCCOMPATIBLEUse idxid="w3807"book="_idx" docset="nw312" tidref="i5037"idxid="w3808"book="_idx" docset="nw312" tidref="i3452"PCCOMPATIBLE to enable the EXIT login script command to work if your workstation's machine name is not IBM_PC. This command does not apply to OS/2 workstations.Command Format  PCCOMPATIBLEUsing PCCOMPATIBLEIf your computer's long machine name in your NET.CFG file is not IBM_PC (for example, HE_PAC, AT&T, or TANDY), and you want to use the EXIT login script command, use PCCOMPATIBLE to inform LOGIN that your machine is an IBM PC compatible.Place the following anywhere before EXIT in the login script:  PCCOMPATIBLEidxid="w3809"book="_idx" docset="nw312" tidref="i3481"ExampleYou have a Hewlett Packard computer and you have changed the long machine name to HE_PAC in the NET.CFG file, and you want to exit to NETADMIN from within your login script.Put the following in your login script:  PCCOMPATIBLE  EXIT "NETADMIN"For more information about setting the machine name in NET.CFG, see book="ws_dos" docset="nw312"Appendix B in Workstation for DOSand Windows. For more information about using the EXIT login script command, IDREF="FM89141"see "EXIT" on page 157.ID="FM63873"REMARKUse idxid="w3810"book="_idx" docset="nw312" tidref="i5782"idxid="w3811"book="_idx" docset="nw312" tidref="i3452"REMARK to insert explanatory text into your login script.Command Format  REM[ARK] [text]  or  * [text]  or  ; [text]Replace text with the comment you want to include in the script.Using REMARKTo include explanatory text in your login script, begin a line with REMARK, REM, an asterisk (*), or a semicolon (;).Any text that follows these symbols is ignored when LOGIN executes your login script. Remarks do not appear on your screen.Using remarks in your login script makes the script easier for you or others to understand.REMARK and its associated text must be the only entry on a line. Placing remarks on the same line as other script commands can cause errors.idxid="w3812"book="_idx" docset="nw312" tidref="i3481"ExamplesThe following are examples of explanatory text that you might use with the REMARK command:   * This is Richard's login script  ; Mapped network drives follow:  REM The next mapping is a fake root.  REMARK This script is for new users.ID="FM74868"SETUse idxid="w3813"book="_idx" docset="nw312" tidref="i6285"idxid="w3814"book="_idx" docset="nw312" tidref="i3452"SET to set a DOS environment variable to a specified value.For OS/2 workstations, SET commands affect the environment only while the login script is running; the settings disappear when LOGIN terminates.Command Format  [TEMP] SET name = "value"Replace name with an environment parameter that identifies the environment you want to change.Replace value with identifier variable substitutions. Enclose values in quotation marks.To change the environment for the login script, but not for the workstation itself after the login script has finished executing, use the optional keyword TEMP.Variables set in the login script for an OS/2 workstation apply only to the current session.Using SETUse SET in a login scripts the same as you use it at the command line. However, when you use SET in a login script, you must enter quotation marks (" ") around values.SET commands do not need to be included in login scripts. For example, you may decide that it is easier to put some SET commands in a workstation's AUTOEXEC.BAT file.For information about values you can set, see the SET command in your DOS or OS/2 documentation.This command does not work if a DOS workstation's environment is too small. (Set the environment size in the CONFIG.SYS file.)For more about environment size, see the SHELL command in your DOS manual. (OS/2 workstations do not have this limitation.)idxid="w3815"book="_idx" docset="nw312" tidref="i3481"ExamplesYou can use SET to make your prompt display your current directory path, such as F:\HOME\MARY>, rather than just the drive letter. To do this, add the following line to your script:  SET PROMPT = "$P$G""$P" lists the current directory; "$G" displays a ">" character. For more information, see your DOS manual.To set a path for a program called DAILY in the REPORTS subdirectory beneath drive G:, add the following line:  SET PATH = "G:\REPORTS"This sets the variable PATH to G:\REPORTS.Setting the variable PATH in the login script removes search drives previously assigned. Use SET PATH only before you map search drives.To display this path, include PATH as an identifier variable in a WRITE command by enclosing the variable (not the value) in angle brackets.For example, the following line would display "My path is G:\REPORTS."  WRITE "My path is" ;<path>To include a DOS environment variable in a MAP command, precede the variable with a percent sign (%).For example, to set and map a drive to the DOS variable NWS:, include the following lines in a login script:  SET NWS = "C:\XYZ"  MAP S16:=%<NWS>For more about using the DOS SET command, see your DOS manual.For more about using DOS environment variables as identifier variables in other login script commands, IDREF="FM58742"see "Identifier Variables" on page 180.ID="FM57858"SHIFTUse idxid="w3816"book="_idx" docset="nw312" tidref="i6337"idxid="w3817"book="_idx" docset="nw312" tidref="i3452"SHIFT to change the order that %n identifier variables are interpreted in the login script. SHIFT allows users to enter LOGIN parameters in any order.Command Format  SHIFT [n]Replace n with the number of places you want the variable to shift. The default is 1.Using SHIFTYou can shift up to 10 arguments.When users execute LOGIN, they can include additional parameters. Each of these parameters is assigned a %n variable.This makes it so that the parameter's real value can then be substituted for the %n variable that appears in the login script.In the login script, you can add the SHIFT command with a positive or negative number to move the variables in either direction. For example, SHIFT -3 moves each %n variable three positions to the left.idxid="w3818"book="_idx" docset="nw312" tidref="i3481"ExampleWhen Mary logs in, she wants to access her word processing program, change the way it is set up, and map a drive to her work directory called ACCNTS.Mary also has a command in her login script to map a drive to her LOTUS directory, but she does not need it today.The commands in Mary's login script are shown below.   LOOP  IF "%2"="WP" THEN   SET WP="\U-CML\B-10\D"  MAP S16:=SYS:APPS\WP\SETUP  IF "%2"="ACCNTS" THEN MAP G:=SYS:ACCNTS  IF "%2"="LOTUS" THEN MAP S16:=SYS:APPS\LOTUS  SHIFT 1  IF "%2" <> " " THEN GOTO LOOP(In the last line, "IF "%2" <>" is followed by a space enclosed in quotation marks, which means "If %2 isn't blank.")With these commands in her login script, Mary can log in as follows:   LOGIN FS1\MARY WP ACCNTSThe parameters in Mary's LOGIN command are given the following values: %0 = FS1%1 = MARY%2 = WP%3 = ACCNTS Mary's login script looks for %2, which is WP, and sets the word processing environment.Then the login script shifts the variables one to the right so that %2 now becomes ACCNTS. Upon executing the loop, the login script maps a drive to the ACCNTS directory. Mary could also change the order of her LOGIN command without affecting the way her work environment is set up.  LOGIN MARY ACCNTS WPThe parameters in this LOGIN command are given the following values: %0 = FS1%1 = MARY%2 = ACCNTS%3 = WP In this case, Mary's login script looks for %2, which is now ACCNTS. The login script maps a drive to the ACCNTS directory. Then the login script shifts the variables to the right so that %2 now becomes WP. Upon executing the loop, the login script sets the word-processing environment.For more about using %n variables in login scripts, IDREF="FM27425"see "Login Script Commands and Variables" on page 148.ID="FM10783"WRITEUse idxid="w3819"book="_idx" docset="nw312" tidref="i7548"idxid="w3820"book="_idx" docset="nw312" tidref="i3452"WRITE to display messages when a user logs in.Command Format   WRITE "[text][%IDENTIFIER]" [;][identifier]Replace text with the words you want to display on the screen.Replace identifier with a variable you want to display, such as a user's login name.Using WRITEText you want to display must be enclosed in quotation marks (" ").There are two ways to display identifier variables in a WRITE command.You can type the identifier variable preceded by a semicolon (;), or you can enclose an identifier variable inside quotation marks, precede it with a percent sign (%), and type it in uppercase letters. This is often used when combining regular text with an identifier variable, because both the text and the variable can be enclosed in the same quotation marks.To join several text strings and identifier variables into a single display without enclosing the variables in quotation marks, use a semicolon between the text and the variables.If you have several WRITE commands, each one will appear on a separate line on your workstation, unless you put a semicolon at the end of all but the last WRITE commands.Then the displays appear as one continuous sentence or paragraph (although they may wrap onto additional lines on the screen).Text strings can also include the following: WIDTH="96"CharacterWIDTH="216"MeaningWIDTH="96"\rWIDTH="216"Carriage return\nNew line\"Embedded quotation mark\7Beep soundIn addition to the semicolon, there are additional operators you can use to form compound strings (in other words, to join text and identifier variables into one command).These operators are listed in the following table, in order of precedence. WIDTH="96"OperatorWIDTH="216"MeaningWIDTH="96";WIDTH="216"Join* / % Multiply, divide, modules+ - Add, subtract>> << Shift left or right (1000 >> 3 becomes 1)idxid="w3821"book="_idx" docset="nw312" tidref="i3481"ExamplesTo display the message "Hello," add the following line to the login script:  WRITE "Hello"To display the user's name along with a greeting, add the identifier LOGIN_NAME to the command.To do this, join the text and the identifier with a semicolon, or include the variable in the quotation marks with the text.Either of the following lines displays "Hello, Bob" when user Bob logs in:  WRITE "Hello, ";LOGIN_NAME  WRITE "Hello, %LOGIN_NAME"For more information about using identifier variables, see the following section, "Identifier Variables."ID="FM58742"Identifier VariablesWith many login script commands, you can take advantage of identifier variables to make your script more efficient and flexible.idxid="w3822"book="_idx" docset="nw312" tidref="i2759"Identifier variables allow you to enter a variable (such as LOGIN_NAME) in a login script command, rather than a specific name (such as RICHARD).By using the variable, you can make the login script command applicable to many users instead of limiting it to user Richard.When the login script executes, it substitutes real values for the identifier variables. Therefore, when Richard logs in, the command  WRITE "Hello, ";LOGIN_NAMEdisplays the following message on Richard's screen:  Hello, RichardSimilarly, when Mary logs in, the message she sees is:  Hello, MaryIn the above example, when the user logged in, the name she used to log in with was substituted for the LOGIN_NAME variable in the command.Identifier Variable ConventionsWhen using idxid="w3823"book="_idx" docset="nw312" tidref="i2759"identifier variables in login script commands, observe the following:Identifier variables are used most often with commands such as IF...THEN, MAP, and WRITE. They can also be used with commands for which you can specify a path, such as COMSPEC.Type the variable exactly as shown.To use DOS environment variables as identifiers, enclose them in angle brackets.Identifier variables can be placed within literal text strings in a WRITE statement.However, the identifier variable must be in uppercase letters and preceded by a percent (%) sign. (Literal text is text that is displayed on screen, such as "Sales report is due today." Enclose literal text in quotation marks.)idxid="w3824"book="_idx" docset="nw312" tidref="i3481"ExamplesIf Mary logs in during the morning, both of the following lines would display the same message on her screen ("Good morning, Mary"):  WRITE "Good ";GREETING_TIME"," ;LOGIN_NAME  WRITE "Good %GREETING_TIME, %LOGIN_NAME"To use DOS environment variables as identifiers, enclose them in angle brackets. The following example uses the DOS environment variable "path."  WRITE "my path is " ;<path>The text displayed would be similar to  my path is z:.;y:.;c:\WINDOWSSetting the variable PATH in the login script removes search drives previously assigned. Use SET PATH only before you map search drives. For more information about SET, IDREF="FM74868"see "SET" on page 173.IDREF="FM38017"Table 4-3 lists identifier variables.LBL="4-3" INLINE="F"ID="FM38017"idxid="w3825"book="_idx" docset="nw312" tidref="i2759"Identifier VariablesWIDTH="84"CategoryWIDTH="120"Identifier VariableWIDTH="216"FunctionWIDTH="84"DateWIDTH="120"DAYDAY_OF_WEEKMONTHMONTH_NAMENDAY_OF_WEEKSHORT_YEARYEARWIDTH="216"Day number (01 through 31).Day of week (Monday, Tuesday, etc.).Month number (01 through 12).Month name (January, February, etc.).Weekday number (1 through 7, with 1=Sunday).Last two digits of year (90, 91, 92, etc.).All four digits of year (1990, 1991, 1992, etc.).TimeAM_PMGREETING_TIMEHOURHOUR24MINUTESECONDDay or night (am or pm).Time of day (morning, afternoon, or evening).Hour (12-hour scale; 1 through 12).Hour (24-hour scale; 00 through 23,  00=midnight).Minute (00 through 59).Second (00 through 59).UserFULL_NAMELOGIN_NAMEMEMBER OF "group"NOT MEMBER OF  "group"PASSWORD_EXPIRESUSER_IDUser's full name.User's unique login name.Group that the user is assigned to.Group that the user is not assigned to.Number of days before password expires.Number assigned to each user for mail  directories, etc.NetworkFILE_SERVERNETWORK_ADDRESSNetWare server name.Network number of the cabling system (8-digit  hexadecimal number).WorkstationDOS_REQUESTERMACHINENETWARE_REQUESTEROSOS_VERSIONP_STATIONSHELL_TYPESMACHINESTATIONVersion of the workstation's DOS shell (1.02, etc.)  Supports v2.x and v3.x shells.Type of computer (IBM_PC, etc.). See your DOS  manual for more information. (non-OS/2)Version of the NetWare Requester for OS/2 (2.00,  etc.).Type of DOS on the workstation (MSDOS, DR  DOS).Version of DOS on the workstation (3.30, 6.0,  etc.).Workstation's node address (12-digit hex).Version of the workstation's DOS shell (1.02, etc.)  Supports v2.x and v3.x shells. Short machine name (IBM, etc.) (non-OS/2).Workstation's connection number.DOS  Environment<variable>Any DOS environment variable can be used in  angle brackets (<path>, etc.).To use a DOS environment variable in a MAP  command, add a percent sign (%) in front of the  variable, such as MAP S16:=%<path>.MiscellaneousACCESS_SERVERERROR_LEVEL%nShows whether the access server is functional  (TRUE=functional, FALSE=not functional).An error number (0=No errors).Replaced by parameters the user enters at the  command line with the LOGIN utility. ID="FM82950"Using LOGIN Parameters with idxid="w3826"book="_idx" docset="nw312" tidref="i8"%n VariablesSome variables in a login script can be indicated by a percent sign (%) followed by a number from 0 to 9.When users log in, they can type additional parameters that the LOGIN utility passes to their login script. The login script then substitutes these parameters for any %n variables in the script.These variables are replaced in order, by the parameters the users type when they execute LOGIN.%0 is always replaced by the name of the first NetWare server the user connected to, and %1 always indicates the user's login name. The remaining variables change, depending on what the user typed when he or she executed LOGIN.The SHIFT login script command allows you to change the order in which these %n variables are substituted (IDREF="FM57858"see "SHIFT" on page 175).idxid="w3827"book="_idx" docset="nw312" tidref="i3481"ExampleA login script contains the following commands:  IF "%2" = "SALES" THEN  WRITE "Meeting today"  END  IF "%3" = "LEGAL" THEN  WRITE "Report is due tomorrow"  ENDIf user RON logged in by typing  LOGIN COUNT\RON SALES MARKETINGthen the login script would substitute the values Ron entered at the keyboard for the %n variables in the script, as shown below:%0 = COUNT%1 = RON%2 = SALES%3 = MARKETINGSince %2 is replaced by "SALES," the message "Meeting today" is displayed on Ron's screen.However, since %3 is replaced by "Marketing," Ron will not see the message "Report is due tomorrow."ID="FM41942"Examples of Login ScriptsThe following examples of login scripts may help you plan your own system and user login scripts.Each example script is shown in a table. The left column of the table shows the commands in the script. The right column explains the command.ID="FM58770"Default idxid="w3828"book="_idx" docset="nw312" tidref="i3477"idxid="w3829"book="_idx" docset="nw312" tidref="i3481"Login ScriptThe default login script executes every time SUPERVISOR logs in until a personal script is created for the supervisor. It also executes for users who do not have user login scripts.You cannot modify the default script. Instead, create system or user scripts.LBL="4-4" INLINE="F"Default login scriptWIDTH="216"Login script commandsWIDTH="192"PurposeWIDTH="216"MAP DISPLAY OFFWIDTH="192"Prevents map commands from displaying  on the screen.MAP ERRORS OFFPrevents mapping errors from displaying  on the screen.Rem: Set 1st drive to most appropriate directory.Remark; explains the following commands.MAP *1:=SYS:Maps the first drive to volume SYS:.MAP *1:=SYS:%LOGIN_NAMEMaps the first drive to the user's home  directory. If the user has no home directory,  the first drive is still mapped to SYS:.IF "%1"="SUPERVISOR" THEN MAP  *1:=SYS:SYSTEMIf the login name is SUPERVISOR, it maps  the first drive to SYS:SYSTEM instead of to  the user's home directory.Rem: Set search drives.Remark; explains the following commands.MAP S1:=SYS:PUBLICThe first search drive is mapped to  SYS:PUBLIC, where DOS-based NetWare  utilities are stored.MAP S2:=S1:%MACHINE\%OS\%OS_VERSIONThe second search drive is mapped to the  directory where DOS is stored.Rem: Now display current drive settings.Remark; explains the following commands.MAP DISPLAY ONAllows map commands to display.MAPDisplays a list of all drive mappings on the  user's screen.Use the default login script temporarily. The default login script is contained in the LOGIN.EXE file in SYS:LOGIN and cannot be edited.Create a system login script before you edit user login scripts. Include as much as possible in the system login script. The more the system login script accomplishes, the shorter user login scripts can be.If you want to execute a system login script and do not want user login scripts to execute,Place the EXIT command at the end of the system login script. This causes login script processing to end before checking for the user login script. No user login scripts can execute.Use the script option of the LOGIN command.This option executes a file containing valid commands. It will not use the system, user, or default login scripts. Since the login script attaches before executing the script option, the file can be located on the network. The following command will execute only the system login script:  LOGIN /S SYS:PUBLIC\NET$LOG.DATFor OS/2, use:  LOGIN /S server name\SYS:PUBLIC\NET$LOG.DATOther users could remove the /s option and have their own login scripts.ID="FM73754"System idxid="w3830"book="_idx" docset="nw312" tidref="i3513"idxid="w3831"book="_idx" docset="nw312" tidref="i3481"Login ScriptThe system login script should contain as much information as possible that applies to all users. LBL="4-5" INLINE="F"Sample system login scriptWIDTH="204"Login script commandsWIDTH="216"PurposeWIDTH="204"MAP DISPLAY OFFWIDTH="216"Prevents map commands from displaying on the  screen as they are assigned.MAP ERRORS OFFPrevents mapping errors from displaying on the  screen.MAP *1:=SYS:Maps the first drive to volume SYS:.MAP *1:=SYS:%LOGIN_NAMEMaps the first drive to the user's home directory.  If the user has no home directory, the first drive is  still mapped to SYS:.IF "%1"="SUPERVISOR" THENMAP *1:=SYS:SYSTEMIf the login name is SUPERVISOR, it maps the first  drive to SYS:SYSTEM instead of to the user's  home directory.IF OS = OS/2 THENMAP *2:=SYS:PUBLIC\OS2ELSEMAP S1:=SYS:PUBLICMAP S2:=SYS:PUBLIC\%MACHINE\%OS\  %OS_VERSIONENDIf the user logs in from an OS/2 workstation, the  second network drive is mapped to the directory  where NetWare utilities for OS/2 are stored.If the user is not using an OS/2 workstation, the  first search drive is mapped to SYS:PUBLIC, where  DOS-based NetWare utilities are stored. The second search drive is mapped to the  directory where DOS is stored.For example, If all workstations use DOS, use the  following two commands instead of the IF...THEN  command:MAP INS S1:=SYS:PUBLICMAP INS S2:=SYS:PUBLIC\  %MACHINE\%OS\%OS_VERSIONMAP S16:=VOL1:APPL\WPMaps the next available search drive to the  directory that contains WordPerfect.MAP S16:=VOL1:APPL\LOTUSMaps the next available search drive to the  directory that contains Lotus.MAP S16:=SYS:EMAILMaps the next available search drive to the E-mail  directory.IF MEMBER OF "MANAGERS" THENMAP *3:=VOL1:PROJECTS\REPORTSIf the user belongs to the MANAGERS group  object, the script maps the third network drive to  the REPORTS directory.IF MEMBER OF "TESTERS" THENMAP *3:=INPUT:STATUS\UPDATESIf the user belongs to the TESTERS group object,  the script maps the third network drive to the  UPDATES directory.COMSPEC = S2:COMMAND.COMSets COMSPEC to the DOS command processor,  located in the DOS directory (in the second  search drive).SET PROMPT = "$P$G"Sets the prompt to display the user's current  directory path, followed by the > symbol.MAP DISPLAY ONAllows map commands to display.MAPDisplays a list of all drive mappings.WRITEDisplays a blank line between the list of mappings  and following lines.WRITE "Good %GREETING_TIME,  %LOGIN_NAME."Displays a greeting to the user. Example: "Good  morning, MARY."WRITE "Your password expires in  %PASSWORD_EXPIRES days."Displays a message indicating the number of days  before the user's password expires.FIRE PHASERS 3 TIMESMakes the phaser sound occur three times.ID="FM31371"User idxid="w3832"book="_idx" docset="nw312" tidref="i3537"idxid="w3833"book="_idx" docset="nw312" tidref="i3481"Login ScriptThe following is an example of a user login script for Mary. (The user login script executes after the system login script.) LBL="4-6" INLINE="F"ID="FM50259"Sample user login scriptWIDTH="228"Login script commandsWIDTH="180"PurposeWIDTH="228"MAP DISPLAY OFFWIDTH="180"Prevents map commands from displaying  on the screen as they are assigned.MAP ERRORS OFFPrevents mapping errors from displaying  on the screen.MAP *4:=VOL1:MARY\PROJECTS\RESEARCHMaps Mary's fourth network drive (after  those assigned in system scripts) to the  RESEARCH subdirectory in her home  directory.MAP *5:=VOL1:FORMSMaps Mary's fifth network drive (after  those assigned in system scripts) to the  FORMS directory.REM Mary needs access to FORMS while she's on theREM troubleshooting team. Remove this mappingREM when she's reassigned.This is a reminder to the person who  created the login script.This remark will not display on the user's  screen. (Because the remark is several lines  long, each line starts with the keyword  REM.)SET WP="/u-mjr/b-5"Sets Mary's environment variables for  WordPerfect.SET EMAIL USER="mrichards"Sets Mary's user name (mrichards) forE-mail.#CAPTURE Q=FAST_Q NB TI=10 NFF Executes the CAPTURE utility so Mary can  print from non-network applications.PCCOMPATIBLEEXIT "NMENU TRAINING"Stops the user login script and sends the  user into a menu program called  TRAINING.(DOS workstations with the machine  name IBM_PC and OS/2 workstations do  not need the PCCOMPATIBLE line.)Where to Go from HereWIDTH="156"ToWIDTH="156"SeeOptimize your server's  performanceIDREF="FM82264"Appendix A, "Optimizing  Network Performance," on  page 313.Install a print serverbook="print" docset="nw312"Print ServerSet up workstations to do file  server commands"book="sysadmin" docset="nw312"Remote Management" in System  Administration.LBL="0"Upgrade an Existing File ServerID="FM29133"Upgrade OverviewUpgrade an existing NetWare v2.1x or v3.x file server to v3.12 using either the NetWare Migration Utility, or the NetWare In-Place Upgrade NLM.The idxid="w3834"book="_idx" docset="nw312" tidref="i4313"NetWare Migration utility, a workstation-based utility, allows you to transfer your network information from a NetWare v2.x or v3.x server to an existing v3.12 server that is on the same network.The idxid="w3835"book="_idx" docset="nw312" tidref="i2792"In-Place Upgrade NLM, a server-based utility, allows you to change your network server that is running NetWare v2.1x or higher into a NetWare v3.12 server without purchasing additional hardware.Upgrade an idxid="w3836"book="_idx" docset="nw312" tidref="i3145"IBM LAN Server v1.3 and idxid="w3837"book="_idx" docset="nw312" tidref="i5038"PCLP v1.3 to a NetWare v3.12 file server using the NetWare Migration utility.Steps for upgrading a NetWare v2.1x or v3.x server are:Choose the Migration or In-Place Upgrade option by reading IDREF="FM51581"Chapter 5, "Choose Migration or In-Place Upgrade."Upgrade your server by following the procedures in either IDREF="FM51581"Chapter 6, "Upgrade Using Migration," on page 221, or IDREF="FM51148"Chapter 7, "Upgrade Using In-Place Upgrade," on page 265.Prepare and install workstation equipment. See the followingbook="ws_get" docset="nw312"Workstation Basics and Installation.book="ws_dos" docset="nw312"NetWare Workstation for DOS and Windows.book="ws_os2" docset="nw312"NetWare Workstation for OS/2.(Optional) Bring your servers up to peak performance by reading IDREF="FM82264"Appendix A, "Optimizing Network Performance," on page 313.(Optional) Install Novell ElectroText€ by reading IDREF="FM87545"Appendix B, "Installing and Using Novell ElectroText," on page 335.Set up your network printing environment by reading book="print" docset="nw312"Print Server.LBL="5"ID="FM51581"Choose Migration or In-Place UpgradeOptions for Upgrading Your Existing File ServerTo upgrade an existing NetWare v2.1x or v3.x server, use either the NetWare Migration utility or the NetWare In-Place Upgrade NLM. This section provides you with information to help you decide which utility is best for you.IDREF="FM45495"Table 5-1, "NetWare Upgrade Options," on page 198 gives you a brief explanation of upgrade options and the advantages of one option over another.The NetWare Migration utility may be used using one of two methods: "Across-the-Wire Migration" and "Same-Server Migration." IDREF="FM45495"Table 5-1 lists both methods.For a complete discussion of the NetWare Migration utility, see IDREF="FM14558""What a Migration Does" on page 200.For a complete discussion of the NetWare In-Place Upgrade NLM, see IDREF="FM29387""What an In-Place Upgrade Does" on page 216.LBL="5-1" INLINE="F"ID="FM45495"NetWare idxid="w3838"book="_idx" docset="nw312" tidref="i7086"Upgrade OptionsWIDTH="108"UpgradeWIDTH="108"Options AvailableWIDTH="96"AdvantagesWIDTH="108"DisadvantagesNetWare v2.x to  v3.12Across-the-Wire to an  installed v3.12 server  (IDREF="FM94462"on page 226)No risk of data  loss.Can migrate many  servers to one  server.Can choose what  data you want to  migrate.Can direct data to  specific volume or  directory.Need a v3.12 server  installed.Same-Server  migration (IDREF="FM81630"on page  247)Can choose what  data you want to  migrate.Some risk of data loss.Need a workstation  (or tape backup) with  enough disk space for  data files.In-Place Upgrade  from v2.1x or v2.2 to  v3.12 (IDREF="FM26458"on page 265)Just need one  v2.1x serverCannot upgrade from  v2.0a.Need an 80386 or  higher processor.If upgrade fails, you  may have to restore  your v2.1x data from  backup.NetWare v3.x to  v3.12Across-the-Wire  migration to an  installed v3.12 server  (IDREF="FM94462"on page 226)No risk of data  loss.Can migrate many  servers to one  server.Can choose what  data you want to  migrate.Can direct data to  specific volume or  directory.Need a v3.12 server  installed.Same-Server  migration (IDREF="FM81630"on page  247)Can choose what  data you want to  migrate.Some risk of data loss.Need a workstation  (or tape backup) with  enough disk space for  data files.NetWare v3.x to  v3.12In-Place Upgrade  from v3.x to v3.12  (IDREF="FM23283"on page 299)Just need one v3.x  server---no  additional  hardware needed.Cannot upgrade from  v3.0.If upgrade fails, may  have to restore  original data from  backup.LAN Server or PCLP to  NetWare v3.12Across-the-wire  migration procedures  (IDREF="FM94462"on page 226)No risk of data  loss.Additional hardware  needed.LAN Server or PCLP to  NetWare v3.12Same Server  migration procedures  (IDREF="FM51807"on page 202)No additional  hardware needed.Some risk of data loss.Need a workstation  (or tape backup) with  enough disk space for  data files.ID="FM14558"What a Migration DoesThe Migration utility converts servers from NetWare v2.1x or 3.x, or from another operating system, to NetWare v3.12 using either of two methods:Across-the-Wire, where you move network information from a NetWare v2.x or v3.x server to a v3.12 server that is on the same network (IDREF="FM94462"see page 226 for procedures).Same-Server, where you change your NetWare v2.x or v3.x server to a v3.12 server (IDREF="FM81630"see page 247 for procedures).All references to NetWare v2.1x throughout this manual include NetWare v2.2.Across-the-Wire MigrationIn idxid="w3839"book="_idx" docset="nw312" tidref="i128"idxid="w3840"book="_idx" docset="nw312" tidref="i3896"across-the-wire migration, files are migrated from a source server across the network to the destination server. Selected bindery information is migrated to a working directory on the local hard drive, translated to NetWare v3.12 format, and then migrated to the destination server.For information on binderies, see "book="concepts" docset="nw312"Bindery" inConcepts.Across-the-wire migration allows you to preserve your user environment (users and their trustee assignments), as well as default account restrictions, accounting methods, print queues, and print servers. These entities are all contained in the bindery. A bindery is a database that contains definitions for entities such as users, groups, workgroups, NetWare servers, and print servers. When you use across-the-wire migration, you can choose either the standard or the custom migration option.The standard option provides the easiest path for a simple migration: it migrates all information from the NetWare v2.x or v3.x server across the network to a NetWare v3.12 server.You can migrate multiple servers with this option, one at a time.The custom option lets you select specific information from the bindery and data files so that you can upgrade a server or several servers (one at a time) and create a customized destination server.IDREF="FM66613"Figure 5-1idxid="w3841"book="_idx" docset="nw312" tidref="i128"idxid="w3842"book="_idx" docset="nw312" tidref="i3896"illustrates the across-the-wire method.LBL="5-1"ID="FM66613"Across-the-wire MigrationFILE="n312i76a.pbm"ID="FM51807"Same-Server MigrationA idxid="w3843"book="_idx" docset="nw312" tidref="i6117"idxid="w3844"book="_idx" docset="nw312" tidref="i3896"same-server migration updates a server that will be installed on the same hardware as the old source server, allowing you to change your NetWare v2.x or v3.x server into a v3.12 server.Unlike across-the-wire migration which utilizes two computers, same-server migration involves only one. There is, however, some risk to the data during the migration process. Also, you may not be able to migrate file attributes (because the same-server method does not migrate data files).When you use the same-server method, you can use only the custom option because you cannot migrate data files. You must back up your data files and then restore them to the NetWare v3.12 server after it is installed.IDREF="FM90063"Figure 5-2 on page 203 illustrates the same-server method.LBL="5-2"ID="FM90063"Same-Server Migration idxid="w3845"book="_idx" docset="nw312" tidref="i6117"idxid="w3846"book="_idx" docset="nw312" tidref="i3896"FILE="n312i75a.pbm"See the following chart for specific page references for across-the-wire and same-server procedures.WIDTH="84"If you chooseWIDTH="228"SeeWIDTH="84"Across-the-WireWIDTH="228"IDREF="FM94462""Across-the-Wire Migration" on page 226.Same-ServerIDREF="FM81630""Same-Server Migration" on page 247.How Data Is Migrated Across the WireMigrating FilesThe migration utility leaves the source server intact and only copies information to the destination v3.12 server.NetWare v2.x or v3.xidxid="w3847"book="_idx" docset="nw312" tidref="i6656"idxid="w3848"book="_idx" docset="nw312" tidref="i3896"system files are not migrated.Any file on a source server that has the idxid="w3849"book="_idx" docset="nw312" tidref="i2300"same name as one that exists on the destination server is not copied to the destination server. An error message appears on the screen during the migration, and is also written to the migration report, to let you know that a file by that name already exists on the destination server. If the file already exists, rename the file and copy it to the destination server after migration.The idxid="w3850"book="_idx" docset="nw312" tidref="i3442"idxid="w3851"book="_idx" docset="nw312" tidref="i3896"system login script is not migrated, but user login scripts are. Examine each user login script after migration and make corrections if the server name or path names have changed.Migrating DirectoriesIf a idxid="w3852"book="_idx" docset="nw312" tidref="i1450"idxid="w3853"book="_idx" docset="nw312" tidref="i3896"directory is being migrated that has the idxid="w3854"book="_idx" docset="nw312" tidref="i1759"idxid="w3855"book="_idx" docset="nw312" tidref="i3896"idxid="w3856"book="_idx" docset="nw312" tidref="i3981"same name and path as a directory that already exists on the NetWare v3.12 server, the files from both directories are merged under the destination directory name. The directory structure and files are migrated and become a part of the v3.12 file system. If necessary, modify the organization on the destination server after all source servers are migrated.Migrating idxid="w3857"book="_idx" docset="nw312" tidref="i7173"idxid="w3858"book="_idx" docset="nw312" tidref="i3896"UsersUsers on the source server are created as new users on the destination server. Account restrictions and user designations for existing users are copied. Users with the same username are merged; that is, their user designations are added together. Custom idxid="w3859"book="_idx" docset="nw312" tidref="i3896"idxid="w3860"book="_idx" docset="nw312" tidref="i1293"MigrationThe custom option lets you select specific information from the bindery and data files so you can upgrade a server or several servers (one at a time) and create a customized destination server.IDREF="FM52992"Table 5-2 shows the information you can migrate using the custom migration option.ID="FM30240"LBL="5-2" INLINE="F"ID="FM52992"Information that can be migrated using the idxid="w3861"book="_idx" docset="nw312" tidref="i1293"custom migration optionWIDTH="108"Category to be migratedWIDTH="312"DescriptionWIDTH="108"All InformationWIDTH="312"Migrates all information listed in this table.Data FilesMigrates all data files and their DOS and NetWare attributes for files and  directories to the corresponding v3.12 attributes.For details on what the corresponding attributes are, see IDREF="FM64329""Migrating File  Attributes" on page 210.Data files are not migrated for same-server migration.Trustee AssignmentsMigrates rights assigned to users and groups for directories and files to  corresponding v3.12 rights.If you select this category, you must also select "Users," "Groups," and  "Data Files" if the users and data files do not already exist on the  destination server.If you migrate "Trustee Assignments" and the corresponding users and  groups do not exist on the destination server, or the directories do not  exist, a series of error messages appears.For details on what the corresponding rights are, see IDREF="FM17346""Migrating Directory  Attributes" on page 213.UsersMigrates the following, unless they already exist on the destination server:UsersUser print job configurations idxid="w3862"book="_idx" docset="nw312" tidref="i5454"(PRINTCON.DAT)User login scripts for both DOS and OS/2 ( idxid="w3863"book="_idx" docset="nw312" tidref="i3563"LOGIN.BAK is not  migrated)User RestrictionsMigrates idxid="w3864"book="_idx" docset="nw312" tidref="i89"account restrictions, idxid="w3865"book="_idx" docset="nw312" tidref="i6516"station restrictions (not migrated from LAN  Server), and idxid="w3866"book="_idx" docset="nw312" tidref="i6777"time restrictions. If a user exists on the destination server, his  or her restrictions are not overwritten.If you select this category, you must also select "Users."If a user with a corresponding set of restrictions doesn't exist on the  destination server, then the restrictions set on the source server are  migrated to the destination server and are not overwritten or merged by  any subsequently migrated source servers.Volume and disk restrictions for users do not get migrated because of  differences in NetWare v2.x and v3.12. In v2.x, the restrictions were  server-wide, whereas in v3.12 the restrictions are volume-specific.GroupsMigrates the Group's members and assigned group trustee rights for  directories and files. Groups that existed on the source server remain  intact.If multiple source servers are migrated, then groups from the servers are  merged on the destination server.Default Account  RestrictionsMigrates default account restrictions. Default account restrictions on the  destination server are overwritten by any source server that also has  default account restrictions. The set of default restrictions includesAccount balance and low limitAccount expiration dateConcurrent connections limitGrace loginsHome directory for usersIntruder detectionPassword minimum lengthPeriodic password intervalTime restrictionsAccounting  InformationMigrates the accounting charge method chosen to charge for services  (blocks read, blocks written, connect time, disk storage, service requests).Migrates account servers.Charge rates that exist on the source server are left intact.Print Queues and  Print ServersLAN Server only migrates print queues. NetWare migrates the following:Print queuesPrint queue operators and usersPrint queue serversPrint queue statusPrint serversPrint server operators and usersPrint server control filesIDREF="FM87105"Table 5-3 describes LAN Server components that do not get migrated.LBL="5-3" INLINE="F"ID="FM35863"LAN Server idxid="w3867"book="_idx" docset="nw312" tidref="i3135"components that are not migratedWIDTH="96"LAN Server componentWIDTH="168"ExplanationWIDTH="144"NetWare equivalentWIDTH="96"ALERTERWIDTH="168"Notifies the administrator of defined  events. WIDTH="144"None, but NetWare keeps track  of many of these events.ATGives Execute command at a set time.None.AUTO LOG OFFShuts the system down after  extended inactivity.None.External resourcesThese don't apply to NetWare.None.MACHINE IDUnique workstation name.Use network board ID.NETRUNAllows you to run programs at the  server.None.REPLICATORPeriodically duplicates selected files.None.RIPLRemote Initial Program Load.Remote Reset or Remote Boot:  The Remote Boot image file must  be set up on the NetWare server.Station restrictionsDefines which machine ID can be  used by a username to log in to the  LAN Server domain.Station Restrictions: Must be set  up using NetWare and LAN card  ID.How Rights and Attributes are MigratedIn NetWare v2.x, rights are assigned only at the directory level. In NetWare v3.12, idxid="w3868"book="_idx" docset="nw312" tidref="i5944"idxid="w3869"book="_idx" docset="nw312" tidref="i556"rights are assigned at the file and directory levels. When you use the across-the-wire migration, all NetWare v2.x rights and attributes are translated into the v3.12 format. The Maximum Rights Mask is replaced with an Inherited Rights Mask, which allows rights to flow down the directory structure.The tables beginning IDREF="FM73775"on page 209 list the corresponding NetWare v3.12 rights and attributes. There is no change in directory and file rights in any v3.x version.Migrating Directory and File RightsIn NetWare v3.12, rights are granted for a specific directory or file by trustee assignments. A user with a trustee assignment to a directory or file is a trustee of that directory or file.If you are migrating from LAN Server, LAN Server permissions (rights) do not flow down, but are limited to the directory where they are set. After the migration to NetWare v3.12, rights do flow down the directory structure.IDREF="FM73775"Table 5-4 on page 209 shows the directory and file rights for NetWare versions 2.1x, 2.2, 3.11, and 3.12. There is no change in directory and file rights from NetWare v3.1x to v3.12.LBL="5-4" INLINE="F"ID="FM73775"Evolution of directory and file idxid="w3870"book="_idx" docset="nw312" tidref="i5944"rightsWIDTH="120"RightWIDTH="144"DescriptionWIDTH="144"Changes in v3.12WIDTH="120"Supervisory (v3.11)WIDTH="144"Grants all rights to the directory,  its files, and its subdirectories.WIDTH="144"Name change to Supervisor.Create (all versions)  [directories, files]Assigned only if Open is also  assigned.Creates subdirectories without  Access Control (was Parental).Delete (v2.1x)  [directories, files]Erase (v2.2, v3.11)Deletes directories and files.Name change to Erase.Modify (v2.1x) [files]Modify (v2.2, v3.11)  [directories, files]Renames directories or files or  changes their attributes.No longer requires Access  Control to rename directories,  files, or attributes.Open (v2.1x)  [directories, files]Opens files and directories.Assigned automatically with  Read, Write, and Create.Read and Open (v2.1x)  [files only]Read (v2.2, v3.11)Reads and scans files and  directories.A separate Open right is no  longer required.Parental (v2.1x)  [directories, files]Access Control(v2.2, v3.11)The trustee assignments and  Inherited Rights Filters control  how other objects can access  the object.Rights assigned with Access  Control can be revoked at the  subdirectory and file level.No longer assigns the right to  create or rename subdirectories.Search (v2.1x)[directories, files]File Scan (v2.2, v3.11)  [directories, files]Searches/scans files and  directories.Includes the right to search to  the root of a directory. Assigned automatically when  any rights are assigned.Write and Open (v2.1x)  [files only]Write (v2.2, v3.11)  [directories, files]Allows the user to write to files  or directories.Open right is no longer  required; Write is sufficient.ID="FM49536"ID="FM64329"Migrating File AttributesNetWare v3.12 reads attributes that you set (for example, to compress or back up a file) or sets attributes to tell you what has been done (for example, that a file is compressed or migrated).IDREF="FM95041"Table 5-5 shows file attributes for NetWare versions 2.1x to 2.2, v3.11, and v3.12.For additional information, see "book="concepts" docset="nw312"Attributes" and "book="concepts" docset="nw312"Security" in Concepts.LBL="5-5" INLINE="F"ID="FM95041"Evolution of file idxid="w3871"book="_idx" docset="nw312" tidref="i556"attributesWIDTH="120"AttributeWIDTH="180"DescriptionWIDTH="120"Changes in v3.12WIDTH="120"Copy Inhibit (v3.11)WIDTH="180"Prevents Macintosh users from copying  a file. Overrides Read and File Scan  rights.Modify right required to remove this  attribute.WIDTH="120"No change.Delete Inhibit (v3.11)Prevents users from erasing files.  Overrides Erase right. Modify right  required to remove this attribute.No change.Execute Only(v2.1x to v2.2, v3.11)Prevents copying or backing up files. Thisattribute cannot be removed.Assign only to files with an .EXE or  .COM extension (program files).Keep a duplicate of these files in case  they become corrupted and need to be  replaced.CAUTION: Some programs will not  execute properly if flagged Execute  Only.No change.Hidden(v2.1x to v2.2, v3.11)Hides files from DOS DIR scans and  prevents them from being deleted or  copied.Files will appear in NetWare NDIR scan if  user has the File Scan right.No change.Indexed(v2.1x to v2.2, v3.11)Allows large files to be accessed quickly.  Automatically assigned to files with over  64 regular FAT entries. Can be set, but has no effect.No change.Modified Since Last  Backup (v2.1x)Archive Needed(v2.2, v3.11)[name change only]Identifies files modified after last  backup. Assigned automatically.Archive needed[same as v3.11].Purge (v3.11, v3.12)Purges a file as soon as it is deleted if the  file is flagged with this attribute or  resides in a directory flagged with this  attribute.CAUTION: Purged files cannot be  recovered with SALVAGE.No change.Read Only (All versions)Indicates whether a file can be modified. All files are automatically flagged Read  Write when they are created and can be  modified unless the Read Only attribute  is set. Assigning Ro automatically activates  Delete Inhibit and Rename Inhibit. Modify right required to remove the Ro  attribute.No change.Read Write (All versions)Set automatically when  the Read Only attribute  is not set.Rename Inhibit(v3.11, v3.12)Prevents users from renaming files.  Modify right required to remove this  attribute.No change.Shareable (All versions)Allows several users to access a file  simultaneously. Usually used in  combination with the Read Only  attribute.No change.Non-Shareable(All versions)Restricts multiple-user access to files.No character is displayed  to indicate the file is  non-shareable.System (All versions)Assign to system files. Hides these files  from DOS DIR scans and prevents them  from being deleted or copied.Files will appear in NetWare NDIR scans  if a user has the File Scan right.No change.Transactional(All versions)Activates the Transaction Tracking  System (TTS).Prevents data corruption by ensuring  that all changes are made to files being  modified or that none are. Especially helpful for database files.No change.ID="FM17346"Migrating Directory AttributesNo directory attributes were available in NetWare versions 2.0a, 2.1, 2.11, or 2.12. If you are migrating from any of these versions, set the directory attributes manually after the migration is complete.IDREF="FM83355"Table 5-6 shows directory attributes for NetWare versions 2.1x, 2.2, 3.11, and v3.12. For additional information, see "book="concepts" docset="nw312"Attributes" and "book="concepts" docset="nw312"Security" inConcepts.LBL="5-6" INLINE="F"ID="FM83355"Evolution of directory idxid="w3872"book="_idx" docset="nw312" tidref="i556"attributesWIDTH="120"AttributeWIDTH="180"DescriptionWIDTH="120"Changes in v3.12WIDTH="120"Delete Inhibit (v3.11)WIDTH="180"Prevents users from erasing directories.  Overrides Erase right. Modify right  required to remove this attribute.WIDTH="120"No changeHidden(v2.1x to v2.2, v3.11)Hides directories from DOS DIR scans  and prevents them from being deleted  or copied.Directories appear in NetWare NDIR  scan if user has the File Scan right.No changeNormal (v2.2)Indicates no attributes have been set.Not availablePrivate (v2.1x to v2.2)Allows users to see the directory but not  its subdirectories.You need to change the trustee  assignments (rights, not attributes) for  users that have access to directories  flagged Private.Grant these users only the Create right  to the directory.Not availablePurge (v3.11)Purges a file as soon as it is deleted if the  file is flagged with this attribute or  resides in a directory flagged with this  attribute.CAUTION: Purged files cannot be  recovered with SALVAGE.No changeRename Inhibit (v3.11)Prevents users from renaming  directories. Modify right required to  remove this attribute.No changeSystem (All versions)Assign to system directories.Hides these directories from DOS DIR  scans and prevents them from being  deleted or copied.Directories appear in NetWare NDIR  scans if a user has the File Scan right.No changeID="FM47391"Password MigrationID="FM49757"ID="FM45241"ID="FM98150"Passwords idxid="w3873"book="_idx" docset="nw312" tidref="i4980"are not migrated. The migration utility allows you to eitherAssign passwords that are generated randomly for all migrated users.Allow users to log in to the new system without a password. Passwords generated randomly are stored in a file called idxid="w3874"book="_idx" docset="nw312" tidref="i4594"NEW.PWD in SYS:SYSTEM on the NetWare v3.12 destination server and can only be accessed by the user SUPERVISOR.Strategies for Merging idxid="w3875"book="_idx" docset="nw312" tidref="i6425"Source ServersChoose one of several strategies to help you minimize the amount of time you spend customizing your v3.12 server after you migrate several servers to it.IDREF="FM52992"Table 5-2, "Information that can be migrated using the custom migration option," on page 205 shows the types and descriptions of information you can choose to migrate from a source server.Read through these categories and their descriptions; then see IDREF="FM73047""Setting Up Your Destination Server."ID="FM73047"Setting Up Your idxid="w3876"book="_idx" docset="nw312" tidref="i1397"Destination ServerWIDTH="108"ToWIDTH="312"ThenWIDTH="108"Set up default  account restrictions  on the destination  server.WIDTH="312"Set up the Default Account Balance/Restrictions on the first source server  and include that category in the information to be migrated. On subsequent source servers that you migrate to the same destination  server, do not migrate that category.Set up uniform user  restrictions on the  destination server.On the first source server, set up the Default Account Balances/Restrictions  with the values you want on the destination server.Choose "Users" and "Default Account Balances/Restrictions" as categories  to migrate, but do not choose "User Restrictions."On subsequent source servers, do not choose "User Restrictions" or  "Default Account Balances/Restrictions."Preserve each user's  individual user  restrictions.Choose "User Restrictions" for each source server.Merge users and  groups from several  source servers.Choose "Groups" and "Users" on all source servers.The corresponding users on the destination server are added to the  appropriate groups.Set up print queues  and print servers.Choose "Print Queues" and "Print Servers" on source servers. In NetWare v3.12, multiple printers can be serviced by each queue and  multiple queues can service the same printer.ID="FM29387"What an In-Place Upgrade DoesAn idxid="w3877"book="_idx" docset="nw312" tidref="i2778"in-place upgrade allows you to upgrade a NetWare 2.1x server to v3.12 using SERVER.EXE with the 2XUPGRDE.NLM.Upgrading a NetWare v2.1x or v2.2 server includes two parts:The file system is upgraded.The new operating system is installed.Upgrading a NetWare v2.1xfile system has four phases:The file system is analyzed/inventoried.The disks are analyzed.The disks are modified.A NetWare v3.12 bindery is created to replace the v2.1x bindery.IDREF="FM87105"Figure 5-3 illustrates the four phases.LBL="5-3"ID="FM87105"Phases in the Upgrade idxid="w3878"book="_idx" docset="nw312" tidref="i2778"FILE="n312i95a.pbm"For experienced installers, a complete set of instructions for the upgrade starts with IDREF="FM69414""Boot NetWare v3.12" on page 268.Following is a discussion of what happens during each phase of the upgrade. When you run the upgrade, status messages will refer to each of the actions discussed here.Phase 1: Analyzing the NetWare v2.1x File SystemEach disk is inventoried.The system displays what volumes are on each disk.This phase approximates the memory needed to successfully complete an upgrade.Phase 2: Analyzing the NetWare v2.1x DiskThe locations of the Hot Fix area, the system and volume areas, the Directory Entry Tables (DETs) and the File Allocation Tables (FATs) are determined. A layout of the disk for v3.12 is created from this information.A list of disk blocks that must be moved is created.For example, if a block on VOL1: is on the disk in a location that is now assigned to VOL0:, it must be moved to a location that was assigned to VOL1: when the disk layout for v3.12 was created.The DETs and FATs for each volume are translated.Directory and file attributes are upgraded automatically. Macintosh folders and files are also upgraded if you are running NetWare for Macintosh. The Macintosh name space module should also be loaded (MAC.NAM).This phase ensures the system has enough memory and free disk space to complete the upgrade.If the v2.1x disks do not have enough space for the upgrade to occur, a warning appears and the upgrade stops. (You must create more room on the disk, and then restart the upgrade.)Phase 3: Modifying Each NetWare v2.1x DiskThe partition table on track 0 is updated and the v3.12 system tables are written to the system area. The DETs and FATs for each of the v3.12 volumes are duplicated.Blocks are moved to their new locations on the disk. The v2.1x system is not functional after this phase begins.If a power failure or similar event occurs during this phase, you must restore your v2.1x system from your backup.Phase 4: Upgrading the NetWare v2.1x Bindery to v3.12Most v2.1x bindery information is upgraded to v3.12. Other information that is upgraded includes account restrictions and print queues.NetWare v2.1x passwords are not retained in the v3.12 bindery. If you chose to assign new passwords to users, those are created and put into a file called NEW.PWD (in the SYS: SYSTEM directory).VAPs do not get upgraded. They are unique to NetWare v2.x and do not exist in NetWare v3.x.Third-party VAP functionality is lost during this upgrade. After you upgrade to v3.12, delete VAP files.Core printing services are not upgraded. After you finish upgrading to v3.12, delete print services and re-create them.Volume and disk restrictions for users are not upgraded because of differences between the v2.1x and v3.x file systems.In v2.1x the restrictions were server-wide, whereas in v3.x the restrictions are only per volume.LBL="6"ID="FM51581"Upgrade Using MigrationOverviewThe NetWare Migration Utility allows you to upgrade your file servers from NetWare v2.1x, v3.x, or another network operating system to v3.12 using two methods:Across-the-wire, where you move your network information from a NetWare v2.1x or v3.x server to a v3.12 server that is on the same network (IDREF="FM94462"see page 226 for procedures).Same-server, where you change your NetWare v2.x or v3.x server to a v3.12 server (IDREF="FM57919"see page 250 for procedures)."Necessary Resources" and "Prerequisites" for the same-server method begin IDREF="FM49719"on page 247.ID="FM49719"Necessary idxid="w3879"book="_idx" docset="nw312" tidref="i128"ResourcesA working copy of the NetWare diskettes (IDREF="FM15526"see "Make Working Copies of the NetWare Diskettes" on page 14).(If migrating from CD ROM) a CD ROM reader.The NetWare Migration Utility files located on the Migration diskette.A DOS workstation with at least 640 KB of memory and 5 MB of free disk space on either a hard drive or another network drive.Be sure the following line is in the CONFIG.SYS file: files=20. Be sure the following line is in the NET.CFG file: ipx retry count=60.NetWare v3.12 installed on a server with a 386 or higher processor.A network with a DOS workstation (using NETx.COM v3.02 or later), a NetWare v2.x or v3.x source server (or LAN Server or PCLP), and a v3.12 destination server attached.A backup device for data storage.ID="FM44787"PrerequisitesFor idxid="w3880"book="_idx" docset="nw312" tidref="i128"across-the-wire migration, set up the NetWare v3.12 destination server.Create the volumes you want to migrate data to. For specific instructions on creating volumes, see IDREF="FM23263""Create Volume SYS:" on page 42. You cannot create volumes from the migration utility.You may want to create a directory to migrate the NetWare v2.x or v3.x SYS: volume to so that you can remove unnecessary v2.x or v3.x files more easily.Since two servers on the same network cannot share the same name, the destination server must have a unique name.If you are migrating from idxid="w3881"book="_idx" docset="nw312" tidref="i3135"LAN Server, add "/API /NMS:2 /NVS:2" to the DOSLAN.INI file. For the order of parameters, see your LAN Server documentation.Make sure that all users (this includes print servers), except SUPERVISOR, are logged out of the source and destination servers and that all files (except bindery files) are closed during migration.If you are migrating from idxid="w3882"book="_idx" docset="nw312" tidref="i3135"LAN Server, you must either be the domain administrator or have administrative privileges in the domain.Remove unnecessary files.Decide if you want to migrate .BAK or .LST files, or any other temporary files. You may want to consolidate some files and directories.idxid="w3883"book="_idx" docset="nw312" tidref="i7273"Value Added Processes (VAPs) that are in a directory that you migrate are copied to the destination NetWare v3.12 server, but VAPs are not compatible with v3.12, so you may want to delete them before you start the migration.The following NetWare v2.1xidxid="w3884"book="_idx" docset="nw312" tidref="i3896"files are not compatible with NetWare v3.12 and should be deleted.LARCHIVE.EXELRESTORE.EXEMACBACK.EXENARCHIVE.EXENRESTORE.EXEIf these files are only in SYS:PUBLIC or SYS:SYSTEM, the migration utility blocks them from being transferred. If copies of these files are in other directories, they are transferred.The following NetWare v2.0a files are not compatible with NetWare v3.12. Delete these files also:ENDSPOOL.EXEQ.EXEQUEUE.EXESPOOL.EXEPrepare Macintosh file support.To store idxid="w3885"book="_idx" docset="nw312" tidref="i3631"Macintosh files and folders on the new NetWare v3.12 server, add name space support to any volume that needs to store files with long names. For more information, see "book="utilref" docset="nw312"Add Name Space" inUtilities Reference.Install NetWare for Macintosh (a separate Novell product) to provide native-mode support for Macintosh workstations that connect to the v3.12 server.Rename DOS files and directories that have long names.NetWare v2.15 and earlier lets you give directories and files 14-character names.NetWare v3.12 allows only DOS idxid="w3886"book="_idx" docset="nw312" tidref="i4030"naming conventions for DOS directories and files.DOS limits filenames to 8 characters with a 3-character extension. (Macintosh and OS/2 files can still follow their respective naming conventions.) Only files that conform to DOS naming conventions (8.3) are migrated.If you are migrating from LAN Server, OS/2 extended attributes and long names are not migrated. Files that use extended attributes or long names will be truncated. All files must conform to DOS 8.3 naming conventions.Move SYS:MAIL directory files that you want to keep to a separate tape drive or other backup device.User print job configurations (PRINTCON.DAT) and DOS user login scripts are migrated from SYS:MAIL to the user's new mail directory on the destination server.Other files left in the mail directories are not copied to the destination mail directory.Prepare the idxid="w3887"book="_idx" docset="nw312" tidref="i7493"workstation.Make sure the CONFIG.SYS file includes the following line: files=20. If you add the line, reboot the workstation. Make sure the NET.CFG file includes the following: ipx retry count=60. Load LAN drivers on the DOS workstation and run NETX.COM. In some cases, the setting may already be established or set to a higher value. In such cases, leave the setting at its present value.If you are migrating from LAN Server, use Novell's ODINSUP or LANSUP protocol stack. These products allow for loading dual requesters on DOS clients to allow access to both LAN Server and NetWare server resources. For more information on ODINSUP, see NetWare Application Notes articles entitled "ODINSUP Interoperability Configurations for DOS Workstations," (February 1993) or "NetWare and Windows for Workgroups Integration," (March 1993).Administrative privileges are required from the LAN Server side.Modify the subdirectory depth to 25. NetWare v3.12 sets the default for idxid="w3888"book="_idx" docset="nw312" tidref="i6567"subdirectory depth to 25 levels, and the migration utility does not copy subdirectories deeper than 25.If the source server has subdirectories deeper than 25, modify the subdirectory structure so that the subdirectories aren't so deep. Do this before you start the migration.Plan for space on the idxid="w3889"book="_idx" docset="nw312" tidref="i1397"destination server.If you merge two or more NetWare v2.x or v3.x servers onto the same NetWare v3.12 server, plan for extra disk space for volume SYS:.SYS: requires at least 6 MB of disk space to accommodate additional users and their login scripts.Obtain NLMs to replace third-party VAPs that are running on the v2.xserver.idxid="w3890"book="_idx" docset="nw312" tidref="i7273"VAPs do not run on NetWare v3.12. To find out about NLMs that are available to replace your third-party VAPs, contact your vendor or call Novell product information at 1-800-NETWARE.Run BINDFIX on the source server.BINDFIX can delete mail subdirectories and trustee rights of all users who no longer exist on the source server.For more information on "book="utilref" docset="nw312"BINDFIX," seeUtilities Reference.ID="FM94462"Across-the-Wire MigrationAcross-the-wire migration allows you to migrate your NetWare v2.1x or v3.x server to another physical server on the network that has NetWare v3.12 installed.Across-the-wire migration includes two options. You can choose either the standard option, explained IDREF="FM56163"on page 228, or the custom option, explained IDREF="FM80556"on page 236.If a idxid="w3891"book="_idx" docset="nw312" tidref="i5127"power failure occurs, or if the migration utility stops while you are running it, restart the utility. When you restart the utility after a power failure, the entire migration process is repeated. Anything that was successfully migrated previously will exist on the destination server.For an illustration of this method, see IDREF="FM66613"Figure 5-1 on page 201.idxid="w3892"book="_idx" docset="nw312" tidref="i128"ProcedureCreate a directory called MIGRATE on your hard drive.If you are migrating using a CD ROM, follow IDREF="FM95411"Steps 1 through IDREF="FM18159"6 under IDREF="FM75772""Installing from CD-ROM" on page 19.If you are migrating using a network directory, follow IDREF="FM34345"Steps 1 through IDREF="FM44346"4 under IDREF="FM83900""Installing from Network Directory" on page 20.If you are using a network drive instead of a hard drive, you must have Create, Read, Write, and File Scan rights in this directory.Insert the Migration diskette into drive A: and type   copy a:*.* c:\migrate <Enter>The following idxid="w3893"book="_idx" docset="nw312" tidref="i2300"idxid="w3894"book="_idx" docset="nw312" tidref="i3896"files are copied:WIDTH="84"FilenameWIDTH="324"ContentsWIDTH="84"BRINFO.MSGWIDTH="324"Message information while the utility is reading the bindery import data.BWINFO.MSGMessage information while the utility is writing the bindery export data.IBM_RUN.OVLReplaces the IBM$RUN.OVL file used in v2.2 and v3.11.LSINFO.MSGMessage information while the utility is reading LAN Server import data.MIGRATE.EXEExecutable code for the migration utility.MIGRATE.EXEList of elements from the source network operating system that may not  translate/transfer to the destination server.MIGRATE.HEPHelp screens for the migration utility.MIGRATE.MSGMessage information for the menus in the utility.MNCOPY.MSGMessage information during the copying of files.PCLPINFO.MSGMessage information while the utility is reading PCLP import data._RUN.OVLReplaces the $RUN.OVL file in v2.2 and v3.11.CPQ_RUN.OVLReplaces the CPQ$RUN.OVL file in v2.2 and v3.11.TEXTTUTIL.HEPReplaces SYS$HELP.DAT.TEXTUTIL.IDXReplaces SYS$ERR.DAT.TEXTUTIL.MSGReplaces SYS$MSG.DAT.PCLP13MU.FMTUsed to migrate from PCLP.PCLP13MU.MSGUsed to migrate from PCLP.PCLPEXPO.EXEUsed to migrate from PCLP.LS10MU.FMTUsed to migrate from LAN Server v1.0.LS10MU.MSGUsed to migrate from LAN Server v1.0.IBMMIG.DOCIBM-specific utility fileCPYRIGHT.DATIBM-specific utility fileID="FM56163"Complete the migration by following the procedures under IDREF="FM49893""Using the Standard Option" on page 228, or under IDREF="FM80556""Using the Custom Option" on page 236.ID="FM49893"Using the Standard idxid="w3895"book="_idx" docset="nw312" tidref="i128"idxid="w3896"book="_idx" docset="nw312" tidref="i6482"OptionThis option migrates all information, including data files and bindery information, from a NetWare v2.x or v3.x server, across the network, to a server that has v3.12 already installed. With the standard option, you cannot select specific information to migrate. To select specific information, IDREF="FM80556"see "Using the Custom Option" on page 236.For an illustration of using the Standard migration option, see IDREF="FM10953"Figure 6-1 on page 229.If you are migrating from LAN Server, you must be logged in to the domain you want to migrate from before you run the migration utility.ProcedureYou should have the necessary resources (see IDREF="FM49719"page 247) and have completed the prerequisite tasks (see IDREF="FM44787"page 222).From the directory that contains the migration utility files, type  MIGRATE <Enter>The "Select a Migration Option" menu appears.Choose the "Standard Migration" option.ID="FM14024"From the "Select the Source LAN Type" menu, choose a source LAN type (v2.x, v3.x, LAN Server, or PCLP).ID="FM57186"From the "Select the Destination LAN Type" menu, choose a destination LAN type (v3.12).Once you have selected a source and destination, the migration utility verifies that you selected compatible versions for the migration.IDREF="FM10953"Figure 6-1 on page 229 illustrates the process of filling out the configuration form used with the standard migration option.Each option appears after you have completed the previous option. The corresponding migration steps are noted where applicable.LBL="6-1"ID="FM10953"Using the idxid="w3897"book="_idx" docset="nw312" tidref="i6482"idxid="w3898"book="_idx" docset="nw312" tidref="i128"Standard migration optionFILE="n312i123.pbm"ID="FM89356"Under Step 1 on the configuration form, press the Down-arrow key to accept the default working directory or press <Enter> to specify another working directory.The idxid="w3899"book="_idx" docset="nw312" tidref="i7486"idxid="w3900"book="_idx" docset="nw312" tidref="i128"working directory is where the bindery information and migration reports are stored. Data files are not stored here. You need 5 MB of free disk space in this directory.Usually, the working directory is located on the hard disk drive of the workstation, but you can also put it on a network drive.If you are using a network drive instead of a hard drive, you must have Create, Read, and Write rights in this directory.If this directory doesn't exist, the migration utility creates it for you on your hard disk.Follow the Quick Help to specify a different working directory.Under Step 2 on the configuration form, press <Enter> to display a list of source servers.If you are migrating from idxid="w3901"book="_idx" docset="nw312" tidref="i3135"LAN Server, the screen shows the domain obtained from the DOSLAN.INI file. Edit this field if the domain you are logged into is not the same as the one listed in the DOSLAN.INI file.Choose the source server that you want to migrate from.This selection must match the source type you specified inIDREF="FM14024"Step 3.If the NetWare source server you want to select is not shown, press <Ins> to see a list of available servers that you can log in to.Under Step 2 on the configuration form, press <Enter> to display a list of volumes on the source server that you want to migrate files and trustee assignments from.If you are migrating from LAN Server, source drives are listed.Select the volumes using <F5> and then press <Enter>.Select source volumes to migrate only if you are migrating information that is contained on those volumes.The standard option migrates "ALL" categories.Under Step 3 on the configuration form, press <Enter> to display a list of servers on the network.Choose the NetWare v3.12 destination server that you want to migrate the source server to.This selection must match the destination type you specified in IDREF="FM57186"Step 4.If the destination server you want to select is not shown, press <Ins> to see a list of available servers that you can log in to.Press <Enter> to display a list of selected source volumes and their default destination volumes.Select a volume (or a source volume in LAN Server) and press <Enter> again to specify the destination volume and directory on the NetWare v3.12 server.Press <Ins> to see a list of available volumes and directories on the v3.12 server. If you are migrating from LAN Server, the list contains servers and drives.If you specify a directory that does not exist on the v3.12 server, you are prompted to create it. Volumes must already be created on the idxid="w3902"book="_idx" docset="nw312" tidref="i1397"destination server before you can migrate to them.The idxid="w3903"book="_idx" docset="nw312" tidref="i7340"volume organization, as well as the directory structure, is migrated. You can modify the organization on the destination server after all source servers are migrated.Press <Enter> when you complete the destination path of the source volume.Continue to specify destination paths if you have multiple source volumes.Press <F10> when you finish filling out the "Volumes destination" field, and continue with IDREF="FM70575"Step 17 to assign user passwords.ID="FM70575"From the "Passwords" option, press <Enter> and select a idxid="w3904"book="_idx" docset="nw312" tidref="i4980"idxid="w3905"book="_idx" docset="nw312" tidref="i128"password option.WIDTH="120"Password OptionWIDTH="192"DescriptionWIDTH="120"Assign random  passwords(Default)WIDTH="192"A password for each username that has a  password on the source is generated  randomly and stored in a file (NEW.PWD)  in SYS:SYSTEM on the v3.12 destination  server.Note: New passwords are given only to  users and print servers that had a password  on the source server.Only users with rights to SYS:SYSTEM have  access to this file. Users cannot log in until  they are given their passwords.Assign no passwordsAfter you finish the migration and bring up  the new v3.12 server, users who had a  username on the v2.x or v3.x system can  log in using their previous username. They  are not prompted for a password.Users have the option to create their  passwords if no passwords were issued  upon migration.Note: If user account restrictions require  users to have a password, they are  prompted to type a new password, which  the system verifies.ID="FM44633"To proceed with the migration, press <F10> to display the "Select a Migration Action" menu.Choose one of the following "Migration Action" options, and then press <Enter>.WIDTH="192"ToWIDTH="120"SelectWIDTH="192"Migrate all information you selected from  the source server to the destination server.(The bindery information you selected is  copied to the working directory and  translated into the v3.12 format; it is then  copied to the NetWare v3.12 server. The  data files are migrated directly to the  destination v3.12 server.)WIDTH="120"Start the MigrationMake changes to your migration  configuration.Return to ConfigurationDisplay reports.View Migration ReportsExit the utility and return to the DOS  prompt.Exit (return to DOS)If you choose "Start the Migration," information about the migration appears on the screen and is entered into a report file, which you can review later.(Conditional) If errors occur during migration, you receive the following message and must answer the question.  A idxid="w3906"book="_idx" docset="nw312" tidref="i3896"migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):  Use the following table to help you answer the question.WIDTH="120"If you selectWIDTH="192"ThenWIDTH="120"YesWIDTH="192"The migration continues. The error is  written to the report file, and you are  prompted again the next time an error  occurs.NoThe migration stops. The error is written to  the report file. You receive this message:Migration from the source  server to the destination  server is complete.Press  <Enter> to continue.Press <Enter> to return to the "Select a  Migration Action" menu.From there, press <Esc> to edit the fields, or  choose "Exit" to leave the utility and return  to the DOS prompt.IgnoreThe migration continues. The error is  written to the report file. You are no longer prompted when an error  occurs, but all errors are written to the  report file.ID="FM38169"When the migration is complete, the following message appears:   Migration from the source server to the NetWare destination server is complete. Press <Enter> to continue.Press <Enter> to view the "Select a Migration Action" menu.(Optional) From the "Select a Migration Action" menu, select "View Migration Reports" and view the migration report.Select the idxid="w3907"book="_idx" docset="nw312" tidref="i5863"idxid="w3908"book="_idx" docset="nw312" tidref="i3896"report for the migration you completed and press <Enter>.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the NetWare v3.12 server.If you find errors on your destination server after the migration, locate them in the migration report file and determine what actions to take on the destination server to correct the errors.The report file is an ASCII text file that consists of the following:Summary information of the bindery import phase (migrating bindery data from the source server to the working directory).Summary information of the bindery export phase (migrating bindery data from the working directory to the destination server).A listing of each item in each category that was read from the source server.A listing of each item in each category that was written to or created on the destination server.The number of errors that occurred during the migration.To exit the report, press <Esc> once.To return to the "Select a Migration Action" menu, press <Esc> again.From the "Select a Migration Action" menu, choose "Exit (return to DOS)."Read IDREF="FM96203""What to Do After the Migration" on page 245.ID="FM80556"Using the Custom OptionThis option lets you select specific types of information to migrate.For example, if you don't want to overwrite default account restrictions, you do not have to migrate the account restrictions from any source servers.For more information on how to customize the destination server, IDREF="FM73047"see "Setting Up Your Destination Server" on page 215.If you are migrating from a LAN Server, you must be logged in to the domain server you want to migrate from.ProcedureYou should have the necessary resources (IDREF="FM49719"on page 247) and have completed the prerequisite tasks (IDREF="FM44787"on page 222).Start the migration utility by changing to the directory that contains the migration utility files and typing  MIGRATE <Enter>The "Select a Migration Option" menu appears.From the "Select a Migration Option" menu, choose the "Custom Migration" option.From the "Select the Type of Migration" menu, choose " idxid="w3909"book="_idx" docset="nw312" tidref="i1293"Across-the-Wire Migration."ID="FM85206"From the "Select the source LAN type" menu, choose a source LAN type (v2.x, v3.x, or LAN Server/PCLP).ID="FM94292"From the "Select the destination LAN type" menu, choose a destination LAN type (v3.x).When selecting a source and destination, the migration utility does version checking according to the source type and destination type you selected.IDREF="FM87860"Figure 6-2 illustrates the process of filling out the configuration form used with the custom migration option. Corresponding migration steps are noted.LBL="6-2"ID="FM87860"Using the idxid="w3910"book="_idx" docset="nw312" tidref="i1293"idxid="w3911"book="_idx" docset="nw312" tidref="i128"custom optionFILE="n312i123.pbm"Under Step 1 on the configuration form, press the Down-arrow key to accept the default working directory or press <Enter> to specify another working directory.The idxid="w3912"book="_idx" docset="nw312" tidref="i7486"idxid="w3913"book="_idx" docset="nw312" tidref="i128"working directory is where the bindery information and migration reports are stored. Data files are not stored here. You need 5 MB of free disk space in this directory.Usually, the working directory is located on the hard disk drive of the workstation, but you can also put it on a network drive.If you are using a network drive instead of a hard drive, you must have Create, Read, Write, and File Scan rights in this directory.If this directory doesn't exist, the migration utility creates it for you on your hard disk.Follow the Quick Help to specify a different working directory.Under Step 1 on the configuration form, press <Enter> to select an error/warning action.WIDTH="120"Error/Warning ActionWIDTH="192"DescriptionWIDTH="120"Pause after warnings and  errors.WIDTH="192"Choose this option if you want the utility to  stop after each warning and error and  prompt you to continue with the  migration.Each time an error is reported and you are  prompted, you can choose to discontinue  the prompting.Do not pause after  warnings and errors.Choose this option if you do not want to be  prompted after each warning and error.All errors are listed in the report file regardless of the option you select.Under Step 2 on the configuration form, press <Enter> to display a list of source servers.If you are migrating from LAN Server, the screen shows the domain obtained from the DOSLAN.INI file. Edit this field if the domain you are logged into is not the same as the one listed in the DOSLAN.INI file.Choose the source server you want to migrate from.This selection must match the source type you specified inIDREF="FM85206"Step 4.If the NetWare source server you want to select is not shown, press <Ins> to see a list of available servers you can log in to.When migrating multiple idxid="w3914"book="_idx" docset="nw312" tidref="i6425"source servers, only one source server can be migrated at a time.Under Step 2 on the configuration form, press <Enter> to display categories of information you want to migrate.If you are migrating from idxid="w3915"book="_idx" docset="nw312" tidref="i3135"idxid="w3916"book="_idx" docset="nw312" tidref="i5038"LAN Server or PCLP, you are limited to the following categories to migrate:Access Control profilesAll informationData filesGroupsPrint queuesUsersOnly files that conform to DOS naming conventions (8.3) are migrated.Using <F5>, mark the information you want to migrate.Mark as many of the categories as necessary.Follow the Quick Help for details on how to select information. IDREF="FM52992"Table 5-2, "Information that can be migrated using the custom migration option," on page 205 shows the types and descriptions of information you can migrate from a NetWare source server when you use the custom migration option.If you select "All Information," all categories are migrated.Under Step 2 on the configuration form, press <Enter> again to display a list of source volumes on the source server you want to migrate data from.If you are migrating from LAN Server, source drives are listed.Mark the volumes using <F5>, and then press <Enter>.Mark source idxid="w3917"book="_idx" docset="nw312" tidref="i7340"volumes to migrate only if you are migrating data files or trustee assignments on those volumes.If you are only migrating one or more of the following categories, you do not need to select a source volume:Accounting InformationDefault Account Balance/RestrictionsGroupsPrint QueuesUser RestrictionsUsersYou must select a source volume (or a source drive in LAN Server) to migrate if you select any of the following categories to migrate:All InformationData FilesTrustee Assignments (or Access Control permissions in LAN Server)Under Step 3 on the configuration form, press <Enter> to display a list of NetWare servers.Choose the NetWare v3.12 destination server you want to migrate the source server to.This selection must match the destination type you specified in IDREF="FM94292"Step 5 on page 236.If the destination server you want to select is not shown, press <Ins> to see a list of available servers that you can log in to.Under Step 3 on the configuration form, select a volume (or source drive in LAN Server) and press <Enter> to specify the destination volume and directory on the NetWare v3.12 server.Destination volumes that match the source volumes are displayed as the default.Press <Ins> to see a list of available volumes and directories on the NetWare v3.12 server.If you are migrating from LAN Server, the list contains servers and drives.If you specify a directory that does not exist on the v3.12 server, you are prompted to create it. Volumes must already be created on the destination server before you can migrate data to them.The volume organization, as well as the directory structure, is migrated. You can modify the organization on the destination server after all source servers have been migrated.Press <Enter> when you complete the destination path of the source volume.Continue to specify destination paths if you have multiple source volumes.Press <F10> when you finish filling out the "Volumes destination" field, and continue with IDREF="FM68697"Step 21 to assign user passwords.ID="FM68697"Under Step 3 on the configuration form, press <Enter> to choose a idxid="w3918"book="_idx" docset="nw312" tidref="i4980"password option.WIDTH="120"Password OptionWIDTH="192"DescriptionWIDTH="120"Assign random  passwords (Default)WIDTH="192"A password for each user that has a  password on the source is generated  randomly and stored in a file (NEW.PWD)  in SYS:SYSTEM on the v3.12 destination  server.Note:New passwords are given only to  users and print servers that had a password  on the source server.Only users with rights to SYS:SYSTEM have  access to this file. Users cannot log in until  they are given their passwords from this  list.Assign no passwordsAfter you finish the migration and bring up  the new v3.12 server, users who had a  username on the v2.x or v3.x system can  log in using their previous username. They  are not prompted for a password.Users have the option to create their  passwords if no random passwords were  issued upon migration.Note: If the user account restrictions  require users to have a password, they are  prompted to type a new password, which  the system verifies.To proceed with the migration, press <F10> to display the "Select a Migration Action" menu.Choose one of the following "Migration Action" options and then press <Enter>.WIDTH="192"ToWIDTH="120"SelectWIDTH="192"Migrate all information you selected from  the source server to the destination server.  If you choose this option, the migration  starts automatically.(The bindery information you selected is  copied to the working directory and  translated into the v3.12 format, and then  copied to the NetWare v3.12 server. The  data files are migrated directly to the v3.12  server.)WIDTH="120"Start the migrationMake changes to your migration  configuration.Return to configurationDisplay reports.View migration reportsExit the utility and return to the DOS  prompt.Exit (return to DOS)If you select "Start the Migration," all information about the migration is displayed on the screen and entered into a report file, which you can review later.(Conditional) If errors occur during migration and you chose to be prompted after errors and warnings, you receive the following error message and must answer the question.  A idxid="w3919"book="_idx" docset="nw312" tidref="i3896"migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):Use the following table to help you answer the question.WIDTH="120"If you selectWIDTH="192"ThenWIDTH="120"YesWIDTH="192"The migration continues. The error is  written to the report file and you are  prompted again the next time an error  occurs.NoThe migration stops. The error is written to  the report file. You receive this message:Migration from the source  server to the destination  server is complete.Press  <Enter> to continue.Press <Enter> to return to the "Select a  Migration Action" menu.From there, press <Esc> to edit the fields, or  choose "Exit" to leave the utility and return  to the DOS prompt.IgnoreThe migration continues. The error is  written to the report file.You are no longer prompted when an error  occurs, but all errors are written to the  report file.When the migration is complete, the following message appears:  Migration from the source server to the destination server is complete. Press <Enter> to continue.Press <Enter> to view the "Select a Migration Action" menu.(Optional) From the "Select a Migration Action" menu, select "View Migration Reports" and view the idxid="w3920"book="_idx" docset="nw312" tidref="i3896"migration report.Select the report for the migration you completed and press <Enter>.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the v3.12 server.If you find errors on your destination server after the migration, locate them in the migration report file and determine what actions to take on the destination server to correct the errors.The report file is an ASCII text file that consists of the following:Summary information of the bindery import phase (migrating bindery data from the source server to the working directory).Summary information of the bindery export phase (migrating bindery data from the working directory to the destination server).Listing of each item in each category that was read from the source server.Listing of each item in each category that was written to or created on the destination server.The number of errors that occurred during the migration.To exit the report, press <Esc> once.To return to the "Select a Migration Action" menu, press <Esc> again.From the "Select a Migration Action" menu, choose "Exit (return to DOS)."Read IDREF="FM96203""What to Do After the Migration." ID="FM96203"What to Do After the idxid="w3921"book="_idx" docset="nw312" tidref="i3896"MigrationAfter the migration is complete, check the NetWare v3.12 server and do the following:Update references to the server in user login scripts.Although user login scripts are migrated, they are not modified, and server names and directory paths are not changed to match your new environment.Run idxid="w3922"book="_idx" docset="nw312" tidref="i6769"idxid="w3923"book="_idx" docset="nw312" tidref="i424"third-party applications. You may have to reinstall them to work properly under NetWare v3.12. You may also need to enter new paths in the setup files for third-party applications.Check applications to see if they run properly. The following conditions require you to reinstall an application:The application has an .EXE file that will not migrate.The application is path-specific and you changed the path structure during migration.Some DOS applications don't work when installed on volumes that have more than 32 MB of disk space. Some of these applications can be made to work by doing the following:Restrict the application's disk space on the destination server with DSPACE in the application's directory.Make the directory a fake root with MAP (see "book="concepts" docset="nw312"Fake Root" in Concepts).Examine the files in merged directories and reorganize them if necessary. Any directories that were merged may contain unrelated files.Update migrated print queues and print servers.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it.If you chose to assign random passwords, you may want to print the idxid="w3924"book="_idx" docset="nw312" tidref="i4594"NEW.PWD file and distribute the password information to your users. The users should change their passwords immediately.The report, an ASCII text file, shows passwords sorted by date. If users were migrated from more than one server, the current password is the last one listed on the report.Check print servers and print queues to make sure they are configured correctly. Also make sure that the physical printer connection is secure. Use the NetWare print utilities to accomplish these tasks.Also, if you are migrating from idxid="w3925"book="_idx" docset="nw312" tidref="i3135"LAN Server, set up print servers and print queues.ID="FM81630"Same-Server MigrationUse the same-server migration to update a server that will be installed on the same hardware as the old server, allowing you to change your NetWare v2.x server to a NetWare v3.12 server.If you are running idxid="w3926"book="_idx" docset="nw312" tidref="i5745"RCONSOLE, make sure you use the latest version of the shell.For an illustration of same-server migration, see IDREF="FM90063"Figure 5-2 on page 203.The same-server method does involve some risk to your data files as a result of the conversion process to NetWare v3.12.ID="FM49719"Necessary idxid="w3927"book="_idx" docset="nw312" tidref="i6117"ResourcesThe NetWare Migration Utility files located on the Migration diskette.A DOS workstation with at least 640 KB of memory and 5 MB of free disk space on either a hard drive or another network drive.Be sure the following line is in the CONFIG.SYS file: files=20. Be sure the following line is in the NET.CFG file: ipx retry count=60.A NetWare v2.1x or v3.x server with a 386 or higher processor.A network with a DOS workstation (using NETx.COM v3.02 or later) and a NetWare v2.x source server (or LAN Server or PCLP).A backup device for data storage.ID="FM44787"Prerequisites idxid="w3928"book="_idx" docset="nw312" tidref="i6117"Back up the data from your source server.Use your regular backup utility to back up your current NetWare server at least twice to ensure a good copy.The NetWare idxid="w3929"book="_idx" docset="nw312" tidref="i6117"same-server migration procedure destroys all data on your hard disk. Back up trustees or bindery information. The migration utility converts the trustees and bindery information to NetWare v3.12 format. Make sure that all users, except SUPERVISOR, are logged out of the source and destination servers (this includes print servers) and that all files (except bindery files) are closed during migration.If you are migrating from LAN Server, you must either be the domain administrator or have administrative privileges in the domain.Remove unnecessary files.Decide if you want to migrate .BAK or .LST files, or any other temporary files. You may want to consolidate some files and directories.Value Added Processes (VAPs) that are in a directory that you migrate are copied to the destination v3.12 server, but VAPs are not compatible with NetWare v3.12, so you may want to delete them before you start the migration.The following NetWare v2.1x files are not compatible with NetWare v3.12.Delete the following files:LARCHIVE.EXELRESTORE.EXEMACBACK.EXENARCHIVE.EXENRESTORE.EXEIf these files are only in SYS:PUBLIC or SYS:SYSTEM, the migration utility blocks them from being transferred. If copies of these files are in other directories, they are transferred.The following NetWare v2.0a files are not compatible with NetWare v3.12. Delete these files also:ENDSPOOL.EXEQ.EXEQUEUE.EXESPOOL.EXERename DOS files and directories that have long names.Although NetWare v2.15 and earlier lets you give directories and files 14-character names, NetWare v3.12 allows only DOS naming conventions for DOS directories and files.DOS limits filenames to 8 characters with a 3-character extension. (Macintosh files can still follow Macintosh naming conventions.)Only files that conform to DOS naming conventions (8.3) are migrated.If you are migrating from LAN Server, OS/2 extended attributes and long names are not migrated. Files that use extended attributes or long names can be truncated. All files must conform to DOS 8.3 naming conventions.Move files that you want to keep out of the idxid="w3930"book="_idx" docset="nw312" tidref="i6615"SYS:MAIL directory.User print job configurations (PRINTCON.DAT) and DOS user login scripts are migrated from SYS:MAIL to the user's new mail directory on the destination server.Other files left in the mail directories are not copied to the destination mail directory.Prepare the idxid="w3931"book="_idx" docset="nw312" tidref="i7493"workstation.Make sure the CONFIG.SYS file includes the following line: files=20. If you had to add the line, reboot the workstation. Make sure the NET.CFG file includes the following line: ipx retry count=60. Load your LAN drivers on the DOS workstation and run NETX.COM. In some cases, the setting may already be established or set to a higher value, in such cases, leave the setting at its present value.If you are migrating from idxid="w3932"book="_idx" docset="nw312" tidref="i3135"LAN Server, use Novell's ODINSUP or LANSUP protocol stack. These products allow for loading dual requesters on DOS clients to allow access to both LAN Server and NetWare server resources.Administrative privileges are required from the LAN Server side.Plan for space on the destination server.If you are merging two or more NetWare v2.x servers onto the same NetWare v3.12 server, plan for extra disk space for volume SYS:.SYS: requires at least 6 MB of disk space to accommodate additional users and their login scripts.Obtain NLMs to replace third-party VAPs running on the v2.x server.VAPs do not run on a NetWare v3.12 system. To find out about NLMs that are available to replace your third-party VAPs, contact your vendor or call Novell product information at 1-800-NETWARE.Run BINDFIX on the source server.BINDFIX can delete mail subdirectories and trustee rights of all users who no longer exist on the source server.For more information on " BINDFIX," seebook="utilref" docset="nw312"Utilities Reference.If you are migrating from LAN Server, you must be logged in to the domain server you want to migrate from.ID="FM57919"Using the idxid="w3933"book="_idx" docset="nw312" tidref="i6117"Same-Server Migration MethodProcedureCreate a directory called MIGRATE on your hard drive.If you are using a network drive instead of a hard drive, you must have Create, Read, and Write rights in this directory.Insert the Migration diskette into drive A: and type   copy a:*.* c:\migrate <Enter>The following files are copied:WIDTH="84"FilenameWIDTH="324"ContentsWIDTH="84"BRINFO.MSGWIDTH="324"Message information while the utility is reading the bindery import data.BWINFO.MSGMessage information while the utility is writing the bindery export data.IBM_RUN.OVLReplaces a file of the same name used in v2.2 and v3.11.LSINFO.MSGMessage information while the utility is reading LAN Server import data.MIGRATE.EXEExecutable code for the migration utility.MIGRATE.EXPList of elements from the source network operating system that may not  translate/transfer to the destination server.MIGRATE.HEPHelp screens for the migration utility.EMIGRATE.MSGMessage information for the menus in the utility.MNCOPY.MSGMessage information during the copying of files.PCLPINFO.MSGMessage information while the utility is reading PCLP import data._RUN.OVLReplaces a file of the same name used in v2.2 and v3.11.CPQ_RUN.OVLReplaces a file of the same name used in v2.2 and v3.11.TEXTTUTIL.HEPReplaces SYS$HELP.DAT.TEXTUTIL.IDXReplaces SYS$ERR.DAT.TEXTUTIL.MSGReplaces SYS$MSG.DAT.PCLP13MU.FMTUsed to migrate from PCLP.PCLP13MU.MSGUsed to migrate from PCLP.PCLPEXPO.EXEUsed to migrate from PCLP.LS10MU.FMTUsed to migrate from LAN Server v1.0.LS10MU.MSGUsed to migrate from LAN Server v1.0.LS10EXPO.EXEUsed to migrate from LAN Server v1.0.IBMMIG.DOCIBM-specific utility fileCPYRIGHT.DATIBM-specific utility fileStart the Same-Server MigrationProcedureHave the necessary resources (IDREF="FM49719"on page 247) and complete the prerequisite tasks (IDREF="FM44787"on page 222).Start the migration utility by moving to the directory that contains the migration utility files and typing  MIGRATE <Enter>The "Select a Migration Option" menu appears.Choose the " idxid="w3934"book="_idx" docset="nw312" tidref="i6117"Custom Migration" option.This option lets you select specific types of information to migrate.For example, if you don't want to overwrite default account restrictions, you do not have to migrate the default account restrictions from the source server.For more information on how to customize the destination server, IDREF="FM73047"see "Setting Up Your Destination Server" on page 215.See IDREF="FM19307"Figure 6-3 on page 253 for an illustration of the custom migration option.From the "Select the Type of Migration" menu, choose "Same-Server migration."The same-server option allows you to stop the utility after you migrate the bindery information to the working directory so that you can install NetWare v3.12.ID="FM41847"From the "Select the source LAN type" menu, choose a source LAN type (v2.x, v3.x, LAN Server/PCLP).ID="FM14372"From the "Select the destination LAN type" menu, choose a destination LAN type (v3.12).Once you have selected a source and destination, the migration utility verifies that you selected compatible versions for the migration.LBL="6-3"ID="FM19307"Using the same-server idxid="w3935"book="_idx" docset="nw312" tidref="i1293"idxid="w3936"book="_idx" docset="nw312" tidref="i6117"custom migration optionFILE="n312i124.pbm"Under Step 1 on the configuration form, press the Down-arrow key to accept the default working directory or press <Enter> to specify another working directory.The idxid="w3937"book="_idx" docset="nw312" tidref="i7486"idxid="w3938"book="_idx" docset="nw312" tidref="i6117"working directory is where the bindery information and migration reports are stored.Usually, the working directory is located on the hard disk drive of the workstation, but you can also put it on a network drive. You need 5 MB free disk space in this directory.If you use a network drive instead of a hard drive, you must have Create, Read, and Write rights in this directory.If this directory doesn't exist, the migration utility creates it for you on your hard disk.Follow the Quick Help to specify a different working directory.Under Step 1 on the configuration form, press <Enter> to select an error/warning action. WIDTH="120"Error/Warning ActionWIDTH="192"DescriptionWIDTH="120"Pause after warnings and  errorsWIDTH="192"Choose this option if you want the utility to  stop after each warning and error and  prompt you to continue with the  migration.Each time an error is reported and you are  prompted, you can choose to discontinue  the prompting.Do not pause after  warnings and errorsChoose this option if you do not want to be  prompted after each warning and error.All errors are listed in the report file regardless of the option you select.Under Step 2 on the configuration form, press <Enter> to display a list of source servers.If you are migrating from LAN Server, the screen shows the domain obtained from the DOSLAN.INI file. Edit this field if the domain you are logged into is not the same as the one listed in the DOSLAN.INI file.Choose the source server you want to migrate from.This selection must match the type you specified in IDREF="FM41847"Step 5.If the source server you want to select is not shown, press <Ins> to see a list of available servers that you can log in to.Under Step 2 on the configuration form, press <Enter> to display categories of information you want to migrate.If you are migrating from LAN Server or PCLP, you are limited to the following categories to migrate:Access Control profilesAll informationGroupsPrint queuesUsersUsing <F5>, mark the information you want to migrate.Mark as many of the categories as necessary.Follow the Quick Help for details on how to select information.For a description of each category, see IDREF="FM73775"Table 5-4, "Evolution of directory and file rights," on page 209.Under Step 2 on the configuration form, press <Enter> to display a list of source volumes on the source server that you want to migrate trustee assignments from.If you are migrating from LAN Server, source drives are listed.Mark the volumes using <F5>, then press <Enter>.Mark source volumes to migrate only if you are migrating information that is contained on those volumes.For example, you do not need to mark a source volume if you are only migrating any of the following categories:Accounting InformationDefault Account Balance/RestrictionsGroupsPrint QueuesUser RestrictionsUsersYou must select a source volume to migrate if you select either All Information or Trustee Assignments.Review the fields on the configuration form and make necessary changes.You cannot complete the information for the destination server, since it does not yet exist.After you migrate the source information and install NetWare v3.12, you return to the migration utility and complete the destination server information.To proceed with the migration, press <F10> to display the "Select a Migration Action" menu.Select "Migrate to the Working Directory," then press <Enter>.All information about the migration is displayed on the screen and is entered into a report file which you can review later.(Conditional) If errors occur during migration and you chose to be prompted after errors and warnings, you receive the following error message and must answer the question.  A migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):Use the following table to help you answer the question.WIDTH="120"If you selectWIDTH="192"ThenWIDTH="120"YesWIDTH="192"The migration continues. The error is saved  in the report file and you are prompted the  next time an error occurs.NoThe migration stops. The error is written to  the report file. You receive this message:Migration is complete.Press  <Enter> to continue.Press <Enter> to return to the "Select a  Migration Action" menu.From there, press <Esc> to edit the fields, or  choose "Exit" to leave the utility and return  to the DOS prompt.IgnoreThe migration continues. The error is  written to the report file.You aren't prompted when an error occurs,  but all errors are saved in the report file.When the migration to the working directory is complete, the following message appears.Migration from the working directory is complete. Press <Enter> to continue.Press <Enter> to view the "Select a Migration Action" menu.(Optional) From the "Select a Migration Action" menu, select "View Migration Reports" and view the migration report.Select the report for the migration you completed and press <Enter>.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the NetWare v3.12 server.If you find errors on your destination server after the migration, locate them in the report and determine what actions to take on the destination server.The report file is an ASCII text file that consists ofSummary information of the bindery import phase (migrating bindery data to the working directory).A listing of each item in each category that was read from the source server.The number of errors that occurred during the migration.To exit the report, press <Esc> once.To return to the "Select a Migration Action" menu, press <Esc> again.To exit the utility, choose "Exit (Return to DOS)."Install NetWare v3.12 on the server. Follow the instructions under IDREF="FM45170""Complete the Upgrade to NetWare v3.12 Using INSTALL.NLM" on page 301 to install your NetWare v3.12 server.ID="FM93156"Prepare Macintosh file support.To store Macintosh files and folders on the new NetWare v3.12 server, add name space support to any volume that needs to store files with long names. For more information, see "book="utilref" docset="nw312"Add Name Space" inUtilities Reference.Install NetWare for Macintosh (a separate Novell product) to provide native-mode support for Macintosh workstations that connect to the v3.12 server.ID="FM63957"Restore the data files from your backup device to a network directory on the NetWare v3.12 server.Make a note of where you restore the data files so that you can direct the bindery information to the correct location.Restart the migration utility by changing to the directory where the migration utility files are and typing  MIGRATE <Enter>The "Select a Migration Option" menu appears.Make sure that the working directory is the same one you used when you migrated from the source server to the working directory.Choose the "Custom Migration" option.From the "Select the Type of Migration" menu, choose "Same- Server migration."From the "Select Source LAN Type" menu, choose a source LAN type (NetWare v2.x or LAN Server/PCLP).This should be the same source LAN type you selected in IDREF="FM41847"Step 5.From the "Select the Destination LAN Type" menu, choose a destination LAN type (v3.12).This should be the same destination LAN type you selected in IDREF="FM14372"Step 6.(Optional) Change the "Error/Warning" prompt if you want.Move the cursor to Step 3 on the configuration form and press <Enter> to display a list of NetWare servers.Do not change the source server information on the configuration form.Choose the NetWare v3.12 destination server that you want to migrate the source server information to.Choose the NetWare v3.12 server you just installed.Press <Enter> to display a list of selected source volumes and their default destination volumes.Destination volumes that match the source volumes are displayed as the default.Select a volume and press <Enter> to specify the destination volume and directory on the NetWare v3.12 server.Press <Ins> to see a list of available volumes and directories on the v3.12 server.If you are migrating from LAN Server, the list contains servers and drives.If you specify a directory that does not exist on the v3.12 server, you are prompted to create it. Volumes must already be created before you can migrate them.Press <Enter> when you have completed the destination path of the source volume.Continue to specify destination paths if you have multiple source volumes.Press <F10> when you finish filling out the "Volumes destination" field.Under Step 3 on the configuration form, press <Enter> and choose a idxid="w3939"book="_idx" docset="nw312" tidref="i4980"idxid="w3940"book="_idx" docset="nw312" tidref="i6117"password option.WIDTH="120"Password OptionWIDTH="192"DescriptionWIDTH="120"Assign random  passwords(Default)WIDTH="192"A password for each user that has a  password on the source is generated  randomly and stored in a file (NEW.PWD)  in SYS:SYSTEM on the v3.12 server.Note:New passwords are given only to  users and print servers that had a password  on the source server.Only users with rights to SYS:SYSTEM have  access to this file. Users cannot log in until  they are given their passwords from this  list.Assign no passwordsAfter you finish the migration and bring up  the new NetWare v3.12 server, users who  were on the v2.x or v3.11 system can log in  using their previous username. They aren't  prompted for a password.Users have the option to create their  password if no password was chosen upon  migration.Note: If the user account restrictions  require users to have a password, they are  prompted to type a new password, which  the system verifies.Review the fields on the configuration form and make necessary changes.Do not change the information in the source server area.To proceed with the migration, press <F10> to display the "Select a Migration Action" menu.Select "Migrate from Working Directory."All information about the migration displays on the screen and goes into a report file, which you can review later.When the migration from the working directory is complete, the migration utility notifies you.(Conditional) If errors occur during migration and you chose to be prompted after errors and warnings, you receive the following error message and must answer the question.  A idxid="w3941"book="_idx" docset="nw312" tidref="i3896"migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):WIDTH="120"If you selectWIDTH="192"ThenWIDTH="120"YesWIDTH="192"The migration continues. The error is  written to the report file, and you are  prompted again the next time an error  occurs.NoThe migration stops. The error is written to  the report file. You receive this message:Migration from the working  directory is complete. Press  <Enter> to continue.Press <Enter> to return to the "Select a  Migration Action" menu.From there, press <Esc> to edit the fields, or  choose "Exit" to leave the utility and return  to the DOS prompt.IgnoreThe migration continues. The error is  written to the report file.You are no longer prompted when an error  occurs, but all errors are written to the  report file.When the migration is complete, the following message appears.  Migration from the working directory to the NetWare destination server is complete. Press <Enter> to continue.Press <Enter> to view the "Select a Migration Action" menu.(Optional) From the "Select a Migration Action" menu, select "View Migration Reports" and view the migration report.Select the report for the migration you completed.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the v3.12 server.If you find errors on your destination server after the migration, review the migration report to see if you can find where they occurred.The report file is an ASCII text file that consists of the following:Summary information of the bindery export phase (migrating bindery data from the working directory to the destination server).Listing of each item in each category that was read from the source server.Listing of each item in each category that was written to or created on the destination server.The number of errors that occurred during the migration.To exit the report, press <Esc> once.To return to the "Select a Migration Action" menu, press <Esc> again.To exit the migration utility, select "Exit (Return to DOS)."Read IDREF="FM29915""What to Do After the Migration." ID="FM29915"What to Do After the idxid="w3942"book="_idx" docset="nw312" tidref="i3896"MigrationAfter the migration is complete, check the v3.12 server and do the following if they apply:Update references to the server in user login scripts if you changed the server name.Although user login scripts are migrated, they are not modified, and server names and directory paths are not changed to match your new environment.Run third-party applications. You may have to reinstall them to work properly under NetWare v3.12. You may also need to enter new paths in the setup files for any third-party applications.Check applications to see if they run properly. The following conditions require you to reinstall an application:The application has an .EXE file that did not migrate.The application is path-specific and you changed the path structure during migration.Some idxid="w3943"book="_idx" docset="nw312" tidref="i1638"idxid="w3944"book="_idx" docset="nw312" tidref="i424"DOS applications don't work when installed on volumes that have more than 32 MB of disk space. Some of these applications can be made to work by doing the following:Restrict the application's disk space on the destination server using DSPACE in the application's directory.Make the directory a fake root with MAP.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it.If you chose to assign random passwords, you may want to print the NEW.PWD file and distribute the password information to your users. The users should change their passwords immediately.The report, an ASCII text file, shows passwords sorted by date. If users were migrated from more than one server, the current password is the last one listed on the report.Check print servers and print queues to make sure they are configured correctly. Also make sure that the physical printer connection is secure. Use the NetWare print utilities to accomplish these tasks.If you are migrating from LAN Server, set up print servers and print queues.LBL="7"ID="FM51148"Upgrade Using In-Place UpgradeOverviewThis chapter covers the procedures for idxid="w3945"book="_idx" docset="nw312" tidref="i128"idxid="w3946"book="_idx" docset="nw312" tidref="i128"upgrading an existing NetWare server using the In-Place Upgrade.Use the In-Place Upgrade for upgrading from an existing NetWare v2.1x, v2.2 to a v3.11 or v3.12 server.If you are upgrading an existing NetWare v3.x server, follow the procedures under IDREF="FM23283""NetWare v3.x to v3.12 Upgrade" on page 299.ID="FM26458"NetWare v2.1x or v2.2 UpgradeReferences in this section to NetWare v2.1x include NetWare v2.2.A NetWare v2.1x server must have an 386 or higher processor to be upgraded to a v3.12 server.If your NetWare 2.1x server uses an 286 processor, see IDREF="FM51581"Chapter 6, "Upgrade Using Migration," on page 221.NetWare v2.0 and v2.0a are not supported by idxid="w3947"book="_idx" docset="nw312" tidref="i2792"In-Place Upgrade.Necessary idxid="w3948"book="_idx" docset="nw312" tidref="i2778"ResourcesA working copy of the NetWare system diskettes (see IDREF="FM15526""Make Working Copies of the NetWare Diskettes" on page 14).A NetWare server running versions 2.10, 2.11, 2.12, 2.15 (revisions a, b, and c), or 2.2.A computer with a 386 or higher processor with a minimum of 4 MB of RAM. NetWare v3.x does not run on a 286 processor.Servers with large disks and a large number of directories may need more memory to complete the upgrade than they would normally need to run the server after the upgrade.A backup device, such as a tape drive or a DOS hard drive.Enough idxid="w3949"book="_idx" docset="nw312" tidref="i1544"disk space to accommodate the v3.12 file system. Each volume should have at least 10% free disk space to accommodate the enlarged directory and file allocation tables.To store the v3.12 operating system files, we recommend you reserve 30 to 40 MB on volume SYS:.We also recommend that you create at least a 5MB DOS partition on the disk containing volume SYS:.Ensure that no disk has more than eight volumes on it.The NetWare System_1 diskette which contains the 2XUPGRDE.NLM.Sufficient time to idxid="w3950"book="_idx" docset="nw312" tidref="i7086"upgrade your server. This depends on the following conditions:The number of hard disks, not including mirrored disksThe amount of disk space in useIf you have several disks, and a lot of disk space in use, this upgrade could take several hours.(Optional) NetWare for Macintosh (to support Macintosh files on your network).Prerequisites idxid="w3951"book="_idx" docset="nw312" tidref="i2778"If you are running NetWare v2.1x on a 286 processor, upgrade your computer to a 386 or higher processor.Back up your v2.1x system twice to ensure that you have a good backup. A idxid="w3952"book="_idx" docset="nw312" tidref="i651"idxid="w3953"book="_idx" docset="nw312" tidref="i2778"backup is essential if you must restore your v2.1x system.Make sure all users are logged out and all files (except bindery files) are closed during the upgrade.Make sure all print servers are logged out.You may need updated disk and LAN drivers to run v3.12. If you have third-party drivers, check with the manufacturer before you upgrade to see if you have compatible versions.If you are using the idxid="w3954"book="_idx" docset="nw312" tidref="i2758"IDE.DSK disk driver, you cannot add a idxid="w3955"book="_idx" docset="nw312" tidref="i1684"DOS partition to an upgraded v3.12 disk.Claiming a DOS partition with FDISK on an upgraded IDE disk causes the IDE.DSK driver to get its parameters for heads, sectors, and cylinders from the CMOS tables instead of from the disk drive.The different parameters cause the DOS and NetWare partitions to overlap, resulting in data loss or data corruption.The NetWare partition will also be read from and written to erroneously with the wrong drive parameters.This problem occurs since the NetWare v2.1x IDE disk driver did not conform to the same specifications as DOS. The IDE driver is designed to check for the existence of a DOS partition. If a DOS partition exists, then the driver uses the drive parameters from the CMOS tables so that they will match what DOS is using. Otherwise, the driver will use the drive parameters from the NetWare v2.1x partition on the IDE disk drive.ID="FM69414"Boot NetWare v3.12idxid="w3956"book="_idx" docset="nw312" tidref="i2778"ProcedureKeep a record of your hardware configuration information to be used at a later stage of the upgrade, as well as for future reference. At the NetWare v2.1x server system console prompt (:), type  CONFIG <Enter>ID="FM59231"Copy the following information from the server screen onto the NetWare v3.12 Server Worksheet provided at the back of this manual:Server nameLAN configuration information (including the network address)Disk channel configuration informationFrom a workstation, run BINDFIX.You must have rights to the SYS:SYSTEM directory to run BINDFIX.idxid="w3957"book="_idx" docset="nw312" tidref="i697"idxid="w3958"book="_idx" docset="nw312" tidref="i7237"BINDFIX deletes mail subdirectories and trustee rights of users who no longer exist on the network and fixes the incorrect records in the bindery.To delete mail subdirectories and trustee rights, answer "Y" to the questions presented during BINDFIX.You may want to copy the NET$BIND.OLD and NET$BVAL.OLD files to diskette to recover the bindery later if needed.For more information on "book="utilref" docset="nw312"BINDFIX," seeUtilities Reference.Down the NetWare v2.1x server.At the system console prompt (:), type  DOWN <Enter>ID="FM81041"Do not down the server simply by turning its power switch to OFF. This creates errors when upgrading to a NetWare v3.x file system.After the server responds that it is down, wait two to three minutes to be sure that all transactions to system files are complete before turning the power off.Run VREPAIR.From the downed server, run the NetWare v2.1x VREPAIR utility on each volume.See the v2.1x VREPAIR documentation for further instructions.Insert the bootable INSTALL diskette into drive A:.If you are upgrading from CD ROM, follow IDREF="FM95411"Steps 1 through IDREF="FM18159"Step 6 under IDREF="FM75772""Installing from CD-ROM" on page 19.If you are upgrading from a network directory, follow IDREF="FM34345"Steps 1 through IDREF="FM44346"Step 4 under IDREF="FM83900""Installing from Network Directory" on page 20.Turn the server off and then on again.The computer now boots with DR DOS 6.0.ID="FM48350"If you are creating a DOS partition on the hard drive, record the information you enter in IDREF="FM46759"Steps 8 through IDREF="FM87212"13 on the worksheet at the end of this manual. You use this information again later.With the System_1 diskette in drive A:, ID="FM46759"load the v3.12 operating system by typing  SERVER <Enter>You receive a message similar to the following:  Loading...  System Console  Novell NetWare v3.12  Processor speed: 193  (Type SPEED at the command prompt for an explanation of the speed rating)  File server name:Don't type "SPEED" at this prompt (unless you want to name the server "SPEED").For an explanation of the speed rating (which is computer-specific), wait until after you name the server and give it an internal network number before you type SPEED at the console prompt.ID="FM30532"Name the idxid="w3959"book="_idx" docset="nw312" tidref="i4371"server by typing  servername<Enter>Use your NetWare v2.1x servername so that you do not have to change any login files, map statements, or batch files.Assign an idxid="w3960"book="_idx" docset="nw312" tidref="i3018"idxid="w3961"book="_idx" docset="nw312" tidref="i4555"IPX internal network number to the server. This number does not exist on a NetWare v2.1x network. In versions 3.0, 3.1, 3.11, and 4.0, it is a logical network number that identifies the individual file server.This number must be different from other network numbers (for cabling systems) or internal network numbers (for NetWare v3.0, v3.1, v3.11, v3.12, and 4.0 file servers). The internal network number for each server must beUniqueHexadecimal (base 16: using numbers 0 through 9 and letters A through F)One to eight digitsAt the cursor prompt, type the IPX internal network number and press <Enter>.The v3.12 console prompt (:) appears. The remaining steps are executed from the console prompt.Load the appropriate disk driver by typing  LOAD A:disk_driver<Enter>Replace disk_driver with one of the NetWare v3.12 drivers from IDREF="FM66920"Table 7-1.LBL="7-1" INLINE="F"ID="FM66920"NetWare v3.12 idxid="w3962"book="_idx" docset="nw312" tidref="i1561"disk driversWIDTH="132"Computer architectureWIDTH="132"Disk controller typeWIDTH="144"NetWare v3.12 disk driver(*.DSK)WIDTH="132"Industry Standard  Architecture (ISA)WIDTH="132"AT, MFM, RLL, ARLLESDIIDEWIDTH="144"ISADISK.ISADISK /b.ISADISK /b /l (lowercase "L").IDE (You cannot add a DOS  partition to an upgraded v3.11  or v3.12 IDE disk.)Novell disk coprocessor  boardDCB.MicrochannelESDIMFMIBM SCSIPS2ESDI.PS2MFM.PS2OPT(replaces PS2SCSI).Extended Industry Standard  Architecture (EISA)AT classISADISK.EISA vendor proprietarySee vendor.Other devices may be  supported. Contact the device  manufacturer to find out if it  has a v3.12-supported driver.To decide which disk drivers to load, look at the disk channel configuration information you recorded in IDREF="FM59231"Step 2. Load the equivalent NetWare v3.12 disk driver.Many more third-party disk drivers are also included on the NetWare v3.12 System_4 diskette. idxid="w3963"book="_idx" docset="nw312" tidref="i6769"Third-party disk driver manufacturers includeAdaptecADICAlways TechnologyBus LogicData Technology Corp.DPTFuture DomainQuantumUltraStorLoad the idxid="w3964"book="_idx" docset="nw312" tidref="i1561"disk drivers in the order of the controller boards. Load the driver for the internal controller first, the driver for the first disk controller board second, etc.If you do not follow the correct order, system messages about your hard disks will be incorrect.ID="FM87212"Answer the disk driver configuration information prompts by entering the information you recorded in IDREF="FM59231"Step 2.In NetWare v2.x, the interrupt number was decimal. In NetWare v3.x, the interrupt number is hexadecimal.(Optional) To test idxid="w3965"book="_idx" docset="nw312" tidref="i6772"third-party LAN drivers for compatibility, load them by typing  LOAD A: LAN_driver<Enter>Replace LAN_driver with the third-party v3.12 LAN driver.IDREF="FM76354"Table 7-2 lists all LAN drivers supported by Novell, Inc.Do not upgrade if LAN drivers are not compatible. Call the manufacturer to get an updated version of the driver.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears when you load the driver.LBL="7-2" INLINE="F"ID="FM76354"NetWare v3.12 idxid="w3966"book="_idx" docset="nw312" tidref="i3122"idxid="w3967"book="_idx" docset="nw312" tidref="i3072"LAN driversWIDTH="108"Cabling SystemWIDTH="156"Network BoardWIDTH="132"v3.12 LAN DriverWIDTH="108"ARCnetWIDTH="156"RX-NetRX-Net IIRX-Net/2WIDTH="132"TRXNETEthernetNE/2NE/2TNE2NE/2-32NE2_32 (replaces NE2-32)NE1000 - ASSY 950-054401NE1000 - ASSY 810-160-001NE1000NE2000 - ASSY 810-149NE2000T - ASSY 810-000220NE2000 PlusNE2000NE2100 - ASSY 810-000209NE2100NE1500T - ASSY 810-000214NE1500TNE3200NE3200NE32HUBNE32HUBToken ringNTR2000NTR2000Many more third-party LAN drivers are also included on the NetWare v3.12 System_4 diskette. idxid="w3968"book="_idx" docset="nw312" tidref="i6772"Third-party LAN driver manufacturers include3COMCabletronHewlett-PackardIBMIntelMadgeNCRProteonRacal DatacomStandard MicrosystemsThomas-ConradUngermann-Bass(Optional) Answer the LAN driver configuration information prompts by entering the information you recorded in IDREF="FM59231"Step 2.If the LAN driver loads, it can communicate with the network board and is compatible with NetWare v3.12.If the LAN driver does not load, it is either incompatible with v3.12 or the configuration is wrong.The following message appears:  Module xxx.LAN not loaded.Check the configuration and try again. If you're sure the configuration is correct, find out if you have the correct driver version.(Optional) Unload the third-party LAN drivers to free the memory for the upgrade by typing  UNLOAD LAN_driver<Enter>Insert the System_1 diskette in drive A: and load Macintosh name space support by typing  LOAD A:MAC <Enter>Loading the Macintosh name space module ensures that all volumes are mounted properly at the phase 4 bindery step.Continue the upgrade by determining which upgrade option to use. See IDREF="FM93322""Choose In-Place Upgrade Options" on page 275.ID="FM93322"Choose idxid="w3969"book="_idx" docset="nw312" tidref="i2778"In-Place Upgrade OptionsBefore doing an In-Place Upgrade, decide the following:Run the upgrade interactively?Run the upgrade as a batch process?The following sections discuss both options to help you make your decisions and then give you instructions for completing each task.Run the Upgrade Interactively?When you run the upgrade interactively, you are prompted whether to continue from one phase of the upgrade to the next, whether to create space for a DOS partition, and whether to have the NLM create and assign new passwords.Status messages and error messages are displayed.If you are a first time installer, use the interactive method so you can follow each phase of the upgrade.Run the Upgrade as a Batch Process?When you run the upgrade as a batch process, only error and status messages are displayed. The upgrade automatically proceeds through the phases without requiring input from the user.Use the optional parameters described on the next page to create space for a DOS partition and to assign random passwords to users. If no options are specified, the defaults are used.If you are an experienced installer and have run several upgrades, use the batch process method, especially if you are upgrading several servers.ID="FM95826"Run the idxid="w3970"book="_idx" docset="nw312" tidref="i2778"In-Place Upgrade The optional parameters shown in IDREF="FM63422"Table 7-3 can be entered whether the upgrade is run interactively or as a batch process.Make sure the System_1 diskette is still in drive A:.(Conditional) To run the upgrade interactively, type  LOAD A:2XUPGRDE <Enter>A warning screen appears. You are asked the following question:  Do you have a recent backup of your server? ySkip to IDREF="FM80222"Step 4. (Conditional) To run the upgrade as a idxid="w3971"book="_idx" docset="nw312" tidref="i2778"batch process, type  LOAD A:2XUPGRDE optional parameters<Enter>Replace optional parameters with any of the following:LBL="7-3" INLINE="F"ID="FM63422"In-Place Upgradeoptional idxid="w3972"book="_idx" docset="nw312" tidref="i2778"parametersWIDTH="60"ParameterWIDTH="252"ExplanationWIDTH="60"B or  BATCHWIDTH="252"Runs the upgrade in batch mode.BATCH2Runs the upgrade in batch mode, not pausing for non- critical errors.BINDERYSkips to phase 4 to upgrade the v2.1x bindery only.F or FASTSkips the memory and free disk space check.H, ? or  HELPShows a list of parameters.P0Does not create space for a DOS partition.PxCreates space for a DOS partition on volume SYS:(x = partition size in megabytes).Size range: 0 to 32 MB.Default: 5 MB.R or R+Assigns random passwords.R-Does not assign random passwords (default).You can enter the parameters in any order. Parameters can be separated by either a slash (/), a minus sign (-), or a space.For example, to run the upgrade as a batch process, create a 5MB DOS partition, and assign random passwords, type  LOAD A:2XUPGRDE /B /P5 /R+ <Enter>When the "Final Status" screen appears (IDREF="FM35781"Figure 7-7), continue with IDREF="FM41224"Step 9.ID="FM80222"To proceed with the upgrade, type "Y."If the procedure runs correctly (that is, if there are no power failures or power surges, etc.), you do not need to restore your disk from the backup. However, if a failure occurs, you may need to restore your disk to its previous condition.IDREF="FM83190"Table 7-4 on page 278 explains the In-Place Upgrade phases.LBL="7-4" INLINE="F"ID="FM83190"In-Place Upgrade idxid="w3973"book="_idx" docset="nw312" tidref="i2778"PhasesWIDTH="120"PhaseWIDTH="192"DescriptionWIDTH="120"1 System AnalysisWIDTH="192"Inventories each disk and each volume.Also ensures that the system has enough  memory to successfully complete the  upgrade.2 Disk AnalysisAnalyzes each disk.An image of the new NetWare v3.12 disk is  built and stored into memory.This phase is non-destructive and does not  damage the existing NetWare v2.1x or v2.2  file system.3 Disk Modification Writes the new NetWare v3.12 file system  to the disk, destroying the NetWare v2.1x  or v2.2 file system.A hardware failure during this phase results  in the irrecoverable loss of data on the  server.4 BinderyUpdates bindery objects, properties, and  values such as user accounts and  passwords. In NetWare v2.1x, these were  included in two files in SYS:SYSTEM:NET$BIND.SYS (for objects and properties)NET$BVAL.SYS (for property data sets)Random user passwords are assigned if  requested.The DOS partition screen (IDREF="FM43891"Figure 7-1) appears.LBL="7-1"ID="FM43891"DOS partition screenFILE="n312i79a.pbm"At the prompt, enter the number of megabytes you want for the DOS partition and press <Enter>.The In-Place Upgrade can create the space (between 0 and 32 MB) for a DOS partition on the disk that contains volume SYS:. We recommend a idxid="w3974"book="_idx" docset="nw312" tidref="i1684"DOS partition of at least 5 MB.Booting the server from a DOS partition is significantly faster than booting from a diskette.The "0" option is available for servers that boot from a diskette rather than from a DOS partition.If you use a DOS boot diskette, refer to the procedures under IDREF="FM67215""Install Server Software for Use with a DOS Boot Diskette" on page 22.If there is not enough space on your disk to create a DOS partition, the upgrade stops and displays the following:  This NetWare server has insufficient free hard disk space to complete the upgrade. The In-Place Upgrade process is now being aborted.Reboot the NetWare v2.1x file server, and then restart the upgrade. Delete unnecessary files to free more space on the disk.After you create the DOS partition, the following screens appear.IDREF="FM25546"Figure 7-2, "System Analysis screen,"  details the System Analysis phase where each disk is scanned and inventoried.LBL="7-2"ID="FM25546"System Analysis screenFILE="n312i80a.pbm"IDREF="FM36657"Figure 7-3, "Disk Analysis screen 1," details the first portion of the Disk Analysis phase.This screen only appears if multiple disks are being upgraded.These extra phases are run to determine how much server memory and free disk space is required per volume to successfully complete the upgrade.LBL="7-3"ID="FM36657"Disk Analysisscreen 1FILE="n312i81a.pbm"Servers with only one hard disk proceed directly to the second part of the idxid="w3975"book="_idx" docset="nw312" tidref="i1544"Disk Analysis phase. See Figure 7-4.The calculations made during the first part of the Disk Analysis phase are discarded to conserve server memory.As shown in IDREF="FM75050"Figure 7-4, "Disk Analysis screen 2," the Disk Analysis phase analyzes each disk. An image of the new NetWare v3.12 disk is built and stored in memory.This phase is nondestructive and will not damage the existing NetWare v2.1x file system.LBL="7-4"ID="FM75050"Disk Analysisscreen 2FILE="n312i83a.pbm"IDREF="FM48810"Figure 7-5, "Disk Modification screen,"  details the Disk Modification phase. In this phase, the NetWare v2.1x file system is overwritten by the v3.12 file system.The idxid="w3976"book="_idx" docset="nw312" tidref="i1588"Disk Modification phase is the only destructive phase of the upgrade. This phase must be completed before NetWare v3.12 can use the disk.LBL="7-5"ID="FM48810"Disk Modification screenFILE="n312i82a.pbm"At the Disk Modification screen, type "Y" to continue with the upgrade or type "N" to quit.If you have multiple disks, the Disk Analysis and Disk Modification process repeats itself.After all disks have been upgraded, volume SYS: is mounted and the bindery is upgraded. The NetWare v2.1x bindery is merged into the newly created v3.12 bindery.The Bindery phase updates bindery objects, properties, and values such as user accounts and passwords.LBL="7-6"Bindery screenFILE="n312i84a.pbm"(Conditional) In the process of assigning passwords, if you did not use the [R+] or [R-] or [B] parameters when you started the upgrade, you are prompted to assign random passwords.See IDREF="FM39085"Step 8 for password options.ID="FM39085"Choose one of the following idxid="w3977"book="_idx" docset="nw312" tidref="i4980"password options:WIDTH="144"Password OptionWIDTH="168"DescriptionWIDTH="144"Y (assign random passwords)WIDTH="168"A random password for each user  who originally had a password is  created by the utility and stored in a  file called NEW.PWD.User SUPERVISOR is not assigned a  password.Only the network supervisor has  access to this file.Users cannot log in until the  supervisor gives them their password  from this list.N (assign no passwords)Users are not prompted for a  password when they first log in. However, after they have logged in  once, and if their accounts are set to  require passwords, they are  prompted to type a new password.The idxid="w3978"book="_idx" docset="nw312" tidref="i2428"Final Status screen displays how your disks and volumes were affected by the upgrade. See IDREF="FM35781"Figure 7-7, "Final Status screen," for an example.LBL="7-7"ID="FM35781"Final Status screenFILE="n312i78a.pbm"The NetWare v2.1x file system has been upgraded to a v3.12 file system.ID="FM41224"Press any key to receive further instructions and then return to the console prompt (:).Mount idxid="w3979"book="_idx" docset="nw312" tidref="i7340"VolumesProcedureMount volume SYS: and other volumes by typing  MOUNT ALL <Enter>Temporarily prevent users from logging in by typing  DISABLE LOGIN <Enter>This prevents users from logging in as SUPERVISOR. To allow users to log in when the upgrade is completed, type  ENABLE LOGIN <Enter>Load idxid="w3980"book="_idx" docset="nw312" tidref="i3123"LAN DriversProcedureInsert the System_2 diskette in drive A:.Load the appropriate LAN drivers by typing  LOAD A:LAN_driver<Enter>See Table 7-2 for a list of Novell LAN drivers.The default frame type for NetWare v3.12 is Ethernet 802.2. To user the Ethernet 802.3 frame type, used in NetWare v3.11 and earlier, add "frame=Ethernet_802.3" when loading the LAN driver.For example, type  LOAD A:NE2000 frame=Ethernet_802.3 <Enter>Bind LAN drivers to the server's registered protocol.For example, to bind IPX to the NE2000 LAN driver, type  BIND IPX TO NE2000Enter the network number for your cabling system. To bind the Ethernet 802.3 frame type to the LAN_driver, add "frame=Ethernet_802.3" when binding the protocol.For example, type  BIND IPX to NE2000 frame=Ethernet_802.3 <Enter>Copy idxid="w3981"book="_idx" docset="nw312" tidref="i6656"idxid="w3982"book="_idx" docset="nw312" tidref="i5696"SYSTEM and PUBLIC FilesProcedureInsert the System_1 diskette in drive A:.Load INSTALL.NLM by typing  LOAD A:INSTALL <Enter>Choose "System Options" and press <Enter>.From the "Available System Options" menu, choose "Copy System and Public Files" and press <Enter>.Insert diskettes as prompted. ID="FM88088"Create a STARTUP.NCF FileA STARTUP.NCF file contains commands to load the disk drivers and name space support for your file server.This file is executed after SERVER.EXE and is stored on the disk you boot from (hard disk or diskette).Once this file loads the disk drivers and name space support, and mounts volume SYS:, it turns control over to AUTOEXEC.NCF to complete the boot process.ProcedureInsert the writeable System_1 diskette into drive A:.Select "Create idxid="w3983"book="_idx" docset="nw312" tidref="i6489"STARTUP.NCF File" from the "Available System Options" menu.Enter the proper drive letter on the "Path For STARTUP.NCF File" screen.Use <Backspace> to make sure the drive is set toC: to boot from hard disk.A: to boot from drive A:. (This file can be copied to drive C: later.)Press <Enter>.A screen similar to the following appears:LBL="7-8"A sample STARTUP.NCF fileFILE="n312i28a.pbm"The operating system reads the information you previously entered for disk drivers and name space support.From the following table, determine your system configuration and decide which additional commands you would like added to the STARTUP.NCF file.WIDTH="84"To WIDTH="216"Add these or other commandsWIDTH="84"Load name  spaces for  Macintosh,  OS/2, UNIX, or  FTAMWIDTH="216"LOAD MAC.NAMLOAD OS2.NAMLOAD NFS.NAMLOAD FTAM.NAM(These commands must precede the command to  mount the volume that stores the files using the  name space.)Set server  parameters(You can add the following eight commands to the  STARTUP.NCF file only. You can add other SET  commands to the STARTUP.NCF and to the  AUTOEXEC.NCF file.)SET Maximum Physical Receive Packet SizeSET Cache Buffer SizeSET Reserved Buffers Below 16 MegSET Maximum Subdirectory Tree DepthSET Concurrent Remirror RequestsSET Auto TTS Backout FlagSET Minimum Packet Receive Buffers(For more on these and other SET parameters, see  "book="utilref" docset="nw312"SET" in Utilities Reference, or type "SET" at the  server console.)Pause after each  commandPAUSEType one command per line.Press <Esc> to save the file.Create an AUTOEXEC.NCF FileAn idxid="w3984"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF file contains commands to complete the boot process after SERVER.EXE and STARTUP.NCF executes.Because AUTOEXEC.NCF is saved in and runs from SYS:SYSTEM, place most boot commands (except the disk driver and name space support commands) in AUTOEXEC.NCF.Commands you can use in AUTOEXEC.NCF do the following:Name the file server.Assign the internal network number for the file server.Load LAN drivers for the file server and assign the network number.Bind LAN drivers to the file server's registered protocol.Load other modules you want loaded when the file server boots. (See "book="sysadmin" docset="nw312"LOAD" inSystem Administration.)Execute other console commands (such as TRACK ON or VOLUMES) during the boot process.Set other parameters for the file server. (See "book="sysadmin" docset="nw312"SET" inSystem Administration.)Mount volumes.ProcedureFrom the "Available System Options" menu, select "Create AUTOEXEC.NCF File."The operating system gathers information you have previously entered at the console prompt for this file.A screen similar to the following appears, showing the commands that are automatically placed in idxid="w3985"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF.LBL="7-9"A sample AUTOEXEC.NCF fileFILE="n312i27a.pbm"When using the 802.3 frame type, rather than the 802.2 default, the screen shown above displays the frame type number.If you load multiple LAN drivers, your AUTOEXEC.NCF file is different. See "book="sysadmin" docset="nw312"INSTALL" inSystem Administration.(Optional) From the table below, decide which loadable modules to load with idxid="w3986"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF.WIDTH="168"ToWIDTH="144"Add these modulesWIDTH="168"Create disk partitions, create  volumes, format a hard disk, etc.WIDTH="144"LOAD INSTALLLock the file server console, view  network operation information.LOAD MONITORLoad the print server on the file  server and establish print services.LOAD PSERVER finance_printCorrect volume problems or remove  name space entries from File  Allocation and directory tables.LOAD VREPAIRTo delete or modify commands, backspace to erase the command.(Optional) From your system configuration, determine additional loadable modules to include in AUTOEXEC.NCF.Additional module types are shown in the table below.WIDTH="168"Module TypeWIDTH="144"Module NameWIDTH="168"EquipmentWIDTH="144"UPS.NLMRemote ConsoleREMOTE.NLMRSPX.NLMRemote Boot for token ringTOKENRPL.NLMRemote boot for IBM and Western  Digital on EthernetETHERRPL.NLMThird-party loadable modules(See third-party  documentation)If you use an uninterruptible power supply, see "book="sysadmin" docset="nw312"UPS" inSystem Administration for troubleshooting tips.Some loadable modules need other loadable modules to function. If the prerequisite module is not loaded first, the operating system will look at your default drive and then at SYS:SYSTEM and automatically load the necessary module.From the table below, decide if you want any of the following console commands to execute with the idxid="w3987"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF file.WIDTH="120"ToWIDTH="192"Add these console commandsWIDTH="120"Implement security  measuresWIDTH="192"SECURE CONSOLEDisplay the processor  speedSPEEDDecide from the table below additional commands you would like added to AUTOEXEC.NCF.WIDTH="120"To WIDTH="192"Add these or other commandsWIDTH="120"Mount Volumes.WIDTH="192"MOUNT VOL1 (or other volume name)MOUNT ALLNote: Volume SYS: is mounted  automatically when its corresponding disk  driver is loaded during the STARTUP.NCF  file's execution.Bind protocols other  than IPX to the LAN  drivers.BIND IP to...Set server parameters.SET commands (see "book="utilref" docset="nw312"SET" in Utilities  Reference.)Pause after each  command.PAUSE(Optional) Allow unencrypted idxid="w3988"book="_idx" docset="nw312" tidref="i4980"idxid="w3989"book="_idx" docset="nw312" tidref="i7071"passwords.Use the table on the next page to help you decide whether to use unencrypted passwords on a network using encrypted passwords.WIDTH="144"ForWIDTH="168"UseWIDTH="144"A new installation with one file  server on the network.WIDTH="168"Encrypted passwords.Upgrading from NetWare v2.x  operating system.Encrypted passwords temporarily.A NetWare v3.12 file server  running on the same network  as NetWare v2.11 or earlier.Encrypted passwords permanently.A NetWare v3.12 file server  running on the same network  as NetWare v2.11 or v2.15.Encrypted passwords. Use SET in  AUTOEXEC.NCF until utilities on  other file servers are upgraded.Copy NetWare v3.12 utilities to all  NetWare v2.12 or v2.15 file servers  to allow all servers to use encrypted  passwords. (See "book="utilref" docset="nw312"Appendix A" of Utilities Reference.)Type the following command at the console prompt to allow unencrypted passwords:  ID="FM43895"SET ALLOW UNENCRYPTED PASSWORDS=ON <Enter>For more information on AUTOEXEC.NCF files or on the commands listed above, seebook="sysadmin" docset="nw312"System Administration. See also "book="concepts" docset="nw312"Boot Files" inConcepts.Press <Esc> to save the file.Press <Esc> twice to exit INSTALL.Format the idxid="w3990"book="_idx" docset="nw312" tidref="i1684"DOS PartitionProcedureAt the console prompt (:), down the server by typing  DOWN <Enter>Insert the INSTALL diskette in drive A:.Return to the DOS prompt by typing  EXIT <Enter>From the downed server, create a DOS primary partition and make it the active partition by typing  FDISK <Enter>The two utilities used to partition and format the DOS partition are found on the bootable INSTALL diskette. These DR DOS files, FDISK.COM and FORMAT.COM, also ship with NetWare v3.12.FDISK is a DOS utility that creates or deletes DOS partitions on your hard disk. It can also select which partition is active. The DOS partition is placed on the first few cylinders of the hard disk. The server reboots DOS as part of the FDISK process.Format the new DOS partition.If you are using DR DOS, the format command is as follows:  FORMAT C:/s/x <Enter>The /s parameter makes the partition bootable.The /x parameter tells DR DOS that it is formatting a hard drive.If you are using DR DOS to format your hard drive, use FORMAT.COM on the INSTALL diskette or a later version.If you are not using DR DOS, type the format command as follows:  FORMAT C:/s <Enter>Reboot the server to make sure that DOS boots from the hard disk.ID="FM42218"Copy the New idxid="w3991"book="_idx" docset="nw312" tidref="i730"Boot Files to a Boot DirectoryProcedureID="FM51381"Create a boot directory.For example:  C:\SERVER.312The boot files are copied to this directory on drive C:.ID="FM92205"Copy the newly created STARTUP.NCF file from the System_1 diskette to the boot directory by typing  COPY A:\STARTUP.NCF C:\Boot_directory<Enter>Change to the A: drive by typing  A: <Enter>Insert the NetWare v3.12 Install diskette into drive A:, and type  A:NWNSTLL /IN_PLACE <Enter>The "Select an Installation Option" menu appears.Choose "Upgrade NetWare v3.1x or v4.x."The "Copy Files to the DOS Partition" screen appears.Specify the destination directory (where you want the boot files to be copied).Copy the NetWare v3.12 server boot files to the boot directory.Press <F4>.The "Enter the destination path" screen appears.ID="FM93344"Enter the destination path created in IDREF="FM51381"Step 1 for the files to be copied.This should be the same directory that the STARTUP.NCF was copied to in IDREF="FM92205"Step 2.WIDTH="132"ToWIDTH="180"ThenWIDTH="132"Change the source drive.WIDTH="180"Press <F2> and enter a new drive letter  or directory, and then press <Enter>.Change the destination  directory on drive C:.Press <F4>, enter a directory name,  choose "Yes," and then press <Enter>.The following files are copied to the newly-created boot directory on drive C: (or another directory on C: that you specify.)SERVER.EXE (the NetWare operating system).NUT.NLM (an interface utility needed for certain NetWare Loadable Modules).NWSNUT.NLM (an interface utility needed for certain NetWare Loadable Modules).Disk drivers (*.DSK).Name space modules (*.NAM).CLIB.NLM (C runtime library).Diagnostic NLMs (*.NLM).INSTALL.NLM (the installation utility).LAN drivers (*.LAN).Message and help files. If the directory you specified in IDREF="FM93344"Step 7b does not exist, the following message appears:  Do you want to create "directory name." Y/NIf you use a third-party driver not shipped in the red box, you may need to exit INSTALL and copy the disk driver (*.DSK) to the new boot directory.ID="FM36565"If you choose "Yes," press <Enter> to create the new directory.Copy your STARTUP.NCF file into the new directory if it is different than the directory created in IDREF="FM51381"Step 1.Press <Enter> to continue.Insert the diskettes as prompted.Once the files have been copied, the following screen appears:LBL="7-10"idxid="w3992"book="_idx" docset="nw312" tidref="i3350"Locale configuration screenFILE="n312i125.pbm"ID="FM92806"Enter your Country Code, Code Page, and Keyboard Mapping setting and press <F10>.For a list of settings for each field, highlight a field and press <Enter>, or refer to your DOS manual.The keyboard mapping command is automatically added to the STARTUP.NCF file.The following screen appears.LBL="7-11"Select a formatFILE="n312i126.pbm"Select a format for your DOS files and press <Enter>.Selecting "NetWare Filename Format" leaves previously-saved DOS files with non-standard DOS characters as they were.The upgrade is complete.From the boot directory, load the server operating system by typing  SERVER <Enter>Complete the steps under IDREF="FMUpgra""What to Do After the Upgrade" on page 307.ID="FM23283"NetWare v3.x to v3.12 idxid="w3993"book="_idx" docset="nw312" tidref="i2778"UpgradeWhat this Procedure DoesCopies new NetWare v3.12 files onto the DOS partition on the NetWare v3.1x server's hard disk.This includes idxid="w3994"book="_idx" docset="nw312" tidref="i1251"SYSTEM and PUBLIC files, SERVER.EXE, disk and LAN drivers, name space support modules, and other loadable modules.Scans the server idxid="w3995"book="_idx" docset="nw312" tidref="i4371"configuration files (STARTUP.NCF and AUTOEXEC.NCF) to make sure information gets updated (especially Ethernet driver frame types).How NetWare idxid="w3996"book="_idx" docset="nw312" tidref="i4203"Name Service Servers Get UpgradedIf you are upgrading a NetWare v3.11 serving running NetWare Name Service (NNS), we strongly recommend upgrading all v3.11 servers in a domain at the same time.Do not log in to the upgrade server until the NNS files have been reinstalled.Necessary idxid="w3997"book="_idx" docset="nw312" tidref="i2778"ResourcesMinimum of 4MB RAM on the server.Minimum of 25 MB free space on volume SYS:.A NetWare v3.0 or v3.11 server with all volumes mounted. This upgrade program upgrades binderies only for mounted volumes.Working copies of the NetWare v3.12 diskettes. For an installation from a network directory, a drive mapped to the working areas where copies of the diskette files are located.Prerequisites idxid="w3998"book="_idx" docset="nw312" tidref="i2778"(Optional) Use the NetWare v3.1x SALVAGE utility to restore deleted files.To salvage already-deleted files, restore them before upgrading.As you mount existing volumes under NetWare v3.12 version of NetWare, purged files are eliminated and appear on the FILER utility screen as eliminated files.Make sure you have a fully functional backup of your NetWare v3.x system. Do not attempt an upgrade without one.Notify users to log out of the NetWare v3.x server.Broadcast a message from the console (using the BROADCAST command) that users must log out before the server upgrade. Users (this includes print servers) must stay logged out until the upgrade is complete.If you are using third-party NLMs, disk drivers (*.DSK), or LAN drivers (*.LAN), check with your Novell Authorized Reseller for compatibility issues before upgrading your network.Most third-party disk and LAN drivers written for NetWare v3.1x work with v3.12.Start the Upgrade to NetWare v3.12ProcedureLoad v3.1x INSTALL.NLM and edit the idxid="w3999"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF file with respect to frame types.NetWare v3.12 accepts 802.2 and 802.3 idxid="w4000"book="_idx" docset="nw312" tidref="i2504"frame types. The idxid="w4001"book="_idx" docset="nw312" tidref="i64"default for NetWare v3.12 is 802.2.For Ethernet networks, we recommend that you load both frame types, or that your frame type be set at 802.3 until all file servers and workstations are upgraded to v3.12.Down the server.At the system console (:), type  DOWN <Enter>Exit to DOS by typing  EXIT <Enter>Copy all old idxid="w4002"book="_idx" docset="nw312" tidref="i730"boot files to another diskette or directory.Take this precautionary measure to ensure that you have a backup of your old boot files.Boot files include:*BAT*.DSK (disk drivers)INSTALL.NLM*.LAN (LAN drivers)*.NAM (name spaces)SERVER.EXESTARTUP.NCFVREPAIRAUTOEXEC.NCFID="FM45170"Complete the Upgrade to idxid="w4003"book="_idx" docset="nw312" tidref="i2778"NetWare v3.12 Using idxid="w4004"book="_idx" docset="nw312" tidref="i2837"INSTALL.NLMProcedureInsert the NetWare v3.12 INSTALL diskette into drive A: and type  INSTALL <Enter>Choose "Update NetWare v3.1x to v3.12.The "Copy Files to the DOS Partition" screen appears. You must specify the idxid="w4005"book="_idx" docset="nw312" tidref="i1396"destination directory (where you want SERVER.EXE, etc. to be copied).ID="FM46237"Copy the new NetWare v3.12 idxid="w4006"book="_idx" docset="nw312" tidref="i4384"server boot files to the boot directory.Press <F4>.The "Enter the destination path" screen appears.Enter the destination path for the files to be copied.WIDTH="120"ToWIDTH="192"ThenWIDTH="120"Change the idxid="w4007"book="_idx" docset="nw312" tidref="i6413"source drive.WIDTH="192"Press <F2> and enter a new drive letter or  directory, and then press <Enter>.Change the destination  directory on drive C:Press <F4>, enter a directory name, choose  "Yes," and then press <Enter>.For example:  C:\SERVER.312The files are copied from the Install diskette to the destination directory on drive C:.The following files are copied to the newly-created boot directory, on drive C: (or another directory on C: that you specify.Standard disk drivers (*.DSK)INSTALL.NLM (the installation utility)Message and help filesNWSNUT.NLM (an interface utility needed for certain NetWare Loadable Modules)LAN drivers (*.LAN)SERVER.EXE (the NetWare operating system)If you enter a directory other than your original NetWare v3.1x directory (such as SERVER.312), complete IDREF="FM50161"Steps 3c and IDREF="FM33230"3d.ID="FM50161"If the directory that you specified in Step 3b does not exist, the following message appears:  Do you want to create the directory "directory name." Y/NIf you are using a third-party driver not shipped in the red box, you may need to exit the INSTALL and copy the disk driver (*.DSK) to the new boot directory.ID="FM33230"If you choose "Yes," press <Enter> to create the new directory. The following message appears:  Enter the path to your existing SERVER.EXE file.Type the path to your existing SERVER.EXE file.ID="FM43771"After you set the destination path, insert the diskettes as prompted.Once the appropriate files have been copied, the following message appears:  OK to invoke existing STARTUP.NCF file?WIDTH="60"If you chooseWIDTH="240"ThenWIDTH="60"YesWIDTH="240"The existing STARTUP.NCF file is invoked in the directory  specified in IDREF="FM46237"Step 3.NoA new STARTUP.NCF file is created in your new boot  directory.Your decision whether to invoke the existing STARTUP.NCF file or create a new one will determine whether you will use your existing STARTUP.NCF file or create a new AUTOEXEC.NCF file as well.Once the files have been copied, the following screen appears:LBL="7-12"idxid="w4008"book="_idx" docset="nw312" tidref="i3350"idxid="w4009"book="_idx" docset="nw312" tidref="i3350"Locale configuration screenFILE="n312i125.pbm"ID="FM92806"Enter your Country Code, Code Page, and Keyboard Mapping setting and press <F10>.For a list of settings for each field, highlight a field and press <Enter> or refer to your DOS manual.The following screen appears.LBL="7-13"Select a formatFILE="n312i126.pbm"Select the desired idxid="w4010"book="_idx" docset="nw312" tidref="i1678"format for your DOS files and press <Enter>.Selecting "NetWare Filename Format" leaves previously-saved DOS files with non-standard DOS characters are they are.Selecting "DOS Filename Format" replaces all non-standard DOS characters with standard DOS characters.If you select "DOS Filename Format," and your selection in Step 8 is unchanged, press <F9> to view what character changes will be made.You are asked if you want to specify any startup SET commands.Select "Yes" or "No."Selecting "Yes" brings up a blank screen for entering the special startup commands. Use this screen mainly for changing the default setting of SET AUTO REGISTER MEMORY to OFF.Turning off SET AUTO REGISTER MEMORY allows you to load disk drivers that can't be loaded in the memory area above 16 MB.Changing the SET AUTO REGISTER MEMORY setting to OFF disables all memory above 16MB. For optimal use of RAM, install a disk driver that can be loaded in the memory area above 16MB.The documentation that accompanied your disk driver will indicate the RAM required for loading.Press <F10> to save the startup commands.Copy the NetWare v3.1x idxid="w4011"book="_idx" docset="nw312" tidref="i6489"STARTUP.NCF file into the boot directory.The STARTUP.NCF file resides in the boot directory of your NetWare v3.1x server and contains commands to load the disk driver and to mount volume SYS:.INSTALL copies the old v3.1x STARTUP.NCF file into the boot directory to ensure that the server will boot like it used to.Press <Alt><Esc> to get to the system console screen.You are prompted for the file server name.Enter the file idxid="w4012"book="_idx" docset="nw312" tidref="i4371"server name and press <Enter>.To avoid changing the server name in all login scripts, leave the server name the same as the existing v3.11 server name.You are prompted for the IPX internal network number.Type the idxid="w4013"book="_idx" docset="nw312" tidref="i3018"IPX internal network number and press <Enter>.If you decided in IDREF="FM43771"Step 4 to create a new STARTUP.NCF file, continue with IDREF="FM46855"Step 14. If you decided to invoke the existing STARTUP.NCF file, skip to IDREF="FM46593"Step 19.ID="FM46855"Load your disk driver by typing  LOAD disk driver<Enter>Load your LAN driver by typing  LOAD LAN driver<Enter>(Conditional) Define the I/O port number by accepting the default number shown on the screen, or by selecting a new one.(Conditional) Define the interrupt number by accepting the default number shown on the screen, or by selecting a new one.idxid="w4014"book="_idx" docset="nw312" tidref="i3967"Mount volume SYS: and other defined volumes by typing  MOUNT ALL <Enter>ID="FM46593"Press <Alt><Esc> to get to the "System Install" screen.Select "System Options" and press <Enter>.The "Available System Options" menu appears.Select "Copy System and Public Files" and press <Enter>.Insert the diskettes as prompted.(Conditional) If you are performing a same-server migration, go to IDREF="FM93156"Step 24 on page 258.Read "What to Do After the Upgrade" IDREF="FMUpgra"on page 307.What to ID="FMUpgra"Do After the idxid="w4015"book="_idx" docset="nw312" tidref="i2778"UpgradeID="FM83559"Complete the following steps before allowing users to log in.ProcedureChange ID="FMSUPER"SUPERVISOR password.Log in from a workstation as SUPERVISOR. Change the password using either SETPASS or SYSCON.Change user ID="FMPassw"passwords.If you chose to assign random passwords, print the NEW.PWD file and distribute the password information to each user. Users should change their passwords immediately, using either SETPASS or SYSCON.Check idxid="w4016"book="_idx" docset="nw312" tidref="i424"applications to see if they run properly.Some DOS applications don't work when installed on volumes that have more than 32 MB of disk space. Some of these applications can be made to work by doing the following:Restrict the application's directory on the destination server with DSPACE.Make the directory path a fake root using the MAP command.Check idxid="w4017"book="_idx" docset="nw312" tidref="i1502"directory security.Check directory security if you used either of the following items for NetWare v2.1x security:Maximum Rights MaskPrivate attributeSet new idxid="w4018"book="_idx" docset="nw312" tidref="i1483"directory and idxid="w4019"book="_idx" docset="nw312" tidref="i2004"file attributes using FLAG or FILER.For a list of directory and file attributes, see IDREF="FM95041"Table 5-5 through IDREF="FM83355"5-6 in Chapter 5.Check directories for unnecessary NetWare files.NetWare v2.1xThe following idxid="w4020"book="_idx" docset="nw312" tidref="i4203"NetWare v2.1x files are not compatible with NetWare v3.12 and should be deleted.VAP files (*.VAP, *.HLD, *.VP?)LARCHIVE.EXELRESTORE.EXEMACBACK.EXENARCHIVE.EXENRESTORE.EXENET$BIND.SYSNET$BVAL.SYSNET$BIND.OLDNET$BVAL.OLDNET$ERR.SYSNET$OS.EXENET$DOS.SYSNET$MSG.SYSNET$REC.DATHIDEFILE.EXE and SHOWFILE.EXE still work but have not been included in NetWare v3.x.These files were copied into SYS:SYSTEM. You can either delete them (FLAG allows users to add and remove System and Hidden attributes from files) or leave them.NetWare v2.0aThe following idxid="w4021"book="_idx" docset="nw312" tidref="i4203"NetWare v2.0a files are not compatible with NetWare v3.x. They should be deleted.ENDSPOOL.EXEQ.EXEQUEUE.EXESPOOL.EXEThe utilities listed above are replaced by ENDCAP, PCONSOLE, and CAPTURE in NetWare v3.12. For more information, see book="utilref" docset="nw312"Utilities Reference.Modify the system and idxid="w4022"book="_idx" docset="nw312" tidref="i3537"user idxid="w4023"book="_idx" docset="nw312" tidref="i3513"login scripts.Update references to the server in the system and user login scripts if you changed the server name.Although user login scripts are upgraded, they are not modified and server names are not changed to match your new environment. Use SYSCON to modify the login scripts.With NetWare v2.x, you could give users drive mappings to directories in which they had not been granted rights. NetWare v3.12 will not allow users to have drive mappings to directories in which they have not been assigned rights.If you have set up your login scripts so that users have drive mappings to directories in which they have no rights, these users receive the following message when they log in:  Attempt to map drive to invalid path in MAP command.Complete one of the following:Delete the drive mapping from the login script.Delete the drive mapping from the system login script and insert the drive mapping in the user login scripts only when the user has been granted rights to the directory.Create a group, grant the group the trustee assignment, assign the appropriate users to the group, and then use an IF. . . THEN command in the system login script before the drive mapping (IF member of "groupname," THEN map p:=volume:directory).Create new idxid="w4024"book="_idx" docset="nw312" tidref="i725"boot diskettes for each idxid="w4025"book="_idx" docset="nw312" tidref="i7493"idxid="w4026"book="_idx" docset="nw312" tidref="i728"workstation.All users on the NetWare v3.x file server need to boot with the new shell and IPX files before they log in.If the server was renamed, change the file server's name in the users' AUTOEXEC.BAT files to the new v3.12 file server name.If you have other NetWare v2.x file servers on your network, upgrade the workstation files for those users even if you aren't upgrading the file server.The new workstation files shipped with NetWare v3.12 are compatible with NetWare v2.x. All users on the internetwork should use the latest version of the workstation files to ensure that there are not conflicts.(Conditional) Copy the NetWare v3.12 idxid="w4027"book="_idx" docset="nw312" tidref="i7237"idxid="w4028"book="_idx" docset="nw312" tidref="i4444"utilities to other file servers on the network.The NetWare v3.x public utilities will run on file servers running NetWare v2.x. Complete one of the following:If you have file servers running v2.0a, v2.10, or v2.11, do not copy the NetWare v3.x public utilities to them. However, copy the NetWare v3.x LOGIN.EXE file to the SYS:LOGIN and SYS:PUBLIC directories.If you have NetWare v2.12 or v2.15 file servers on your network, replace the NetWare public utilities with the NetWare v3.x public utilities to allow the v2.12 and v2.15 file servers to work with encrypted passwords.To copy utilities, complete the following steps:Log in to the NetWare v2.x file server as SUPERVISOR.Flag the NetWare v2.x utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, type  FLAG *.* N <Enter>Protect the system login script. In the SYS:PUBLIC directory, type  FLAG NET$LOG.DAT SRO <Enter>Map a drive to the SYS:PUBLIC directory on the NetWare v3.12 file server by typing  MAP drive:=fileserver/SYS:PUBLIC <Enter>Replace drive with a drive letter not being used and replace fileserver with the name of the NetWare v3.12 file server.ID="FM85318"Enter your username and password for the NetWare v3.12 file server.ID="FM26837"Copy the NetWare v3.12 PUBLIC files to the NetWare v2.x file server.For example, if drive Q is mapped to SYS:PUBLIC on the NetWare v3.12 server and drive F is mapped to SYS:PUBLIC on the NetWare v2.x file server, change to drive F and type  NCOPY Q:*.* <Enter>Flag the NetWare v3.12 utilities on the NetWare v2.x file server Shareable and Read Only. Type  FLAG *.* SRO <Enter>Repeat IDREF="FM85318"Steps 9e and IDREF="FM26837"9f for the SYS:LOGIN directory.Login scripts on the NetWare v3.12 file server do not execute properly unless you copy the NetWare v3.12 login programs to all NetWare LOGIN directories on your internetwork.When you have copied the NetWare v3.12 utilities to all NetWare v2.1x file servers and you do not have any NetWare v2.0a file servers, you can change the setting for unencrypted passwords. At the console prompt of the NetWare v3.12 file server, type  SET ALLOW UNENCRYPTED PASSWORDS=OFF <Enter>If you still have NetWare v2.0a file servers on your internetwork, the setting at the NetWare v3.12 file server for unencrypted passwords must be ON.If your v2.x server had mirrored disks, remirror them using INSTALL.NLM.Update as necessary upgraded print queues using PCONSOLE.Use NBACKUP to make a backup copy of all data on the NetWare v3.12 server.For NBACKUP instructions, see book="utilref" docset="nw312"Utilities Reference.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it.(Optional) If your network includes workstations that use an operating system that supports long filenames, make sure you have loaded the name space module, then use the idxid="w4029"book="_idx" docset="nw312" tidref="i145"ADD NAME SPACE command to add name space to the volume. Type  ADD NAME SPACE name-support TO VOLUME volume_name<Enter>For example, if you have a volume named MAC for Macintosh files, type the following at the console prompt:  ADD NAME SPACE MACINTOSH TO VOLUME MAC <Enter>Use the command once for every volume that needs to store files with long names.To ensure name space support each time the file server is brought up, load the appropriate name space module in the STARTUP.NCF file.(Optional) To store idxid="w4030"book="_idx" docset="nw312" tidref="i3661"Macintosh files and folders on a NetWare v3.12 server, install NetWare for Macintosh (a separate Novell product) on the v3.12 server.This product provides support for Macintosh workstations that connect to the v3.12 server.Allow users to log in to the NetWare v3.12 file server.User can log in ifVolume SYS: is mountedThe user exists in the binderyThe LAN driver is loaded and bound to a protocolLogin is enabledTo ensure that login is enabled, type  ENABLE LOGIN <Enter>LBL="A"ID="FM82264"Optimizing Network PerformanceTwo concepts are vital to fine-tune a NetWare v3.12 file idxid="w4031"book="_idx" docset="nw312" tidref="i4371"idxid="w4032"book="_idx" docset="nw312" tidref="i7052"idxid="w4033"book="_idx" docset="nw312" tidref="i5066"server to achieve idxid="w4034"book="_idx" docset="nw312" tidref="i4846"optimized performance:A NetWare v3.12 server is not a single device, but rather a collection of components and subsystems that directly or indirectly affect the performance of the entire network.The NetWare v3.12 operating system is designed to be as self-tuning as possible.This appendix briefly discusses server components and ways of optimizing them.It also gives fine tuning tips, including guidelines on how to adjust NetWare v3.12 SET command parameters.File server optimization is not an exact science and each file server configuration is unique.For these reasons the tips and techniques described in this appendix may or may not prove effective for your network environment.Do not proceed with this appendix until you have given your newly installed or upgraded server adequate time to tune itself.You should not expect your server to be fully optimized immediately following installation or upgrade. NetWare v3.12 must be allowed to fully use the individual components that make up NetWare v3.12.We also recommend that you not test your server for performance without first tuning the server for performance.For more on the subjects covered in this appendix, see "Netware v3.11 Server Tuning and Optimization" in NetWare Application Notes 3(6):1-40 (June 1992).idxid="w4035"book="_idx" docset="nw312" tidref="i4371"Server ComponentsThe principal NetWare v3.12 server components that can be modified for performance areMemory. NetWare is extremely memory-oriented and makes extensive use of caching.The communications subsystem. This is the server's LAN I/O channel.A number of areas can affect performance within this category: packet size, communication buffers, Packet Burst(tm) protocol, SAP traffic, and network boards.The file system and cache. NetWare's file system is very closely related to cache.The system processor. If all other server components are optimized, the ultimate bottleneck could be the system processor and bus.Use NetWare v3.12 SET parameters to optimize these server components and, as a result, the network. Tuning these server components is explained in the following sections.The idxid="w4036"book="_idx" docset="nw312" tidref="i4444"NetWare v3.12 Memory ModelThe memory model for NetWare v3.12 is based on the use of 32-bit registers, which enables NetWare to provide access to one flat segment of RAM up to 4 GB.The entire NetWare environment---the operating system (OS), LAN and disk drivers, and NLMs---can be loaded into this RAM segment.idxid="w4037"book="_idx" docset="nw312" tidref="i3790"Memory PoolsNetware v3.12 manages RAM through the use of memory pools. These memory pools are designed to be allocated and optimized based on how they are used: either long-term or short-term.Rather than allocating chunks of memory at the time of installation, most resources (such as memory for communication buffers and drive mappings) are allocated as needed.Any values that must be preassigned are specified in the server's STARTUP.NCF and AUTOEXEC.NCF files.IDREF="FM77995"Table A-1 summarizes the memory pools and subpools created and maintained by NetWare v3.12.LBL="A-1" INLINE="F"ID="FM77995"idxid="w4038"book="_idx" docset="nw312" tidref="i3790"Memory pools and subpoolsWIDTH="132"Memory Pool or SubpoolWIDTH="168"Description and UseWIDTH="120"StatusWIDTH="132"idxid="w4039"book="_idx" docset="nw312" tidref="i2005"idxid="w4040"book="_idx" docset="nw312" tidref="i875"File Cache BufferWIDTH="168"Main memory pool; used for caching  reads and writes.WIDTH="120"Primary memory  segment.Cache MovableSubpool owned by NetWare; used  for internal system tables that  change size dynamically:Hash tablesFile allocation tables (FATs)Directory entry tables (DETs)No fragmentation. Expandable.Returnable to File Cache  Buffer in contiguous  blocks.Cache Non-MovableSubpool used by NLMs, including  CLIB, when loaded.Causes fragmentation. Non- expandable.Returnable to File Cache  Buffer in non-contiguous  blocks.idxid="w4041"book="_idx" docset="nw312" tidref="i5070"idxid="w4042"book="_idx" docset="nw312" tidref="i3758"Permanent MemoryOne-way allocation pool for long- term memory needs:Communication buffersDirectory cache buffersNot returnable to File  Cache Buffer.Semi-PermanentSubpool used by LAN and disk  drivers.Returnable to  Permanent Memory, but  not to File Cache Buffer.idxid="w4043"book="_idx" docset="nw312" tidref="i201"idxid="w4044"book="_idx" docset="nw312" tidref="i6339"idxid="w4045"book="_idx" docset="nw312" tidref="i3758"Allocated Short-term  MemoryPool used for small, short-term  allocations:Drive mappingsSAP and RIP tablesQueue manager tablesUser connection informationNot returnable to either  Permanent Memory or  to File Cache Buffer.Unused allocated  memory remains in the  pool for other uses.IDREF="FM93476"Figure A-1 illustrates the relationship of NetWare v3.12 idxid="w4046"book="_idx" docset="nw312" tidref="i3790"memory pools.LBL="A-1"ID="FM93476"Relationship of memory poolsFILE="n312i74a.pbm"Optimizing idxid="w4047"book="_idx" docset="nw312" tidref="i3758"Memory AllocationOnce memory resources are released from the File Cache Buffer pool to the Permanent Memory pool or to the Allocated Short-term Memory pool, they cannot be returned until after the server is brought down and the primary memory segment is re-established.Frequent loading and unloading of idxid="w4048"book="_idx" docset="nw312" tidref="i4310"NLMs causes fragmentation of your file server's memory.Although there may be plenty of total RAM to satisfy memory requests, there may not be enough contiguous RAM to actually service the requests.There are two ways to optimize your file server's memory allocation:Minimize loading and unloading of NLMs to prevent RAM fragmentation.If the RAM becomes fragmented, bring down the server and start it back up. This eliminates fragmentation and makes contiguous memory available to NLMs.idxid="w4049"book="_idx" docset="nw312" tidref="i1064"Communications SubsystemsThe following are communications subsystems that the NetWare installer or network supervisor can modify to tune the NetWare environment:Burst Mode technology. Technology that improves NetWare's performance when reading and writing large files over local and remote links.Packet size. The size of the frame or packet that a client and server communicate with.Communication buffers. The shared buffers available for incoming and outgoing packets, whose quantity will affect performance.SAP traffic filtering. Clients use SAP in their initial attachment to find the nearest server. Routers also use it to exchange server information.Network boards. The configuration flexibility of your network board, along with volume and makeup of the network traffic, could quickly cause saturation and create a bottleneck.idxid="w4050"book="_idx" docset="nw312" tidref="i863"Burst Mode TechnologyBurst Mode is a special-purpose service protocol designed to optimize large NetWare Core Protocol (NCP) reads and writes.NCP is a communication protocol that uses IPX as a transport and controls the dialogue between client and server.Burst Mode protocol allows a client to issue a single read or write request for blocks of data up to 64 KB. The data is partitioned into appropriate packets which are transmitted back-to-back.Burst Mode ComponentsTwo components necessary to implement Burst Mode are the idxid="w4051"book="_idx" docset="nw312" tidref="i5032"PBURST.NLM for the server and a new shell ( idxid="w4052"book="_idx" docset="nw312" tidref="i718"BNETX) for the client. The server component, PBURST.NLM, becomes part of the operating system and provides an extended set of NCPs which are supported by the new client shell.A number of Burst Mode buffers must be configured in the client's NET.CFG file to support the multi-packet reads and writes.These buffers are the size of the maximum frame size supported. More RAM is required at the client to adequately support Burst Mode communication.Burst Mode offers better performance in a variety of network environments. The following list names some environments that can benefit from Burst Mode:WANs with 9600-baud or slower asynchronous linksLocal network segments in which large files are read and written oftenInternetworks with multiple bridges and routersX.25 packet switching networksWANs with high-speed T1 and satellite linksidxid="w4053"book="_idx" docset="nw312" tidref="i4371"Server Default idxid="w4054"book="_idx" docset="nw312" tidref="i4890"Packet SizeThe default packet receive buffer size for a NetWare v3.12 server is 1 KB (1024 bytes).This is true even if the network board or LAN driver specified a packet size of 4 KB (as in token ring) and the hardware has been configured to handle 4KB packets.The 1KB default setting could cause large packets to slow the server. Increasing the packet size default allows the server to move more information at a time, increasing the speed with which large jobs are sent.Once the packet size default setting is increased, NetWare's Communication Buffers (also known as LSL Receive Buffers) increase in size automatically to accommodate the new default.Modification of the idxid="w4055"book="_idx" docset="nw312" tidref="i4890"packet size is achieved with a SET parameter in the STARTUP.NCF file:   SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE =Default: 1514Range: 618 to 4202The value for this parameter equals the size of the data portion plus the protocol overhead.When changing this parameter, be careful not to exceed the largest client packet size in use on the network.The network board manufacturer's driver specifies the maximum packet size it can handle.The default size for the NetWare DOS client shell is always 4 KB. However, the proposed packet size takes its reference point from the network board driver.The following is a list of default packet sizes that can be used if a driver-specific size is unknown.WIDTH="120"DriversWIDTH="192"Default packet sizeWIDTH="120"Token-Ring 4 MbpsWIDTH="192"2154 KBToken-Ring 16 Mbps4202 KBEthernet1130 KBArcnet618 KBidxid="w4056"book="_idx" docset="nw312" tidref="i4890"Packet Size through an Intermediate RouterWorkstations connected to a file server through a router are limited to sending packets of 512 bytes.To get around this limitation, use the Large Internet Packet support (LIP) NLM that is part of the Packet Burst technology.idxid="w4057"book="_idx" docset="nw312" tidref="i3161"Large Internet PacketThe idxid="w4058"book="_idx" docset="nw312" tidref="i3161"LIP Internet Packet eXchange (IPX) allows the client and server to negotiate the largest available packet size and then use that size for communication through an intermediate router.The server must contain PBURST.NLM. The workstation must contain the NETX.EXE v3.31 shell. Each is available in the NetWare v3.12 diskette set.In addition to requiring NETX.EXE, two parameters must be configured in idxid="w4059"book="_idx" docset="nw312" tidref="i3161"NET.CFG:  Large Internet Packets = 1 (on)  LI Frame Max = Default: 512Range: 512 to 16384Communication Buffersidxid="w4060"book="_idx" docset="nw312" tidref="i1064"Communication buffers are allocated dynamically, based on an aging algorithm in the OS.A minimum number of buffers can be preallocated when the server boots, and a maximum number specified to prevent an out-of-control growth situation.Communication Buffer SET ParametersThe network supervisor can control the increase in the number of communication buffers by using SET parameters in STARTUP.NCF and AUTOEXEC.NCF.You can use two SET parameters to preconfigure or preallocate the number of buffers based on use. The first is the SET Minimum Packet Receive Buffers parameter:  SET MINIMUM PACKET RECEIVE BUFFERS =Default: 10Range: 10 to 1000Using MONITOR, the network supervisor can compare the number of configured buffers to the number in use.The second SET parameter controls the maximum number of buffers that can ever be allocated:  SET MAXIMUM PACKET RECEIVE BUFFERS =Default: 100Range: 50 to 2000Occasional peaks in server use cause the number of buffers to grow significantly. This growth may need to be controlled because of impact on memory.A third SET parameter controls the amount of time the system waits before spawning a new buffer:  SET NEW PACKET RECEIVE BUFFER WAIT TIME =Default: 0.1 secondsRange: 0.1 to 20 secondsThis parameter complements the SET Maximum Packet Receive Buffers parameter and functions as a growth inhibitor. The most common use is on networks with occasional spikes of activity.The network supervisor needs to be conscientious in configuring these parameters. While they provide great flexibility, they can also have a negative impact on memory.The impact on overall system memory must be thoroughly understood, and the settings should be based on server performance over extended periods of time.idxid="w4061"book="_idx" docset="nw312" tidref="i6259"Service Advertising Protocol (SAP) TrafficIn NetWare, idxid="w4062"book="_idx" docset="nw312" tidref="i6258"SAP is used by file servers, print servers, gateways, etc. to advertise their services.Workstations use SAP in their initial attachment to find the nearest server. Routers also use it to exchange server information.A single SAP packet is broadcast for every seven servers on the network. SAP packets are broadcast every 60 seconds on local segments and over high speed links.Filtering SAP Traffic with NSARThe idxid="w4063"book="_idx" docset="nw312" tidref="i4203"idxid="w4064"book="_idx" docset="nw312" tidref="i4468"NetWare Service Advertising Restrictor ( idxid="w4065"book="_idx" docset="nw312" tidref="i4456"NSAR) is a set of NLMs that allows masking or filtering of SAP packets to minimize the amount of broadcast traffic on the network.These NLMs can be used as a route designator and to determine which servers are visible.The main module, RESTRICT.NLM, lets the network supervisor review the services to be advertised and can then restrict certain entries from being made available on certain segments.Network Board IssuesThe configuration flexibility of your idxid="w4066"book="_idx" docset="nw312" tidref="i4494"network board, along with volume and makeup of the network traffic, can quickly cause saturation and create a bottleneck.NetWare's idxid="w4067"book="_idx" docset="nw312" tidref="i3956"idxid="w4068"book="_idx" docset="nw312" tidref="i7237"MONITOR utility provides two sets of statistics for every network board in the server.The first set consists of general error entries.All driver manufacturers are instructed to maintain information on 15 different statistics.These include statistics such as total packets sent and received, packets dropped due to no available communication buffers, etc.The second set consists of custom statistics. There are 15 to 20 additional statistics that vendors can provide.One particularly helpful custom statistic for the Ethernet NE2000 card is "Enqueued Sends Count."This indicates the number of packets that the network board had to buffer because the driver was too busy to send the packet that the processor had ready.If this count increments regularly and reaches one to two percent of the total packets transmitted, the network board driver is having trouble keeping up with the server and is reaching or has reached its saturation point.If the network board is an 8-bit or 16-bit card, you may need to replace it with a 32-bit card.File System and CacheOptimizing the NetWare caching mechanism includes adjusting parameters that affect NCP reads and writes, block and buffer size, FATs, and directory entry tables. This section covers the following file system and cache subsystem areas:File cache buffers. Increasing the amount of cache optimizes the file system.Cache buffer and volume block size. Modifying the cache block size adds efficiency to the file server by increasing response time between server and client.Turbo FAT indexing. Increasing the Turbo FAT re-use wait time ensures that Turbo FAT index structures are not flushed if the file is reused quickly.Directory entry table caching and name space considerations. Adding name spaces at volume creation, and using separate volumes to divide files that require name spaces, can help optimize NetWare file system performance.Additional SET parameters for file system and cache. Additional SET parameters can optimize the file system and cache.Disk drivers and controllers. Using an intelligent controller provides support for scattering to help optimize disk I/O in a large network configuration.idxid="w4069"book="_idx" docset="nw312" tidref="i2005"File Cache BuffersThe amount of total server memory being used as cache buffers should never fall below 20 percent.A good rule of thumb is that the File Cache Buffers pool should be at least 40 to 60 percent of the total server work memory. However, the higher this percentage, the better.Additional memory not only benefits cache, but also adds to the memory available for the other pools that allocate from the main File Cache Buffer pool.idxid="w4070"book="_idx" docset="nw312" tidref="i875"Cache Buffer Size and idxid="w4071"book="_idx" docset="nw312" tidref="i7340"Volume Block SizeModifying the cache block size in memory and the block size on the physical disk adds efficiency to the file server by increasing response time between server and client.Cache buffer size is determined at server startup time by the following SET parameter:  SET CACHE BUFFER SIZE =Default: 4096Range: 4096, 8192, 16384Volume block size is set for each volume when the volume is created. The default is 4 KB (4096 bytes).The system is optimized when cache block size and volume block size are the same.However, this is not always possible when you have multiple volumes on the server and they aren't all configured to use the same block size.NetWare requires that the cache buffer size be the same as the smallest volume block size.For optimal performance, Novell recommends that cache buffer size and volume block size be configured to 8 KB when using NetWare NFS.idxid="w4072"book="_idx" docset="nw312" tidref="i7053"Turbo FAT IndexingThe idxid="w4073"book="_idx" docset="nw312" tidref="i1990"File Allocation Table (FAT) indexes one or more disk allocation blocks in which a file is located.The entire idxid="w4074"book="_idx" docset="nw312" tidref="i1989"FAT is cached in server memory, allowing the server to quickly access disk allocation blocks of data volume.When a file exceeds 64 blocks, NetWare creates a Turbo FAT index that groups all FAT entries corresponding to the file.When a file accessed through a Turbo FAT index is closed, the Turbo FAT index is not immediately flushed from memory. Rather, an aging process begins.An existing index is only flushed and re-used when there is an allocation from the Permanent Memory pool and the aging timer has exceeded its default time of 5 minutes and 29.6 seconds.This time can be altered through the following SET parameter:  SET TURBO FAT RE-USE WAIT TIME =Default: 5 minutes 29.6 secondsRange: 0.3 sec. to 1 hour, 5 minutes, 54.6 secondsIncreasing the Turbo FAT re-use wait time helps ensure that the index structures are not flushed if the file is reused quickly.idxid="w4075"book="_idx" docset="nw312" tidref="i1491"Directory Cache Buffers and idxid="w4076"book="_idx" docset="nw312" tidref="i3992"Name Space ConsiderationsName spaces allow the NetWare file system to support the files and file characteristics of diverse desktop operating systems such as NFS, AppleTalk, HPFS, and FTAM.Name space support has an impact on the speed and efficiency with which a directory is searched and a file is accessed.For each name space loaded, NetWare creates a separate set of directory entries and appends them to the existing directory entry blocks.In this environment, the DOS name is the ultimate reference. When a user searches for a non-DOS file, both the name space directory entry and the DOS directory entry are cached every time.Adding Name Space at Volume CreationWhen name space support is added at volume creation, the system creates the DOS directory entry followed immediately by the name space directory entry.This virtually guarantees that both entries are in the same directory entry block. When searching for a particular file from a non-DOS client, the file system most probably will only have to cache one block.The main benefit of adding name space support at volume creation is that it speeds up certain operations, such as directory searches from non-DOS clients and file modifications and deletes.Using Volumes to Divide Name Space UseAssigning name space support by volumes can also be used to divide name space allocation. This allows the name space and volume to be used more efficiently.Additional idxid="w4077"book="_idx" docset="nw312" tidref="i6285"idxid="w4078"book="_idx" docset="nw312" tidref="i7237"SET Parameters for File System and CacheAdditional SET parameters can optimize the file system and cache.Dirty Cache Delay TimeA Dirty Cache Block contains updated information that has not yet been written to disk.These blocks are flushed to disk when either the client write operation fills a cache block completely, or after the Aged Write default setting has expired.NetWare v3.12 has a SET parameter that allows the network supervisor to optimize and fine-tune the frequency with which Aged Block Writes occur.  SET DIRTY CACHE DELAY TIME =Default: 3.3 secondsRange: 0.1 to 10 secondsIncreasing the aging parameter to ten seconds allows the system to store up many write operations before going to disk and results in less frequent disk I/O.Maximum Concurrent Disk Cache WritesWhen Dirty Cache Blocks are ready to be written to disk, a system parameter determines how many write requests are put to the elevator for the actual disk I/O.This parameter is configurable to help fine-tune the system to optimize in either a read-intensive or write-intensive environment.  SET MAXIMUM CONCURRENT DISK CACHE WRITES =Default: 50Range: 10 to 100In a write-intensive environment, increasing this value improves write performance. Conversely, reducing this value improves the performance of the read operations.Immediate Purge of idxid="w4079"book="_idx" docset="nw312" tidref="i1351"idxid="w4080"book="_idx" docset="nw312" tidref="i2300"Deleted FilesThis file system SET parameter configures how file deletions are handled by the system:  SET IMMEDIATE PURGE OF DELETED FILES = ON/OFFDefault: OFFThe default setting of OFF allows the file system to maintain deleted files on the disk to be purged as necessary.However, the system must perform additional disk operations to keep the file in the salvage file list.Changing this parameter to ON decreases the number of operations the system must perform, increasing response time. It also eliminates salvage capability for users.Files that have been deleted but not purged are not cached as directory entries and do not impact the allocations on the Cache Movable subpool.Military, government, and other security-conscious agencies usually turn this parameter on.Disk Read-After-Write VerifyThis SET parameter allows you to turn off NetWare's read-after-write verification capability.  SET ENABLE DISK READ AFTER WRITE VERIFY =Default: ONThis capability complements Hot Fix.The default setting of ON allows the system to prevent a file from being written to a bad disk block by attempting to read the data after it has been written to disk.If a problem is encountered, Hot Fix is invoked, the data is redirected to a good area of the disk, and the original blocks are flagged as bad. For some controllers (such as those used with Compaq disk arrays), the Hot Fix verification is perceived as redundant and the hardware turns the read-after-write and Hot Fix functionality off.Some SCSI controllers implement read-after-write verification, providing a second and redundant level of error checking.In a disk I/O-intensive environment, eliminating the redundant layer of verification can increase performance.If the hardware encounters a problem, NetWare's Hot Fix is invoked as usual to redirect the data.Changing the setting after the driver is loaded can have unpredictable results. It is better to control the disk drivers individually through MONITOR's "book="sysadmin" docset="nw312"Read After Write Verify" option as explained in System Administration. Consult the disk/controller manufacturer before turning off the read-after-write feature.Fixed Disk idxid="w4081"book="_idx" docset="nw312" tidref="i1409"idxid="w4082"book="_idx" docset="nw312" tidref="i1561"Device Drivers and idxid="w4083"book="_idx" docset="nw312" tidref="i1549"ControllersNetWare supports the use of different idxid="w4084"book="_idx" docset="nw312" tidref="i1549"disk controllers and disk drives including intelligent controllers such as a SCSI device or a Disk Coprocessor Board.An intelligent controller provides support for scattering (multiple simultaneous requests to different drives connected to the same controller).When multiple disks are chained together, the controller can initiate a write to one disk and, without waiting for a completion code, service another disk, and then come back to where it left off with the first request.This helps optimize disk I/O in a large network configuration.idxid="w4085"book="_idx" docset="nw312" tidref="i6647"idxid="w4086"book="_idx" docset="nw312" tidref="i5588"System ProcessorHigh server CPU use does not always mean the server lacks system processor power. Many resources, including NLMs and NICs, contend for CPU time.Replacing the server with a new 486 machine may not yield the expected performance gains.Typically, other server subsystems must be optimized before the system processor emerges as the bottleneck.Starting MONITOR with the "-p" flag displays a CPU utilization option. This option provides a list of processes and interrupts that identify inefficient or CPU-intensive resources in the server.One area of focus is server hardware, which is always tied to an interrupt. How often that interrupt is triggered is an indication of which hardware device is being accessed most frequently.Managing the server from a hardware perspective involves finding ways to steal CPU cycles.For example, using 32-bit disk controller technology optimizes read and write operations. One 32-bit read request is more efficient than four 8-bit reads since the CPU is interrupted only once instead of four times.In a sense, Bus Master is the ultimate in terms of stealing CPU cycles. Hardware using this technology can move data in and out of system memory and on to the card without interrupting the CPU. However, keep in mind that while the Bus Master card has control of the bus, the CPU can't use it.LBL="A-2" INLINE="F"idxid="w4087"book="_idx" docset="nw312" tidref="i4371"idxid="w4088"book="_idx" docset="nw312" tidref="i5066"Summary TableWIDTH="108"ComponentsWIDTH="312"Suggestions for OptimizationMemory  ManagementMinimize loading and unloading of NLMs to prevent RAM fragmentation.If the RAM becomes fragmented, bring down the server and start it back  up. This eliminates fragmentation and makes the contiguous memory  available to NLMs.Communications  SubsystemsUse Burst Mode protocol when it will help.Increase the packet size default for servers that are not connected  through an intermediate router through the STARTUP.NCF file.Use the LIP.NLM to increase the packet size when packets crossthrough an intermediate router.Pre-allocate communication buffers according to peak use over time.SET MINIMUM PACKET RECEIVE BUFFERSSET MAXIMUM PACKET RECEIVE BUFFERSSET NEW PACKET RECEIVE BUFFER WAIT TIMEUse NSAR to minimize the amount of broadcast traffic on the  network.Monitor network board statistics:    General errors (retries)    Enqueued Sends CountFile System and  CacheFile Cache Buffer Pool should be greater than 20 percent of total  server work memory. The higher this percentage, the better (40 to  60% recommended).Volume block size should match cache buffer size whenever possible.  Volume block size is set at volume creation.    SET CACHE BUFFER SIZE in SERVER.CFG file.    Configure cache buffer and volume block size to 8 KB when using      NetWare NFS.    For multiple-disk volumes, cache buffer size must be smaller than    volume block size.Turbo FATs speed access to large, randomly accessed files.    SET TURBO FAT REUSE WAIT TIMEName space recommendations:    Add name space at volume creation.    Separate homogeneous volumes from mixed volumes.SET Parameters:    SET DIRTY CACHE DELAY TIME    Increase to boost server efficiency.    SET MAXIMUM CONCURRENT DISK CACHE WRITES    In write-intensive environment, set greater than default.    In read-intensive environment, set less than default.    SET IMMEDIATE PURGE OF DELETED FILES    Turn ON for better performance (lose salvage capability).    SET ENABLE DISK READ AFTER WRITE VERIFY.    Follow disk/controller manufacturer's recommendations.Use an intelligent controller for multiple disks chained together.System ProcessorFind ways to "steal "CPU cycles:32-bit technologyEISA, Micro channel busBus Master technologyLBL="B"ID="FM87545"Installing and Using Novell ElectroText Introduction to Novell idxid="w4089"book="_idx" docset="nw312" tidref="i4676"ElectroTextidxid="w4090"book="_idx" docset="nw312" tidref="i4676"The idxid="w4091"book="_idx" docset="nw312" tidref="i4676"Novell ElectroText viewer allows you to read NetWare idxid="w4092"book="_idx" docset="nw312" tidref="i4676"manuals from your Windows or OS/2 idxid="w4093"book="_idx" docset="nw312" tidref="i4676"workstation.All NetWare v3.12 manuals except the Quick Access Guide are available through Novell ElectroText:Server BackupBtrieve Installation and OperationConceptsInstallationNetWare Management Agent for NetViewPrint ServerSystem AdministrationSystem MessagesNetWare TCP/IP Supervisor's ManualWorkstation Basics and InstallationUtilities ReferenceWorkstation for DOS and WindowsWorkstation for OS/2NetWare for Macintosh Installation and MaintenanceNetWare Client for MacintoshThis chapter documents the installation and use of Novell ElectroText only on Windows and OS/2 platforms. For instructions on using Novell ElectroText on Macintosh or UNIX, see your Macintosh or UNIX manual.Installing Novell ElectroTextYou can install Novell ElectroText on a NetWare server or local hard disk. You must set up a Windows or OS/2 workstation to view Novell ElectroText. After you install Novell ElectroText, you can customize the library. See "book="sysadmin" docset="nw312"Creating Custom Libraries and Bookshelves" in System Administration. If you do not have the complete set of printed NetWare v3.12 documentation, and therefore do not have the procedures for installing NetWare workstations, install Novell ElectroText on a computer that is not attached to the network.Then use Novell ElectroText to read the procedures for setting up computers as NetWare workstations.ID="FM96071"Prerequisitesidxid="w4094"book="_idx" docset="nw312" tidref="i4676"The computer on which Novell ElectroText is installed (the NetWare server, workstation with local hard disk, or standalone computer) must have the following:A minimum of 30 MB of hard disk space free for program, book, and temporary files. (If Novell ElectroText is read directly from CD-ROM, only 1 MB of disk space is necessary.)A CD-ROM drive that can read ISO 9660 formatted CD-ROM disks. (This is not necessary if you install Novell ElectroText from floppy diskettes.)The computer on which Novell ElectroText is viewed (the network workstation or standalone computer) must have the following:Hercules monochrome, EGA, VGA, or Super VGA display card and monitor.A minimum of 4MB of RAM.Microsoft Windows 3.x or OS/2 2.x.(Optional) A printer for printing sections of the electronic text.If Novell ElectroText is installed and viewed on a standalone computer or a workstation, all of the above sets of requirements apply to the same computer.If Novell ElectroText is installed on a NetWare server and viewed on a workstation attached to that server, the first set of requirements applies to the server and the second set to the workstation. InstallationNovell ElectroText files can be installed on a NetWare server, a local hard disk, or they can be accessed directly from the CD-ROM disk. Installing on a NetWare ServerThis procedure involves copying the Novell ElectroText files from the NetWare v3.12 CD-ROM to your server's hard disk.ProcedureInstall the CD-ROM drive, cables, and drivers according to the manufacturer's instructions.Load the INSTALL utility.At the console prompt, type LOAD INSTALL <Enter>The "Installation Options" menu appears.LBL="B-1"Installation Options menuFILE="n312i128.pbm"Select "Product Options."The "Currently Installed Products" screen appears.LBL="B-2"Currently Installed Products screenFILE="n312i129.pbm"Press <Ins> to install the Novell ElectroText files.You are prompted for the location of the ElectroText files.LBL="B-3"Enter the drive and pathFILE="n312i130.pbm"Enter the drive letter and path by typing CD-ROM drive letter>\DOCPress <Enter> to begin copying.A message will appear indicating when all of the files have been copied.Press <Esc> to continue.The following screen appears, displaying the installed files.LBL="B-4"Currently Installed Products screen with the installed ElectroText filesFILE="n312i131.pbm"Press <Esc> to return to the "Installation Options" menu.Press <Esc> to exit INSTALL.Installing on a Local Hard Diskidxid="w4095"book="_idx" docset="nw312" tidref="i4676"Instead of installing Novell ElectroText on a server, you can install it to run on a standalone computer or from a workstation's hard disk.When you do this, Novell ElectroText is available only from that computer or workstation, and is not available to other workstations on the network.To install Novell ElectroText on a workstation's hard disk, complete the following steps.ProcedureInstall the CD-ROM drive, cables, and drivers according to the manufacturer's instructions.Copy the \PUBLIC directory structure from the CD-ROM to your local disk. For example, if D: is your CD-ROM drive and C: is your local hard disk drive, type XCOPY D:\PUBLIC C:\ /S <Enter>Copy the \DOC directory structure from the CD-ROM to your local disk. For example, if D: is your CD-ROM drive and C: is your local hard disk drive, type  XCOPY D:\DOC C:\ /S <Enter>Now set up a workstation for viewing as explained in IDREF="FM96951""Setting Up a Windows or OS/2 Workstation for Viewing" on page 340.Running from CD-ROMidxid="w4096"book="_idx" docset="nw312" tidref="i930"You can idxid="w4097"book="_idx" docset="nw312" tidref="i4676"run Novell ElectroText directly from the CD-ROM disk. Instead of copying the Novell ElectroText files to a hard disk, use the drive letter for the CD-ROM drive when setting up the workstation files as specified in IDREF="FM96951""Setting Up a Windows or OS/2 Workstation for Viewing" below.ID="FM96951"Setting Up a Windows or OS/2 Workstation for Viewingidxid="w4098"book="_idx" docset="nw312" tidref="i4676"Whether idxid="w4099"book="_idx" docset="nw312" tidref="i4676"you run Novell ElectroText from a server or from a workstation's local hard disk, you must set up one or more workstations for viewing. Novell ElectroText is a Windows application; to run it on an OS/2 workstation you must open a DOS session under OS/2 and then start Windows. All other setup and operating instructions are the same.ProcedureCopy the ET.INI file from the CD-ROM's \DOC\DATA\CONFIG directory to the WINDOWS directory on the workstation's hard disk.For example, if D: is your CD-ROM drive and C: is your local hard disk drive, type  COPY D:\DOC\DATA\CONFIG\ET.INI C:\WINDOWS <Enter>Edit your copy of the ET.INI file.Set the paths for ET files.The first three sections of the file contain directory paths that specify where various ET files are located.The ET.INI file as installed will probably be incorrect because your drive mappings will be different.Edit the file so that the drive letter or directory path points to the location of the DOC directory and its subdirectories.For example, if the DOC directory is installed at the root of volume SYS:, as we recommend, either map a drive to SYS: and specify that drive letter, or specify the SYS:DOC directory path. (Optional) Set the display type. If you are using an LCD display, enter the line "DISPLAY=WLCDVGA" under the [PREFERENCES] section of the file.If you are using any other type of display, Novell ElectroText determines the display type.Add the following line in your AUTOEXEC.BAT file: set nwlanguage=languageFor language, substitute the name of the language for the book text. For example, English, Deutsch, Español, Français, etc. This variable specifies which set of electronic books will be viewed. The name must match one of the subdirectories under the \DOC directory. Reboot the workstation so that the language setting will take effect, or enter the setting on the command line. If you set up Novell ElectroText to run under Windows 3.0 (not 3.1) copy the DDEML.DLL file from a Windows 3.1 WINDOWS\SYSTEM directory into the directory where the ET.EXE file is located, usually \PUBLIC. Start Windows.Create a program icon for Novell ElectroText. Make sure the program group you want to place the icon in is active and then choose "New" from the "File" menu in Windows.Specify "Program Item" and select "OK."Enter "Novell ElectroText" for the description of the icon, type "ET.EXE" in the "Command Line," and type the drive letter and path for the \PUBLIC directory where ET.EXE is located in the "Working Directory" field. Select "OK."Novell ElectroText is now ready to run from your Windows or OS/2 workstation. Continue with the next section, IDREF="FM61447""Starting Novell ElectroText."ID="FM61447"Starting Novell ElectroTextidxid="w4100"book="_idx" docset="nw312" tidref="i4676"After Novell ElectroText is installed, you can access it from a workstation running Windows or OS/2. To run Novell ElectroText, complete the following steps.ProcedureStart Windows.Choose the "Novell ElectroText" icon on your Windows desktop. Icons for the available bookshelves appear. Choose the icon for the bookshelf containing the book you want to view.Icons for the books in the bookshelf appear. Choose the icon for the book you want to view.The text and the Table of Contents outline for the book you specified appear. Using Novell ElectroTextAfter starting Novell ElectroText and selecting a book to view, you can do the following to idxid="w4101"book="_idx" docset="nw312" tidref="i4676"navigate through the book.WIDTH="120"ToWIDTH="180"ThenWIDTH="120"Move directly to a specific  section of the book.WIDTH="180"Choose the section title in the outline  window.Scroll through the book's  text.Use the scroll bar on the right side of the  text window.View a graphic or table.Choose the icon representing the graphic  or table.Move to another section  that is referenced in the  text.Choose the underlined or colored text;  the display moves to the referenced  section. If the referenced section is in a different  book, a new window opens displaying the  other book.Locate a specific word or  phrase in the book.Use the "Search" field by typing a word or  phrase to search for, and then choosing  "Next."Occurrences of that word or phrase are  highlighted. Choose "Next" to jump to  the next occurrence. The number of occurrences in each  section of the book is listed in the outline  window.Choose a section title to jump to the first  occurrence of the word or phrase in that  section.For more on Novell ElectroText, see Chapter 4, "book="sysadmin" docset="nw312"Using Novell ElectroText," in System Administration.Novell ElectroText also has online help available; select the "Help" option from the menu bar.LBL="C"WorksheetsID="FM66968"ID="FM66968"This section contains worksheets for the following:File server installationWorkstation installationPlanning directoriesPlanning usersPlanning groupsPlanning user defaultsPlanning trustee directory rightsPlanning trustee file rightsLBL="3-1"File server installation worksheetFILE="n312i85a.pbm"LBL="3-2"Workstation Configuration worksheetFILE="n312i86a.pbm"LBL="3-3"Directories worksheetFILE="n312i87a.pbm"LBL="3-4"User worksheetFILE="n312i88a.pbm"LBL="3-5"Group WorksheetFILE="n312i89a.pbm"LBL="3-6"User defaultsFILE="n312i90a.pbm"LBL="3-7"Trustee file security worksheetFILE="n312i91a.pbm"LBL="3-8"Trustee directory security worksheetFILE="n312i92a.pbm"