Finally, after ignoring the vendor's denial of the printer's problem when we've gotten garbled printing for pdf files, Ricoh has finally released an updated driver.<\/p>\n
I'm a little impressed by Ricoh's responsibility in this matter. <\/p>\n
There's usually little errors on my part. Whenever I've concluded it's the manufacturer's or the vendor's fault, it usually is. I just had to follow the only solutions they had in mind at that time such as install postscript driver, older driver, etc.<\/p>\n
This fault by Ricoh's previous defected driver has cost NYGC lots of paper waste. <\/p>\n
Seems that the latest version was out about two months ago, I thought I had given up on them. Just happened to come across it and noticed a note in their fix detail...which was exactly the problem I have been researching into...thinking that I was going crazy for being the only one looking for a @PJL JOB NAME problem. <\/p>\n
Latest version: 3.1.0.0<\/em><\/p>\n ...<\/em><\/p>\n <\/p>\n <\/font><\/em><\/p>\n ... <\/em><\/p>\n <\/p>\n Now the next NYGC networking enigma is the accessibility of certain https form sites that recently occurred. My guess is IP\/ISP related issue. <\/p>\n [@more@]<\/p>\n","protected":false},"excerpt":{"rendered":" Finally, after ignoring the vendor's denial of the printer's problem when we've gotten garbled printing for pdf files, Ricoh has finally released an updated driver. I'm a little impressed by Ricoh's responsibility in this matter. There's usually little errors on … Continue reading