Yahoo Groups archive

QTR-Quadtone RIP

Index last updated: 2026-04-28 23:12 UTC

Message

Re: Epson 10000 not printing

2007-01-08 by Roy Harrington

Hi Mark,

I see you've had a couple questions about the 10000.
First, I've never had access to a 10000 so I not sure what 
idiosyncrasies it may have.
Also I haven't be able to run tests on the printer.

I don't think using the Epson UC inks will work as well as the 9600 
because it's a 6 ink
printer rather than 7 inks.   The light-black is key for the B&W 
printing on the 9600.

I suspect that connecting to both the USB port and the network port may 
be causing
the communication problem.   I think you should be able to use either 
connection
with QTR.   (Running DiagnosticScript may also have more clues if 
necessary.)

There has been interest in using the Cone K6 inks on the 10000 printer 
so that may be
the "supported" inkset in the future.

Roy

On Saturday, January 6, 2007, at 07:02  AM, Mark Savoia wrote:

> Roy,
> I posted this on the QTR RIP Yahoo group and it did not show up after 
> a few hours, not sure why. Anyway this is what I posted, can you help 
> me?
>
> I am at the beginning of trying to get QTR to see my Epson 10000. I 
> have it both connected via USB and network. If I run the Epson utility 
> from within Printer Setup Utility in OSX it sees it fine, both via USB 
> and network, and even provides status of ink remaining. But if in 
> Photoshop I set up everything correctly and ready to print, it appears 
> to rip it, but will not send the data to the printer. If I just print 
> to preview it looks fine and again if I hit the print button from 
> there I see the status bar saying it is printing and then within 
> seconds it clears and no data is sent to the printer. There must be 
> some simple thing I am overlooking.
>
> Thanks,
> Mark
>
>
-
Roy Harrington
roy@...m
Black & White Photo Gallery
http://www.harrington.com

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.