When I print to my brand new xerox docucolr 242 with bustled Fiery RIP I'm getting some weird "random shape" stars on the page when I print from Draw X3 or Draw X4. If I use publish to PDF and print the same page from acrobat, everything is fine. On one page there is a gray "star" shape covering half the page. On another there is a black "star" over much of the content and a white "star" over another part of the page. I started using the same postscript settings in draw that I've used with my canon printers for years without issues. i've tried postscript 2, 3, and conform to DSC in corel's postscript tab. I've also tried the flatness to 1 just to see if it would make a difference, but no change. A few simple pages are fine, but most of my pages are printing with these weird knockout stars to the xerox driver (latest dc242 driver, windows vista os. From acrobat everything is fine. Also if I rasterize the whole page everything is fine, but that's losing a lot of quality and really bloating the print size.) Anyone see something like this before or have any ideas?
Here are some illustrations of what is happening:
In CorelDraw
(prints exactly like this on my canon printers also with fiery rips)
As printed by the Fiery + Docucolor 242'
I've tried setting changing postscript from level 3 to level 2 with no change.
If I publish to PDF and print the PDF from acrobat/adobe reader, it prints perfectly.
It also prints perfectly if I raster the entire page in coreldraw, other than having to really slow down the print or lose quality of text.
If prints fine to my older canon + fiery rips, so it's something with CorelDraw combined with the new FIery Docucolor 242 rip, but I'm running out of ideas.
Are you using postscript driver or PCL driver for the device?
Island said:If prints fine to my older canon + fiery rips, so it's something with CorelDraw combined with the new FIery Docucolor 242 rip, but I'm running out of ideas.
I'm using the latest EFI/Fiery/Xerox Postscript driver.
The postscript driver has things like support for FreeForm to do variable data merging to print the addresses on and I've always found the postscript drivers preferable in the past with the Fiery controllers.
(I'm using the postscript drivers for my canon fiery rips too without any issue with draw so this was quite unexpected.)
This is the driver I'm using:
http://www.support.xerox.com/go/results.asp?Xtype=download&prodID=DC242_DC252_DC260&Xlang=en_US&Xcntry=USA&ripID=XRIP_DC260_Base
The PCL driver for this RIP won't install on Vista - get an error - and it's labeled for Windows 2k and XP only. Thought it could provide an interesting workaround, but I really need to figure out how to get the postscript driver to work with corel (even if the PCL driver would install, I really want the freeform plus colorwise settings and all the detailed settings in the PS driver). Since it does work fine printing the corel pdf-exported content from acrobat to this postscript driver, something very strange it going on that I have not experienced before causing this very weird and extreme error when printing from corel.
Yes, I see the same error with a Xerox Docucolor 242, but doesn't happen with other models (250 for example) and is not for all jobs, or allways, only sometimes happens. And sometimes it seems a memory problem, because we can print fine a copy fine, other copy, but when print again, the same document, the Docucolor prints with this error. If you reset computer and printer, in most cases print fine again.
Try to change the level of Postscript (level 2 works fine) and don't use the PCL driver (Postscript is better).
I might have solved it at last - at least I'm not seeing it on the two test pages above which were happening every time earlier tonight and driving me nuts having to publish to pdf every time to print a page from corel or else have to wonder if I would get something wild.
I went back and applied this patch http://www.support.xerox.com/go/getfile.asp?Xlang=en_US&XCntry=USA&objid=65469&EULA=0&prodID=DC242_DC252_DC260&Family=DocuColor&ripId=XRIP_DC260_Base&langs=English%20(US)&plats=Windows%20Vista&Xtype=download&uType= from 2007 because it mentions a non specific problem with coreldraw x3 being solved.
I passed right by that before because the date on the brand new fiery itself is from a month ago in 2008 or a year after that patch was relased so I just figured it was already integrated into the build of the fiery, but I guess the patches are not installed by default.
Glad you may have solved it. I agree with Ariel, a PS driver is going to be better in long run.
Island said:I passed right by that before because the date on the brand new fiery itself is from a month ago in 2008 or a year after that patch was relased so I just figured it was already integrated into the build of the fiery, but I guess the patches are not installed by default.