🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.netware.misc
Article #506

Re: Need help with a Bindery Problem

#506
From: t3623ad
Date: Fri, 22 Dec 1995 00:00
48 lines
2875 bytes
abu@access2.digex.net (Bob Dahm) writes:

>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"            /
> /======================================================/   
> 
Only a few hints.
1. You may start vrepair for SYS from the startup drive only (usually c:).
   To Do this all necessary files must reside on this drive. VREPAIR
   will give you the names of the necessary modules.
2. The old bindery files will be named netxxxx.old.
   Copy these three files to floppy or a local hard disk. Look for the
   attributes of these files. There mus be normal access possible.
   By no means write protection is allowed. This gives a desaster, if
   you call bindfix.
3. Try deleting the *.old files and repeat bindfix.
4. The very very last attempt:
   Restore the *.old files from the backup medium and run
      bindrest
   But take into account: all information concerning new users since the
   last bindfix will be lost.
By the way: it is impossible to delete the bindery files.

Rainer Haessner
TU Muenchen
rh@linda.org.chemie.tu-muenchen.de
Technical Details
Message-ID: <4betg5$gde@sparcserver.lrz-muenchen.de>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <abu.819457317@access2>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe659,aa817bcf59f5a939
X-Google-Attributes: gidfe659,public
X-Google-Thread: f8bf7,aa817bcf59f5a939
X-Google-Attributes: gidf8bf7,public
From: t3623ad@sun2.lrz-muenchen.de ()
Subject: Re: Need help with a Bindery Problem
Date: 1995/12/22
Message-ID: <4betg5$gde@sparcserver.lrz-muenchen.de>
X-Deja-AN: 122566443
distribution: world
references: <abu.819457317@access2>
organization: Leibniz-Rechenzentrum, Muenchen (Germany)
keywords: Bindery
newsgroups: comp.os.netware.misc,bit.listserv.novell