WinSCPPortable integration with PuttyPortable is messy. It wouldn't launch putty automatically or interactively and will ask you to manually launch it. Everytime I set the settings in WinSCP to point to the PuttyPortable.exe file, WinSCPPortable.exe overwrites the settings with path to "PortableApps\WinSCPPortable\App\winscp\PuTTYPortableLinker.EXE." There are two ways to fix this:
- Change WinSCPPortable.exe
- Change PuTTYPortableLinker.exe
I chose option 2 as it was easy. Here are the steps:
- Rename "PortableApps\WinSCPPortable\App\winscp\PuTTYPortableLinker.EXE" to "PortableApps\WinSCPPortable\App\winscp\PuTTYPortableLinker1.EXE."
- Copy "PortableApps\PuTTYPortable\App\putty\PUTTY.EXE" to "PortableApps\WinSCPPortable\App\winscp\PuTTYPortableLinker.EXE."
This will launch putty right from winSCP automatically.
This does come with a price - the settings for Putty will be stored in the registry. Since I use portable apps on only few computers, this is OK for me, much better than launching putty manually every time. In fact, I renamed "PortableApps\PuTTYPortable\PuTTYPortable.exe" to "PortableApps\PuTTYPortable\PuTTYPortable.exe1" so that I don't have two different set of settings.
Here is something I did more to make my life easier:
- After running this setup for first time, launch "PortableApps\WinSCPPortable\App\winscp\PuTTYPortableLinker.EXE" and set the options for "WinSCP Portable Temporary Session"
FULL ACK, the integration sucks.
ReplyDeleteFollowing your suggestion, I did the following:
- moved whole content(!) of "PuTTYPortable" directory to "...\WinSCPPortable\App\winscp\"
- there I renamed "PuTTYPortable.exe" to "PuTTYPortableLinker.exe"
- and then I renamed "...\WinSCPPortable\App\winscp\App\AppInfo\Launcher\PuTTYPortable.ini" to "PuTTYPortableLinker.ini"
This then runs a truly portable PuTTY (settings in INI file instead of regsitry) directly from WinSCP.
Victor