Text that is formatted in printer device fonts may not print correctly in x64 versions of Windows Server 2008, of Windows Vista, and of Windows Server 2003

Article translations Article translations
Article ID: 948696 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You print some documents.
  • The printer driver is based on Microsoft Universal Printer Driver (Unidrv).
  • The rendering occurs on a computer that is running an x64 version of Windows Server 2008, of Windows Vista, or of Windows Server 2003.
  • The printer driver includes some font metrics data in its resource DLLs. The data is in formats compatible with versions of Windows earlier than Windows 2000. (This situation usually occurs in drivers for old nine-pin printers.)
  • Text strings that are output to the printer are formatted in a device font.
In this scenario, certain printer drivers may print the text characters by using incorrect ASCII character codes. Therefore, the output may be rendered by using incorrect fonts. Additionally, text that is formatted in bold or italic fonts may be rendered differently on a 32-bit platform than on a 64-bit platform. In this case, the 32-bit platform output is correct.

Notes
  • This problem occurs only on x64 versions of Windows Server 2008, of Windows Vista, and of Windows Server 2003. It does not occur on x86-based versions of these operating systems.
  • Documents are rendered before they are printed. This problem occurs on the computer on which rendering is performed. Rendering may occur on the client or on the print server, depending on several factors specific to each configuration. Therefore, to understand whether the hotfix that is described in this article is applicable, you must consider the platform type (32-bit or 64-bit) for the client and for the print server.

CAUSE

A printer driver usually provides information about its device fonts. For example, this information may include font metrics and conversion tables. This information is available in several formats. These formats include the following:
  • Unidrv Font Metrics (UFM) and Glyphs Translation Tables (GTT) as defined by Microsoft Universal Printer Driver
  • Printer Font Metrics (PFM) and Character Translation Table (CTT) as defined by Windows NT 4.0
  • Image Font Information (IFI) and Run Length Encoding (RLE) as defined by Windows 3.1 (16 bit)
For compatibility reasons, all these formats can be interpreted by Microsoft Universal Printer Driver or referenced by a Unidrv-based driver. However, these formats may undergo an internal conversion when they load from the driver's binary data into memory. Depending on the specific format, this conversion is more likely to occur or is more complex on a 64-bit platform. This is true because the original definitions are not based on 64-bit specific data types. Therefore, a different implementation is used on 64-bit platforms. This implementation causes the problem.

RESOLUTION

Hotfix information for Windows Server 2008 and for Windows Vista

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix on a Windows Server 2008-based computer, no prerequisites are required.

To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed. For more information about how to obtain the latest Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File information notes for Windows Server 2008 and for Windows Vista

  • You can determine the files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.0.6001.22xxxWindows Server 2008 SP1 and Windows Vista SP1SP1LDR
  • Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista.
  • The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, together with the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files are signed with a Microsoft digital signature. The attributes for the security catalog files are not listed.
All supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ntprint.infNot applicable9,53606-Jun-200823:01Not applicable
Locale.gpdNot applicable14,08818-Dec-200721:43Not applicable
Msxpsinc.gpdNot applicable7318-Dec-200721:43Not applicable
Msxpsinc.ppdNot applicable7218-Dec-200721:43Not applicable
Mxdwdrv.dll0.3.6001.22198748,03207-Jun-200803:56x64
P6disp.gpdNot applicable25,48918-Dec-200721:38Not applicable
P6font.gpdNot applicable3,29318-Dec-200721:38Not applicable
Pcl4res.dll0.3.5479.0288,76807-Jun-200803:55x64
Pcl5eres.dll0.3.5479.01,058,81607-Jun-200803:55x64
Pcl5ures.dll0.3.5479.01,057,28007-Jun-200803:55x64
Pclxl.dll0.3.5479.0207,87207-Jun-200803:40x64
Pclxl.gpdNot applicable10,37518-Dec-200721:38Not applicable
Pjl.gpdNot applicable1,15618-Dec-200721:38Not applicable
Pjlmon.dll6.0.6001.2219821,50407-Jun-200803:57x64
Ps5ui.dll0.3.6001.22198854,01607-Jun-200803:55x64
Pscript.hlpNot applicable26,03818-Dec-200721:16Not applicable
Pscript.ntfNot applicable1,062,73218-Dec-200721:43Not applicable
Pscript5.dll0.3.6001.22198628,73607-Jun-200803:55x64
Pscrptfe.ntfNot applicable1,293,18018-Dec-200721:43Not applicable
Ps_schm.gdlNot applicable5,56118-Dec-200721:43Not applicable
Stddtype.gdlNot applicable23,81218-Dec-200721:43Not applicable
Stdnames.gpdNot applicable14,36218-Dec-200721:43Not applicable
Stdschem.gdlNot applicable59,11618-Dec-200721:43Not applicable
Stdschmx.gdlNot applicable2,27818-Dec-200721:43Not applicable
Ttfsub.gpdNot applicable69818-Dec-200721:43Not applicable
Unidrv.dll0.3.6001.22198472,57607-Jun-200803:58x64
Unidrv.hlpNot applicable21,22518-Dec-200721:16Not applicable
Unidrvui.dll0.3.6001.22198884,22407-Jun-200803:55x64
Unires.dll0.3.6001.22198761,34407-Jun-200803:55x64
Xpssvcs.dll6.0.6001.221982,936,83207-Jun-200803:58x64

