JustinEzequiel's point concerned a filename, not the total length of a full path. And for NTFS the maximum length of a filename is 255 (other file systems that Windows might be able to use may not have the same limits). There is, therefore, an API call (GetVolumeInformation) that can return, amongst other things, the the actual current maximum file name length for a specific volume. For NTFS volumes this returns 255. Guaranteed.
And I have never come across an occurrence of the 'filename too long' problem that was caused simply by the filename itself being 200 characters or more (but less than 255). It has always turned out to be caused by the fact that the full path is too long (a related error sometimes occurs if illegal - as far as Windows is concerend - characters get into the filename, as can happen if you are sharing volumes with other operating systems such as MacOS X)
>just find it's shortened name in CMD prompt
Careful. Although the default for XP is to support the creation of shortnames alongside along names it is not always guaranteed, as enterprises may elect to deactivate it.