You're not using one of those MS keyboards are you?
The one with that accursed F-lock key? The one which is off by default on boot?

If so, it's worth noting that f-lock needs to be off to use prtscn.

Apropose to the original poster.

One of my pet hates is the way users send screenshots. Guaranteed, almost every screenshot I've received in my current post has been:

* of the entire screen, not the offending window
* pasted into word and e-mailed as an attachment, rather than as an inline image in the e-mail
* so bloody small that you need to twat around with the zoom functions to make out the goddamn text of the error message

In addition, the fault description will be in the body of the e-mail while the screenshot will be in the word document, so as well as having to fire up a Word I'm having to juggle windows to work out what is going on.

I thought this was just a minor bit of user education, that our mail setup (outhouse/exchange) supports inline images and that the word would get out soon enough. But no, five years on and I'm still receiving ERROR MESSAGE.DOC by e-mail.

On the brighter side, I relieve my tension by venting in the support log (initially as an experiment to prove no-one ever reads it). I'll get some of the choicer ones and post them next week.
(_(_(_(_(_(_(_(_(_ =o.o=, Fri 25 Sep 2009, 14:46, Reply)