Yahoo Groups archive

Digital BW, The Print

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

Message

Re:7600/9600 problem(2200?) confirmed by TSS

2002-11-07 by jim hayes

Chris Bair at TSS photo confirms the problem too. It is a question of 
paper that just doesn't work well in the printers. Paper with the 
Epson name on it from Somerset. I still can't get a fix on what paper 
it is, apparently one of the Somerset offerings offered in 255gsm roll 
form.


Chris has a theory that the paper becomes saturated with ink and 
starts to buckle slightly. Since the paper is no longer flat, the head 
hits it, causing the grid pattern to print roughly every 1.5 inch in 
wavy , not quite striaght line grid pattern.


The solution is to either switch papers to something that works, or 
use a thicker version of the paper. Apparently just one or two papers 
cause problems...


Rather than spread innacurate rumors I suggest reading the original 
thread:

http://www.dpreview.com/forums/read.asp?forum=1000&message=3613378

and decide for yourself. 

Someone had mentioned that photorag was also affected but Chris does 
not mention this and Bryan apparently has no problem using it. I don't 
know what thicknesses Bryan is using and whether that would influence 
the problem as it does with the Somerset.

If someone has an 2200 and cares to run the test outlined in the 
thread, can you verify whether it occurs with 2200 as well? I suspect 
it would, as it is paper/ink, not printer specific.
Jim H.






--- In DigitalBlackandWhiteThePrint@y..., "bryanwhitney" 
<bryanwhitney@m...> wrote:
> I suspect that the original post is bogus.
> 
> Firstly, the post says that the person had the problem with 
> somersest velvet: and now Hanamuhle is dragged in.
> 
> All I can say is that I have been printing 36 x 48 on Photo Rag 
> and have no problems with squares.  I have problems with 
> triangles. 
> 
> Just kidding.
> 
> Bryan Whitney

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.