Altap Salamander Support Forums

lzh anomaly. No big deal, but since I came across it, just thought I'd note it... 1. Salamander with the lzh archive open -vs- extracted file contents ("invalid" entries) 2. Salamander extracted contents -vs- lha extracted file contents ("invalid" entries) 3. 7zip extracted file contents -vs- lha ex...

Date: 12-31-1979 shows as 1-1-1980

Voidtools (Everything Search Engine) forums, Date: 1-1-1980 shows as 12-31-1979.

So....



(For some reason, Is it live or is it Memorex has been popping into my head.)

(Already mentioned here, Full path too long. Really?)

(Was waiting until I had run into it again...) XP SP3, 2 GB RAM No, no "sub-processes". Browser (SeaMonkey, largest RAM user) was open (as it always is). Two sets of "Memory", Private bytes & Working set. (SeaMonkey) was using about 1300 MB | 800 MB. More typical would be for the numbers to be close...

And just what is the issue?

Is the picture a picture of the issue?
Or is the jpg a sample of a jpg that does not display correctly?

I don't know what "correct" is, but saved from dropbox, it opens & displays fine on this end.


(And while we're on dropbox, Drop Box Breach.)

Cannot Close Salamander from a Right-click (& Close, of the) Taskbar Icon - sometimes. This is nothing new, just thought I'd mention. Not a big deal, but would rather it didn't happen, if possible. From what I recall, it may occur if you attempt the close just after you initiated a close in another ...

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).

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 ...

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

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 ...

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.

Salamander Configuration Corrupted.png 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 Salama...

Ach, to bude ošklivý ... zatímco v okně najít, můžete zvolit chtěli soubory a použít možnosti kontextová menu Path Copy Copy zkopírovat do schránky. ------- oh, this is going to be ugly... while in the Find window, you can select wanted files & use "Path Copy Copy" context-menu options to copy to cl...

? Path Copy Copy

Thanks.