Path too long?

[leosefcik]

I was making a thing for fun, a folder in a folder in a folder in a folder, and when i hit the 13th level

(C:/Users/Leo/Desktop/FolderCeption/1blahblah/2lol/3boi/4stuffs/5evenmorestuffs/6idk/7folders/8deep/9deepnesswarningdeep/10reallydeepwarningdeepnesslevel100/11okweresoodeeprightnowletsgouplol/12isaidgoup/13okwhateverjustreturn)

i wanted to create a folder called 14secretfilebelowmelol but it just stopped at 14secretfilebelowmelo. 21 characters limit, but what is it? It just makes a beep sound when i try to write more. And when i copy-pasted it it stopped at the 21th character too. Then, when i rename it to 14test and add another folder in it, it worked but this time it was called aaaaaaaaaaaaaa and i couldnt write more a's. When i came inside to add another folder it just gave me an error with title saying: The target path is too long. but things get weirder when i put in a text, i can just add in 1234567.txt and nothing more. but i can edit the file freely. Can anyone tell me why does this happen and if i can bypass it? Thanks in advance

 

[Paul Black]

Hi leosefcik, welcome to SevenForums,

What exactly are you trying to achive?

 

[leosefcik]

Forgot

Hi leosefcik, welcome to SevenForums,

What exactly are you trying to achive?

Oh, yea, sorry, uhmm that if i can fix this and go further and know more about it.

 

[Paul Black]

Hi leosefcik,

The thing is, when you have folders and files that are as deeply embedded as you are creating, it makes it very hard to find files within each of the individual folders. You would be better off coming up with a strategy that is structured in a more logical way so as to make the files easily accessible within each of the folders. It would also increase the search time if you were to do a search for a particular file!

I hope this helps!

 

[leosefcik]

Hi leosefcik,

The thing is, when you have folders and files that are as deeply embedded as you are creating, it makes it very hard to find files with each of the individual folders. You would be better off coming up with a strategy that is structured in a way that it makes the files easily accessible within each of the folders.

I hope this helps!

Ok, thanks! So this means creating deep folders will make it hard for the system to read them, right?

 

[Paul Black]

Hi leosefcik,

OK, thanks! So this means creating deep folders will make it hard for the system to read them, right?

No, the system will still be able to read them.

I am talking about from a users point of view in which the user can find and access the files within the folders quickly. At the end of the day, you don't want to spend a significant amount of time looking for files in order to be able to use them!

I hope this helps!

 

[Megahertz07]

I think that the limit path in windows is 256 characters. This includes disk letter, folders and file name + extension
Ex.: C:\users\Mike\desktop\myfile.zip = 32 characters

 

[iko22]

Yes, Megahertz07 is quite correct. The system can only read pathnames up to 260 characters.

Although, having said that, the NTFS file system allows pathnames up to 32,767 characters, the 260 character limitation was set in the MS-DOS days. I believe you can overcome the 260 character system limitation by using the subst command. NTFS long paths can also be enabled in Windows 10 via group policy.

 

[Paul Black]

Hi Megahertz07 & iko22,

I think that the limit path in windows is 256 characters. This includes disk letter, folders and file name + extension.
Ex.: C:\users\Mike\desktop\myfile.zip = 32 characters.

Yes, Megahertz07 is quite correct.

Although, having said that, the NTFS file system allows pathnames up to 32,767 characters, the 260 character limitation was set in the MS-DOS days. I believe you can overcome the 260 character system limitation by using the subst command. NTFS long paths can also be enabled in Windows 10 via group policy.

The thing is, that with such long file paths it becomes extremely confusing and very difficult to administer!

 

[iko22]

Hi Megahertz07 & iko22,





The thing is, that with such long file paths it becomes extremely confusing and very difficult to administer!

(d) ... but it can be done that way!!!