Altap Salamander Support Forums

I'm new here but I use Salamander for a hell of years since 1.52 appearence.
I went through all possible versions of Servant/Altap Salamander including betas and RCs and I never got any problems.
At the moment I have Altap installed on three my computers. Two of them are running WinXP so I don't want to talk about them - there's no problems.
Since February I have Vista 32b Ultimate installed on my new PC (core2duo E6600, 4 GB Corsair - dual, MB Asus P5WDH Deluxe)
I was quite happy that my favorite file manager worked pretty well in new system (except some minor issues with network - took a bit time to detect all my computers in neighbourhood).
Strande and unpleasant things started a couple of weeks ago when the new microcode update from Intel was applied to my PC via BIOS update. That fix was also announced by Microsoft as a critical update: http://support.microsoft.com/?kbid=936357

So after applying the fix I obtained big problems with Altap Salamander. When I start the program - system hungs up (not every start but, let's say - every second start of the program)....

I've tried everything during last two weeks - reinstalled Salamander in different ways, applied compatibility to WinXP SP2 of all the executables in the folder, replaced salamand.exe with one offered by the member of Altap staff (attached here at the forum), installed expired (old) versions, ran the program with administrative privileges....
Nothing helped me! System suddenly can become totally unstable, the processor's behaviour - full marginality. First core is in use for 2 - 5%, second core is in use for 100%.
I've tried to roll back to old bios ver and to uninstall the microcode hotfix - nothing works....

Altap Salamander now causes problems anyway... No other programs or applications cause hang up and deep coma of my PC. But I hate to stop using Altap and turn my face to Total Commander or something like that (BTW - Total works without issues by now). Maybe you have detected some strange things concerning compatibility of the program and processor behaviour after applying "necessary" fix from Intel?
I would be happy to get any kind of advise or information from you!
Thanx in advance!

That behavior looks really strange to me. AS AFAIK uses normal OS system calls and no special low level functions. AS is a application.

I would suggest that you reset/clean your CMOS after the update using the mainboard jumper (while the PC is OFF and disconnected from power!!!) Dont forget to write down or atleast remember the current configuration else you will have problems caused by different SATA configurations. (SATA IDE emulation vs native SATA mode)

Let us know...

SelfMan wrote:.... AS AFAIK uses normal OS system calls and no special low level functions.....

Thanx for the reply!
I understand how AS works. That's why I'm here.... I'm totally pissed out!
I even crashed the BIOS on purpose by interrupting the flashing procedure after erasing BIOS step in order to restore the original old BIOS from the support CD! The only thing I did not perform yet - is clearing the CMOS with a jumper or backup battery removing......
I will try that today for sure 'cause I really do not imagine what the hell is going on with that bloody computer!
I will keep you informed.

Added in a couple of hours
So, CMOS was cleared. Than everything was set up back in system settings.
Reboot.
Total manual cleaning of the registry from all traces of Salamander (old installations)
Altap Salamander 2.5 installation (trial - without any registration keys)
Executable (salamand.exe) - original, not replaced by the fixed one from Altap staff.
Program setup (prefs, appearence and so on)
HUNG UP!!! The same as described in my first post.
Reset of the system with the "magic" button.
Start AS (strange start btw, popup window with trial message did not disappear, but program started)
Create Report Bug text.
Attach it here.... Sorry but in zip 'cause txt extension's not allowed.

Waiting for some ideas or advises from Altap Team....

P.S. Sometimes icons and pictograms of files turn to "simple" style. It can be for a couple of types of files (example: gif and jpg turn to simple default icon, other extensions - normal).
P.P.S. One of the installations of the old beta versions caused crash on trying to set program font from default to different - may be that can help understanding the problem....

I have no idea how can Salamander cause whole system hung. It does not install any system driver nor anything similar. It is just application like any other, so I think this is primarily some bug in Vista system.

You can try if older versions cause the same problem - version 2.0 and 1.52. Link for 2.0: http://www.altap.cz/download.html#sal20
Link for 1.52: http://www.altap.cz/download.html#salrel

Is there any error message when system hungs?

Petr, thanx for the reply....
The point is that system does not send any error message 'cause it hungs up totally....
Actually, after hungup SYSTEM & Kernel NT process occupies 55 to 60 % of the recourses. It means explorer stops responding completely. So I am unable to reboot normally (via system buttons) and launch any kinda applications. Funny, that previously launched apps - work and I even can close them.
The core1 is busy for 5 to 7 %
The core2 is totally occupied (100%)
I suppose my next step will be format c: and complete Vista install.
I can for sure understand that Salamander can not theoretically crash the system. Other "heavy" apps, like Photoshop with really hard tasks, 3D Max, other things - work perfectly even when both cores of the processor are loaded for 99 to 100 percent..... Different crazy games from my son (Stalker etc) also work well.....
I will for sure try old versions to make a complete check.... But it's so hard and unpleasant to roll back to old Servant Salamander.....

You may also try to kill explorer.exe process (it will be started automatically again or if not, you can simply start it from Task Manager, see menu File > New Task (Run...), run "explorer.exe").

There are two more thing to try.
- Create a new user profile and run salamander from there.
- Are you using some shell extensions like TortoiseSVN/CVS?

SelfMan wrote:There are two more thing to try.
- Create a new user profile and run salamander from there.
- Are you using some shell extensions like TortoiseSVN/CVS?

Wow.... thanx for the idea.....
Right-clicking caused problems sometimes. I don't use the mentioned above extension but anyway..... You are on the right way...
Concerning the creation of the new user profile - I did the following several days ago: deleted two of three user profiles on the computer (one of mine and one of my wife). I left the user account of my son because he claimed that he had no problems while using his account in general and AS in particular..... I have no idea what bloody program had that young computer freak installed and what shell extensions were added and applied.....
Anyway - when I recreated both user accounts from "zero" - the problem appeared again.
Yesterday I detected that AS has nothing common with hungup problem: I checked the disk management feature (finally) and found out that it does not work properly..... I mean Administrative Tools/Computer Management/Disc Management
I was out of any ideas how to fix that so I started the Vista installation to the different logical drive, than interrupted it after creating all nesessary files and refreshed almost all system librares and some executables manually in the old system folder..... Stupid method (and very sophisticated) but for the moment - no problems!
Anyway I'm pretty sure you are right - something's giong wrong with shell extensions......
Thanx again for the idea.... Would be pretty nice if you write a bit more - just to get some new ideas.
To Altap Staff:
Sorry for trying to charge your excellent program in my private troubles and thanx for patience and understanding. I would like to ask you not to close or delete the topic for several days more - maybe Mr. SelfMan will "generate" some more ideas for me!
P.S. I'm too old for all that shit.....

you are welcome...
Still it would be good to know which extension/program caused the problem.