I had a crash corrupt my 4.1 DS database, and I can't load ds.nlm as a 
esult,
which means I can't log onto NDS from anything, which means I can't access 
anything on the server. The server is patched with current ds.nlm and
dsrepair.nlm.
DSRepair won't repair the database because it says its version doesn't match. 
I can't go into Install.nlm and remove the database and start from scratch 
because you have to open the database to remove it.
The volume is the Sys volume, so there's no way I can think of to mount it on 
a working server to retrieve the data.
Right now the drive's a doorstop, which is really torking me off because if I 
could just reinitialize a bare minimum NDS, I could restore the rest from 
tape. (The backup is one day old, and a lot of work happens in one day).
This is a huge case of deja vu for me. I had a Netware 2.11 volume do the 
exact
same thing to me a few years back: the wrong area of the drive went bad, so 
the volume wouldn't mount. It was the Sys volume, so couldn't mount on 
another server. Ontrack Netutils 2 was able to retrieve the data (the most 
excruciating exercise I've ever gone through: pathetically clunky interface, 
restore one directory at a time).
Ontrack sells a product for Netware 4.x but if it takes longer to run the 
data recovery utility than to do the work over I'll save the money.
Any data recovery tips out there that might help?
Jeff
--- GoldED/2 2.42.G0615
---------------