Now that's some unique typing. Even allowing for being a programmer. I'd guess that either the keys on that keyboard aren't labelled with the Latin alphabet or that it was entered via an SMS thumbpad.
But, cultural critiques aside, the problem is that you don't access CVS archives via UNC (sometimes known as Windows Share Names). CVS isn't served up by a file server, it's served up by a CVS server. So the machine that contains the CVS repository must have a CVS server process running.
A typical CVS server ID sequence might look something like this:
That specifies the protocol (extssh), user ID on the CVS server (user123), the server itself (cvsserver.mydomain.com) and finally, the location of the CVS archive as an absolute pathname within the CVS server's filesystem. I've used a Unix pathname for my example, since I've never actually seen a CVS server running on Windows.
The Eclipse CVS setup lets you break that ID into its components (the parts separated by ":") and enter them as individual items in its setup dialog. And to test the definition by actually querying the server.
Customer surveys are for companies who didn't pay proper attention to begin with.
Originally posted by Tim Holloway: I've used a Unix pathname for my example, since I've never actually seen a CVS server running on Windows.
I have. And it allows you to provide an external name for your repository's path, so you can make it look like a Unix path.
It looks like Essam should be talking to the person who installed the CVS server, especially to get the "user name" and "password" information. Those are not necessarily the same as the Windows user name and password used to sign on to the network.