Yahoo Groups archive

Digital BW, The Print

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

Message

Designjet Vs 2400/4800 - Black is Beautiful

2005-07-01 by Djon

Epson's biz is machinery, pigment, and paper. They'd be nuts to worry
about Black Only enthusiasts...they don't need us. Epson's pig costs
surely aren't a concern to 90% of the users, which is why they're
overjoyed to introduce systems with extra carts. Look at all the SUVs
we drive :-)

HP only makes $$ on printers and paper, the machine's tight with ink.
On the other hand, there's no paper versatility (I think), so that's
their $$ game. And the black may beat everybody else...
And the machine's cheaper, not that we care... :-)

That's the comparison I'd like to see: 4800 Vs Designjet 130 in B&W.





--- In DigitalBlackandWhiteThePrint@yahoogroups.com, Steve Kale
<stevekale@b...> wrote:
> Your "best bet" is to make yourself heard at Epson.  I have no doubt
that
> without substantial feedback black only will not be available on any
future
> Epson printer with more than one shade of K...
> 
> 
> > From: Djon <westsidemaurice@y...>
> > Reply-To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> > Date: Fri, 01 Jul 2005 01:24:13 -0000
> > To: <DigitalBlackandWhiteThePrint@yahoogroups.com>
> > Subject: [Digital BW] Re: 2200 says "no ink here" but there is - BO?
> > 
> > I routinely print B-O using 2200 and Epson driver with OEM
> > pigments...looks GREAT, readily better than silver paper from small
> > format negs. Sometimes QTR driver is more appropriate, but only if I'm
> > trying to emulate large-format images using 35mm...which isn't my main
> > thing.  
> > 
> > The absence of B-O on the 2400/4800 is alone reason to hesitate
> > purchase. 2200 and 4000 are built for the ages so maybe the best bet
> > is to see what follows 2400/4800...and surely HP will soon get it
> > together better than the Designjet 130.

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.