I did a quick search on the forum and didn't see anything related to FindFirstFile, so I thought that I would post to see if anyone has seen something similar. I have an application that uses the Win32 FindFirstFile/FindNext/FindClose functions. The reason that I use the API as the .NET directory/file functions are limited to 256 characters or so for the full directory/file name and my customer file systems often have far more than 256 characters.
I'm seeing an issue with ONLY Windows 2003 x64/XP x64 where the FindFirstFile will not pick up the first directory name correctly (only showing the first character of the directory name). I can run my application on other flavors of Windows, both 32bit and 64bit, with no issues.
I did a search on Google as well, but I could not find a reference to this particular issue. Anyone else run across this, and if so, any solution?
TIA
I'm seeing an issue with ONLY Windows 2003 x64/XP x64 where the FindFirstFile will not pick up the first directory name correctly (only showing the first character of the directory name). I can run my application on other flavors of Windows, both 32bit and 64bit, with no issues.
I did a search on Google as well, but I could not find a reference to this particular issue. Anyone else run across this, and if so, any solution?
TIA
