Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

anoncoward

Re: winscp419 - copy remote to local failed at 4GB of data

<covering face in shame>

disk does indeed have plenty of space.

Unfortunately I did not realize filesystem was Fat32, which is apparently limited to 4GB max file size. <sigh>

sorry
anoncoward

Re: winscp419 - copy remote to local failed at 4GB of data

I have now tried logging in with SFTP withOUT allowing SCP fallback, and I still get the same error.
martin

Re: winscp419 - copy remote to local failed at 4GB of data

SCP protocol does not allow more then 4GB. Please read documentation.
anoncoward

winscp419 - copy remote to local failed at 4GB of data

(reposted, in case it was lost on end of 2GB file size wrapping report)

Copy of remote file to local directory failed on file reaching max unsigned 32bits.

Reports insufficient disk space to write file, asks what to do (abort, retry, skip, skip all, etc.)

destination drive has > 500GB available.

winscp 4.1.9, build 416 (per help about box)

The item was a foreground download, not queued.

add'l:
I presume this was via SCP connection. filesize after abort was 4,294,947,919 bytes (which is a rather strange 19377 less than 2^32.)

Glancing at code briefly, guessing it may be related to some of the 'int' parameters variables involved in the TStream/TMemoryStream/TFileStream/THandleStream family of objects (even though the seek() methods of at least TFileStream and THandleStream apparently support 64bit offsets, implying their internals probably should also - but a TMemoryStream is also used in TFileBuffer::WriteToStream(), which I expect may be the source of the error.)