Bug: Vista File Copy Dialog

[Guest]

A source directory has files named with the pattern filename~N.ext where “Nâ€
is a number 1, 2, 4, 15, etc.

Many files share similar names, but the “N†is unique to each file. When I
copy the folder to a new location (drag-and-drop the folder) I get the File
Copy dialog:

There is already a file with the same name in this location.

- Copy and Replace (filename~2.ext)
- Don’t copy (filename~10.ext)
- Copy, but keep both files

Vista is trying to replace filename~10.ext with filename~2.ext, even though
these are unique files with unique names.


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/co...5e2&dg=microsoft.public.windows.vista.general

 

[Carl Farrington]

A source directory has files named with the pattern filename~N.ext where
“Nâ€
is a number 1, 2, 4, 15, etc.

Many files share similar names, but the “N†is unique to each file. When I
copy the folder to a new location (drag-and-drop the folder) I get the
File
Copy dialog:

There is already a file with the same name in this location.

- Copy and Replace (filename~2.ext)
- Don’t copy (filename~10.ext)
- Copy, but keep both files

Vista is trying to replace filename~10.ext with filename~2.ext, even
though
these are unique files with unique names.

That isn't happening for me. Is the tilde really part of the filename? They
look like they could be 8.3 filenames from a FAT filesystem which may have
corrupt VFAT (long file name) entries or something odd like that. Perhaps it
thinks the LFNs are the same.
What is the source of these files?

 

[Guest]

Thanks for the clues. It seems Vista is confusing my filenames
with 8.3-generated names.
I cannot recreate the problem if the filenames are 9 characters or longer.
The files have tilde+number as part of the name. The source system
creates unique files with tilde+number as part of the name. This is it's
scheme for managing revisions. The files are recently created on
NTFS. To recreate the problem, create these files in a Vista folder.

007419~1.txt
007419~10.txt
007419~2.txt

Actually, if you create the files in Vista, it will complain when you name
the
third file:
-- Do you want to rename "007419.txt" to "007419~10(2).txt"?

 

[Carl Farrington]

Thanks for the clues. It seems Vista is confusing my filenames
with 8.3-generated names.
I cannot recreate the problem if the filenames are 9 characters or longer.
The files have tilde+number as part of the name. The source system
creates unique files with tilde+number as part of the name. This is it's
scheme for managing revisions. The files are recently created on
NTFS. To recreate the problem, create these files in a Vista folder.

007419~1.txt
007419~10.txt
007419~2.txt

Actually, if you create the files in Vista, it will complain when you name
the
third file:
-- Do you want to rename "007419.txt" to "007419~10(2).txt"?

You're onto something here

It's fine with everything (that I've tried so far) except 123456~10.ext
followed by 123456~2.ext
It almost looks as if it's treating the ~10 as binary, but I'm sure that's
just a coincidence.