Hotfix information for Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed. For more information about how to obtain the latest Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 with Service Pack 2, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Locale.gpdNot applicable14,08802-Jul-200815:59Not applicableSP2
P6disp.gpdNot applicable25,48902-Jul-200815:59Not applicableSP2
P6font.gpdNot applicable3,29302-Jul-200815:59Not applicableSP2
Pcl4res.dll0.3.5479.0288,76802-Jul-200815:59x64SP2
Pcl5eres.dll0.3.5479.01,058,81602-Jul-200815:59x64SP2
Pcl5ures.dll0.3.5479.01,057,28002-Jul-200815:59x64SP2
Pclxl.dll0.3.5479.0207,87202-Jul-200815:59x64SP2
Pclxl.gpdNot applicable10,37502-Jul-200815:59Not applicableSP2
Pjl.gpdNot applicable1,15602-Jul-200815:59Not applicableSP2
Stddtype.gdlNot applicable23,81202-Jul-200815:59Not applicableSP2
Stdnames.gpdNot applicable14,36202-Jul-200815:59Not applicableSP2
Stdschem.gdlNot applicable59,11602-Jul-200815:59Not applicableSP2
Stdschmx.gdlNot applicable2,27802-Jul-200815:59Not applicableSP2
Ttfsub.gpdNot applicable69802-Jul-200815:59Not applicableSP2
Unidrv.dll0.3.6001.22198472,57602-Jul-200815:59x64SP2
Unidrv.hlpNot applicable21,22502-Jul-200815:59Not applicableSP2
Unidrvui.dll0.3.6001.22198884,22402-Jul-200815:59x64SP2
Unires.dll0.3.6001.22198761,34402-Jul-200815:59x64SP2

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This problem may occur with the IBM Proprinter printer driver. This driver is included with the Windows Server 2003 installation CD.

For example, when the IBM Proprinter printer driver is used, string "abcd" is output in the following sequence of character codes:
0x96, 0x97, 0x98, 0x99
The string is output in this sequence instead of in the corresponding ASCII values. These values are 0x61 and the appropriate successive codes. On the same printer, bold fonts are unexpectedly output after a double-width escape sequence.

This hotfix also addresses another problem. In this problem, font metrics that are queried by the GetTextMetrics function return invalid data for the TEXTMETRIC::tmWeight field and for the TEXTMETRIC::tmItalic field.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameAmd64_ntprint.inf_31bf3856ad364e35_6.0.6001.22198_none_974f88548c6fb869.manifest
File versionNot applicable
File size19,295
Date (UTC)09-Jun-2008
Time (UTC)15:41
PlatformNot applicable
File namePackage_1_for_kb948696~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,990
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_2_for_kb948696~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,826
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_3_for_kb948696~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,826
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,375
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,438
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,429
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,430
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,433
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable
File namePackage_for_kb948696_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot applicable
File size1,438
Date (UTC)09-Jun-2008
Time (UTC)15:38
PlatformNot applicable

Properties

Article ID: 948696 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 Standard
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Business 64-bit Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
Keywords: 
kbautohotfix kbexpertiseinter kbbug kbfix kbqfe KB948696

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com