Groupwise mail printing problem - all formatted?

[Manim]

Hi,

One of my users has managed to acquire a problem whereby every timehe tries to print an email from groupwise to any printer, (be it newly created or existing printer)the mail always prints Italic and Strikeout.

His Groupwise client was recently upgraded from 5.2 to 6.5, and he logs into a win2k laptop using a roaming profile.

If i log into his email account using any other computer but with a different user profile, i can print fine, but if i log in using his (windows 2000) roaming profile and attempt to print then this problem occurs. This then points to a setting or error in his profile but i cannot find it! Every other programme that i can think to try (office progs etc) prints ok on his laptop.

Does anyone know how to rectify this or have any suggestions i might try to fix this, short of completely recreating his roaming profile?


Thanks

Chris

 

[MichiganRon]

Manim,

Download and install the most recent printer drivers for whichever printers he is using. If available, do not use the "enhanced" driver. For example, if you have a choice between PCL6 or PCL5e, choose the PCL6 (the "e" in PCL5e stands for "enhanced&quot.

GroupWise has had problems using "enhanced" versions of HP drivers in the past. It may not solve your problem, but it's a good start.

-Ron

P.S. I'm assuming that you've tried uninstalling the GroupWise client and reinstalling it? If you haven't, try that too.

We all play from the same deck of cards, it's how we play the hand we are dealt which makes us who we are. -Me

murof siht edisni kcuts m'I - PLEH

 

[ironwood]

You may find that you have to recreate the users profile.

Ironwood

 

[Manim]

Thanks for your replies, unfortunately whichever printer he attempts to use with whichever drivers this occurs. (apart from those without the ability to print in italics of course!). Also had tried uninstalling and reinstalling groupwise but that didn't fix it either. I can recreate the problem on different machines using his login (active directory) so I wasn't holding out too much hope!

I have to say it looks like one of those problems I'll have to file in "Don't know why it occurred, know how to fix it". Could spend days trying to find out what caused it and still be no closer. I think if I don't get struck by blinding light of inspiration during today i'll just recreate the profile as ironwood suggests.