Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Conflict With winsock
#8
(08-26-2018, 02:17 AM)tultalk Wrote: As I indicated in original post, FTP upload 16k text file truncated to 1440 or 2880 using Indy (9.0.11), uploads the full 16k using ICS.

9.0.11 is a VERY old version. The last version of Indy 9 was 9.0.50. Please upgrade to that version, if not to Indy 10.

That being said, which TYPE mode are you uploading files in - ASCII or BINARY? The FTP protocol defaults to transferring files in ASCII mode, and so does TIdFTP (I don't know what ICS defaults to). That mode doesn't really affect TIdFTP itself (as it always transfers raw binary data as-is), but it would affect how the server receives and stores the files. Unless you need (or don't mind) line break conversions between platforms, you should always transfer files in binary mode. See the TIdFTP.TransferType property for that.

(08-26-2018, 02:17 AM)tultalk Wrote: When I invoked program conditional _WINSOCKAPI_ got different errors.

As you should be, since you are disabling winsock.h, but are using components that depend on the VCL's Winsock unit, which depends on winsock.h. That must be a carry-over from your ICS tests, because Indy doesn't use the Winsock unit at all (and never has), it has its own IdWinsock2 unit, which uses winsock2.h instead.

Reply


Messages In This Thread
Conflict With winsock - by tultalk - 08-24-2018, 05:52 PM
RE: Conflict With winsock - by rlebeau - 08-24-2018, 09:59 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 02:17 AM
RE: Conflict With winsock - by rlebeau - 08-27-2018, 08:15 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 03:14 PM
RE: Conflict With winsock - by tultalk - 08-26-2018, 06:55 PM
RE: Conflict With winsock - by tultalk - 08-27-2018, 11:39 AM
RE: Conflict With winsock - by tultalk - 08-27-2018, 01:34 PM
RE: Conflict With winsock - by tultalk - 08-28-2018, 02:24 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)