Transfer dialogs popping up

Report client bugs
Post Reply
ForumAdmin
Site Admin
Posts: 1011
Joined: Mon Mar 24, 2003 4:37 am

Transfer dialogs popping up

Post by ForumAdmin »

Article reposted - unintentionally deleted.


Posted: 13 Apr 2005 01:18 pm Post subject: Transfer dialogs

--------------------------------------------------------------------------------

I am using Core FTP Pro build 1391. Is there any way to suppress dialog boxes? I am attempting to download files from the command line and when I tested the case where the file was not on the server was hung up waiting for a "File does not exist" dialog. I am using the -s flag but this only suppresses the splash screen and GUI. I am not certain of the time that the file will arrive on the server. Is there a means to check for the existance of a file unattended?

Another thing I've noted is that when the file transfer is successful it is logged with a status of 3. If I turn on email notification the email states erroneously that the transfer failed.

Thanks,
Tom

--------------------------------------------------------------------------------

Tom,

This has been fixed in the 1.3c release.

Chris

--------------------------------------------------------------------------------

Chris:
I've upgraded to build 1417.05 and I still receive the dialog boxes.


--------------------------------------------------------------------------------

A few things that might help:

1: view -> options -> transfer -> uncheck 'display transfer dialog'.

2: With the 1417 and greater builds, there is a -hide option you can add to the command line that will hide the transfer dialog.

Wait a minute, those might not help your scenario, are you saying you still get a 'file not found' dialog? If so, what command line parameters are you using?

--------------------------------------------------------------------------------

Looking closer, I can see where the problem would occur. We'll get a change out there shortly.

--------------------------------------------------------------------------------

fixes for this issue are in build 1417.07 and greater.
Post Reply