View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012488 | MMW v4 | Other | public | 2015-01-13 18:07 | 2015-10-01 13:04 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | duplicate | ||
| Target Version | 5.0.0 | ||||
| Summary | 0012488: LongFilenames: NFS/NTFS/SMB 3.0 Long Filenames support up to 32k path | ||||
| Description | Problem is due the Windows back compatibility limitations even NTFS actually supports it see 0011799:0039472 and document http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx#maxpath I created generic app to create such long paths and access/change files in with 100 success rate. NOTE: Linux Systems do not have such issues. I confirmed that Both Windows and Linux support path+filenames up to 32k Unicode Windows Support is from XP SP3 but Full unicode and usable case sensitive is supported as of Windows 7 (http://support.microsoft.com/kb/100625 and http://superuser.com/questions/266110/how-do-you-make-windows-7-fully-case-sensitive-with-respect-to-the-filesystem ) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| duplicate of | 0012868 | closed | michal | MMW 5 | Ability to support long filepaths (> 260 chars) on Windows |
| related to | 0012459 | closed | Ludek | MMW v4 | Locate Moved/Missing: Full filename and path larger than 260 chars can result in MMW crash |
| parent of | 0011799 | closed | Ludek | MMW v4 | Scanning: Full filename and path larger than 260 chars can result in MMW crash |
|
|
I created small app to test long filenames (limit to aprox 1024 characters) which will stop in case file can't be created,read and deleted from path and will show last length. EXE and sources is on FTP Note I also checked and even Cyrillic, Japanese and Chinese filenames work although example is made with Latin only. |
|
|
Windows always have issues with long paths in certain environments (even if it is NTFS), see my notes: 0011799:0039472 and 0011799:0039765 and 0012459:0041864 |
|
|
Tracked as 0012868, resolving this one as duplicate |
