Re: resume issue in 4.04
This has been resolved already. The fix will be included into the next release.
- martin
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.
Topic review
- martin
Re: resume issue in 4.04
I have sent you an email.
- martin
Re: resume issue in 4.04
OK, thanks. I'll try to solve that.
- Crepeau
resume issue in 4.04
Concerning the resume issue (see my previous topic far below) , I am very disapointed.
I download 4.04 , and use it in DOS mode
And after this downloading, when a communication break occurs, transfer of a large file doesn't restart at all
see the log file:
Searching for host...
Connecting to host...
Authenticating...
Using username "100.0.0.126".
Authenticating with pre-entered password.
Authenticated.
Starting the session...
Reading remote directory...
Session started.
Active session: [1] mysession
batch on
confirm off
transfer binary
D:\data\essai19M.ex | 8924 kB | 376.9 kB/s | binary | 46%
Network error: Software caused connection abort
(A)bort, (R)econnect: Abort
Network error: Software caused connection abort
Copying files to remote side failed.
Session 'mysession' closed.
No session.
No session.
end of log file
Is there any difference in settings between 4.02 and 4.04 ?
I currently work with settings in winscp.ini file
I only found the following settings:
confirmResume = 1
resumeSupport=1
resumeThreshold=102400
these settings seems OK
can I check any other settings in winscp.ini ?
Any idea ?
thanks for your product and your support
Alain Crepeau
______________________________________________________________________________
currently use winscp 4.02 in DOS mode.
After a communication break, WinSCP tries to reconnect automatically every 2s . ( By the mean, this delay cannot be changed -refer to my previous topic)
If the communication break is too long ( 2 or 3 hours), the transfer cannot resume correctly after communication repair and
The following message :
No buffer space available.
appears
For information, memory space used by Winscp.exe grows up to 18MB !
______________________________________________________________________________
I download 4.04 , and use it in DOS mode
And after this downloading, when a communication break occurs, transfer of a large file doesn't restart at all
see the log file:
Searching for host...
Connecting to host...
Authenticating...
Using username "100.0.0.126".
Authenticating with pre-entered password.
Authenticated.
Starting the session...
Reading remote directory...
Session started.
Active session: [1] mysession
batch on
confirm off
transfer binary
D:\data\essai19M.ex | 8924 kB | 376.9 kB/s | binary | 46%
Network error: Software caused connection abort
(A)bort, (R)econnect: Abort
Network error: Software caused connection abort
Copying files to remote side failed.
Session 'mysession' closed.
No session.
No session.
end of log file
Is there any difference in settings between 4.02 and 4.04 ?
I currently work with settings in winscp.ini file
I only found the following settings:
confirmResume = 1
resumeSupport=1
resumeThreshold=102400
these settings seems OK
can I check any other settings in winscp.ini ?
Any idea ?
thanks for your product and your support
Alain Crepeau
______________________________________________________________________________
currently use winscp 4.02 in DOS mode.
After a communication break, WinSCP tries to reconnect automatically every 2s . ( By the mean, this delay cannot be changed -refer to my previous topic)
If the communication break is too long ( 2 or 3 hours), the transfer cannot resume correctly after communication repair and
The following message :
No buffer space available.
appears
For information, memory space used by Winscp.exe grows up to 18MB !
______________________________________________________________________________