FtpFindFirstFile and file sizes

[paul-shed]

If I query a file with a size greater than or equal to 4GB (0x100000000) then
the nFileSizeHigh field in the WIN32_FIND_DATA structure is always zero.

The file size always maxes out for these large files. nFileSizeHigh is zero
and nFileSizeLow is 0xFFFFFFFF.

Why is this?

Is there a patch available?

Regards,

Bob

[Jeffrey Tan[MSFT]]

Hi Bob,

Thanks for your post!

Yes, with writing a small sample application regarding your problem I can
reproduce it. It seems the nFileSizeHigh is always 0.

This is definitely a bug of OS. If you use IE to visit the ftp site with
"Details" view mode, the "Size" column will report 3.99GB for any file that
is greater than 4GB.

After performing some research in our internal database, I found this is a
known issue of the OS. There is a similiar record titiled with
"FtpGetFileSize() doesn't support over 4GB file". This bug record has been
kept in the longhorn bug database, I hope it will be resolved in future OS
release.

Anyway, thanks for your reporting!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[paul-shed]

Post by Jeffrey Tan[MSFT]
Hi Bob,
Thanks for your post!
Yes, with writing a small sample application regarding your problem I can
reproduce it. It seems the nFileSizeHigh is always 0.
This is definitely a bug of OS. If you use IE to visit the ftp site with
"Details" view mode, the "Size" column will report 3.99GB for any file that
is greater than 4GB.
After performing some research in our internal database, I found this is a
known issue of the OS. There is a similiar record titiled with
"FtpGetFileSize() doesn't support over 4GB file". This bug record has been
kept in the longhorn bug database, I hope it will be resolved in future OS
release.
Anyway, thanks for your reporting!
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jeffery,

Thanks for this. I've come across this problem on more than one accasion.

So how do I get around it? What is the official MS workaround for this
problem in Windows XP SP2?

Regards,

Bob

[Jeffrey Tan[MSFT]]

Hi Bob,

Thanks for your feedback!

Currently, there is no official workaround in Wininet for this issue. You
may contact Microsoft PSS for requesting a hotfix for this issue. Since
this is a known issue of our product, this support incident will be free.

You can contact Microsoft Product Support by contacting us at
1-[phone] or by choosing one of the options listed at:
http://www.microsoft.com/services/microsoftservices/srv_support.mspx

Thanks for your understanding!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[paul-shed]

Post by Jeffrey Tan[MSFT]
Hi Bob,
Thanks for your feedback!
Currently, there is no official workaround in Wininet for this issue. You
may contact Microsoft PSS for requesting a hotfix for this issue. Since
this is a known issue of our product, this support incident will be free.
You can contact Microsoft Product Support by contacting us at
http://www.microsoft.com/services/microsoftservices/srv_support.mspx
Thanks for your understanding!
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jeffrey,

Thanks for this. Unfortunately the rest of MS is not that helpful. Saying
that 'FtpGetFileSize' is broken doesn't get me very far on the phone. They
want a KB id or something else to go on.

What I need is some bug id or equivalent so that they can match it on their
database.

Also, is there a number in the UK I can call for this?

Regards,

Bob

[Jeffrey Tan[MSFT]]

Hi Bob,

Thanks for your feedback!

Yes, you can provide the following bug title to them:
"IE OE Sustained Eng. 26395 - FtpGetFileSize does not work as expected for
files greater then 4Gb (dwFileSizeHigh always NULL)"

Note: the bug id is 26395.

Also, you may provide a little sample project for them to reproduce this
behavior. If they still failed to figure it out, please feel free to
provide my email(***@online.microsoft.com) to them.

Thanks!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.