Install your NetWare v3.12 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.).
You 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.
Make working copies of all NetWare v3.12 diskettes.
For instructions, see Make Working Copies of the NetWare Diskettes.
Determine the method you will use to boot your file server by reading Determine File Server Boot Method.
Based on your decision in Step 2, follow the procedures under Install Server Software for Use with a DOS Boot Diskette, or continue with Step 1 under Installing from Floppy Diskettes on Installing from Floppy Diskette.
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 SYSTEM and PUBLIC files.
Install the CD-ROM drivers according to the 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. Change to the drive letter corresponding to the CD-ROM, then change to the NETWARE.312/ENGLISH directory and type INSTALL <Enter> Continue with Step 1 under Installing from CD-ROM. NOTE: You can install from a network directory only if you already have a NetWare server (of any version) installed on your network.
Create a NETWARE directory on an existing network server and copy the files from the installation media to that directory. For example, if you are copying from CD-ROM drive E: to network drive K:, you might type K:MD NETWARECD NETWAREXCOPY E: /S /E NOTE: This copies not only the NetWare files, but also the Novell ElectroText online documentation. If you copy the entire CD, you will need approximately 100MB of free disk space.
Or, if you are copying from floppy diskettes, make subdirectories for the Install, Unicode, and System_x diskettes. You might type K:MD NETWARE.312CD NETWARE.312MD INSTALLMD UNICODEMD SYSTEM_1...MD SYSTEM_8 Then, for each subdirectory you created, change to the subdirectory and copy all files and subdirectories from the floppy diskette. You might type CD INSTALLXCOPY A: /S /ECD.. Then repeat the three commands above, substituting the Unicode diskette and all the System_x diskettes for the Install diskette. On every computer you want to make a NetWare v3.12 server, create a DOS partition of at least 5 MB. Install NetWare DOS workstation software on each prospective server. For instructions on installing workstation software, refer to the installation instructions in Workstation for DOS and Windows. 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. HINT: For ease of use in specifying the path, use a MAP ROOT command.
If you copied from CD-ROM in Step 1, change to the NETWARE.312\ENGLISH directory. If you copied from diskette, change to the INSTALL directory and type INSTALL <Enter> Continue with Step 1 under Installing from CD-ROM. If you install from diskette, before you install the 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. NOTE: If you install from CD-ROM or from a network directory, you must have a DOS partition on your server's hard drive.
Use File server boot options to determine which method.
Procedure
Installing from Network Directory
Procedure
Determine File Server Boot Method
Table 4. File server boot options
| Boot option | Advantages | Disadvantages |
|---|---|---|
Boot DOS from a diskette |
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. |
Booting from diskette is significantly slower. |
Boot DOS from a partition on the hard disk |
After 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. |
IMPORTANT: Machines that do not have an 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, continue with Install Server Software for Use with a DOS Boot Diskette or go to Install Server Software for Use with a DOS Partition on the Hard Disk.
NOTE: 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 File server boot options.
On a computer other than the server, create a directory for temporary storage of the server boot files. Copy the following files from the System_1 diskette to the directory you created in Step 1.
Create the server boot diskette. Copy the NWSNUT.NLM from the System_8 diskette to the designated directory. Place the Install diskette in drive A: and type A:NWXTRACT A: NWSNUT.NLM [path] <Enter> Replace [path] with the path to the directory you created in Step 1. You are prompted with the following message: Leave the Install diskette in drive A: and press <Enter>. You are then prompted to insert the System_8 diskette (which contains NWSNUT) into drive A: to uncompress NWSNUT.NLM. Copy the disk driver for your system from the System_1 (for Novell drivers) or System_2 (for third party drivers) diskettes to the designated directory. To determine which disk driver, use Disk driver determination. (Optional) Copy the files in Optional boot diskette files that apply.
LAN_driver You want a copy in case your LAN driver located on volume SYS: becomes corrupted. VREPAIR You want a utility for repairing volume SYS: or you added name spaces to volumes and want a way for VREPAIR to repair those volumes. Name space support You added name spaces to volumes. (Conditional) Create an AUTOEXEC.BAT file in the designated directory that includes the following command: SERVER Use this command if you want the server to load automatically when the computer reboots. For information on creating an AUTOEXEC.BAT file, see your DOS manual. NOTE: 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 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=HIGH
Format a high-capacity diskette for the server's A: drive with the /s parameter. Copy the files from the designated directory to the new bootable diskette. Place the new server boot diskette in the server's A: drive. Reboot the server. To determine whether to boot from a boot diskette or from a DOS partition, see File server boot options. Insert the Install diskette in drive A: and reboot your computer, or change to drive A: and type INSTALL <Enter> From the "Select an Installation Option" menu, select "Install new NetWare v3.12." Determine your DOS disk partition requirements. If you already have an adequate DOS partition, select "Retain Current Disk Partitions" and skip to Step 1. To create a new DOS partition, continue with Step 3a. 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 Install Server Software for Use with a DOS Boot Diskette. Your bootable DOS partition must have at least 2 MB of free (usable) space, though we recommend that you allocate a minimum of 5 MB. Select "Create a new DOS partition or retain DOS partition." If you select the option to retain a DOS partition, skip to Step 1. WARNING: 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. NOTE: 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. 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:. NOTE: Some revisions of NetWare v3.12 prompt you for a non-existent NetWare-1 diskette. If prompted, insert the Install diskette instead.
Restart INSTALL by typing INSTALL <Enter> 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: NOTE: 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. Continue the installation by following the procedures under Name Your Server and Copy Boot Files. From the "Select an Installation Option" menu, select "Install new NetWare v3.12." Determine your DOS disk partition requirements. If you already have an adequate DOS partition, select "Retain Current Disk Partitions" and follow the procedures under Name Your Server and Copy Boot Files. Your bootable DOS partition must have at least 2 MB of free (usable) space, though we recommend that you allocate a minimum of 5 MB. From the "Disk Partition Options" menu, select "Create a new DOS partition." WARNING: 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. NOTE: 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. Make sure that the SYSTEM_1 diskette is in drive A: prior to rebooting your system. WARNING: All data is destroyed on an existing DOS partition. This could include the driver used to access the CD-ROM.
Reboot the computer. Format the new DOS partition. At the A: prompt, type DOSTOOLS\FORMAT C: /X/S <Enter> NOTE: The /X option is a DR DOS option that indicates you are formatting a hard disk.
To access the CD-ROM drive, reinstall the CD-ROM drivers on the DOS partition. Install the CD-ROM device drivers according to the CD-ROM manufacturer's instructions. Reboot the computer after installing the CD-ROM drivers. To restart INSTALL, change to the NETWARE.312\ENGLISH directory and type INSTALL <Enter> Select "Retain Current Disk Partitions" and follow the procedures under Name Your Server and Copy Boot Files. From the "Select an Installation Option" menu, select "Install new NetWare v3.12." Determine your DOS disk partition requirements. If you already have an adequate DOS partition, select "Retain Current Disk Partitions" and follow the procedures under Name Your Server and Copy Boot Files. Your bootable DOS partition must have at least 2 MB of free (usable) space, though we recommend that you allocate a minimum of 5 MB. From the "Disk Partition Options" menu, select "Create a new DOS partition." WARNING: 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. NOTE: 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. Make sure that the System_1 diskette is in drive A: prior to rebooting your system. WARNING: All data is destroyed on an existing DOS partition. This could include the client software.
After the system reboots, format the new DOS partition. At the A: prompt, type DOSTOOLS\FORMAT C: /X/S <Enter> NOTE: The /X option is a DR DOS option that indicates you are formatting a hard disk.
To access the server containing your NetWare v3.12 directory, reinstall the client files on the DOS partition. Reboot the computer after installing the client files. Log in to the server and change to the directory where you copied your NetWare 3.12 files in Step 1. To restart INSTALL, type INSTALL <Enter> You must reboot your server so that DOS recognizes the new partition. Pressing any key automatically reboots the server. Be sure the System_1 diskette is in drive A:. NOTE: Some revisions of NetWare v3.12 prompt you for a non-existent NetWare-1 diskette. If prompted, insert the Install diskette instead.
Select "Retain Current Disk Partitions" and follow the procedures under Name Your Server and Copy Boot Files. Name the file server. Give the file server a unique name using these guidelines:
Assign an IPX internal network number. An internal network 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 be
NOTE: You can't assign an IPX internal network number of "0" or "FFFFFFFF."
For more on internal network numbers, see "IPX internal network number" in Concepts.
Accept the default number. 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>. (Conditional) If you are installing NetWare for use with a DOS boot diskette, go to Load Disk Driver Loadable Modules. Press <Enter> to copy the server boot files to the hard disk. Server boot files are copied from the System_1 or System_2 diskettes or from the CD-ROM 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 and name spaces. Accept or change the default source path.
Copy the files from drive A:. Continue with Step 4.c. Copy the files from a source other than the default. Press <F2>. Type the complete drive and path. Press <Enter>.
Copy the files to the default destination directory created for you (SERVER.312). Continue with Step 4.c. 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. Press <Enter> to begin copying. (Conditional) During the copy process, insert the NetWare diskettes when prompted into the source drive and press <Enter>. A bar graph indicates the status of the copy process: Figure 1
Once all files are copied, the language screen appears: Figure 2 Enter your Country Code, Code Page, and Keyboard Mapping setting and press <F10>. NOTE: For a list of settings for each field, highlight a field and press <Enter>, or refer to your DOS manual.
The following screen appears. Figure 3
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" causes all files created from this point on to conform to DOS filename conventions. NOTE: If you upgrade from a previous version of NetWare to NetWare v3.12, and you have files that do not conform to DOS filename format conventions, you must run VREPAIR.NLM before you can mount any volumes. VREPAIR renames invalid DOS filenames to valid DOS filenames.
If you select "DOS Filename Format," and no changes were made in the "Language Configuration" screen, 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. NOTE: 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. INSTALL prompts you to add SERVER.EXE to your AUTOEXEC.BAT file. SERVER.EXE contains the NetWare v3.12 operating system.
Yes 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) No The DOS prompt appears whenever you reboot the file server and you must type "SERVER" to load NetWare. (Optional) Use the REGISTER MEMORY command to add additional memory. If your file server is incapable of addressing memory over 16 MB, 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> For more information, see "Register Memory" in Utilities Reference. Continue with Load Disk Driver Loadable Modules. 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. Load 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 Disk driver determination. For example, if you have an AT-type controller board, type LOAD ISADISK <Enter> NOTE: If you load the 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.
Procedure
Place a master data file diskette in drive A: and press Enter, or Esc to Exit.
Table 5. Optional boot diskette files
Copy
If
Install Server Software for Use with a DOS Partition on the Hard Disk
Installing from Floppy Diskette
Procedure
WARNING All existing data on non-removable disk C: will be destroyed!-Continue (Y/N)?Installing from CD-ROM
Procedure
Installing from a Network Directory
Procedure
Name Your Server and Copy Boot Files
To
Do this
To
Do this
To
Do this
Copy process bar graph
Language Configuration Screen
Select a filename format
If you choose
This happens
Load Disk Driver Loadable Modules
Procedure
Table 6. Disk driver determination
| Type of Architecture | Controller Type | Add-On Board | Disk Driver |
|---|---|---|---|
Industry Standard Architecture (ISA) |
AT, MFM, RLL, ARLL |
Built in |
ISADISK |
|
|
Third-party secondary adapter |
ISADISK |
|
ESDI |
|
ISADISK /B |
|
IDE |
|
IDE |
|
Novell SCSI |
DCB |
DCB |
Microchannel |
ESDI |
Built in |
PS2ESDI |
|
MFM |
Built in |
PS2MFM |
|
IBM SCSI |
IBM SCSI |
PS2OPT |
|
|
Built in |
PS2OPT |
Extended Industry Standard Architecture (EISA) |
AT class |
Built in |
ISADISK |
|
|
See vendor |
ISADISK |
|
EISA vendor proprietary |
Built in |
See vendor |
|
|
See vendor |
See vendor |
IMPORTANT: If you install more than one 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.
IMPORTANT: If you do not follow the correct order, system messages about your hard disks will be incorrect. For more information, see "Device Numbering" in Concepts.
(Conditional) On ISA and IDE file servers, answer the prompt for the I/O port address and interrupt number.
(Conditional) 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 Run DISKSET (Optional). If you do not need to run DISKSET, go to Create NetWare Disk Partition Tables.
Use DISKSET only with ADIC/Novell DCB disk drivers or with a third-party driver if the manufacturer requires you to use DISKSET.
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.
To run DISKSET, type
DISKSET <Enter>
Select "Disk Coprocessor Board Setup" from the "Diskset Options" menu.
Select the disk driver and settings that match external hard disk 0 (physical device 0 attached to the controller) on the "Select Desired Driver" list:
Figure 4
Select Desired Driver
On the "EEPROM Config" screen, highlight the text "***>>-none" under the "Device 0" heading next to the appropriate controller address: Figure 5
Press <Ins>. Scroll through the "Select Disks and Controller Type" list and select the name of the hard disk you are setting up: Figure 6
NOTE: 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: Figure 7
(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: Figure 8
Save the information by pressing <Esc> and answering "Yes" at the prompt. To configure the remaining hard disks for your file server, repeat Step 4 through Step 9. For more information, see "DISKSET" in System Administration. Continue with Create NetWare Disk Partition Tables.
EEPROM Config Screen
Select Disks and Controller Type
EEPROM Screen
EEPROM Screen
Once the disk drivers have been loaded, use 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.
Hard disk partitions illustrates hard disk partitions:
Figure 9
Hard disk partitions
Load INSTALL by typing LOAD path INSTALL <Enter> Replace path with the directory path to INSTALL.NLM. For example: LOAD C: INSTALL <Enter> This loads the INSTALL.NLM from the server boot directory. 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 "Delete Partition" from the "Partition Options" menu. WARNING: Deleting a partition deletes all data. To delete existing partitions, (don't delete the DOS partition you created in Step 3 on page 25) make sure you have a backup of the data prior to following these procedures.
From the "Partition Options" menu, select "Create NetWare Partition." 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 allocates
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: Figure 10
For more information, see "Hot Fix" in Concepts. Accept or decrease the NetWare partition size and press <Enter>. If you don't want to use the whole partition for NetWare, 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 disk space you want in the partition: Figure 11
Accept or change the size of the data area or the Hot Fix redirection area and press <Enter>. NOTE: If you have a NetWare-ready hard disk, ignore the free space left on the hard disk and continue with Step 8.
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: Figure 12
Press <Esc> and select "Yes" at the prompt to create the partition. If you have more than one disk, press <Esc> to return to the "Available Disk Drives" menu. Select the next disk to partition. Repeat Step 6 through Step 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 Mirror or Duplex the Disk (Optional). Otherwise, press <Esc> and go to Create Volume SYS:. NOTE: (Optional) You may want to conduct a surface test to check for bad blocks (select "Surface Test" on the "Available Disk Options" menu). The 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. 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. Disk mirroring illustrates disk mirroring: Figure 13
If NetWare partitions are duplicated over two or more hard disk controllers, the process is called duplexing and is a more effective way to protect data. Disk duplexing illustrates disk duplexing. Figure 14
For more information, see "Disk Duplexing" or "Disk Mirroring" in Concepts. NOTE: Even though your hard disks may be mirrored or duplexed, perform a regular backup of your hard disks at least once a week.
To 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 equal to or greater than the primary partition. Select the primary logical partition to be mirrored or duplexed on the "Partition Mirroring Status" screen: Figure 15
For more information on logical partitions, see "Device Numbering" in Concepts. Press <Ins> on the "Mirrored NetWare Partitions" screen: Figure 16
Select the secondary partition to be mirrored or duplexed with the primary partition on the "Available Partitions" screen: Figure 17
NOTE: 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: Figure 18
Press <Ins> to mirror or duplex additional hard disks to the primary hard disk. Go to Create Volume SYS:. With NetWare v3.12, your file server can have from 1 to 64 volumes. Your NetWare partition must have a SYS: volume for storing the 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. When spanning single volumes over hard disks, we strongly recommend that you duplex every hard disk. See "Disk Duplexing" in Concepts. If your network includes workstations using an operating system that allows long filenames (such as Macintosh workstations), create a separate volume for each name space. Long filenames take up more disk space than DOS filenames. Creating separate volumes for each filename type helps optimize disk space use and isolates network problems more easily. From the "Installation Options" menu, choose "Volume Options." 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 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. IMPORTANT: To change the block size for volume SYS:, follow the procedures under Changing the Block Size (Optional) before continuing with Step 4.
Press <Esc> and answer "Yes" at the "Create Volume?" prompt to create volume SYS:. (Optional) Create additional volumes by repeating Step 2 through Step 4. NOTE: When creating volumes other than SYS:, you are required to enter a volume name.
(Optional) To change the block size, continue with 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 Creating Additional Volumes on External Disk Subsystems (Optional). In NetWare v3.12, the default block size is 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. With 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. Available block sizes shows available block sizes. Figure 19
NOTE: 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. IMPORTANT: To have more than one volume on a hard disk, enter a lower number for the "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 rules to determine whether to make changes:
Determine the size of the volume segment by dividing 1024 by the block size. The result is blocks per megabyte: Figure 20
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: Figure 21
HINT: Set the size of volume SYS: between 60 and 100 MB, depending on your needs and your hardware configuration.
Press <Esc> and answer "Yes" at the "Create Volume?" prompt to change the block size. (Conditional) If you changed the block size for a volume (such as volume SYS:), finish creating the volume by returning to Step 4. To create additional volumes on an external disk subsystem, continue with Creating Additional Volumes on External Disk Subsystems (Optional) Otherwise, go to Mount Volumes. If your NetWare v3.12 file server uses external hard disks you can choose to make the additional hard disks separate volumes. From the "New Volume Information" screen, press <Esc> until the "Insert" option is enabled. 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. NOTE: To change the block size for volumes on external disk subsystems, follow the procedures under Changing the Block Size (Optional) before continuing with Step 4.
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 Step 2 through Step 4. Continue with Mount Volumes. Once you create volumes, you must mount them, one at a time. 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. Press <Enter> and select "Mount Volume." To mount other volumes, press <Esc> and repeat Step 1 through Step 3. WARNING: If you are installing from CD-ROM and the CD-ROM reader is cabled to the same SCSI controller as the hard disk containing volume SYS:, your server may lock up during installation.
If volume SYS: and your CD-ROM reader share the same SCSI controller, follow the procedures under Mounting a CD-ROM as a NetWare Volume (Conditional) If not go to Copy SYSTEM and PUBLIC Files. To mount the CD-ROM reader as a NetWare volume and avoid SCSI device conflicts, follow the procedures below. Press <Alt> <Esc> until you are at the console prompt (:). Type DOWN <Enter> Then type EXIT <Enter> Using a text editor, remove the CD device drivers from your CONFIG.SYS file. Save the updated CONFIG.SYS file. Using a text editor, remove any references to the CD drivers from your AUTOEXEC.BAT file. Save the updated AUTOEXEC.BAT file. Reboot the server by pressing <Ctrl> <Alt> <Del>. (Conditional) If the server doesn't boot automatically from the AUTOEXEC.BAT file, change to the subdirectory with your SERVER.EXE and other boot files, and type SERVER <Enter> (Conditional) If you are using ASPI device drivers (for example, for an Adaptec controller), you need to load one of the following disk drivers
At the console, type the following LOAD C:CDROM.NLM <Enter>CD MOUNT NETWARE_312 <Enter> At the console, type the following LOAD C:INSTALL <Enter> Continue with Copy SYSTEM and PUBLIC Files. INSTALL copies the NetWare utility files into the file server's SYS:PUBLIC and SYS:SYSTEM directories.
Procedure
Partition Information
Formula for decreasing the number of cylinders 
Formula for determining a fixed percentage of disk space
Mirror or Duplex the Disk (Optional)
Disk mirroring
Disk duplexing
Procedure
Partition Mirroring Status
Mirrored NetWare Partitions
Available Partitions
Mirrored NetWare Partitions
Create Volume SYS:
Procedure
Changing the Block Size (Optional)
Procedure
Available block sizes
Formula for determining blocks per megabyte
Formula for determining block segment size
Creating Additional Volumes on External Disk Subsystems (Optional)
Procedure
Mount Volumes
Procedure
Mounting a CD-ROM as a NetWare Volume (Conditional)
Copy SYSTEM and PUBLIC Files
| To | Do this |
|---|---|
Install the SYSTEM and PUBLIC files from drive A:. |
Continue with Step 1. |
Install the SYSTEM and PUBLIC files from a source other than drive A:. |
Follow the procedures under Copy SYSTEM and PUBLIC Files from CD or a Network Directory |
From the "Installation Options" menu, select "System Options."
Select "Copy System and Public Files" from the "Available System Options" menu.
Insert the Install diskette and press <Enter>.
Follow the prompts for the other diskettes.
Press <F5> to skip a diskette. For more information, see "Install" in System Administration.
NOTE: Depending on your version of DOS and your server speed, the Unicode diskette may require anywhere from 30 to 60 minutes to install. This is because approximately 147 files must be copied to three different locations.
From 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
D:\NETWARE.312\ENGLISH <Enter>
Or, if the CD-ROM reader is mounted as a NetWare volume on this server, type
NETWARE_312:NETWARE.312\ENGLISH
Press <Esc> twice and select "Yes" to exit INSTALL and get to the console prompt.
Continue with Load LAN Drivers.
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 default Ethernet frame type for NetWare v3.12 is 802.2.
If you have a mixed environment where you have NetWare v3.11 or earlier that use the 802.3 frame type, you may need to specify both 802.2 and 802.3 frame types.
To do this, you load the LAN driver twice and specify a different frame type each time the LAN driver is loaded.
A workstation running the 802.3 frame type can't communicate with the NetWare v3.12 server (which defaults to 802.2) until both frame types are loaded.
IMPORTANT: Some routers may not support the Ethernet 802.2 frame type. Check your router's documentation and load the frame type the router supports.
IMPORTANT: Loading both 802.2 and 802.3 frame types can affect network speed and performance. Standardize your network on 802.2 if possible.
Load the drivers with the default frame type. LOAD LAN_driver <Enter> LAN driver identification 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®. The LAN drivers are copied to SYS:SYTEM and can be loaded from there. (Conditional) If you are loading a Novell-supplied LAN driver, replace LAN_driver with the driver listed in LAN driver identification for your cabling system and network board. (Conditional) If you are loading a third-party LAN driver, load the driver from SYS:SYSTEM or from the diskette that came with the network board.
ARCnet RX-Net RX-Net II RX-Net/2 TRXNET Ethernet NE/2 NE/2T NE2 NE2-32 NE2_32 (replaces NE2-32) NE1000 - ASSY 950-054401 NE1000 - ASSY 810-160-001 NE1000 NE2000 - ASSY 810-149 NE2000T - ASSY 810-000220 NE2000 NE2100 - ASSY 810-000209 NE2100 NE1500T NE1500T NE3200 NE3200 NE32HUB NE32HUB Token-Ring NTR2000 NTR2000 For example, if you have an Ethernet cabling system and an NE2000 network board, type LOAD NE2000 <Enter> Answer the prompts for addresses and interrupts according to the information you entered on the File Server Worksheet. (Conditional) Load the drivers with another frame type. Type LOAD LAN_driver FRAME=frame_type <Enter> Replace frame_type with the frame type listed in Frame type for your cabling system and network board.
ARCnet Novell_RX-NET Default. Use on networks connected by ARCnet cabling. Ethernet ETHERNET_802.2 Default. Assigns the IEEE and OSI standard frame type. Required for networks using NCP security signature. ETHERNET_II Assigns a unique packet header (type code). Use on networks connected to DEC computers or to computers using the TCP/IP protocol. ETHERNET_802.3 Assigns the Novell IPX frame. Use on an existing network that only uses the 802.3 frame type. ETHERNET_SNAP Use when the 802.2 SNAP extension is required. Token ring TOKEN-RING Default. Assigns the standard packet header 802.2. Use only with protocols that require 802.2 encapsulation (such as the OSI protocol suite). TOKEN-RING_SNAP Assigns the 802.2 with SNAP header. Use with networks that need to communicate with protocols such as AppleTalk and TCP/IP. IBM PC Network IBM_PCN2_802.2 Default. Use on networks connected by PC network cabling. IBM_PC2N2_SNAP Use 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> If the LAN driver has been loaded previously, a message similar to the following appears: Do you want to add another frame type for a previously loaded board? n Type "Y" to continue. Select the correct frame type from the confirmation list. The following message appears: Previously loaded module was used re-entrantly For more information, see "Load LAN Driver" in System Administration. 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. Bind IPX to the LAN driver. To bind IPX to each LAN driver, type BIND IPX TO LAN_driver If you use multiple frame types on the same network board, NetWare v3.12 lists the 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 "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 a protocol to a driver that is loaded with two or more frame types for the same network board, see "BIND" in System Administration. Assign the 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. NOTE: This network address is not the same as the internal IPX network number you assigned to the file server in Step 2.
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 be
NOTE: If you use multiple frame types with your LAN drivers, assign a network address for each frame type.
For more on internal network numbers, see "Network numbering" in Concepts. 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 Create File Server NCF Files to create the STARTUP.NCF and AUTOEXEC.NCF files. A STARTUP.NCF file contains commands to load disk drivers and name space support for your file server. This file is executed after you run SERVER.EXE, and is stored on the disk you boot from (hard disk or diskette). Once STARTUP.NCF loads disk drivers and name space support and mounts volume SYS:, it turns control over to AUTOEXEC.NCF to complete the boot process. (Conditional) If you use a boot diskette to boot your file server, make sure the boot diskette is in drive A:. Load INSTALL by typing LOAD INSTALL <Enter> From the "Installation Options" menu, select "System Options." From the "Available System Options" menu, select "Create STARTUP.NCF File." On the "Path For STARTUP.NCF File" screen, enter the proper drive letter. Make sure the drive is set to
Press <Enter>. A screen similar to the following appears: Figure 22
The operating system reads the previously-entered disk driver and name space support from memory. Determine your system configuration and, from the following table, decide which additional commands you would like added to the STARTUP.NCF file. Type one command per line.
Load name spaces for Macintosh, OS/2, UNIX, or FTAM LOAD MAC.NAM LOAD OS/2.NAM LOAD NFS.NAM LOAD 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 or to the AUTOEXEC.NCF file.) SET Maximum Physical Receive Packet Size SET Cache Buffer Size SET Reserved Buffers Below 16 Meg SET Maximum Subdirectory Tree Depth SET Concurrent Remirror Requests SET Auto TTS Backout Flag SET Minimum Packet Receive Buffers (For more on these and other SET parameters, see "SET" in System Administration, or type "SET" at the server console. Press <Esc> to save the file.
To unload INSTALL utility Press <Esc> until you get the exit prompt. Select "Yes." To keep INSTALL loaded Press <Alt><Esc> to move to a different console screen. An AUTOEXEC.NCF file contains commands to complete the boot process after SERVER.EXE and STARTUP.NCF execute. 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:
From the "Available System Options" menu, select "Create AUTOEXEC.NCF File." The operating system reads the previously-entered disk driver and name space support from memory. A screen similar to the following appears, showing the commands that are automatically placed in AUTOEXEC.NCF. Figure 23
NOTE: 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 "INSTALL" in System Administration.
(Optional) From the table below, choose which of the more common commands to include in AUTOEXEC.NCF.
Create disk partitions, create volumes, format a hard disk, etc. LOAD INSTALL View network operation information. LOAD MONITOR Automatically lock the console at the time the server is booted. LOAD MONITOR L Load the print server on the file server and establish print services. LOAD PSERVER print_server Correct volume problems or remove name space entries from File Allocation and directory tables. LOAD VREPAIR (Optional) From your system configuration, choose additional loadable modules to include in AUTOEXEC.NCF. Additional module types are shown in the table below.
Equipment UPS.NLM Remote Console REMOTE.NLM RSPX.NLM RS232.NLM Remote Boot for Token-Ring RPL.NLM Remote boot for IBM and Western Digital on Ethernet RPL.NLM Third-party loadable modules (See third-party documentation) NOTE: If you use an uninterruptible power supply, see "UPS" in System 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 console commands to include in AUTOEXEC.NCF.
Implement security measures SECURE CONSOLE Display the processor speed SPEED Mount Volumes MOUNT VOL1 (or other volume name) MOUNT ALL Note: 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... See "Bind" in Utilities Reference. Set server parameters. SET commands (see "SET" in Utilities Reference). Pause after each command. PAUSE PAUSE allows you to read system messages displayed after the operating system executes a command. (Conditional) Decide whether to allow unencrypted passwords. If you have workstations using NET3.COM or NET4.COM shells, or existing servers using NetWare 2.1x utilities on the network, allow unencrypted passwords by typing the following SET ALLOW UNENCRYPTED PASSWORDS=ON <Enter> Press <Esc> to save the file. NOTE: The SET parameter to allow unencrypted passwords will not take effect until the server has been rebooted. To avoid rebooting, you may want to enter the SET command at the console prompt.Procedure
Table 7. LAN driver identification
Cabling System
Network Board
Driver
Table 8. Frame type
Cabling System
Frame Type
Explanation
Bind the Protocol to the LAN Driver
Procedure
Create File Server NCF Files
Create a STARTUP.NCF file
Procedure
A sample STARTUP.NCF file
To
Add these or other commands
Create an AUTOEXEC.NCF File
Procedure
A sample AUTOEXEC.NCF file
To
Add these commands
Module Type
Module Name
To
Add these commands