Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: you cannot move physically a file on a remote computer

aliber wrote:

Can you make it an option to let the user decide? My server doesn't support it but it would sure be nice to be able to have the file move automatically to a different filesystem.

You can make a custom command for that.

Especially since this causes the error to come up when I have the recycle bin feature enabled so I have to have the recycle bin feature turned off.. :cry:

What error?
aliber

Re: you cannot move physically a file on a remote computer

But I cannot know that the server does not allow the move between filesystem by itself.

Can you make it an option to let the user decide? My server doesn't support it but it would sure be nice to be able to have the file move automatically to a different filesystem.

Especially since this causes the error to come up when I have the recycle bin feature enabled so I have to have the recycle bin feature turned off.. :cry:

Great program btw, and the old Norton Commander interface is the bomb :D
martin

Re: you cannot move physically a file on a remote computer

michaa wrote:

OK, now I understand, but I was confused because WinSCP's behaviour is different from moving (physically) files localy with the explorer, where you do not need to copy and delete.

That's not about WinSCP, that's about operating system. While Windows function to move files allows moving even between filesystems, the same function of your SFTP server does not allow this.

As written in the documentation:
Note that most servers does not allow moving files across different file systems

That does not mean that no servers allow it. For example both Windows SFTP servers I use for testing also allow moving files across file systems. So again, this is not different behaviour of WinSCP!

And why the non informative error message?

Answered in FAQ.

May be you could improve this operations (copy, new session, delete) to one single operation witch handles the rest in the background?

But I cannot know that the server does not allow the move between filesystem by itself.

There should be a "Verlaufsbalken", do not know the right word. "Verlaufsbalken" means the growing blue line witch represents the amount of data being transferred. The little window appears, but the blue line does not.

It is there. But if you copy/move one file only, it can hardly show anything, as it is once step process. It is useful only if you move/copy multiple files.
michaa

Re: you cannot move physically a file on a remote computer

martin wrote:

Of course. Moving file means just to move the file information and let the data be. You cannot do this between filesystems.
For copy you need to copy the data to anyway, ...

OK, now I understand, but I was confused because WinSCP's behaviour is different from moving (physically) files localy with the explorer, where you do not need to copy and delete. And why the non informative error message?

May be you could improve this operations (copy, new session, delete) to one single operation witch handles the rest in the background?

What would you want "something happening" to be like?

There should be a "Verlaufsbalken", do not know the right word. "Verlaufsbalken" means the growing blue line witch represents the amount of data being transferred. The little window appears, but the blue line does not.

Thanks for your nice programm!
martin

Re: you cannot move physically a file on a remote computer

This is how it is supposed (not) to work. Please read documentation.
If you want to "physicaly" move file to another filesystem, you need to copy and delete the file anyway. WinSCP allows you to do so.

But it works when you copy the file.

Of course. Moving file means just to move the file information and let the data be. You cannot do this between filesystems. For copy you need to copy the data to anyway, so it naturally works even between filesystems.

In this case, the only confusing thing is that you cannot see something happening in the GUI.

What would you want "something happening" to be like?
michaa

you cannot move physically a file on a remote computer

Hi,

(physicaly moving meens not only rename the file but move it physicaly to another hd)

I use Winscp to copy and move (move physically) files between my 2 computers, a debian/linux server and a windows WS. Works fine. But I can move (rename) files on the remote computer (debian/linux server) only within the /home/user1 directory. When I try to move (physicaly move) a file from /home/user1/dir1/file1 to /home/video/*.* I get an error message:
Allgemeiner Fehler (Der Server sollte eine Fehlermeldung bereitstellen).

Fehlercode: 4
Fehlermeldung vom Server: Failure
Anforderungscode: 18

It seems to be related to the fact, that moving a file outside of /home/user1 moves the file to a physically different hd.
But it works when you copy the file. In this case, the only confusing thing is that you cannot see something happening in the GUI.