Novell Cool Solutions

Automatic Print Screen Trick


March 1, 2007 10:28 am





By Bryan Keadle

We’ve incorporated a free PrintScreen utility into our Standard Load so as to enhance Print Screen functionality; PrintKey 2000.

One easily overlooked feature of PrintKey2000 is the “Auto Save ( Timer )” feature. I just had an opportunity to use this feature (again), and thought I’d share with you this trick/tip:

I started a process that was taking longer than I had expected to complete. I didn’t want to wait around for it to finish (it was getting late), but I did need/want to know how long the process would take.

So, I configured PrintKey2000 to take a print screen every 5 minutes, and enabled the “Auto Save ( Timer )” feature:

When I got in this morning, I had 181 print screen images in my temp directory. Now, by viewing the TEMP directory as thumbnails, I was easily able to locate where the screen changed, indicating the process having completed (between images # 17 and 18):

And, by viewing the first image, looking in the System Tray’s clock to get the start time, then looking at the image showing the screen change indicating the stop time, I’m able to determine the elapsed time of the process…within 5 minutes:

BEFORE – 6:11PM:

AFTER – 7:36PM:

Almost 1 1/2 hours! Glad I didn’t stick around waiting for it to finish!

Thanks to the author, Alfred Bolliger, for providing the free version of his great utility available for download with this article. Please visit to consider the Pro version for additional features.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.