Yahoo Groups archive

Digital BW, The Print

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

Message

RE: [Digital BW] Re: Kirkland Paper Print Longevity?

2005-08-14 by Paul Roark

Scott,

 
> Which Kodak paper did you use: Premium or Professional?

It was the latest Kodak paper as of 3/04 that was said by Kodak to be a
"breakthrough."  They were marketing is under the name "Ultima Picture
Paper," "ColorLast" version.  The inks were the HP 7660 B&W inks.  They were
printed by a third party.  My interest was that Kodak was claiming something
like 100 years even without framing.  It turns out, of course, that Kodak
simply re-defined how much light a print would get in "100 years" of
display.  Nonetheless, it appears to be a good "swellable polymer" type of
paper.

> 
> By the way, I was using Epson inks in the R800, fwiw.

The Kodak paper I used was specifically for dyes.  My attempts to print
pigments on these swellable emulsions has resulted in prints that take a
very long time to dry.

Paul
www.PaulRoark.com 


> 
> 
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Paul Roark"
> <paul.roark@v...> wrote:
> > >
> > > HP Premium Plus Photo Paper should be the only paper to use with
> an
> > > HP photo printer if you expect longevity.
> > >
> >
> > In March 2004 I fade tested the HP B&W ink on HP, Ilford Classic
> Pearl, and
> > Kodak's latest paper at the time.  They were all close, with the HP
> paper
> > having a very slight edge in the midtones, and Kodak having a
> slightly
> > better dmax after the fade test.  (The Ilford 100% patch actually
> increased
> > in density, but it was significantly lower to start with.)  I
> generally
> > concluded the swellable papers on the market are close to the same
> and all
> > very good considering the inks are dyes.  (They are still not in
> the same
> > league with carbon, however.)
> >
> > Paul
> > www.PaulRoark.com
> 
> 
> 
> 
> 
> Please visit the Group Homepage to check the Files, and other resources as
> they are often being updated.
> 
> http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint
> 
> If you wish to receive no emails or just a daily digest, or you wish to
> unsubscribe, please edit your Membership preferences by visiting this same
> page.
> 
> Please follow these basic guidelines:
> - As threads develop, trim off excess portions of earlier messages to keep
> them short.
> - Good manners are required at all time. No personal attacks or flames.
> Hostile, aggressive or argumentative users may be removed from the
> membership without notice.
> - Keep your posts and threads related to the group topic of digital B&W
> printing. Users who persistently make off-topic posts may be removed from
> the membership.
> - By posting on this forum you agree to abide by the group rules and
> guidelines, and to abide by the actions and decisions of the group Owner
> and Moderators. See "Group Topic, Rules and Guidelines" in the Files
> section:
> http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint/files/
> 
> BY PARTICIPATING IN AND/OR POSTING MESSAGES TO THE DIGITAL BW, THE PRINT
> YAHOO! GROUP YOU EXPRESSLY UNDERSTAND AND AGREE THAT THE "OWNER" AND
> "MODERATORS" OF DIGITAL BW, THE PRINT YAHOO GROUP SHALL NOT BE LIABLE TO
> YOU FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR
> EXEMPLARY DAMAGES, INCLUDING BUT NOT LIMITED TO, DAMAGES FOR LOSS OF
> PROFITS, GOODWILL, USE, DATA OR OTHER INTANGIBLE LOSSES (EVEN IF THE
> "OWNER" AND "MODERATORS" OF DIGITAL BW, THE PRINT YAHOO GROUP HAVE BEEN
> ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), RESULTING FROM: (i) THE USE
> OR THE INABILITY TO USE THE DIGITAL BW, THE PRINT YAHOO GROUP; (ii)
> UNAUTHORIZED ACCESS TO OR ALTERATION OF YOUR TRANSMISSIONS OR DATA; (iii)
> STATEMENTS OR CONDUCT OF ANY THIRD PARTY ON THE DIGITAL BW, THE PRINT
> YAHOO GROUP; OR (iv) ANY OTHER MATTER RELATING TO THE DIGITAL BW, THE
> PRINT YAHOO GROUP.
> 
> Yahoo! Groups Links
> 
> 
> 
> 
>

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.