file shredder app not shown in context menu

[Mark Spencer]

Hello. The File shredder app (https://www.fileshredder.org/) does not show up in the right click context menu in one commander, however it does show up in windows explorer. What is the issue?

[OneCommander Support]

You can try shift + rightclick in case it is just too slow and OC opens regular menu without it. Otherwise it might be that their extension is not 64bit

[Mark Spencer]

Thanks for replying. Shift RC doesn't show the app in context menu. This is from file shredder dll that handles the context menu, and according to Google AI, the dll is 64-bit . What are your thoughts?

dll opened with notepad:

MZP   ÿÿ  ¸       @                                    º ´ Í!¸ LÍ! This program must be run under Win32
$7                                                                                                                                        PE  d†  ò wO        ð "  V  °      €e      @                 2                                                 + ¤    0+ ^O   Ð.  @   - ­           + Pt

from google ai:

Based on the header snippet you provided, this DLL is 64-bit (x64).

Here is the breakdown of how to tell from that specific block of text:

1. The Machine Type Field

Directly after the PE signature (which marks the start of the Portable Executable header), there are two bytes that identify the architecture.

• In your text, you see: PE d†

• In hex, d corresponds to 0x64 and † (in common Windows character encoding) corresponds to 0x86.

• Because Windows uses "little-endian" byte ordering, this reads as 0x8664.

• The value 0x8664 is the industry standard constant for AMD64 (64-bit).

2. The Legacy "Win32" Message

You might see the text This program must be run under Win32 and assume it's 32-bit. However, this is just part of the DOS Stub—a tiny piece of legacy code that runs only if you try to execute the file in MS-DOS.

• Almost all Windows executables (both 32-bit and 64-bit) include this exact same message for compatibility reasons. It doesn't actually reflect the architecture of the modern program inside.

3. The "MZP" Signature

The MZP at the very beginning (instead of just MZ) usually indicates this was compiled using Delphi or C++ Builder. These compilers have supported 64-bit output for many years, and the d† machine code confirms this specific file was built for a 64-bit environment.

---

Summary: | Signature | Hex Value | Architecture | | :--- | :--- | :--- | | d† | 0x8664 | 64-bit (x64) | | L | 0x014c | 32-bit (x86) |

[OneCommander Support]

OC just requests context menu items from Windows and if Windows doesn't include something, there is nothing I can do.

[Mark Spencer]

Thank you, I understand. Already tried modifiying the registry, with no result in OC. Weird how it works in Explorer without a problem.