Altap Salamander Support Forums

Running Salamander sandboxed, (Sandboxie 5.12, WinXP) a couple of times now I've gotten I get the message, "Configuration stored in registry is corrupted...".

Running Salamander sandboxed is something I rarely do.
I've hit this a couple times now since Salamander 3.07.

Don't know if it might be an issue (with 3.07 specifically) or just a coincidence?
Don't know any reason that this should be happening?
There is no telling what kind of state my sandbox is in, as in what I may or may not have done to it?


Any others seeing this?
Or I ought to create a new sandbox & see if I happen upon this there?

Salamander is killed while it is saving configuration into registry. We have no idea why, maybe something related to Sandboxie.

Could you reproduce this problem without running Salamander in Sandboxie?

Changes in shutdown handling in 3.07 are Vista+, so it should not change behavior under XP. We have changed slightly also routines for unloading plugins, but I don't expect it is the source of this problem.

Could you reproduce this problem without running Salamander in Sandboxie?

No.
Other then just recently & only when running Salamander in Sandboxie [a couple times now], I've never seen that message before.

New sandbox & I've reproduced it, but I don't know steps to do so consistently?

Basically all I did was to create the sandbox, opened S sandboxed, closed S, opened S sandboxed...
Repeated a number of time, all successfully.

Then I opened Regedit (from a sandboxed C:\ prompt, sandboxed) just to look to see just what is being stored in 'HKEY_CURRENT_USER\Software\Altap\Altap Salamander 3.07' (as to me, I can't really imagine that anything in there should "break" S), then after the next few open/close of S (with Regedit still open), the Corrupt message ensued.

An out of sandbox S does not see the sandboxed version, so Help | Task List is not of value.
(And at present if I try to open another instance of S, where I could use Help | Task List, that too generates the Corrupt message.)

But I can open Salamander 3.06 & work it that way...

Then I opened Regedit (from a sandboxed C:\ prompt, sandboxed) just to look to see just what is being stored in 'HKEY_CURRENT_USER\Software\Altap\Altap Salamander 3.07' (as to me, I can't really imagine that anything in there should "break" S), then after the next few open/close of S (with Regedit still open), the Corrupt message ensued.

Regedit, C:\ prompt, ... are immaterial in reproducing.

Reproducible in Win7.

XP is Salamander 3.07 x86.
Win7 is Salamander 3.07 x64.

And it does appear to be 3.07 specific.
(At least I couldn't duplicate the issue on XP with Salamander 3.06).