🚀 go-pugleaf

I need some help with a Bondery problem I am having.

I was doing some end of the year admin on our Netware 3.12 file server 
when I ran into this problem.  I was backing up the Bindery when I got a 
Network error saying that NET$VAL.SYS could not be read.  I tried BINDFIX 
and it will not fix it.  BINDFIX gives a quick little message saying that 
it can't fix the bindery.  So I tried to vrepair the SYS volume and 
vrepair says that it can't find V_MAC.NLM.  When the Server boots up now, 
I get a error reading NET$VAL.SYS, but the SYS volume mounts and from a 
user stand point everything looks OK.

My first question is: What am I doing wrong here? Am I missing something?

I had an idea that I could delete NET$VAL.SYS and netware would generate 
a new one, but then I thought I should ask the net first before doing 
anything I might regret later.  If it is OK to delete NET$VAL.SYS, what 
do I loss? Do I need to regenerate one or will netware do that for me.

Thanks for any help in advance.

         /======================================================/
       /     Robert Dahm - ConQuest Software                  /
     /       Internet Address: Abu@access.digex.com         /
   /          "And Thank You for Your Support"            /
 /======================================================/