P.1 "Lan receive buffer limit reached"

Your server is probably running out of memory or you need to raise the "maximum packet receive buffers" limit.

Also, you may want to set you "minimum packet receive buffers" to a large enough number so that when you start the server up next time, it will start with a large packet buffer pool.

This error normally indicates faulty cabling rather than anything else. Look at the LAN driver statistics to see which one has errors on it.

P.2 "Primary Interrupt Controller Detected A Lost Hardware Interrupt"

Your server may have a device, commonly a NIC, configured to use an IRQ above 8. Re-configure the device to use an IRQ less than 8.

>>>New info on this:

The above is wrong. The primary interrupt controller handles IRQs below 8; it's the _secondary_ one that handles IRQs 9 and up. Note that IRQ 2 on an AT or higher is, in real life, IRQ 9.

Also, the vast majority of servers don't get these messages. A lost hardware interrupt means that something generated an interrupt, but by the time the system went to find out what it was, the system could no longer figure out which device generated the interrupt. If the system appears to be functioning normally, it's usually safe to ignore these, and there's a SET parameter which you can use to turn off the display (and logging - these things can really eat up your system error log) of these messages.

[Thx S.M.D.] To disable the display of this message, type the following SET commands at the NetWare server console prompt (and/or add them to your Autoexec.NCF file):

	SET DISPLAY LOST INTERRUPT ALERTS = OFF
	SET DISPLAY SPURIOUS INTERRUPT ALERTS = OFF

P.3 "Loader cannot find public symbol..."

The NetWare Loader cannot find a needed NLM and/or cannot autoload it. Make sure all relevant NLMs are present and are the correct (usually newest) version.

[Thx H.B.]

P.4 Getting rid of *all* NetWare system messages on a client PC

Execute CASTOFF ALL on any PC where you do not want to receive NetWare messages like "Volume SYS: out of disk space".

[Thx R.C.]

Another option is to use CASTAWAY from Infinite Technologies or MSG_20 from Gary Dobbins (dobbins@arizona.edu) together with TSRCOM.

[Thanks to Soren K Lundsgaard for this info]

P.5 Using the Message Timeout option of the VLM

If you use VLMs you can set the Message Timeout paratemter in the DOS Requestor section of NET.CFG and the messages will stop displaying automatically after the time period expires.

[Thx R.J.L.]