Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

VRepair 3.11

VRepair 3.11

VRepair 3.11

I posted the below on the netware 3 forum but then noticed that it has had no activity for a couple of years so I am posting to this forum in hopes that someone takes pity on me and can help.

We have a Netware 3.11 server that has eaten it's drive. I was able to find a backup drive but when I power it up I get the message that volume sys could not be mounted.
From looking at the forums I have found that I need to run vrepair so I followed some of the threads and input the name of the server and a hex number for the internal network number. I then typed in load vrepair and get the message "unable to find load file vrepair".

I don't have the media for the server does anyone have a copy of VRepair and can they tell me how to load it or tell me the next step?


RE: VRepair 3.11

IF the server "ate its hard drive" that had the operating system on it (with the SYS volume) and you put in a new drive, you have no operating system to work on (no SYS volume). So, I don't think getting a copy of VREPAIR is going to save you - you have nothing to work with (no sys vol and no install media). Does it try to boot up to DOS? Usually, Novell loads a DOS partition, then launches SERVER.exe from the C:\Nwserver folder. Can you see it trying to boot to dos? If you can press F5 and just get to a DOS prompt, can you do a directory (DIR) and see if there is an NWSERVER directory at all?

If I misunderstand the situation - tell me.

I think it's time you called a time out and said, "what are we doing running a horribly outdated operating system, with no media, and someone not too well versed in Novell (no offense intended). I'd say it's time to move away from Novell (just in general due to their decline) OR get current on the software. You're really at a decision point here.

It's possible that there is an operating system download out there somewhere for you - either from the Novell site or somewhere else. May be your last chance. You realize that your user objects and rights, etc. are probably all gone......

RE: VRepair 3.11


I totally agree with your statements in the second half of your response and no offense taken.
The powers that be have been told repeatedly by myself and others that it was just a matter of time until we lost everything, but they did not want to spend the money to have a new program written.
We are finally taking steps to move to a newer platform but we do need to get this one running in the interim if at all possible.

I did do a dir and the following files show up in the listing.

command com
wina20 386
server exe
autoexec bat
files dat
readme 311
nut nlm
ide dsk
readme doc
ipxeth16 com
386me-16 lan
startup ncf
3c507 lan

I did get a response from my original posting on the netware 3 forum and one of the guys is going to give me a link to download vrepair for me to try.
all I have to do is be able to figure out how to load it and make it work :)

I figure it is worth a try as we are desperate to get something back up and running.


RE: VRepair 3.11

I never ran 3, but I did run 4.11, 5.x and 6.x, so I know quite a bit.

If you get the file on a floppy, you can do the following at the netware command prompt:
load vrepair.nlm or load vrepair
You can't run vrepair if the server is not booting at least to the novell server prompt. Run it until errors are gone or don't go down any more.

If you can get to the dos prompt, change to the nwserver directory and run server -ns it will startup the server with the bare minimum OR edit the startup.ncf using dos EDIT command and REM out anything not needed (everything but disk drivers basically).

My concern is that you don't have other files or all your OS files that you need.
What directory was it that you took and showed the file list above???

Find your vrepair file here:
in this file: VRPUP1.exe

As to the rest of your sad story - what the hell is wrong with people like that. "You're going to die if you don't have this operation", the doctor says. "Oh, no thanks, I'll take my chances." The mind boggles at that level of complacency and incompetence. If they aren't the owners of the company, they should be fired.

RE: VRepair 3.11

Sorry, that Novell site doesn't actually have a link to a REAL download of that file, unless my computer is not working correctly.

I couldn't find an official location for the download either. You can roll the dice and download one from an unofficial site.

RE: VRepair 3.11

Hi goombawaho, long time no speak.

I have offered the OP a copy of vrepair in his duplicate thread; just waiting for a reply.

All those old Novell 3.x files and patches seem to have disappeared. Bit of a shame, it is surprising how many 3.x boxes are still running (I support 2)


RE: VRepair 3.11

The directory list is from C:\
and unfortunately "They" are the owners of the company. they are so far removed from the real nuts and bolts of the company that they can't/won't understand that just because they did everything by hand back in the day doesn't mean that you can do it that way now.

jockmullin on the Netware 3 forum is going to send me a copy of VRepair... here's hoping it works!


RE: VRepair 3.11


it is surprising how many 3.x boxes are still running
More like amazing. Makes me wish for a software drop dead date where an OS just stops working.

I hate to say that I doubt the vrepair will work. But, be sure to let us know the results.
1. The SYS volume and other volumes might not even exist at this point
2. They may exist but on a hard drive that is toasty.

I kind of hope the owners suffer a lot from this and maybe learn a lesson.

RE: VRepair 3.11

That's the thing, they just sit there doing the job day after day year after year until finally entropy wins. One of mine hasn't even been rebooted in a year, and that was because the UPS failed.

Damn that Novell reliability - I feel like the Maytag repairman (but then he died, too) :)

Meanwhile the OP responded to his other thread - your prophecy was correct, no netware volumes found. It always was a long shot. Don't know what they'll do now; probably Winserver.


RE: VRepair 3.11

Unfortunately the owners are not the ones who will suffer as they just say do everything by hand and don't realize what it will take to do that in time and stress.
on the bright side I did get them to commit to having a new program written for our "new" 2003 server but that will take several months to complete and we need it in four weeks.

I like the idea of a drop dead date but the owners would probably ignore that also. :)


RE: VRepair 3.11

While researching/refreshing stale synapses, I did locate the old repository of Novell 3.x patches and modules. They can still be found via the Novell patch finder:


In case it may help others in the future (or myself).


RE: VRepair 3.11

Given that you were running Netware 3.12, Server 2003 seems a BOLD advance. Maybe you can even have RAID to make things safer.

Work what you've got to work with and don't stress out. It's not your fault.

RE: VRepair 3.11

Even back in the day, 3.x had excellent raid support and I can attest from personal experience to how well SFT worked.

The sad thing is whoever installed that server chose not to use it, put everything on the SYS volume, didn't put essential tools in the boot partition and on and on. Likely saved money.

An idiot proof server OS has yet to be invented. 2K3 is too easy to install; anyone can get one running, which is only half the job. Linux is just the opposite; its geek quotient is so high by the time you get it working you probably know what you're doing.

"Not certified but certifiable"

RE: VRepair 3.11

Bottom line - you don't install a server, put it in the corner and expect it to run 10 years with no disk failures, ignore the backup, etc. It's pretty comical when that happens.

Computers aren't like toasters - they need TLC and maintenance. I'm sure the OP knows that but it was the company environment that caused the snafu.

RE: VRepair 3.11

Thanks again for all of the help! and yes when the 2003 server was put in it was put in with a "RAID" the owners probably thought it was bug killer :)
As for Linux I was a bit apprehensive about it until a friend of mine told me he had, had one up for 7 years with out a re-boot or any other OS problems.
It took me awhile to get the server up and running as I decided to figure it all out myself so I would learn more. It was a challenge but worth it.

Thanks one more time guys.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close