Yahoo Groups archive

Digital BW, The Print

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

Message

Re: dying 1280 printer

2006-11-07 by Bob Michaels

The cost of a replacement 1280 usually less than your investment in
inks and carts, and in turn that is less than your time invested in
developing workflows to make everything work well. I faced your
decision twice in recent years with a less than optimal 1280 but
everything else to make good prints. Once I bought another 1280 and
kept making good prints for another 18 months. I don't regret that
decision. I had more time when the most recent 1280 began to falter,
so I stepped up to a 2400. That was a good decision for me at that time. 

Just realize how small the printer purchase price is in relation to
the total investment. So pick your time carefully to step up to new
printer models. And when you do step up, don't stop short of the
latest proven model to save $200 on the hardware. BTW, I wouldn't
consider a 3800 a "proven model". 

Bob Michaels

 --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "mmrroott"
<mike.rott@...> wrote:
>
> Hi,
> 
> I have been using a 1280 with the UT2 inset. My printer has the 
> problem in that the LM head is not longer working after repeated 
> cleaning. I even injected the MIS cleaner through that nozzile but 
> it did not help. The printer was repaired less then a year ago with 
> a similar problem which turned out to be electrical. I don'tthink it 
> is worth sending out for repairs again. I can pick up a very lightly 
> used 2200 for a good price. What is the difference between the UT2 
> and UT7 inks? Can I still use my inks (I just bought some so have a 
> lot left). Is the 2200 a good printer to work with? will there ever 
> be spongless carts for it?  My other option is to wait for the 3800, 
> use it for awhile as is until there are 3rd party inks and carts for 
> it. Find it hard to justify the new price for a 2400.
> 
> Mike
>

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.