Richard,
you were right. Waitfor isn't that smart to wait for command to be executed. Rather, it waits for your fullprompt> and when it find it it returns.
Now, you have a problem if you don't consume first fullprompt> that was sent by the server immediately upon login. If you don't eat that one, you will get invalid responses all the time.
Can you try that?
Kreso
Complete thread:
![[*]](themes/default/images/complete_thread.png "Open whole thread"){kind=small}
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
You made it so simple for us to integrate SFTP - a technology we had little experience with...
Brilliant, even works on the mobile phone...
Your .NET components allow us to blend .NET technology seamlessly with secure communication, and with excellent technical support.
...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...
Don't be fooled by the cost, it's value and quality far exceeds the price being charged!
...with a minimum of effort as the DLL interface was written with such simplicity...
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...