[BUG] with "Error executing program"

[XPEHOPE3KA]

The best way to describe this bug is to show this image

I suggest, someone could have encountered such a bug before me. If so, post a link here, please.

[Sheepdog]

Errmm, what exactly did you do to get this message? My crystal ball has gone a bit misty today.


I can reproduce it by trying to start the 16 bit Total Commander from a partitition with more than 40 Gigabyte space. But this is no error but plainly clear since you can't register those big values with 16 bit variables.

sheepdog

[petermad]

2Sheepdog

I can reproduce it by trying to start the 16 bit Total Commander from a partitition with more than 40 Gigabyte space

You wrote something similar in the German forum. There must be more to it than just the partition size, because I have NO problems opening the 16 bit TC (6.54a) from a 56 Gb NTFS partition.

[Sheepdog]

Maybe it is because my Partition is FAT32?

sheepdog

[XPEHOPE3KA]

That's a problem with registry.
I doubleclicked on a dll-file. See my registry settings to it:

HKCR\.dll\default value = dllfile
HKCR\dllfile\shell\default value=value not set
The only thing that I have in HKCR\dllfile\shell\ is
HKCR\dllfile\shell\View Dependencies\command and there default value=value not set

That is in fact that for a dll-file I have the only action to View Dependencies, which has no command assigned.

Next, if you delete the key "Command" you'll get the same.
Next, if you delete the key "View Dependencies", TC *may* even hang. It really hangs *often* if these registry settings were true right after you turned on your computer (if you make last two changes and don't log off, TC never hangs).

[petermad]

2Sheepdog

Maybe it is because my Partition is FAT32

I thought that could be it - my FAT 32 partions are not bigger than 32 Gb, so I can't test it.


2XPEHOPE3KA

I don't have a HKCR\dllfile\shell\ at all in my registry - only HKCR\dllfile\ and HKCR\dllfile\Defaulticon - an I get this: http://madsenworld.dk/tcmd/dllerror.png when doubleclicking a dll file: So maybe you should just get rid of the HKCR\dllfile\shell\ since it doesn't have seem to be there.

[XPEHOPE3KA]

2petermad

I've already deleted that key, but anyhow it's a bug!
For some reason, some program when uninstalled hasn't completely removed its settings from registry - this happens each day, and no TC dialog should depend on this.

I don't have a HKCR\dllfile\shell\ at all in my registry

To reproduce a bug create mentioned registry structure.

BTW, HKCR\dllfile\shell\View Dependencies is added by Dependency Walker utility which is shipped with VisualStudio.

[Sheepdog]

2XPEHOPE3KA

Just try to copy the dll entry from HKLM to HKCU. It's well known that TC prefers the key in HKCU. I get the same error on dll files here but none by Explorer. So although I did not test the copying I bet it should work (for me I have no problems with this behavior, because I usually do not doubleclick on DLLs. )

sheepdog

[XPEHOPE3KA]

2Sheepdog
I don't complain on this behaviour as I know how to get rid of it, but this is a BUG and should be FIXED.

I usually do not doubleclick on DLLs

That has no direct connection with dll, but that has with unusual registry settings, which *may* happen on each computer. Dll was only an example. You can reproduce this bug with any filetype, which has only one action with no assigned command.

I get the same error on dll files here but none by Explorer

forget about explorer - I'm speaking of TC bug