SuperBK
2007-12-03 17:39:22 UTC
I have searched and only found one mention of this. I find it amazing
that such a blatant bug could still exist. When I use Wininet's
FtpGetFileSize() the size returned is incorrect for a file larger than
4.2 Gig. My file is (7,119,037,160 bytes), FtpGetFileSize() returns
4294967295 for the low size and 0 for the high size. Also,
FtpFindFirstFile() doesn't return the correct size either.
The data back from the ftp server, as seen in the ftp command line
client looks like this:
213 7119037160
which is the exact size of my file.
Is there any workaround? Use an ftp client that doesn't use Wininet?
Thanks,
Brian
that such a blatant bug could still exist. When I use Wininet's
FtpGetFileSize() the size returned is incorrect for a file larger than
4.2 Gig. My file is (7,119,037,160 bytes), FtpGetFileSize() returns
4294967295 for the low size and 0 for the high size. Also,
FtpFindFirstFile() doesn't return the correct size either.
The data back from the ftp server, as seen in the ftp command line
client looks like this:
213 7119037160
which is the exact size of my file.
Is there any workaround? Use an ftp client that doesn't use Wininet?
Thanks,
Brian