Disaster!!
Posted: Mon Sep 21, 2009 12:16 am
I really wanted to like this program and was planing to buy the key. Good quality prints, useful controls over ink usage and rendering. Above all long prints on my Epson Stylus Pro 3800. Then the first shadow, I could not induce landscape printing (see my post in this forum, Sept 18.) Well, I could always rotate the image in PhotoShop. I did so and made some nice prints. Then disaster! Went to make a print, same settings as the previous one. Got the dreaded "%%BoundingBox error message received" and the job would not print. Deleted the job, reset all the print parameters is PS and PF. Same error message, same failure. So I closed everything (including PhotoShop). PF toolbox could find the printer and show ink, etc. Relaunched PS and it Froze without showing the print dialog - Well and truly froze! I had to force quit! I then tried to remove the PrintFab Printer. But now the System Preferences froze when attempting to open "Printers and Faxes". Forced quit, rebooted and this was repeated several times. Also couldn't access jobs of printers on the CUPS "server". Tried to used the Uninstall on the PF disc image. Another freeze. So now I have a Mac Pro which cannot print - not a pretty thing for a photographer with a show coming up! So now I'm trying to restore from Time Machine. I've been a heavy computer user since 1987 and involved with digital imaging shortly there after. I've had some buggy software, but nothing as nasty as this. I'd appreciate learning where the hidden code for PF resides so that I can remove it by hand (If I can get my system to work).
Here is the system information. Mac Pro quad core (late '09). OS X 10.5.6, Epson Stylus Pro 3800, PhotoShop CS 4 11.01.
Bob Hesse
Perhaps my antennae should have been alerted when I noticed several unresolved threads in this forum without further replies from zedonet.
Here is the system information. Mac Pro quad core (late '09). OS X 10.5.6, Epson Stylus Pro 3800, PhotoShop CS 4 11.01.
Bob Hesse
Perhaps my antennae should have been alerted when I noticed several unresolved threads in this forum without further replies from zedonet.