Multi Commander > Beta Releases
[3.9.9] TabColors
Mathias (Author):
AV Sandboxing. hmm maybe.. never used anything like that.
If you name the tab in the Tab Properties dialog.. is the name also removed after restart of MC. ?
Ulfhednar:
(Now on b1598) I cannot make the tabs retain any settings text or colour etc past a restart.
As regards the AV - I tried shutting down sandboxing - no effect.
Also if an item is whitelisted/excluded the REG shouldn't be virtualized for that app anyway.
Other settings are OK - do core settings etc get entered to the REG in the same way? If yes, then, logically, the AV isn't blocking the tabs REG entries...assuming it is logical!
MC is always run in Admin mode so should have elevated rights.
Mathias (Author):
--- Quote from: Ulfhednar on December 19, 2013, 15:17:25 ---(Now on b1598) I cannot make the tabs retain any settings text or colour etc past a restart.
--- End quote ---
Strange. There are no changes done with that.
--- Quote from: Ulfhednar on December 19, 2013, 15:17:25 ---As regards the AV - I tried shutting down sandboxing - no effect.
Also if an item is whitelisted/excluded the REG shouldn't be virtualized for that app anyway.
Other settings are OK - do core settings etc get entered to the REG in the same way? If yes, then, logically, the AV isn't blocking the tabs REG entries...assuming it is logical!
--- End quote ---
Normal settings are stored in .xml files under account or in config folder.. Only "Session" settings is stored in the registry.
Ulfhednar:
Hmm so I need to double check if MC can (permanently) write to the REG somehow...
Ulfhednar:
Using MC regedit functions only -
REG:\HKEY_CURRENT_USER\Software\MultiCommander\
I can add 0x000000 value keys that survive a restart - tried REG_SZ, DWORD & QWORD
If I manually add any key to the
REG:\HKEY_CURRENT_USER\Software\MultiCommander\SessionHistory\a4c2985d9c7e4035a3221cfd600171d0\AutoLoad\ (tab #)
(tab REG keys folders) they disappear on a restart.
I assume this means that MC can write to the REG but that for some reason ...\autoload is refusing to retain the entry.
I suspect this would rule out AV activity as any REG activity should be flagged/restricted. AV logs no events whilst I am making these entries. It shouldn't be tree-depth dependent.
What else can I do to watch/test these events?
Could it be related to the tabbed_startup.INI that I'm using?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version