Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

harkman

Thanks.
This is much appreciated.
harkman

Yes, sure.

But I think you could save the ini location in the registry (I guess you save the setting if a ini file should be used in the registry too?)

So on startup the program could work like this:
1) connamdline ini option set? No:
2) use ini file option = true? Yes:
3) check registry for ini location
4) load settings.
martin

harkman wrote:

I'm sorry I did not expect the commandline would expose settings not available in the GUI configuration panel.

INI file path has to be known before loading the configuration, so it cannot be part of the configuration :)
harkman

Great thank you.

I'm sorry I did not expect the commandline would expose settings not available in the GUI configuration panel.
harkman

Version 5 storage location of winscp.ini wrong!

Hello.

In version 5 of WinSCP there is a issue with the storage location of the winscp.ini (If you switch to file based configuration).

Since the first beta of version 5 I get this error (see attachment) because the application tries to write the configuration file in the programs installation directory.

Version 4 does handle this properly and stores the file in the %APPDATA% directory.

I would love to see a option to define a custom configuration location to be able to save the configfile in my dropbox directory to sync my config file between two locations.

Thank you for this absolutely essential application.