Altap Salamander Support Forums

Today, while using Salamander as usual, I suddenly noticed strange things happening.
First, I thought my keys were not working in Salamander. But a closer look showed, that the screen was just not updated completely.
I restarted Salamander to see if that helped. But sadly, it became much worse, in that every line suddenly filled a large part of the screen!

After comparing the registry entries with a saved configuration, it turned out that the entry "Panel Font" was corrupted. It contained the value: "en Bosch.doc,1764584545,1766072423,115,105,99,116,32,68", instead of "Fixedsys,-12,400,0,0,1,2,1,49".
The start of the string is the last part of a filename I worked with.

I recollected some memory about the exact same behavior, and I found out that it happened to me once before, on 16-10-2003 with some beta 9. The value then was "Fixedsys,807412332,540028960,34,0,1,2,1,49" (named "Basic Font" in that version).

I am afraid I will not be able to reproduce this strange situation.

Thank you for the report. Are you using Eroiica Viewer to display your .DOC documents?

EDIT: Only the one registry entry was corrupted in whole Salamander configuration?

Jan Rysavy wrote:Thank you for the report. Are you using Eroiica Viewer to display your .DOC documents?

Sometimes, not often. I do not think I used it today, before the corruption happened.

Jan Rysavy wrote:EDIT: Only the one registry entry was corrupted in whole Salamander configuration?

I just compared to a previous config: yes. And after fixing this one entry, everything works as usual.

I now remember that I changed some Hot Paths before it happened. And I unchecked all Hot Path checkboxes, and unselected my only "drive separator".
These are things I don't do very often. Other than that, nothing special I'm afraid.

Or... wait... In the "Grep History", I found a recent and relatively long entry ending with the filename; I searched for file containing this text: "Start converting the html to MS Word file: D:\Users\Michel\Src\DataDetective\Problems\POLDM\BBN\Scripts\Results\Partial\20091102T054937_S\Diefstal-inbraak woning District Den Bosch.doc"
The same text occurs in the "Viewer History" list (searching for the text in the log containing it).
Could it be a buffer overrun, perhaps not counting the doubled backslashes in the registry key? No, 184+12<=200.
Just speculating of course...

It just happened again, accidentally.
I can now reproduce it:
- Using Ctrl+F, search for files containing a specific text with length 180 characters or so
- For a found file, press F3 (View, with the internal text viewer) and F3 (Find Next) again
The first 101 characters are highlighted, although the Find dialog only allows 100.
- Close the viewer
Now Salamander's display is garbled: many things are not updated.
- Close Salamander (with automatic saving of settings)
Now Salamander has a corrupted registry configuration.

One does not need backslashes in the text searched for.

One time, I got this error restarting Salamander with corrupted registry:
Error Loading Configuration
(234) More data is available.

Hope this helps.

Great, I can see error message with string ending with random characters, so something is buggy there. I'll fix this, thanks for your report!

Well, it was buffer overrun, buffer was 101 characters long, we were storing up to 201 characters into it. It is fixed. It will be available in version 2.53 (in preview build).