We have a server running Netware 5.1 with SP 7 on our server. On Friday,
October 7 at 6:30 a.m., the Server abended. At the server console I was
unable to access any applications, such as PowerChute, ArcServe,
Netshield, etc, they were all non-responsive. I was forced to restart the
server by pressing the power reset button. I next checked the server abend
log and found that the server was running the "Automatic DAT Update" task
for Netshield when the abend occurred. I contacted Network Associates on
server abend and talked to a Technical Support Representative who she
recommended we immediately update Netshield to version 4.6.3. because it
is more stable than the 4.6.2 product. Next the Representative analyzed
the abend log and further recommended the following in the text below:



This article will also apply to Netware 5.1 SP7. With the abend that
occured, you want to check the filesys.nlm on the Netware and check on the
Novell site and apply the latest version of filesys.nlm for the Netware
5.1 SP7.

McAfee NetShield 4.6.2 for NetWare
Novell NetWare
EIP in FILESYS.NLM with a running process of NETSHLD XUReceive
The CPU encountered a problem executing code in FILESYS.NLM
Server abends while performing an On-Demand scan
Server abends during an AutoUpdate
Server abends in the On-Access Scanner
Abend with a running process of NETSHLD XUReceive
Abend with a running process of NETSHLD SCScan_0x
Abend with a running process of NETSHLD MCShld_Access_0x
This issue is caused by a corrupted Extended Attribute handle. The
NetWare OS blocks on a disk I/O while it is in the process of generating
an Extended Attribute. While this thread is blocked another thread
deletes a directory leaving an incomplete Extended Attribute structure
Download and install Novell's latest version of FILESYS.NLM. As of the
creation of this article the latest version is contained in FLSYSFT9.EXE
The version of FILESYS.NLM which addresses this issue can be applied to
NetWare 5.1 SP5, NetWare 5.1 SP6 and NetWare 6.0 SP3. This fix will be
distributes with future support pack releases.

For more information on this issue, please refer to Novell TID 10088133.

My questions are as follows:
1. What possible problems could occur from updating our current version
of the "FILESYS.NLM" version 5.10 dated 10-31-2003 to the latest