(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Specified Target Server for This Job Is Unknown"
DOCUMENT ID#: FYI.P.8976
DATE: 30SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Specified target server for this job is unknown."
ISSUE/PROBLEM
The printer on the server COM1 port would not print. Jobs would make it to the queue; however when the user looked at the job in PCONSOLE, the following error displayed:
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Print Jobs Just Sit in Queue - Addman Application
DOCUMENT ID#: FYI.P.8989
DATE: 29SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Print jobs go to the queue and never print or never go active.
ISSUE/PROBLEM
Configuration:
■New installation of NetWare v2.2 operating system
■Running the PSERVER VAP dated 02-11-91
■Printers connected off the file server
The user created two print queues and a print server. The jobs would go to the print queues and remain in the queue without ever printing to the printer. All jobs were being printed through a software application called Addman.
SOLUTION
The user contacted ADDMAN who explained that the program was attempting to mount Form 1 within their application. Because the application was looking for Form 1 and no Form 1 had been defined, the jobs just accumulated in the queue and never printed. When the user went into the ADDMAN setup options and set the form setting to 0, the jobs began to come out of the printer.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: GPI on Model 95
DOCUMENT ID#: FYI.P.8991
DATE: 29SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Abend: GPI
ISSUE/PROBLEM
Configuration:
■The server was a model 95 with an IBM 16/4 Token ring nic,
■12 MB 70 ns IBM RAM
■IBM SCSI controller with cache
The user's system was receiving an abend GPI message.
SOLUTION
The user upgraded the IBM microcode from v1.02 to v1.1. The user also found bad sectors on the working copy of SYSTEM-1 disk, that had been used to reinstall the operating system and track zero information. The user made new working copies of the SYSTEM-1 disk and verified that there were no bad sectors with Norton's Disk Doctor. Then after the user did a complete reinstall and restore, the system did not experience any more GPIs.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Getting Burned-In Address from NIC"
DOCUMENT ID#: FYI.P.8987
DATE: 29SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Error getting burned in address from NIC"
ISSUE/PROBLEM
The user upgraded a model 95 from 16 MB to 24 MB of RAM. When the user rebooted the system, it displayed the following error:
┌────────────────────────────────────────┐
│Error getting burned in address from NIC│
└────────────────────────────────────────┘
The network interface card was a Proteon P1840 with a driver called PRONET4.LAN dated 05-23-91.
SOLUTION
Proteon Inc. informed the user that they have no P1840 driver for the NetWare v3.11 operating system that allows use of more than 16 MB of RAM. Upgrading to a P1892 card solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "A File Server Could Not Be Found." - SMC PC-600
DOCUMENT ID#: FYI.P.8993
DATE: 29SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "A file server could not be found."
ISSUE/PROBLEM
File server has an SMC PC600 Arcnet card in it. When a workstation is directly cabled to the server, it locates a connection without a problem. When the user placed a passive hub between the server and the workstation, the following message displayed when executing NETX:
┌─────────────────────────────────┐
│A file server could not be found.│
└─────────────────────────────────┘
The user tried do the following to solve the problem:
■ Replacing passive hub and terminators
■ Checking impedance setting for topology:
BUS - set to high impedance
STAR - set to low impedance
SOLUTION
Replacing the file server card solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error "SSB Not Free during Initialization of Token-Ring"
DOCUMENT ID#: FYI.P.8961
DATE: 28SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "SSB not free during initialization of Token-Ring"
ISSUE/PROBLEM
After the server (IBM Model 80) experienced a power hit, the user had to run REFERENCE to get the server to boot again. Then when the user brought the server up, the system displayed the following error:
When running REFERENCE again, the user discovered that the card was set to a different interrupt and port than what NetWare was configured for. Setting the card for the correct settings solved the problems.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Locate Subdirectory and Files - DOS 5.0
DOCUMENT ID#: FYI.P.8963
DATE: 28SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.15c
SUPERSEDES: NA
SYMPTOM: Not locating one subdirectory or files when running DOS 5.0
ISSUE/PROBLEM
Configuration:
SMC 10BaseT 16-bit network interface cards
When booting with DOS 3.3, the files can be located. However, one subdirectory and files could not be located when running DOS 5.0 on an IBM P70 (386 DX workstation). The files are not flagged HIDDEN.
SOLUTION
Even though the files could not be located, the user could run the executables from the subdirectory. When the user ran an executable, all the files reappeared in the subdirectory and have not disappeared since.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Possible Open Cable Disconnect Detected" - SMC Elite 32T
DOCUMENT ID#: FYI.P.8941
DATE: 25SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Possible open cable disconnect detected"
ISSUE/PROBLEM
Configuration:
Using SMC Elite 32T drivers dated 10-14-91 that shipped with the cards
The user's system displayed the following error message:
┌───────────────────────────────────────┐
│Possible open cable disconnect detected│
└───────────────────────────────────────┘
SOLUTION
Standard Microsystems Corp. (SMC) acknowledged that there are several problems with that driver including the reporting of the above error message. The faulty driver date is 10-14-91. When the user downloaded the newest driver from SMC, the system came up and is running fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Only One Workstation Can Attach to Arcnet Server
DOCUMENT ID#: FYI.P.8890
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Cannot connect more than one workstation at a time to the server
ISSUE/PROBLEM
Configuration:
Arcnet topology
One workstation could log into the server through a passive hub only when the two unused connections (four total, one for workstation, one for server, and two unused) on the hub were not terminated. When the unused connections were terminated, the workstation received the following message after running NETX.COM:
┌─────────────────────────────────┐
│A file server could not be found.│
└─────────────────────────────────┘
When all three workstations were connected, no one could connect to the server.
SOLUTION
The user found that the Arcnet address on the server had been set to zero. Changing the address to number other than zero solved the problem. Valid Arcnet addresses are 1 through 255.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Finding Start Info Record"
DOCUMENT ID#: FYI.P.8895
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Error finding start info record"
ISSUE/PROBLEM
When loading SERVER, the following error immediately displayed:
┌───────────────────────────────┐
│Error finding start info record│
└───────────────────────────────┘
SOLUTION
The CMOS had some corruption. Resetting the CMOS solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Lotus Translator Program Needs DOS Path Statement
DOCUMENT ID#: FYI.P.8902
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: All Versions
SUPERSEDES: NA
SYMPTOM: Program will not run without a DOS "Path" statement to the directory of its files.
ISSUE/PROBLEM
Lotus works fine over the network. However, the translator would not locate the files necessary to run even with a drive mapping and the cursor sitting at that prompt or a search mapping. Lotus said that the user had to have a DOS path statement to run the program.
SOLUTION
The files resided in a directory off the SYS: volume. The user did the following in the AUTOEXEC.BAT to get the program to run:
IPX
NETX
Path = f:\<dir path>.
Then the user logged in and was able to get the necessary DOS path to a network directory.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Packets Not Crossing Micom Remote Bridge
DOCUMENT ID#: FYI.P.8901
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Packets do not cross the bridge
ISSUE/PROBLEM
Configuration:
■Two Micom bridges across a 56 Kbps leased line.
■Each site was set up identically with a NetWare v3.11 server using the following:
-SMC Elite NIC
-SMCPLUSSV.LAN v3.09
-SMC 3512 concentrator
■Each workstations had SMC network interface cards
SLIST only showed the local server and the two servers could not locate each other. Packets were almost all rejected by the bridge but it was setup for no filtering. When the user tried Ethernet_802.2 at the servers and workstations, the servers could locate each other and SLIST and USERLIST worked; however, when logging in, the system displayed the following error:
┌───────────────────────┐
│server does not respond│
└───────────────────────┘
The hardware configuration, including the cabling, was set up as MICOM Communications Corp. recommended.
SOLUTION
Originally, the Micom bridge was connected locally to twisted pair 10BaseT cabling through an AUI connector and to the concentrator. The workstations were all on twisted pair cabling, and the server had a coax connection to the concentrator. The problem was fixed by removing the bridge from twisted pair cabling and putting it on the coax connection with the server.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Slow Performance with PERFORM2 and Adaptec AHA-1740
DOCUMENT ID#: FYI.P.8900
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM: PERFORM2 causes disk channel bottleneck and slow performance.
ISSUE/PROBLEM
A user was concerned about the slow performance of the server while running PERFORM2. Running PERFORM2 in sequential mode caused dirty cache buffers on the server to increase to around 2000 and performance would drop to a crawl. The faster 32-bit network interface cards had the problem more than 16-bit network interface cards.
SOLUTION
The user was using the AHA-1740 driver and IO_COMBINE=1. Without IO_COMBINE=1, the disk channel had no problem keeping up with LAN traffic and dirty cache buffers stayed very low. The reason the switch was set to 1 to begin with is that Adaptec recommended trying it when the user was having problems with a different controller and drive.
This is a good example of the tradeoff made when using the switch "io_combine=1" with the 1540, 1640, or 1740 family of Host Bus Adapters (HBAs) and their NetWare v3.11 drivers. The last word is that only the 1740 HBA (not the 1740A or 1742A) requires the switch, turning off Scatter/Gather (S/G). When disabling the S/G to solve a problem and it does not solve the problem, always re-enable S/G by taking the switch out of the load statement.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: System NMI - Two Bus Mastering Cards with Micronics Motherboard
DOCUMENT ID#: FYI.P.8905
DATE: 24SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Nonmaskable Interrupt (NMI) errors
ISSUE/PROBLEM
When trying to use more than two bus-mastering cards in a Micronics 486/50 EISA motherboard, with Adaptec 1740 cards and NE3200 cards, the system received NMI errors.
The Micronics 486/50 EISA motherboard has eight slots. Six of these slots are supposed to be able to handle bus mastering cards. When trying to use more than two bus-mastering cards with this motherboard and NetWare, the system stops the file server and sends an abend message with an NMI generated by the system board.
SOLUTION
Micronics is working on a fix for this. As of 09-24-92, only two bus-mastering devices can be used with the Micronics motherboard and NetWare.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Invalid COMMAND.COM Exiting Windows
DOCUMENT ID#: FYI.P.8908
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Invalid COMMAND.COM"
ISSUE/PROBLEM
When exiting from Windows, the user gets following error:
┌───────────────────┐
│Invalid COMMAND.COM│
└───────────────────┘
Other symptoms were not having all the search mappings show up from within the MAP utility for NetWare and Windows. If the user went to a DOS box in Windows and typed MAP, all the mappings were there.
The user had just installed the NetWare Workstation Kit for Windows. When the user checked in the C:\WINDOWS subdirectory for the WINSTART.BAT file that is created by the NWSETUP program, it was still there.
SOLUTION
Deleting WINSTART.BAT solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Search Mappings Show as Regular Mappings - NOVI Program
DOCUMENT ID#: FYI.P.8912
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Search mappings show up as drive mappings.
ISSUE/PROBLEM
Configuration:
■IPX 3.10
■NETX 3.26
When the user logged in the system, all the search mappings were only drive mappings. However, if the user logged out and back in, everything was fine.
SOLUTION
The problem was with the anti-virus program called NOVI by Certus International Corp. After removing the terminate-and-stay resident program, everything worked without a problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: File Server Hung Loading SERVER.EXE - NEC PowerMate 486/33E
DOCUMENT ID#: FYI.P.8914
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: The file server hung while loading SERVER.EXE.
ISSUE/PROBLEM
The file server hung while loading SERVER.EXE.
SOLUTION
The user disabled Global Caching on the NEC machine and replaced four
1 MB Single In-line Memory Modules (SIMMs) on the memory board for one
4 MB SIMM. The user also had one 4 MB SIMM on the motherboard. With the new items installed, SERVER.EXE now loads and mounts the duplexed volumes successfully.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Plotter Printing in Wrong Place - Power Spikes
DOCUMENT ID#: FYI.P.8909
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Plotter plotting correct data in wrong place
ISSUE/PROBLEM
The user had an electrostatic plotter running as an RPRINTER. It had been working fine until the building was struck by lightening. After the lightning struck, the user started have problems such as the following:
Some jobs would print fine. Then some jobs had problems where the data would be plotting fine, and then the plotter would jump across the page and start plotting the data again only it would be offset.
SOLUTION
When the building was hit by lightning, it messed up the power so that the power was getting 100 watt power spikes every 5 minutes. After the user put a power conditioner on the plotter, the problems went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "A File Server Could Not Be Found." - Cold Boot, 3C503
DOCUMENT ID#: FYI.P.8907
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Error: "A File Server could not be found."
ISSUE/PROBLEM
When the user cold boots the machine, it displayed the following error:
┌─────────────────────────────────┐
│A File Server could not be found.│
└─────────────────────────────────┘
When the user warm boots the machine, it located the file server.
SOLUTION
This is not a driver problem. It is a memory management problem. In this case, the user had DOS 5.0. When cold booting, DOS 5.0 loads and 3c503 is loaded after stepping on DOS in memory. The warm boot reloads DOS while recognizing the 3c503 driver in memory and does not touch it. Using the exclude statement for whatever memory address the 3c503 driver is using will allow the server to come up from a cold boot.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: Bad Resource Tag Passed... SMC Elite-32
DOCUMENT ID#: FYI.P.8904
DATE: 23SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Errors: "Abend: bad resource tag passed to LSLRETURNEDECB" or "Abend: bad resource tag passed to SCHEDULEINTERRUPTTIME call back"
ISSUE/PROBLEM
Configuration:
■Running a noncertified 486/50 EISA machine with SMC Elite-32 Ethernet cards
■Using SMCE32.LAN dated 10-14-91 v1.10
The user's system displayed the following abend messages:
When the user replaced the Elite-32 cards with other 16-bit Ethernet cards, the abends went away.
Standard Microsystems Corp. (SMC) has had some problems with faster EISA boxes. SMC has a beta driver that has resolved many Elite-32 problems in these faster boxes. To obtain the driver, the user needs to contact SMC.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Bad or Missing Command Interpreter - DXMC0MOD.SYS
DOCUMENT ID#: FYI.P.8924
DATE: 22SEP92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Bad or missing command interpreter
ISSUE/PROBLEM
The user was unable to do a RPL (Remote Program Load) when using IBM's LAN Support Program.
SOLUTION
The user had IBM LAN Support program v1.25 with DXMC0MOD.SYS dated 01-23-92. After getting a newer DXMC0MOD.SYS from IBM, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Beaconing Errors Adding New Server to Existing Ring
DOCUMENT ID#: FYI.P.8926
DATE: 22SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Token-Ring card beaconing during insertion process
ISSUE/PROBLEM
The user tried to add a NetWare v3.11 server to an existing ring. As soon as the sever was brought up, beaconing errors occurred.
SOLUTION
The new card was set for 4 mb and the ring was 16 mb. Changed the speed to match the ring solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NMI Error Loading Two Adaptec 1542b Controllers
DOCUMENT ID#: FYI.P.8879
DATE: 21SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: File server received Nonmaskable Interrupt (NMI) errors
ISSUE/PROBLEM
Configuration:
Two Adaptec HBAs (duplexed).
When the user tried to boot the machine from diskette, it loaded the first 1542b fine. On the second load attempt the file server received NMI error.
SOLUTION
Although loading drivers manually worked, the real solution was to set the DMA on the Adaptec controllers to the same setting (5 in this case).
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Drive Does Not Map to Any Volume on Server" - Windows
DOCUMENT ID#: FYI.P.8865
DATE: 18SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Errors: "Restoring local drive to..." "Drive does not map to any volume."
ISSUE/PROBLEM
When the user booted the workstation, the system displayed the following WINDOWS message:
┌────────────────────────────┐
│Restoring local drive to....│
└────────────────────────────┘
Then the following NetWare message overlaid the Windows message:
┌───────────────────────────────────────────┐
│Drive does not map to any volume on server.│
└───────────────────────────────────────────┘
The workstation continued to boot up and work fine.
The user checked for PERMANENT drives that had been set when viewing "Network Connections" under the "DISK" option in the "File Manager." Nothing was set, and none of the mappings had a "DRIVE" icon on the left side.
SOLUTION
The user's WIN.INI file, under the "NETWORK" heading, contained the statement
D:=
Removing this statement stopped the error messages.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When trying to run TCPIP on the workstation, the system displayed the following error:
┌──────────────────────────────┐
│Error registering protocol IDs│
└──────────────────────────────┘
This error usually means that something is messed up something in the NET.CFG file, such as not specified the frame types and protocols correctly for the card they are using. The user was registering IPX and TCPIP and the NET.CFG looked fine. After the user removed the TCPIP protocol and just loaded the IPX protocol, the system worked fine.
SOLUTION
The user had a menuing program called LANselect loaded. The user had loaded a switch /win30 for 3.0 windows support for LANselect. The only problem was that the user was using Windows 3.1 that does not need this switch. This switch was causing the problem. After taking out the switch, everything worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: Bad Resource Tag Passed to LSLReturnRCVECB
DOCUMENT ID#: FYI.P.8799
DATE: 17SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Abend: Bad resource tag passed to LSLReturnRCVECB
ISSUE/PROBLEM
The file server (a Compaq SystemPro) had been up and running for 60 days. Then they got the following ABEND one morning before anyone had logged in, and a second time about 2 hours later (with users logged in).
The user rebooted the server each time the abend occurred, and it came up fine.
SOLUTION
Replaced the NE3200 in the server and upgrading NE3200.LAN to the version dated 01-15-92 from NE386.ZIP solved the problem.
NE386.ZIP is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Although the Grafika 3c-2 was certified with PTI-217 controller, the manufacturer had begun shipping these machines with a different IDE, PTI-227 controller. DTK Computer Inc. said they had seen some problems with the new controller. When the user switch to using the PTI-217 controller, the error message went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Insert Disk with COMMAND.COM in Drive A" - Mountain Tape
DOCUMENT ID#: FYI.P.8808
DATE: 16SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Insert disk with command.com"
ISSUE/PROBLEM
Configuration:
Mountain FileSafe External 8000 Plus v5.2.3-TD running on NetWare v3.11 operating system.
Every time the user performed an unattended backup using the above utility with a Mountain FileSafe External 8000Plus on a client, the system displayed the following error:
┌───────────────────────────────────────┐
│Insert disk with command.com in drive A│
└───────────────────────────────────────┘
A boot disk with the correct COMMAND.COM was in the A: drive. When the user tried setting the COMSPEC to the A: drive and to the network drive, the system still displayed the error message when running a tape backup. This problem was only occurring while using the Mountain FileSafe External 8000Plus.
SOLUTION
In the utility options in the Mountain FileSafe External 8000Plus software, there is an install option. Switching "BYPASS DEVICE CONCURRENCY" to YES fixed the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NetWare and Banyan Vines Example - ODINSUP.COM
DOCUMENT ID#: FYI.P.8844
DATE: 14SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
NetWare and BANYAN VINES example using ODINSUP.COM.
SAMPLE AUTOEXEC.BAT
ECHO OFF
PROMPT $P$G
lsl
ne2000
odinsup
ban /nc
ndisban
ipxodi
netx
f:login supervisor
c:
redirall
z:login admin@eng@testing
SAMPLE CONFIG.SYS
files=20
buffers=20
DEVICE=c:\banyan\protman.dos /I:c:\lanman
lastdrive=E
SAMPLE NET.CFG
LINK DRIVER NE2000
INT 2
PORT 320
FRAME ETHERNET_802.3
FRAME ETHERNET_SNAP
FRAME ETHERNET_II
FRAME ETHERNET_802.2
PROTOCOL ODINSUP
BIND NE2000
SAMPLE PROTOCOL.INI
[PROTOCOL_MANAGER]
DRIVERNAME=PROTMAN$
[VINES_XIF]
DRIVERNAME=NDISBAN.DOS$
BINDINGS=NE2000
Notes:
1. Execute Banyan's PCCONFIG.EXE and select network interface card such as NE2000 and the necessary settings.
2. Execute SETHAND.EXE (available from Banyan) against REDIRALL.EXE to decrease the amount of file handles used by Banyan's REDIRALL.EXE. Decrease file handles from 255 to 200 (200 representing the highest numbered file handle assigned by VINES). Ensure that the version of SETHAND works with the version of REDIRALL.EXE that you have.
3. The shell that is loaded last (REDIRALL.EXE or NETX.COM) will be the shell that will have the drive mapping for any given letter. For example: If you are using drive M: for a NetWare mapping and NETX.COM was loaded after REDIRALL.EXE, you cannot use Banyan's SETDRIVE to map drive M: to a Banyan drive.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Database Corruption on LAN Manager Server
DOCUMENT ID#: FYI.P.8843
DATE: 14SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Database corruption
ISSUE/PROBLEM
Configuration:
■Microsoft's LAN Manager 2.1 server
■NetWare v3.11 server
■ODINSUP.COM with a 3Com 3c503-16 TP card
■ODI driver 3c503.COM 04-27-92 v1.10
Database corruption occurred on the data files on the Microsoft LAN Manager server. Files residing on the NetWare v3.11 server did not get corrupted.
SOLUTION
Changing the workstation 3c503 cards to 8-bit mode solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Saber Menu Not Working on Some Connections
DOCUMENT ID#: FYI.P.8846
DATE: 14SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Saber menu not working
ISSUE/PROBLEM
NetWare v3.11 operating system (1000 user version)
The Saber Menu system works on all connections except 256, 512, and 768. The Saber menu would not show the name at the top of the screen on the above connections while all other connections worked. Also, it would not display menu options that needed NetWare groups defined to work.
SOLUTION
Saber Software Corp. found a bug in their Saber menu code that was using 00 for a test. Connections 256, 512, and 768 all have 00 in their least significant byte. Because Novell does not use connection zero, the Saber menu considered that this was not a NetWare network. Saber Software Corp. has a patch available to correct this problem. Their number is 800-338-8754.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Form 44 Mount Being Requester when Print Jobs Sent
DOCUMENT ID#: FYI.P.8787
DATE: 10SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Requesting a Form number 44
ISSUE/PROBLEM
None of the following conditions existed for a valid form mount request:
1. No print job configurations on the whole system.
2. No Job = in CAPTURE anywhere on file server or workstation.
3. Workstation had no RPRINTER that might be calling for a specific form mount.
4. Window 3.1 "Network--Options" setting had no form mount specified.
5. No other workstations with the same configuration were having this problem.
6. Problem existed only after going into Windows 3.1.
The only issue that appeared to remain was some type of corruption.
SOLUTION
Reinstalling Windows 3.1 solve the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Timing Problems with SMC PC-130 and Model 56, 57
DOCUMENT ID#: FYI.P.8777
DATE: 10SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.2, v3.11
SUPERSEDES: NA
SYMPTOM: Errors: "File server has no free connection slots" or "A File Server could not be found"
ISSUE/PROBLEM
While trying to set up a server and workstation with the PC-310 SMC card on the server and a PC-130 on the workstation, the system displayed the following message when the user tried to execute NETx.
┌────────────────────────────────────────┐
│File server has no free connection slots│
└────────────────────────────────────────┘
┌────────────────────────────────┐
│A File Server could not be found│
└────────────────────────────────┘
SOLUTION
SMC PC-310 cards and IBM 56 and 57 SLC machines have a timing problem. Standard Microsystems Corp. (SMC) says that this will be fixed in the next revision of the board. In the mean time, SMC will replace the board with a PS-110 board for any user with this problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The user was duplexing the 1740 Adaptec controllers and the second drive was chained to a tape drive. When backing up the drive that did not house the tape, the drive deactivated (HP 35450A). The user tried updating the ARCSERVE files, using the io_combine=1 setting, and a number of other things; however, the problem still existed.
SOLUTION
The user added a third 1740 controller and put the tape drive on it. Then the user loaded the adapter with the tape drive before loading the other adapters and could back up the drive.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to RPL - Old RPL Still in Memory
DOCUMENT ID#: FYI.P.8778
DATE: 10SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Cannot RPL
ISSUE/PROBLEM
The workstation could not do a Remote Program Load (RPL).
SOLUTION
The user discovered that even after unloading and reloading the RPL.NLM to fix the RPL problem, the old RPL still showed up in memory. After the user took down the server, brought it back up, and reloaded the RPL.NLM, the workstation can now attach.
The problem may have been caused from the user not flagging the RPL.NLM correctly and not copying the new file over the old file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Directory Restrictions Set after Mountain Restore
DOCUMENT ID#: FYI.P.8782
DATE: 10SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: File creation errors
ISSUE/PROBLEM
After doing a restore with Mountain Software v5.3 MT, directory restrictions are set beginning at the fifth level (or any level) of the directory structure.
When attempting to create a file, file creation errors are reported. When DOS DIR is executed it indicates that 0 bytes are free.
SOLUTION
In the past simply running DSPACE and setting directory restrictions= NO at the root of the volume was sufficient. However, in this case the user had to set directory restrictions at each level affected to solve the problem. Mountain Technical Support indicated that they are aware of the problem. They said that if the user does not select to restore bindery or trustee information, the DSPACE information is not adjusted.
Mountain is working to correct the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: 3C505 Driver Does Not Support Frame Types for ODISNUP in PS/2
DOCUMENT ID#: FYI.P.8769
DATE: 09SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Errors: "Macname=[] using first 3c505 mlid MLI 0213 unable to find named adapter" and "Macname=[] using first 3c505 mlid MLI 0211 insufficient frames supported"
ISSUE/PROBLEM
When the user tried to boot the workstation, the system displayed the following error message:
When the user swapped the device=C:\NetWare\odinsup.sys and the device=c:\NetWare\3c505.sys lines in the CONFIG.SYS, the system displayed the second error message:
The 3Com Corp. 3c505 driver does not yet support the four frame types that the user tried to load in the NET.CFG so the ODINSUP will work on the PS/2 machine. 3Com Corp. is currently working on a driver for it.
In this case, the user must go to a 3c503 card that has a driver that supports the frames.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Servers GPPE Writing to Disk - CPQDA386.DSK
DOCUMENT ID#: FYI.P.8768
DATE: 09SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: General Protection Processor Exception (GPPE)
ISSUE/PROBLEM
Configuration:
Four servers on an Ethernet backbone
The servers sent an ABEND GPPE at random intervals (such as 3 hours or 6 days). The servers always crashed in pairs; the second server sent the ABEND message a few minutes after the first server.
SOLUTION
Core dumps indicated the servers were always sending abend messages during write to disk process. The user had a CPQDA386.DSK v2.10 dated 03-06-91 (which is 4 days earlier than the certified version). After the user updated all disk drivers to v2.2 dated 05-29-92 (on NetWire), the server did not send any more abends.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: Invalid Request Returned NPutIOCTL - AHA1540.DSK
DOCUMENT ID#: FYI.P.8764
DATE: 08SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
If your machine auto-registers memory correctly on bootup or if you register memory above 16 MB before loading the Adaptec AHA1540.DSK date 07-26-91 or before, you will likely experience problems.
One frequently noted error message is:
┌─────────────────────────────────────────┐
│ABEND: Invalid request returned NPutIOCTL│
└─────────────────────────────────────────┘
Newer versions of Adaptec driver will resolve this issue; however, the following describes the issue and provides a workaround:
aha1540 <- --loads above 16 MB
SYS AHA1540.DSK loaded above 16 MB will not operate properly.
VOL1
VOL2
....
.
.
.
To avoid the above condition, Novell recommends the following:
1. Insert the following lines within STARTUP.NCF file:
set auto register memory above 16 megabytes = off
set <any other applicable set commands>
2. Create AUTOEXEC.NCF on the C: drive (or A: drive for booting from diskette) and use the following format:
file server name <server name>
ipx internal net <address>
load aha1540 above16=y port=330 int=b
register memory 1000000 <memory above 16 MB>
load <applicable NLMs>
set <applicable parameters>
The above procedure will force the AHA1540.DSK to load in memory below the 16 MB mark and still permit the volumes to mount at the 20 MB mark or whatever the top of memory is for the given server configuration.
SYS
VOL1
VOL2
....
aha1540 <────loads below 16 MB
.
.
.
Also check the "SET RESERVED BUFFERS BELOW 16 MEGABYTES=<xx>" parameter. The default is 16; however, for multiple devices, you may need to increase the number of buffers. Adaptec Inc. does not have a formula or guideline. If your server experiences abends, they said to increase the parameter.
Users have asked if they could leave the "load aha1540 ...." statement in the STARTUP.NCF rather than moving it to the AUTOEXEC.NCF. The answer is that it is much safer to move all "load <drivername> <parameters>" statements to AUTOEXEC.NCF. The reason is that if a driver that is loaded in STARTUP.NCF is responsible for the controller or HBA that has the SYS: device attached, then the SYS: volume will mount implicitly.
This principle is paramount whenever a user is moving the AUTOEXEC.NCF to C: drive. The reason is if SYS: mounts, implicitly or otherwise, before the REGISTER MEMORY command is executed, then the FATs and DETs for all volumes will mount below the 16 MB mark.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "File Server Could Not Be Found" - Requester, SMC, and TC NICs
DOCUMENT ID#: FYI.P.8762
DATE: 08SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "A file server could not be found"
ISSUE/PROBLEM
When in the OS/2 full screen session, the workstation attaches to the server. When in a DOS full screen session, the workstation gets the following error when loading NETX:
┌────────────────────────────────┐
│A file server could not be found│
└────────────────────────────────┘
The system displays the same error with global support selected (loading VSHELL in CONFIG.SYS and not NETX). The workstation came up fine in all screens with the Thomas-Conrad's 6245 NIC, but the above problems cropped up with the 6145 NIC and SMC's PC110. In all cases, the 2/92 TRXNET.SYS driver that shipped with the requester was used.
SOLUTION
Switching from interrupt line 2 to 3 and from I/O 2E0h to 300h on the 6145 NIC and the SMC PC110 solved the problem. According to Standard Microsystems Corp. interrupt lines 2 and 9 and I/O 2E0h are known to conflict with VGA cards.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE Running Support Magic Program
DOCUMENT ID#: FYI.P.8751
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: General Protection Processor Exception (GPPE)
ISSUE/PROBLEM
The user's system received a GPPE.
SOLUTION
The user was running an application known as Support Magic. This application is a desktop management package that runs from the server (it is not an NLM). The software makes calls to BTRIEVE. Magic Solutions Inc. said that the software can cause a server to GPPE when it makes certain calls and that they are working on a solution.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Everex Machines GPPE when Used with DMA Controllers
DOCUMENT ID#: FYI.P.8759
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Errors: "General Protection Processor Exception (GPPE)" or "Drive deactivated due to drive failure"
ISSUE/PROBLEM
Configuration:
Everex Step 386 file server
When used in conjunction with DMA disk controllers, a certain batch of these machines produces the following errors:
┌─────────────────────────────────────────────┐
│General Protection Processor Exception (GPPE)│
└─────────────────────────────────────────────┘
┌──────────────────────────────────────┐
│Drive deactivated due to drive failure│
└──────────────────────────────────────┘
SOLUTION
Everex Systems Inc. has a BIOS upgrade that fixes this problem and is available through their technical support.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: High Utilization on HP Vectra - Easyconfig
DOCUMENT ID#: FYI.P.8760
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: High utilization on HP Vectra 486/25 (90 to 95 percent)
ISSUE/PROBLEM
After a lighting strike and power outage that had caused damage to their Hewlett-Packard Vectra 486/25, the user replaced their Ethernet LAN board and had added 16 more megabytes to a total of 32 MB. Then their utilization jumped from 40 to 95 percent or more. All the LAN statistics were fine. Because the user had 3.8 MB free, they ran PURGE. As a result, the utilization went down to 85 percent but continued to be at 95 percent.
SOLUTION
When Hewlett-Packard ran a diagnostic on the user's system, they checked the Easyconfig and discovered that the system speed had changed from Fast to Auto. When the user set the system's speed to Fast and saved the configuration, the utilization went down to 40 percent and has stayed there.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cannot Log in or Use .EXE Utilities after Swapping Memory
DOCUMENT ID#: FYI.P.8748
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: The workstation appears to lock when running LOGIN or SLIST.
ISSUE/PROBLEM
After swapping a memory card in the file server, the user was unable to log in or use any .EXE utilities from the file server. The workstation seemed to lock. When copying a file up to the server and back to the workstation, the user found the file had changed in the process.
SOLUTION
After swapping the old memory card back into the file server, the user noticed that the memory on the new card had different speeds than the other memory on the motherboard.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Data Overrun during 82588 Configuration" IBM Education
DOCUMENT ID#: FYI.P.8757
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: Error: "Data overrun during 82588 configuration"
ISSUE/PROBLEM
IBM is sending out something called Education Bundles, which include Model 35, 40sx, 35sx, 55, 56, or 57 PS/2s loaded with DOS v5.0 and Windows v3.1. The following error would come while executing IPX at a workstation:
┌───────────────────────────────────────┐
│Data overrun during 82588 configuration│
└───────────────────────────────────────┘
SOLUTION
The user said that several sites with these "bundles" that seemed to have just the software loaded, but not really configured properly. After investigation, the user found memory manager conflicts with Windows drivers. Removing EMM386.EXE from the CONFIG.SYS allowed the PCN II card to initialize just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Windows Hangs when Loading IPX.COM - SiteLock
DOCUMENT ID#: FYI.P.8715
DATE: 03SEP92
PRODUCT: NetWare
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: Windows 3.1 hangs when loading at the workstation.
ISSUE/PROBLEM
After the user upgraded from IPX v3.02 to v3.10, the workstation hung. The user updated the Window drivers with WINUP6.ZIP with no success.
SOLUTION
When the user quit loading high SiteLock v3.20, the problem went away. SiteLock had loaded high sucessfully with IPX v3.02.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Problems Printing with CAPTURE Loaded in Private VDM
DOCUMENT ID#: FYI.P.8719
DATE: 02SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.15c, v2.2, v3.x
SUPERSEDES: NA
SYMPTOM: Error: "Trap E"
ISSUE/PROBLEM
Configuration:
■SMC ELITE 16 Plus card
■Running under OS/2 v2.0
Printing with CAPTURE loaded in a PRIVATE Virtual DOS Machine (VDM) session displays the following error:
┌──────┐
│Trap E│
└──────┘
SOLUTION
The newest driver for SMC Elite 16 for OS/2 2.0 is on CompuServe SMC forum. The file name is NOR210.EXE, and the file is self-extracting with the driver SMC8000.SYS dated 07-16-92. The user originally had the OS/2 1.3 SMCPLUS.SYS driver dated 10-08-91. Switching to the new driver cleared up the error.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Compaq Hardware Mirroring and Bad Drives
DOCUMENT ID#: FYI.P.8729
DATE: 02SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Compaq's hardware mirroring (not data guarding) with an IDA controller
ISSUE/PROBLEM
A user was using Compaq's hardware mirroring under a NetWare v3.11 operating system and one of the drives died. The user shut down the system to do some maintenance on it. When the user tried to reboot the server, it would not come up and displayed a message about having problems with the hardware mirroring. Unplugging power to the faulty drive did not help.
SOLUTION
When the user replaced the faulty drive, everything came up fine. COMPAQ Computer Corp. told the user that when a mirrored drive goes bad, the system will continue to function. However, when the server is shut down, it must be replaced or it cannot be brought back up. There is no way to disable the hardware mirroring once it has been established unless you start all over and have a good backup.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Log in -- DOS Partition Set at F: Drive
DOCUMENT ID#: FYI.P.8723
DATE: 02SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Workstation cannot log into the server. No files are in F: drive.
ISSUE/PROBLEM
They had a NetWare v3.11 network with several workstations that could attach and log into the server fine; however one workstation could not log into the server. At the server, the user could see that the station was attached, but if the user typed F:login, the system displayed the following error:
┌──────────────┐
│File not found│
└──────────────┘
If the user changed to F: drive and did a DIR, no files were in the directory. The user executed LOGIN from a diskette and the workstation logged into the network, but it attached to the H: drive instead of the F: drive. A DOS lastdrive statement was not in the CONFIG.SYS file.
SOLUTION
The user was using DOS 3.3 and had set up DOS drive partitions D:, E:, F:, and G:, so the first available drive for the network was H: drive. When the user changed the AUTOEXEC.BAT file to run NETX and go to H: drive, the user could log into the network fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: DeleteFileToLimbo Found an Invalid Tnode
DOCUMENT ID#: FYI.P.8724
DATE: 02SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "ABEND: DeleteFileToLimbo found an invalid Tnode"
ISSUE/PROBLEM
Within 24 hours after the server was installed on site, the system displayed the following error:
┌───────────────────────────────────────────────┐
│ABEND: DeleteFileToLimbo found an invalid Tnode│
└───────────────────────────────────────────────┘
The user tried VREPAIR and selected the option to purge all deleted files, but the abend continued to occur. Then the user tried deleting and recreating the volume but could never get the volume to mount. Then when the user deleted the NetWare partition, the DOS partition strangely disappeared also. Then the user ran FDISK on the drive, and it returned the following error:
┌───────────────────────────┐
│invalid drive specification│
└───────────────────────────┘
SOLUTION
The user determined that the Hewlett-Packard drive in their new Hewlett-Packard 486/50u file server had failed. Replacing the hard drive with another Hewlett-Packard drive solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Register Memory Will Not Load in AUTOEXEC.NCF - Micro Design
DOCUMENT ID#: FYI.P.8708
DATE: 01SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Register Memory will not load in AUTOEXEC.NCF
ISSUE/PROBLEM
Configuration:
■EISA 486/50
■64 MB RAM
■VGA monitor
■Two - Mylex LNE390
■Two - AMI EISA fast SCSI controllers
■Four - 1.2 GB drives (two off each controller)
When loading the server, the AUTOEXEC.NCF would not execute the REGISTER MEMORY XXXXXXX XXXXXXX command even though it could be executed from the console. When the user checked the STARTUP.NCF, which loaded the disk drivers, and the AUTOEXEC.NCF, both files looked fine. The user also checked speed and brand of RAM and disabled all caching; however, the problem still existed.
SOLUTION
In the STARTUP.NCF, the user was loading a driver for the controller to emulate an ADAPTEC controller. The driver was written by Micro Design International Inc. This driver does not recognize RAM above 16 MB. When the user removed this driver, the server now recognizes all 64 MB of RAM.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: NMI Parity Error... - Symphony Chip Set
DOCUMENT ID#: FYI.P.8712
DATE: 01SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "ABEND: NMI parity error generated by system board"
ISSUE/PROBLEM
Configuration:
Fountain 486-33 ISA machine with Symphony chip set,
■16 MB of RAM
■Two Adaptec 1542b controllers (revisions E and F)
■Two SMC Elite combination cards
■Three Micropolis 1.5 GB hard drives
■Newest drivers from Standard Microsystems Corp. (SMC) and Adaptec
Everything worked fine (for months) until the user tried to duplex the drives. The following abend would be generated anywhere between 2 minutes and 24 hours after duplexing the drives.
Novell suggested disabling both internal and external processor caches, disabling all shadow RAM/ROM. Apparently the Fountain motherboard does not allow disabling BIOS shadowing. When the user replaced the motherboard with a Fountain 486-33 ISA with an International chip set, the problem went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NCR BIOS v2.09 Will Not Support over 1 GB
DOCUMENT ID#: FYI.P.8713
DATE: 01SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Volume over 1 GB only has 64 directory entries
ISSUE/PROBLEM
Configuration:
■NCR PC486 MC25 Micro Channel machine
■NCR 53C90 controller
■One Conner 300 MB drive using 1C90.DSK
■20 MB of RAM
When they added a second 1.7 GB Maxtor po175 drive the last volume only had 64 directory entries available. After they had used the 64 directory entries, no more entries were allocated by the operating system.
SOLUTION
If the NCR PC486 has a BIOS of 2.09 or lower, it will not support drives over 1 GB. The user needs to contact NCR for an upgraded BIOS (800)241-8255. In this case, the user needed to ask for FRO 17-fro-3577 and part 603-5015204.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Oracle NLM, RDBMS, and Procedural Lanquage/SQL
DOCUMENT ID#: FYI.P.4594
DATE: 07NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: PL/SQL is not releasing memory
ISSUE/PROBLEM
Configuration:
■Oracle NLM,
■RDBMS v6.0.33.0.2
■PL/SQL
If users are using the Oracle NLM and a version of RDBMS earlier than v6.0.33.0.2 and Procedural Language/Structured Query Language (PL/SQL), they may come across problems with PL/SQL not releasing memory.
Specifically, along with the functionality of SQL, developers are able to develop scripts that do procedural functions such as branching and looping.
The Oracle NLM that has been certified by Novell began shipping May 01, 1992.
Oracle Corp. said that about 5,000 Oracle NLMs have been sold to date. Please have users upgrade to this version of Oracle. You can reach Oracle at (415) 506-7000.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Windows Enhanced Mode Issue with TC 3045ST Card
DOCUMENT ID#: FYI.P.4595
DATE: 07NOV91
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The user could not get Windows 3.0 to work in the Enhanced mode with a Thomas-Conrad 3045ST. The machine worked fine in the Real mode and in Enhanced stand-alone but not on the network. The user's workstation always locked or received Network abort errors.
ISSUE/PROBLEM
Configuration:
■Workstation 386 33 clone
■Thomas-Conrad 3045st card
The user checked for the usual problems such as interrupt line and memory conflicts but nothing seemed to be wrong.
SOLUTION
Thomas-Conrad Corp. support told the user to insert the following line into the SYSTEM.INI file:
emmexclude= CC00-CFFF
This entry in that file solved his problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Patch for Intel SnapIn 386
DOCUMENT ID#: FYI.P.4561
DATE: 05NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Intel produces a 80386 processor board that will "snap into" a 286 machine. However, NetWare v3.x still recognizes the machine as a 80286 CPU.
SOLUTION
Novell has written a patch to be applied to SERVER.EXE. Intel's documentation refers to it as the NetWare 386 Bit 20 Patch.
XLOAD.EXE is the program that applies the patch. The patch name itself is called LDR001.PTF.
LDR001.PTF is the first of what may be a series of patches to the LOADER portion of SERVER.EXE. When additional patches come out they will be named with a sequential number.
This patch has been renamed to XLOAD.ZIP and is available on NetWire and NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "162 Option Error" Advanced NetWare v2.0a
DOCUMENT ID#: FYI.P.4554
DATE: 05NOV91
PRODUCT: NetWare
PRODUCT VERSION: v2.0a
SUPERSEDES: NA
SYMPTOM:
The user's old system on Compaq 386 DeskPro had been fine for years. One day when the user rebooted the machine, it displayed the following error and then hung:
┌───────────────────┐
│162 option error...│
└───────────────────┘
ISSUE/PROBLEM
The drive type field in the CMOS was blank.
SOLUTION
When the user selected the drive type again, type 1, the file server booted just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Model 80 Server Hangs Running DISKSET
DOCUMENT ID#: FYI.P.4370
DATE: 16OCT91
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
DISKSET would not recognize the ADIC N330 disk subsystem. When the user ran MDISKSET supplied by ADIC with their subsystem, the Model 80 hung.
ISSUE/PROBLEM
Advanced Digital Information Corp. (ADIC) technical support indicated the symptom is caused from a common timing problem with their product and the IBM model 80 units produced before January of last year and that IBM is aware of the problem.
SOLUTION
Contact IBM.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE after NetWare v2.2 Upgrade to NetWare v3.11 Operating System
DOCUMENT ID#: FYI.P.4371
DATE: 16OCT91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
After the user upgraded from a NetWare v2.x to v3.11 operating system, the system kept receiving GPPE messages.
ISSUE/PROBLEM
Configuration:
■Proteon p1990 NIC
■Mylex controller
■Northgate elegance 486 433e
■Older .LAN and .DSK (DCE31.DSK dated 02-7-91)
The user only had 1 MB RAM on the controller.
SOLUTION
Increasing the RAM to 4 MB and updating the .LAN and .DSK drivers with the newest version available for the NetWare v3.11 operating system solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Mirror Copies of Volume Dir Don't Match" - Ontrack
DOCUMENT ID#: FYI.P.4291
DATE: 09OCT91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user had extremely sensitive data stored on a file server in Kuwait. Thinking something was wrong, the user turned off the power to the server. After powering the machine back up, the system displayed the following error message:
┌───────────────────────────────────────┐
│Mirror copies of volume dir don't match│
└───────────────────────────────────────┘
ISSUE/PROBLEM
The Novell technician told the user to run VREPAIR because it fixes this problem 99 percent of the time. The user did not want take the 1 percent risk of running VREPAIR.
SOLUTION
The user flew a team from Ontrack to Kuwait and they successfully recovered 100 percent of the data.
Ontrack's data recovery phone numbers are the following:
USA 1-800-872-2599
International 1-612-937-5161
FAX 1-612-937-5750
Ontrack has two offices in the U.S. and one in Europe.
Ontrack London office
Phone: 44-81-549-3444
Fax: 44-81-546-6642
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: High Utilization with PWRCHUTE.NLM
DOCUMENT ID#: FYI.P.4238
DATE: 07OCT91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user was backing up a 32 MB workstation hard drive to the network, using XCOPY. The hard drive had 939 files. The XCOPY took 21 minutes to complete and utilization on file server climbed to over 90 percent.
ISSUE/PROBLEM
Powerchute NLM v3.0 was loaded.
SOLUTION
The user had a newer version of Powerchute to try (v3.13). After installing this new version, XCOPY flew with the utilization expected.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When the user replaced the PC-500 with a PC130 using Novell's TRXNET driver, the abend went away. The user also used the SET command to disable the lost hardware interrupt message, and now the system works fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Established Connection Failed", Short in Patch Cable
DOCUMENT ID#: FYI.P.5163
DATE: 10JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The system displayed the following error:
┌─────────────────────────────┐
│Established connection failed│
└─────────────────────────────┘
The error seemed to happen only when the user was using RCONSOLE.
ISSUE/PROBLEM
Configuration:
■IPX v3.01e
■IBMs NetBIOS
There was a short in the patch cable from the file server to the Multi-Station Access Unit (MSAU).
SOLUTION
Replacing the cable solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: CTRL and ALT Keys Sticking, WordPerfect Office
DOCUMENT ID#: FYI.P.5166
DATE: 10JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The workstation's keyboard CTRL and ALT keys are sticking with WordPerfect and in DOS.
ISSUE/PROBLEM
The user was using WordPerfect Office to shell out to DOS.
The problem will occur in workstation's with LAN cards set to use interrupt line 2 (which cascades to interrupt line 9).
SOLUTION
User's with this problem need to download KBFIX.ZIP from WordPerfect's BBS. It redirects WordPerfect from using interrupt line 9 that is causing the problem with clone machines and others.
The WordPerfect BBS numbers are the following:
(801) 225-4414 for 2400 baud
(801) 225-4444 for 9600 baud
If the user has WordPerfect v5.1 with an Interim date of 03-09-92, loading WordPerfect with the /ND parameter (WP /ND) will have the same effect as the above mentioned keyboard fix.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM Memory Expansion Board Not Finding Memory
DOCUMENT ID#: FYI.P.5154
DATE: 09JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.1x, v3.11
SUPERSEDES: NA
SYMPTOM:
The user was upgrading the machine from a NetWare v2.x to v3.11 operating system. After installing NetWare v3.11 software, the user noticed that only 4 MB of memory was registered at bootup and that the 4 MB IBM-memory expansion board was not registering its memory.
ISSUE/PROBLEM
The IBM-memory expansion board has software that straps itself to the cold boot loader. NetWare v2.x software needs a patch so that the bootstrap would not trample over Novell's operating system.
SOLUTION
Now that the user is running a NetWare v3.11 operating system with a DOS partition, he only needs to reinstall the bootstrap software on the track zero where DOS is, then the machine will recognize all 8 MB of memory.
After the user reinstalled the bootstrap software, the machine registered all 8 MB of memory.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: WD Ethercard Plus Problems in IBM Model 50z
DOCUMENT ID#: FYI.P.5156
DATE: 09JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15c, v2.2
SUPERSEDES: NA
SYMPTOM:
When trying to load NET3 or NET5 on an IBM Model 50z and using a Western Digital EtherCard Plus adapter, the system displayed the following message:
┌────────────────────────────────┐
│A File Server could not be found│
└────────────────────────────────┘
The driver appeared to load fine when the user executed IPX. The system also worked fine when the user tried using the Western Digital card on a Model 70.
ISSUE/PROBLEM
Standard Microsystems Corp. (SMC) said that there was a known bug using the Western Digital EtherCard Plus with the Model 50z machines.
SOLUTION
SMC has written a new driver for users with the Model 50z machines.
The driver is available in N21400.EXE on CompuServe. Locate the file by typing GO SMC and going into Library 2.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The server stopped and sent the following message:
┌─────────────────────────────────────────────┐
│ABEND: NMI (parity error) processor exception│
└─────────────────────────────────────────────┘
When the server was rebooted, volume SYS: would not mount and the system displayed the following error:
┌───────────────────────────────────────────────┐
│Some or all volume segments can not be located.│
└───────────────────────────────────────────────┘
VREPAIR could not recognize volume SYS: either.
In INSTALL under "Partition Tables" option, both partition 0 and partition 1 (from the primary controller) shown as expected. Partition 2 shown the following error:
┌─────────────────────────────┐
│Error reading partition table│
└─────────────────────────────┘
Partition 3 did not show up at all (partitions 2 and 3 are on the drives on the secondary controller).
ISSUE/PROBLEM
Configuration:
The file server had duplexed two DCE376 SCSI caching controllers.
Each controller had two 1.2 GB drives.
Further testing of the original secondary controller showed that the parity error was caused by memory failure on the controller.
SOLUTION
The user ended up using Ontrack's Data Recovery to recover the data and replacing the secondary controller.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Slow Printing and Printing Garbage with Harvard Graphics
DOCUMENT ID#: FYI.P.5149
DATE: 08JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Printing slow and outputting garbage
ISSUE/PROBLEM
Configuration:
The PaintJet was set up in parallel mode.
When the user used Harvard Graphics with a Hewlett-Packard PaintJet printer, it printed slowly and the output printed was garbage.
SOLUTION
Using the newest PSERVER.NLM (07-10-91) solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Jerusalem B Virus Causing "Error Receiving from Network.."
DOCUMENT ID#: FYI.P.5146
DATE: 08JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When any user tried to log into the network, they started to get in; then during the execution of the System login script, the following error displayed:
After the error displayed the user was locked out of the system and no one could log into the network.
ISSUE/PROBLEM
When the user logged in with an alternative script "login /s" and got into the network, some files and all their date stamps, including NET$LOG.DAT, were changed. Using NetScan on the network, the user discovered the Jerusalem B virus.
SOLUTION
Cleaning the virus off the network and restoring clean files to the network solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When the user loaded NE2000.LAN at the server by loading the NE2000, entering the I/O, and then entering the interrupt line, the following error displayed:
When the user swapped card several times, the same result occurred.
ISSUE/PROBLEM
Configuration:
NE2000T NIC for 10BaseT
The sever was running too fast for the network interface card.
SOLUTION
Slowing down the file server (an Everex 386/25) solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "GPPE: Error Code 0014 0000 Running Process Initialization"
DOCUMENT ID#: FYI.P.5119
DATE: 07JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user was trying to set up a NetWare v3.11 system on an ALR Business VEISA 486/33 with 16 MB of RAM. After booting the machine and typing SERVER, the machine displayed the following error:
On the second screen of the machine setup, the option "Maximum RAM Size" defaults to a "No Limit" setting.
SOLUTION
Changing this setting to "16-MB Limit" and rebooting the machine allowed the RAM to count to 15460, which is 16 MB less 640 KB, and the server to boot fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Initializing LAN Driver: Server Will Be Shut Down
DOCUMENT ID#: FYI.P.5131
DATE: 07JAN92
PRODUCT: NetWare
PRODUCT VERSION: ELS II v2.15
SUPERSEDES: NA
SYMPTOM:
When the user brought the file server up, it displayed the following message:
The server had been moved and one of the connectors on the cable running into the server was damaged.
SOLUTION
After the user replaced the cable, the server came up fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Print Server Giving Off-Line Status - Loose Cable
DOCUMENT ID#: FYI.P.5130
DATE: 07JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
Whenever a print job was sent to the queue, the print-server console screen flashed a "printer off-line" status.
ISSUE/PROBLEM
Configuration:
On a NetWare v3.11 system:
■RPRINTER.EXE v1.21
■PSERVER.NLM v1.21b
■Printer connected to LPT1
The printer cable was loose.
SOLUTION
After the user tightened the cable, printing worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: New Stealth Feature in QEMM v6.x
DOCUMENT ID#: FYI.P.5122
DATE: 07JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
QEMM v6.x has a feature called a Stealth feature. The user could not get it to work with remote boot. The workstation would lock up during remote boot when using the Stealth feature.
ISSUE/PROBLEM
The Stealth mode redirects the system BIOS areas in the 640 to 1024 KB area to other memory regions within that area. The purpose of this is as follows:
If you have two ROM regions at 700 KB and 800 KB that are each 1 KB in size, you have three memory regions into which you can fit programs. These sizes would be 140 KB, 99 KB, and 224 KB. However, if you could relocate both of those ROM areas to 641 KB and 642 KB, then you would have only one memory region that was 382 KB big. It is a great idea, but some machines have a really bad time with it.
SOLUTION
To prevent the use of the Stealth mode feature, take out the ST:M on the device=Qemm line in the CONFIG.SYS file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE using ADIC EISA DCB/DRIVER and AST Machines
DOCUMENT ID#: FYI.P.5129
DATE: 07JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
After the user installed the NetWare v3.11 operating system on an AST 386 Tower EISA machine, the system displayed a General Protection Processor Exception (GPPE) message.
ISSUE/PROBLEM
Advanced Digital Information Corp. (ADIC) said that the user was using the wrong driver for this Disk Coprocessor Board. The user was using VTXNW31.DSK and should have been using BTXNW31.DSK from BusTek. ADIC also told the user that there was a known problem with AST EISA machines and any revision of the DCB before revision G.
SOLUTION
When the user swapped the DCB with a new revision G (they had
revision D), everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "IPX Received an Incomplete Packet"
DOCUMENT ID#: FYI.P.5107
DATE: 06JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user logged into a NetWare v3.11 server from PS/2 Model 30/286 with a Thomas-Conrad 6045 Arcnet card, the following error displayed on the file server:
┌─────────────────────────────────┐
│IPX received an Incomplete Packet│
└─────────────────────────────────┘
ISSUE/PROBLEM
The Thomas-Conrad 6045 does not take into account any type of error correction for the irregular bus speeds of the PS2 Model 30/286.
SOLUTION
Upgrade to a Thomas-Conrad 6145 or 6245 card.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Network Device Fault Reading Drive"
DOCUMENT ID#: FYI.P.5105
DATE: 06JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user upgraded from a NetWare v2.15 to v3.11 operating system using Hong Technologies NIC on the workstation. When the user went into WordPerfect 5.1, the following error displayed sometimes:
┌──────────────────────────────────┐
│Network Device Fault Reading Drive│
└──────────────────────────────────┘
The error displayed most of the time when the user went into WordPerfect, then left it for 1/2 hour or so. When the user came back, the error would be on the screen.
ISSUE/PROBLEM
The above error is a WordPerfect error that usually means there is some kind of network communication problem.
SOLUTION
When the user swapped the Hong Technologies network card for a CNet card, the error disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "No Future Domain SCSI Drives Found"
DOCUMENT ID#: FYI.P.5111
DATE: 06JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM:
During the installation of the operating system, the following message came up and the server hung:
┌──────────────────────────────────┐
│No Future Domain SCSI drives found│
└──────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
■Future Domain 871 SCSI controller
■Conner CP-3360 drive
■Future Domain disk driver v1.3
Using the Future Domain disk driver v1.3 made the machine unable to recognize any SCSI drives connected to the server.
SOLUTION
Future Domain supplied the user a new disk driver (v2.11) that solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "No Host Bus Adapter Found" - CSS Research Labs 486
DOCUMENT ID#: FYI.P.5117
DATE: 06JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user loaded an AHA1740 driver on CSS Research Laboratories 486/33 machine, the system displayed the following message:
The error message displayed with or without using the IO_COMBINE parameter.
The user used an AHA1540 driver, it loaded fine. However, after a volume was created the user could not see it when attempting to modify it. The system displayed a message that read something to the effect of the following:
Could not find a volume on the partition
ISSUE/PROBLEM
The controller was faulty.
SOLUTION
After changing to a BusTek controller, the user was able to create and modify the volume.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Mirrored copies of the FAT don't match"
DOCUMENT ID#: FYI.P.5087
DATE: 02JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The system displayed the following message:
┌──────────────────────────────────────┐
│Mirrored copies of the FAT don't match│
└──────────────────────────────────────┘
When the user issued the SLIST command, the system displayed the following message on most of the 161 file servers in the network:
┌──────────────────────┐
│Unable to read address│
└──────────────────────┘
ISSUE/PROBLEM
Configuration:
■Compaq SystemPro 486/33
■Two Mylex DCE376 controllers
When the user initially set up the SystemPro using EISA CONFIGURATION, the Mylex controllers were set to different caching sizes.
SOLUTION
When the user set the controllers up to the same caching size, the problems disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Future Domain said that they have seen this problem with a "phantom" parallel port or a bad parallel port.
One FD 860 was set at interrupt line 5 (which is usually used by LPT2).
SOLUTION
When the user switched the interrupt setting from interrupt line 5 to 15, the error disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: CSMS Software Problems on Model 35
DOCUMENT ID#: FYI.P.5304
DATE: 23JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The combination of running CSMS software on a Model 35 produced an extremely slow keyboard response. The user checked for the usual causes such as serial number problems, shell, drivers, and ECA085 patches from IBM.
ISSUE/PROBLEM
The user compared the setup to an identical setup at another site that was not having the problem. The only difference was that he was running DOS v3.3 and the other site was running DOS v5.0.
SOLUTION
When the user upgraded to 5.0, the problem went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Grounding Problems Stopped the Network
DOCUMENT ID#: FYI.P.5299
DATE: 23JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The user had one particular office that had a 386 machine in it. No matter what machine was plugged into the network in that room, the rest of the network went down. If the user connected the cable from the workstation to the cabling, it caused the rest of the network to go down also.
ISSUE/PROBLEM
The power outlet was faulty.
SOLUTION
When the user ran an extension cord to the same outlet in another room where the machines worked fine, no crashes occurred.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Dell Computer Corp. told the user that this machine has a problem with the Intel 486 chip handling interrupts properly. Dell made a hardware change at the controller to latch the interrupt line high to circumvent the problem.
SOLUTION
Using the "set display lost interrupt alerts: off" parameter allowed the user to mount the volumes.
Using this new controller will solve the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TRUST.ZIP Lists DIRs in Volume with Trustee
DOCUMENT ID#: FYI.P.5296
DATE: 23JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Is there a product that will generate a listing of all the directories and subdirectories in a Novell volume and all of their associated trustee assignments?
SOLUTION
The file TRUST.ZIP available on NetWire will to do the requested function.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Loading Three Proteon Token-Ring Cards in Server
DOCUMENT ID#: FYI.P.5310
DATE: 23JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to load three Token-Ring cards
ISSUE/PROBLEM
The user was trying to load three Proteon Token-Ring cards and an SMC Ethernet card in a NetWare v3.11 server. Page 139 of the NetWare Version 3.11 System Administration manual reads as shown below:
Proteon Inc. said that it is possible to load three cards by doing the following:
1. Load the first two cards with the newer driver (3NW39XR.LAN v1.09)
2. Load the third card with the older driver (NWR-139x.LAN v2.03).
The user was able to get all cards loaded by following Proteon's instructions.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abends Occur Due to Faulty Core Disk Drive
DOCUMENT ID#: FYI.P.5273
DATE: 21JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
After the server was installed and running for two weeks, the following ABEND messages began displaying:
The volume SYS: would not mount. The card was fine but it could not access the disk.
ISSUE/PROBLEM
The core disk drive was faulty.
SOLUTION
The user had to replace the disk drive.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NMI Parity Error with Techmar Proserv Backup
DOCUMENT ID#: FYI.P.5276
DATE: 21JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user attempted to backup through the tape unit, the server received the following error:
┌─────────────────┐
│NMI Parity Error.│
└─────────────────┘
ISSUE/PROBLEM
Configuration:
■Techmar Proserv tape backup unit attached to a HP Vectra 486/33 file server
The tape unit was connected to a AHA1540 SCSI controller that came with the unit.
SOLUTION
At the suggestion of Cheyenne, the user removed the AHA1540 controller card and attached the tape unit to the AHA1740 disk controller. Now the backup unit is running fine without any NMI parity errors.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: No Free Connections with 3C503
DOCUMENT ID#: FYI.P.5278
DATE: 21JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "No free connections"
The user generated a nondedicated server with a 3C503 as the LAN card. The user could log in from server/workstation, but other workstations received the following error when trying to log into the system:
┌───────────────────┐
│No free connections│
└───────────────────┘
ISSUE/PROBLEM
The 3C503 card was probably faulty.
SOLUTION
When the user put in an NE2000 card, the problem disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "... Send Failure in Advertiser" - Btrieve v5.0
DOCUMENT ID#: FYI.P.5261
DATE: 20JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM:
The user's system occasionally received the following error:
┌──────────────────────────────┐
│... Send failure in advertiser│
└──────────────────────────────┘
ISSUE/PROBLEM
The user thought the error was Btrieve related. The user had recently installed two Tiara 10BaseT NICs in an existing server that had an IBM Token-Ring card. The user mentioned that they were not entirely setup the way they wanted to be and that one of the Tiara cards was not being used but soon would be.
SOLUTION
The user cabled in the unused card. When they connected the cable the, entire system began to work faster and they have not seen the error for 4 days.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "FAT Update Process Could Not Find..." - PSI Controller
DOCUMENT ID#: FYI.P.5260
DATE: 20JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user was upgraded from NetWare v3.10 to v3.11 software, something did not work. The user went back to v3.10 and had to run VREPAIR. It failed with the following error:
┌────────────────────────────────────────────┐
│FAT update process could not find dirty bit.│
└────────────────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
PSI controller (supposed to be Western Digital compatible)
The PSC driver that the user was using was a beta v2.48.
SOLUTION
PSI Integration Inc. gave the user a new driver, v2.46. After installing the new driver and executing VREPAIR, the system worked fine the first time and everything is okay.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MarxMenu and Nondedicated NetWare v2.2 Operating System
DOCUMENT ID#: FYI.P.5254
DATE: 17JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
A user called with a problem on the nondedicated server. They ran a menu called MarxMenu on the DOS side of the server and left it running over night. This menu has a screen saver that is a box that moves around the screen. When the user came in the next morning, the monitor on the server was blank and the user could not use the server or DOS side of the nondedicated server. However, the user could use the server from a workstation.
ISSUE/PROBLEM
After going through all the hardware, the user finally started looking at this menu. After talking to Computer Tyme Inc., the user discovered that an early version of the MarxMenu would use 200 bytes of memory every time the box on the screen saver moved. Eventually, the complete memory on the server would be used and never released and the screen would go blank. Computer Tyme was not sure which version number caused the problem but they thought it was between v2.22 and v2.27.
SOLUTION
When the user installed the newest version, it worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Corrupt SETVER.EXE Problems on PS/2 Machines
DOCUMENT ID#: FYI.P.5252
DATE: 17JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
A PS/2 workstation suddenly stopped booting from the C: drive. The user accessed the drive when booting up the workstation and then it hung. The user scanned for viruses and did not find any on the drive or diskettes from which they were booting.
ISSUE/PROBLEM
The user had a corrupt SETVER.EXE on the DOS 5.0 diskettes and had used the same copy on all the machines.
SOLUTION
When the user replaced the SETVER.EXE from another copy of DOS, it worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE on Gateway 2000, Faulty Motherboard
DOCUMENT ID#: FYI.P.5245
DATE: 17JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user said if the machine's speed was set to "high" a GPPE occurred after about 20 minutes of being up. If the speed was lowered to the low speed, the server would continue to operate.
ISSUE/PROBLEM
Configuration:
Running a NetWare v3.11 operating system on a Gateway 2000 file server
The motherboard on the server was faulty.
SOLUTION
When the motherboard was replaced, the server no longer gave the GPPE error.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "System Message File SYS$MSG.DAT Is the Wrong..."
DOCUMENT ID#: FYI.P.5248
DATE: 17JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The user used the UPLOAD utility to run INSTALL from the hard drive. The install was running fine until the linking and configuring process within Install. At that point, the system displayed the following error:
This was a fresh install and no other NetWare existed in the building.
ISSUE/PROBLEM
The user checked the file size and contents of the SYS$MSG.DAT against the diskette listing and did a DOS "compare" against the file in the working diskettes. No discrepancies were found.
The user had a corrupt SYS$MSG.DAT file.
SOLUTION
After receiving a clean SYS$MSG.DAT file, the Install went just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Stoned Virus and Diskless Workstations Using DOSGEN
DOCUMENT ID#: FYI.P.5247
DATE: 17JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The user needed to have more open files and file handles, so they modified the CONFIG.SYS and SHELL.CFG and reran DOSGEN. It started out fine but weird things started happening as the DOSGEN process went on. ASCII characters started showing up on the screen and DOSGEN indicated that it was processing some files in a directory that did not exist. DOSGEN created the NET$DOS.SYS file, but when the diskless workstations try to boot, they hung. The user could use that diskette to boot up a workstation with a floppy drive.
ISSUE/PROBLEM
It turns out that they had the Stone virus on the machine from which they were running DOSGEN.
SOLUTION
When they cleaned the hard disk, reformatted the diskette, and reran DOSGEN, the problem disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When the user replaced the hub, the error disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
■Mylex DCE376 SCSI caching controller with 4MB of RAM
■Seagate 1.2 GB drive
SOLUTION
Novell instructed the user to switch out the memory on the Mylex disk controller. After the user changed the memory out on the controller, the sever quit receiving the NMI errors.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Intermittent Send and Receive Errors, AB Adapter Upgrade from v2.15 to v2.2
DOCUMENT ID#: FYI.P.5206
DATE: 15JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Intermittent send and receive errors
ISSUE/PROBLEM
Configuration:
Allen-Bradley LAN PC/AT broadband adapter
Allen-Bradley (v4.1) drives (newest version)
The user upgraded from a NetWare v2.15c to v2.2 operating system. Shortly thereafter, the system started getting intermittent send and receive errors. The user also noticed that the File Service Used route was incrementing about one each second. After the user tested the cable and the workstation's and file server's cards, the symptoms still existed.
SOLUTION
The Allen-Bradley LAN PC/AT broadband adapter is not certified for the NetWare v2.2 operating system.
The FCONSOLE problem denotes that the drivers were written to prefetch a receive buffer from the communication buffer pool. Apparently, this messes up the statistic in FCONSOLE and can cause a variety of problems. Allen-Bradley Inc. is aware of the problem and is working on a new release (v4.2) to fix the drivers.
Allen-Bradley Company Inc. technical support number is 216-646-6800.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Acer 1000 Sends GPPE when Installing 32 MB of Memory
DOCUMENT ID#: FYI.P.5213
DATE: 15JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When installing all 32 MB of memory and trying to run SERVER.EXE, the system displayed a GPPE.
ISSUE/PROBLEM
In the CMOS setup (not the EISA configuration) paging down to the second screen, a section prompts the user to select whether the system or an add-on card uses the memory between 15 and 16 MB. Selecting the "add-on card" option was causing the problem. When this option is chosen, it places a hole in the memory between 15 and 16 MB. The NetWare v3.11 operating system has to recognize contiguous memory.
SOLUTION
When the user selected the "system" option, the memory was contiguous. Now the operating system could recognize all 32 MB, and the server was up and running.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unable to Read from File OS 16"
DOCUMENT ID#: FYI.P.5220
DATE: 15JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The following error appeared in the Oracle error log file many times after running the backup software:
┌────────────────────────────────┐
│Unable to read from file [os 16]│
└────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
■AST 486/33
■48 MB RAM
■Two ADIC/Novell DCB
■DCB.DSK
■Racal Interlan NIC
■Oracle.NLM
■Mountain Backup Software v5.01
The error was caused by Mountain's Backup Software v5.01.
SOLUTION
The user needs to have v5.22a. Mountain said that they have seen similar results when their software is used with CCMAIL and Paradox along with Oracle.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: SMC PC-500 Problems in PS/2 Model 35
DOCUMENT ID#: FYI.P.5214
DATE: 15JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The SMC PC-500 board in the workstation initializes but returns the following error:
┌─────────────────────────────────┐
│A file server could not be found.│
└─────────────────────────────────┘
ISSUE/PROBLEM
The card was originally configured using the default of interrupt line 2, and I/O base of 2E0. There was a conflict with the IBM PS/2 Model 35 set at the default option.
SOLUTION
When the user changed the interrupt line to 3 and I/O base to 340, it worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Drop Cable Exceeding Length Limit Causing Error
DOCUMENT ID#: FYI.P.5219
DATE: 15JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
Only one group of workstations received the following error, and they were all physically connected to File Server 1:
┌────────────────────────────┐
│No response from file server│
└────────────────────────────┘
These workstations could attach and log into File Server 1, but they received the above error when trying to attach to any of the other file servers.
SLIST displayed all six file servers, and File Server 1 had been rebooted. Other workstations -- physically connected to File Server 2 through 6 -- could attach and log into any server.
ISSUE/PROBLEM
Configuration:
Network consisted of six file servers connected by thick Ethernet.
Workstations were cabled to servers through Token-Ring.
At a file server some 750 feet away from File Server 1, someone had added an AUI cable (a drop cable from the thick Ethernet) that exceeded the 50 foot maximum segment length.
SOLUTION
Replacing the drop cable with a shorter cable solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The user's file server machine displayed the following message:
┌───────────────────────────────┐
│Abend: Invalid Opcode Interrupt│
└───────────────────────────────┘
ISSUE/PROBLEM
When looking at the 386 machine, the user found that one of the Single In-line Memory Modules (SIMMs) was loose.
SOLUTION
When the user locked the SIMM into place, the server ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The server stayed up but continually displayed the error.
ISSUE/PROBLEM
Configuration:
■NetWare v3.11 operating system on a Compaq 486s/25m
■Storage Dimensions 1632 controller
■Storage Dimensions LAN 650E drive
■LANStor6 dated 05-9-91
■12 MB RAM
The problem causing the symptom is the revision of the mother board in the Compaq.
SOLUTION
When the user issued a mode command before loading server to disable the cache on the mother board (command was MODE MEM CACHE=OFF), this fixed the problem.
Also, an updated mother board can be ordered using the part number 129-126.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Okidata 2410e Printing Garbage in NetWare v3.11 Operating System
DOCUMENT ID#: FYI.P.5183
DATE: 14JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The Okidata 2410e printer with the IBM emulation worked fine, but the printer with the Pacemark printed garbage characters.
The user slowed down the baud of the port and this helped but a few characters were still missing.
ISSUE/PROBLEM
Configuration:
Two Okidata 2410e serial printers:
■One used IBM emulation
■One used Pacemark emulation
Pins 4 and 20 oscillating high and low caused the symptoms to occur.
SOLUTION
Installing RPRINTER.EXE v122R, PSERVER.NLM v122R, and PSERVER.EXE v122R fixed the problem. This version of the PSERVER pulls pin 4 and 20 high and leaves them high rather than oscillating high and low.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Duplicate Drive Mappings with "Hard Disk Manager"
DOCUMENT ID#: FYI.P.5173
DATE: 13JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Duplicate drive mappings
ISSUE/PROBLEM
Drive mappings were duplicated when using the Hard Disk Manager shareware menu program. All workstations received duplicate drive mappings when they logged out and logged back in. The user thought the problem might be a problem with the shell.
SOLUTION
Using an updated version of Hard Disk Manager menu program solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: HP IIIsi Prints Banner Page with No Username
DOCUMENT ID#: FYI.P.5162
DATE: 10JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: HP IIIsi prints banner page with no username
ISSUE/PROBLEM
Configuration:
Ethernet card - Firmware revision A.00.02 for the Hewlett Packard laser printer
The first entry on the banner page is the username and connection number. Because of the way that Hewlett Packard implemented the method for picking up the information for the username, the banner may print without a username but with the connection number only.
SOLUTION
Hewlett Packard is aware of this issue. The problem will be fixed in a future release of the Hewlett Packard queue server firmware.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "SSB Not Free during Initialization..."
DOCUMENT ID#: FYI.P.5161
DATE: 10JAN92
PRODUCT: NetWare
PRODUCT VERSION: All Versions
SUPERSEDES: NA
SYMPTOM: "SSB not free during initialization of Token-Ring"
ISSUE/PROBLEM
When the adapter initializes, it sets up a System Status Block (SSB). A System Status Block is an 8-byte block of memory in shared RAM. One of the SSB functions is used by the Token-Ring adapter to report its progress toward completing the last command it received from the LAN driver. The only time the SSB is used is when the command takes extra processing to finish and the adapter has to signal the driver to wait for completion.
The SSB is also used to report Ring status, Command Reject status, and status of commands issued to the adapter (example as above). The SSB does not contain the status of a Token-Ring frame.
SOLUTION
The SSB cannot be used until the adapter has been successfully initialized.
The IBM LAN Technical Reference is recommended for additional reading.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE Loading SERVER on EISA machine
DOCUMENT ID#: FYI.P.5168
DATE: 10JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "ABEND: General Protection Processor Exception"
ISSUE/PROBLEM
When the user put in the file server boot diskette and typed SERVER, the machine, a Gateway 2000 486/33E, would chug for a minute and then give the following error:
┌─────────────────────────────────────────────┐
│ABEND: General Protection Processor Exception│
└─────────────────────────────────────────────┘
They tried the diskettes on another machine and everything was fine.
SOLUTION
The machine was supposed to have 8 MB of RAM. The POST (Power On Self Test) counted up to 8 MB. Typing MEM showed 8 MB. Running the EISA CONFIGURATION utility showed only 3 MB. When the user configured the machine through EISA CONFIGURATION to reflect the 8 MB that was physically installed, then SERVER.EXE executed just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The system displayed the following errors when booting the 386 clone workstation:
┌────────────────┐
│RAM Buffer Error│
└────────────────┘
SOLUTION
Disabling the "Video BIOS shadow" parameter in the CMOS setup solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Sending on Network" - Hot CPU
DOCUMENT ID#: FYI.P.5400
DATE: 31JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Network Error: Error sending on network"
ISSUE/PROBLEM
Configuration:
■Wyse 486-33 EISA, 34 MB RAM
■DPT Cache Controller
■Three 1.4 GB SCSI, one 650 MB SCSI
■NE3200 adapter
Five months ago, this user installed this network as part of a three-file server WAN. This segment has 14 workstations running Western Digital 16-bit Elite16 10BaseT cards and two SynOptics 2800, and 12 port concentrators daisy-chained.
About three months after installing the network, the user noticed that the last workstations to log in caused the LAN channel to fail and display the following error:
┌───────────────────────────────────────┐
│Network Error: Error sending on network│
└───────────────────────────────────────┘
Each week the number of workstations that could log in decreased, and now only two workstations can log in. The file server appeared to remain operational except for Ethernet packets not reaching the card.
SOLUTION
While replacing the memory, the user noticed the Central Processing Unit (CPU) was almost red hot. After the user replaced the CPU, everything seems to work. After the user contacted Wyse Technologies, they will send a new box, motherboard, and CPU.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Sending on Network - Motherboard Problems
DOCUMENT ID#: FYI.P.5398
DATE: 31JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Network Error: Error sending on network"
ISSUE/PROBLEM
Configuration:
■NetWare v3.11 network installed.
■386/25 clone machines called Relab machines
■Eleven machines in the network - 1 server and 10 nodes
■Ethernet topology with EXOS 105t 16-bit cards in all machines
■NE2100 drivers for the EXOS 105t cards
Nine of the nodes can boot and log in and stay connected to the server. Two of the nodes can log in, but after three to four minutes they receive the following error and hang:
┌───────────────────────────────────────┐
│Network Error: Error sending on network│
└───────────────────────────────────────┘
SOLUTION
After the user replaced the system board in the two clone machines, the network did not have any more problems. The error seemed like a strange response for a bad motherboard; however, the machines are connecting and staying up now.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Attach to Server - XT, DOS 5.0
DOCUMENT ID#: FYI.P.5386
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "A File Server could not be found"
ISSUE/PROBLEM
Configuration:
■3c501 on workstations
■ODI drivers
■DOS 5.0
The user could not connect to file server from the XT machines and the system displayed the following error:
┌────────────────────────────────┐
│A file server could not be found│
└────────────────────────────────┘
The user suspected the problem to be timing issues because of the 16-bit card in file server and 8-bit card in workstation.
SOLUTION
When the user booted from DOS 3.3, the workstation was able to connect to the file server.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Keyboard Problems on Nondedicated COMPAQ 386 Machines
DOCUMENT ID#: FYI.P.5387
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Keyboard problems
ISSUE/PROBLEM
Configuration:
Nondedicated COMPAQ file server 386/20 machine
The user had erratic keyboard problems like numbers showing up when a letter is pressed or automatically switching from lower case to upper case.
SOLUTION
COMPAQ Computer Corp. said that if the UPS is connected to the server through the mouse port that this problem will occur because the mouse port is controlled by the keyboard controller (along with the switching from Protected to Real mode that happens in the nondedicated server).
The fix is to connect the UPS through a stand-alone serial card. COMPAQ and Novell are working on a patch.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Attach to NetWare v3.11 Server - IMC LAN Extender
DOCUMENT ID#: FYI.P.5395
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Cannot log in or attach to file server
ISSUE/PROBLEM
Configuration:
LAN extender
The user could not attach or log in to a NetWare v3.11 server on the internet. The user was successful attaching to a NetWare v2.2 server on the same segment. SLIST could recognize both servers. The user thought the problem might be a one way router (3Com bridge).
SOLUTION
They had one Ethernet segment over 300 meters. It was between the LAN extender and the NetWare v2.2 server. After the user cut the segment down to 80 meters, everything worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Workstation Locks while Indexing FoxPro Database
DOCUMENT ID#: FYI.P.5391
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Workstation locking
ISSUE/PROBLEM
The user was running a FoxPro database application on a NetWare v3.11 network. The user intentionally flagged the files as transactional to ensure the protection of the Transition Tracking System (TTS). However, when the user tried to index these files, the workstation locked. If the transactional flag was removed, the user was able to index the files without problem.
SOLUTION
Microsoft Corp. was aware of the problem and is sending the user a patch for their software application.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: I/O Addressing Issue - Ethercard Plus and COMPAQ 25e
DOCUMENT ID#: FYI.P.5394
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM: Problems initializing LAN card
ISSUE/PROBLEM
When the user to get a 3Com Ethercard Plus to work on a COMPAQ 25e machine, the system continually had problems initializing the LAN card.
SOLUTION
When using an address other than 280h or 300h on the LAN card, the user could get the card to initialize without any problems.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Recognize Volumes Using IDE.DSK, DOS 5.0
DOCUMENT ID#: FYI.P.5393
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to recognize volumes
ISSUE/PROBLEM
After a user experienced the usual problems with ISADISK and an IDE hard drive, Novell recommended trying IDE.DSK. The user a DOS 5.0 partition and loading the IDE driver would not allow the system to recognize the volumes. The hard drive appeared empty.
SOLUTION
The user removed the DOS partition with FDISK and started over on a NetWare level. After the user installed a DOS v4.01 partition, the system worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Thomas-Conrad 4045 Card Problems in NetWare v2.2 Server
DOCUMENT ID#: FYI.P.5392
DATE: 30JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Error: "Corrupt or missing EAGLEMAC.BIN file"
ISSUE/PROBLEM
Configuration:
■ Thomas-Conrad Token-Ring card (the 4045, which is switchable between 4 and 16 Mb) in an ALR 386/33 machine
The DMA setting was not an option in INSTALL, so the user ran JUMPERS utility on the NET$OS.EXE. After executing INSTALL -F and reloading the operating system, the user rebooted the machine. The cold boot loader loaded and the volumes mounted, but during the initialization of LAN A, the system displayed the following error:
┌────────────────────────────────────┐
│Corrupt or missing EAGLEMAC.BIN file│
└────────────────────────────────────┘
EAGLEMAC.BIN is a Thomas-Conrad file. The user found the file and put it on the boot disk but still could not get LAN A to initialize.
SOLUTION
The user replaced the Thomas-Conrad 4045 Token-Ring card with a Token-Ring card called IRMAtrac by Digital Communications Associates Inc. (This card is switchable between ISA and MCA. The part of the card that plugs in to the motherboard is modular). The IRMAtrac worked in the NetWare v2.2 server. The Thomas-Conrad 4045 card worked in both a workstation and a NetWare v3.11 file server. Apparently, the card was not defective; it just would not work in a NetWare v2.2 server.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Lotus, Always - Printing Blank Page
DOCUMENT ID#: FYI.P.5385
DATE: 29JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM: Print job disappearing from queue
ISSUE/PROBLEM
Using CAPTURE NB NFF, the Lotus application printed all documents fine. From the Always application, the job went into the queue and then disappeared, and the printer printed one blank sheet no matter what size the print job was.
SOLUTION
Using NT (No Tabs) to set the job as byte stream solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend: Returned Permanent Memory... Tiara Driver
DOCUMENT ID#: FYI.P.5383
DATE: 29JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user was upgrading to NetWare v3.11 from NetWare v2.15 software. Towards the end of the process, the NetWare v3.11 server received the following error:
The problem was the drivers for the Tiara boards. They continually request permanent memory but do not release the memory until the system crashes.
SOLUTION
When the user replaced the Tiara boards with Acton boards using the NE2000 driver, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Fastening I/O Card to Chassis Causing GPI
DOCUMENT ID#: FYI.P.5380
DATE: 29JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "Abend: General Protection Interrupt"
ISSUE/PROBLEM
Configuration:
COMPAQ 486/33 file server
After the user did a brand new installation of NetWare 2.2 software, the server immediately sent the following error message when the server came up:
┌───────────────────────────────────┐
│Abend: General Protection Interrupt│
└───────────────────────────────────┘
SOLUTION
If the user did not screw the LAN card into the chassis of the computer, the GPI would not happen.
The screw hole in the chassis was off just enough that it caused the LAN card to twist a little bit in the machine. The twist was causing the GPI messages.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Zenith 386 GPPEs Looking at Volume Information
DOCUMENT ID#: FYI.P.5384
DATE: 29JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: GPPE error
ISSUE/PROBLEM
Configuration:
Zenith 386/25 machine as the file server
ISADISK.DSK disk driver
When the user installed NetWare v3.11 software, everything seemed to work fine. However, after the user rebooted the system and tried to look at the volume information, the system set a GPPE error. Then, when the system stopped sending GPPE errors and the user looked at the volume information, the SYS: volume did not appear.
SOLUTION
Using the /b parameter when loading ISADISK solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
With a C: partition on a NetWare v3.11 file server and loading BTXNW31 from drive C:, the following error appeared when the user tried loading INSTALL or MONITOR:
┌────────────────────────┐
│Invalid load file format│
└────────────────────────┘
Also, when the server was shut down after the BTXNW31 driver was loaded, the following message appeared:
┌───────────────────┐
│Invalid COMMAND.COM│
└───────────────────┘
Invalid COMMAND.COM errors reported that occur when shutting down the server are the following:
1. CONFIG.SYS should not be on the server.
2. Ensure the drive type is correct.
SOLUTION
The solution in this case was upgrading the BusTek BT542 SCSI controller firmware from 2.20 to 2.21 and the BIOS from 2.40 to 2.41.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error 918" Microfocus COBOL Application
DOCUMENT ID#: FYI.P.5365
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
While running a medical application written with a Microfocus COBOL compiler v2.1 revision 016, the system displayed the following error:
Microfocus said the "error 918" indicated that the user's system had a corrupt file or record and that the compiler shipped with a REBUILD utility to correct the problem.
SOLUTION
Executing the REBUILD utility solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Improper ROM Parameter" Moving Hard Drive from 386 to 486
DOCUMENT ID#: FYI.P.5363
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The user had a Gateway 386 machine with NetWare v2.2 software and a Western Digital 120 MB IDE drive. The user wanted to move the drive to the 486 machine; however, after installing it and trying to boot the system, it displayed the following error:
┌────────────────────────────┐
│Abend:Improper ROM Parameter│
└────────────────────────────┘
ISSUE/PROBLEM
The problem was most likely a setup problem of the drive type not matching. The 386 machine drive type was 30. In the 486 machine, to match the drive architecture, the user selected type 49. Items such as the head count and cylinders matched in the different machines even though the drive type was a different number.
SOLUTION
The user said the 486 machine did have a drive type 30 that was the same as type 49 (the 386 machine did not have a type 49). After the user selected type 30 in the 486 machine, it booted just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unable to Unlock Disk.." - COMPAQ NetWare Ready Drive
DOCUMENT ID#: FYI.P.5366
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Unable to Unlock disk it is currently used by another process: A mounted volume may be using it. The partition table cannot be modified at this time."
ISSUE/PROBLEM
Configuration:
IDAMON.NLM loaded
When the user installed a new COMPAQ NetWare ready drive and a COMPAQ Intelligent Drive Array (IDA) controller in a COMPAQ SystemPRO, the system displayed the following error:
Unload the IDAMON.NLM. This NLM monitors disk information such as partition information and FAT tables. The NLM would not relinquish the disk for modification when it was loaded.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Files Too Low" Starting Paradox
DOCUMENT ID#: FYI.P.5367
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Error files too low"
ISSUE/PROBLEM
The following error appears when the user routes the output to "> null" in a .BAT file when starting Paradox.
SOLUTION
According to Borland International Inc, the CONFIG.SYS and SHELL.CFG routine each need to have at least 90 open files available.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Recognize Core Drive - NetWare ISADISK
DOCUMENT ID#: FYI.P.5370
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to recognize drive
ISSUE/PROBLEM
The user has COMPAQ 386-33L EISA with 650 MB ESDI (COMPAQ) loading ISADISK. The second drive is a CORE drive using ISA ESDI controller that is not busmastering. When the user loaded ISADISK, the CORE drives would not show up in INSTALL.
SOLUTION
CORE International said that each time before executing the EISA CONFIG on the COMPAQ machine, the user should execute CORE's PREP utility (debug routine) on the drive or EISA CONFIG will not recognize the drive.
Contact Core for the PREP utility at #408-997-6033.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Poor Drop Cables Causing "Error Sending on Network"
DOCUMENT ID#: FYI.P.5361
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15a SFT
SUPERSEDES: NA
SYMPTOM: Error: "Network Error: Error sending on network"
ISSUE/PROBLEM
Configuration:
■Forty users on the network
■Running SMC 8-bit twisted pair star/bus cards
■File server has two Hewlett Packard PC500 twisted pair cards (LAN split equally)
■600 MB Imprimis SCSI drive
■DCB (Generic SCSI)
■Three File Service Process (FSP)
■Four MB RAM
■Not loading any VAPs
■Workstations running IPX v2.15, NET3 v2.15a, DOS 3.3
■Using existing Unshielded Twisted Pair (UTP) wire in walls
About five times per day, each workstation hung with following error and had to reboot:
┌───────────────────────────────────────┐
│Network Error: Error sending on network│
└───────────────────────────────────────┘
The user checked the set up of the following items and did not find any problems:
■ Wiring distances
■ Terminate-and-stay residents
■ Active hubs
■ Applications
SOLUTION
Novell had the user looked at the drop cables (wire between wall and network interface card). The wire was made using flat silver-satin, two-pair phone wire. The user did not think that 3 feet made a difference. Using twisted-pair drop cables solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Load LanStor5, Proteon NIC
DOCUMENT ID#: FYI.P.5359
DATE: 28JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to load LanStor5
ISSUE/PROBLEM
Configuration:
■COMPAQ SystemPRO
■Three NE3200 adapters
■Proteon TR NIC (Proteon driver)
■Two LANStor SCSI controllers
■Two LANStor disk subsystems (1.2 GB) duplexed
The user could only get the LANStor5 driver to load with the above configuration if one of the network interface cards was physically removed from the system's bus.
SOLUTION
After the user replaced the Proteon TR NIC with an IBM 16/4 NIC, everything works fine now.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Corvus Omninet-4 Card Drivers
DOCUMENT ID#: FYI.P.5350
DATE: 27JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15, v2.2
SUPERSEDES: NA
SYMPTOM: File server disappears from network
ISSUE/PROBLEM
The user was connecting a NetWare v2.2 server on an existing NetWare v2.15c network. The v2.2 server would stay available for about 30 seconds, then disappear from the network. Both servers and workstations had Corvus Omninet cards. The v2.2 server had an OMNINET-4 card slowed down to an OMNINET-1 speed because all other cards were OMNINET-1 cards.
SOLUTION
The user had to get a new driver from ATRIX (formerly Corvus) for the v2.2 server's OMNINET-4 card. This new driver is needed if you are slowing the OMNINET-4 card down to the OMNINET-1 speed.
ATRIX BBS: (408)972-9154
The drive name is: OMNI1P.xxx
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Hole in File" Mixing Drives
DOCUMENT ID#: FYI.P.5354
DATE: 27JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Error: "Error Hole in file"
ISSUE/PROBLEM
Configuration:
IDE286.ZIP
■NEC 386sx/vi
■Maxtor 125 MB drive
■Western Digital 80 MB drive
When the user used the above listed drives on the NEC built-in controller with the new IDE driver, the system displayed the following error:
┌──────────────────┐
│Error Hole in file│
└──────────────────┘
SOLUTION
If the user used only one drive or two drives of the same manufacture (such as two MAXTOR or two WESTERN DIGITAL), the error would not occur.
This problem is a good reminder of a problem concerning the use of two IDE/ATA drives on a single paddleboard (PB) or embedded interface. Mixing drive manufacturers on a single PB or interface generally will not work. Having identical drives is the best and safest configuration.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Write of 140 Bytes Returned.." - BINDFIX
DOCUMENT ID#: FYI.P.5357
DATE: 27JAN92
PRODUCT: ELS NetWare Level I
PRODUCT VERSION: v2.12
SUPERSEDES: NA
SYMPTOM: "Write of 140 bytes returned 0"
ISSUE/PROBLEM
While executing BINDFIX, the system returned the following error:
┌─────────────────────────────┐
│Write of 140 bytes returned 0│
└─────────────────────────────┘
SOLUTION
The disk was completely full. After the user deleted and purged some old files, BINDFIX executed fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Initializing LAN Driver... SMC ELS I 2.0a
DOCUMENT ID#: FYI.P.5355
DATE: 27JAN92
PRODUCT: ELS NetWare Level I
PRODUCT VERSION: v2.0a
SUPERSEDES: NA
SYMPTOM: Error: "Error initializing LAN driver NIC Initialization Signature not found"
ISSUE/PROBLEM
The user removed an emulation card from the PS/2 Model 50. Then the user executed reference and selected "Automatically Configure the System" to remove the emulation card from the CMOS memory. After the user rebooted the system and mounted the SYS: volume, the system displayed following error:
When the user ran automatic configuration sequence in reference, it changed the PS110 (SMC Arcnet card) settings. After the user changed the RAM buffer address to D000h, the system came up just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: HP IIIsi Shows Offline
DOCUMENT ID#: FYI.P.5356
DATE: 27JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Printer going Offline
ISSUE/PROBLEM
Jobs piled up in the queue, and the printer status showed Offline.
SOLUTION
The user said that the newer NE3200 driver v3.15 found in NE386.ZIP solved this problem.
NE386.ZIP is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: FAT Chains Colliding - IN2000F and ST41600N
DOCUMENT ID#: FYI.P.5347
DATE: 25JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "A FAT chain is colliding with another FAT chain"
ISSUE/PROBLEM
The user had an Always IN-2000 disk controller and Seagate ST41600n hard drive that had worked together fine for 4 months. Now, the system displays the following error when the user mounts the volume:
┌───────────────────────────────────────────────┐
│A FAT chain is colliding with another FAT chain│
└───────────────────────────────────────────────┘
VREPAIR would not clean up the volume.
SOLUTION
The newest driver from Always Technology Corp. goes beyond the 1 GB addressable limit. Installing the new driver and slowing down the bus speed allowed VREPAIR to fix the volume.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Firmware Will Not Initialize" Bad NE3200
DOCUMENT ID#: FYI.P.5341
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Firmware will not initialize"
ISSUE/PROBLEM
When the user tried to load the NE3200.LAN driver (the one that shipped with NetWare v3.11 software), the system displayed following error:
┌────────────────────────────┐
│Firmware will not initialize│
└────────────────────────────┘
The server was an ALR 486/33 EISA, so the Novell thought the problem might be speed or timing issue because there were many references in the Network Support Encyclopedia (NSE) to problems with the NE3200 and ALR machines.
SOLUTION
A defective NE3200 card caused the error. Replacing the card solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Server Unable to Recognize Workstation - IBM PS/2 65, PCN2 Adapter
DOCUMENT ID#: FYI.P.5371
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM: File server unable to recognize workstation
ISSUE/PROBLEM
A user upgraded an IBM PS2 50 running NetWare v2.15c software using IBM PCN2 baseband adapters in an IBM PS/2 65 with NetWare v2.2 software. Comcheck works fine between the file server and workstation; however, when file server boots NetWare, the file server does not recognize the workstation. If the user uses a different kind of LAN card in the IBM PS/2 65, it works fine. The user has also installed NetWare v2.2 software and the PCN2 card in a PS/2 50sx and PS/2 60 without problems.
SOLUTION
Using the ODI driver at the workstation solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Acer 1000 Errors when Creating NetWare Partition
DOCUMENT ID#: FYI.P.5343
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Abend: GPPE" or "Abend: ALLOC called with invalid resource tag"
ISSUE/PROBLEM
Configuration:
■ACER 1000 EISA
■1740 controller
■1.1 GB Fujitsu hard drive
As soon as the user pressed <Enter> on "Create NetWare Partition" option while trying to create a NetWare partition in INSTALL, the server crashed with the following errors:
┌───────────┐
│Abend: GPPE│
└───────────┘
or
┌─────────────────────────────────────────────┐
│Abend: ALLOC called with invalid resource tag│
└─────────────────────────────────────────────┘
SOLUTION
The INSTALL.NLM was corrupt. Using a fresh copy of INSTALL.NLM allowed the user to create the partition.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: File Indexing Application Nisam and NetWare
DOCUMENT ID#: FYI.P.5353
DATE: 21JAN92
PRODUCT: ELS NetWare Level II
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Nisam is a file indexing application compiled in COBOL that must be run on a file server's local C: drive. The user says it works with PC LAN and wants better performance. Therefore, the user is trying to get it to work with NetWare.
SOLUTION
Unless the user created a DOS partition on the C: drive and ran nondedicated, running the Nisam program on NetWare is not possible because of the requirement of running the application from the file server's local C: drive that is not accessible in NetWare when the file server is up.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NetWare v2.0a Server Cannot Recognize NetWare v3.11 Server
DOCUMENT ID#: FYI.P.5153
DATE: 09JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11, v2.0a
SUPERSEDES: NA
SYMPTOM: Servers cannot recognize each other on same network.
ISSUE/PROBLEM
The user had a NetWare v3.11 server, as well as an ELS NetWare Level I v2.0a server to upgrade on the same network. Both servers had 01 as the network address but neither could recognize each other.
SOLUTION
Because ELS NetWare Level I (v2.0a and v2.12) software does not send Service Advertising Protocol Packets (SAPs) or Routing Information Protocol Packets (RIPs), the NetWare v3.11 server and the ELS NetWare Level I v2.0a server are not compatable.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MONITOR and FCONSOLE Unable to Clear Connections
DOCUMENT ID#: FYI.P.8703
DATE: 01SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Not clearing connections
ISSUE/PROBLEM
Configuration:
Two Ethernet thinnet segments
Both MONITOR and FCONSOLE appeared to allow a connection to be deleted; however, MONITOR on the file server showed the connection still in use. The problem occurred on both segments.
The user tried replacing some server cards, connectors, and cables, but the problem still existed.
SOLUTION
One of the Thinnet segments was grounded on both ends. After removing the grounding from one of the terminators, the user could clear connections successfully.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Drive Deactivation, Abends, SD Drives Unmirror - Model 95
DOCUMENT ID#: FYI.P.8704
DATE: 01SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Drive deactivation and various abends
ISSUE/PROBLEM
Configuration:
■IBM SCSI controller
■Two Storage Dimensions controllers, duplexed
When more than 64 MB of RAM was installed in a Model 95, the machine sent abends and the drives unmirrored and deactivated.
SOLUTION
The user found that the problem only happened with the PS/2 SCSI part number ANOSPRIME. When the user switched to a PS/2 SCSI part number ANOS6451018, the machine worked just fine with more than 64 MB of RAM.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM PC, XT, and AT Model Numbers
DOCUMENT ID#: FYI.P.4581
DATE: 06NOV91
PRODUCT: Netware
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The following IBM model numbers, located on the back of an IBM PC, may be useful references:
IBM PC 5160 and 5161 10 MB drive
IBM XT-286 5162 20 MB drive
IBM AT 5170 20 MB and 30 MB drive
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Western Digital 1009SE2 - NetWare v3.11
DOCUMENT ID#: FYI.P.4558
DATE: 05NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: INSTALL does not recognize disk partition.
ISSUE/PROBLEM
Configuration:
■Wren 4 drive
■DOS 5.0 on a 386/20 machine
The user could not get INSTALL to recognize the disk partition on the drive.
SOLUTION
The user could not find the Western Digital 1009SE2 disk controller in the list of certified controllers and tried all the flags to get it to load. When the user used a different controller, the system came up and worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Invalid ROM Parameter Table" - NetWare v2.2
DOCUMENT ID#: FYI.P.4567
DATE: 05NOV91
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Error: "Invalid ROM parameter table"
ISSUE/PROBLEM
Novell normally associates this message with the generation of a server where driver types above 45 are included. This one has a twist. The user had the NetWare v2.2 server up and running just fine. Then after the server experienced a power glitch, the server displayed the following message during bootup:
┌───────────────────────────┐
│Invalid ROM parameter table│
└───────────────────────────┘
After the user reinstalled NetWare v2.2 software on the server, it still displayed the same message.
SOLUTION
The machine's CMOS was ruined during the power glitch, so the BIOS was not available to load into RAM. The user needed to replace the CMOS and/or the motherboard to solve the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Dell Computer Corp. has a 486/33 and a 486/25 EISA computer that has been certified under NetWare v3.11 and v2.2 software. Certain situations cause the EISA configuration to become corrupted or incorrect and the system will display the following system message during bootup:
┌────────────────────┐
│Invalid EISA storage│
└────────────────────┘
If the machine has a nonconfigured EISA card in one of the slots, the boot up process will also hang.
Dell has a file to erase the information in the EISA CMOS chip on the 486-based systems named ZAPXCMOS.COM. This file can be obtained from Dell's BBS. This utility will erase the current EISA configuration information and permit the user to load the EISA configuration utility to reconfigure the computer correctly.
Dell Computer Corp. BBS phone number is 512-338-8528.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NEC MultiSync Graphics Engine Adapter - NetWare v3.11
DOCUMENT ID#: FYI.P.4563
DATE: 05NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Server hangs occasionally while toggling between screens.
ISSUE/PROBLEM
Configuration:
■Running NetWare v3.11 software on NEC Powermate 386/33 EISA
■NEC MultiSync Graphics Engine adapter
Sometimes when the user toggled between screens at the console, the display went black and the server crashed with no messages displayed. The user had to reboot the server to get it to come back up.
SOLUTION
NEC Technologies Inc. suggested using any other adapter than the NEC MultiSync Graphics Engine adapter because they have seen these types of problems with this adapter before.
When the user switched to a Paradise adapter, the system ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Locate Subsystem in INSTALL - NetWare v3.11
DOCUMENT ID#: FYI.P.4541
DATE: 04NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to locate disk subsystem
ISSUE/PROBLEM
While in INSTALL, the user loaded VTXNW31.DSK for the disk driver. At this point, the user could not view the subsystem at all.
SOLUTION
Exactly 16 MB was in the server, so the user needed set the following parameter on the COMPAQ SystemPRO:
Set Auto Register Memory = Off
Also the VTWNW31.DSK is not certified by Novell; however, the BTXNW31.DSK is certified. The dates were the following:
BTX... 01-04-91
VTX... 01-07-91
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: 3C507 Card Will Not Work with DOS 5.0 Loaded High
DOCUMENT ID#: FYI.P.4524
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user could not load MS-DOS 5.0 high and get the 3c507 card to work on the network. Other 3Com cards worked fine.
SOLUTION
Using the following syntax, the user was able to load MS-DOS high:
CONFIG.SYS file
device=himem.sys
device=emm386.exe x=c800-cfff noems
DOS=high,umb
AUTOEXEC.BAT file
loadhi netx
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
When the user loaded the NE3200.LAN from the diskette or the C: drive, the system displayed the following error:
┌─────────────────────────────┐
│Module initialization failure│
└─────────────────────────────┘
The user set the default option on the card.
SOLUTION
Switching the card from slot 7 to slot 5 solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IRQ Conflict Causing "A File Server Could Not Be Found"
DOCUMENT ID#: FYI.P.4520
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "A File Server Could Not Be Found"
ISSUE/PROBLEM
Configuration:
■Two NetWare v3.11 file servers
■Each file server - internally routing with Tiara Arcnet cards
When the user tried to attach the workstations to the servers, the system displayed the following error message:
┌────────────────────────────────┐
│A File Server Could Not Be Found│
└────────────────────────────────┘
Suspecting a bad card, Novell had the user run COMCHECK. The workstations could not locate each other when running COMCHECK. The user also switched the card, but the problem still existed.
SOLUTION
The user discovered that the video card had the same interrupt line settings as the second Tiara Arcnet card in the servers. When the user changed the interrupt settings, the workstations could attach and log in.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM SCSI Cache Pal Chip Replacement
DOCUMENT ID#: FYI.P.4535
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: v3.1x
SUPERSEDES: NA
SYMPTOM: Data corruption
ISSUE/PROBLEM
The user had an IBM SCSI adapter that kept corrupting data, but it did not return any error codes. The adapter also caused the mirror drives to get out of synchronization. Remirroring messages kept appearing frequently on the server console.
SOLUTION
Contact IBM source to obtain ECA027 Programmable Array Logic (PAL) chip replacements. To determine if chips need replacement, look at position U47 on the adapter for 64F1333. Old PALs are N64F0124 and new PALs are N85F0000.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Applications Hang after Tape Backup
DOCUMENT ID#: FYI.P.4530
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Applications hang after tape backup
ISSUE/PROBLEM
The user had upgraded from a Zenith 286 server to a Chip & Technologies 386 server to increase speed. After restoring the server from a Mountain tape drive, the applications hung.
SOLUTION
The user found that the person doing the restore from the tape drive was not paying attention to the verify process. Even though it apparently restored without problems, the verify showed errors on some of the files.
The user repeated the process with a new Mountain backup system without problems.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Broken Connector on Pinout Cable Causing Error 22
DOCUMENT ID#: FYI.P.4523
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Error: "Error 22"
ISSUE/PROBLEM
Configuration:
■ The HP Laserjet Series III printer was connected to the file server serial port
■ Running PSERVER.NLM v1.22
A Hewlett-Packer Laserjet Series III printer displayed the following error:
┌────────┐
│Error 22│
└────────┘
SOLUTION
While checking the pin configuration on the cable, the user found a broken connector. Repairing the cable solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM PS/1 for Use on a Network
DOCUMENT ID#: FYI.P.4526
DATE: 01NOV91
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When the PS/1 was first introduced as a home computer, IBM's stance on its network ability was that network adapters were not supported in the machines. With the recent enhancements to the PS/1, including an 80386SX processor, networking has been added to its supported features. It has passed workstation certification by Novell Labs.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Defective Cable Causing "Printer Out of Paper"
DOCUMENT ID#: FYI.P.8970
DATE: 01OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Printer out of paper"
ISSUE/PROBLEM
When a user tried to send print jobs to a HP III printer, the printer status showed that the printer was out of paper. The print jobs would just stack up in the queue. When the user tried printing under DOS, the jobs came out fine.
SOLUTION
While checking the printer, the user discovered a ribbon cable, attached to the I/O card, was crimped and four of the wires had shorted out. Replacing the cable solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Undefined Offending Command" - HP IIIsi
Using a HP IIIsi that allows switching between PCL mode (standard printer) and postscript mode. The user noticed that when printing jobs in postscript applications (in this case Word for Windows) the following error displayed before and after the job printed. The job printed fine.
SOLUTION
The user had the HP IIIsi printer configured for postscript mode. Word for Windows was sending ESC sequences to the printer to switch to postscript mode. Because the printer was already in postscript mode, it was unable to make the switch so it displayed the errors. When the user set the printer for the PCL mode, the problem went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Poor Cable Causing Corrupt SERVER.EXE
DOCUMENT ID#: FYI.P.4512
DATE: 31OCT91
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error: "Cannot find public symbol"
ISSUE/PROBLEM
The user kept getting symptoms of a corrupt SERVER.EXE on the NetWare v3.11 network and it displayed the following error message:
┌─────────────────────────┐
│Cannot find public symbol│
└─────────────────────────┘
After the user replaced SERVER.EXE, the system still displayed the same errors and some workstations could not locate the file server and others lost their mappings.
SOLUTION
The user had a short in the Ethernet cabling that corrupting the SERVER.EXE file. Replacing the cable solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The user tried switching drive controllers and Token-Ring boards and tried several different interrupt lines and addresses, but the errors still displayed.
Running "inspect" on the COMPAQ machine showed an ID code of 65. COMPAQ told the user that machines with ID code of 64 had some type of timing problems on the motherboard. COMPAQ will fix the timing problem with service advisory 84.
COMPAQ also told of another service advisory on the 386/33. System boards with assembly 001286 with revision E or earlier (A,B,C, D, or E) are known to have intermittent timing problems that will show up when running diagnostics. This timing problem can be fixed with service advisory 91.
SOLUTION
The user's machine was not within the specifications above (ID code 65). However, when the user replaced the motherboard with an assembly 001184 and ROM chips 115305-004 and 115306-004, it solved the Nonmaskable Interrupt (NMI) problems. The machine was a new machine, and the problem had happened on two different occasions.
Note: This problem does not apply to the COMPAQ 386/33L
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: AT&T StarLAN 10 - Banyan, NetWare
DOCUMENT ID#: FYI.P.4506
DATE: 30OCT91
PRODUCT: NetWare
PRODUCT VERSION: v2.15, v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
A user was comparing the time it took for Banyan VINES, NetWare v3.11 and 2.15c operating systems to complete a particular process. The results were the following:
Operating System Seconds
NetWare v2.15 = 106
NetWare v3.11 = 120
Banyan VINES = 186
SOLUTION
In trying to figure out why the NetWare v2.15 operating system was faster than the NetWare v3.11 operating system, the user ended up speaking with Hewlett-Packard because they were using a Hewlett-Packer machine for the file server. The user was using the AT&T StarLAN 10 card on the NetWare v3.11 system and the AT&T driver that came with it, ATTDRV.LAN.
Hewlett-Packard told the user that they had tested the procedure using the 3Com 3c501 card and found it to increase the performance. The user tried the test with the 3c501 card and the performance did increase.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Dell 333-D Board Hanging Server
DOCUMENT ID#: FYI.P.4488
DATE: 29OCT91
PRODUCT: NetWare
PRODUCT VERSION: All Versions
SUPERSEDES: NA
SYMPTOM: File server hanging
ISSUE/PROBLEM
A user's file server hung after about 20 minutes of use. The user tried disabling the Cache and various other solutions, but the problem still existed.
SOLUTION
Dell Computer Corp. has noted a problem with early versions of their 333-D system board. After Dell replaced the system board with a new revision, the problem went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Everex 16-bit Board Problems in 486 Server
DOCUMENT ID#: FYI.P.4508
DATE: 28OCT91
PRODUCT: NetWare
PRODUCT VERSION: v2.15c
SUPERSEDES: NA
SYMPTOM: High utilization and server hanging
ISSUE/PROBLEM
The user was running with an Everex 2027 Ethernet card that worked in a 386/33 machine, but does not work when the file server was upgraded to a 486/33 machine. The utilization went up to 650 percent. Also the server hung.
SOLUTION
When the user replaced the Everex card with an NE2000 card, the system worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unknown Error Returned by Attach 89ec" - Columbia Data Products
DOCUMENT ID#: FYI.P.3685
DATE: 02AUG91
PRODUCT: Netware
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Error: "Unknown error returned by attach 89ec"
ISSUE/PROBLEM
When the user tried to log in as either a supervisor or guest after a new install of NetWare v2.2 software, the system displayed the following message:
┌─────────────────────────────────────┐
│Unknown error returned by attach 89ec│
└─────────────────────────────────────┘
Nothing seemed to be out of place until the user said that he thought the network address during the operating system generation was supposed to be the address on the card (node address).
SOLUTION
Changing the network address to something other than the card address solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Cabletron Systems Inc. said that NetWare v3.11 software requires the updated Cabletron Driver v3.13. This driver version needs to be set to interrupt line 8 or below to be able to load automatically out of the AUTOEXEC.NCF file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Bad Resource Tag Passed to LSL Returnrcvecb"
DOCUMENT ID#: FYI.P.9351
DATE: 09JUL91
PRODUCT: Netware
PRODUCT VERSION: v3.1
SUPERSEDES: NA
SYMPTOM: Error: "Bad resource tag passed to LSL Returnrcvecb"
ISSUE/PROBLEM
Configuration: User 1
■Wang 486 EISA machine
■NWR-1990x .LAN driver
When user 1 was trying to load the LAN driver for their Proteon NIC, the system displayed the following error message:
┌───────────────────────────────────────────┐
│Bad resource tag passed to LSL Returnrcvecb│
└───────────────────────────────────────────┘
Configuration: User 2
■Ethernet topology
■Ethernet SMC-PC270e 10BaseT cards
User's 2 system displayed the same above message.
SOLUTION
The solution in both cases was a faulty hardware communication connection.
In the case of User 1 with the Token-Ring topology, the message displayed because of a faulty Multi-Station Access Unit (MSAU) port
In the case of User 2 with the Ethernet topology, the message displayed because of a bad concentrator.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NMI Errors Using Cumulus Memory
DOCUMENT ID#: FYI.P.9350
DATE: 23MAY91
PRODUCT: Netware
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Nonmaskable Interrupt (NMI) errors
ISSUE/PROBLEM
Configuration:
Cumulus memory in a COMPAQ 386/25
The user's system kept getting NMI errors. If the user took out the memory card, the errors disappear.
SOLUTION
Cumulus memory will virtually pass all diagnostic tests but will still give NMI errors. Cumulus Corp. has acknowledged that they have a certain batch problem. The user must contact the manufacturer to verify the item batch number and get it replaced.
In this case, replacing the Cumulus memory with Compaq memory solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Incompatibility Using AST 386/33 and ADIC DCB
DOCUMENT ID#: FYI.P.9361
DATE: 27SEP90
PRODUCT: Netware
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM: ADIC Disk Coprocessor Board fails to intialize.
ISSUE/PROBLEM
Configuration:
■AST 386/33
■ADIC Disk Coprocessor Board (DCB)
When the user loaded a second DCB (with two network interface cards in the machine), the DCB.DSK failed to initialize.
SOLUTION
Move the two DCBs closer to the CPU board (the CPU board is plugged into a planer bus slot) for a more reliable system. The user chose to use a different configuration other than using the DCBs.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IRMA Token-Ring NIC Unable to Attach to Micronix 486
DOCUMENT ID#: FYI.P.8696
DATE: 31AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM: "A File Server could not be found"
ISSUE/PROBLEM
Configuration:
File Server - Micronix 486/33 EISA
Network interface card - DCA IRMA Token-Ring
No workstation could attach to the file server with the IRMA card in the server.
SOLUTION
When the user disabled the Direct Memory Access (DMA) on the load statement in the server, the problem disappeared.
The load statement now reads as shown below:
LOAD IRMATRAC INT=3 PORT=A20 NODMA DR=16M
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Not Enough File Handles to Run Application" - Windows
DOCUMENT ID#: FYI.P.8686
DATE: 28AUG92
PRODUCT: NetWare
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: "Not enough file handles to run application"
ISSUE/PROBLEM
While running Windows v3.1, the system displayed the following error message when the user tried to run an application:
┌──────────────────────────────────────────┐
│Not enough file handles to run application│
└──────────────────────────────────────────┘
SOLUTION
Try putting the following setting in the SYSTEM.INI file:
[386Enh]
PerVMFiles=xxx
Replace xxx with the number of files. This option sets a number of file handles to be created "per virtual machine," if the CONFIG.SYS FILES= setting has not already used all 255 files. The limit for the CONFIG.SYS FILES= and PerVMFiles= together is 255.
Putting this setting in the SYSTEM.INI file has solved the problems associated with the above error message many times.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Warning Commercial Power Detected Off during UPS Install"
DOCUMENT ID#: FYI.P.8680
DATE: 28AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Warning Commercial power detected off during UPS install"
ISSUE/PROBLEM
Configuration:
■Tripplite card
■UPS NLM
After the user loaded the UPS.NLM, the system displayed following error:
Changing the jumper 2 (AC Fail) from setting 3 to 4 solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
After a time (not consistent), the server displayed the following error message and died:
┌────────────────────────────────────┐
│Packet Receive Buffer Limit reached.│
└────────────────────────────────────┘
ISSUE/PROBLEM
PSCAN, a utility that ships with Intel's LANProtect program, was causing the Maximum Short Term Alloc memory pool to exceed the maximum limit.
SOLUTION
Do not run the PSCAN utility or contact Intel to see if they have a newer version of PSCAN that does not cause the file server to run out of memory.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: File Server Hanging with Arcade LAN Cards
DOCUMENT ID#: FYI.P.8674
DATE: 27AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: File server hangs
ISSUE/PROBLEM
Configuration:
■File server - Compaq SystemPro 486/33
■Arcade Ethernet LAN card in the file server
■Arcade Ethernet LAN card in the workstation running RPRINTER v1.21
When a job was sent by more than one workstation to the RPRINTER workstation, the file server would hang and have to be rebooted. The user did not have a number for Arcade, so getting drivers for this card was not an option.
SOLUTION
After the user did the following, printing works fine:
1. Upgraded PSERVER.NLM to 1.22r
2. Upgraded RPRINTER to 1.22r
3. Put Eagle NE2000 LAN cards in both the file server and in the workstation running RPRINTER
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Receiving from Network" - SMC PC-130
DOCUMENT ID#: FYI.P.8668
DATE: 27AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Error receiving from Network"
ISSUE/PROBLEM
Configuration:
Epson Equity 386/25 PLUS
One - TCNS (Thomas-Conrad Network System) 100 Mb Arcnet card using the TCCARC.LAN driver
One - SMC PC-130 (PC130) 8-bit Arcnet card using the TRXNET.LAN that shipped with the NetWare v3.11 operating system
The workstation lost its connection and displayed the following error message:
┌────────────────────────────┐
│Error receiving from Network│
└────────────────────────────┘
Using the newest TRXNET.LAN file on NetWire did not help.
SOLUTION
The user did the following to solve the problem:
1. Replaced the SMC PC-130 card with a Thomas-Conrad 8-bit card
2. Used the TCCARC.LAN driver (for both Arcnet cards)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
After some time of being up, the server displayed the following abend message:
┌────────────────────────────┐
│Abend: Divide Overflow Error│
└────────────────────────────┘
The same abend message was displayed when the user tried to create a partition on the drive.
SOLUTION
UltraStor Corp. has a new driver US24_31X.ZIP that is downloadable file from their BBS that includes a driver dated 05-31-92. Using this driver kept the system from sending the abend messages.
Note: The UltraStor 12F also has this problem, documented in the Network Support Encyclopedia (NSE).
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error 1.1.29 and 1.1.33 Writing to File - Dell 486TE
DOCUMENT ID#: FYI.P.8644
DATE: 25AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Error 1.1.29 and 1.1.33 writing to file
ISSUE/PROBLEM
Configuration:
■Dell 486TE server
■20 MB of RAM
■Two ESDI 650 drives
■UltraStor 12f controller
■Loading ISADISK /b /l
When writing to device 0, the system displayed the following error:
┌───────────────────────────────────────┐
│Error 1.1.29 and 1.1.33 writing to file│
└───────────────────────────────────────┘
The error was also recorded in the system error log. MONITOR showed no Hot Fix redirection area or bad blocks. The area was blank.
The user tried running VRP31X.ZIP and replacing the UltraStor controllers but the problem still existed.
SOLUTION
When the user made a backup of the drives, reintialized the drive, and restored the drives from the backup, the Hot Fix redirection area showed in MONITOR and the errors disappeared.
The UltraStor 12f documentation specifies that ISADISK should be loaded with a "/l" option only.
UltraStor Corporation's suggestion not to use the "/b" option is probably based on lack of information. Unless the installer is certain that the drive attached to the controller on the ISADISK channel is a NetWare Ready (NR) or a Common Configuration Method (CCM) drive, the "/b" option should be used on each instance of ISADISK. If the "/b" option is not used, the ISADISK driver will set up the controller once to read sector 30 (NR) and sector 2 (CCM). If no NR or CCM stamp is found, the driver will search INT41 and use the options in the table where the INT41 vector points. With those options, it will set up the controller again.
The problem with many controllers or IDE drives is that they operate erratically under multiple setup conditions. If the "/b" option is used, then the NR and CCM tests will be bypassed and the option table pointed to by the INT41 vector will be used to set up the controller (once).
The use of the "/b" option is recommended, as indicated above, when using ISADISK.DSK dated 02-15-91 or 03-25-91. Currently, ISADISK.DSK dated 07-08-92 can be found in ISA311.ZIP available on NetWire or NetWare Express. The default (no option) for this version of ISADISK.DSK is to bypass the NR and CCM test. The "/n" option should be used for an NR or CCM sector drive.
The rule for the "/l" option is very simple and it applies to all three of the drivers mentioned in the preceding paragraph. If ISADISK.DSK is loaded at I/O address 170 (secondary AT controller I/O), then use the "/l" option. If "/l" option is used when loading ISADISK at I/O 1F0, it will be ignored.
For more information, see Technical Bulletin TB.P.302.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Three 3Com Stations Lock Using WordPerfect
DOCUMENT ID#: FYI.P.8444
DATE: 04AUG92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: Three 3Com stations locking
ISSUE/PROBLEM
Configuration:
Three 3Com stations running:
■WordPerfect v5.1 dated 20AUG90
■WordPerfect Office v3.1
The 3Com stations would lock randomly.
SOLUTION
Upgrading WordPerfect v5.1 from 20AUG90 to 31DEC90 solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Cannot Execute SYS:\PUBLIC\SYSCON.EXE" or FILER.EXE
DOCUMENT ID#: FYI.P.8055
DATE: 30JUN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user tried to execute SYSCON or FILER at the workstation, the following messages were displayed:
┌─────────────────────────────────────┐
│Cannot Execute SYS:\PUBLIC\SYSCON.EXE│
└─────────────────────────────────────┘
┌────────────────────────────────────┐
│Cannot Execute SYS:\PUBLIC\FILER.EXE│
└────────────────────────────────────┘
ISSUE/PROBLEM
The user had the Reflection terminate-and-stay resident (TSR) loaded.
SOLUTION
Unloading the Reflection TSR before executing NetWare utilities solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unable to Create Intermediate File" - NSE
DOCUMENT ID#: FYI.P.7892
DATE: 15JUN92
PRODUCT: Network Support Encyclopedia
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: "Unable to create intermediate file."
ISSUE/PROBLEM
While running the NSE Pro version (Network Support Encyclopedia) from a local drive, the following error displayed when the user attempted to print an active Folio:
┌───────────────────────────────────┐
│Unable to create intermediate file.│
└───────────────────────────────────┘
SOLUTION
Complete the following steps to be able to print an active Folio:
1. Go into "Options" on the main menu.
2. Select the "User Defaults" settings.
3. Select the local drive as the drive to save all VIEWS.CFG settings.
4. Then, when setting up printing, set the "save settings to:" field to the same drive.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Support for LANProtect NLM from Intel
DOCUMENT ID#: FYI.P.7143
DATE: 14APR92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Intel Corp. has released a new product called LANProtect that is an NLM that runs on a NetWare v3.11 file server and periodically checks (depending on how it is setup) for all known viruses. Intel also has workstation software that can be run at the local workstation to check each workstation for viruses.
LANProtect is Novell certified. Intel has released and started shipping this product. Any questions or problems relating to this product can go through Novell's Technical Support Alliance (TSA) contacts and be fielded by the Intel group in Provo.
LANProtect is IMSP Bulletin N-12.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE with BusTek BTXNW31.DSK Driver
DOCUMENT ID#: FYI.P.5816
DATE: 17MAR92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: The system received a GPPE while mounting the SYS: volume.
ISSUE/PROBLEM
Configuration:
BusTek 742a 32-bit EISA SCSI controller
Using the BusTek driver BTXNW31.DSK, dated February 1990, would not allow the file server to have more than 16 MB of memory without stopping the server and sending an abend:GPPE while mounting the SYS: volume.
SOLUTION
When the user updated the BusTek driver to a version dated July 02, 1991, the system can now go above the 16 MB limit. The user went as high as
32 MB without any problems.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Maintain Connections to AS/400 and Server
DOCUMENT ID#: FYI.P.5125
DATE: 17MAR92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
1. The user could not maintain simultaneous connections to the AS/400 and NetWare server.
2. Errors: "File server not found" and "Unable to attach to file server"
ISSUE/PROBLEM
Problem 1
Configuration:
■IBM LANSupport 1.2 with the LANSUP ODI driver.
■IRMAtrac Token-Ring boards from DCA
■TOK380.DCA driver (v1.11)
■AS/400 PC Support v2.0.
The user could start a session to the AS/400, but if the user tried to attach to the file server, the AS/400 connection would be lost. Everything worked fine until the user loaded LANSUP.COM.
Problem 2
Configuration:
■NE2000 Ethernet LAN
■DCA IRMA TRAC Token-Ring LAN
■Each LAN had a single server connected through a dedicated real-mode router.
When the user executed SLIST from the workstations, both servers showed on each side of the network. Workstations on the Token-Ring side could connect to both servers. Workstations on the Ethernet-side received one of the following messages when trying to attach to the Token-Ring server.
┌─────────────────────┐
│File server not found│
└─────────────────────┘
┌───────────────────────────────┐
│Unable to attach to file server│
└───────────────────────────────┘
Track "On" showed all get nearest server packets transiting the router.
SOLUTION
Digital Communications Associates Inc. (DCA) has a new TOK380.DCA driver (v1.2). Using the new driver solved both problems.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Windows and Queue Corruption with Norton Virus TSR
DOCUMENT ID#: FYI.P.4800
DATE: 11MAR92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM:
Print jobs in the queue were corrupted. The user tried the WINUP5.ZIP file hoping that it would fix the problem but it did not.
ISSUE/PROBLEM
The problem was being caused by loading the Norton virus terminate-and-stay resident (TSR) into high memory.
SOLUTION
When the user loaded the TSR into low memory, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Mountain Tape Software for NetWare v2.0a
DOCUMENT ID#: FYI.P.5644
DATE: 04MAR92
PRODUCT: NetWare
PRODUCT VERSION: v2.0a
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Configuration:
Mountain Tape backup software v5.1 and v5.21
The Backup skipped every file on the server.
SOLUTION
Mountain Company said the problem is a known problem with these versions. The 5.3MT is a newer release available on their BBS, 408-438-2665. For v2.0a, the user needs version 4.8MT. The 5.3 version has not been tested with v2.0a NetWare.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Losing Search Mappings when Using Norton Commander
DOCUMENT ID#: FYI.P.5514
DATE: 12FEB92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user could not map search drives. The search mappings were lost whether the command was issued at the command line or from the login script.
ISSUE/PROBLEM
The Norton Commander utility, which the user loaded in the AUTOEXEC.BAT at the workstation, deleted the mappings when using XMSNET or NETX with DOS 5.0.
SOLUTION
When the user stopped using the Norton Commander utility, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "A File Server Could Not Be Found" - Bocaram Card
DOCUMENT ID#: FYI.P.5312
DATE: 25JAN92
PRODUCT: NetWare ELS II
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM:
The user's system displayed the following error:
┌─────────────────────────────────┐
│A File Server could not be found.│
└─────────────────────────────────┘
ISSUE/PROBLEM
The user could not find any card that was in conflict with interrupt line 3 setting of the network interface card in the server. All other communication configurations checked out.
The Bocaram serial/parallel card has the logic for an additional COM and LPT port. These ports were not installed, but were enabled on the card. The COM2 port was conflicting with the interrupt line 3 setting on the network interface card.
SOLUTION
After disabling COM2, everything worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Running DOS 5.0 at workstation with MSCDEX v2.2 that ships with Panasonic CD-ROM produced the following error:
┌───────────────────────────┐
│Invalid drive specification│
└───────────────────────────┘
It worked fine running DOS 3.3 and 4.01.
SOLUTION
Using DOSUP5.ZIP solved the problem.
DOSUP5.ZIP is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Invalid Process ID Passed" Lost CMOS Setup
DOCUMENT ID#: FYI.P.5314
DATE: 25JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.15
SUPERSEDES: NA
SYMPTOM:
The user was changing from nondedicated to dedicated. During the process of writing the operating system, SYSTEM, and PUBLIC files to disk, the system crashed. Rebooting the machine returned the following error:
The user could not boot operating system from diskette. NETGEN returned the same error.
ISSUE/PROBLEM
The hard drive had lost its CMOS setup. No error was displayed, or the user missed it.
SOLUTION
When the user set the drive type and finished the installation, everything was fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Mirror Copies of FAT Don't Match" - TMC-950
DOCUMENT ID#: FYI.P.5316
DATE: 25JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Mirror Copies of FAT Don't Match."
ISSUE/PROBLEM
Configuration:
■Future Domain TMC-950 disk controller
■Two Maxtor 8760 drives
■One Hewlett-Packard 661 MB drive
■One Maxtor 1.6 MB drive
A USR: volume that spanned across three drives received the following error:
┌─────────────────────────────────┐
│Mirror Copies of FAT Don't Match.│
└─────────────────────────────────┘
Three other volumes on the system were fine. Repeated tries to run VREPAIR resulted in no errors found.
SOLUTION
The user got an updated driver from Future Domain. This driver enabled VREPAIR to repair the volume. It also allowed the user to finish setting up the 1.6 GB drive that showed as NetWare READY only after the driver upgrade.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error 0068 Displayed from Folio
DOCUMENT ID#: FYI.P.5315
DATE: 25JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user updated and added information to a Folio in Folio v2.0, the system displayed the following error:
┌─────────┐
│Error 068│
└─────────┘
ISSUE/PROBLEM
This error indicates database corruption.
SOLUTION
Using NETX.COM v3.26 and IPX v3.10 solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Invalid COMMAND.COM" v2.2 - DOS
DOCUMENT ID#: FYI.P.5311
DATE: 25JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The same workstation boot disks used under NetWare v2.12 operating system were now giving the following error sporadically after the upgrade to the new IPX and shell v3.02.
┌───────────────────┐
│Invalid COMMAND.COM│
└───────────────────┘
ISSUE/PROBLEM
The appropriate version of COMMAND.COM was being reloaded and COMSPEC was fine.
The user was using a proprietary version of the same version of DOS on the network that was just different enough to mess things up. The user had several different machines on the network.
SOLUTION
When the user switched to using a straight MS-DOS formatted boot diskettes and placed the same version on the server for COMSPEC, everything worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NET 01 08: Unable to Locate File Server
DOCUMENT ID#: FYI.P.5339
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
When the user booted the machine, it displayed the following error after loading NWIFS.IFS in the CONFIG.SYS:
┌────────────────────────────────────────┐
│Net 01 08: Unable to Locate File Server.│
└────────────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
■Installed OS/2 v1.3 standard on WANG PC 386-33
■16 MB RAM
■200 MB hard drive
■3C503 running coax
The syntax of NET.CFG was the following:
PREFERRED SERVER=boston
SOLUTION
Changing the syntax to the following, solved the problem:
PREFERRED=boston
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Abend: Stack Overflow Detected.." - IBM Model 55sx
DOCUMENT ID#: FYI.P.5335
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.0
SUPERSEDES: NA
SYMPTOM:
The system displayed the following error after the user switched printers:
┌─────────────────────────────────────────┐
│Abend: Stack Overflow Detected by kernel.│
└─────────────────────────────────────────┘
The cable and port and everything else stayed the same. When the user switched the printers back, the error disappeared. When the user when back to using the second printer, the errors displayed again.
ISSUE/PROBLEM
Configuration:
IBM 55sx
The user did a diagnostic on the IBM 55sx machine and it passed, but the user still suspected a faulty motherboard.
SOLUTION
When the user replaced the motherboard anyway, the errors disappeared and printing was fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Abend: Segment Not Present Processor Exception.."
DOCUMENT ID#: FYI.P.5333
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The file server stopped and sent the following abend error when the user ran ARCSERVE v4.0:
Disk driver NWIIOP31.DSK v1.05 -- This driver was only certified with NetWare v3.1 and not with the v3.11 operating system.
The problem is an incompatibility with the ARCSERVE version and the disk driver.
SOLUTION
Tricord System Inc. is aware of this problem. They have a new version of the driver, v1.06, dated 01-23-91. When the user used the new driver, the server ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Problems Printing from Windows on Diskless Workstations
DOCUMENT ID#: FYI.P.5322
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user print in Windows using a diskless workstation, the jobs would not print.
ISSUE/PROBLEM
In the Windows setup, the directory that Windows uses to create temporary print files was set to the C: drive. The user did not have a C: drive.
SOLUTION
Changing the drive to point to the user directory on the F: drive solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Proteon BBS and Technical Support Numbers to Upgrade Drivers
DOCUMENT ID#: FYI.P.5318
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How do I get the newest drivers (upgrade) for my Proteon Token-Ring adapter to fix problems I am experiencing?
SOLUTION
Users are getting their Proteon Token-Ring driver problems fixed by calling Proteon's support hotline and downloading the newest Proteon drivers from Proteon's BBS.
Proteon's technical support line is available to help with BBS file names and other issues.
Examples of the *.ZIP file names:
139xNWWS.ZIP is for all NetWare workstation drivers (such as ODI or Dedicated-IPX) for the Proteon 139x series of Proteon Token-Ring adapters (even contains JUMPERS.EXE).
139xNWFS.ZIP is for all NetWare (v2.x/v3.x OSs) file server drivers for the 139x series of Proteon Token-Ring adapters.
Proteon Inc. BBS phone numbers: 508-898-2154 or 508-898-2164
Proteon Inc. Support hotline: 508-898-3100
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "An Error Occurred in Buffer Number 2"
DOCUMENT ID#: FYI.P.5320
DATE: 24JAN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
While the user tried to log into the network from a workstation, it displayed the following error:
┌────────────────────────────────────┐
│An error occurred in buffer number 2│
└────────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
Compaq/M EISA machine running IBM Token-Ring
An option in the COMPAQ EISA configuration program allows the user to choose a Novell server or another configuration. The user had chosen the Novell server option.
SOLUTION
Changing the option to the "other configuration" option solved the problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "SYS3013 A Loader Module Error Has Occurred"
DOCUMENT ID#: FYI.P.10139
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "SYS3013 A loader module error has occurred"
ISSUE/PROBLEM
When the user tried to run a DOS application on an OS/2, the following error displayed:
┌───────────────────────────────────────────┐
│SYS3013 A loader module error has occurred│
└───────────────────────────────────────────┘
SOLUTION
Install the patches in NSD201.ZIP available on NetWire or NetWare Express.
Note: If a user types HELP SYSnnnn at an OS/2 prompt when a SYS error is returned on an OS2 machine, the system will return more information about the error and a possible action.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Problems Source Routing after Creating New Token-Ring
DOCUMENT ID#: FYI.P.10138
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user loaded the card to the main backbone, the system could recognize all the servers. However, when the user loaded the other card also, the system could not recognize any of the servers across the IBM bridge.
ISSUE/PROBLEM
Configuration:
■ Using Token-Ring, the user created a new ring with a NetWare v3.11 server.
■ They wanted to connect it to the other rings through a source routing bridge.
■ The main backbone was at a network address of 1.
■ They also had a second card in the new server with a net address of 87.
The user was loading the card with the net address of 87 first. Then the user loaded the card to the backbone with the net address of 1, second. Then the user loaded the ROUTE.NLM. The ROUTE.NLM will default to
board 1 when a board is not specified.
SOLUTION
When the user issued a LOAD ROUTE BOARD=2 command, they could recognize all the servers on the other side of the bridge.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Can't Recognize Proteon Token-Ring Driver while Changing Configuration
DOCUMENT ID#: FYI.P.10135
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
Because of making changes in the hardware, the user was changing the configuration of a NetWare v2.2 server. When the user pressed <Insert> on the screen, where the drivers were listed, to select a driver for the Proteon Token-Ring board, the driver was read from the diskette, but it could not be recognized in the available drivers list.
ISSUE/PROBLEM
The former file server machine was a Micro Channel, and the disk driver selected was for a Micro Channel board.
SOLUTION
When the user deleted the Micro Channel driver from the configuration the Proteon driver and all the other non-Micro Channel drivers appeared on the available drivers list.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Reading Partition Table - RLL Drives
DOCUMENT ID#: FYI.P.10247
DATE: 23OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When trying to create the NetWare partition on the drive, the system displayed the following error:
┌──────────────────────────────┐
│Error reading partition table.│
└──────────────────────────────┘
ISSUE/PROBLEM
Configuration:
■Western Digital disk controller WD1007v
■Microscience drive HH2160
The user was trying to use drive type 47 for a Run Length Limited (RLL) drive.
SOLUTION
After changing the drive type to type 1 and setting the controller to translation mode, the user was able to create the NetWare partition on the disk.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: American Power Update to Fix Slow Printing
DOCUMENT ID#: FYI.P.5140
DATE: 08JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Slow printing
ISSUE/PROBLEM
Configuration:
■PSERVER.VAP v1.22
■APC.VAP a UPS VAP from American Power
A printer connected off a nondedicated NetWare v2.2 LPT1 port sometimes printed slowly.
SOLUTION
American Power Conversion Corp. said their APC.VAP v3.14 fixes this problem.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NetWare v2.2 Server Reboots Intermittently - Extra Cable
DOCUMENT ID#: FYI.P.10260
DATE: 26OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2, v3.11
SUPERSEDES: NA
SYMPTOM:
The user's NetWare v2.2 file server intermittently rebooted.
ISSUE/PROBLEM
After the user tried another machine, replaced the Arcnet card, added a power monitor, and regenerated another copy of NET$OS, the symptom still occurred. The user was convinced that the problem was with the NetWare v2.2 operating system because the symptom did not occur until they upgraded.
When the user installed a NetWare v3.11 server, it did the same thing.
When the user upgraded, someone added some extra cable for future growth but had not terminated them.
SOLUTION
After the user removed the extra cables and a laser printer that was on the same circuit as the file server, the file server worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Reported Deleting Files Flagged RW DI from Windows
DOCUMENT ID#: FYI.P.10251
DATE: 26OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM: "Cannot delete <filename> Access denied. Make sure disk is not full or write-protected"
ISSUE/PROBLEM
Using the Windows File Manager to delete files, the user could delete files flagged RO DI, but the system displayed the following error when trying to delete files flagged RW DI:
DOS couples the abilities to modify and delete together under Read-Only.
NetWare separated this ability and made it possible to modify a file but not delete it (RW DI), or made it possible delete a file but not modify it (RO).
To provide compatibility to DOS, by default FLAG RO also gives the user DI rights, and FLAG RW also takes away DI rights; however, you can override it with FLAG RO -DI or FLAG RW DI.
If Windows File Manager locates a file with RO, it issues a DOS call equivalent to FLAG RW, which takes off the DI and allows it to delete the file. However, if the manager locates a file with RW, it only issues the DOS call to delete, which fails.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Abend: NMI" - Installing NACS on Runtime NetWare
DOCUMENT ID#: FYI.P.10254
DATE: 26OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user was installing a NetWare Asynchronous Communications Server (NACS) on NetWare Runtime. Every time they attached a hub to the file server, it received the following error:
┌─────────────────────────────────┐
│ABEND: NMI Non Maskable Interrupt│
└─────────────────────────────────┘
The user tried replacing the following items, but the NMI error still occurred:
■NE1500T
■Hub
■Cable
■Motherboard
■RAM on server
When the user took out the Digiboard, the system still displayed the NMI error.
Even when the user just attached the cable to the RJ45 jack on NE1500T, the system still displayed the NMI error.
ISSUE/PROBLEM
The power supply was too weak.
SOLUTION
When the user replaced the power supply, the error disappeared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Abend: Purgetrustee Found an Entry It Couldn't Deal With"
DOCUMENT ID#: FYI.P.10111
DATE: 12OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Abend: purgetrustee found an entry it couldn't deal with."
ISSUE/PROBLEM
While the user was trying to change the name of supervisor in SYSCON, the system displayed the following abend message:
The same abend displayed when the user tried to bring the server back up.
SOLUTION
Running VREPAIR from VRP31X.ZIP and downing the server solved the problem.
VRP31X.ZIP is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Issues Using TOKEN.LAN LS Option
DOCUMENT ID#: FYI.P.10323
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: TOKEN.LAN would not load.
ISSUE/PROBLEM
Configuration:
■TOKEN.LAN v3.16 and v3.17
■IBM 16/4 Token Ring cards
■Model 80 file server
When loading TOKEN.LAN with the LS option (LOAD TOKEN LS=2), any LS value of two or more keeps the driver from loading. If LS values of 0 or 1 are used, the driver loads and functions fine. The user had the same results from both versions of the driver.
SOLUTION
When the user reran the Reference Disk, the problem went away. Now, both versions of the driver work with the LS option.
Note: This user needed to use LS=8 as specified in the NetWare for SAA documentation.
The documentation reads:
For every eight Link Station (LS=8) connections, you also need to specify one SAP (SAPS=1) on the LOAD line.
The documentation should read:
For every four Link Station (LS=8) connections, you also need to specify one SAP (SAPS=1) on the LOAD line.
The proper syntax for the load statement is the following:
LOAD TOKEN SAPS=2 LS=8.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Disk Capacity Complaints under INSTALL.NLM
DOCUMENT ID#: FYI.P.10320
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Partition size is smaller than what the user expects.
ISSUE/PROBLEM
Users often complain about the partition size being smaller than they expect.
SOLUTION
Some of the difference between what the user expects to see and what INSTALL reports is because of the way Novell defines a megabyte or gigabyte.
In pure mathematical terms, the megabyte prefix is ten to the sixth power or one million.
DOS's FDISK and Novell's INSTALL utilities use what is termed "binary" megabytes and gigabytes. The "binary" megabyte is two to the twentieth power or 1024 x 1024.
The following table illustrates the different representation:
Disk drive manufacturers use the decimal representation to specify their drive sizes. Example using an actual drive:
The Maxtor XT-8760S is specified at:
768.9MB unformatted
675.6MB (decimal) formatted
The binary representation of 675,600,000 is (675,600,000/1,048,576) = 644.3 MB (binary).
When viewing a partition size under Novell's INSTALL utility, the user can multiply by 1.049 to get the approximate decimal representation. So, if the partition size is 985.4 MB, it is approximately 985,400,000 x 1.049 or 1,033,680,000 bytes.
The difference is that the two representations will not reconcile all the difference between what the user sees and what is expected, but it covers a good part of it.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Network Spooler Error - EtherExpress 16 NIC
DOCUMENT ID#: FYI.P.10318
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11, v2.2
SUPERSEDES: NA
SYMPTOM: "Network spooler error"
ISSUE/PROBLEM
When the user loaded IPX and NETX on a PS/2 Model 30 that had an Intel EtherExpress 16 NIC, the system displayed the following error:
┌─────────────────────┐
│Network spooler error│
└─────────────────────┘
SOLUTION
When the user downloaded a new OBJ file from Intel for the EtherExpress 16 NIC, and regenerated with the current IPX 3.10, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: INSTALL Hanging after It Is Loaded - PROSERV.NLM, TAPEDRV.NLM
DOCUMENT ID#: FYI.P.10314
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: INSTALL hanging
ISSUE/PROBLEM
INSTALL kept hanging after it was loaded. The user could not access any of the menus.
SOLUTION
When the user unloaded the PROSERV.NLM and TAPEDRV.NLM, everything worked fine. After the user reconfigured the Adaptec cards (even though the reference program said everything was fine) and reloaded TAPEDRV and PROSERVE with the new configuration, the system worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Limit of SPX Connections for IPX.OBJ and IPXODI.COM
DOCUMENT ID#: FYI.P.10312
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the maximum amount of SPX sessions allowed?
SOLUTION
The SPX session limit for IPX.OBJ 3.1 and the newest version of IPXODI.COM is 150.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Setting Environment Variable Equal to DOS Variable
DOCUMENT ID#: FYI.P.10311
DATE: 28OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user wanted to set an environment variable in the system login script equal to the value of the path variable.
SOLUTION
The following is the syntax Novell used in the login script:
DOS SET NETPATH="%<PATH>"
Replace NETPATH with the name of the new variable.
The user was trying to set NETPATH=path+network mappings. The end goal was to get the path set up so that the local drive mappings came first, followed by network drives Z:, Y:, and .... After setting NETPATH, the user would make path=NETPATH.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Requester v1.3 Named Pipes Inter-operating with v2.0
DOCUMENT ID#: FYI.P.10310
DATE: 27OCT92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: v1.3, v2.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Some users are wondering whether OS/2 1.3 Named Pipe clients using NetWare Requester would be able to inter-operate with Named Pipe servers running v2.0 and Novell's requester (and vice versa). The user had been told that there were problems.
SOLUTION
No changes have been made to the named pipe protocol. Therefore, a named pipe request looks the same from a 1.3 machine and a 2.0 machine. The only issues that could come into play would be configuration differences at the Link Support Layer (such as buffers ...).
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Loading Software on Networth NAE Machines
DOCUMENT ID#: FYI.P.10309
DATE: 27OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Unable to load software because of no A: drive on the server
ISSUE/PROBLEM
The new Networth NetWare Application Engine (NAE) machines are like a diskless workstation. These machines do not have an A: drive or keyboard, and the monitor is optional. These machines use IPX and SPX calls with a modified DOSGEN to help in loading the server on the machines.
A consultant for Networth called wanting to know how to load software that needs to be loaded from the A: drive. He wanted the code to Novell's PATCHMAN.NLM so he could modify it to patch the CLIB to replace the seven DOS function calls with his own calls to redirect the input and output to a drive on a workstation.
SOLUTION
Because PATCHMAN.NLM code is proprietary, Novell recommends using the following procedures to load NetWare for SAA on the server:
1. Load the files onto the C: drive of the server on the DOS partition. Then load the SAA software from there to the server itself.
2. Get the files out onto the C: drive by using RCONSOLE from a workstation.
a. When in RCONSOLE, press <*> and a menu of options will come up.
b. Choose the option to copy the files to the server.
c. Type the source path first (A:\filename), then type the destination on the server (C:).
3. Then copy the files to the server drives or to the DOS side of the drive on the NetWare v3.11 server.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Using Publisher's Power Pack with DR DOS
DOCUMENT ID#: FYI.P.10304
DATE: 27OCT92
PRODUCT: DRDOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Atech, the makers of Publisher's Power Pack v3.0, recommend doing the following when using DR DOS and Power Pack.
1. To print, run memmax -u>nul
2. To INSTALL, create a Power Pack directory.
3. To use the FM option to change fonts, delete the PRS file before going into FM.
For more information, call 1-619-438-2244.
SOLUTION
NA
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Batch File Not Found" - NetWare v2.2 Remote Boot
DOCUMENT ID#: FYI.P.10307
DATE: 27OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "Batch file not found" while remote booting
ISSUE/PROBLEM
Configuration:
Using NET3.COM from 1988
A user was trying to set up a remote boot with multiple image files. Whenever they had more files than NET$DOS.SYS, the system displayed the following error even though the AUTOEXEC.BAT and other *.BAT files were in the LOGIN subdirectory:
┌────────────────────┐
│Batch file not found│
└────────────────────┘
It worked fine with only a NET$DOS.SYS file.
SOLUTION
After upgrading to NET3.COM from 02-91, the user could remote boot using another image file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Printing Corruption - NetWare, Excel, and Windows v3.1
DOCUMENT ID#: FYI.P.10302
DATE: 27OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user tried to print Excel files to the network printer with truetype fonts and specifying the use of legal size paper and print to fit format, the job had printing corruption in the form of lost characters and misplaced words.
ISSUE/PROBLEM
The user tried PSERVER.NLM v1.22 and v1.22r and the newest RPRINTER both from the server and from the RPRINTER and got the same corruption. Nothing Novell knew of helped solve the problem. When the user contacted Microsoft, they could not help either.
SOLUTION
Another company site that had the same problem quit capturing out side of Windows and set up all print queues from within Windows itself.
Changing to this setup solved the printing problems.
Change the print setup by going into the control panel, into printers, connection, NetWare, and then set the queues to be permanent.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Files in LOGIN Subdirectory Corrupt - NetWare v2.2
DOCUMENT ID#: FYI.P.10301
DATE: 27OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The user just installed a NetWare v2.2 server and ran INSTALL to upload all the utilities. When the user tried to logs into the network, the workstation attached to the server, and displayed the F: drive prompt. When the user typed LOGIN, an error displayed saying that the system was unable to run login. All commands such as MAP or SLIST did not work.
ISSUE/PROBLEM
When the user ran ATTACH from diskette, the workstation attached to the network. The user ran LOGIN from the diskette as well and got right into the network. When the user looked at the files in the LOGIN subdirectory, all the files were size 4096. The same happened in SYSTEM and PUBLIC directories.
The files had been corrupted during INSTALL.
SOLUTION
When the user manually copied everything over, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Report: MIGRATE - 1.08-107 Failed to Open Report File"
DOCUMENT ID#: FYI.P.10232
DATE: 23OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
While executing MIGRATE.EXE and after selecting Volume Destination, Passwords, and pressing F10 to select the migrate method, the system displayed the following error message:
The user executed MIGRATE.EXE from the C: drive and still had the MIGRATE.CFG file.
ISSUE/PROBLEM
Configuration:
Using MIGRATE.EXE dated 08-18-92
When checking CONFIG.SYS for conflicts, the user could not find a CONFIG.SYS file.
SOLUTION
When the user created CONFIG.SYS and put buffers=30 and files=30, MIGRATE.EXE executed just fine.
Novell suggests specifying at least buffers=20 and files=20.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Script Error: Could Not Interpret Line
DOCUMENT ID#: FYI.P.10133
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The user's system displayed the following message:
┌──────────────────────────────────────┐
│Script Error: could not interpret line│
└──────────────────────────────────────┘
ISSUE/PROBLEM
The user had the following line in the System login script:
IF P_STATION="XXXXXXXXXXXX" OR "XXXXXXXXXXXX" THEN.
SOLUTION
The syntax was wrong. After changing line to the following syntax, the system worked fine:
IF P_STATION="XXXXXXXXXXXX" OR P_STATION ="XXXXXXXXXXXX" THEN.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unable to Allocate Memory for New Object EntryRights"
DOCUMENT ID#: FYI.P.10113
DATE: 12OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.x
SUPERSEDES: NA
SYMPTOM:
When running SECURITY.EXE, the following messages are given on the workstation:
In some cases, these messages will scroll up the screen and the workstation may also hang.
ISSUE/PROBLEM
Most of the conventional memory on the machine was used before the user executed SECURITY.EXE.
SOLUTION
When the user freed up conventional memory and executed SECURITY.EXE again, it executed with no errors or warnings.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NET$OS.EXE Hanging at Cold Boot Loader Message
DOCUMENT ID#: FYI.P.10344
DATE: 29OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The user created a dedicated NetWare v2.2 server on the machine. When starting up the machine, it hung when it reached the cold boot loader message.
If the user booted to DOS and then executed NET$OS.EXE, the system displayed the following message:
┌───────────────────────────────────┐
│Program too big to fit into memory.│
└───────────────────────────────────┘
ISSUE/PROBLEM
Configuration:
Unisys 286/8 with 512 KB base memory and 2 MB extended
The NetWare v2.2 operating system requires 640 KB of base memory to load.
SOLUTION
After the user increased the base memory to 640 KB, no more errors occurred.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "GetOriginalNameSpace Could Not Find the Origination Name Space"
DOCUMENT ID#: FYI.P.10338
DATE: 29OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
It is common to see the following error after an upgrade from NetWare v2.15c with MAC support to a NetWare v3.11 operating system:
The error is caused by a corrupt name space entry in the DET (Directory Entry Table).
SOLUTION
Run VREPAIR.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Out of NIC Resources"
DOCUMENT ID#: FYI.P.8984
DATE: 30SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The server came up with the following message:
┌────────────────────┐
│Out of NIC resources│
└────────────────────┘
ISSUE/PROBLEM
With a 3c527 in a Model 95 server, the workstations had performance and connection problems.
SOLUTION
The user used the Reference diskette to turn the Fairness option OFF.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Error Writing to SYS: Volume" - Paddle Board
DOCUMENT ID#: FYI.P.10059
DATE: 08OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
The user's system consistently displayed the following error message:
┌────────────────────────────┐
│Error writing to SYS: volume│
└────────────────────────────┘
The user ran VREPAIR one time and another time had to repartition and reinstall to fix the hard drive, but the symptom still persisted.
ISSUE/PROBLEM
Configuration:
80 MB Maxtor IDE hard drive in a 386 Clone
The user was using a low-end Paddle Board (complete with Game port and other items).
SOLUTION
When the user replaced the board with a higher-end Paddle Board (more well known and certified), the system did not display the error any more.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Known Bugs Fixed by PATCH311.NLM
DOCUMENT ID#: FYI.P.10051
DATE: 08OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user wanted to know specifically what problems are resolved with PATCH311.NLM. PATCH311.NLM is located in PAT311.ZIP available on NetWire or NetWare Express.
SOLUTION
The following is a list of known bugs that are fixed by PATCH311:
NON-API FIXES
Symptom: A multi-threaded NLM performing heavy I/O activity hangs when exiting. The reason is that if a thread is killed in the middle of a stream I/O function, then other threads will hang when they try to access a second-level file still locked by the dead thread.
Symptom: When unloading from the console a special multi-threaded NLM, the server stops and sends an abend message. In a situation when SIGTERM is registered for, and multiple thread groups exist and the signal function waits for termination of these thread groups, an internal variable was being invalidated when control was returned from raise (SIGTERM).
API FIXES
API: readdir
Symptom: Extended file attributes (: TTS bit) are not returned for remote 286 servers.
API: SetCurrentConnection
Symptom: SetCurrentConnection is setting the current working volume and current working directory to zero. This can be a problem if the current working name space is something other than DOS.
API: mkdir
Symptom: On a remote 286 mkdir () fails when the directory name has an extension [: mkdir ("test.xxx) fails]. Note: This error also exists for remote portable.
API: rename
Symptoms: Similar to the remote 286 mkdir bug, on remote 286 rename anyDir and SOMEDIR.EXT fails. Note: This error exists with portable.
API: GetVolumeStatistics
Symptom: The function is typecasting the AvailableBlocks member from a LONG to a WORD. This is truncating the upper word of this field, thus returning an invalid number AvailableBlocks on large volumes.
API: _FSFD
Symptom: This support function is used to convert a float number (4 bytes) into a double. It falls into an infinite loop if -0.0 represented as 80000000H is passed to the function.
API: ClearConnectionNumber
Symptom: ClearConnectionNumber does not clear the connection if the workstation is only attached.
API: open
Symptom: Open fails on remote portable servers.
API: fcloseall
Symptom: Standard files (STDIN, STDOUT, STDERR) get closed by this function when they should not be closed.
API: AFPDirectoryEntry
Symptom: AFPDirectoryEntry only works for the SYS: volume.
API: Logout, LogoutFromFileserver
Symptom: Logout and LogoutFromFileserver do not maintain the current working name space.
API: DestroyScreen
Symptom: If a screen has a custom cursor shape when unloading the NLM, it complains about two resources ("Event Notification Call Backs") that were not freed.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM PS/2 Model 8555 Hangs during Remote Boot
DOCUMENT ID#: FYI.P.10050
DATE: 08OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The IBM PS/2 model 8555 hung when the remote boot was executed.
ISSUE/PROBLEM
The user loaded TOKEN.LAN v3.16 (09-09-91) from TOKENB.ZIP and RPL.NLM v4.01 (05-28-92) from RPLB.ZIP. The LOGIN directory contained TOKEN.RPL v4.01 (06-15-92) from TOKENB.ZIP and NET$DOS.SYS created from an IBM DOS 5.0 bootable diskette containing the following:
COMMAND.COM
IPX.COM v3.10 linked with STOKEN.OBJ v2.63
NETX.COM v3.26
AUTOEXEC.BAT
IPX
NETX
The wrong version of TOKEN.RPL was loaded into the file server's memory when RPL.NLM was loaded. The original TOKEN.RPL (11-01-90) wrote over part of DOS 5.0 and DOS 6.0 transient portion of COMMAND.COM.
SOLUTION
When the Novell Remote Program Loader message appeared on the workstation screen, it displayed as v1.30. TOKEN.RPL v1.30 (11-01-90) is an old version that shipped with the NetWare v3.11 operating system and was installed in the LOGIN directory. TOKEN.RPL v4.01 (06-15-92) should be used with RPL.NLM v4.01 (05-28-92). Deleting TOKEN.RPL v1.3 from the LOGIN directory and copying the correct TOKEN.RPL v4.01 to the LOGIN directory was not enough.
Unload the RPL.NLM then load it with the correct version of TOKEN.RPL (06-15-92). When RPL.NLM loads, it will search the SYS:LOGIN directory for a RPL file. The Remote Program Load (RPL) file is loaded by RPL.NLM into the file server's memory. Then bind RPL to TOKEN.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PCONSOLE Reporting Serial Printer Is Offline
DOCUMENT ID#: FYI.P.10040
DATE: 06OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The PSERVER.NLM Parallel server was working fine, but serial printer would not print. PCONSOLE reports this printer is offline.
ISSUE/PROBLEM
Configuration:
Running with a parallel printer and a serial printer both off the server.
Most printers can be setup with hardware or software handshaking (a dip switch). If the switch is set to the "hardware" setting, then Xon/Xoff is OFF at the printer. If the switch is set to the "software" setting, then Xon/Xoff is ON. This should be set the same in PCONSOLE.
SOLUTION
When the user turned the Xon/Xoff switch to ON in PCONSOLE, the serial printer started printing.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Writing FAT Table after Upgrade - DTC 6180
DOCUMENT ID#: FYI.P.10034
DATE: 06OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user did an upgrade from a NetWare v2.11 to v3.11 operating system. The user talked to Novell before the upgrade and they suggested using the newer ISADISK dated 07-20-92 from ISA311.ZIP. After the upgrade, the server kept getting error writing to FAT table and drive deactivation.
ISSUE/PROBLEM
Configuration:
■DTC 6180 controller
■Micropolis 1558 drive
DTC said the following:
"Please be advised, all users that use DTC products must use the ISADISK driver dated 02-15-91, file size 10415. We have had reports that when users attempt to use the NEW Novell v3.11 ISADISK.DSK driver, problems with drive deactivation occur. Lastly, DTC has not tested the new driver available from Novell. The original driver is recommended for use with all DTC ESDI products."
SOLUTION
When the user changed back to the original ISADISK, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Load Ethernet_802.3 Frame Type with Intel Driver
DOCUMENT ID#: FYI.P.10033
DATE: 06OCT92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM: Cannot load frame type Ethernet_802.3 with Intel driver.
ISSUE/PROBLEM
When the user used the NET.CFG shown below, the frame type is not recognized.
link driver exp16odi
int 10
frame ethernet_802.3
SOLUTION
When the user added the "protocol ipx 0 ethernet_802.3" line to the NET.CFG as shown below, the new frame loaded without a problem:
link driver exp16odi
int 10
frame ethernet_802.3
protocol ipx 0 ethernet_802.3
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Network Functions Disabled after Running NWSETUP
DOCUMENT ID#: FYI.P.10029
DATE: 06OCT92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
The user updated the Windows v3.1 using the DOS/Windows Workstation Update Kit (v2.0). When restarting Windows, the system displayed the following error message:
The SYSTEM.INI file had the following line under the [386Enh] section:
network=*dosnet,*vnetbios,vNetWare.386,vipx.386
SOLUTION
When the user removed the *dosnet line from the SYSTEM.INI file, Windows loaded as expected (with no errors).
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Sticking Shift Key Using dBASE IV, Excel, and WordPerfect
DOCUMENT ID#: FYI.P.10025
DATE: 07OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Sticking Shift key
ISSUE/PROBLEM
Configuration:
■Using dBASE IV, Excel, and WordPerfect on many different types of workstations with different configurations.
■Running on an Ethernet topology
After the user swapped out keyboards and tried KBDFIX.EXE and INT9FIX.EXE, the Shift key still continued to stick. When the user rapidly depressed one of the Shift keys, the problem went away for a little while.
SOLUTION
When the user changed from a dedicated shell to an ODI shell, the sticking Shift key went away.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NetWare v3.11 Abend Binding Second Mylex Card
DOCUMENT ID#: FYI.P.8858
DATE: 18SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user could LOAD and BIND the first LAN card with no problem. When the user loaded the second LAN card, the system displayed a message that the second card could not be loaded or the server sent an ABEND message.
When the user changed cards and drivers, the same problem occurred. When the user tried Intel LAN cards, the same problem still occurred.
ISSUE/PROBLEM
Configuration:
■EISA 486/50
■Two - Mylex LNE390 Ethernet cards
■Two - AMI EISA fast SCSI controllers
■Four - 1.2 GB drives (two off each controller)
■VGA
■DOS 5.0
■64 MB of RAM
The user needed to use the NAME option when loading the cards in the AUTOEXEC.NCF file.
SOLUTION
After the user changed the AUTOEXEC.NCF file, the server came up and functioned fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Opening Image File - NetWare v3.11
DOCUMENT ID#: FYI.P.8804
DATE: 17SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user had two image files on the network, Ethernet and Arcnet. The user created the NET$DOS.SYS with DOSGEN and then renamed the file to ETHER.SYS. Then, the user created the Arcnet image file and kept it as NET$DOS.SYS. When the user created the BOOTCONF.SYS, everything looked fine. However, when trying to get the Ethernet stations booted up, the system displayed opening image file errors. It appeared that they were trying to open the Arcnet image file.
ISSUE/PROBLEM
The user used the Node IDs received from SESSION.EXE in the BOOTCONF.SYS file. These numbers have been known to be incorrect.
SOLUTION
Novell suggested that the user log in all the Ethernet stations, use USERLIST /A, and use the Node IDs listed there. When the user switched to the new IDs, the stations came up fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: GPPE Error when Remote Workstations Log in across Newport Boards
DOCUMENT ID#: FYI.P.8754
DATE: 04SEP92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
Local workstations could log in fine. However, after the remote workstations logged in over the WAN, the server received GPPE messages.
ISSUE/PROBLEM
Configuration:
■NetWare v3.11 operating system
■Wide Area Network (WAN) installed with Newport boards and 56 KB lines
The user was using older IPX and shells from NetWare v2.15 at the remote workstations.
SOLUTION
After upgrading the IPX and shells to the newer versions in DOSUP5.ZIP, the remote workstations logged in and the server stayed up.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Maximum Number of Allowed Connections...Are Used"
DOCUMENT ID#: FYI.P.8718
DATE: 02SEP92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "Maximum number of allowed connections on this server are used. You must wait until another user logs out"
ISSUE/PROBLEM
Configuration:
■NetWare v2.2, five-user version
■PSERVER v1.21 and v1.22
The user was running fine with PSERVER v1.21. When the user upgraded to PSERVER v1.22, the system displayed the following message when the fifth user tried to log in the system:
After testing, Novell found that all PSERVER versions listed below should work because none of them took a user connection on a NetWare v2.2 five-user version.
PSERVER.VAP 02-11-91 64130 V1.21
PSERVER.VAP 07-10-91 64994 v1.22
PSERVER.VAP 02-27-92 65202 v1.22R
In this case, the user went back to using PSERVER v1.21.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Server Going into Debugger after Upgrade
DOCUMENT ID#: FYI.P.10021
DATE: 07OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user did an upgrade from a NetWare v2.2 to v3.11 operating system, everything looked fine. When the Supervisor went into user information of SYSCON, highlighted a user, and selected the "Change Password" option, the workstation hung and the sever went into the debugger.
ISSUE/PROBLEM
The user ran BINDFIX, VREPAIR, and tried setting unencrypted passwords to ON, but nothing seemed to fix the problem.
SOLUTION
After the user recreated the binderies, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: RPL.NLM and ETHER.RPL with the SMC 3016.
DOCUMENT ID#: FYI.P.10015
DATE: 07OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the diskless workstations were brought up, the packets received parameter at the server never incremented when the packets were sent from the diskless workstation.
ISSUE/PROBLEM
Configuration:
■ An SMC 3016 board was used at the server.
■ The driver was loaded twice once with Ethernet_802.3 frame type and once with Ethernet_802.2 frame type.
■ IPX was bound to both frame types.
■ RPL was bound to the Ethernet_802.2 frame type.
The SMC 3016 board does not work with RPL.NLM even though everything appears to load properly.
SOLUTION
The user had to change to another board (and driver) in the server. SMC does have other Ethernet boards (other than the 3016 boards) that will work.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Trap 0003 with Device IPX$" - NetWare Requester
DOCUMENT ID#: FYI.P.9029
DATE: 02OCT92
PRODUCT: NetWare Requester For OS/2
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM:
Every time the user tried to execute any program whether from an OS/2 session or DOS session from the network, the system displayed the following message:
┌──────────────────────────┐
│Trap 0003 with device IPX$│
└──────────────────────────┘
The user was able to log in and MAP drives without any problem.
ISSUE/PROBLEM
The user was using IPX dated 05-06-92.
SOLUTION
After the user applied the NSD201.ZIP patch that contains a new IPX.SYS file dated 06-30-92, the error did not display.
The NSD201.ZIP file is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Files Left Open on NetWare v2.11 Server, OS/2 Requester
DOCUMENT ID#: FYI.P.8587
DATE: 20AUG92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM:
Files left open on a NetWare v2.11 file server were taking up file handles and not allowing other users to access the files from the network.
ISSUE/PROBLEM
A Close file NetWare Core Protocol (NCP) is not in the NetWare v2.12 and below operating system.
SOLUTION
The NCP became available in v2.15 and above. The solution is to upgrade to NetWare v2.15c or above software.
Page 2 of the OS/2 Requester v1.3 manual states that NetWare v2.15c is required for using the NetWare Requester for OS/2 product. NetWare v2.15c is where the File locking issue was fixed.
The symptoms that occur on a lesser version of NetWare are the following:
If a text file is open from a NetWare volume with the OS/2 editor and changes are made, the file cannot be saved back to the volume by the same name because the file is locked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: DIR Shows Zero Bytes Free after Mountain Data Restore
DOCUMENT ID#: FYI.P.8499
DATE: 07AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
After restoring data from Mountain v5.3, a DOS DIR command showed 0 bytes free.
ISSUE/PROBLEM
In DSPACE under the "Directory Restrictions" option and "Vol SYS" selection, the "restrictions" parameter was set to Y.
SOLUTION
When the user set the "restrictions" parameter to NO, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error "SYS$MSG.DAT Cannot Be Opened" with Netware 2.0 Requester
DOCUMENT ID#: FYI.P.8495
DATE: 07AUG92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: 2.0
SUPERSEDES: NA
SYMPTOM:
When the user logged into the server and tried to run PCONSOLE, SYSCON, or other PUBLIC utilities, the system failed to run the utility and sent the following message:
┌────────────────────────────┐
│SYS$MSG.DAT cannot be opened│
└────────────────────────────┘
ISSUE/PROBLEM
These utilities were on the user's local drive.
SOLUTION
Two solutions to the problem are the following:
1. Place the files in a Network directory and default to that directory so the utilities will work.
2. Copy the SYS$MSG.DAT and other files that Novell utilities use to the local drive.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cache Pool Decreasing to Minimum - FATFIX Patch
DOCUMENT ID#: FYI.P.8457
DATE: 04AUG92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When upgrading from the NetWare v2.12 to v3.11 operating system, the user applied all patches from 311PTX.ZIP. Over time, the cache pool decreased to the minimum defined by SET MINIMUM FILE CACHE BUFFERS.
ISSUE/PROBLEM
Through MONITOR -p, the user discovered that the turbo indexing process had accumulated 9 MB.
SOLUTION
When the user removed the FATFIX patch, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: No EXCLUDE Parameter for LAN Card Causes Problems
DOCUMENT ID#: FYI.P.8439
DATE: 04AUG92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM:
The user had difficulty logging into the network with DR DOS 6.0.
ISSUE/PROBLEM
Configuration:
■Card - Western Digital Star Ethernet+ v3.06
■Memory - C400-CFFF
■IPX - v3.01
■NETX - v3.22 (from DR DOS 6.0)
Novell had the user check the settings for the card and IPX option. The EMM386.SYS file did not have an /EXCLUDE command for the LAN card's memory area.
SOLUTION
After adding the /EXCLUDE command to the EMM386.SYS (/E=C400-CFFF), the user booted and logged onto the network with no difficulty.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "A File Server Could Not Be Found" - Network and Node Address Set at 1
DOCUMENT ID#: FYI.P.8261
DATE: 22JUL92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
While trying to log in to a NetWare v2.2 nondedicated server from the nondedicated workstation, the system displayed the following message:
┌─────────────────────────────────┐
│A File Server could not be found.│
└─────────────────────────────────┘
ISSUE/PROBLEM
The user set both the network and node address to 1.
SOLUTION
After the user changed the node address to 10, the system worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The user was trying to install OS/2 v2.0 utilities onto a NetWare v2.15a server. During the attempt to copy the utilities, the system displayed the following error message:
┌───────────────────────────┐
│Error Unable to Copy File 0│
└───────────────────────────┘
ISSUE/PROBLEM
This user had previously installed the requester utilities for OS/2 v1.3. While they were installed, some of the files were flagged as Read-Only.
SOLUTION
After the user reflagged the original OS/2 v1.3 files to read/write, the installation went smoothly.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Runtime Version of SERVER.EXE...File Server Not Found
DOCUMENT ID#: FYI.P.8169
DATE: 10JUL92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user did a new install of NetWare v3.11 and connected one workstation to server to set up the system. If the user rebooted the workstation, the system displayed the following error when trying to load NETX:
┌─────────────────────────────────┐
│A File Server could not be found.│
└─────────────────────────────────┘
The user had to shut down the file server and bring it back up to be able to log in again. Then they could log in one time before experiencing the same problem when rebooting.
ISSUE/PROBLEM
The user was using the Runtime version of SERVER.EXE that allows only one connection.
When the user watched track on the first time they ran NETX, they saw "getnearestserver" and "givenearestserver" packets. The second time, they saw many "get" but never any "give" packets. When the connection was cleared, the user could log in again. Watching this process is how the user realized that they had the one-user version of SERVER.EXE installed.
SOLUTION
When the user switched to the correct version, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Cache Memory Allocation Memory Error..."
DOCUMENT ID#: FYI.P.8038
DATE: 26JUN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Cache memory allocation memory error. 7 buffers of 6144 bytes have been allocated. 1.1.39 cache memory allocator out of available memory."
This error is usually solved by using the Register Memory command before disk drivers are loaded. See FYI.P.4044. The solution for this user was to Set Reserve Buffers Below 16 MEG = 30.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Problems Deleting Server from a Domain
DOCUMENT ID#: FYI.P.7765
DATE: 03JUN92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user removed a server from a domain and set it up in another location as a stand alone server. He said he deleted the server from the domain before removing it. When the user tried to change such items as the supervisor password or change printing parameter, the system denied him access and appeared to be part of the previous domain. When he used NETCON to try again to delete the server from the domain, the system displayed the following error:
┌────────────────────────────┐
│Cannot Delete Primary Domain│
└────────────────────────────┘
After the user replaced all the NNS utilities with the original NetWare v3.11 utilities and ran BINDFIX, it did not find any errors, and the problem persisted.
ISSUE/PROBLEM
Configuration:
NetWare Name Service (NNS)
The user had changed the name of the server when setting it up in the new location. The old name probably was not deleted from the original domain when it was moved. Properties associated with the original server name appeared legitimate to BINDFIX.
SOLUTION
When the user renamed the server to the original name and deleted it from the domain, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "VIEWS.COM Not Loaded" NetWare v2.2 and Previews v2.1
DOCUMENT ID#: FYI.P.7246
DATE: 21APR92
PRODUCT: NetWare
PRODUCT VERSION: V2.2
SUPERSEDES: NA
SYMPTOM:
When the user typed HELP on a NetWare v2.2 server (Folio Views v2.1) and tried to access an external program (VIEWER.EXE) by selecting the appropriate tab, the system displayed the following error message:
┌───────────────────────────────────────────┐
│VIEWS.COM not loaded. Press ESC to continue│
└───────────────────────────────────────────┘
ISSUE/PROBLEM
When VIEW.COM is not loaded the user is not able to launch an external program.
SOLUTION
Two workarounds for this problem are the following:
Workaround 1. Place NFOLIO.COM in the PUBLIC directory. If you cannot find NFOLIO.COM on your distribution diskettes, then download HELP2A.ZIP from NetWire or NetWare Express.
Workaround 2. Instead of typing HELP to initiate Previews, type PREVIEWS and highlight the appropriate NFO.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unknown Error Returned by Attach 89E7" - NetWare v2.2
DOCUMENT ID#: FYI.P.5971
DATE: 30MAR92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
When the user tried to connect to the file server, the system displayed the following error message:
┌───────────────────────────────────────┐
│Unknown error returned by attach (89E7)│
└───────────────────────────────────────┘
ISSUE/PROBLEM
This error can occur if the target server has exceeded the maximum number of user connections.
SOLUTION
Reduce the number of connection by having a user log out or get a larger user version of NetWare.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "DOS Shell Error - Could Not Find 'Comspec'.." NetWare v3.11
DOCUMENT ID#: FYI.P.5917
DATE: 24MAR92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user tried to print from an application called from Windows, the system displayed the following error:
Windows would load with Norton's desktop. The user had a PIF file for a DOS application that they loaded from within Windows. When the user tried to call the DOS prompt from Windows, the system displayed errors like the one above and others such as those shown below:
┌───────────────────┐
│invalid command.com│
└───────────────────┘
┌───────────────────────┐
│cannot find command.com│
└───────────────────────┘
ISSUE/PROBLEM
The symptom was caused from a conflict.
SOLUTION
Put an EMMExclude a000-efff in the [386enh] section of the SYSTEM.INI file and that did it.
The following is a quotation from the Microsoft Windows Resource Kit concerning the EMMExclude command:
"To explicitly exclude an area of the upper memory block Adapter Segment from mapping by Windows 3.0 Enhanced Mode, use the 'EMMExclude' statement. The 'EMMExclude' parameter accepts a four-digit hexadecimal memory range, such as EMMExclude=E000-EFFF. Since there is no standard for hardware implementation of the E000-EFFF area, it is frequently necessary to exclude this range, so that Enhanced Mode can function properly. Most adapter cards will be automatically detected and excluded by Windows 3.0 Enhanced Mode.
If you suspect an upper memory block conflict, use 'EMMExclude.' There are very few uses for the "EMMInclude=" statement. Normally, Windows 3.0 Enhanced Mode will automatically use all free pages in the upper memory block."
If you are troubleshooting this type of problem using EMMExcluding A000-EFFF, try reducing the area EMMExcluded until the conflict is found. For example, EMMExclude A000-EFFF may cause the problem to disappear, but the conflict may be at D000-D3FF.
By EMMExcluding the whole of A000-EFFF, you deny Windows memory it could use. Also, remember that multiple EMMExclude statements are permissible.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PRINTCON.DAT File Not Saved in PRINTCON - NetWare v2.2 Upgrade
DOCUMENT ID#: FYI.P.5754
DATE: 13MAR92
PRODUCT: NetWare
PRODUCT VERSION: v2.15, v2.2
SUPERSEDES: NA
SYMPTOM:
The user was upgrading from a NetWare v2.15 to v2.2 operating system and upgrading hardware. The user backed up the binderies to a diskette, installed the NetWare v2.2 operating system, ran BINDREST to the NetWare v2.2 server, and restored the data from tape. After making these changes, the user could not get PRINTCON to save PRINTCON.DAT files. However, when the user logged in with a supervisor equivalency, he could get the files to save.
The user tried copying the PRINTCON.DAT that worked to the MAIL directories of the other users. The file was there but was not accessible to the users. If the security equivalence was changed to supervisor, the users could see and use the job definition.
ISSUE/PROBLEM
The user decided it must be a bindery problem left over from the old file server.
SOLUTION
When the user deleted the users and recreated them, PRINTCON worked fine. He had not used MAKEUSER to create the network user first.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Incomplete Packet Errors and Database Corruption
DOCUMENT ID#: FYI.P.5750
DATE: 11MAR92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user's system kept getting incomplete packet error, and the database kept getting corrupted.
ISSUE/PROBLEM
If the media header of the packet is corrupted, it will never make it past the LAN driver.
If the media header and protocol identifications are fine and the corrupted packet is not too short or too long, it will pass the driver. However, the operating system, the router, or the protocol stack will catch it unless the IPX header has been corrupted or the packet length does not match the actual length of the packet.
All these corrupted packets get thrown away and retried. However, if the data part of a packet gets corrupted without effecting the headers and the packet size, as in the case of this user it could corrupt the database if it is not caught by the application.
SOLUTION
Update the drivers. Check the cabling and LAN boards.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Duplexing Micropolis Drives with Two Ultrastor 12F Controllers
DOCUMENT ID#: FYI.P.5641
DATE: 04MAR92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user was duplexing using ISADISK driver v2.10 dated 12-19-90. The user wanted to duplex two Micropolis 300 MB drives with two Ultrastor 12F controllers. The server is a Dell System 310.
SOLUTION
After talking to Dell, the user briefly explained the procedure he took to set up the drives. These steps must be repeated for each drive:
1. Run debug and choose the "drive parameter setup" option to set all options to the "no" parameter.
2. Save and reboot.
3. Run debug again and choose the "drive preparation" option.
4. Set "auto format" option to the "brief -n" parameter (the N is for Novell).
Call Dell Computer Corp. for more information on this procedure.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Unable to Login to File Server" - NetWare v3.11, PSERVER.EXE
DOCUMENT ID#: FYI.P.9017
DATE: 03OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user loaded PSERVER.EXE from the network or local hard drive, the system displayed the following error:
┌──────────────────────────────┐
│Unable to login to file server│
└──────────────────────────────┘
ISSUE/PROBLEM
Configuration:
Dedicated print server on a Netware v3.11 network
The user had recently upgraded from a NetWare v2.15 to v3.11 operating system and still had IPX v3.01b.
SOLUTION
When the user changed to IPX v3.02, PSERVER would load and connect.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "No Print Server Available" after NetWare v3.11 Upgrade
DOCUMENT ID#: FYI.P.10081
DATE: 09OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user had just upgraded from NetWare v2.2 to v3.11 operating system. When running capture at the workstation, the system displayed the following error message:
┌─────────────────────────┐
│No print server available│
└─────────────────────────┘
The user was logged in as Supervisor, and everything in PCONSOLE and the CAPTURE statement was in order.
ISSUE/PROBLEM
The user Supervisor was not assigned to the group EVERYONE.
SOLUTION
After the user reassigned Supervisor to the group EVERYONE, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Search Mode=5 Stops Working after a Hard Server Crash
DOCUMENT ID#: FYI.P.10075
DATE: 09OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
After a hard server crash, the SEARCH MODE=5 parameter in the SHELL.CFG (NET.CFG) quit working.
ISSUE/PROBLEM
After a the server experienced a hard crash, it came back up with no errors; but the SEARCH MODE=5 parameter in the SHELL.CFG (NET.CFG) quit working.
SOLUTION
After the user ran the new VREPAIR (VRP31X.ZIP available on NetWire or NetWare Express), the server ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Loader Cannot Find Public Symbol..." Requester
DOCUMENT ID#: FYI.P.10074
DATE: 09OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Loader can not find public symbol: SpxListenForConnectedPacket"
ISSUE/PROBLEM
The user was loading the NetWare Management software package. When the user tried to load the RATTLER.NLM on the server both at the console and by remote, the system displayed the following message:
Three NLMs in 311PTX.ZIP are for OS/2 machines. After the user loaded SPXFSFIX.NLM, SPXFIX1.NLM, and OSOPNFX.NLM, the NetWare Management software loaded properly.
The file 311PT9.ZIP is available on NetWire or NetWare Express.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Novell NetBIOS Failing with IBM Extended Services
DOCUMENT ID#: FYI.P.10069
DATE: 09OCT92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM:
Novell's NetBIOS was failing with IBM v1.0 Extended Services (ES) and Lotus Notes loaded on an v2.0 OS2 client. Without ES, it worked as advertised.
ISSUE/PROBLEM
The NETAPI.DLL that ships with IBM's Extended Services does not have code in it to hand off to Novell's NETSUB.DLL. IBM's Extended Services is supposed to have this call but it does not. With the OS2 kernel debugger, Novell determined that a loop was occurring between Lotus's IBMEENB.DLL and Novell's NBDAEMON.EXE and DDAEMON.EXE. Several different ways that both IBM and Novell NetBIOS work in an OS/2 v2.0 environment are detailed in the NetWare OS/2 Requester manual on pages 7-7 through 7-12 and are graphically shown on pages B-8 through B-12.
SOLUTION
Use the following procedure to provide the necessary code:
1. Copy the following files from the IBM LAN Services diskettes into the C:\MUGLIB\DLL subdirectory structure: NETAPI.DLL 322144 04-01-92, NETSPOOL.DLL 6280 04-01-92.
2. Change Lotus Notes to use NETBIOS.DLL instead of IBMEENB.DLL. Both files are Lotus Notes DLLs located in the Notes subdirectory.
The key issue here is IBM's NETAPI.DLL that ships with Extended Services v1.0 is missing some critical code for coexistence when NetBIOS is involved. If you do not have a copy of IBM's LAN Services, buy it or give IBM a call.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Screens Go Blank Entering Passwords after Power Outage
DOCUMENT ID#: FYI.P.10068
DATE: 09OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: After the user attempted to log in and enter the password, the screen went blank except for a blinking cursor.
ISSUE/PROBLEM
The user's system lost power and the server went down. The user brought the server back up. The user attempted to log in; and after entering the password, the screen went blank except for a blinking cursor. This symptom happened on all workstations, even the nondedicated workstations. The user executed VREPAIR, tried logging in from diskette, and executed BINDKILL, but the problem still existed.
SOLUTION
When logging in with a new script file (Login /s a:\test.log), the user got right in. After the user renamed the NET$LOG.DAT file (the system login script) and recreated it, the network users were then able to login successfully.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: What is NQcount or NQ count?
DOCUMENT ID#: FYI.P.10071
DATE: 09OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is NQcount or NQ count?
SOLUTION
NQcount or NQ count is really EnqueuedSendsCount. This counter increments when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board. (EnqueuedSendsCount is documented on page 466 of the NetWare Version 3.11 System Administration manual.)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Remote Booting Problems with IBM 35ls and DOS 5.0
DOCUMENT ID#: FYI.P.5604
DATE: 21FEB92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: Hanging workstation
ISSUE/PROBLEM
Configuration:
■Using TOKENB.ZIP and RPLFIX.ZIP downloaded from NetWire
■Using DOS 5.0
■Using the IBM boot PROM that came with the machine
The user was trying to remote boot using an IBM Model 35LS on a Token-Ring network. When the user brought the workstation up, it loaded the IPX and NETX, showed that it had attached to the file server, and showed the date and time. Then the cursor went to the next line and just sat there and the machine hung.
SOLUTION
When the user switched from using DOS 5.0 back to DOS 3.31, the workstation worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
■Running NetWare v2.2 nondedicated on a 386 clone with 8 MB RAM.
At the workstation side of the server, the user did a DIR of the A: drive before putting a diskette in the drive. The system displayed an error while reading the A: drive, then the user pressed <Esc> to abort. Then the server locked up. When the user rebooted the server, the operating system loaded and all three volumes mounted. Then when the user tried to login as supervisor (no other users had been created yet), the system displayed the following message:
The system also displayed Divide Overflow errors when the user ran programs at the nondedicated workstation.
The other workstations were diskless, and no boot image file had been created yet; so the user could not log in from another workstation.
SOLUTION
The user finally had to reinstall NetWare v2.2 to be able to login.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: INSTALL or CSINSTAL Hangs Server when Loaded
DOCUMENT ID#: FYI.P.5554
DATE: 18FEB92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: File server hangs
ISSUE/PROBLEM
Whenever the user typed "load install" or "load csinstal" (for SAA), the server hung and no additional keyboard input was allowed. The server executable was still running, but no keyboard input was allowed. When the user tried to load the install modules from the C: drive, the situation did not seem to improve.
Novell suggested using a newer DPT disk controller driver. The user tried using a new controller and a new drive but neither action resolved the problem.
SOLUTION
When the user replaced the 3c505 board with an NE2000, the server worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cannot Install NetWare v2.2 with More Than 12 MB RAM
DOCUMENT ID#: FYI.P.5469
DATE: 06FEB92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM:
A was trying to install NetWare v2.2 software on an Everex Cube 386/33 that had a Future Domain 1680 controller (driver revision 2.11) and a Maxtor Panther 1.7 GB drive. The operating system would not completely install, and the system displayed the following error:
┌────────────────────┐
│No SCSI drives found│
└────────────────────┘
The user could install a NetWare v3.11 operating system with no problem.
When the user tried using an IN2000 controller, the install completed. However, when the user booted the server, it hung when trying to load the operating system.
The user tried a 1.3 GB drive and a 40 MB drive with the same results.
Disabling parity on the drive, slowing the machine down, and using the newest drivers did not remove the symptom either.
ISSUE/PROBLEM
The machine had 16 MB of RAM that was causing the performance problem. The limit for operating a NetWare v2.2 operating system is 12 MB.
SOLUTION
After taking out 4 MB, the user could install NetWare v2.2 software with no problems. It must have been a problem with Direct Memory Access (DMA).
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Applying PS2ISA.ZIP Patch for Model 40
DOCUMENT ID#: FYI.P.5407
DATE: 31JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "File creation error"
ISSUE/PROBLEM
This document pertains to the PS2ISA.ZIP patch on NetWire.
The PS2ISA.ZIP patch fixes system slowdown and keyboard slowdown in Models 40 and 35. Note: The way to apply this patch depends on whether you are installing NetWare by diskette method or hard or network drive method.
The user was trying to use the diskette method. When the user executed Step 9 (run install -N), the system displayed the following error after inserting the SYSTEM-2 diskette and then it continued:
┌───────────────────┐
│file creation error│
└───────────────────┘
At this point, the patch is trying to create the NET$OS.LNK file on the SYSTEM-2 diskette. The user tried Step 9 several times, and each time the NET$OS.LNK file was a different size.
When the user increased the number of files in the CONFIG.SYS and rebooted the machine, the system still displayed the same error. When the user continued with the rest of the procedures for the patch anyway, the keyboard hung after booting the server.
SOLUTION
The user was using DOS 5.0. When the user tried applying the patch with DOS 3.3, the error no longer displayed and the server came up fine without hanging the keyboard.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Abend: Bad Block Returned Via Free" - NetWare v2.2
DOCUMENT ID#: FYI.P.5178
DATE: 13JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "Abend: Bad Block Returned via Free"
ISSUE/PROBLEM
The user had Attachmate Gateway IPX version on the network. When the user brought up a NetWare v2.2 server, the server stopped and displayed the following message:
┌──────────────────────────────────┐
│Abend: Bad Block Returned via Free│
└──────────────────────────────────┘
SOLUTION
Attachmate was not null terminating the server name field in a SAP packet. The user fixed this problem by upgrading the IPX.
Users with Attachmate's IPX product should call Attachmate at 1-800-688-3270 for an upgrade.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Deleting NetWare Partition - NetWare v2.2
DOCUMENT ID#: FYI.P.5240
DATE: 16JAN92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user wanted to make a server back into a workstation and wanted to know how to get rid of the NetWare partition.
SOLUTION
The solution is to use ZTEST or DOS 5.0 FDISK.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Cache Buffer Not Found in Drive Table ..." - NetWare v3.11
DOCUMENT ID#: FYI.P.10172
DATE: 16OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user mounted SYS: volume, the system displayed the following message:
After the volume mounted, the system displayed other strange results.
ISSUE/PROBLEM
The problem sounded like a disk channel problem. However, the user said that the system had a memory add-in card with 1 x 3 SIMM modules. The cards were the same speed of memory in the system board, but the dimensions of this Single In-line Memory Module (SIMM) were different from the 1 x 9 SIMMs on the system board.
SOLUTION
When the user changed the add-in card to 1 x 9 SIMMs, the server ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unknown Error Returned by Attach - WD7000
DOCUMENT ID#: FYI.P.10167
DATE: 22AUG91
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: "Unknown error returned by attach"
ISSUE/PROBLEM
While trying to bring up a new server, the system displayed the following message:
┌───────────────────────────────────────┐
│Unknown error returned by attach (89ec)│
└───────────────────────────────────────┘
SOLUTION
Columbia Data Products new driver SST_DRVR.OBJ and .DSK dated 07-03-91 solves this problem. The driver is available on their bulletin board, phone #407-862-4724.
The driver is contained in the NW22.ZIP that is password protected and will not unzip without the password. The user must contact Columbia Data Products Technical Support and give the serial number for their SST_DRVR.OBJ driver disk to obtain the password on the file.
To download the file, go into File, and then into Area 5, and download the NW22.ZIP file. The file must be unzipped with the password and is encrypted, so type
PKUNZIP -s<password> NW22.ZIP
A README file is also available.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Find MENUPARZ.EXE - SMODE in SHELL.CFG
DOCUMENT ID#: FYI.P.10165
DATE: 16OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When the user ran the menu utility in any directory other than the PUBLIC directory, the system displayed a messaged that it could not find the MENUPARZ.EXE program.
ISSUE/PROBLEM
The user had previously put the line "smode = 2" in the SHELL.CFG for an issue with Procomm. This smode Option 2 specifies that the executable file will not use the search drives. As a result, the MENUPARZ.EXE was not being found outside the default PUBLIC directory.
SOLUTION
When the user removed the SMODE command from the SHELL.CFG, the menu utility worked.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to MAP COMSPEC = S5:COMMAND.COM
DOCUMENT ID#: FYI.P.10227
DATE: 21OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: Could not MAP comspec = s5:command.com. in the login script. This returned "Invalid command.com." error.
ISSUE/PROBLEM
Configuration:
■User was using a clone 386 server and DOS 5.0 at the workstation.
■The login script consisted of the following commands:
;map s1:=sys:public\dos\%MACHINE
;comspec=s1:command.com
map s5:=sys:public\dos\%MACHINE
comspec=s5:command.com
■LONG MACHINE TYPE = COMPAQ on the Compaq workstations
■LONG MACHINE TYPE = MSDOS on the machines using DOS 5.
■The directory structure looked like the following:
sys:public\dos\msdos
sys:public\dos\compaq
Only the workstations with Compaq machines would get a correct mapping. The workstations with DOS 5.O displayed the following error:
┌───────────────────┐
│Invalid command.com│
└───────────────────┘
SOLUTION
The user removed the two lines that were disabled and changed the mappings to look like the following:
map s1:=sys:public\dos\%MACHINE
comspec=s1:command.com
After the user changed the login script, both the Compaq and DOS 5.O workstations could log in.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Drive Deactivated Due ... " - Adaptec 1740 Cards
DOCUMENT ID#: FYI.P.10224
DATE: 21OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: "Drive has been deactivated due to drive failure..."
ISSUE/PROBLEM
Configuration:
■ARCSERVE.NLM
■SBACKUP.NLM
■Over 40 servers on the LAN
When the user ran either of the backup applications, the system got well into the backup then suddenly died and displayed the following error:
The error displayed on all the LAN workstations or at one time or another.
SOLUTION
The user was using Adaptec 1740 cards. After upgrading all the cards to the newest revision of the BIOS, either application worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: DR DOS FDISK Issues Adding Second Hard Drive
DOCUMENT ID#: FYI.P.10222
DATE: 21OCT92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user had a hard drive partitioned as C: and D: drives. Then the user decided to add second hard drive. FDISK designated the second hard drive as the D: drive and redesignated the current D: drive to be the E: drive. Now, applications that search for the D: drive cannot locate themselves. Is there a way to get FDISK to make the second drive E: drive instead of D: drive?
SOLUTION
Yes.
The drawbacks for making the second hard drive the E: drive include the following:
■50 to 100 KB less space available (loss of 1 cylinder)
■The user cannot make the second hard drive bootable because it does not have a primary partition.
If making the second hard drive the E: drive is still desired, use the following procedures:
1. Delete any partitions on the second hard disk and create an extended partition only.
2. Do not create a primary partition.
3. Do not start the partition at track 0. Start at cylinder 1. Otherwise, the D: drive will still be assigned to the second drive.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Compressed File Errors Shelling Out from Windows - DR DOS
DOCUMENT ID#: FYI.P.10215
DATE: 21OCT92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM:
The three programs listed displayed the same error message when the user started them from a Windows 3.1 icon:
■ DRDOS PROMPT
■ DRDOS EDITOR
■ PC PAINT BRUSH 4+
Each of these programs is a non-Windows program that shells out (temporarily exit) Windows to run. The error that displayed was the following:
This user was not using SuperStor or any other disk compression utility. When the user used the EXPAND command on the files and directories associated with these programs, it came back with no compression in any programs.
ISSUE/PROBLEM
Windows uses a number of video drivers depending on what the program function (as seen in the SYSTEM.INI file). The "component" that was compressed was the Windows video driver associated with shelling out from Windows.
SOLUTION
When the EXPAND command was used in the C:\WINDOWS\SYSTEM\ directory, it found one video driver that had not been expanded during the regular installation of Windows. When the video driver was expanded, the user had no trouble running these programs.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Using IBM NETAPI.DLL to Communicate with Novell's NetBIOS
DOCUMENT ID#: FYI.P.10201
DATE: 22OCT92
PRODUCT: NetWare Requester for OS/2
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The user wanted to use the IBM NETAPI.DLL to communicate with Novell's NetBIOS using Extended Services on OS/2 2.0.
This scenario would only work if the NETWKSTA.SYS was started from LAN services. The user wanted this to work without invoking the NETWKSTA.SYS.
SOLUTION
IBM said the user needs to use the NETAPI.DLL from LAN Services with size 322144. This NETAPI.DLL makes calls to Novell's NETSUB.DLL that will allow this to work. The NETAPI.DLL, which currently ships with Extended Services, does not make calls to NETSUB.DLL. Also, the user needs to disable the statements pertaining to NETBEUI in the CONFIG.SYS file.
A schematic on page B-10 of the NetWare Requester for OS/2 manual outlines what the user wanted to do.
Also, IBM is creating an APAR to fix NETAPI.DLL that ships with Extended Services to make calls to NETSUB.DLL.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Can FDISK delete a primary partition while leaving the extended partition intact?
SOLUTION
Yes. In FDISK, select the option to delete the primary partition while it still has an extended partition. Then, recreate the primary partition, and the extended partition will not be effected.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Windows Hangs with Black Bar in Logo - DR DOS
DOCUMENT ID#: FYI.P.10196
DATE: 22OCT92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM:
When the user executed Windows, the Logo came up but it had a black bar running through it; then the system hung. Sometimes the system did not hang, but returned to the prompt. However, it was hard to tell that the cursor was at the prompt because it was in a strange video mode.
ISSUE/PROBLEM
This symptom is just one of the possible side effects of running SuperPCK in Expanded memory (also known as EMS or LIM memory). The /A or /A+ switch on the SuperPCK line indicates use of Expanded memory.
SOLUTION
Changing this switch to a /EM will cause the cache to use Extended memory instead of Expanded. When using Windows 3.0 or 3.1, set SuperPCK for Extended. In fact, if the questions in the INSTALL or setup for DRDOS were answered correctly, SuperPCK will default to Extended on a system that runs Windows.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MEM.EXE Reporting over 1 GB of Expanded Memory
DOCUMENT ID#: FYI.P.10194
DATE: 22OCT92
PRODUCT: NetWare
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM:
MEM.EXE would report over 1 GB of total Expanded memory, but only 16 KB of it was available.
ISSUE/PROBLEM
The problem was that the CONFIG.SYS file had DEVICE=EMM386.SYS /F=AUTO /K=64.
SOLUTION
When the user switched to /K=AUTO, the problem went away. Whenever the memory was /K=253 or less, MEM.EXE reported 1 GB of total Expanded memory.
Novell recommends that users do not go below /K=256 or /K=512. The memory manager needs to use some of that memory to create the page frame. If the user must have EMS memory, then the best option is /K=AUTO. With the /K=AUTO option, the programs that load into it will use what memory is needed and the rest of the memory is still available to XMS memory.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Running PCSHELL /r, DR DOS
DOCUMENT ID#: FYI.P.10192
DATE: 22OCT92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Configuration:
■DR DOS v6.0
■Central Point PCSHELL v7.1
The issue is being able to run file such as *.EXE or *.COM after loading PCSHELL /R (memory resident).
SOLUTION
Central Point Software Inc. support gave this order for loading the needed SWAPSH program and PCSHELL in the AUTOEXEC.BAT:
HILOAD SWAPSH /N
MEMMAX -U >NUL
PCSHELL /RT
The order does not need to be exact. The important part is the SWAPSH /N comes before access to upper memory is closed (MEMMAX -U) and the PCSHELL /RT comes after access is closed.
After inserting the necessary command in the AUTOEXEC.BAT file, the system ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: DIR and CHKVOL Showing Different Values
DOCUMENT ID#: FYI.P.10191
DATE: 22OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: DIR and CHKVOL showing different values
ISSUE/PROBLEM
When the user executed the DIR and CHKVOL command, they showed a drastic difference in values. The user never exceeded the maximum limit on the drive. When the user executed PURGE ALL, the symptoms still occurred.
SOLUTION
When the user dismounted and mounted the volume, the difference cleared.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abend during AES Sleep Process
DOCUMENT ID#: FYI.P.10188
DATE: 20OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The file server had been running for some time with no problems. Then it crashed with the following error:
┌────────────────────────────────┐
│Abend...during AES sleep process│
└────────────────────────────────┘
The user checked items such as the following but did not find any resolution:
■ Memory
■ LAN and disk drivers
■ SERVER.EXE
ISSUE/PROBLEM
Configuration:
Amax 486/33 - file server
Someone at the user's site had rerun EISA CONFIGURATION (CF.EXE) and changed the available memory from 16 MB to 1 MB.
SOLUTION
As soon as memory was correctly defined in EISA CONFIGURATION, the server stopped sending abend messages and everything ran fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Returned Error 255" - Clipper, DR DOS, and NetWare v3.11
DOCUMENT ID#: FYI.P.10186
DATE: 19OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
While using DR DOS 6.0 and a Clipper menu program on a NetWare v3.11 system, the system displayed the following message when the user tried to save a newly created file in WordPerfect or when saving a new user or login script in SYSCON:
┌──────────────────┐
│returned error 255│
└──────────────────┘
Also, the following message displayed when the user tried to send a mail message even though the mail box was not full.
┌─────────────┐
│Mail box full│
└─────────────┘
Executing WordPerfect, SYSCON, and the Mail programs from the command line without using the menu program worked fine. Also, when the user took DR DOS off and put MS DOS 5.0 on, all three applications functioned properly while using the menu program.
ISSUE/PROBLEM
Configuration:
■DR DOS v6.0
■Clipper Summer '87 version
A conflict exists among the combination of DR DOS 6.0, Clipper '87, and NetWare v3.11 software.
SOLUTION
Novell Monterey has a patch available on their BBS called UTL792.ZIP. After the user unzipped that file and copied over the COMMAND.COM file to each machines root directory, everything worked fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: CAPTURE Statement Taking 10 Seconds to Work
DOCUMENT ID#: FYI.P.10183
DATE: 19OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
When logging into the server, the CAPTURE statement in the system login script was taking about 10 seconds to work.
ISSUE/PROBLEM
The MAIL directory was empty.
SOLUTION
After the user restored the MAIL directory from a backup, the CAPTURE started working quickly again.
When CAPTURE is invoked, it first attempts to use the user's default PRINTCON defined print job found in the user's mail directory if it exists. In this case, it must have taken a long time for CAPTURE to determine that the user had no MAIL directory in which to find the PRINTCON.DAT file.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Not Enough Extended Memory to Run Novell 386..."
DOCUMENT ID#: FYI.P.10181
DATE: 20OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
The user had two IDE drives set up off one paddle board, and the drives were set up as master and slave. When the user ran SERVER.EXE, the system displayed the following error even with 8 MB in the server:
┌───────────────────────────────────────────────┐
│Not enough extended memory to run Novell 386...│
└───────────────────────────────────────────────┘
When the user removed the slave drive (second drive), the server came right up.
ISSUE/PROBLEM
The user had both drives set to the same memory address.
SOLUTION
When the user switched the address, the server came right up.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: System Locks Up after Adding Second Seagate IDE Drive
DOCUMENT ID#: FYI.P.10180
DATE: 20OCT92
PRODUCT: NetWare
PRODUCT VERSION: v2.2
SUPERSEDES: NA
SYMPTOM: System locks
ISSUE/PROBLEM
The user had a Seagate ST507A 40 MB IDE drive currently installed. When the user tried to add a second Seagate 80 MB IDE drive as a slave, the system lock after INSTALL prompted for the SYSTEM-1 disk.
The user tried replacing the 80 MB drive with a Seagate ST1156 130 MB drive but the symptom still occurred.
SOLUTION
The only way this configuration would work was to designate the 130 MB drive as the master and the 40 MB drive as the slave. Any other configuration caused INSTALL to hang on the SYSTEM-1 disk.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Ethernet Stations Unable to Log into Network - T-Connector
DOCUMENT ID#: FYI.P.10177
DATE: 20OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
Two Ethernet stations cannot attach or login to the NetWare v3.11 Server while two others on the same bus can. If the places of station 1 that cannot login to the server and station 3 that can login to the server are reversed, the result is the same (station 1 can login but station 3 cannot).
ISSUE/PROBLEM
Station 3 was connected to the Ethernet bus through an extension or drop cable rather than through a loop of the Ethernet bus. The T-connector was not directly attached to the network interface card but was separated by several feet of coaxial cable on a single run.
SOLUTION
After the user removed the drop cable from the T-connector and moved station 3 to the wall to connect the Ethernet bus, station 1 could attach and log into the NetWare server.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Installing DR DOS in a PS/1 Machine
DOCUMENT ID#: FYI.P.10176
DATE: 20OCT92
PRODUCT: DR DOS
PRODUCT VERSION: 6.0
SUPERSEDES: NA
SYMPTOM:
DR DOS installed just fine. However, when trying to boot from the C: drive, the system sent a message that the user had the incorrect DOS version and invalid lines in the CONFIG.SYS file. Then the system hung.
After the user reinstalled DR DOS without a flaw and rebooting, the same problems occurred.
ISSUE/PROBLEM
Configuration:
DR DOS v6.0 in a PS/1 (386 SX) file server
The PS/1 (386 SX) machine has an interesting feature where it loads in the operating system from a ROM chip if specified. The user kept saying that a menu program kept coming up when booting from the C: drive and that was where the option was to boot from the ROM chip.
The menu really said to boot from the fixed disk and then the floppy.
SOLUTION
After changing to booting from the floppy and then to the fixed disk, the sever came up just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: ViewMax Problems on 286 Laptop
DOCUMENT ID#: FYI.P.10163
DATE: 16OCT92
PRODUCT: DR DOS
PRODUCT VERSION: v6.0
SUPERSEDES: NA
SYMPTOM:
When the user tried to execute ViewMax on a 286 laptop, the screen went blank and nothing happened.
ISSUE/PROBLEM
After rebooting and going into the DR DOS setup to check the options for ViewMax, the user could not get the MEMMAX, TASKMAX, DISKMAX, or VIEWMAX options.
For some reason, the "CurrentDrv=" line was set to 0 (IBM VGA) in the VIEWMAX.INI file.
SOLUTION
After the user edited the VIEWMAX.INI file so that the "CurrentDrv=" line was set to 6 (monochrome), ViewMax executed just fine.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Working on Other Volumes when SYS: Volume Goes Down
DOCUMENT ID#: FYI.P.10146
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: SYS volume dismounts
ISSUE/PROBLEM
What happens when you are working on another volume and SYS: volume goes down (dismounted)?
SOLUTION
You still can work within that volume if you still have access to PUBLIC files on another server. Utilities that make bindery calls (such as FILER) will have limited capabilities. All rights are maintained. New files created have no owner.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Binderies Have Already Been Upgraded"
DOCUMENT ID#: FYI.P.10144
DATE: 14OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM:
A user performed an upgrade just fine using the backup method. Then the user decided he wanted a larger block size on the SYS: volume. Before the user deleted the volume on the NetWare v3.11 server, he backed up the SYSTEM directory. Then the user deleted the SYS: volume and reinstalled the NetWare v3.11 operating system. When the user tried to restore from the backup using the RESTORE.EXE again, the system displayed the following error:
┌────────────────────────────────────┐
│Binderies have already been upgraded│
└────────────────────────────────────┘
ISSUE/PROBLEM
Before trying to restore the server using upgrade, the user restored the previous backup of the SYSTEM directory. A file named UPGR$000.BMF was in this backup. This file must not exist if you want to restore the binderies again.
SOLUTION
After removing the UPGR$000.BMF file, the user could run RESTORE.EXE again. The UPGR$000.BMF file is a log of previous upgrades.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Printing to a Printer through Another Server
DOCUMENT ID#: FYI.P.10143
DATE: 13OCT92
PRODUCT: NetWare
PRODUCT VERSION: v3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How can you print through server B to a printer on server A?
SOLUTION
Use the following set up to print a printer on server A through server B.
On server A:
1. Create a queue, printer, and print server as normal.
2. Verify that all items created are working properly.
3. Add server B under the "servers to be serviced" option.
On server B:
1. Create a queue with any name to put the files in.
2. Create a print server with the same name as the one on server A.
3. Create a printer with the same printer number as the printer on server A, and set its type to the "defined elsewhere" type.
Note: You do not load this print server! You are only creating an object on server B that will have rights to the printing portions of NetWare on server B.
What happens:
When the print server on A loads, it recognizes that it is supposed to service server B, and logs into server B, using the object created on B. Because that object has rights to the print services on B, now the print server on A has rights to those services as well.
