That subsequently posted link seemed to have identified the API call, and provided some PowerShell-hosted code to call it...
-sc -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ben Scott Sent: Wednesday, July 9, 2014 10:14 AM To: [email protected] Subject: Re: [NTSysADM] Mouse trails On Wed, Jul 9, 2014 at 5:43 AM, James Rankin <[email protected]> wrote: > You may have to do something like restart the shell to get it to kick in. It's not the shell... I can exit Explorer, and kill the remaining EXPLORER.EXE, and I can still toggle the trails on and off using "CONTROL MAIN.CPL" (which just starts a RUNDLL32.EXE process). (Win 7) I'm guessing it's done in the GDI or USER layers (or whatever might have replaced/supplemented them under NT 6). There's presumably an API call or something that occurs to tell whatever-it-is to change behavior (or re-read the registry). ProcMon doesn't seem to show anything happening in a quick test; might be my exclude filters are too strict. -- Ben
