search

xnodeps / superputty

Automatically exported from code.google.com/p/superputty
MIT License
0 stars 0 forks source link

When Using GNS3 with the latest version of SuperPutty, I get error regarding -wt option #426

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. GNS3 tries to launch SuperPutty with the args:  -telnet %h %p -wt "%d" -gns3 
5 -skin 4
This gives error, it seems -wt is not a valid option? Also -gns3??

2. What is the correct syntax?
3.

What is the expected output? What do you see instead?
I expect Superputty to launch with a Tab for the router I launch console to

What version of the product are you using? On what operating system?
1.4.0.4 (GNS3: 0.8.6) (Windows 7)

Please provide any additional information below.
Where are the CLI arguments for Superputty documented? I cannot find them 
anywhere?

Original issue reported on code.google.com by abp...@gmail.com on 28 Apr 2014 at 2:40

GoogleCodeExporter commented 8 years ago 
*SuperPutty.exe --help* will show you all the commandline options (if you have 
single instance only set in settings you will need to close SuperPuTTY first). 
I am not personally familiar with GNS3, does it allow you to specify command 
line arguments sent to the application?

Original comment by jimradford@gmail.com on 20 Jun 2014 at 12:51

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I think this is caused because as far as i know putty shipped with GNS3 is 
patched. It is not the same putty you download from official site.
If you install/run separate instance of superputty, in the first run you are 
advised to set paths to putty executable and so on. This creates a superputty 
configuration file (actually overwrites the one created by installation of 
superputty which is done wth GNS3).
Then when you open a console connection to router in GNS3 it opens superputty 
with the configuration file you have created. It is different than the one 
provided by GNS3 installer and it uses different (standard) putty executable.
Thats why it gives you an error of not a valid option.

SuperPutty should not be altered so you should be ok with new version (until 
something is not broken :) ).

What you can do is to point superputty conf file to putty executables inside 
GNS3 folder. and also the settings folder to the one in GNS3

Original comment by dul...@gmail.com on 14 Jan 2015 at 4:34