Yahoo Groups archive

QTR-Quadtone RIP

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

Message

Re: [QuadtoneRIP] QTR "error"

2013-10-10 by Roy Harrington

Yes. Just double click the script. It pops up a bunch of text. Copy & paste the whole thing back to me.
Roy

On Wednesday, October 9, 2013, wrote:


I'm afraid it only says "error"..

I see the diagnostic script here in the qtr folder, I'll try to lead him through that tomorrow and hopefully have something more helpful to pass on. I assume you just run it and a log comes up I can paste in here?

Thanks Roy



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

Hi Tyler

Can you find out more about what the error is? Running the DiagnosticScript right after getting the error should give more info.

I wonder if the Epson driver is somehow hogging the USB port.

Roy

On Wednesday, October 9, 2013, wrote:


well I'm going to keep hammering away at this because it's become an ongoing problem. So he reinstalled QTR and made a good print, worked. Then made a few color prints with the OEM driver, then went back to B&W and tried to make another print with QTR. This is within minutes of the reinstall, the good print, etc.

This time, same "error" again..

He's about had it.

No ideas here?

Thanks,

Tyler



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

Not sure it will work. But I remember having similar problems that were solved by reinstallation.
No idea why.

From: <tyler@...>
Reply-To: <QuadtoneRIP@yahoogroups.com>
Date: Monday, October 7, 2013 4:34 PM
To: <QuadtoneRIP@yahoogroups.com>
Subject: RE: Re: [QuadtoneRIP] QTR "error"

Hi David, I'll pass it on. Any idea why this happens, requiring this solution?

David Kachel

___________________

Artist-Photographer
Fine B&W Photographs

david@...

Gallery:
director@...

PO Box 1893
Alpine, TX 79831
(432) 386-5787




--
Sent from Gmail Mobile




--
Sent from Gmail Mobile

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.