![]() ![]() If the key is not set, a section inherits the state of its parent section. Setting a configuration section read-only makes WinSCP silently discard any changes to that section, when saving the configuration.Īn access to individual sections is controlled using an optional Access key. This way you can for example prevent a user from changing default transfer settings, while still allowing other kinds of customizations. You can set individual configuration sections read-only. Particularly, when using a shared INI file or when pre-configuring WinSCP for a specific task, you may want to set the configuration or its parts read-only. This is also the configuration mode used by WinSCP. That is particularly useful for scripting, to make sure that the script always starts with all defaults. With /ini=nul command-line switch, WinSCP starts with the default configuration and does not save the configuration on exit. You may also use an INI file in a different folder or with a different name using /ini switch or in preferences. If the directory is not writable, INI file is stored to application data directory of your user profile. When you opt to use INI file for the first time, WinSCP tries to write it to directory, where WinSCP executable is stored in. to C:\Users\username\AppData\Roaming\WinSCP.ini. If INI file in not found there, WinSCP looks to application data directory of your user profile, i.e. ini extension and the same name as the executable (i.e. When loading configuration, WinSCP first looks for an INI file in the directory, where WinSCP executable is stored in. If you use registry as configuration storage, the configuration is stored under the following key: See Sharing WinSCP configuration between machines using cloud storage. ![]() Sharing the Configuration between Machines ![]() Transfer the URL to the target location, paste it to the Login dialog and save it. If you want to transfer just one specific stored site, you can generate a session URL from the site on the source location (make sure you include Advanced settings to the URL). To transfer your configuration to another computer/location, export the configuration to an INI file and then import the file on the another computer/location. See also How do I transfer my settings from a non-working computer? Transferring the Configuration To import/restore the configuration, go to Tools > Import/Restore configuration on Login dialog. This folder is 100% portable and does not even access the C drive.In older versions of WinSCP, use Export button on Preferences dialog. Running KittyPortable.exe with the -convert-dir param will create several folders in your kitty_portable folder, including all of your PuTTY settings (which are now stored in plain textfiles instead of using the registry, like PuTTY does. Delete kitty.exe (you won't ever need it again).Go to a DOS shell, cd to the kitty_portable directory, and type:.It will pull in all of your PuTTY config settings. Download both the Windows Classic and Windows Portable.Create a folder somewhere called kitty_portable (preferably not on.Then go to a PC on which you have admin rights (your home PC, maybe), install PuTTY, double-click the exported registry file that you exported earlier (this imports all the PuTTY sessions), and then. HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SessionsĪnd do File/Export (make sure the radio button for "selected branch" is selected). So you would need to export your PuTTY registry keys at work and import them on your home PC. But maybe your home machine doesn't have the PuTTY config settings that you use at work. So you need to convert your PuTTY settings to Kitty on a machine you have admin rights on, such as your home machine. Many people do not have admin rights on their PC at work, but this is where you might want to use KittyPortable. This approach will not work if you don't have sufficient privileges to install Kitty Classic. ![]() = If you do NOT have administrative rights on your PC, continue reading. I was able to accomplish it indirectly by installing Kitty Classic, which automagically picked up PuTTY's registry keys, and then running The problem is that, being portable, KittyPortable does not even LOOK at the C drive, so it can't read the PuTTY keys in the Windows registry. I have been unable to get PuTTY settings directly into KittyPortable. Cyd's answer seems to apply to Kitty Classic (not Portable). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |