![]() You wrote, one should use it as is, but it is not working for me! Hi, I know this is a quite old post and there are some solutions proposed in this and other posts, but why is it that integration is not working still? StrCpy $EXECSTRING `"$PORTABLEAPPSDIRECTORY\PuTTYPortable\PuTTYPortable.exe" $0` ![]() StrCpy $EXECSTRING `"$PORTABLEAPPSDIRECTORY\PuTTYPortable\PuTTYPortable.exe"` StrCmp "'$0'" "''" "" LaunchProgramParameters MessageBox MB_OK|MB_ICONINFORMATION `Please start PuTTY Portable before attempting to use PuTTY integration within WinSCP Portable.` StrCmp $FAILEDTORESTOREKEY "true" "" GetPassedParameters VIAddVersionKey ProductName "$ "HKEY_CURRENT_USER\Software\SimonTatham-BackupByPuTTYPortable" "HKEY_CURRENT_USER\Software\SimonTatham" $R0 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. along with this program if not, write to the Free Software You should have received a copy of the GNU General Public License GNU General Public License for more details. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. but WITHOUT ANY WARRANTY without even the implied warranty of This program is distributed in the hope that it will be useful, of the License, or (at your option) any later version. as published by the Free Software Foundation either version 2 modify it under the terms of the GNU General Public License This program is free software you can redistribute it and/or OSI Certified is a certification mark of the Open Source Initiative. This software is OSI Certified Open Source Software. I think I got this working, testing and feedback would be appreciated. In effect, this would achieve the same as having PuTTYPortable open when the user clicked on the PuTTY button in WinSCP because the registry would be in the correct state. Now you can launch PuTTYPortable and the temp session key will be loaded correctly, without having to have PuTTYPortable open first Restore the registry to it's original state Now we re-import the temp session key into the registry because it is in it's "portable state"Įxport the entire PuTTY key back into PuTTYPortable/Data/settings/putty.regĭelete the portable PuTTY keys from the registry ![]() (Because we've already found PuTTYPortable, so we can access its Data) Import PuTTYPortable/Data/settings/putty.reg into the registry Back up the registry the same way PuTTYPortable does. Simulate a launch of PuTTYPortable.exe (but only the registry edits) reg file.ĭelete the temp session key from the registry Ok, so how about this for an idea? At the point where PuTTYPortableLinker normally deletes that key and sends up an error, why can't we do the following:Įxport just the temp session key into a. So this is why PuTTYPortable must be launched first, so when that key is created, the key will go into the portable version of the registry. So the problem is that the one key HKCU\.\Sessions\WinSCP Portable Temporary Session is a "portable" key, but it has been put into the local version of the registry,so when you launch PuTTYPortable, that session will get backup up as part of the local registry and not passed on to the portable version. At the point where PuTTYPortableLinker.exe sends up the error and the prompt to the user, it has already checked for the existence of PuTTYPortable and found it (from reading the linker source).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |