[TC 11.01rc1 32bit] CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} does not work

[AntonyD]

Moderator message from: petermad » 2023-08-24, 01:20 UTC

This topic is split from MENUITEM "&Fonts", 2124 doesn't work for me

Notice that the second part of the GUID link: {5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} is NOT the same as mentioned in the post Re: MENUITEM "&Fonts", 2124 doesn't work for me = {BD84B380-8CA2-1069-AB1D-08000948F534}

TC 11.01 RC1
works fine now. I mean as on Win10 so and on Win11 now I can "step in" the cmd "shell:Fonts".
And see the list of installed fonts. Both bitness of TC is ok.
BUT we have a biiiig difference between the results of the cmd
"CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}"
which means go into the Control Panel and inside the subitem "All tasks".
TC 32 bit shows only

Spoiler

Почта

TC 64 bit shows now:

Spoiler

Автозапуск\
Администрирование\
Брандмауэр Защитника Windows\
Восстановление\
Дисковые пространства\
Диспетчер учетных данных\
История файлов\
Подключения к удаленным рабочим столам и приложениям RemoteApp\
Программы и компоненты\
Программы по умолчанию\
Рабочие папки\
Распознавание речи\
Резервное копирование и восстановление (Windows 7)\
Система\
Устранение неполадок\
Устройства и принтеры\
Учетные записи пользователей\
Центр безопасности и обслуживания\
Центр синхронизации\
Центр специальных возможностей \
Центр управления сетями и общим доступом\
Шифрование диска BitLocker\
Шрифты\
Электропитание\
Java
Windows To Go
Графика и медиа Intel(R)
Дата и время
Диспетчер устройств
Звук
Инфракрасная связь
Клавиатура
Меню "Пуск"
Мышь
Панель задач и навигация
Параметры индексирования
Параметры Проводника
Почта (32 бита)
Региональные стандарты
Свойства браузера
Телефон и модем
Управление цветом
Учетные записи пользователей
Центр мобильности Windows

Also TC 64 bit supports the cmd:
"CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{BD84B380-8CA2-1069-AB1D-08000948F534}"
which will open the same \\Fonts\ virtual folder.
But TC 32 bit - does NOT support it! As petermad stated above in his post about it.
AND what is more interesting! TC 10.52 of both bitness - supports this cmd!
It seems that these virtual folders, which are assigned a certain GUID parameter, NOW (at the TC 11.xx build branch)
work only on behalf of the bitness of the application, which is equal to the bitness of the OS itself.

https://docs.rainmeter.net/tips/launching-windows-special-folders/
most of these GUIDs does not work for TC32 and does work for TC64...

[AntonyD]

2ghisler(Author)
It would also be very helpful and nice to know that you can explain the difference in the output of the command
"CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}"
As you saw in the spoilers above, the output results differ in a terrible way!
TС 32 bits produces 1 record, TС 64 bits produces 44 records!

[AntonyD]

2ghisler(Author)
That's really good news but pls don't forget about diffs from post above: viewtopic.php?p=439810#p439810

[AntonyD]

2ghisler(Author)
I don't get the conclusion: you think that this current behavior is intentional and could not be changed?
But if so - maybe we should popup some information dialog - which will explain - which commands with GUID
will be possible to call and which impossible, because we have a different bitness of launched TC and the
destination-virtual folder, represented by "this GUID"...

[ghisler(Author)]

I don't get the conclusion: you think that this current behavior is intentional and could not be changed?

No, why do you think that? The conclusion is that I have to put shell: in front of the path before calling ParseDisplayName if the call without it fails. You can put shell: in front of it yourself to see how it will look after the change.

[AntonyD]

2ghisler(Author)

You can put shell: in front of it yourself to see how it will look after the change.

Did so and did not get any better results ...

[ghisler(Author)]

