Re: [ARMini-support] SafeStore Question
- From: Steffen Huber <steffen@xxxxxxxxxxxx>
- To: armini-support@xxxxxxxxxxxxx
- Date: Wed, 28 Jun 2017 20:38:57 +0200 (CEST)
A Rawnsley <rcomp@xxxxxxxxxxx> wrote:
(Another one to watch out for, since I've been battling it all day today,
is that Windows' max file path is smaller than RISC OS' at roughly
200chars. There's the potential there for *very* deep folder structures
to cause issues. This one always makes me smile, in a way, because
everyone expects Windows to be soooo good for that kind of thing, yet RISC
OS actually handles longer paths!)
This is not correct. What path length Windows supports depends on
the FS and the API the software trying to read/write the path
uses. NTFS and/or the Windows Unicode file API has a path length
limit of 32767 characters. Each part of the path name has a
limit of 255 characters.
Typical problem I am facing daily: "native" Windows Git using
MingW uses the old Windows API and is limited, when checking
out stuff, to 260 characters max path length (260 minus the
terminating null and the necessary preceding drive letter of
course). When using Java (JGit via Eclipse/EGit) however, very
long paths are no problem.
IIRC, Windows Explorer at least in Windows 7 still uses the
old API, so this leads to the user experience that there is
such a path length limit. At least, they got rid of the
"you can only delete 32767 files at once in a directory"
problem...
See here the info from the horse's mouth:
https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx
It looks like Windows 10, if you change a registry key,
allows longer paths by standard.
Steffen
--
Steffen Huber LambdaComm System – Welcome to Trollinger Country
steffen@xxxxxxxxxxxx
Private homepage
http://www.huber-net.de/
RISC OS Blog
http://riscosblog.huber-net.de/
---
To alter your preferences or leave the group,
visit
//www.freelists.org/list/armini-support
List-related queries to info@xxxxxxxxxxxx
Other related posts:
