QTR-Quadtone RIP

I have just installed the QuadtoneRIP software on my Mac using the 10.4 system and an Epson Stylus Pro 4000 printer.  When trying to print, I'm getting the "crashed on Signal 5" situation.  I've done a message search here to see if anyone had also encountered the problem and whether a solution had been posted.  I saw dialogue about signal 10 a a couple of others who had the signal 5 problem, but didn't find any solutions.  Any help would be appreciated.  Here's the diagnostic script:

I [21/Apr/2009:09:01:29 -0600] Adding start banner page "none" to job 7.
I [21/Apr/2009:09:01:29 -0600] Job 7 queued on 'Quad4000-K7' by 'rodhanna'.
I [21/Apr/2009:09:01:29 -0600] Started filter /usr/libexec/cups/filter/cgpdftoraster (PID 202) for job 7.
I [21/Apr/2009:09:01:29 -0600] Started filter /Library/Printers/QTR/filter/quadtoneprint (PID 203) for job 7.
I [21/Apr/2009:09:01:29 -0600] Started backend /usr/libexec/cups/backend/usb (PID 204) for job 7.
N [21/Apr/2009:09:01:33 -0600] [Job 7] : QuadToneRIP: using curve K7-2880-EpEnhancedMatte
E [21/Apr/2009:09:01:36 -0600] PID 203 crashed on signal 5!
I [21/Apr/2009:09:01:36 -0600] Hint: Try setting the LogLevel to "debug" to find out more.
I [21/Apr/2009:09:03:52 -0600] Adding start banner page "none" to job 8.
I [21/Apr/2009:09:03:52 -0600] Job 8 queued on 'Quad4000-K7' by 'rodhanna'.
I [21/Apr/2009:09:03:52 -0600] Started filter /usr/libexec/cups/filter/cgpdftoraster (PID 224) for job 8.
I [21/Apr/2009:09:03:52 -0600] Started filter /Library/Printers/QTR/filter/quadtoneprint (PID 225) for job 8.
I [21/Apr/2009:09:03:52 -0600] Started backend /usr/libexec/cups/backend/usb (PID 226) for job 8.
N [21/Apr/2009:09:03:53 -0600] [Job 8] : QuadToneRIP: using curve K7-2880-EpEnhancedMatte
E [21/Apr/2009:09:03:54 -0600] PID 225 crashed on signal 5!
I [21/Apr/2009:09:03:54 -0600] Hint: Try setting the LogLevel to "debug" to find out more.

********************************************************************

**** QuadToneRIP Diagnostic Script --- Save Output for Analysis ****

********************************************************************

logout
[Process completed]