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

Number   :  72
Date     :  2001-05-17
Author   :  Joseph Maddison
Subject  :  Re: xxcopy switches, etc.
Size(KB) :  2


> Joseph Maddison said he was using a DIR command to locate
> the files which contains a tilde (the letter "~").

Actually, I said I used

DIR /B /L /S

Try it and see what I mean. It really does display LFNs, not SFNs.
Note that I do *not* do DIR /B /L /S *~1, since pattern matching
matching either SFN or LFN-- I do 

DIR /B /L /S | FIND "~" >tmp.bat

This gives me a list of LFNs containing a ~. It works under Win98
and Win2k. It's just a hassle. I do like your XXCOPY /LDZSL to display
the SFN and LFN side by side, though.

> From your description, I assume that in your system, you observe
a file named "TECHSP~1". The fact you observe this is already a
sign that the directory has been manipulated by a file-copy utility
in DOS or a utility which does not support LFN. <

Actually, just the file was manipulated. Say I download three files
and because they were uploaded incorrectly, the LFN has been lost
on one of the files uploaded by A and the two related files uploaded
by person B are fine. That is not something I can control if I am
using a batch download process.

> Otherwise, you would not get a fliename like XXXXXX~1 except for the 
SFN of a real LFN which is non-8.3 format. <

Or unless the unstable user decided to rename a file to XXXXXX~1. Don't ask me why, but there's nothing preventing this possibility,
though you might just say that anybody who does this is asking for
trouble!

> So, when you spot such thing, you should correct it as soon as 
possible, else funny things start to happen. <

I agree wholeheartedly.

Sounds like I can choose from the following: 
a) use /NX and XXCOPY copies the files potentially slowly and 
propagates the problem, since that's what's in the source dir.
b) use /NX0 and experience unpredictable behavior
c) fix the problem in the first place, so that the unpredictable
behavior of b) is elimated and then use b).
or 
d) there's also the option of "sorting" the directory using a low
level directory sorting program to sort the directory entries by
SFN. This will allow programs like XXCOPY or Explorer (or a DIR
without a /O clause), to access the files in the proper order, thus avoiding unpredictable behavior. 

d) is in fact what I've been doing, up until Win2k, where my DIRSORT
utility no longer works. I think I need to set my eyes on a program
to do c), or else find a new Directory sorting program that works under 
Win2K. I'd be willing to bet the DIRSORT actually does work, but
the installation dies when it detects Win2k and the author is nowhere
to be found.

> Again, it's not XXCOPY which did this in the first place
and /NX or /NX0 does not contribute or correct the situation. <

Never said it was. I was just hoping it might be able to help.

I remember, Joseph, you are using Windows 2000. In that case,
to observe the SFN which is attached to a file with LFN is not
as easy as in Win9x because the DIR command would not give you
both LFN and SFN. You can use



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