Phaser 6280DN print host driver failing for 32bit applications

[Helios]

Kimzi - we will give that a try.  I have no problem changing settings, etc.  I just don't want to tell an end user "well, you can't use that font or image......" as we have hundreds of canned documents that are very standardized.

Will report back.

[Kimzi]

Hey!

Sorry if I didnt clarify enough, it's not only a workaround it's also a way to determine where the problem is. It's hard for someone not being near the machine as there can be several different reasons for your problem.

You can try changing the protocol from LPR to RAW in the port config, you can also try going to Printing Preferences -> Advanced and check "Print Truetype font as bitmap"

Thanks!

[Helios]

Please take no offense.  We are looking for a solution.  Not a workaround.  We have went round and round with trying the "does it do it when you change X, Y or Z....?".

We've went through a lot of the 15 and 20 step processes to continuously come back to the same thing.....it still tombstones the printer until it is rebooted.

The most basic, brand new Word doc will reproduce this over and over again....no matter the font.  Lots of history on this anomaly since 09 so I would hope by now there would be a known fix.

This is Windows 7 64 bit vs Office 2010 32 bit vs Phaser 6280DN.  Has to be an answer.

Thank you for the response though!

[Kimzi]

Hey!

if you try to convert the word documents FONT from Calibri to Arial or similar, does that work?

Thanks!

[Helios]

Windows 7 64 bit systems pointing to this printer (either PC or PS) with Office 2010 32 bit product (predominantly Word) cause it to freeze up with "data processing - lpr" and you then have to reboot the printer.  Notepad, test pages, pdf files print fine.  Tried universal driver, etc.  Research on the has many references to 15 and 20 step processes to try and figure out if it is the doc or app but not much else as in a fix.

The search engine results here for the issue are far too literal and text oriented - no context rich results.

Lots of complaints about this issue as far back as 2009 so there should be a fix by now.

Our HP printers do not do this...............