WinFax PRO 4.0 Frequently Asked Questions
0.1 What is an FAQ?
0.2 What is the best way to get support from Symantec's online services?
1.0 General Questions
1.1 What is WinFax PRO 4.0?
1.2 What do I need to run WinFax PRO 4.0?
2.0 Installation And Setup
2.1 What do I need to do to move WinFax from one drive location to another.
2.2 What can I do to optimize my WinFax settings under Windows 3.x.
2.3 What should I do to optimize WinFax under Windows For WorkGroups 3.11?
2.4 Can I run WinFax under OS/2?
3.0 Connection Problems
3.1 WinFax was working fine, and then it stopped working or gives me errors.
3.2 I am having difficulty getting the area code or long distance numbers to function correctly.
3.3 I want to set WinFax so it won't detect the busy tone.
3.4 I have difficulty connecting to fax machines at rates greater than 9600 baud. How can I restrict the connection to 9600?
3.5 Graphics in the cover pages are showing as a cross-hatched area in the viewer and are not faxing.
3.6 What is Error Correction Mode (ECM) faxing?
4.0 Error Messages Within WinFax
4.1 I receive the error: "FAXMNG caused a General Protection Fault in module RTFCTL.DLL".
4.2 I receive the error: "Cannot locate VIM.DLL". How do I correct this?
4.3 I receive the error: "Integer Divide by Zero" when trying to send a fax.
4.4 I receive the error: "Abnormal Program Termination" when starting WinFax
5.0 Miscellaneous
5.1 I am having difficulty getting the Credit Card option to work. How can I test this option?
5.2 My fax image does not match the printout of my original.
5.3 Why are my TrueType fonts affected when I send a fax?
0.1 What is an FAQ?
An FAQ, short for Frequently Asked Questions, is a compilation of the most common questions and answers about a subject. This is an established technique (adopted from its widespread use on usenet) for reducing the repetition of questions and answers posted our online technical support areas.
This FAQ should not replace your User's Guide or your program's built-in Help files. This FAQ is prepared and maintained by our technical support staff and contains questions and answers that may not be covered in the original documentation.
Symantec aggressively maintains each FAQ to ensure that it contains solutions to the most current product support issues. You are encouraged to read this FAQ before posting a message to an online service and incurring any charges. In most cases, you will find an answer to your question here.
If you were referred to this document by one of our technicians or another customer, keep in mind that they are trying to provide you with answers to your questions in the most convenient, least expensive for you, and most accessible way. We also encourage you to suggest ways we can improve this or other FAQs. If you have suggestions about how we can improve these FAQs, we want to hear from you. Please feel free to post your suggestions on one of our online support forums.
--------------------------------------------------------------------------------
0.2 What is the best way to get support from Symantec's online services?
For technical support for WinFax, please visit our web site at http://service.symantec.com.
--------------------------------------------------------------------------------
1.0 General questions
1.1 What is WinFax PRO 4.0?
WinFax PRO 4.0 is a fax software application for Windows. It enables you to fax a Windows application document as if you were printing the document. WinFax PRO then sends the document through your fax modem over telephone lines to another fax machine or fax modem where an image of the document is received and can be read or printed. For more information about this product, you can view the press release about WinFax PRO 4.0.
--------------------------------------------------------------------------------
1.2 What do I need to run WinFax PRO 4.0?
Minimum hardware requirements:
IBM PC, PS/2 or 100 percent compatible
Intel 80386 or higher (486 or Pentium recommended)
4 MB of RAM (8 MB or more recommended)
OCR requires 4 MB of RAM and a 4 MB swap file.
10 MB hard disk space. Additional space is required for temporary files.
Microsoft Windows 3.1 or Windows For Workgroups 3.11
Microsoft or compatible mouse recommended
--------------------------------------------------------------------------------
2.0 Installation And Setup
2.1 What do I need to do to move WinFax to a new location?
Moving WinFax involves several steps and procedures. This is because WinFax assigns arbitrary numeric names to the fax image files when the files are created. Identifying these files through File Manager is extremely difficult. WinFax uses specific resources to display the information about image files and maintain pointers to fax image files. These resources contain a complete path to the image file. If the image is moved, the pointer no longer works. You can overcome this problem for the Send/Receive logs and the phonebooks but not for the Cover Pages and the Attachments. When Cover Pages or Attachments are moved, the pointers no longer work. The items no longer display when you select them in WinFax. Before you move a program or any part of a program, read the following procedure completely. Be sure you understand the steps involved and consequences of moving certain parts of WinFax before you actually do so.
The [WinFax] section of the WIN.INI file contains path statements relating to WinFax as follows:
ExePath=C:\WINFAX\
Fax Path=C:\WINFAX\DATA\
Cover Path=C:\WINFAX\COVER\
ExePath is the path to program files,
Fax Path is the path to the data (sent and received faxes), attachments and phonbook files.
Cover Path is the path to the cover pages and the graphic images contained in them.
When you move WinFax, you need to correct these entries so they point to the new location of these components.
Attachments
Attachments are managed by the ATTACH.DB file in the DATA directory. Normally, the attachment images are also in the DATA directory and have names like 23455001.FXS. (ãFXSä is the extension for attachments created by WinFax.) After you move the contents of the DATA directory, the ATTACH.DB file will still point to the original location. You need to create the folders again by hand and pick up the attachments in the old folders. This can be time consuming.
If possible, leave the attachments in their original location after you move the rest of WinFax. To do that, move all files except those with a .FXS extension. You also need to move ATTACH.DB. If you use this approach, attachments will display correctly.
If you have to relocate the attachments, you will need to recreate the attachment folders and the attachments themselves by hand. Before moving these attachments, print them as follows:
Open the Attachment screen by clicking the Attach button.
Click Fax/Print on the menu.
Repeat this for each attachment folder.
After you have moved the WinFax data, rename ATTACH.DB to ATTACH.OLD in the new data location.
Then complete this procedure:
Open the Attachments screen
Follow the procedure in Chapter 6 of the Userâs Guide to create the folders.
Follow the procedure ãAdding Attachments to Foldersä to add the attachments. The printout created above will serve as a guide for the descriptions and the file names.
Cover Pages
Cover Pages are managed by the COVER.DB file in the DATA directory. Normally, Cover Pages image files are in the COVER directory. If you move the COVER directory, the COVER.DB file is longer valid. You will need to edit the Cover Path entry in the WIN.INI file as follows:
Open the WIN.INI file and find the [WinFax] section.
Edit the line Fax Path=C:\WINFAX\COVER to point to the new location of the COVER directory.
After completing the previous steps, you will note that pointers in COVER.DB will be to old locations. You can correct this easily by deleting the COVER.DB file in the DATA directory and do a custom install of WinFax. Select Program Files and Cover pages only during the installation. This recovers the default folders that WinFAX installs. You'll need to create custom cover pages and folders by hand as described in the Userâs Guide.
Logs and Phonebooks
Create the new directory for the new DATA directory and then rename the old DATA directory to OLDDATA.
Copy the contents of the OLDDATA directory to the new directory location (this can be on a different drive).
Open the WIN.INI file and find the [WinFax] section.
Edit the line Fax Path=C:\WINFAX\DATA to point to the new DATA directory
In the new DATA directory, rename the file LOG.DB to LOG.OLD. When WinFax is started up again, the renamed file will be recreated. The send log, receive log and phonebooks are now relocated. If there were archive folders set up, they will have to be recreated.
To recreate the archive folders, open the send log by clicking the Send Log button on the tool bar.
Double click on ãNew Folderä on the left side of the screen.
Click the ãSelectä button then select the FTM file that corresponds to the archive folder that is being created. This has to be done for each folder. (Note that the STATUS.FTM file is for the Send/Receive logs and is already being used.)
--------------------------------------------------------------------------------
2.2 What can I do to optimize my Windows 3.x settings for WinFax send/receive reliability?.
Only make the following changes if you use Windows 3.x. These chances do NOT apply to Windows for Workgroups.
In the SYSTEM.INI file, add or edit the following lines:
Under the [boot] section:
COMM.DRV=WFXCOMM.DRV
under the [386Enh] section:
ComBoostTime=30
ComxBuffer=4096 (lower to 1024 if set to use 9600 buad or less)
ComxFifo=0
Where represents x the COM port number.
If your modem/serial port has a 16550AF UART chip (You can determine if your system uses such a chip by running MSD.EXE from the DOS prompt.
Under the [386Enh] section of the SYSTEM.INI file:
ComBoostTime=30
ComxBuffer=4096 (please note that some modems will not work with the buffer set greater than 512)
ComxFifo=1 (If you have high speed communication difficulties set this line to 0.)
ComxTXSize16
ComxRXSize=8
Where represents x the COM port number.
--------------------------------------------------------------------------------
2.3 What should I do to optimize WinFax under Windows for Workgroups 3.11?
Only make the following changes if you use Windows for Workgroups 3.11:
In the SYSTEM.INI file, add or edit the following lines:
Under the [Boot] section:
COMM.DRV=COMM.DRV
Under the [386enh] section:
;Device=*VCD (place a semicolon at the beginning of this line if this Device line is in this section)
** The VCD is only needed to be remarked if the Serial 386 is not the most recent.
Netheapsize=64
ComBoostTime=30
ComxBuffer=4096 (please note that some modems will not work with the buffer set greater than 512)
Comxprotocol=xoff
ComxFifo=1
ComxTXFIFO=1
ComxRXTrigger=8
Where x represents the COM port number.
Open the Control Panel in Program manager.
Double-click the 386 Enhanced icon (it looks like a computer chip), and turn off 32-bit File Access.
Open Control Panel in Program manager.
Double-click the ports icon, and open the port section being used by the modem and setup.
Type in a new baud rate of 38400, and set flow control for HARDWARE.
Exit and restart Windows so the new changes will take effect.
Ensure that you have the current version of a driver called SERIAL.386. This file is available through the Microsoft BBS as a self extracting file called WG1001.EXE.
The following is a Microsoft(R) Product Support Services Application Note that may be helpful:
WG1001: UPDATED SERIAL.386 DRIVER
FOR WINDOWS(TM) FOR WORKGROUPS Revision Date: 2/94
Introduction
"When you use Windows for Workgroups version 3.11 with serial communications software, you may experience the following problems: "If you are using a Pentium(TM)-based machine with a 16550 UART chip, your system stops responding (hangs) if there is data in the chip when the serial communications application attempts to open the communications port."
"A problem with the 16550 UART implementation causes the chip to become trapped in a mode in which data is always detected in its FIFO buffer."
"When you are using communications software, you may be able to make one connection after starting Windows for Workgroups, but any subsequent connections fail and may hang your system."
"This problem occurs when SERIAL.386 sends an extra NUL character through the port when the communications software calls the CloseComm application program interface(API) function. While this does not normally cause problems, your second connection may fail with some modems."
Note: The WG1001.EXE is a self extracting file that includes a read.me file (with this Microsoft Application Note, disclaimers, and installation instructions), and the updated SERIAL.386 driver that corrects both of these problems. If you follow the Microsoft instructions, you should also remove any COMxFIFO=0 line if it exists in the [386 Enh] section of your Windows SYSTEM.INI file.
--------------------------------------------------------------------------------
2.4 Can I run WinFax under OS/2?
WinFax PRO 4.0 was written to run under Windows 3.x. Many users run it under OS/2, but we cannot guarantee results because we have not tested WinFax Pro under this operating system. Because of that, we cannot offer technical support to OS/2 users.
However, the following information may be useful if you want to run WinFax PRO under OS/2:
Install WinFax under native Windows 3.1 and then migrate the application to WIN-OS/2. If the system locks up while checking the system configuration, try the following:
Remark out the serial port drivers COM.SYS and VCOM.SYS from the OS/2 CONFIG.SYS file. Once Winfax has been installed, remove the remark statements from in front of the serial port drivers.
When you run WinFax PRO under Warp, ensure that you have the latest NetWare requester patch for requester 2.11. This file is called R211FT.EXE and is dated 5/22/95. It is in NOVFILES.
We offer additional information through our technotes that are available electronically at the Delrina FTP site.
--------------------------------------------------------------------------------
3.0 Connection Problems
3.1 WinFax was working fine, and then it stopped working or gives me errors.
Try the following steps, which cover the most common causes of problems:
Disable any screen savers or anti-virus software.
Delete Windows temporary files from the \TEMP directory on the hard drive. You can check where \TEMP is located by typing in SET at the DOS prompt and pressing Enter. Delete only files with .TMP extension. Repeat this step for any other hard drives on the system.
Run CHKDSK or SCANDISK to check for file corruption.
NOTE: Before using these utilities, consult your DOS User's Guide.
To check your disk, type CHKDSK /F and press Enter at the DOS prompt. If you are prompted to use SCANDISK instead of CHKDSK, respond Yes. If you see a message indication there are lost allocation units in chains, and you are asked to convert the lost chains to files, respond Yes.
Type DIR and press Enter at the DOS prompt. Check to see how much free space is available on your hard drive. You should have at least 15MB. If not enough space is available, you will need to delete files or free up disk space in some other way until enough is available.
Type DEFRAG C:/F/N/B and press Enter at the DOS prompt. The switches in this command configure Defrag for full optimization, to sort files by name, and to restart the computer. This procedure can take some time depending on the size of the hard disk and the level of fragmentation. To learn more about DEFRAG, refer to your DOS manual. This utility was not included in versions of DOS before 6.0. Y should run Speed Disk from Norton Utilities or similar utility to defragment your hard disk.
Check your WIN.INI file for two lines:
LOAD=
RUN=
For testing purposes, disable these lines by placing a semicolon (;) in front of them. Save the changes, exit, and restart Windows. We ask that you disable these lines because they can run applications such as Quicken's BillMinder or other telephone dialers that can interfere with faxing.
Performance issues exist with the minimum RAM requirements, so if you are using a temporary swap file, you should change to a permanent swap file if you have enough disk space. You cannot create permanent swap files on DoubleSpaced or Stacked drives. For more details about swap file configuration, refer to your Windows User's Guide).
--------------------------------------------------------------------------------
3.2 I am having difficulty getting the area code or long distance numbers to function correctly.
If the destination area code is different than your local area code, WinFax treats the call as a long distance call. It will always use a "1" or another prefix that you specify.
WinFax compares the text in the area code fields; it does not perform a numerical check. WinFax determines that two area codes are different if one is prefaced by a minus (-) sign. The extra character is ignored during dialing.
As a result of an area code split, local calls can use different area codes, and long distance calls can use the same area code. You must change the recipient records in your WinFax Phonebook to accommodate the various dialing combinations as shown in the following chart.
Dialing from 222 to... In Area Code
field, type... In Local Number
field type...
Actually Dials...
a local 222 number 222 555-1234 5551234
a long distance 222 number -222 555-1234 12225551234
a long distance 222 number
(but must not dial area code) 222 1-555-1234 15551234
a local 888 number 222 888-555-1234 8885551234
a long distance 888 number 888 555-1234 18885551234
a long distance 888 number
(but must not dial area code) 222 1-555-1234 15551234
If you are using WinFax on a laptop computer and want to send a fax to somebody in your local area code when you are outside of it, place a minus sign (-) before the area code in the User Setup.
--------------------------------------------------------------------------------
3.3 I want to stop WinFax from detecting the busy tone.
When configured to "Detect Busy Tone", many fax/modems will mistake a voice response as a busy tone and disconnect the call. Machines that play a voice greeting while listening for a calling fax's periodic CNG tones confuse these fax/modems, and you may choose to override the feature as follows:
For Class 2 fax/modems, disable the Detect Busy Tone option in the Setup dialog
For Class 1 fax/modems, disable the Detect Busy Tone option in the Setup dialog, and insert the entry "AllDialControls=1" in the [General] section of WINFAX.INI file. This enables WinFax to respect the Detect Busy Tone setting in the Setup dialog. *Please note that this solution will only work for the standalone version of WinFax PRO 4.0.
--------------------------------------------------------------------------------
3.4 I have difficulty connecting to fax machines at rates greater than 9600 baud. How can I restrict the connection to 9600 baud?
For Class 1 fax/modems, insert "MaxTXSpeed=9600" into the [General] section of the WINFAX.INI file.
For Class 2 fax/modems, use the initialization string:
AT+FDCC=1,3
--------------------------------------------------------------------------------
3.5 Graphics in the cover pages are showing as a cross-hatched area in the viewer and are not faxing.
Follow these steps to resolve the problem:
Open the cover page in the Cover Page Designer.
Verify that View/Show Graphics is selected. If it is not then enable it. A check mark will appear next to the entry in the menu.
If the problem still occurs, then the [WinFax Importers] section may be missing from the WINFAX.INI file. The missing section follows:
[WinFax Importers]
Windows Bitmap (*.bmp)=BMP,DTIFLBMP.DLL,*.BMP
Windows Metafile (*.wmf)=WMF,DTIFLWMF.DLL,*.WMF
TIFF (*.tif)=TIF,DTIFLTIF.DLL,*.TIF
PC Paintbrush (*.pcx)=PCX,DTIFLPCX.DLL,*.PCX
GEM Image (*.img)=IMG,DTIFLIMG.DLL,*.IMG
GEM Metafile (*.gem)=GEM,DTIFLGEM.DLL,*.GEM
Mac Paint (*.bin)=PNT,DTIFLPNT.DLL,*.BIN
Encap. Postscript (*.eps)=EPS,DTIFLEPS.DLL,*.EPS
Gr. Interchange (*.gif)=GIF,DTIFLGIF.DLL,*.GIF
WinFax (*.fxs)=FXS,DTIFLFXS.DLL,*.FXS
After you make these changes to the WINFAX.INI file, close and restart WinFax.
--------------------------------------------------------------------------------
3.6 I receive an ECM error when connecting to some machines.
Disable the ECM feature in the [General] section of the WINFAX.INI file by adding the following line (in upper case) if you have a release of WinFax PRO 4.0 dated prior to July 1994:
ECM=0 (The default is ECM=1)
If you have the July 1994 release, simply uncheck the ECM option in the setup.
What is Error Correction Mode Faxing (ECM)
Although the ECM fax standards have existed for some time, it is a relatively new technology to computer faxing. On the other hand, even the least expensive fax machine may have ECM capability. ECM is different from the error correction that is incorporated in data communications. Modems have been available with V.42 and MNP features for some time, and data communications programs with file transfer "protocols" that provide error detection and correction capabilities are standard (ie: Xmodem, Zmodem, Compuserve B+. etc). None of this has any relevance to ECM faxing.
In ECM faxing, the error detection and correction is done entirely by the software (for instance, WinFax PRO 4.0). The modem is simply acting as a fax data pump. The Class1 fax modem is essentially unaware that the fax data it is sending or receiving carries error detection information. ECM faxing can occur at any fax speed from 14400BPS down to 2400BPS. ECM requires that WinFax have direct control over the fax protocol. For this reason, only Class1 modems support ECM faxing. Although the fax modem is unaware that it is sending ECM data, ECM faxing does alter the way in which WinFax must operate the modem. ECM faxing requires that WinFax exercise Class1 modes and command sequences that are never used in non-ECM faxing.
Modems that are fully capable of non-ECM faxing may not correctly support the additional functions used during ECM faxing. This can be a significant factor when attempting to resolve WinFax ECM send/receive faxing problems. The "Delrina Approved" status is only given to those Class1 modems that properly support ECM faxing. Another significant factor is that some fax machines, especially older units, that support ECM faxing do not correctly follow the ECM fax protocol. Often, the ECM in these fax machines not only wonât send or receive with WinFax, but it also won't work with many other fax devices.
--------------------------------------------------------------------------------
4.0 Error Messages Within WinFax
4.1 I receive the error: "FAXMNG caused a General Protection Fault in module RTFCTL.DLL".
This problem occurs if the Spell Checker is left open during a send from WinFax.
If you click on the cover page during a Spell Check, the Spell Check dialog box will disappear, hidden behind the cover page fill-in area. If you then choose Text/Spelling, the dialog box will reappear. At this point, if you initiate a send, the error will occur as follows:
FAXMNG: An error has occurred in your application.
This is followed by:
Application Error:
FAXMNG caused a General Protection Fault in module RTFCTL.DLL at ...
The only way to avoid this is to minimize the cover page fill-in area to reveal the Spell Check dialog box. You can then continue with no problem. This error only occurs if the Spell Check dialog box is hidden behind the Cover Page Filler.
--------------------------------------------------------------------------------
4.2 I receive the error: "Cannot locate VIM.DLL". How do I correct this?
This message occurs when WinFax recognizes that Lotus cc:Mail or Lotus Notes is present on the system, but the programs cannot be found.
Add the location of the VIM.DLL file to the path by following these instructions:
Search the system for the file VIM.DLL.
If you cannot find VIM.DLL file, contact Lotus.
If you find more than one copy: Determine the mail version being used (for example, cc:Mail 1.11 or cc:Mail 2.0). Determine the directory of the mail system. The correct VIM.DLL file must be first.
Add the path you found in the VIM.DLL search to the PATH statement in the AUTOEXEC.BAT file.
Reboot the system.
NOTES:
Previous versions of cc:Mail may not include VIM.DLL
Similar errors may occur if:
the E-mail directory is on a network drive, and the system does not have a drive mapped to that location.
Both cc:Mail and Lotus Notes are installed on the same system. Both of these programs use VIM.DLL which may be different versions.
The system searches for Windows .DLL files in this order:
Current directory,
Windows directory,
Windows\System directory,
Path statement
For furthe4r information, also refer to the Delrina WinFax PRO 4.0 Userâs Guide: Appendix B "Using WinFax with Your Mail System"
If you do not wish to link WinFax with the mail system, you can remove that parameter from the WINFAX.INI file under the [General] section. Disable the line ãMailProgram=CC20ä by placing a semicolon at the beginning.
--------------------------------------------------------------------------------
4.3 I receive the error: "Integer Divide by Zero" when trying to send a fax.
In most cases, this error is generated by a video driver that is capable of 32,000 colours or more. You may need to change to a video driver that supports a maximum of 256 colours. Change the video display setting by clicking on the Windows Setup icon and choosing Options.
If changing to a lower resolution does not help, try excluding the memory address of the video card. You need to consult the video card documentation for information on this procedure.
NOTE:
WinFax was designed to be compatible with Windows video drivers,that offer a maximum resolution of 256 colours. We recommend testing with the standard Windows VGA driver to determine if there is a video driver problem. This resolution is fully compatible with WinFax.
--------------------------------------------------------------------------------
4.4 I receive the error: "Abnormal Program Termination" when starting WinFax.
CAUTION:
This solution will erase any custom folders and their contents from the logs.
One of the following files in the \WINFAX\DATA directory is corrupt:
LOG.DB
COVER.DB
ATTACH.DB
PHONE.DB
The following steps will likely result in some data loss but are necessary to determine which file is corrupt.
Close WinFax.
In File Manager, rename the \WINFAX\DATA directory to \WINFAX\DATA_OLD.
Create a new \WINFAX\DATA directory.
Copy one *.DB file to the \WINFAX\DATA directory. Hint: first try to copy the *.DB file that was accessed last. For example, if WinFax was set to display the Attachments Adap-Table before the Abnormal Program Termination message occurred, copy the ATTACH.DB file first.
Launch WinFax, and see if the error message displays again.
If no error message displays, repeat steps 4 and 5 using the remaining *.DB files. When the Abnormal Program Termination message appears, you'll be able to determine that the last *.DB file copied back to the \WINFAX\DATA directory is corrupt.
Delete that *.DB file, and copy any remaining *.DB files over from \WINFAX\DATA_OLD to \WINFAX\DATA.
--------------------------------------------------------------------------------
5.0 Miscellaneous
5.1 I am having difficulty getting the Credit Card option to work. How can I test or troubleshoot this option?
The following steps will help locate or correct this problem:
In the WinFax menu, go to Setup/User, and make sure these settings are correct:
Country Code =1 (for North America)
Area Code= (your area code)
International Access=01
Long Distance Access=0
(These settings will vary depending on the country you are dialing from)
In the WinFax menu, go to Setup/Credit Card, select the Long Distance Service, then click Modify. Make certain the fields are set up correctly for the credit card you are using. If the credit card service requires a "0" before the area code, it should be in the Long Distance Access Code field (some services do not require this).
The wait times might need to be adjusted depending on the requirements of the service. Be careful using "Wait for Dial Tone". Some services have a "Bong" sound or a voice, neither of which is detected as a dial tone. Use "Wait" instead.
Click Send in WinFax, and select a long distance number from the phonebook. It should appear in the ãNumberä field as 1-555-123-4567
-Click on "Schedule/Hold" to hold the fax in the Outbox (for troubleshooting)
-Click ãOptionsä and check ãCredit Cardä then OK.
-Click "Cover Page"
-Click "Send" button at the bottom.
The fax will appear in the Outbox.
Click the Outbox button on the toolbar and highlight the event you just created. This will display the complete credit card dial string. The long distance access number, credit card number, and commas will appear as asterisks. (There will be a comma for every 2 seconds of delay). This will indicate whether or not the sequence is being set up correctly by WinFax.
Highlight the item in the Outbox then, on the menu click Outbox/Send Now. The fax should send.
If the fax does not send, check the modem using Windows Terminal as follows:
Open Terminal (normally in the Accessories Group).
On the Terminal menu, select Settings/Communications. \
Select the modem port. Then click OK. (The other settings are not relevant for this test)
Type ATZ, and press Enter (the letters may not appear on screen when typed).
Type ATDT12345678901234567890123456789012345678, and press Enter.
Make certain that all 38 characters dial. If not, the modem is most likely not capable of dialing a long string and will not handle credit card dialing.
Dial the credit card sequence: ATDTssssssss,,0-aaa-nnn-nnnn,,cccccccccc, and Press Enter (Where s is the service access number, n is the phone number, c is the credit card number) This will depend on the service you are using.
Connect a telephone to the line the modem is on, and listen while the number is being dialed and the modem is connecting. This will probably indicate where the problem lies.
Try dialing the number with the telephone. This will indicate whether or not the line is working correctly.
Listen on the phone while the modem is dialing. The messages should offer a clue as to what is going wrong.
Some modems enable you to break the dialing string up by inserting a semicolon (;) between digits.
--------------------------------------------------------------------------------
5.2 My fax image does not match the printout of my original. Why does WinFax affect the image size?
This situation is not uncommon when changing from one print driver, such as a laser printer driver, to another, such as the WinFax printer driver. It happens because the resolutions (dots per inch) vary from one printer driver to another. In addition, the printable area and the number of dots across the width and along the length of the page vary when switching between printer drivers.
Fax resolution in WinFax is 204 dpi wide by 196 dpi high. Many printers now support 600 dpi or more. Since images (fonts and graphics) must fit on an integral number of dots, the scaling from one driver to another will seldom be perfect. For example, a line 5 dots wide at 600 dpi should be 1.7 dots wide in WinFax at 200 dpi. The nearest fit is 2, so the scaling is going to be slightly off.
In conclusion, the fax is not going to be a perfect copy of the original but a close approximation of what it should look like.
--------------------------------------------------------------------------------
5.3 Why are my TrueType fonts affected when I send a fax?
When printing the same document to both a 300 dpi device and a 100 or 200 dpi device, you may frequently see a difference in font size. Though the fonts are scaleable, the scaling will only be to the nearest dot.
A TrueType character rendered to 37 pixels tall on a 300 dpi DeskJet, will be 24.7 pixels tall to be the same size on a 200 dpi fax. Since only an integral number of pixels can be used, 24.7 must be rounded to either 24 or 25 pixels. Once that occurs, the font for the fax is a different size, though Word indicates the same point size value on the ribbon.
As this phenomenon occurs on a page of text, line wraps will occur at different points, and a different number of lines can result on the page, thereby changing the page breaks.
--------------------------------------------------------------------------------