QTR-Quadtone RIP

Hi everyone - this is my first post here. I recently decided to try
out the QTR inks for printing BW prints on my Epson PHOTO 890. I have
had more than a few problems to date..  prints too light and such, but
my major problem which I cannot seem to fix is 'staircasing' or how
would you say it.. 'wiggly lines' all over the place. Now, I have
recalibrated my print heads I don't know how many times to no avail..
any suggestions?

Thanks - Bernard

--- In QuadtoneRIP@yahoogroups.com, "brooksveriwide"
<brooksveriwide@...> wrote:

>BTW - I am using a PC with Windows 2000 professinal...what else ??


> Thanks - Bernard
>

I tried posting this earlier but I'm not sure it went through. My 
apologies if it did. Here's my situation; I'm printing with QTR to both 
a 4000 and a 7600 from 10.3.9.
Everything has been great until a couple of days ago. Now no matter
what I do, I get a Command Error when attempting to print to the 7600
(the 4000 is fine). The Epson driver prints fine, it's only QTR. I've
tried different files, reinstalling QTR, unplugging and replugging in
the printer, changing my brand of breakfast cereal. What am I doing 
wrong?
Any help would be appreciated.
Thanks,
-Alan

Hi Alan,

Where are you getting this "Command Error"?  I.e. where is the message
displayed to you?   It may be helpful if you run DiagnosticScript after
the error.  This will put up a big page of data, just cut & paste it 
and email
me the output.

Roy
quadtone at harrington dot com


On Monday, May 8, 2006, at 11:31  AM, Alan Sanders wrote:

> I tried posting this earlier but I'm not sure it went through. My
> apologies if it did. Here's my situation; I'm printing with QTR to both
> a 4000 and a 7600 from 10.3.9.
> Everything has been great until a couple of days ago. Now no matter
> what I do, I get a Command Error when attempting to print to the 7600
> (the 4000 is fine). The Epson driver prints fine, it's only QTR. I've
> tried different files, reinstalling QTR, unplugging and replugging in
> the printer, changing my brand of breakfast cereal. What am I doing
> wrong?
> Any help would be appreciated.
> Thanks,
> -Alan
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
-
Roy Harrington
roy@...
Black & White Photo Gallery
http://www.harrington.com

Sorry I didn't mention that, it's on the printer display. Plus, all the 
lights on the printer light up. In the meantime, Print Setup Utility 
thinks it's printing just fine. I'll try another print in just a bit, 
run the DiagnosticScript and send you what I get.
Thanks, Roy.
-Alan

On May 8, 2006, at 3:15 PM, Roy Harrington wrote:

> Hi Alan,
>
> Where are you getting this "Command Error"?  I.e. where is the message
> displayed to you?   It may be helpful if you run DiagnosticScript after
> the error.  This will put up a big page of data, just cut & paste it
> and email
> me the output.
>
> Roy
> quadtone at harrington dot com
>
>
> On Monday, May 8, 2006, at 11:31  AM, Alan Sanders wrote:
>
>> I tried posting this earlier but I'm not sure it went through. My
>> apologies if it did. Here's my situation; I'm printing with QTR to 
>> both
>> a 4000 and a 7600 from 10.3.9.
>> Everything has been great until a couple of days ago. Now no matter
>> what I do, I get a Command Error when attempting to print to the 7600
>> (the 4000 is fine). The Epson driver prints fine, it's only QTR. I've
>> tried different files, reinstalling QTR, unplugging and replugging in
>> the printer, changing my brand of breakfast cereal. What am I doing
>> wrong?
>> Any help would be appreciated.
>> Thanks,
>> -Alan
>>
>>
>>
>>
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
> -
> Roy Harrington
> roy@...
> Black & White Photo Gallery
> http://www.harrington.com
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

--- In QuadtoneRIP@yahoogroups.com, "brooksveriwide"
<brooksveriwide@...> wrote:
>
> --- In QuadtoneRIP@yahoogroups.com, "brooksveriwide"
> <brooksveriwide@> wrote:
> >BTW - I am using a PC with Windows 2000 professinal...what else ??
> 
> 
> > Thanks - Bernard

'fixed' the prob myself.. surprised no one else had the answer - it
was simply a matter of printing in 'better' rather than 'faster'
mode...  anyone else seen this ?
> >
>