D
Darryl
I've got regular nonsystem files that I download to a Linux box, then
copy over to a Win2k box through a mapped Samba drive.
When I copy a group of files from the Linux samba drive to my C:
drive, the LAST file to copy always reports a sharing violation.
When I then copy a different group from C: to D: (both local, C=ntfs,
D=fat32), the last file always reports a sharing violation.
I've found I can actually work around it by selecting files I don't
need to copy to decrease the odds that the last file will be a needed
file.
Are there permissions from the Samba drive that are confusing Win2K,
enough so that it persists with the copy from C: to D:, or is there
something else operating here?
copy over to a Win2k box through a mapped Samba drive.
When I copy a group of files from the Linux samba drive to my C:
drive, the LAST file to copy always reports a sharing violation.
When I then copy a different group from C: to D: (both local, C=ntfs,
D=fat32), the last file always reports a sharing violation.
I've found I can actually work around it by selecting files I don't
need to copy to decrease the odds that the last file will be a needed
file.
Are there permissions from the Samba drive that are confusing Win2K,
enough so that it persists with the copy from C: to D:, or is there
something else operating here?