Messages

1

Support and Feedback / Re: Splash Screen at startup..

« on: Today at 00:13:51 »

Hi Charles,

I use the portable version in my WinPE images, and I just tested MultiCommander v15.4 and saw behavior unchanged from previous versions. I think you and I may have seen the same old post showing how to suppress the splash screen, but in your recent transition you just got the directory wrong. The full file path you should use is...
"C:\Tools\MultiCommander\SessionConfig\Misc\MultiCommander.ini"

With a fresh portable version, you'll have to create that new "Misc" folder and its "MultiCommander.ini" file. I'm not sure of the significance of the "wp" entry, but here are the full contents of that file from my WinPE image:

Code: [Select]

[Root]
wp=LAAAAAIAAAADAAAA/////////////////////4IAAACCAAAA4gMAANcCAAA=
HideSplash=1


2

Support and Feedback / Re: Latest version of Multicommander detected as a virus

« on: Yesterday at 23:00:17 »

I had the same issue with Windows Defender, and a deeper dive reveals that the only executable flagged was the MultiCommander updater. Two shortcuts pointing to that file were also flagged. The main program passed just fine...

3

Support and Feedback / Re: Missing "New Text Document" Context Menu Item in MultiCommander on Windows 11

« on: April 13, 2025, 19:33:51 »

Thx, will check asap.

No double item in default Windows File Explorer?

No double here, but it's possible you might end up with repetition if you've already fixed this issue another way.

4

Support and Feedback / Missing "New Text Document" Context Menu Item in MultiCommander on Windows 11

« on: April 13, 2025, 11:59:43 »

Hi all! One of the first things I noticed when running MultiCommander on Windows 11 (v23H2) is the absence of "Text Document" on the cascading "New" line of the right-click context menu. After more tinkering than I'd like to admit, I arrived at 3 small registry entries that solve the problem with no apparent ill effects on the proper functioning of other file managers that already include this standard Windows shell feature. These entries are specifically for Windows 11, since prior editions use a "txtfile" registry key instead of the "txtfilelegacy" key introduced in Windows 11. So here's what I came up with:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.txt\ShellNew]
"NullFile"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\txtfilelegacy]
@="Text Document"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\txtfilelegacy\DefaultIcon]
@="%SystemRoot%\\system32\\imageres.dll,-102"


Context menu before registry additions:




Context menu after registry additions: