Re: When copy from CD to HDD (exessively long header truncated)


"MIUSS" <miuss@xxxxxxxxx> wrote in message
news:2160001f-552d-4041-b53f-6aa656904cff@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 16 Pro, 12:32, "Pegasus \(MVP\)" <I....@xxxxxxxxxx> wrote:
"MIUSS" <mi...@xxxxxxxxx> wrote in message

news:14268f02-a2d5-420f-af71-23fe7ed71693@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Hello,

I'll try to introduce my problem:

I've got a CD where is located few directories with more
subdirectories and I need to copy all of them to determined directory
on a shared folder on server. When the destination I choose is not too
much deep (that means to example S:\Share\Projects\Test\), it's
successfully proceeded. But when I choose deeper destination (like S:
\Share\Projectse\Subdirectory01\.....\...\...\..\..\..\..\..
\..Subdirectory10\) then Total Commander reports me the faults like
"Directory was not created", "Do you want to overwrite this file/
directory"(although it couldn't exist before I start to copy) and
simmiliar reports.. :-( In addition there's one strange thing, there
are some DWG files content. These files lost their formats so they
can't be open in AutoCAD. I got experiences with this strange
behaviours in last half year sometimes and I really don't know what
could be the cause of this:( I use NTFS and I look to its limitations
and it seems that there can't be anything wrong in there (I've found
NTFS filename 255 characters, pathname cca 32000 chars). The cd file
system is CDFS...

Could you please advice me what else can be wrong?

Thank you very much in advance!

Mike.

You need to limit the total path+file name to about 258 characters (same
as
the Subject line of your post).

Thank you pegasus, this was my first presumption until I find the
limitation details for NTFS on wikipedia:

http://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits

You can read from the table that filenames on NTFS can have 255
characters and full path name can have "32767 characters with each
path component (directoryname or filename) up to 255 characters long".
So why do I have to limit full path name to 258 charachters? Did I get
something wrong? Or are there some another limitations to example from
OS and such?

Thank you!


While it is correct that NTFS supports path+file name lengths of up to 3276
characters, most applications (such as Windows Explorer) don't. Here are a
couple that do: ntbackup.exe, robocopy.exe. Until Windows Explorer, your CD
burner and most other major applications support the full NTFS path length,
you have to put your information into your files, not into the path or file
name.


.

Relevant Pages

  • Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2
    ... >> I still got occasional hangs. ... whethe the Unicode (i.e. NTFS) to your code page conversion fails (NLS ... maybe your terminal/gui may dislay some garbage characters if it does not ... That is just Gnome and in particular gconf stuff (i.e. the Gnome ...
    (Linux-Kernel)
  • Re: convert to short name
    ... >Every time you create a file with a long file name, NTFS ... extension containing 1 to 3 characters. ... the fsutil behavior set disable8dot3 command to disable ...
    (microsoft.public.windowsxp.customize)
  • Re: File names size limit?
    ... For NTFS the limit is 256 characters and this includes the whole ... include it with Vista but later they removed the proyect from Vista, ... If successful the command will create a path of some 300 chars. ...
    (microsoft.public.windows.file_system)
  • Re: When copy from CD to HDD (exessively long header truncated)
    ... subdirectories and I need to copy all of them to determined directory ... But when I choose deeper destination (like S: ... NTFS filename 255 characters, pathname cca 32000 chars). ...
    (microsoft.public.windows.file_system)
  • Re: [BUG]: Software compiling occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2
    ... > whethe the Unicode (i.e. NTFS) to your code page conversion fails (NLS ... > As the message suggests if you adjust your mount options to include the ... > maybe your terminal/gui may dislay some garbage characters if it does not ...
    (Linux-Kernel)
Loading