|
Known Issues
|
|
- There is a known problem which occurs during the installation of Novell NetWare 4.0X, that involves the DDI file used during the initialization of the host adapter device driver. The DDI file does not contain all the possible slot number options available on all PCI systems, as there are too many combinations. As a result, during the installation procedure, Novell NetWare will report that it is unable to load the driver in the given amount of time. This is because the DDI file does not contain any slot options, which causes Novell NetWare not to load the driver. Note, however, that this is not an error. The user simply needs to go to the console screen and manually enter in the correct slot number and installation will continue.
- A second known problem exists that will hang the server after loading the host adapter device driver. This problem involves targets that do not support scanning of multiple luns, with the command line option lun_enable. The user simply needs to set the command line option multlun_targets to only scan targets that support multiple luns. This problem is known to occur with Quantum Empire 540S drives.
- Novell recommends not using IRQ 15 for host adapters. If your system bios allows the assignment of IRQs, change your adapters IRQ to a value other than 15.
- On Novell NetWare 4.11, without media in the CD-ROM drive, and using built in driver support for CD-ROMs, the message "No CD-ROM Devices Registered with NetWare." is reported, if "cd device list" is issued.
- There is a known problem with some hard drives that are less than or equal to 1 GB. If these drives were previously formatted using the Adaptec 7800 Family Manager Set v2.1x driver for Novell NetWare, and are now being upgraded to the 7800 Family Manager Set driver, the user may have problems in finding the device during initialization. If this occurs, use the following command line option in your STARTUP.NCF file:
ext_tran=n
- On some system configurations and during a first time installation or when upgrading to the 7800 Family Manager Set v3.02.2 driver, the user may see a window with the following warning message:
"One or more partitions on drive 0 are inconsistent with the driver
geometries (xxx heads, xx sectors, and xxx cylinders) that Novell NetWare is
using. You may continue and edit the partition anyway, although this inconsistency
could create problems later on."
This message is shown when the "Installation Options" window appears, and the user highlights and selects "Disk Options", followed by "Modify Disk Partitions and Hot Fix". The user should simply continue to the "Disk Partitions Options" window to edit the partition, and installation will complete successfully.
- The AIC78U2.HAM driver will not load if older versions of the NWPA.NLM file have been used. To fix this problem, use the updated version of the NWPA.NLM file that is included in this diskette.
- The AIC78U2.HAM driver requires a minimum of 16 MB of memory.
- When starting a Novell NetWare server with two Ultra2 host adapters, the error message "Unbound Device Object" might appear. Manually unloading and reloading the driver will fix the problem, as well as removing the "slot=xx" option in the STARTUP.NCF file (and then selecting the default slot number(s)). This is being addressed by Novell.
- When loading server.exe with the ""load aic78u2.ham slot=# lun_enable"" switch, the server locks up while scanning the LUNs. This is being addressed by Novell.
- On some SMP systems, if the IRQ setting is set to "Auto" in the system's BIOS then NW 4.11 installation will hang at loading a NIC driver. This problem was tested with a Tyan P5 SMP, and it did show up. The problem did not show up on the DEC SMP system. This is being addressed by Novell.
- Certain systems will not run Sbackup under Novell NetWare v3.12. Novell NetWare v4.11 runs it with no problems. This is an issue which is currently being addressed by Novell.
- Some systems experienced problems loading Novell NetWare when loading the AIC7870.DSK and ASPICD.DSK drivers after the AIC78U2.HAM driver. The workaround is to load the DSK drivers before the HAM driver.
|
|