2AntonyD
Did you use 3 colons? The shell: is in addition to ::{ so the command should look like this:
cd shell:::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{BD84B380-8CA2-1069-AB1D-08000948F534}
This works for me on Windows 7, 10 and 11 with TC 11.00 and TC 11.01 RC1, both 32-bit.

Please note that it does not work on Windows XP, there you need to use cm_OpenFonts instead.

[AntonyD]

2ghisler(Author)
why you talk about the Fonts\ virtual folder? I am taking in latest posts about
"CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}"
which means go into the Control Panel and inside the subitem "All tasks".
TC 32 bit shows only 1 element. And that's wrong!
TC 64 bit shows 44 elements. And that's right!
And adding "shell:" suffix - does not make all look good((( for TC 32bit.

Regarding Fonts\ folder we already all here confirmed that rc1 produced a correct,
full and fixed output for this "folder" after the calls to corresponding commands.

[Hacker]

AntonyD,
It's better to create a new thread for a different bug, so this confusion can be avoided.

Roman

[AntonyD]

OK, maybe any moderator - could be so kind and rip-off from this thread all these related posts and create the new topic?
Please....

Moderator message from: petermad » 2023-08-24, 01:25 UTC

This topic is split from MENUITEM "&Fonts", 2124 doesn't work for me

[ghisler(Author)]

CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}
does not work for me at all, neither on Windows 10 nor on Windows 11. It brings me to the same folder as
CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}
which is all control panel elements. However, it only works in 64-bit - the control panel doesn't seem to have any 32-bit elements any more on 64-bit Windows 10 or 11, so only third party control panel elements like Java will show up.

2AntonyD
On what Windows version does
CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}
work for you in 64-bit?

[AntonyD]

On what Windows version does
CD ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0}
work for you in 64-bit?

Win10 1809 + Win11 21H2

[petermad]

Here is what I see:

64Bit TC:
cd ::{21EC2020-3AEA-1069-A2DD-08002B30309D} = All elemensts in Control panel
cd ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} = All elemensts in Control panel
cd ::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} = No directory change at all
cd ::{26EE0668-A00A-44D7-9371-BEB064C98683} = Control panel - Categories only
cd ::{ED7BA470-8E54-465E-825C-99712043E01C} = All Tasks - AKA God mode

32Bit TC:
cd ::{21EC2020-3AEA-1069-A2DD-08002B30309D} = All elemensts in Control panel - ONLY third party programs (Java etc)
cd ::{21EC2020-3AEA-1069-A2DD-08002B30309D}\::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} = All elemensts in Control panel - ONLY third party programs (Java etc)
cd ::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} = No directory change at all
cd ::{26EE0668-A00A-44D7-9371-BEB064C98683} = Control panel - Categories only
cd ::{ED7BA470-8E54-465E-825C-99712043E01C} = All Tasks - but with EMPTY file panel.

And it is the same for TC 11.01rc1 and TC 10.52 under both Windows 7 and 10 22H2.

shell:::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} OR shell:ControlPanelFolder (without cd) does open Windows Control panel in All Elements mode.
cd shell:::{5399E694-6CE5-4D6C-8FCE-1D8870FDCBA0} has no effct from TC's command line
cd shell:ControlPanelFolder in TC's command line opens file panel with All elemensts in Control panel

[AntonyD]

https://www.elevenforum.com/t/list-of-windows-11-clsid-key-guid-shortcuts.1075/
Well, I should probably apologize for the persistence to figure it out here and "go puzzle" the OS developers - because they obviously weren't friends with their heads when they implemented these features with GUID objects. I have already found about 5 different manuals - where not even these two GUIDs that we use in this topic were associated with this control panel.

I'm rather confused now - is it POSSIBLE to actually implement this support in Total? If, according to the initial thoughts of the OS developers, these GUIDs should work when only commands are called from under the explorer command line. And it must open some an appropriate windows/dialogs. And we, as it were, impudently climb in the middle of this chain of logically connected actions and try to intercept the "output" of such chain, as it were. IMHO this is incorrect. Probably, out of all the variety of these GUIDs in Total, it is necessary to implement support for only a strictly limited number of such "chain commands", which definitely makes sense and can be "intercepted" and displayed in Total's file panels.

The above link seems to me to be the clearest and most accurate description of all such command/call chain GUIDs.

[ghisler(Author)]

I'm moving this thread to "will not be changed" because it doesn't lead anywhere. I'm getting the same results here on Windows 11 as petermad, so I suggest that you just pick the GUIDs which work for you and forget about the others which don't. There is nothing I can do when there are no 32-bit shell extensions available, only 64-bit.

Moderator message

Will not be changed