Adjust buffer sizes.

[nssm.git] / nssm.h

diff --git a/nssm.h b/nssm.h
index 8e82d59..1ad2b94 100644 (file)
--- a/nssm.h
+++ b/nssm.h
@@ -1,6 +1,37 @@
 #ifndef NSSM_H\r
 #define NSSM_H\r
 \r
+/*\r
+  MSDN says, basically, that the maximum length of a path is 260 characters,\r
+  which is represented by the constant MAX_PATH.  Except when it isn't.\r
+\r
+  The maximum length of a directory path is MAX_PATH - 12 because it must be\r
+  possible to create a file in 8.3 format under any valid directory.\r
+\r
+  Unicode versions of filesystem API functions accept paths up to 32767\r
+  characters if the first four (wide) characters are L"\\?\" and each component\r
+  of the path, separated by L"\", does not exceed the value of\r
+  lpMaximumComponentLength returned by GetVolumeInformation(), which is\r
+  probably 255.  But might not be.\r
+\r
+  Relative paths are always limited to MAX_PATH because the L"\\?\" prefix\r
+  is not valid for a relative path.\r
+\r
+  Note that we don't care about the last two paragraphs because we're only\r
+  concerned with allocating buffers big enough to store valid paths.  If the\r
+  user tries to store invalid paths they will fit in the buffers but the\r
+  application will fail.  The reason for the failure will end up in the\r
+  event log and the user will realise the mistake.\r
+\r
+  So that's that cleared up, then.\r
+*/\r
+#ifdef UNICODE\r
+#define PATH_LENGTH 32767\r
+#else\r
+#define PATH_LENGTH MAX_PATH\r
+#endif\r
+#define DIR_LENGTH PATH_LENGTH - 12\r
+\r
 #define _WIN32_WINNT 0x0500\r
 #include <fcntl.h>\r
 #include <io.h>\r