Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!lll-winken!uunet!munnari.oz.au!uniwa!doug
From: doug@psy.uwa.oz.au (Doug Robb)
Newsgroups: comp.protocols.nfs
Subject: Re: XCOPY - PCNFS
Message-ID: <1991May20.063256.15130@uniwa.uwa.oz>
Date: 20 May 91 06:32:56 GMT
References: <2098@Terra.cc.brunel.ac.uk>
Sender: news@uniwa.uwa.oz (USENET News System)
Organization: University of Western Australia
Lines: 26
Nntp-Posting-Host: wapsy.psy.uwa.oz.au

lbsrdrt@cc.brunel.ac.uk (David Thomas) writes:


>Is XCOPY supposed to work both ways when used from PC to Unix file
>server ?

>I've succeeded in XCOPYing to a PC Disk from a Unix file server, but
>not the other way around.

Yes xcopy does work both ways. If you can't xcopy from a pc hard disk
to a unix server I'll bet your umask is wrong! Make sure you
set 'net umask 022' (on the pc) or something sensible (rwxr_xr_x).
If the 'execute' bit (x) is not set then xcopy can't
cd into any subdirectories and so the copy fails.
Copy on the other hand doesn't need to create and directories
so you are never aware of a crummy umask.
To check this either do a net umask and it will tell you
the current umask or try it yourself.
cd e:		(or whatever drive is the server disk)
md test		(or any name you think of, must have write perm on e:)
cd test
If your umask is such that the execute bit of the file it created
is not set then the cd will fail.
ls -l test   (file should be rwx or whatever and not rw-rw-rw etc)

cheers doug@psy.uwa.oz.au