|
DCS to Epson Pro 7600 from IDCS2
Okay, our output files to vendors are DCS files. We pull proofs of everything in house for approval prior to sending the DCS to a vendor. Although it's not nearly ideal (we're working on it) we've been importing the DCS files into a Quack template and sending them to various proofers, including an Epson 7600, with no troubles (at least not that apply here). But, now we're switching completely to ID and when I place a DCS into ID (one that works when sent from a Quack doc) and print it to the 7600 there's a problem.
I get an error message saying that there may be binary info in one or more EPS files and that it might not output. And, well, I can't get it to output. Actually, I did once but it was nothing but a bunch of binary code. The print dialog is set up to output ASCII and all other setting, for the most part, mimick how we do it in Quark. In short, why does this file output from Quack and not ID? I've been digging around for days and haven't found a solution but have a feeling it might be right under my nose. Any one have any ideas?
Thanks,
Soilworker
|