Keeping previous INI file when switching to new version of WinSCP
Hi. I continue to be impressed by this robust program. I've sent many your way to find it and hope they'll become loyal users supportive of your work.
I prefer to use the stand along application file rather than download the Installation Package. Therefore, I do my own placing of files and shortcut creating. I also like to continue using the INI file from the previous version.
QUESTION: So far, I believe that I've updated the application file twice and kept the INI file in use by copying from the previous folder and RENAMING it, for example, from winscp356.ini to winscp368.ini . I've never seen any posting about doing this, but it seemed logical and has not caused any problems that I am aware of. I just wanted to make sure that your naming convention will continue and I can expect success ifI follow this procedure should I choose to update to v3.7.1.
Salutations to you!
Best,
Werdhi
I prefer to use the stand along application file rather than download the Installation Package. Therefore, I do my own placing of files and shortcut creating. I also like to continue using the INI file from the previous version.
QUESTION: So far, I believe that I've updated the application file twice and kept the INI file in use by copying from the previous folder and RENAMING it, for example, from winscp356.ini to winscp368.ini . I've never seen any posting about doing this, but it seemed logical and has not caused any problems that I am aware of. I just wanted to make sure that your naming convention will continue and I can expect success ifI follow this procedure should I choose to update to v3.7.1.
Salutations to you!
Best,
Werdhi
_________________
Windows XP Home (SP II)
PIV 2.4 Ghz
1 GB RAM
56k Dial-up
Windows XP Home (SP II)
PIV 2.4 Ghz
1 GB RAM
56k Dial-up