Yahoo Groups archive

QTR-Quadtone RIP

Index last updated: 2026-04-28 23:12 UTC

Message

RE: [QuadtoneRIP] Printer Issues Screwy

2007-11-29 by E Neilsen

After rebooting the system and starting QTR first, it printed to the 2200
straight away. I suspect CS3 and it having a hold on the drivers. I have not
deleted and re installed all the printer after the CS3 major up date. That
could be it too. 

 

Eric

 

Eric Neilsen Photo

4101 Commerce Street, Suite 9

Dallas, TX 75226

214 827-8301

 

http://ericneilsenphotography.com

SKype ejprinter

 

  _____  

From: QuadtoneRIP@yahoogroups.com [mailto:QuadtoneRIP@yahoogroups.com] On
Behalf Of E Neilsen
Sent: Thursday, November 29, 2007 4:07 PM
To: QuadtoneRIP@yahoogroups.com
Subject: [QuadtoneRIP] Printer Issues Screwy

 

I have some new inks that I am working with a gifted 2200. I am having some
issues with my printers. I had PS CS3 open and was first using it to print a
profile target with lots of color patches just to test the flow of inks
(cleaning fluid). So I was finally ready to run some tests. All was going
just fine until I tried to print a color image file to my 4800 from within
PS CS3. I had been running through QTR to the 2200 making curves for the new
inks when I decided to get the color print queued up in PS. I went to access
the 4800 driver from within PS and the 2200 driver window opened. After
shutting down PS and re launching it, the 4800 showed up and worked fine.
But now when I go back to QTR it won't print to the 2200. 

QTR? PS? Just computers???? Since the latest Adobe up date to the printers
have you been seeing an increase in crashes, problems? 

Eric

Eric Neilsen Photo

4101 Commerce Street, Suite 9

Dallas, TX 75226

214 827-8301

http://ericneilsenp <http://ericneilsenphotography.com> hotography.com

SKype ejprinter

[Non-text portions of this message have been removed]

 



[Non-text portions of this message have been removed]

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.