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: Scripting of WINSCP oder "Command-line" Version?

dab wrote:

I get the following error:
invalid characters in scp command!
here:
pwd

I've never used PLINK. But I would suggest you to check, whether you have UNIX-style end-of-line character (LF = 10) in your input file.
dab

Re: Scripting of WINSCP oder "Command-line" Version?

Thanks, plink is working almost perfectly.
Possible I'm to stupied to use the -m option (batch-mode) but this is real plink question and has no more to do with winscp so it's a bit OT. But feel free to quote me a line about the following error: If I try to use batch-mode and my textfile look like this(as easy example):
pwd
pwd

I get the following error:
invalid characters in scp command!
here:
pwd

When i have only one command line then it works fine ...

try using a wildcard to match this file/directory
martin

Re: Scripting of WINSCP oder "Command-line" Version?

I'm not sure, but maybe PLINK (another application from PuTTY package) might do the work, just redirect list of commands to it. Let me know, if it does not work.
dab

Scripting of WINSCP oder "Command-line" Version?

I have to work with a scponly ssh-server, which works perfectly with WINSCP. But I have to do transfers from another application. How can I realize this???
First I thinked about use of pscp (beacause that some part of WINSCP is based on putty?) to do the transfers but i can't do "ls", "md" or "rm" with pscp and in WINSCP it works perfect!

Thanks for a short feedback.

Daniel