... but I'm not the end-user - and they are all cretinous morons.

7 years ago I was fitting out a building for 500 people over 3 floors. The design was such that no-one was more than 10 metres from a printer - 4 printers per floor. Printers had secure printing by default. Cartoon picture training provided etc.

Users moaned about having to "walk miles" and remember a "huge code" (4 digits) endlessly. IT dept stood firm, no more printers so they went and got their own insecure expensive-per-page local printers and bitched about the centrally provided printing ad infinitum. Then started whining about the local printers dying because they bought printers with low duty cycles rather than the 30ppm beasts we fitted.

How about eliminating some of the security risks inherent - .303 between the eyes of the users incapable of using the technology.

So, the EU has finally discovered dumpster diving? They'll be worrying about this interwebnet thing next.

Remember to remind any Irish friends to vote against the Lisbon treaty.

My last office had MFDs hooked up to the network. You print, then go to whatever printer you feel like, swipe your security card, and then it prints.

More secure and more green than the old "print to printer x" set up. But the managers whined (the geeks were perfectly happy, all they ever printed was their CVs anyway), they got their static printer names back, and by the time I left, they were back up to around 90% of prints never being picked up, and leaving confidential papers in public recycling bins.

I'm sure there's a phb joke somewhere - why don't we have a Dilbert icon?

99.9 reccuring % of printed documents are so boring as to represent a health hazzard.

When was the last time you saw anything remotly interesting sitting on the office printer?

The EU really needs to apply some basic quality control over the drivel thier overpaid drones produce.

More importantly the UK civil sevice really, really desperately, needs to learn how to ignore this drivel just like all the other EU members do. Honestly they never actually expect anyone to pay any attention to this rubbish, they are only churning out documents to meet some internal words per year target and are too busy filling in expense claims to enforce anything.

my last job in a large banks hq - well there was no such thing as thing as secure printing, it was basicly in the wing i worked in - three networked hp printers just churning off printing most of the day. The amount of customer data that i saw, was unbelievable - espcially when there were secure disposal bins next to the printers!!!!!!

Some printers and basically all MFDs have large hard disks (several GB+) that allow jobs to be stored and reprinted if required. This technology was originally put in for printing of large graphic and design files (normally from Apple Macs) where the spool time could be around 1 hour due to the amount of large high resolution colour images used. It allowed the graphic designer to proof a job and then re-print it directly from the hard disk without having to go through the lengthly spool process again (and you also made sure that the final prints were the same as the proof as it was the same file). The first "copiers" to also be printers were colour machines where the quality was needed.

This technology has also come though to the black and white devices that you will find in the office. At a previous company, we used share a printer with the IT director who was always really secretive and never shared any info with the team. Every time we saw him walk up to the printer, we would re-print his job as soon as he walked away....

Happy printing!

Nothing new... at a former employer me and a co-worker made it a hobby to google for certain terms in printer status pages, figuring out their IP address from the hits, telnetting into them and mucking with settings.

AFAIK there's still a printer over at MIT that speaks french.

> "As the spread of the Code Red worm demonstrated, modern networked printers can be affected by malware."

Uh, no it didn't. Well, anything with a webserver - or indeed anything at all listening on port 80 - will have received a few requests, but they won't have *done* anything to it; Code Red was entirely specific to IIS.

I think you may have been misremembering: Code Red exploited a buffer overflow in the IIS web printing facility. Not in the printer itself.

Do remember to check facts. You're supposed to be doing journalism.