Search found 5 matches
- Mon Feb 14, 2011 11:42 am
- Forum: Client - Issues
- Topic: Command line hangs when user not logged in
- Replies: 4
- Views: 2476
Re: CoreFTP hangs in task scheduled whether user logs in or
Here's something odd- If my program calls corecmd with -s for silent and I run the program directly, it works fine. Here's the command and (redacted) log: c:\progra~2\coreftp\corecmd -site x -s -dira abc dirdump.txt Started on Monday February 14, 2011 at 02:03:AM Resolving ftp.x.com... Connect socke...
- Mon Feb 14, 2011 7:59 am
- Forum: Client - Issues
- Topic: Command line hangs when user not logged in
- Replies: 4
- Views: 2476
Re: CoreFTP hangs in task scheduled whether user logs in or
Tom- I upgraded from WS 2003 to WS 2008 to find out that corecmd no longer works correctly from a scheduled task. I have a program that shells out to corecmd to grab a directory listing with the -dira command, then the program processes that file list for new files, uses corecmd to download those, p...
- Sun Aug 12, 2007 11:34 pm
- Forum: Client - Issues
- Topic: Core FTP 2.0 and lots of files
- Replies: 0
- Views: 742
Core FTP 2.0 and lots of files
When I try to access a directory containing about 61,000 files, Core FTP always gives an "Error loading directory..." message. I don't know if it's a timeout or out-of-memory issue. Both Core FTP 1 and 2 do this.
Thanks-
Sean
Thanks-
Sean
- Sat Jan 27, 2007 12:07 am
- Forum: Client - General
- Topic: Error loading directory... when lots of files
- Replies: 1
- Views: 323
Error loading directory... when lots of files
Hello- I'm using Core FTP Pro V1.3c build 1447.6. It works fine, except that I have one directory on my FTP site that has lots of files, and Core always gives me "Error loading directory... disconnected" when I try to bring it up. I don't really need to see the files there as I'm only uplo...
- Wed Dec 28, 2005 1:11 am
- Forum: Client - Issues
- Topic: Norton whack-a-mole notice
- Replies: 0
- Views: 293
Norton whack-a-mole notice
Hello- I was uploading about 1700 smallish files when Norton AV popped up a notice saying it had blocked the Whack-A-Mole trojan, and gave CoreFTP as the filename. I did a search and found that trojan uses port 12361. I'm guessing CoreFTP used that port and triggered the message, but wanted to check...