這是歷史版本頁面 — 看 FlashFXP 最新版本

FlashFXP 4.1.5 Build 1667

FlashFXP 軟體圖示 FlashFXP 4.1.5 Build 1667 資料更新 2011-11-08

FlashFXP 操作介面
FlashFXP 的操作介面

下載與官方連結

前往官方網站 下載 FlashFXP

FlashFXP41_1667_Setup.exe · 3.3 MB · 連結指向軟體原廠

版本紀錄

再看 5 筆

看完整版本清單

這一版改了什麼

What's new in this version:

- Fixed an issue that resulted a false positive error "Change Folder Failure: (5: Access is denied)" during upload. The IO result wasn't cleared before testing for failure.
- Fixed an issue where switching between MLSD and LIST (or stat -al) didn't correctly clear the remote folder cache.
- Added a work-around specifically for XeXMenu FTPD 0.1 to address an issue when navigating into empty folders.
- Fixed an issue where the oldest site in the quick connect history was removed when the history limit was reached, instead of removing the site with the oldest last connection time.
- Fixed an issue where FlashFXP was throttling the rate at which commands were sent to the server, this was most noticeable during recursive deletes and when transferring many small files.
- Fixed changing the per-site preserve file date/time settings in the file transfer rules dialog didn't take immediate effect.
- Fixed proxy/connection failure when connecting to an sftp server, resulting in an error message 'SSH Error: The packet is too large.'
- Fixed a connection failure that occurred under the following conditions, connect to a ftp+ssl server and then disconnect before the ssl handshake completes, now connecting to a non-ssl ftp server, after about 30 seconds the connection attempt would fail.
- Fixed an access violation that occurred when performing an en-queued operation (rename, exec custom command, move, delete).
- Fixed reported progress percentage during an en-queued delete operation, the progress would jump between the correct value and 100%, and the progress bar wasn't shown on the status-bar.
- Fixed an issue where several toolbar buttons would enabled/disabled while transferring a queue under multiple different conditions.
- Added additional support to handle servers that report the remote path as "//path/to/my/home", the tree navigation wasn't allowing "//" as a valid root.