https://www.novell.com/documentation/oes11/stor_nss_lx/data/b5wurur.html
Please extend this limit to lets say 65k. When migrating from other filesystems, fileservers to nss its a pain in the neck. You cannot copy large filesystems because copy stops every few minutes and you have to rename, reorganize everything to accept this limit. AFAIK NSS can do 4k. NCP is who cannot do more then 255.
by: Gellért H. | over a year ago | NCP
Comments
That section of the docs is wrong. There is no such limitation in any part of OES code, the limitation is actually *in Windows*.
https://news.slashdot.org/story/16/05/31/0012222/microsoft-removes-260-character-path-length-limit-in-windows-10-redstone
According to the Softpedia article :
"Enabling NTFS long paths will allow manifested win32 applications and Windows Store applications to access paths beyond the normal 260 char limit per node."
So is the Novell client a "manifested win32 application" ? And Microsoft does not allow to access path/filenames more than 256 characters for other application then Windows?
I can create path/filenames with more the 256 characters on a windows share from a windows 7 workstation. This is a big problem, when I migrate from Windows shares to OES file servers and there are longer path/filenames than 256 characters.
There is no difference whatsoever in your ability to create such share on windows or OES servers, they bahave 100% identical. Again, the limitation of 256 characters *EXITS IN WINDOWS* (whikch you can read at that article, which obviously has no conection whatsoever to OES; right?), and has absolutely nothing to do with OES.
One point to remember in path names too long as we deal with it frequently. If the user dos a CUT 1/2 way up the directory tree and PASTE it into another directory where the result is over 256, it will work, but the files will not be accessible. A COPY/PASTE in the same vain does not work. In one you modify the pointer(entry) to the folder you selected which does not touch anything violating the length, in the other you attempt to touch every file in the path.
As of Windows10 in 2017 (and it is a 2017 version) the WINDOWS limit of 256 chars has been removed - very strange to see so many more files on an OES system than they used to see... This Entry should be removed from the ideas portal as it is a non-issue.
Yes it's necessary and basic function for electronic firm company to use the OES to be their wafer file server.
Tim H. This is still very much an issue. I have found that Windows 10 does not get around it either--at least not in the case of copying from an NSS volume using NCP client.
Windows 10 no longer 256 character actually,we try to copy the exceed 256 characters name file from NAS to Windows Server from windows 10 client is no issue ,but the issue is occur if copy to NSS volume from same Windows 10 client .
Windows 10 no longer 256 character limitation actually,we try to copy the exceed 256 characters name file from NAS to Windows Server from windows 10 client is no issue ,but the issue is occur if copy to NSS volume from same Windows 10 client
Unlock the 260 character limitation from Windows 10 Client.
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
But the NSS volume still can not support longer than 255 characters no matter what's kind the Windows clients access.
If the documentation for NSS is wrong, can it be updated to be accurate?