Confusion between "everything64.exe" and "everything.exe"

[ChrisGreaves]

My installation of three weeks ago provides me with an executable file Everything64.exe on my hard drive.
Works great!
Thus equipped I set off to try a few more useful examples from the forums, but then run in to examples such as this great one which of course will not work for me until I realize that I no longer have Everything.exe, but have instead Everything64.exe.

Right now this is not a major issue, and a couple of months ago I dabbled (injuriously!) with Instances

But might we think about some way to map the generic Everything.exe to whatever is installed locally?
I know, I know: now that I have a proper system (grin) I should go back and review Instances, and I will, I will!

In the meantime references within the forums to "Everything.exe" are going to trip up some beginners. (Like me, obviously!)

Back in the Good Old Days there was CED (Command Line Editor) and SetKey that created synonyms for all sorts of commands, mapping to Function keys; but a Windows version of that seems like overkill.

I'm just wondering if anyone has found a simple solution to resolving these different names?
Thanks, Chris

[horst.epp]

Sorry Chris, you see problems which are not real problems for a normal user.
It is a difference to run a 32 or 64 bit version of Everything and that is not only in Everything.
For example my Total Commander also has different names of its exe file, depending of its bitness.
A typical user only runs one of the versions and knows how the exe is named.

[therube]

(I inadvertently downloaded the x64 version the other day, & simply renamed it to Everything.exe .)