Using loaddll in scheduler jobs #302
Replies: 1 comment
-
In fact, glass8 also uses an aerohost.exe background process. DWMBlurGlass does this for more than just checking for crashes and reloading it, it also has multi-dwm instance support for multi-user (not fully completed) and RDP, and monitors each dwm process. In addition, the background process of DWMBlurGlass takes up less than 5MB of memory and less than 0.5% of cpu, which does not cause any performance impact. At the same time, due to dwm's permission limitations, it is not possible to read some configurations of the user (HKCU), so the DWMBlurGlass.exe process is resident, and is used by DWMBlurGlassExt to query settings from the main process, and to return Ext. Since DWMBlurGlass now features automatic injection, there is no reason for this option( |
Beta Was this translation helpful? Give feedback.
-
In version 2.2 loaddll was removed. The EXE process is launched instead
I suggest keeping loaddll. You can monitor application crashes using Dwminit events. Is this possible? Example of a task with tracking:
Aeroglass check.zip
Beta Was this translation helpful? Give feedback.
All reactions