Search the Community
Showing results for tags '256 characters'.
Hello - I have tried searching the forums a bit and I did find this helpful post - But I was hoping for some clarification before I start work on my pools. 1. Since DrivePool uses UNC, are MaxPath restrictions not an issue if programs are accessing the pool drive directly AND if the pool drive's file length is under the maxpath length limit (256 characters)? By that, I mean - the PoolPart path length is around 45 characters, so if I have a file within the PoolPart folder that has a path length of 280, then it's over the maxpath limit. But, roughly 45 characters of that is due to the PoolPart foldername. DrivePool has no problems moving it around etc because DP is written using UNC. Within the pooled drive however, that same file will have a path length of roughly 235 (280-45). Does this mean that as long as I only access the files via the pooled drive, there will be no issues with Win32 API from programs that don't support UNC? 2. If the answer to #1 is yes, if I need to evacuate a drive from the pool and use the data somewhere else, can I use robocopy or another UNC compatible program to copy the data OUT of the PoolPart folder? The issue I have is that, like Drashna mentions in his post above, I'm meticulous with my folder and filenaming, but I'm trying in general to stay under the 256 limit and not regedit the maxpath restriction away. So I'm planning path lengths in a pool that will be in the 240s/250s, which will go over the limit in the PooPart folders, but still be copacetic in theory in the actual pooled drive itself. Sorry if I'm overcomplicating things and thanks Christopher/Drashna and the CoveCube team for all of your work on this amazing product.