Not sure if that could break installations of STAF running on very old, non-unicode systems.
Just in case, it could, it's possibly a good idea to detect whether those unicode APIs are available and falling back to the ANSI functions, if not... or require explicit configuration defaulting to the ANSI functions.
STAF currently uses the ANSI version of functions in the Windows API.
STAF should be changed to use the Unicode versions of these Windows API functions, e.g. GetFullPathNameW instead of GetFullPathName) to permit an extended-length path of 32,767 characters.