Wed Mar 30, 2016 3:00 pm
There was also a user complaining recently about write permissions denied because the drive itself only had a logical path name and not a "proper" name. The safest names for drives basically go back to MSDOS alphanumerics only. If you put in a slash, or a # sign, dash, asterisk, or anything like that the browser will either get lost or simply refuse to move or create files.
There is a reason that Apple delivers its computers with the boot drive named "Macintosh HD" -- frankly even the lowercase alphanumerics may give some cross-platform OS grief. Like a Linux overlay, for example may have trouble -- if you get into generating DCPs, this will become another issue.
jPo