Skip to main content

misc: power savings problem with snagit 12

I have been a fan of snagit for very long time now. when I saw snagit 12 was released, I had to get my hands on it! as a mvp, one of the many benefits you get is nfr (not for resale) licenses for a lot of different software by a lot of vendors.

I won’t pretend there was some immediate correlation I drew to the problem I started having after installing snagit. it wasn’t something immediate or evident. my monitors will go into low power mode after 10 minutes of inactivity. I noticed after coming back to my desk several times that it wasn’t happening anymore.

I checked all my power settings to make sure nothing changed. everything looked fine. I recalled at some point that powercfg was a utility I had seen and played with some while back that could be useful in narrowing down where the issue might be.

 

LOOKING FOR THE CULPRIT

the first thing I did (other than figuring out how to use the tool) was run an energy report.

powercfg /energy /output "energy.html"

 

without the /duration switch, the default collection period is 60 seconds. this seemed more than plenty to catch what I needed to see. looking through my report (energy.html) I found these lines:

System Availability Requests:System Required Request
The program has made a request to prevent the system from automatically entering sleep.
Requesting Process \Device\HarddiskVolume3\Program Files (x86)\TechSmith\Snagit 12\Snagit32.exe
 
System Availability Requests:Display Required Request
The program has made a request to prevent the display from automatically entering a low-power mode.
Requesting Process \Device\HarddiskVolume3\Program Files (x86)\TechSmith\Snagit 12\Snagit32.exe

 

I was able to verify what was displayed here by looking at the current requests:

powercfg /requests

 

as you can see, the snagit32.exe process is clearly registered as a process in two places.

DISPLAY:
[PROCESS] \Device\HarddiskVolume3\Program Files (x86)\TechSmith\Snagit 12\Snagit32.exe
 
SYSTEM:
[PROCESS] \Device\HarddiskVolume3\Program Files (x86)\TechSmith\Snagit 12\Snagit32.exe
...

 

I ran a very quick test to make sure I could reproduce the effect (as I had intended to open a bug.) sure enough, when I closed the snagit program and ran powercfg /requests, it no longer appeared. when I turn on snagit, it still doesn’t register anything. it happens only after you initiate a screen capture.

it would appear proper that it should request not to go into a low power mode while the capture is occurring. I think where it’s failing is removing the request after it completes the capture. bug filed.

 

USING OVERRIDES

powercfg has another useful switch: requestsoverride. it’s not one of the more friendlier switches since it doesn’t provide any positive feedback if you do something right. (it ain’t your mama.) I like to have snagit running all the time. you never know when I need to capture a picture of a cat and create a quick meme. it happens.

image

since, in my scenario, the snagit32.exe process is registered in two places (display and system,) I ran the requestsoverride switch like this:

powercfg /requestsoverride process snagit32.exe display system

 

and when I hit enter, nothing. validation was only found running the switch with no parameters:

[SERVICE]
 
[PROCESS]
snagit32.exe DISPLAY SYSTEM
 
[DRIVER]

now my monitors switch into low power mode just fine with snagit running. hurray for cats!

 

CLEARING OVERRIDES

I’m sure there must be a hidden switch to do this in powercfg, but I wasn’t able to find it. I took a guess that the overrides were written to the registry somewhere and thus fired up procmon. tracing powercfg.exe to find it was cake.

image

 

jumping over to this section in the registry confirmed that this is where the overrides are:

image

so… if you need to clear them, just delete the values of interest.

 

FOLLOW UP WITH TECHSMITH

techsmith is a great company to work with. I used their support forum to file a bug indicating that I could easily repro it. the same day, techsmith responded with their acknowledgment. :]

Hi Marcus,

This is a bug we have logged and are hoping to get this fixed for an upcoming release we're working on. Im really sorry for the trouble.

Please let me know if there is anything else I can do to help.

Kind Regards,
Mike
Senior Support Specialist

Labels:

Comments

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »