I resolved a postscript issue by applying two patches from the xerox.com site to my brand new xerox docucolor 242 with bustled EFI feiry X3eTY RIP (1 and 2)
Now I have a new problem specific to CorelDraw (both X3 and X4) printing to this RIP/printer.
To the best of my memory all docucolor and other high end Xerox devices were originally designed to operate with Creo work flows from a MAC environment. This rotation issue existed many years ago and still does to this day with Creo work flows. Some times even if you distill PDF Creo will rotate the output so I use the device independent driver and then Distill the PDF.
You might try not using the portrait or landscape feature, use the custom page size and ignore any portrait and landscape warnings.
A good idea, but unfortunately when I print to the full-featured Fiery X3eTY driver without the pagemaker PPD file it doesn't give me the option of the standard postscript custom page side dialog box but instead when I select postscript custom size it intercepts and enters maximum values which allow 11 x 17 to be entered only one way.
So if you aren't on Vista but XP you should be able to use the other driver and the printer's PPD. If the PPD is correct yo shouldn't loose any features.
That said what everyone I know does is print files as PS using the printers PPD then process in Acrobat to check and output the file back to PS from Acrobat.
In other words everything in the workflow no matter what the output program was is processed in Acrobat. That way they only have to fuss with 'is Acrobat correct'.
I don't use Acrobat. I just send out PDF.
Email me your PPD for that printer. akayani at aapt dot net.au
And I'll see what happens here. And let me know if you are working from Vista or XP.
OK I can see that driver is based on the Adobe one. That is a positive.
I think it's up to the lads at Corel to step in and make some comment now.
Just editing the values seems to work fine here. I'd have thought if it was complex to fix on the Draw output end that it couldn't be impossible or that big a deal to fix via a script acting on the output PS file.
You would have to track down an editor that could cope with big PS files to do it manually. Emacs maybe.
Clearly if we had a few clues here this is doable.
http://www.winvi.de/en/download.html
That seems to manage big files with resonable easy. But I can see this approach getting really slow on big ps files.