Liren Large Software Subsidy 11

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 11 / 11.iso / n / n007 / 2.ddi / README / README.UPG < prev next >

Wrap

Text File | 1993-07-24 | 47.3 KB | 1,119 lines

ReadMe Document for In-Place Upgrade NLM **************************************************************** TABLE OF CONTENTS **************************************************************** 1. Upgrade Options 2. Enhancements to v1.10 3. Known Problems 4. Needed Files A. NetWare 4.01 B. NetWare 4.0 C. NetWare 3.12 D. NetWare 3.11 E. NetWire 5. Disk Drivers 6. Using the /BINDERY Option 7. Calculating Memory Requirements A. Using the Memory Estimation Equation B. Memory Estimation Example 8. Timing and Memory Case Study 9. Using 4.0x LAN Drivers 10. File System Differences A. Disks B. Volumes C. Directories and Files D. Memory E. Bindery 11. NetWare v2.1x and v3.1x Specifications 12. A Brief History of NetWare 286 and 386 13. Disclaimer **************************************************************** 1. Upgrade Options **************************************************************** The In-Place Upgrade NLM uses the NetWare v3.1x operating system to upgrade a NetWare v2.1x or v2.2 file system and bindery to a NetWare v3.1x file system and bindery. After the file system is upgraded, the INSTALL NLM places the new operating system files on your server's SYS:volume. If your current server has an 80386 or higher microprocessor, the In-Place Upgrade method is the easiest way to upgrade your server. Unlike the Transfer method (v3.11), the In-Place Upgrade method only requires one server. The In-Place method reformats your hard disk's NetWare partitions without losing any data. The Across-the-Wire Migration utility is ideal if you are upgrading to a new server. The Migration utility is also available on NetWire. **************************************************************** 2. Enhancements to v1.10 **************************************************************** The following enhancements have been added In-Place Upgrade NLM v1.10: 1. Fixed all problems listed in the version 1.00 README file. 2. Added color. 3. Quickly estimates the memory needed to upgrade during System Analysis. 4. Detects if the MAC.NAM module needs loading during System Analysis. 5. Makes more efficient use of memory, shrinking the size of the NLM. 6. Added the /BATCH2 option to not pause on non-critical errors. 7. Renames the server object in the bindery if the server is renamed. 8. Added the /BINDERY option to upgrade the v2.1x bindery only. 9. No longer upgrades DYNAMIC bindery objects, like advertising servers. 10. Added seven new error messages (104, 114, 123, 135, 214, 248, 249). 11. Allows users to easily exit the upgrade whenever the screen pauses. 12. Formats the random password file (NEW.PWD) better. 13. Shortened random passwords to their original length. 14. Added a command-line error locator. 15. Made some text changes on the screens. 16. Enhanced the NLM to work with the NetWare v3.1x operating system. **************************************************************** 3. Known Problems: **************************************************************** Known problems in 2XUPGRDE.NLM v1.10 include: 1. Will not upgrade disks on IBM PS2 models 56 and 95. Models 57 and 90 have not been tested but are similar to the model 56 and 95. These models contain a hidden disk partition which stores the microchannel reference disk information. The In-Place Upgrade fails at the beginning of the Disk Modification phase and does not harm the file system. 2. For the v3.1x Read Only attribute to be functionally equivalent to the v2.1x Read Only attribute, the Delete Inhibit and Rename Inhibit attributes should be set. Unlike v3.1x, the v2.1x Read Only attribute does not allow a file to be deleted. 3. If the /BINDERY option is used, trustee assignments for all users, except the SUPERVISOR and GUEST are lost. Simply use the GRANT utilityto restore trustee rights. 4. Under rare circumstances the In-Place upgrade will run out of memory after upgrading the file system and bindery, but before updating trustee assignments. If this happens, simply use the GRANT utility to restore trustee rights. **************************************************************** 4. Needed Files: **************************************************************** The following files, shipping with various versions of NetWare, are used when performing an In-Place upgrade: A. NetWare 4.01 Diskette File Name Description ------------------------------------------------------------- UPGRADE: DR DOS 6.0 Bootable DOS Diskette FDISK COM DOS Partitioning Utility FORMAT COM DOS Format Utility SERVER EXE Single-User NetWare v3.11 Operating System MAC NAM Macintosh Name Space Module DCB DSK NetWare v3.11 Disk Driver IDE DSK NetWare v3.11 Disk Driver ISADISK DSK NetWare v3.11 Disk Driver PS2ESDI DSK NetWare v3.11 Disk Driver PS2OPT DSK NetWare v3.11 Disk Driver 2XUPGRDE NLM In-Place Upgrade NLM v1.10 AUTOEXEC BAT Simple Upgrade Instructions INSTALL: README 401 In-Place Upgrade Readme File B. NetWare 4.0 Diskette File Name Description ------------------------------------------------------------- UPGRADE: DR DOS 6.0 Bootable DOS Diskette FDISK COM DOS Partitioning Utility FORMAT COM DOS Format Utility SERVER EXE Single-User NetWare v3.11 Operating System MAC NAM Macintosh Name Space Module DCB DSK NetWare v3.11 Disk Driver ISADISK DSK NetWare v3.11 Disk Driver PS2ESDI DSK NetWare v3.11 Disk Driver PS2OPT DSK NetWare v3.11 Disk Driver 2XUPGRDE NLM In-Place Upgrade NLM v1.00 AUTOEXEC BAT Simple Upgrade Instructions INSTALL: README 40 In-Place Upgrade Readme File C. NetWare 3.11 Diskette File Name Description ------------------------------------------------------------- SYSTEM-1: SERVER EXE NetWare v3.12 Operating System SYSTEM-2: *.DSK Novell Disk Drivers *.LAN Novell LAN Drivers *.NAM Name Space Modules INSTALL NLM Install NLM running on NetWare (NETWIRE): 2XUPGRDE NLM In-Place Upgrade NLM v1.00 or v1.10 D. NetWire The files below are available on NetWire in NOVLIB Library 6, in the self-extracting 2XTO3X.EXE file. Future updates to the 2XUPGRDE.NLM will be uploaded to NetWire. For the most current NetWare v3.11 PS/2 disk drivers, see NOVLIB Library 4 in PS2311.EXE. For additional information about NetWire, call 1-800-NETWARE. If you need to do an In-Place Upgrade and do not have access to the necessary files, call Novell's Technical Support to obtain the same single-user version of the v3.11 operating system and drivers shipped on NetWare 4.01's UPGRADE diskette. Diskette File Name Description ------------------------------------------------------------- (NETWIRE): 2XUPGRDE NLM In-Place Upgrade NLM v1.10 2XUPGRDE DOC In-Place Upgrade User's Manual in ASCII ERRORS DOC In-Place Upgrade System Messages in ASCII README UPG This Readme File **************************************************************** 5. Disk Drivers **************************************************************** Below is a partial list of Novell-certified disk drivers and their testing status with the In-Place Upgrade NLM. Third-party disk drivers with known problems are also listed. Only the disk drivers listed below have been tested with this release of the In-Place Upgrade NLM. The NetWare 4.0 and 4.01 disk drivers included may not load correctly on the NetWare v3.1x operating system (SERVER.EXE). When upgrading, use the v3.1x disk drivers included on the 4.0 or 4.01 UPGRADE disk or get a v3.1x disk driver either from NetWire or a third-party vendor. DCB.DSK: - Novell Disk Coprocessor Board (DCB) Disk Driver 02-12-91 * Shipped with NetWare v3.11. * Shipped with NetWare 4.0's UPGRADE diskette. 02-02-93 * Shipped with NetWare v4.01's UPGRADE diskette. IDE.DSK: - Imbedded Drive Electronics (IDE) Disk Driver 06-11-92 * Available on NetWire (See IDE386.ZIP). * The IDE disk driver was written to work with ATA/IDE disk drives. The ISADISK driver should not be used with these disk drives. This driver is a self-configuring driver and does not rely on the BIOS for disk drive support. * The IDE disk driver will not work with ESDI and the ST506/412 bus controllers. The ATA/IDE, ST506, and ESDI interfaces look similar to the system software; however, they are handled differently by the disk driver. * If a disk drive is to have a DOS partition installed, it must be installed BEFORE the NetWare partition is installed. 04-08-93 * Shipped with NetWare v4.01. >>>>>> WARNING <<<<<< YOU CANNOT ADD A DOS PARTITION TO AN UPGRADED V3.1X OR V4.0X 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 and/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 286 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 286 partition on the IDE disk drive. Novell's engineering department is currently making every effort to alleviate the problem. For current status, please contact Novell technical support. ISADISK.DSK: - Industry Standard Architecture (ISA) and Extended ISA (EISA) Disk Driver - AT, MFM, RLL, ARLL, ESDI, IDE 06-17-92 * Shipped with NetWare v3.11. * NOT tested with the In-Place Upgrade NLM. * Had debug statements accidently left in it. 07-08-92 * Shipped with NetWare v3.11. * Shipped on the NetWare 4.0 UPGRADE diskette. * Fixed a problem associated with the Compaq 510 disk drive. The disk drive would appear to go off-line. * Available on NetWire (See ISA311.ZIP). 02-09-93 * Shipped with NetWare v4.01. LANSTOR5.DSK: - Storage Dimensions (third-party) * Storage Dimensions' LANSTOR5.DSK for NetWare v3.11 will not work with the In-Place Upgrade NLM due to a translation difference between their 286 and 386 Lanstor Drivers. The latest version of Lanstor Plus corrects this problem and can be obtained from Storage Dimensions. PS2ESDI.DSK: - PS/2 Enhanced Small Device Interface (ESDI) Disk Driver - Microchannel ESDI 02-12-91 * Shipped with NetWare v3.11. * Shipped on the NetWare 4.0 UPGRADE diskette. * Has some known problems. * We recommend that you use the 04-08-93 version or later. 02-20-91 * Was available on NetWire in PS2ESD.ZIP. 04-07-92 * Was available on NetWire for NetWare v3.11. * Has some known problems and is no longer available on NetWire. 02-09-93 * Shipped with NetWare v4.01. 04-08-93 * NetWare v3.11 driver * Available on NetWire in NOVLIB Library 4, in the file named PS2311.EXE. PS2MFM.DSK: - PS/2 Modified Frequency Modulation (MFM) Disk Driver - Microchannel MFM 01-31-91 * Shipped with NetWare v3.11. * Not shipped on the NetWare 4.0 UPGRADE diskette. * Unsupported in NetWare 4.0. * Available on NetWire upon request. PS2OPT.DSK: - PS/2 Small Computer Systems Interface (SCSI) Disk Driver - Microchannel SCSI, Magneto-Optical and CD-ROMs 10-15-91 * This driver replaces PS2SCSI.DSK. * Released on NetWire after NetWare v3.11 was released (PS2311.EXE/04). * Pulled off of NetWire after discovering problems with re- mirroring disks. Re-mirroring would take from 15-20 minutes. * PS2OPT.DSK is a SCSI driver supporting SCSI fixed disk drives and magneto-optical disks. Note, however, that PS2OPT is not compatible with the PS2ESDI and PS2MFM disk drivers released prior to October 25, 1991. New versions of the PS2ESDI and PS2MFM disk drivers will be released in the future that are compatible with PS2OPT. 05-21-92 * Available on NetWire upon request. * For use with SFT III NetWare v3.11 ONLY! 02-04-93 * Shipped on the NetWare 4.0 UPGRADE diskette. * Added logic to drive tape devices, such as the HP DAT device. * Available on NetWire in NOVLIB Library 4, in the file named PS2311.EXE. PS2SCSI.DSK: - PS/2 Small Computer Systems Interface (SCSI) Disk Driver - Microchannel IBM SCSI 02-12-91 * Shipped with NetWare v3.11. * Available on NetWire (See PS2386.ZIP). * This driver was replaced by PS2OPT.DSK in NetWare v3.1x. 02-04-93 * Shipped with NetWare v4.01. * This driver is the same as PS2OPT.DSK used in NetWare v3.1x, but with 4.0x function calls. **************************************************************** 6. Using the /BINDERY Option **************************************************************** If the SYS: volume won't mount, the v2.1x bindery will not get upgraded. Some situations which may cause a volume not to mount include: 1. Not loading the Macintosh name space module (MAC.NAM) when upgrading systems with Macintosh files on the volumes. 2. Having duplicate file names in the same directory. This is a problem that VREPAIR fixes and that the MAC.NAM module hides. 3. Insufficient server memory in the Cache Buffers memory pool. Caused by the Permanent and Alloc memory pools not releasing memory back to the Cache Buffers. Remedied by rebooting the server or adding more memory. 4. A power failure just before the Bindery phase has begun. With v1.00 of the In-Place Upgrade NLM, the only alternative was to recreate the bindery from scratch or to restore the system from backups, fix the problem, and then restart the upgrade. With v1.10, a new option has been added to resolve this problem. The new /BINDERY option allows you to restart the upgrade, skipping directly to the Bindery phase. The NLM looks for the v2.1x bindery files (NET$BIND.SYS and NET$BVAL.SYS) in the SYS:SYSTEM directory and merges them into the v3.1x bindery (NET$OBJ.SYS, NET$PROP.SYS and NET$VAL.SYS). If your v2.1x bindery files are corrupt, then simply rename the files created when you ran the BINDFIX utility (NET$BIND.OLD and NET$BVAL.OLD) with a ".SYS" extension, and restart the upgrade with the /BINDERY option. WARNING: When using the /BINDERY option, trustee assignments for all users, except the SUPERVISOR and GUEST are lost. Simply use the GRANT utility to restore trustee rights. **************************************************************** 7. Calculating Memory Requirements **************************************************************** An In-Place Upgrade may require more memory than the server normally needs to operate effectively. Servers normally cache a volume's entire FAT and only part of the DETs. However, during the upgrade the entire DET for each volume on the disk is cached. This is necessary since the NLM needs to store in memory all of a disk's system tables before it moves the disk blocks. A typical upgrade requires from 8 to 16 MB of RAM. The actual amount is dependent upon the number of directories on the disk. The upgrade process uses no more than 4 KB of additional memory for each megabyte of your hard disk and approximately 8 KB for each directory. Servers with large hard disks or having many directories may require additional memory installed before upgrading. Version 1.10 of the NLM quickly estimates server memory requirements during the System Analysis phase. The Disk Analysis phase also checks that your server has enough free memory and disk space to complete the upgrade. This is an exact measure of necessary resources, not an approximation. The upgrade process can take several hours for large disks. If your server has 8 MB of RAM and one or more large disks to upgrade, add another 4 MB to 8 MB of RAM. If your server needs more memory to complete the upgrade, the NLM will print an error message and exit the upgrade. If you get this message, then your time, not your server's file system, has been wasted. A. Using the Memory Estimation Equation If you do not have version 1.10 of the NLM, you can obtain an accurate estimation of server memory requirements using VOLINFO and NDIR. This rather complex equation, described below, requires six variables, but is accurate to within 5%. RAM = 1,640 + DISK_max {BMT + (0.157 * UDE_max) + (8 * DIR)} KB where BMT = (0.12 * SIZE) + (4 * DOS * VOLS) + (1.75 * LGVOLSIZE) KB RAM should be rounded up to the nearest megabyte. The 1,640 KB represents the memory used by DOS (COMMAND.COM), the NetWare v3.1x Operating System (SERVER.EXE), the disk drivers (*.DSK), the Macintosh Name Space module (MAC.NAM), and the In-Place Upgrade NLM (2XUPGRDE.NLM). DISK_max represents the largest sum from 32 possible disks. BMT represents the memory needed for the disk Block Move Table, the Hot Fix Redirection area, the optional DOS partition, and the FAT tables. SIZE = Disk capacity in MB DOS = DOS partition size in MB VOLS = Number of volumes on the disk LGVOLSIZE = Largest volume size on the disk in MB UDE_max = Maximum number of Used Directory Entries (UDE) for a selected volume on the disk DIR = Number of directories on the disk. It does not include files, salvage files, or trustee node entries. Multiply DIR by 2 if the v2.1x volume stores Macintosh files. The six variables above can be derived by running the NetWare v2.1x VOLINFO and NDIR utilities. Use PURGE first to permanently erase previously erased files. SIZE: Add the "Total KiloBytes" for each volume on the disk and divide by 1024 to convert from Kilobytes to Megabytes. Increase this number by 2% to include the Hot Fix area. SIZE is usually no larger than about 500 MB per disk. DOS: This number is determined when running the In-Place Upgrade NLM. A 5 MB DOS partition is the default. This number can be as high as 32 megabytes. VOLS: This number should not exceed eight. LGVOLSIZE:For the largest volume, LGVOLSIZE = "Total KiloBytes" / 1024. This converts Kilobytes into Megabytes and cannot exceed 255 MB. UDE_max: For a given volume, UDE = "Total Directories" - "Free Directories". UDE_max is the largest UDE for a given disk and will be no larger than 16,768. DIR: For each volume on the disk, subtract the number of files from the UDE of that volume. The number of files can be determined by running "NDIR \*.* /SUB /C" on each volume. (NOTE: The NetWare 4.0x NDIR utility gives the total directories count directly). DIR is usually no larger than 33,536. B. Memory Estimation Example The example below estimates the memory needed for an upgrade using the equation described above. This example server has the following resources. o 8 MB of server RAM o A two hard disk, three volume file system o Disk #0's capacity is 500 MB. It has volumes SYS: and VOL1: o Disk #1's capacity is 150 MB. It has volume VOL2: o After running "NDIR \*.* /SUB /C" on each volume, the following information is obtained: Files on SYS: 4,533 Files on VOL1: 0 Files on VOL2: 2,293 o VOLINFO gives the following information: ╔════════════════════════════════════════════════════════════╗ ║ Page 1/1 Total Free Total Free ║ ║ ╔═══════════════════╦═════════════════════╗ ║ ║ Volume name ║ SYS ║ VOL1 ║ ║ ║ KiloBytes ║ 261,120 36,592 ║ 227,112 224,842 ║ ║ ║ Directories ║ 16,768 11,381 ║ 14,720 14,717 ║ ║ ║ ╠═══════════════════╬═════════════════════╣ ║ ║ Volume name ║ VOL2 ║ ║ ║ ║ KiloBytes ║ 149,504 22,426 ║ ║ ║ ║ Directories ║ 9,856 7,148 ║ ║ ║ ║ ╚═══════════════════╩═════════════════════╝ ║ ╚════════════════════════════════════════════════════════════╝ Substituting the above data into the two equations produces the variables in the table below. ╔═════════╤════════════════════════════╤═══════════════════════╗ ║Variables│ Disk #0 │ Disk #1 ║ ╠═════════╪════════════════════════════╪═══════════════════════╣ ║SIZE │= ((261,120+227,112)/1024)* │= (149,504/1024)*1.02 ║ ║ │ 1.02 │= 149 MB ║ ║ │= 486 MB │ ║ ║─────────┼────────────────────────────┼───────────────────────║ ║DOS │= 5 MB (Has the SYS: volume)│= 0 MB ║ ║ │ │ (Has no SYS: volume) ║ ║─────────┼────────────────────────────┼───────────────────────║ ║VOLS │= 2 │= 1 ║ ║─────────┼────────────────────────────┼───────────────────────║ ║LGVOLSIZE│= 261,120/1024 = 255 MB │= 149,504/1024 = 146 MB║ ║─────────┼────────────────────────────┼───────────────────────║ ║ UDE │SYS: = 16,768-11,381 = 5,387│VOL2: = 9,856-7,148 ║ ║ │ │ = 2,708 ║ ║─────────┼────────────────────────────┼───────────────────────║ ║ UDE │VOL1: = 14,720-14,717 = 3 │ ║ ║─────────┼────────────────────────────┼───────────────────────║ ║UDE_max │= 5,387 │= 2,708 ║ ║─────────┼────────────────────────────┼───────────────────────║ ║DIR │= (5,387-4,533)+(3-0) = 857 │= 2,708-2,293 = 415 ║ ║─────────┼────────────────────────────┼───────────────────────║ ║BMT │= (0.12*486)+(4*5*2)+ │= (0.12*149)+(4*0*1)+ ║ ║ │ (1.75*255) │ (1.75*146) ║ ║ │= 545 KB │= 273 KB ║ ║─────────┼────────────────────────────┼───────────────────────║ ║DISK │= 545+(0.175*5,387)+(8*857) │= 273+(0.157*2,708) ║ ║ │ │ +(8*415) ║ ║ │= 8,247 KB │= 4,018 KB ║ ╚═════════╧════════════════════════════╧═══════════════════════╝ DISK_max = 8,247 KB, taken from Disk #0. RAM = 1,640 + DISK_max = 9,887 KB = 10 MB (rounded up to the nearest megabyte) Therefore, the server may temporarily need an extra 2 MB of RAM added to the existing 8 MB of RAM to complete the upgrade. Remember, because this is only an approximation, the server may still be able to complete the upgrade without adding more RAM. Either way, the In- Place Upgrade NLM will never destroy your file system because of lack of server memory. **************************************************************** 8. Timing and Memory Case Study **************************************************************** The case study below upgrades a large, fast hard disk on a typical 80386 server. For servers with slower hard disks, the Disk Modification phase times will be longer. Software Configuration: 2XUPGRDE.NLM v1.10 NetWare v3.1x Operating System NetWare v2.2 File System Server Configuration: Computer System: Compaq DeskPro 386/25m (80386 @ 25 MHz) Processor Speed: 242 Total Memory: 11.7 MB Hard Disk: Conner CP3504 - 510.4 MB (internal channel 0) ISA Type 104 Ave. Seek Time: 12 ms Disk Driver: ISADISK.DSK /b /l port=1F0 int=E Macintosh Files: None Other Modules: MAC.NAM Hot Fix Size: 2% Statistics: VOLINFO and NDIR gives the following information: ╔════════════════════════════════════════════════════════════╗ ║ Page 1/1 Total Free Total Free ║ ║ ╔═══════════════════╦═════════════════════╗ ║ ║ Volume name ║ SYS ║ VOL1 ║ ║ ║ KiloBytes ║ 261,120 36,312 ║ 227,112 197,100 ║ ║ ║ Directories ║ 16,768 11,381 ║ 14,720 14,047 ║ ║ ║ ╚═══════════════════╩═════════════════════╝ ║ ╚════════════════════════════════════════════════════════════╝ ╔════════╤══════════╤════════════════╤═══════╤══════╤═══════╗ ║ VOLUME │ CAPACITY │ PERCENT FULL │ FILES │ DIRS │ UDE ║ ╠════════╪══════════╪════════════════╪═══════╪══════╪═══════╣ ║ SYS: │ 255 MB │ 86% (219.5 MB) │ 4,533 │ 857 │ 5,387 ║ ║ VOL1: │ 222 MB │ 13% ( 29.3 MB) │ 567 │ 106 │ 673 ║ ╚════════╧══════════╧════════════════╧═══════╧══════╧═══════╝ Memory Results: SIZE = 484 MB UDE_max = 5,377 (+10 Trustee entries) DIR = 963 DOS = 5 MB Substituting the above data into the memory estimation equation produces: Total Server Memory: 11.70 MB RAM Estimate: 10.48 MB RAM Actually Needed: 10.50 MB Accuracy: ± 0.2% Incidentally, the server did not have enough memory to mount the volumes and upgrade the bindery at the start of the Bindery phase. I simply rebooted the server, which released memory from the Permanent and Alloc memory pools, and restarted the upgrade with the /BINDERY option. The volumes were then able to mount, the bindery was upgraded and the upgrade was completed. Server memory Statistics BEFORE running the In-Place Upgrade NLM: Permanent Memory Pool: 262 KB 2% Alloc Memory Pool: 65 KB 1% Cache Buffers: 10,602 KB 96% Cache Moveable Memory: 0 KB 0% Cache Non-Moveable Memory: 152 KB 1% Total Server Work Memory: 11,082 KB Server memory Statistics AFTER running the In-Place Upgrade NLM and failing at the Bindery phase: Permanent Memory Pool: 880 KB 8% Alloc Memory Pool: 459 KB 4% Cache Buffers: 9,576 KB 86% Cache Moveable Memory: 0 KB 0% Cache Non-Moveable Memory: 152 KB 1% Total Server Work Memory: 11,082 KB Timing Results (in minutes): 0:02 Boot DOS and NetWare server from floppy diskette >>>>> PHASE #1: SYSTEM ANALYSIS <<<<< 0:01 >>>>> PHASE #2: DISK ANALYSIS <<<<< 0:04 Analyzing Disk #0 0:43 Creating list of disk blocks to be moved 0:26 Creating list of Hot Fix Redirection Area blocks to be moved 0:25 Translating the Directory Entry Table (DET) for volume SYS: 0:29 Translating the File Allocation Table (FAT) for volume SYS: 0:14 Translating the Directory Entry Table (DET) for volume VOL1: 0:03 Translating the File Allocation Table (FAT) for volume VOL1: 0:00 Creating the Volume Segment Table >>>>> PHASE #3: DISK MODIFICATION <<<<< 0:01 Modifying Disk #1 0:11 Moving disk blocks to their new locations. Percent Moved: 0:01 Mirroring each volume's DET and FAT tables >>>>> PHASE #4: BINDERY <<<<< 0:01 Upgrading the bindery information Time-Per-Phase Summary: 0:03 Phase #0 - Load DOS, load NetWare, initialize NLM 0:00 Phase #1 - System Analysis 2:24 Phase #2 - Disk Analysis 0:13 Phase #3 - Disk Modification 0:01 Phase #4 - Bindery ------------------------------------------------------------- 2:41 TOTAL TIME TO UPGRADE THE FILE SYSTEM **************************************************************** 9. Using 4.0x LAN Drivers **************************************************************** NetWare 4.0x LAN drivers can be used with NetWare v3.11 only after loading an enhancement patch. Three modules are used to accomplish this task. NetWare 4.0x MLIDs are also more modular than v3.11 MLIDs. The 4.0x MLID is divided into three layers whose loading order is described below. The enhancement patch modules are: PATCHMAN.NLM: A patching utility used to load patches and enhancements to the NetWare operating system. LSLENH.NLM: An enhancement to the LSL needed if running a 4.0x LAN driver on a v3.11 server. This enhancement is built-in to NetWare 4.0x. It allows the Novell Source Routing Bridge to function properly. MSM31X.NLM: A Media Support Module needed to run 4.0x MLIDs on a v3.1x server. NetWare 4.0x uses MSM.NLM instead of MSM31X.NLM. To get these and other files off of the CD-ROM or floppy diskettes, the NWXTRACT.EXE utility must be used. This utility is located in the \NETWARE.40\<language> or \NETWARE.312\ENGLISH directories of the CD-ROM as well as on the INSTALL diskette. Its purpose is to extract single files from the 4.0x CD-ROM without using the Install program. To use this utility, at the DOS prompt, type: NWXTRACT path filename [destination] The path is the location of the Master Data file (FILES.DAT) on the install media. For example, to extract the file LSLENH.NLM from the E: drive, you might type: NWXTRACT E: LSLENH.NLM To load a 4.0x LAN driver on NetWare v3.11, type the following at the v3.11 console prompt: 1. LOAD LSLENH This enhancement NLM will auto-load the PATCHMAN NLM. 2. LOAD <MSM> Load the Media Support Module (MSM). The MSM uses MSM.NLM for 4.0x and MSM31X.NLM for v3.11 or later. After 4.0x is installed, the MSM is usually auto-loaded when the LAN driver is loaded. The MSMs shipping with NetWare 4.0x include: MSM.NLM MSM31X.NLM 3. LOAD <TSM> Load the Topology Specific Module (TSM). After 4.0x is installed, the TSM is usually auto-loaded when the LAN driver is loaded. The TSMs shipping with NetWare 4.0x include: ETHERTSM.NLM PCN2LTSM.NLM TOKENTSM.NLM FDDITSM.NLM RXNETTSM.NLM 4. LOAD <driver> Load the LAN driver module. The LAN drivers (*.LAN) shipping with NetWare 4.0x include (this list is subject to change): 3C503 HP386E32 NE2_32 TCARCH 3C509 HP386M16 NE3200 TCE16ATH 3C523 HP3AT16P NE32HUB TCE16MCH 3NW391R IBMETHR NI5210 TCE32MCH 3NW392R IBMFDDIO NI6510 TCNSH 3NW89XR ILANAT NI9210 TCTOKH 3NW990R IPTUNNEL NTR2000 TOKEN E20N4X MADGEODI PCN2L TOKENDMA E21N4X NCRWL06 SMC8000 TRXNET E2HN4X NE1000 SMC8033 UBPCETP E30N4X NE1500T SMC8100 UBPSETP E31N4X NE2 SMCARC EXP16 NE2000 T20N4X HP386A16 NE2100 T30N4X 5. BIND <protocol> TO <driver> The protocol may be IPX, TCPIP, etc. and the driver is the LAN driver loaded above. Please note that the default frame type for NetWare 4.0x Ethernet LAN drivers and for binding to a protocol is Ethernet 802.2 (FRAME=Ethernet_802.2). The default for NetWare v3.11 is Ethernet 802.3 (FRAME=Ethernet_802.3). **************************************************************** 10. File System Differences **************************************************************** When upgrading from NetWare v2.1x to v3.1x with the In-Place Upgrade NLM, you may notice some differences between the v2.1x file system and the v3.1x file system. Some of these differences and limitations are described below. A. Disks o In NetWare v2.1x, disk allocation blocks (volume block size) are limited to 4 KB. NetWare v3.1x allows block sizes of 4, 8, 16, 32 and 64 KB. o Secondary mirrored disks are not upgraded. If the In-Place Upgrade fails, these secondary mirrored disks can be used to quickly restore the server to NetWare v2.1x. After the primary mirrored disks have been successfully upgraded, the secondary mirrored disks can be re- mirrored using the INSTALL NLM. They can also be upgraded by first removing the upgraded disks and then running the In-Place Upgrade NLM a second time. o Disks with a maximum of 16 heads, 63 sectors per track and 1023 cylinders can easily be upgraded. Disks with more heads, sectors, or cylinders can also be upgraded; however, they will not be utilized as efficiently. This is a limitation of the DOS partition table. o Disks must have at least 10% free disk space per volume before upgrading them. This allows for NetWare v3.1x's larger directory entry structures (4 times larger), larger FAT structures (2 times larger), and mirrors of these tables. o Disk space can be set aside to create a DOS partition. This space must be partitioned using the DOS FDISK command and formatted using the DOS FORMAT command. These DOS utilities work only on internal hard disks. B. Volumes o NetWare v3.1x allows for 8 volumes per disk, even though v2.1x allowed for up to 16 volumes per disk. o Volumes cannot be resized. They remain the same size as before the upgrade. o The optional DOS partition reduces the available size of the SYS: volume by the number of megabytes specified for the DOS partition. C. Directories and Files o DOS directory and file names are shortened from 14 characters to 12 characters to conform to the 8.3 format in DOS. Name conflicts are renamed with numbered extensions, starting with ".001". o NetWare v2.15 allowed file names with an extension greater than 3 characters. All extensions are now truncated to 3 characters. o NetWare v2.1x directories named "PIPE" are renamed to "PIPE.001". "PIPE" is a reserved word in NetWare v3.1x. o Free and salvage entries in the directory are not upgraded. Free entries are unused and are for newly created files and directories. Salvage entries store information on files and directories that have been deleted. Salvage files can be recovered using the SALVAGE utility and deleted altogether using the PURGE utility. o Rights are now assigned at both the file and directory level. o File and directory attributes are different in NetWare v3.1x. o NetWare v3.1x is configured with a default that limits subdirectory depth to 25 levels. The default can be changed by adding "SET MAXIMUM SUBDIRECTORY TREE DEPTH = xxx" command, where xxx is between 10 and 100, to the STARTUP.NCF file. o Obsolete and incompatible v2.1x files are retained, such as VAP files. Remove them manually after the upgrade. D. Memory o The upgrade may take more server memory than the server normally needs to operate. Servers normally cache only part of the Directory Entry Table (DET). However, during the upgrade the entire DET of each volume for a disk is cached. See the "Calculating Memory Requirements" section above for more details. E. Bindery o In NetWare v2.1x, passwords are encrypted for greater security, and therefore cannot be retained during the upgrade. The encryption and decryption algorithms use the user's bindery ID. New user IDs are assigned when the bindery is upgraded. o User SUPERVISOR is not given a password, even if random passwords have been selected. To avoid inadvertent access to the server, the network supervisor should promptly set their password after loading the LAN drivers or type "DISABLE LOGIN" at the console prompt. o Core printing services are not upgraded. Printing capabilities must be reinstalled after the upgrade is completed. **************************************************************** 11. NetWare v2.1x and v3.1x Specifications **************************************************************** NetWare v2.15 NetWare v3.11 Specifications: NetWare v2.2 ---------------------------------------------------------------- Maximum Hard Disks Per Server 32* 2,048 Maximum Hard Disks Per Volume 1 32 (16 if mirrored) Maximum Volumes Per Server 32 64 Maximum Volumes Per Hard Disk 16 8 Maximum Directory Entries Per Volume 32,000 2,097,152 Maximum Volume Size 255 MB 32 TB Maximum File Size 255 MB 4 GB Maximum Addressable Disk Storage 2 GB 32 TB Maximum Addressable Server RAM 12 MB 4 GB Maximum Directory/File Name Length 14 Chars 12 Chars Name Spaces Supported DOS DOS Macintosh Macintosh NFS (UNIX) FTAM OS/2 Disk Block Allocation Sizes 4 KB 4, 8, 16, 32, 64 KB * NOTE: ELS Level II NetWare v2.15 allowed for only 2 hard disks per server (internal only). **************************************************************** 12. A Brief History of NetWare **************************************************************** Most NetWare 286 products were offered in three categories. SFT III was introduced with NetWare 386: 1. Advanced NetWare 68 - For Motorola 68000 or later based servers 86 - For Intel 8088 or later based servers 286 - For Intel 80286 or later based servers 2. SFT NetWare (System Fault Tolerant) Level I - Duplicate directories, duplicate FATs, read-after-write verification, UPS monitoring and Hot Fix Level II - Disk mirroring, disk duplexing, and TTS Level II - Mirrored servers 3. ELS NetWare (Entry Level Solution) Level I - 4 user versions Level II - 8 user versions Version Date Enhancements ---------------------------------------------------------------- v2.0 1986 Written for Intel 80286 and above based servers. Separated the LAN driver software from the operating system. This allowed users to mix and match network cards without having to buy extra operating systems. 100 users maximum. Currently not upgradeable. Replaced by v2.0a 2 weeks after release. v2.0a 1986 Supported Token Ring cards. Added System Fault Tolerance (SFT) I features (duplicate directories, duplicate FATs, read-after-write verification, and Hot Fix) and SFT II features (disk mirroring, disk duplexing, and TTS). Currently not upgradeable. v2.1 1987 Added an accounting feature that lets managers tally up the usage of the network and bill the users. Also separated the disk driver software from the operating system. v2.11 1988 Worked with the physical "key card" software protection scheme. v2.12 1988 Protected software via "embedded serial numbers." v2.15 1988 Added Macintosh support (versions a and b). v2.15c 1989 Enhanced Print Server functionality and fixed some disk limitations. v2.2 1991 Consolidated ELS NetWare Levels I and II, Advanced NetWare and SFT Levels I and II NetWare. Simple to install. Has v3.1x-like utilities. v3.0 1989 Written for Intel 80386 and above based servers. Replaced VAPs with NLMs. High performance file system. Added OS/2 name space. Introduced a 250-user version. v3.1 1990 Added enhancements and bug fixes to v3.0. v3.11 1991 Added NFS and FTAM name spaces. Supports TCP/IP, AppleTalk and SNA transport protocols. Introduced SFT III. v4.0 1993 Written for multi-server network environments. Added directory services, file compression, block suballocation, data migration, auditing, multiple-language enabled, and VLMs. Introduced a 1000-user version. v4.01 1993 Maintenance release of v4.0. NetWare History Summary ╔═══════╤══════╤══════╤══════╤══════╤══════╤══════╤══════╤══════╗ ║ v2.0 │o │ │ │ │ │ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ │ooooooooooooooooooo │ │ │ │ │ ║ ║ v2.0a │ xxxxxxxxxxx│ │ │ │ │ │ ║ ║ │ │ %%%%%%%%%%%%%%%%% │ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v2.1 │ │ xxx │ │ │ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v2.11 │ │ │ oooo│ │ │ │ │ ║ ║ │ │ │ xx │ │ │ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ │ │ │ ooo │ │ │ │ ║ ║ v2.12 │ │ │ xxx │ │ │ │ ║ ║ │ │ │ ***** %%%%%%%% │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ │ │ │ o │ │ │ │ ║ ║ v2.15 │ │ │ xxxxxxxxxxxxxxx │ │ ║ ║ │ │ │ │ ************ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v2.2 │ │ │ │ │ │xxxxxxxxxxxxxxxx ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v3.0 │ │ │ │ +++++++ │ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v3.1 │ │ │ │ │ +++++ │ │ ║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v3.11 │ │ │ │ │ │++++++++++++++++++ ║ ║ │ │ │ │ │ │ &&&&&&&&║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v4.0 │ │ │ │ │ │ │ │$$$$$$║ ╟───────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┼──────╢ ║ v4.01 │ │ │ │ │ │ │ │ $$$$║ ╚═══════╪══════╪══════╪══════╪══════╪══════╪══════╪══════╪══════╝ └┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┴┴─┴─┴─┘ 1986 1987 1988 1989 1990 1991 1992 1993 KEY: ooo = Advanced xxx = SFT I and II &&& = SFT III %%% = ELS I *** = ELS II +++ = 3.x $$$ = 4.x **************************************************************** 13. Disclaimer **************************************************************** Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell.