And, there is a syntax with escapes for feeding Very Long Pathnames through Win32.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Monday, December 01, 2003 9:10 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] RE: Prevent writing of files with name >MAX_PATH
You could do so with a file system filter driver.
Just as an aside: this limit is a Win32 subsystem limit, not a Windows limit. The Windows limit is 65534 bytes (32767 characters) and that is enforced by Windows. But that is why Windows itself does not enforce such a restriction.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: Leo Havm?ller [mailto:xxxxx@-nospam-rtx.dk]
Sent: Monday, December 01, 2003 8:58 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Prevent writing of files with name >MAX_PATH
Hi,
This isnt a question about file system drivers, but i know that this is the group where the file system experts are, so please direct me to an appropriate newsgroup or other resource.
We are continously running into problems when people copy files to a Windows 2000 server and the path exceeds 259 characters. The problem depends on the application - obviously because the app uses a buffer limited to MAX_PATH=260.
Can I somehow prevent the users from copying the file to the server in the first place? Ideally I would like to give the user an error, the same way as if he tried to create a file with illegal characters in the filename.
Leo Havm?ller.
Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@basistech.com To unsubscribe send a blank email to xxxxx@lists.osr.com