Hi,
If anyone ever has this error message then you can resolve this by responding to the escape chars that VMS sends out. Not sure if this is relevant to any other OS types.
[code]
sshConnection.Connect()
sshConnection.WaitFor(Chr(27) & [c )
sshConnection.Execute(Chr(27) & [?1;1c , regex:[$ #>] , 30)
[/code]
This resolves the issue and tells VMS the terminal type.
Regards
Mike
Complete thread:
Many thanks for your excellent support service. I can see why you have a long list of excellent testimonials on your website.
You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.
...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...
The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.
I really like these products - they are consistently first rate!
...not only that you provide these components at very reasonable cost, your responsiveness to emailed technical questions is simply outstanding...
You did a great job on wodSSH and wodSSHServer! I got a lot for very little money. Thanks!
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...
...with a minimum of effort as the DLL interface was written with such simplicity...
![[*]](themes/default/images/complete_thread.png "Open whole thread"){kind=small}