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

Number   :  4965
Date     :  2003-07-08
Author   :  Garry Deane
Subject  :  Re: copying file with unicode chars from NTFS to FAT
Size(KB) :  2


--- In xxcopy@yahoogroups.com, "ndemou"  wrote:
> If I try to copy a file with a *specific* style of names
> that include unicode chars xxcopy reports that it did copy
> it. But in fact at the destination drive I find a file named
> like "`6A1.tmp" or "`7BA.tmp" etc (i.e. an ` then a 3 digit
> hex). This file is indeed an exact copy of the original file
> but does not have the same name.
> 
> DETAILS:
> 1) The bug *ONLY* apears if I copy the file from NTFS to
> FAT32. It wont apear when copying from FAT32-to-NTFS or
> NTFS-to-NTFS or FAT32-to-FAT32 (yes it was borring to try
> them all ;-).
> 
> 2) I have confirmed the bug in this style of names: a file
> name of 8 chars maximum of which at least one is unicode.
> The extension seems not to be important. I havent seen this
> bug in any file name with more than 8 chars 
> For example you may try to copy a file named "1234567w" but
> replace w with unicode char 1E85 which is a "w" with two
> dots on top of it
> 
> 3) I used xxcopy 2.84.6 but I think I had the same problem
> with xxcopy 2.84.0. The command line is:
> xxcopy "n:\test" "f:\test\" 
> n:\ is an ntfs volume
> f:\ is a fat32 volume
> 
> 4) I run xxcopy on windows 2000 pro
> 
> This bug troubles me a lot because I copy files with greek
> file names. So I can't copy those with file names of 8
> characters!
> 
> Nick Demou

This is not necessarily a permanent fix may be worth looking at to 
see if it can temporarily resolve the problem. Since it appears long 
file names are being copied correctly, the problem may be restricted 
to 8.3 names containing extended/unicode characters. There is a 
registry key which controls whether extended/unicode characters can 
be used in 8.3 names. Setting this value to 0 MAY (not tested) cause 
8.3 names with unicode characters to be created with LFNs. On the 
other hand, it may cause the loss or conversion of those characters. 
Below is a copy of the NT Resource Kit reference regarding the key. I 
assume it would be the same on W2k.

HKLM\System\CurrentControlSet\Control\FileSystem\NtfsAllowExtendedChar
acterIn8dot3Name

"Determines whether the characters from the extended characters
(including foreign access characters) can be used in 8.3 short
filenames on NTFS volumes. If the value of this entry is 1,
extended characters are permitted. If the value of this entry is
0, 8.3 short filenames on NTFS volumes are limited to the standard
ASCII character set (minus any reserved values)."

I guess you could also disable the creation of 8.3 filenames 
(...\FileSystem\NtfsDisable8dot3NameCreation) but that seems a bit 
drastic.

Note that these settings will only come into effect after a reboot 
and only apply to newly created files.

If this change works for you, please post back as others seem to be 
having this same problem.

Garry



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