I get an interesting email from my boss.
"Expect to help the CTO with a print problem"

Hmm.

OK.

We have some inkjet printers. BIG. FAST.
Dual heads. Driven by a Win9x box.

They kick out 30,000 pieces an hour each. We
have 8 of them. We print a bit, ehh?

Symptom:

Occasionally some data would be missing.

For example, the 1st line of the 2nd print head for each piece
would have the words abbreviated. But the data was GOOD!
Send the file through again and it printed fine.

But files sent to the printer BEFORE that file might have had some
high or low characters that confused the printer.

The operations guy said they can't be sure the exact order of
the files before that particular job.

So I write a simple Perl script that goes through the 3,000
files on the disk, finds bad characters in 70 of them, but no
way to determine if they cause the problem. And I don't have
the luxury of printing a 1,000,000 pieces of mail to test.

For now on, they need to run this program right before the
print job, on the Windows box. And they MUST be able to
pointy clicky their way through it.

I was in a meeting with the IT director (hardware reponsibility),
MIS director (my boss), and the CTO. I ask my boss if he's
manufactured this problem to make me write some pointy clicky
Perl in my newfound WxWindows.

The CTO hears that I now write for windows, and he starts thinking.
What he's really like is a Windows Explorer extension to right
click on a file name and do stuff with it.

I told I'd be lucky to be able to do that type of stuff in
6 months.

Any direction?

Where do I find into on binding code to be launched via right
clicking on the Explorer?