dir >C:\Users\roboticus\JUNK
Then see if the JUNK file is actually created. If so, you're not starting your batch file. I originally guessed that you were having trouble starting the batch file, but I'm thinking that you're actually having problems with Net::SSH2. If that's the case, I won't be much help, as I don't use that package (nor any similar ones).
...roboticus
When your only tool is a hammer, all problems look like your thumb. | [reply]
[d/l] |
Hi and thanks roboticus !
My batch does run now but there is still no display of the cmd windows printing the output of my script.
Still open to any idea :)
Porax
| [reply] |
Porax:
So putting a command like that in the beginning of your batch file actually generated a file? If so, and your batch file isn't doing what you expect, then I'd check the environment of your batch file to see if it's different from when you run it under your perl script. To do so, I'd first put this in your batch file:
set >C:/Users/roboticus/JUNK
Then you can see what the various environment variables are. Then check your path, etc.
...roboticus
When your only tool is a hammer, all problems look like your thumb. | [reply]
[d/l] |