Re: Path is too deep error
- From: "Terry R." <F1Com@xxxxxxxxxxxxxxx>
- Date: Tue, 24 Feb 2009 19:20:10 -0800
The date and time was Tuesday, February 24, 2009 7:03:11 PM, and on a whim, John John (MVP) pounded out on the keyboard:
Terry R. wrote:The date and time was Tuesday, February 24, 2009 1:14:01 PM, and on a whim, John John (MVP) pounded out on the keyboard:
Terry R. wrote:Yes, the OP was. But in the testing done by Pegasus (which I replied directly to), his file/folder depth didn't exceed the limitations of Joliet.The date and time was Tuesday, February 24, 2009 12:43:41 PM, and on a whim, Pegasus (MVP) pounded out on the keyboard:The OP is having problema on a USB stick, not a CD and these old Joliet limits were change quite a while back!
"Spamcop User" <spamcop_user@xxxxxxxxxxxx> wrote in message news:%23uWV6srlJHA.4912@xxxxxxxxxxxxxxxxxxxxxxxMaybe your example didn't exceed the Joilet limit. I believe Joliet is restricted to 64 Unicode characters for the filename and 64 for the directory path. I regularly get messages that filenames will be truncated when backing up certain folders to CD/DVD.
John JohnThis appears to be a moving target. First you wrote (and I quote): "Windows cannot handle properly anything over 8 levels deep". Now you restrict your claim by saying that it only applies to folders burnt to CD, then copied back to a hard disk. This does not appear to be correct either - see below:
Recored a CD then copy it back
You will see for yourself
Some protection for CD's including Visual Studio is done over 8 levels deep to protect it from being copied
As you suggested, I did this:
1. Create a folder tree on drive C: of 20 levels.
2. Place a file inside.
3. Burn it to CD (drive F: on my machine)
4. Copy it back to drive E:.
And here are the results:
C:\>dir /s /b F:\xxcopy.txt
f:\Spamcop User\1\2\3\4\5\6\7\8\9\10\11\12\13\14\15\16\17\181\19\20\xxcopy.txt
C:\>dir /s /b E:\xxcopy.txt
e:\CD1\Spamcop User\1\2\3\4\5\6\7\8\9\10\11\12\13\14\15\16\17\181\19\20\xxcopy.txt
To support your claim you should now post a process that you have tried and proven yourself so that others can duplicate the phenomenon you insist on.
http://www-plateau.cs.berkeley.edu/people/chaffee/jolspec.html#relaxation
John
There is still limitations, as stated in your link, and because as I said, I have had burning issues where I was informed the length was too long and therefore truncated.
Yes, as with all file systems there are limitations, we know it's nothing to do with Windows not being able to handle properly anything over 8 levels deep...
John
Agreed.
Terry R.
--
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.
.
- References:
- RE: Path is too deep error
- From: Riyazuddin Sk
- Re: Path is too deep error
- From: Spamcop User
- Re: Path is too deep error
- From: John John (MVP)
- Re: Path is too deep error
- From: Spamcop User
- Re: Path is too deep error
- From: Pegasus \(MVP\)
- Re: Path is too deep error
- From: Terry R.
- Re: Path is too deep error
- From: John John (MVP)
- Re: Path is too deep error
- From: Terry R.
- Re: Path is too deep error
- From: John John (MVP)
- RE: Path is too deep error
- Prev by Date: Re: New registry DWORD value
- Next by Date: Re: Unable to get ICS to work
- Previous by thread: Re: Path is too deep error
- Next by thread: Re: Path is too deep error
- Index(es):
Relevant Pages
|
