Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: Anyone using large format Canon or HP printers?

2007-12-24 by pjb74nz

Strange your having major problems. Most issues can be related to the 
user not knowing how to operate the printers. The Large format 
printer are quite different from normal desktop printers. 
You don't really explain what problems your having or is it just you 
wanting things different than what Epson offers.

I sell all 3 brands and Epson is by far the best and support is 
excellent. Can say that about the others yet. Yes the PK/MK issue is 
there and ink is expensive. The 4000 is quite old now so I'll assume 
you are buying secondhand and maybe you are ending up with some elses 
headache. 

peter


--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Louis Dina" 
<lou@...> wrote:
>
> I've finally given up on my Epson 4000.  Mine (my 3rd actually) is 
> totally unreliable.  (Thanks anyway, but please, no suggestions on 
> this thread on making it work....I have tried it ALL, over and over 
> again).    
> 
> So, I am in the market for a new 17" or probably a 24" pigment 
based 
> printer.  I want a printer with both MK and PK permanently 
installed, 
> since I will print on glossy and matte papers, both color and B&W.
> 
> I'm interested in feedback from any large format Canon or HP 
owners, 
> whether the feedback is good or bad.  I am looking specifically at 
> the 24" HP Z3100 and the 24" Canon iPF 6100, but I am still 
> interested in comments if you have a 17" carriage or wider than 
24".  
> I am specifically interested in print quality, ink usage, clogging 
or 
> alignment problems, OEM support, B&W output with the standard 
driver, 
> toning, etc.  
> 
> Oh, BTW, is there a good online forum for either the HP Z3100 or 
the 
> Canon iPF 6100?
> 
> Thanks for any comments, and Merry Christmas to all.  
> 
> Lou
>

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.