Annoying "Error executing program" message

[pawelsky]

In my FS plugin in FsExecuteFile method I handle the open verb in the following way:

Code: Select all

if (strcmp(Verb, "open") == 0)
{
  return FS_EXEC_YOURSELF;
}

When I press ENTER on such file in the plugin this works fine only for files that have some shell->open->command associated in registry (e.g. txt file opens in notepad, .jpg file opens in image viever, etc.). Unfortunately for files with extensions that don't have any associations (e.g. .xyz or no extension at all) I always recieve "Error executing program" message which is quite annoying.

Is it an expected behaviour? Can this message be somehow disabled?

[Sir_SiLvA]

This is a Windows-Message...

2nd you dont need to open a new thread for every question.

[pawelsky]

This is a Windows-Message...

Well, the Message box has "Total Commander" in the title bar so this is rather a TC popup, not a Windows one.

2nd you dont need to open a new thread for every question.

My two questions were about two completely different problems, so I think it's better to have them in separate threads.

[Sheepdog]

My two questions were about two completely different problems, so I think it's better to have them in separate threads.

Right.

sheepdog

[CoMiKe]

2nd you dont need to open a new thread for every question.

I don't think this is the best way to talk to a potential plugin developer...

[pawelsky]

As there are no replies let me rephrase the problem.

I have a my_example_file.no_assoiciation file (with extension that has no association in registry) on a C: drive

When I press ENTER on this file in TC, Windows opens an "Open with..." dialog box. Now I copy the file to my plugin's filesystem and press ENTER on the copy. Instead of the "Open with..." dialog I get the "Error executing program" message from TC (this is not a windows message as Sir_SiLvA suggested).

Why is the behaviour different on C: drive than on the plugin filesystem? Note that for files with extensions that have some associations in registry behaviour is exactly the same on C: drive and on filesystem plugin - the file is opened with the associated application.

You can reproduce this problem also on other FS plugins (e.g. Temporary Panel by Sergey Puljajev http://www.totalcmd.net/plugring/temporarypanel.html) so this rather looks as problem in TC.

P.S. I use Windows XP SP2 and TC 6.54