Thanks Thorsten! I was not aware of these changes. Finally a step into the right direction. I wonder when the (not so) "special" characters ":?" will become acceptable in file and directory names.. -- Dominik Psenner
On Thu, Feb 21, 2019, 11:22 Thorsten Schöning <[email protected] wrote: > Guten Tag Dominik Psenner, > am Sonntag, 2. Dezember 2018 um 08:58 schrieben Sie: > > > Unfortunately windows in the year > > 2018 still has a fixed path limit of something along 260 characters. > > It doesn't: > > > The Windows API has many functions that also have Unicode versions > > to permit an extended-length path for a maximum total path length of > > 32,767 characters. > > > https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation > > In case of legacy software which doesn't care about long Unicode paths > being available for decades: > > > Starting in Windows 10, version 1607, MAX_PATH limitations have been > > removed from common Win32 file and directory functions. However, you > > must opt-in to the new behavior. > > > HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled (Type: > REG_DWORD) > > Computer Configuration > Administrative Templates > System > Filesystem > > Enable NTFS long paths > > > https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail: [email protected] > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...........05151- 9468- 55 > Fax...............05151- 9468- 88 > Mobil..............0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
