Altap Salamander Support Forums

Hi !

Since few days i have a problem with Salamander.

I press the COMMAND button, and get the error message:

(87) Parameter is incorrect

Did anybody knows this error ?

THANK,
Bernhard

You might check this thread http://forum.altap.cz/viewtopic.php?f=2&t=5030

Hi !

Thanks for that.

But i have this entries with COMSPEC, ....

This error message also appears with other user profiles.

So, according to the linked thread, I ask:

therube wrote:Are you able to run Start | Run -> CMD ?

Of course i can run die command prompt via START-RUN

Thanks,
bernhard

So apparently (according to a Google search), error 87 is not very descriptive. What is the value of your COMSPEC?

SOrry.

But its the only error message i got.

COMSPEC=C:\windows\system32\cmd.exe

I really dont know why this happen.
But i can´t install the hole computer because of that problem

Thanks,
Bernhard

So I did another Google search and this time it showed better results suggesting that the command line could be too long (although I can't see why ). Could you record the problem with Process Monitor and post the log here (zipped PML is the best format)?

Also the CUSTOMIZE function does not work

I create a user bar just with "Notepad.exe"
At a txt-file i press F9, then my Customize button and this error appears:

the filename, dir. name or. vol label syntaax is incorrect


I tried this on other machines, and there works perfectly. (also the Command)


Our collegue told me, his salamander tolds him something like
" Do you want to delete/use one copy of Servant Salamander? "

I deleted everything at the local drives, registry.

Thanks for your help.
Bernhard

It's a wild guess, but it might be that the "working directory" of the Salamander process is somehow wrong (too long, or containing special characters, I'm not sure). It would really help if you posted here the Process Monitor log file capturing both of these problems happening. Of course, you should also try backing up your Salamander configuration, deleting it and seeing if the issue wasn't resolved by this.