Quote:
Originally Posted by gm9
The general issue is not new however, if your code is not calling the unicode Windows API functions when dealing with files you always run the risk of exceeding MAX_PATH regardless of the OS. Most of the builtin functions and dialogues use the ANSI calls btw which is why they crash due to buffer overflows in those situations.
edit: http://msdn.microsoft.com/en-us/libr...47(VS.85).aspx
|
The crash occurs on both wide and multi-byte versions of the API, and the path generated (~130 bytes) is significantly less than MAX_PATH (260 bytes). I've written a 5-line program that reproduces the problem and reported the findings to MS. They've opened a ticket to address it. I'll be following it closely.
In the meantime, using custom UIs necessitates picking the advanced option and installing to a directory with a shorter path. I'll talk to the launcher guys and see if we can get a shorter install path by default, but that won't happen until after the holidays.