|
|
|
Forum Newbie
Group: Forum Members
Last Login: 7/11/2006 12:18:51 PM
Posts: 7,
Visits: 10
|
|
| While waiting for in builtin ssh and telnet capabilities, would the following be possible: The 'do not connect on error' works great and reports the error number. If the error is a specific value then an error message box is not reported. This allows for access via vbs script to telnet or putty (or anything else) without receiving an error message. As an aside, can I call vbs scripts direct? I currently just use a batch file to pass on the same arguments to a vbs script - not a major issue, but tidys things up. Regards
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2 days ago @ 10:30:35 PM
Posts: 836,
Visits: 1,364
|
|
As an aside, can I call vbs scripts direct? I currently just use a batch file to pass on the same arguments to a vbs script - not a major issue, but tidys things up Yes, you can do it. Actually two of the sample scripts (start/stop VNC service) included with the VNC Manager are vbs based. When you adding new script, you should enter cscript.exe as executable name and your vbs file as argument.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 7/11/2006 12:18:51 PM
Posts: 7,
Visits: 10
|
|
| Ok, that was obvious if I had looked. What about not returning an error message? Regards
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2 days ago @ 10:30:35 PM
Posts: 836,
Visits: 1,364
|
|
What about not returning an error message? I think this is doable. Will add it to the v3.1 features list.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 7/11/2006 12:18:51 PM
Posts: 7,
Visits: 10
|
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2 days ago @ 10:30:35 PM
Posts: 836,
Visits: 1,364
|
|
since v3.1 was never released and scraped in favor to v3.5, so this feature didn't make it too ..just kidding 
But anyway, it's not implemented yet. What you actually suggesting will require a GUI that will allow the end user to build some conditions. I'm not sure how many users would use such feature. Could you please give an example of a typical use case for such? You mention Putty... but I don't see why current error conditions are not enough to satisfy Putty's needs ?
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 7/11/2006 12:18:51 PM
Posts: 7,
Visits: 10
|
|
| The idea is for the vbs script to return the error code. Eg for putty: Dim Args
set Args = WScript.Arguments
Set WshShell = WScript.CreateObject("WScript.Shell")
ip = Args.Item(0)
WshShell.Run "putty -ssh " & ip, 1, false
WScript.Quit 999
|
|
|
|