Custom Query (8117 matches)

I have my hard drive logically partitioned -- the first partition has Windows and FileZilla, the second one is only 40 MB in size for misc. stuff.

When I am transferring a large (51 MB) file to my second partition, at some point (not immediately, but I guess when it runs out of space) FileZilla pops up a window saying that this file already exists and would I like to overwrite it, skip it, rename it, etc. When I choose overwrite it, FileZilla begins transferring the file from the beginning. When I choose rename it, FileZilla creates a 0-byte file with that name and immediately pops up the same window again.

Suggested behavior: pop up a message saying that the volume is out of space and possibly offer to save to a different location.

I downloaded the new versionof Filezilla server, and when double-clicked the exe file pops open a window that looks like it will run like the installer for the client of FZ, but after a fraction of second it disappears and nothing happens.

In case I had a bad transfer I went ahead and downloaded it again from a different mirror, with the same result. To be extra a redundant I tried it one more time a couple hours later, and had the same result.

I tried to eliminate anything on my end which may be interfering, such as antivirus software and other apps, and still have not been able to get it to work, so I thought I should let you know.

Thanks for a great product - I appreciate Filezilla immensely!

I see that someone posted a bug about an incorrect timestamp in UNIX. We are seeing an incorrect datestamp, where the date shown in filezilla is a year later than the actual date. So, a file dated Oct 11 2001 is shown in Filezilla as Oct 11 2002. The file is on a Sun Solaris 2.8 server. If you have a fix for this, let me know, as this is makes Filezilla unusable for us. Thanks.

Margaret mlouie@…