Ricoh mp7001sp printer function problem

[BlueCopy]

Customer recently networked their copier to function as a printer for two computer terminals running Windows 7. They want the copier to hold print until the user selects the print job on the copier printer control panel. At this time the copier immediately prints the documents from the computer even when the computer printer properties places the job as a hold print job. Is there a Ricoh printer mode or setting I am missing to make this happen?

I did not perform the networking as the company has their own IT department. Their IT department has been unhelpful in working with me to solve this issue.

[sharpmind]

Re: Ricoh mp7001sp printer function problem

Customer recently networked their copier to function as a printer for two computer terminals running Windows 7. They want the copier to hold print until the user selects the print job on the copier printer control panel. At this time the copier immediately prints the documents from the computer even when the computer printer properties places the job as a hold print job. Is there a Ricoh printer mode or setting I am missing to make this happen?

I did not perform the networking as the company has their own IT department. Their IT department has been unhelpful in working with me to solve this issue.

Have you assigned user code for HOLD PRINT? Using PCL printer driver, go to Printing Preferences-- Detailed Settings---Job Setup. Select HOLD PRINT and then assign user code on it.

[Choro1dal]

Re: Ricoh mp7001sp printer function problem

The User ID field is a has to be populated (and optionally a file name when using hold print.

Without a User ID the print job will be parsed as a normal print job. It is possible to customise the print driver so that hold print is the default and the User ID is automatically populated or a pop-up dialogue requesting a User ID to be entered.

[BlueCopy]

Re: Ricoh mp7001sp printer function problem

The User ID field is a has to be populated (and optionally a file name when using hold print.

Without a User ID the print job will be parsed as a normal print job. It is possible to customise the print driver so that hold print is the default and the User ID is automatically populated or a pop-up dialogue requesting a User ID to be entered.

That is exactly what I need to have done. Could you give me a step by step how to that I could email to their IT Tech? The Tech won't let me touch the computer, he installed the driver without me. He does have access as the Network administrator on the copier too.

[TonerMunkeh]

Re: Ricoh mp7001sp printer function problem

I'd just point them in the direction of the Printer Reference manual and say "read this". Don't go out of your way to help a customer who isn't willing to acknowledge any help you provide.

[Choro1dal]

Re: Ricoh mp7001sp printer function problem

Totally agree with TonerMunkey. If the IT guys are treating you like a third rate citizen bow to their superior knowledge, let them trawl the web, RTFM and then offer them the Ricoh Print Driver Editor.

[Llama God]

Re: Ricoh mp7001sp printer function problem

Personally I'd send it as a locked print job, but that's just me.

Also, being the kind and customer-focused chap that I am, I'd go out and show them how to do it. Then I'd ram my best screwdriver into the IT guy's ear.

[BlueCopy]

Re: Ricoh mp7001sp printer function problem

Lots of good advice! Thanks everyone! Well here was my solution, I started by emailing the department heads that I had a solution to the issue that wouldn't involve a big expense. That got their attention. I followed those emails with a call to the IT department, turns out the IT guy had some other guy install the driver. He didn't even know what driver was installed! I downloaded the correct driver for him and gave him a copy of the instruction manual. Everything is working fine now. One thing I know in all of this, nepotism is alive and well, as the IT guy is a nephew to the company CFO. If this wasn't a $20,000 account I would have walked away from the circus long ago...