Long file paths in Box Drive

Help & Support
1

I’ve been testing Directory Opus for a few weeks. It solves a lot of problems for us including navigating and accessing files beyond the 260 character limit imposed by File Explorer. It’s also much faster overall.

I’ve run into one issue that is holding us back. While I can navigate to folders well over 350 characters on our mapped network drives, I cannot browse the same path on BOX Drive. When attempting to copy/paste files or open Word or PDF files, DOpus crashes. I checked both the Logs and %TEMP% for crash logs and found none. Sometimes CTRL+C (copy) causes the crash, other times attempting to open the DOCX with Word but Word will close before opening the file. Again, this only occurs when browsing Box.com Drive loud. Browsing the local and network mapped network drive path works perfectly.

I've also tested the same path over 350 characters on OneDrive with DOpus and again it works fine. I also noted that browsing Box.com Drive is much slower than OneDrive cloud navigation or network mapped drives. Perhaps there is an interface issue between Box Drive and DOpus?

Using DOpus 13.6 x64 on Windows 11 64 Enterprise

2

Opus doesn't treat Box drives differently to any other path. That sounds like a bug in Box.

In fact, Box says as much on their support site:

Box only supports file or folder names that are 255 characters or less .

1 Like
3

Thank you for that reference. That is clearly the issue.

1 Like