"Michael Fritz" <spam_athome@yahoo.de> wrote in message
news:j3q6i0r5py62$.1hfsmcmxk0yux$.dlg@40tude.net...
> Can't believe this since, as mentioned in my initial posting,
> Internet Explorer shows it up correctly.
That doesn't mean anything. IE could simply be doing what I suggested
earlier - retreiving a directory listing and then getting the size
from that. You can use a packet sniffer to check that.
> Using ICS as socket components and a basic FTP client demo,
> it works, too, so it's definitely an issue with Indy.
Like I said, there are only two possibilities - 1) the server does not
support the SIZE command, or 2) the reply is malformed so Indy can't
parse out the size value.
What is the value of the LastCmdResult.NumericCode property after
Size() returns? If it is not 213, then there is no size value
available for Indy to extract. In your other discussion thread, you
mention that ICS is reporting 550. That would certainly cause Size()
to return -1 in Indy.
Gambit
