Jim
I had the same problem a year and a half ago with PSE 2.0 and a LaserJet 1200. It was a known issue with the LaserJet and had nothing to do with PSE.
The problem was that when using a USB connection, the LaserJet could in Binary only print endless pages of garbage. The problem was solved by switching to ASCII in PSE 2.0. And, by following a set procedure to resetup the LaserJet. When I contacted HP they were immediately helpful. Hope this is of help.
Gordon
Gordon,
Thanks for the info. I tried ASCII but knew of no set procedure. I will give HP a call on Monday when their full tech support service is available.
Thanks Again,
Jim
This may or may not be related, but when I first installed Tiger (10.4), all my Brother laser prints came out as gobbledygook. I took the advice on Apple’s forums and deleted *all* my printers (not just the Brother) and re-added them, and then suddenly all was right with the world again. Seems odd, but it worked.
Oh, and, um, it would be nice if you changed your middle name. 😉
We will work on that Lou. We had a brief chat via email and Jim was very good about the whole thing. Just looking into whether this will affect past posts as well.
Thanks for the observation.
Cheers
Lou,
I tried the all-printer deletion and added back only the 2200d; nothing changed. Changing to ASCII format has allowed me to get a tolerable (though moderaely noise-corrupted) printer output – thanks Jim J.
Sorry for the middle name. I am not usually a poster – nor a hot head. This was my first posting – anywhere. I am usually a simple business user, with adequate experience to keep most things working – and a business policy that says when my product is part of a problem, my small company is part of the solution (w/o additional charge). So I reacted strongly when a multi-billion dollar Goliath couldn’t be bothered. Not being an experienced poster, I thought the name was for registration purposes only, and had no idea that the world would be exposed to it. My apologies. Once it was there, I didn’t know how to change it, but Jim J emailed some guidance that I will try. If I’m unsuccessful, he implied Adobe could and would fix it.
JM