Results 1 to 10 of 19

Thread: Issues with long path names

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #4
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Issues with long path names

    Update 1: most internal and external I/O components in SetupBuilder make use of the standard MAX_PATH in the Windows APIs. The maximum length for a path is MAX_PATH, which is defined as 260 characters. We have to check if it's possible to increase MAX_PATH without creating negative side effects :-(

    Update 2: starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions. We have to find out how to handle this scenario for Windows environments prior Windows 10, version 1607 and how to opt-in to the new behavior. Interesting problem. In the Windows APIs to create, say, a directory, the specified path cannot be so long that you cannot append an 8.3 file name (that is, the directory name cannot exceed MAX_PATH minus 12).

    Update 3: even WinZip only supports the "Simple Long Path" method. 260 characters is the maximum (the unzip process fails here because the internal folder structure and the output folder is >260 bytes). But of course, we have to fix the buffer-overrun bug in SB.

    To sum it up: 260 bytes is the expected limit for all systems prior Windows 10, version 1607.

    Friedrich
    Attached Images Attached Images   

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •