2 Tuska, Why are in your configuration the 64bit Plugins separately listened?

[Native2904]

2 Tuska

(when my question is not right on this place, please move or delete this)

Why are in your configuration the 64bit Plugins separately listened; I mean, I install the *.wlx without "64"?
In your case, what is different between e.g. slister.wlx and slister.wlx64 (?) because my installation run on both TC 32bit | 64bit without focus ->*.wlx64.
https://imgur.com/M00AQBA

Moderator message from: white » 2025-06-06, 10:36 UTC

This thread was in response to this post:

I created a new thread created for this, because it was off-topic there.

2Native2904
If you wish to edit this post, remove this moderator block.

[tuska]

[OT]

2 Tuska

(when my question is not right on this place, please move or delete this)

Why are in your configuration the 64bit Plugins separately listened; I mean, I install the *.wlx without "64"?
In your case, what is deferent between e.g. slister.wlx and slister.wlx64 (?) because my installation run on both
TC 32bit | 64bit without focus ->*.wlx64.
https://imgur.com/M00AQBA

The difference is that I cannot display a file preview in Total Commander 32-bit with sLister 64-bit.
TC 32-bit is not allowed to access the file “slister.wlx64”.

I only installed the file “wlx64_sLister_1.1.2.zip” and not the file “sLister_1.1.2.zip”.
After extensively testing the sLister plugin and TCSumatraPDF plugin, I decided to go with TCSumatraPDF.

Apart from that, TCSumatraPDF would still run BEFORE the sLister plugin for the following reason:
Because I have defined *.pdf under “Define view method by file type...”
Picture: TC-Lister-plugins-WLX-Rules-German-English.png

This setting overrides the rule: “The plugins are processed from top to bottom.”
[/OT]

[petermad]

2tuska

The difference is that I cannot display a file preview in Total Commander 32-bit with sLister 64-bit.
TC 32-bit is not allowed to access the file “slister.wlx64”.

You do not have to state .wlx64 as the plugin type in the [ListerPlugins] section - TC x64 will automatically use the .wlx64 plugin file - also if the plugin type is stated as .wlx

So using:

Code: Select all

%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx64
%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx

is redundant - it is enough (and the correct way) to use:

Code: Select all

%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx

[tuska]

2tuska

The difference is that I cannot display a file preview in Total Commander 32-bit with sLister 64-bit.
TC 32-bit is not allowed to access the file “slister.wlx64”.

You do not have to state .wlx64 as the plugin type in the [ListerPlugins] section - TC x64 will automatically use the .wlx64 plugin file - also if the plugin type is stated as .wlx

So using:

Code: Select all

%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx64
%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx

is redundant - it is enough (and the correct way) to use:

Code: Select all

%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx

Hmm, I don't think I understand what you're trying to tell me.

The point is to show the differences between a 32-bit and a 64-bit installation,
as they were carried out (according to the images provided).

If I only INSTALL the file “wlx64_sLister_1.1.2.zip,” which only contains the file “slister.wlx64,”
then the following is automatically displayed in the Lister plugins (.WLX) - configuration:

Code: Select all

%COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx64    ext=“PDF” ...

No manual definition in wincmd.ini is required for this.

If I had wanted to install the file “wlx_sLister_1.1.2.zip” as well, I would have done so.
(I had previously used this installation (32-bit) for testing purposes only).

I would not carry out the procedure you described, as separate installations (32-bit, 64-bit) are possible.

EDIT:
I looked at my picture again and now I understand what you meant.
I would still perform two installations (32+64 bit) with the sLister plugin. For me, that's the most common way.

[tuska]

[OT]

In your case, what is different between e.g. slister.wlx and slister.wlx64 (?)
because my installation run on both TC 32bit | 64bit without focus ->*.wlx64.
https://imgur.com/M00AQBA

In case that wasn't clear above:
You have installed the 32-bit version of the sLister plugin.

TC x64 and x86 can display a preview with this version.
EDIT:
TC x86 can display a preview with this version.

[/OT]

[Native2904]

[OT]
In any way, I download a plugin and install it via double-click. In this way it is available on both installations of TC; only when I download an “only” 32bit or a 64bit version, then I have to note the build of TC (e.g.audio-burner) because the plugin only works on his architecture. But in general I can install a 32/64 e.g. ULister plugin from TC64, and then I can start beside TC32 with the plugin instantly loaded.
Or I'm theoretically wrong because practically it does work in this way?!
[/OT]

[tuska]

[OT]
2Native2904

Basically, it is true that double-clicking on a .zip, .7z or .rar file *in Total Commander* starts the plugin installation.

The “uLister” plugin is not an ideal example, even though the files ulister.wlx and ulister.wlx64 are present in a .rar file.
I have noted in the folder “redist32” (%COMMANDER_PATH%\Plugins\wlx\ulister\redist32\) that since OIT 8.5.7 - 18.10.2023,
only Windows x64 is supported and this folder is therefore obsolete (only serves as HISTORY)!
A test with TC 11.55RC5 (32-bit) confirmed this.

For example, in the plugin “TC SumatraPDF Plugin 1.18,” the text “Download (x32, x64)” contains the download link
to the file “wlx_TCSumatraPDF_1.18.7z” and the files “SumatraPDF.wlx” and “SumatraPDF.wlx64” are included.
This means that installation is performed for 32-bit and 64-bit systems.

However, the plugin in question, “sLister 1.1.2,” distinguishes between “Download (x32)” and “x64 version”.
In this case, two installations are theoretically possible/necessary.

As already mentioned, in TC 32 bit, only with sLister 64 bit, NO preview can be displayed.

Mandatory Integrity Control
... For example, a process is not able to write to an object (file system, registry, etc.)
     with a higher trust level than its own trust level or in other words,
     a process can only write to objects with the same trust level or objects with a lower trust level than its own trust level. ...
----
Mandatory Integrity Control - German: Obligatorische Integritätsprüfung
... Ein Prozess ist z.B. nicht in der Lage einen Schreibzugriff auf ein Objekt (Dateisystem, Registry usw.)
     mit einer höheren Vertrauensstufe als der eigenen Vertrauensstufe auszuführen oder anders formuliert:
     Ein Prozess kann nur Objekte derselben Vertrauensstufe oder Objekte mit niedrigerer Vertrauensstufe als der eigenen Vertrauensstufe beschreiben. ...

Own trust level:          TC 32 bit
Higher trust level: sLister 64 bit

Please create a separate topic for such inquiries in the future.
Thank you.

---

User Account Control | Benutzerkontensteuerung
[/OT]

[Native2904]

Please create a separate topic for such inquiries in the future.

OK, and thank you for your patience!
I have asked this question, because in the past I have done this in the same way which I have seen on your screenshots. But while reviewing my TC setup, I removed it again because there is no need - I download slister 32& 64 unpack it in the same Folder (c:\tcmd\plugins\wlx\slister) and open:

Code: Select all

TC\Configuration\plugins\wlx-config | "add"

And pick up the slister.wlx- so there is no need to pick up wlx64 - it is only important that the wlx64 is in the same Folder.
It sounds maybe a bit pedantic, but I don't like entries in my configuration that are unnecessary or duplicated.
Thx again.

[tuska]

With the configuration you have selected: %COMMANDER_PATH%\Plugins\wlx\slister\slister.wlx,
you can use both TC 64 Bit (x64) and/or TC 32 Bit (x86) with plugin sLister 32 Bit (x86).
EDIT:
you can use TC 32 Bit (x86) with plugin sLister 32 Bit (x86).

... a process can only write to objects with the same trust level or objects with a lower trust level than its own trust level. ...
... Ein Prozess kann nur Objekte derselben Vertrauensstufe oder Objekte mit niedrigerer Vertrauensstufe
    als der eigenen Vertrauensstufe beschreiben. ...

own trust level   : TC 32 Bit (x86) OR  TC 64 Bit (x64)         German: eigene Vertrauensstufe
same trust level : TC 32 Bit (x86) <=> sLister 32 Bit (x86)    German: dieselbe Vertrauensstufe
lower trust level: TC 64 Bit (x64)  <=> sLister 32 Bit (x86)    German: niedrigere Vertrauensstufe

[white]

Moderator message from: white » 2025-06-06, 10:36 UTC

Thread split to new topic. It was originally after this post:

[Native2904]

It seems to be a good question - because I have never read of this before.
Conversely, does this mean that all plugins only run as 32bit?
Why when I try to use an only 32bit Plugin [TTFViewer, listdoc] on TC64 it is not possible?
And for what is this config file by sLister:

Code: Select all

[plugininstall]
description=sLister is SumatraPDF wrapper plugin for TotalCommander.
type=wlx
file=slister.wlx64
defaultdir=slister

Classic me if I draw an unnecessary bow.

[white]

Conversely, does this mean that all plugins only run as 32bit?
Why when I try to use an only 32bit Plugin [TTFViewer, listdoc] on TC64 it is not possible?

No, petermad already pointed out this:

You do not have to state .wlx64 as the plugin type in the [ListerPlugins] section - TC x64 will automatically use the .wlx64 plugin file - also if the plugin type is stated as .wlx

So 64-bit TC will automatically look for .wlx64 plugin file when the user specified a .wlx file.

It is not possible to run a 32-bit plugin using 64-bit TC. Plugins are .dll files (dynamic-link library) and are basically an external part of the program which can be shared and loaded when necessary. A program is either running in a 64-bit environment or a 32-bit environment. You cannot have part of a program running as a 64-bit program and other parts running as 32-bit program.

[tuska]

Conversely, does this mean that all plugins only run as 32bit?

No, of course not.
Thanks to White for the detailed description!

Why when I try to use an only 32bit Plugin [TTFViewer, listdoc] on TC64 it is not possible?

I can confirm this for the “TTFViewer” plugin.
I was unable to set up the plugin, which was last updated on April 7, 2005, for TC 64-bit.
However, it works with TC 32-bit.

Since it is exclusively a 32-bit plugin, it must be installed via TC 32-bit,
otherwise you will receive an error message from Total Commander.

TTFviewer 0.1.2.4
This plugin is missing the file “pluginst.inf” which specifies the installation location.
Example: defaultdir=Plugins\wlx\TTFviewer

This means that the plugin cannot be installed by double-clicking on the file “wlx_ttfviewer_0.1.2.4.rar” in Total Commander.
I therefore extracted this file with TC 32 Bit to the directory “%COMMANDER_PATH%\Plugins\wlx\TTFviewer\”.
For me, this is: C:\totalcmd\Plugins\wlx\TTFviewer\.

Menu "Configuration" > Options... > Plugins > Lister plugins (.WLX): Configure > click on "Add"-button >
click on file "TTFviewer.wlx" > OK > OK.

Search for *.ttf files, e.g. in C:\Windows\fonts
Example in TC 32 Bit: Lister (ttfviewer) - [C:\Windows\Fonts\24517.ttf]

If TC x64 should be used, then the plugin “AKFont” can be considered.
[Even the plugin “IrfanView” displays a preview for .ttf files].

The plugin “ListDoc 1.2 (32-bit only)” - created on November 12, 2003 - may behave similarly (untested).

"Views MS Words texts in Total Commander lister very fast without formatting.
 No need of Microsoft Word to be installed or any additional libraries."

This plugin is deprecated.

The plugin “uLister” can display previews for Word documents and other formats:
OutsideIn_8.5.7_Supported_File_Formats (October 2024).pdf)

PS:
Next time, you could make my job easier by posting the web links to the plugins you mentioned here.

[tuska]

And for what is this config file by sLister:

Code: Select all

[plugininstall]
description=sLister is SumatraPDF wrapper plugin for TotalCommander.
type=wlx
file=slister.wlx64
defaultdir=slister

This is the “pluginst.inf” file that is used for the plugin installation.
Among other things, the installation directory is also displayed here.

Only if this file is present you can start the installation of this/a plugin
by double-clicking on the “wlx64_sLister_1.1.2.zip” file in Total Commander.

Example:
%COMMANDER_PATH%\Plugins\wlx\sLister\Downloads\wlx64_sLister_1.1.2.zip\pluginst.inf

[tuska]

Thanks to white for this contribution!

Why when I try to use an only 32bit Plugin [TTFViewer, listdoc] on TC64 it is not possible?

It is not possible to run a 32-bit plugin using 64-bit TC.
Plugins are .dll files (dynamic-link library) and are basically an external part of the program
which can be shared and loaded when necessary.
A program is either running in a 64-bit environment or a 32-bit environment.
You cannot have part of a program running as a 64-bit program and other parts running as 32-bit program.

Based on this statement, I ran another test as follows:
Total Commander (x64) 11.55RC5 <-> Plugin “sLister - only 32 bit”
and unfortunately discovered that I forgot to remove the file:
“C:\totalcmd\Plugins\wlx\sLister\slister.wlx64” during my previous test.

For this reason, I came to the incorrect conclusion that it would be possible to preview .PDF files
using TC x64 and sLister x86. This is NOT the case!

I have edited my above posts accordingly:
https://www.ghisler.ch/board/viewtopic.php?p=472641#p472641
https://www.ghisler.ch/board/viewtopic.php?p=472668#p472668

I am very sorry for my mistake and the incorrect statement.