Date: Wed, 4 Nov 1998 11:00:43 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Mike Hackbart <hackbart AT chesapeake DOT rps DOT slb DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: RCS and Network Drives - ENODEV, ENOENT
In-Reply-To: <199811031559.KAA20728@scrooge.chesapeake.rps.slb.com>
Message-ID: <Pine.SUN.3.91.981104110022.25255G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Tue, 3 Nov 1998, Mike Hackbart wrote:

> c:\devel\rcstest\rcs>copy main~1.c_v i:\censoft\xxrcs

Why did you use the short 8+3 alias instead of the long name main.c,v?
The COPY command (and all other commands) built into Windows 95
version of COMMAND.COM support long file names, so why didn't you use
them?  (You might need to quote the long file name because of the
comma, but otherwise they should work.)

> c:\devel\rcstest was then changed to delete the rcs folder and add a file
> named rcs that contained:
> 
> i:\censoft\xxrcs

I see you tried to use the RCS pseudo-link feature.  I have never
tried to use that, and I don't know whether it works correctly on
Windows 9X (or at all).  Maybe that is the source of your problem.

What happens if you chdir to the I: drive and try to extract the file
there?  Does it work?  If it does, then the problem most probably is
caused by the pseudo-link feature.

>  Directory of I:\CENSOFT\xxrcs
> 
> .              <DIR>                        .
> ..             <DIR>                        ..
> MAIN     CV         34,814  11-03-98 10:33a main.c,v

Note that the short alias is different in this case: it is not
main~1.c_v, but something else.  I don't know what is the significance
of this fact.

> synchronization between the server time and the local PC time.  Could this
> be the source of the problem?

I don't think RCS cares about the time stamps.