X-Spam-Check-By: sourceware.org Message-ID: <44B98274.1010407@tlinx.org> Date: Sat, 15 Jul 2006 17:04:04 -0700 From: Linda Walsh User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: pathnames >255 characters: supported by NT, not cygwin... References: <00ec01c6a1dd$ab40c1b0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <44AECD02 DOT 2090306 AT tlinx DOT org> In-Reply-To: <44AECD02.2090306@tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Linda Walsh wrote: > Dave Korn wrote: >> Still lacking in useful information. You *still* haven't told us >> HOW on >> earth you managed to get impossibly long file names, you *still* >> haven't shown >> us the names of any directories that have failed. --- (from: http://support.microsoft.com/?kbid=320081 Resolution 5: Use a tool that can traverse deep paths Many Windows programs expect the maximum path length to be shorter than 255 characters. Therefore, these programs only allocate enough internal storage to handle these typical paths. NTFS does not have this limit and it can hold much longer paths. You may experience this issue if you create a share at some point in your folder structure that is already fairly deep, and then create a deep structure below that points by using the share. Some tools that operate locally on the folder tree may not be able to traverse the whole tree starting from the root. You may have to use these tools in a special way so that they can traverse the share. (The CreateFile API documentation describes a method to traverse the whole tree in this situation.) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/