General discussion

Print Dialog Crashing Apps

Came across an interesting problem with a flat pannel iMac (10.3.Cool at work. Every time a user tries to print something, instead of the print dialog coming up, the application crashes. Every application, not just specific ones.

All printers are HP LaserJets, and all printing is done via TCP/IP.

So far things tried include deleting and re-adding the printer. Updating the drivers from HP's website. Running a printer repair program, and running the full (103MB) 10.3.8 updater.

Anyone here have any other ideas of things that might be tried?

Discussion is locked

Reply to: Print Dialog Crashing Apps
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Print Dialog Crashing Apps
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Archive and install

seems to be the only thing you have not tried. When did the problem actually start? Was it straight after the .8 update or before? Can it be linked to any of the recent updates. If not, then the Archive and install may well be the way to go.
Interesting name..European connotations??


- Collapse -
Print Dialog

Try uninstalling Print Dialog software. Every designer in our company never uses print dialog because it takes memory to run and it runs in the background all the time. Print dialog never crashed an app, but it certainly slows down just about everything. Try uninstalling it on your imac first. and let me know if that solves a memory issue.


CNET Forums

Forum Info