https://www.webmaster-forums.net/crss/node/1019026 en https://www.webmaster-forums.net/server-side-scripting/filesystems-and-file-access-effeciency#comment-1112733 <p>Paths do matter. For optimum performance, you are best using the shortest possible path. It is probably not going to be all that big of hit but it can be. It will as you have seen make the links rather long which can make emailing them and accessing them sometimes difficult.</p> Tue, 20 Aug 2002 11:53:27 +0000 mairving comment 1112733 at https://www.webmaster-forums.net https://www.webmaster-forums.net/server-side-scripting/filesystems-and-file-access-effeciency#comment-1112714 <p>Yes, Win machines still have that 255 (or so) character limit <em>for the entire path</em>.</p> Tue, 20 Aug 2002 06:38:26 +0000 Mark Hensler comment 1112714 at https://www.webmaster-forums.net https://www.webmaster-forums.net/server-side-scripting/filesystems-and-file-access-effeciency#comment-1112710 <p>well, i think while creating an environment for my benchmark i stumbled upon the answer, at least as far as NTFS is concerned.</p> <p>i wrote a script to create a directory structure 50 levels deep, containing a random number of randomly named files and directories between 1-100 in each. When the script got 30ish levels deep i started getting errors like "the directory 'kdfie9_kf\jfie9\...\...' doesn't exits". Basically, what (i think ) this means a NT filename such as 'myfile.txt' is really, internally named 'path\to\myfile.txt'. Which is nice, i think...</p> <p>i assume what happened is i hit the filename character limit, which id guess is 255.</p> Tue, 20 Aug 2002 05:15:43 +0000 ROB comment 1112710 at https://www.webmaster-forums.net