Garbled Faxes with Class 2 Fax/Modem

ID: Q148877


The information in this article applies to:
  • Microsoft Windows 95
  • Microsoft Windows 98

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you receive a fax in Microsoft Exchange, the fax may appear garbled. When you open the fax in Fax Viewer, the output may resemble a bar code or contain blank pages.


CAUSE

This behavior can occur because some Class 2 fax/modems reverse the bit order of incoming faxes.


RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

To resolve this issue, switch the bit order of incoming faxes for affected fax/modems. To reverse the bit order for incoming faxes, follow these steps:

  1. Exit and log off Microsoft Exchange.


  2. Using Registry Editor, add the string value CL2SWBOR to the following registry key


    Hkey_Local_Machine\Software\Microsoft\At Work Fax\Local Modems\TAPI0001<xxxx>


    where <xxxx> is a unique TAPI identifier for the fax/modem.


  3. Set the string value for CL2SWBOR to 1.


  4. Quit Registry Editor, and then restart your computer.


Additional query words: garbage unreadable barcode etech

Keywords : kbenv kbhw win95 wincomm awfax win98
Version : 95
Platform : WINDOWS
Issue type : kbprb


Last Reviewed: January 28, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.