Custom Query (8073 matches)
Results (280 - 282 of 8073)
|#865||connecting to os/2 ftp server|
While filezilla does connect to an os2 ftp server (IBM's supplied server), when filezilla attempts to get a file listing, if fails:
Status: Connecting to wa4zlw.homedns.org ... Status: Connected with wa4zlw.homedns.org. Waiting for welcome message... Response: 220 shana IBM TCP/IP for OS/2 - FTP Server ver 13:32:38 on Sep 13 2002 ready. Command: USER Response: 331 Password required for. Command: PASS Response: 230 User logged in. Command: FEAT Response: 502 Unknown command. Command: SYST Response: 215 OS/2 operating system Status: Connected Status: Retrieving directory listing... Command: PWD Response: 257 "L:/xfer" is current directory. Command: PORT 156,12,52,164,13,39 Response: 200 PORT command successful. Command: TYPE A Response: 200 Type set to A. Command: LIST -a Response: 550 No files found Error: Could not retrieve directory listing
At this point user can't do anything without the directory information.
For some reason the IBM ftp server doesn't like list -a:
Connected to wa4zlw.homedns.org. 220 shana IBM TCP/IP for OS/2 - FTP Server ver 13:32:38 on Sep 13 2002 ready. User (wa4zlw.homedns.org:(none)): 331 Password required for . Password: 230 User leon logged in. ftp> bin 200 Type set to I (Image/Binary). ftp> list -a Invalid command. ftp> quit 221 Goodbye.
On Windows platforms newer than WinXP besides SetFilePointer+SetEndOfFile preallocation method which fills required disk space with zeros which might take a lot of time in case of a very large file, there is another literally instant function: SetFileValidData (see MSDN), it just claims disk space leaving intact whatever data there was.
Despite common belief that fragmentation isn't an issue, it's quite the opposite - 1+GB files downloaded in such applications as FileZilla Client which doesn't preallocate disk space, are extremely slow to copy and work with when mounted and impose absolutely unnecessary huge load on HDD due to a lot of disk seeks.
Apparently only a few win32 ftp clients can preallocate space and none of them uses SetFileValidData. Out of about 20 most popular ftp clients I've tested, only Flashget and NetTransport had the feature. Actually I've searched all files on my PC and out of hundreds of small and large win32 apps that constantly deal with creation of files, large and small, only VirtualDub and uTorrent use SetFileValidData, also the latter allows user to select whether he prefers instant preallocation, complete with zeroing or none of the two.
There was a similar ticket (#1486) 7 years ago and now it's already 2012 but FileZilla Client still doesn't preallocate space.
|#3567||On z/OS - unable to switch from HFS to MVS file listing|
If z/OS server is set to default to HFS (Unix) the client is unable to switch to normal MVS file system. It appears that there is a mistake with the FileZilla directory information. If a user is in HFS the CWD prefixes with a "/". To go to native MVS file system the client should drop the "/" prefix. Here's some info from the log;
Command: CWD /'tsospw3.' Trace: CFtpControlSocket::OnReceive() Response: 550 CWD cmd failed : EDC5129I No such file or directory. (errno2=0x05190050)
What I entered in the "Remote site:" box was;
If I "Enter custom command" here's the log;
Command: cwd 'tsospw3.' Trace: CFtpControlSocket::OnReceive() Response: 250 "TSOSPW3." is the working directory name prefix.
However, even though I can do the custom command the GUI interface stuff still insists on using the "/" prefix. It seems that if a user enters something in the "Remote site:" box that is a single quoted (') string the Filezilla client should NOT attempt to prefix the string with the front slash (/).