More clues.
Now looking at Wireshark data to try and analyse what is going on.
Test 1:
My application small FTP file: All OK
Test 2:
My application with large file: Not OK, seem to be missing the "FTP 226
Transfer Complete" from server to client.
Test3:
Running xferdemo3w. This works OK. The F
Graham Powell wrote:
> I have tried Passive, Active, ASCII and Binary modes - no difference.
Have you tried with the OverbyteIcsFtpTst demo yet?
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/tws
The OverbyteIcsFtpTst demo suffers from the same problem. No ftpPutAsync
event generated at the end of the transfer.
Graham
-Original Message-
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On
Behalf Of Arno Garrels
Sent: 26 November 2012 15:49
To: ICS support mail
Graham Powell wrote:
> The OverbyteIcsFtpTst demo suffers from the same problem. No
> ftpPutAsync event generated at the end of the transfer.
Interesting, Angus should know how he tweaks the ICS component
to make them working.
--
Arno
--
To unsubscribe or change your settings for TWSocket maili
> My code just does putAsync and waits for the ftpPutAsync event.
> I don't know exactly how the xferdemo3w does it
You have all the source code for TMagFtp, so you can easily check. There
are probably two main differences:
1 - TMagFtp uses the sync FTP calls and WaitUntilReady, so check that
f
