[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  9471
Date     :  2004-12-12
Author   :  des4212001
Subject  :  Re: That stinkin' DEP.DUS
Size(KB) :  3



--- In xxcopy@yahoogroups.com, "des4212001"  wrote:
> 
> --- In xxcopy@yahoogroups.com, "John Zeman"  
wrote:
> > 
> > --- In xxcopy@yahoogroups.com, "des4212001"  wrote:
> > > 
> > > Well, obviously xxcopy isn't seeing any "\\El-Diablo\My 
> > > Documents\DPE.DUS". What all the other "\\El-Diablo\{subpaths}
> > > \DPE.DUS's" are about beats me.
> > > 
> > >
> > 
> > 
> > I'm wondering if this DPE.DUS problem isn't somehow related to 
the 
> fact that you are using this on a network. That's only a WAG (a 
> guess) on my part though as I know almost zilch about networks. 
It 
> does appear that to xxcopy "\\El-Diablo\My Documents\" is not 
> actually the source, at least when it comes to the exclusions. 
> Instead, at least for the exclusions, it certainly appears 
> that "\\El-Diablo\" is the source. However even if that was so, 
it 
> does not explain why the "\\El-Diablo\My Documents\DPE.DUS" file 
is 
> not being excluded.
> > 
> > At the risk of making myself look like a total fool here (I'm 
> literally shooting blindly in the dark on this subject) is it 
> possible you somehow have "\\El-Diablo\My Documents\" set up to 
> actually point to "\\El-Diablo\" or some other location instead?
> > 
> > That's the only somewhat plausible explanation I can come up 
> with. However I also know if that was somehow true, that xxcopy 
> would be copying a lot more directories than just "My Documents" 
and 
> its subfolders.
> > 
> > John
> 
> "\\EL-Diablo\My Documents" is a share, which is actually "F:\My 
> Documents\" if that makes any diference? Just as on the other 
> computer "\\Cx532597-a\My Documents\" is a share there, which is 
> actually "C:\My Documents\".
> 
> It was Kan I believe, referring to one of my share names, who said 
> something like, "Who whould ever have a share by that name?" All I 
> could figure was the space in the name? I had only glossed over 
his 
> comment and immediately dismissed it as a bad day, as the "My 
> Whatever" names are system generated in both flavors of Windows. 
> Anyway, this has stuck in my mind, and I was going to try renaming 
> the shares to something more unix, ie no spaces or use an 
> underscore. Just to see if it makes any difference? Stranger 
things 
> have happened.
> 
> I recently ran headlong into some major character understanding 
> differences between Win98 vs WinXP. Tied to the unicode business I 
> believe? Anyway, many characters, like the copyright & registered 
> symbols, are displayed correctly in WinXP, but default to 
something 
> else in Win98. This creates a situation where the names are indeed 
> the same, but seen & understood differently by the 2 systems!
> 
> And as a further example, yesterday I suceeded in copying a URL to 
> Win98 that contained a special character. WinXP had no problem 
with 
> it, and it transfered ok, but created a file Win98 couldn't 
> manipulate as it couldn't recognize it. Had to delete it with MS-
> DOS, and rename it back on the source to avoid this problem again.
> 
> But all that's off the subject. This not recognizing an exclusion 
> seems to directly related to the source being remote.
> 
> DES

And I finally did... rename the share to "\\El-Diablo\My_Documents\" 
just on the outside chance. And that doesn't make any difference to 
the DEP.DUS exclusion. I'm out of ideas.

DES



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.