The VNC Manager - SmartCode Solutions Forum / SmartCode VNC Manager / Feature Requests / Error code message / Latest Posts

RE: Error code message

cse — Tue, 11 Jul 2006 12:22:38 GMT

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

RE: Error code message

Support (s-code) — Fri, 07 Jul 2006 05:13:32 GMT

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 ?

RE: Error code message

cse — Fri, 07 Jul 2006 04:10:28 GMT

Has this been do able?

RE: Error code message

Support (s-code) — Mon, 21 Nov 2005 00:05:16 GMT

[quote]What about not returning an error message?[/quote]

I think this is doable. Will add it to the v3.1 features list.

RE: Error code message

cse — Fri, 18 Nov 2005 10:42:10 GMT

Ok, that was obvious if I had looked.

What about not returning an error message?

Regards

RE: Error code message

Support (s-code) — Fri, 18 Nov 2005 09:23:10 GMT

[quote]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[/quote]

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.

Error code message

cse — Thu, 17 Nov 2005 08:07:18 GMT

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