saving Salamander's configuration to the registry

[ibex]

I somewhat confused about Salamander_2.5 When closing Salamander it always saves its configuration to the registry... and this consumes in comparison to Salamander_2.0 distinctly more time Deselecting 'save configuration on exit' within the menu 'options - configuration - general' is only valid for the running instance of Salamander. When opening and closing it once more, it again saves its configuration automatically.

Am I doing something wrong? Currently I still have installed and running Salamander 2.0 in parallel.

Espacially when experimenting with the configuration of Salamander - for example when setting window colours -, it's sometimes very helpfull not automatically to save the messed configuration to the registry.

Best regards and many thanks for your suggestions in advance!

[Jan Rysavy]

Try to defragment your Registry using NTREGOPT and let us know.

[zarevak]

Deselecting 'save configuration on exit' within the menu 'options - configuration - general' is only valid for the running instance of Salamander.

You changed the configuration to not save the configuration automaticaly, but you haven't saved the configuration with this change After deselecting "save configuration on exit" you should save the configuration manualy. (Maybe Salamander should inform the user about this)

[therube]

In addition, if you have multiple instances of SS open, you must close those that may still have Save On Exit enabled first, then manually Save Configuration on that last remaining instance. (If you did not do that, then the other instances, when closed, would overwrite the setting to not save settings .)


Earlier, slow configuration saving thread, Saving configuration on exit / multiple instances.

[ibex]

thanks to all, who responded to my subject! I've learned from your answers

Defragmenting the registry distinctly accelerated the procedure of 'exit Salamander and save its configuration on exit'!

Regards, Gerd