Critical file transfer error when download a file

[wyatts]

After changing root drive into B:\ by commnad CWD, I faced Critical file transfer error when download a file.

Reproduction step

1. enter custom command "CWD B:\" (default A:\)
2. refresh for list B:\ drive
3. download one of files in B:\ drive root

Expectation
downloaded successfully

Actual Action
Critical file transfer error

Attaching log file

[Tim Kosse]

Custom commands are just that, custom commands. They bear no semantic meaning, especially not for independent transfer connections.

If you need to transfer files from a particular directory that isn't displayed in the remote file list, use the manual transfers dialog.

[wyatts]

Thanks for the quick response.
I have some questions
After refreshing, the particular directory is displayed in the remote file list.
I think that it should work because I try to transfer files that exist in the remote file list.
Do you mean it is not allowed to transfer files that are not from default drive?
It seems to go to default drive when transfering files because new session is opened everytime transfering.
When I enter "A:\" into default remote directory In the site manager,I faced Critical file transfer error.

Is Manual transfer a unique solution when I try to transfer files after changing directory?

[wyatts]

I've opend the issue to get the answer for the last comment that I left.
Thanks

[Tim Kosse]

As can be seen by the reply to the PWD command, your server uses a Unix-style path syntax.

A:\ is a relative Unix-style path. Assuming for example the current path is /some/thing/, the result of CWD A:\ is /some/thing/A:\/ or, if the server treats backslashes like slashes as some servers do, /some/thing/A:/

That said, you cannot even enter relative paths into the default remote directory field, the Site Manager shows an error in that case.