• Import WinFax PRO faxes and contacts.
• Powerful, easy-to-use fax software.
• Produce professional looking faxes with full preview and annotation.
• Access Microsoft Outlook contacts directly when sending faxes.
• Forward received faxes by email.
• Operates as a network fax client for FaxTalk Multiline Server
• Broadcast faxes to fax numbers and email addresses.
• Block the reception of unwanted junk faxes.

Windows Server 2003

The first problem with installation of WinFax PRO under Windows 2003 is that the printer driver support in the operating system was moved from kernel to user mode. The reason is that the use of kernel mode printer drivers can possibily cause a server to hang, result in a blue screen and require a reboot. This isn’t something you want happening on a server. Because of this possibility, Microsoft decided to block the installation of all kernel mode printer drivers in Windows 2003. During the installation of WinFax PRO, a kernel mode printer driver (also called version 2 printer driver) is added to your list of installed printers. By default, Windows 2003 won’t allow you to add this printer, and during the installation it is either ignored silently or a printer driver related error message is displayed. Fortunately, in Windows 2003 you can bypass this restriction. You can set a group policy in Windows 2003 to allow the installation of kernel mode printers. Once you’ve done this, you should be able to successfully install WinFax PRO under Windows 2003.

Windows Server 2008

 Windows Server 2008 does not support Type 2/Kernel Mode printer drivers. While the installation of WinFax (may) appear to complete under Windows 2008, the installation  will not include these printer drivers.  WinFax PRO is not compatible with this operating system.

FaxBack has recently released version 8.6 of NET SatisFAXtion server software.  WinFax PRO client support has been completely omitted in the documentation of versions 8.5 and 8.6. The last version that mentioned the ability to connect WinFax as a client was version 8.1. 

We couldn’t find any upgrade warnings in the 8.5 or 8.6 upgrade or administration documentation for users that could possibily upgrade only to find they now have a bunch of  client software that won’t connect to NET SatisFAXtion anymore.

It’s obvious that the WinFax client feature has been depreciated since version 8.1, but it’s possible that WinFax PRO clients are still “unofficially supported”  in versions 8.5 and 8.6 with use of the latest WinFax Connector.

If you have any additional details regarding compatibility with these versions please let us know.   We contacted FaxBack directly and received a reply that WinFax PRO connector had not been supported since version 8.0 (while we found a WinFax Connector update released about 2 years after the release of 8.0? and 8.1 mentions it in the documentation   )

So, we’re unsure about this and FaxBack hasn’t been helpful with an answer.  We do know that  NET SatisFAXtion version 8.0 will be retired December 31, 2009.

If you are experiencing errors installing the WinFax printer driver, such as Error Code ->1797 or Error Code->126 you may have problems with the WinFax driver files.

Symantec has a list of troubleshooting steps here, but we’ve found these are usually not always effective in solving this problem (and is very time consuming, a reinstall is usually not required). 

http://service1.symantec.com/SUPPORT/faxprod.nsf/docid/2002012814193804

Subscribers to our forums and download access to WinFax Tools can automatically check for these files and repair any errors automatically.

This error can be fixed in WinFax Tools by clicking on “Install & Setup Tools” and then, “Install Printer Driver”

Click here for more information on subscribing to WinFax Tools.

WinFax printer add failed. Error code ->1930

WinFax PRO and TalkWorks PRO requires a Windows compatible operating system such as Windows 9x, Windows NT, Windows 2000 and Windows XP, that will support Kernel Mode (Type 2) printer drivers. Microsoft VISTA and Windows 7 do not support Kernel Mode printer drivers.  While Windows 2003 does support kernel mode printers, they are blocked by default. Windows 2003 requires a policy change to allow for Kernel mode printer driver installation. You must disallow Kernel Mode blocking in Windows 2003 before you can install the WinFax printer drivers.

Our initial testing confirms that you can run WinFax PRO in Windows XP mode, but you cannot “share” the WinFax PRO printer driver with Windows 7 applications.  We successfully shared the fax modem, (and it was a software based modem!) but not the fax printer. This prevents any access from Windows 7 programs to the WinFax printer. Only the applications that are installed within the Windows XP Virtual machine can be used with WinFax to send faxes, you cannot create faxes from within Windows 7 applications. 

This limits the usability of WinFax in Windows 7.  if you require to fax from a Windows 7 application, it will not work.  Although, having Windows XP within your Windows 7 operating system saves you the expensive of having another separate computer just to run legacy Windows XP applications such as WinFax.

An alternative to WinFax PRO is FaxTalk FaxCenter Pro 7.5,  more details here: http://www.getfaxing.com

 More on Windows XP Mode.

Windows XP Mode is a feature that is optional on Professional, Ultimate and Enterprise versions of Windows 7. Windows XP Mode is not available in the Home Premium or Starter Editions of Windows 7. Windows XP Mode option can be downloaded at no additional charge with a qualified version of Windows 7 directly from Microsoft’s Web site here:

http://www.microsoft.com/windows/virtual-pc/download.aspx

In addition to the downloads, you’ll need a compatible processor and motherboard that supports hardware virtualization (AMD-V or Intel VT , also code named Vanderpool technology) . Microsoft has released a tool which you can download to test to see if your processor can support the AMD-V or Intel VT mode.  See Microsoft’s link above for more details.

More info on some compatible CPU’s in this post: http://www.getfaxing.com/forums/viewtopic.php?f=17&t=718

• Symantec never included the actual revision of WinFax PRO 10 (10.01,10.02 or 10.03)  on the CD ROM.  So, if your WinFax PRO CD ROM says “WinFax PRO 10.03″ its a fake. All genuine WinFax PRO 10 cd’s contain the heading ”WinFax PRO 10.0″
• If you see text with “winFAX” or “Live Update” anywhere on the CD its a fake.  The official Symantec trademarks are ”WinFax” and “LiveUpdate”, no other variations of this text should appear on the CD ROM.
• Failure to capitalize ”symantec” and “corporation”.
• An “All rights resverd” spelling error, or other spelling errors.
• Incorrect font used for WinFax PRO and Symantec logo. The current Symantec logo is consistant across all software they produce.
• Silver portion of CD is a (dull) matte finish, on the real CD it is relective (mirror surface).
• To determine if the CD is brand new and sealed – geniune WinFax PRO 10 CD’s come in a white envelope sleeve that are sealed with a sticker that may have one or more of the following: a bar code, a Symantec 5 or 6 digit product code, a brief license agreement. 
• In most cases, manufacturer information is printed on the inner rim of the CD ROM of genuine CD’s. This is usually missing on a counterfeit.
• Update patch 10.04 is not included on genuine CD ROMs. Any CD that contains the patch update to 10.04 is a counterfeit.

Example of a counterfeit CD ROM (left) and genuine WinFax PRO 10 CD ROM (right). Notice the differences in the mirror surface, the Symantec logo, and different font types. The counterfeit contains ”10.03″ version, something that is not printed on the genuine CD.  You’ll also probably see manufacturer information around the inner rim of the genuine CD ROM.  This is  likely to be missing on the counterfeit WinFax PRO CD.

Here is the original design of the CD ROM surface used for North American releases of WinFax PRO 10.0 and WinFax PRO 10.01. This has a different design with use of the older style Symantec logo. This image on the left is an example of a genuine WinFax PRO 10.0 or 10.01 CD ROM. Version 10.02 or 10.03 use the updated design & Symantec logo. It’s not known if any counterfeits exist, but a version 10.02 or 10.03/10.04 distributed with this design could indicate a counterfeit version. This design also uses a reflective mirror finish on portions of the CD ROM. Lack of reflective mirror finish would indicate a counterfeit CD.

• About.cfg
• ISUtil.dll
• UNINSTAL.DLL
• WFXCTL32.EXE (2 different versions depending on operating system)
• WFXRES32.DLL
• WFXIFWPP.DLL
• WPHOST.WPI

The update should only be applied to WinFax PRO 10.03 (North America) version, and is recommended only if you are using the Fax Sharing feature where one or more client(s) are using Windows XP.  

We do not recommend installing this patch for any other purpose, as it does not solve any other issues. If you’re having a problem with WinFax not related to fax sharing under Windows XP, then this update will not fix it. If you are using version 10.03 and do not use fax sharing, this update is not recommended. Do not install this update overtop any other version of WinFax, or any non-English language version of WinFax.

Symantec’s instructions to download and install WinFax PRO 10.04 update is available here: http://service1.symantec.com/SUPPORT/faxprod.nsf/docid/2004113014595304

WinFax PRO and TalkWorks PRO stores log records in the default Messages message store. A message store works like a filing cabinet with drawers that hold different types of files. For easy access, the Messages message store organizes your messages by placing them in one of four default folders:

• Send Log  Stores sent messages.
• Receive Log  Stores received messages.
• Outbox  Stores scheduled, held, and pending messages.
• Wastebasket  Stores deleted messages until you remove them manually or automatically.

Fax and voice log entries in the Messages message store are uncompressed; the Messages message store is therefore more suitable for short-term message storage or for storing a smaller number of messages. 

If you want to keep your messages for long-term use or you receive large numbers of messages, you can set up your own message filing system with custom message stores and subfolders. For example, you might want to organize correspondence by customer and your sales reports by quarter.

Versions of WinFax affected: Confirmed with all versions of WinFax PRO 9.0x, WinFax PRO 10.0x and TalkWorks PRO 3.0. This error only exists on a fax sharing client, when connecting to a fax host. 

This error occurs when a Fax Sharing client connects to a Host, and displays the Received Fax Dialog box.  This dialog box contains a selection list box from the Host computer containing the Fax Message information, including the number of pages, the Remote CSID, the type of message (fax or voice), and the date & time the message was received.   This data is stored internally as comma delimited format.  If a Remote CSID contains a comma, the list is becomes shifted and is positioned in the list box incorrectly. Lack of error conditions in this module causes the error message in to fault in module WFXIPWPP.DLL

Solution/Workaround:

To correct this problem, you need to view the Host receive log and examine any received faxes that have a Remote CSID that contain a comma.  You need to remove these specific faxes from the Receive log (either delete them, or move them into another folder). 

If these faxes are being received from within your own organization, you can prevent future occurances of this error by remove any comma’s from the CSID’s in the fax machines, or software that you use within your organization. Unfortunately, you cannot control other fax machines that you receive from, so any other fax machine you receive from with a comma is the CSID will trigger this error.

What is a Remote CSID (also called a TSID)? 

This is the data that the caller has entered in the fax machine, or fax software that identifies that specific fax machine. Usually, this information contains the fax number but sometimes can also contain a text message, like a company or department name.  If the CSID (or the TSID) contains a comma, this triggers the error in WinFax.  This is a flaw that was not fixed by Symantec, expecting that a CSID would never contain a comma.

We’ve been testing an on-line fax service for a few months now, and have found OneSuite.com to be reliable for incoming and outgoing faxes.  Get yourself your own fax number, from a selection of 16 U.S. states, with unlimited incoming fax pages.  Your faxes are then transmitted to you instantly to your e-mail address in a multi-page PDF format. Get started for as low as $1.00 a month for unlimited incoming fax service! and you can get started within minutes with a minimum pre-paid amount of $10.00 US Dollars. Use the link below to sign up, and get an additional 5% sign up bonus and your 1st month free!  https://www.onesuite.com/A96909221/suitetreat

If you want to be able to send and receive faxes, the service is $2.95 a month and includes unlimited incoming faxes.  Sent faxes are charged at a per page rate , in USA/Canada the current rate is 2.5 cents per page. 

No setup fees, no hidden fees, you pay for what you use and the monthly fee of only $2.95 for sending and receiving, or $1.00 a month for receiving only.  Each subscription plan includes your own fax number, with unlimited fax receive.

Use SuiteTreat promotion code : A96909221 to receive the 5% Bonus plus your 1st month free.

Situation: During the installation of WinFax, or when you reboot your computer, the WinFax PRO configuration wizard setup screen appears. When you are presented with the screen to enter your name, fax number and CSID, the screen disappears or the computer hangs/freezes. You cannot continue the setup, and you cannot start WinFax as the setup is not completed.

These steps apply to Windows XP with Service Pack 2 or Service Pack 3, and all versions of WinFax PRO and TalkWorks PRO.

Start WinFax Tools (The full version of WinFax Tools is provided to all paid subscribers to the WinFax Forums. Click here for Premium Subscription Information)

1. Click on Install & Setup Tools button.
2. Click on Fix Start Up Errors button.
3. Click YES, WinFax will automatically close if active.
4. Click OK to any messages that appear, until completed.
5. Click Fix Entry Problem on the Main WinFax Tools screen.
6. Follow the on screen instructions that appear.
7. Reboot computer when done.
8. If WinFax setup appears, continue with setup. If WinFax Setup does not automatically start, start WinFax Tools, click on Install & Setup Tools button, click Start WTNSETUP button & Continue the WinFax installation.

This is a common question that isn’t always easy to answer without more details on the specific fax pages you’re actually sending or receiving. There is a possibility that transmission errors  can cause pages to be re-transmitted, increasing the overall send and receive time.  In addition, there are compatibility issues with specific types of fax devices, where the maximum fax speed may be limited due to different fax specifications such as v.34, v.32bis and v.17 (more on this later.)

WinFax and the maximum fax transmission and reception speed.

The truth is, all fax transmissions are slow when compared with today’s high speed internet. The maximum speed you can receive and send with WinFax PRO is 14.4kbps (14,400bps), regardless of the type of fax modem you use.  This is a fax specification that is called v.17. You can send a 50 page Word document via e-mail in about a minute, while that same 50 page document would take almost an hour to fax using a v.17 fax.

Super G3 and v.34 fax

Some newer office fax machines support something called Super G3 (also called v.34bis), and an older fax standard called v.34, both with transmission speeds of 33.3kbps and 28.8kbps respectively.  However, most  consumer grade fax modems that you buy for your computer don’t support Super G3 or v.34.

Both Super G3 and v.34 fax are not supported by WinFax PRO, even if WinFax did support the newer Super G3 standard, chances are you don’t have the fax modem hardware to be able to take advantage of it. Super G3 is usually reserved for higher-priced office fax machines and higher-end fax modem cards.  Usually, large and medium sized businesses may have a Super G3 Fax machine, but many are still using fax machines and devices that support the older v.17 standard at 14,400bps.  About 3 out of 10 fax machines support the Super G3 specification.

If you use a Super G3 Fax, your maximum speed is 33.3kbps — that’s less throughput then standard telephone based dial-up internet access! Now that’s not so Super speed, but it does cut the transmission time in half when compared to v.17 fax. To see the benefits of a Super G3 Fax machine, you must communicate with another Super G3 Fax machine or compatible device.

The good news is its all compatible, so a Super G3 Fax Machine can talk with other types of fax machines, including a WinFax equipped computer. The lowest speed of the two machines fastest speed is the transmission speed that is set during the initial connection.

Average time to send or receive a fax page

The time it takes to send or receive a fax is based on the actual content of the fax, and how that fax is compressed during the transmission. On average, a single page will take approximately 1 minute to transmit at the WinFax maximum 14.4kbps speed (about 1/4 the speed of the fastest dial up modem internet connection).

That time will increase considerably if the fax image includes photographs, or complex images on the page. A fax with continuous white-space can be sent or received much faster when compared to faxes with a lot of text and graphics, usually a single fax page with a lot of white-space can be transmitted within 30 seconds.

How to speed it up

If you are concerned about the time it takes to send a fax. I recommend reducing the quality of the fax transmitted by sending pages in “Standard” or “Low” resolution. This can be configured in WinFax setup, under the Send options. This can reduce the sending time of faxes by as much as 50%, but the quality of the fax that is received on the other side suffers. If you use a Class 1 fax modem, you can also turn on the High Speed and 2D Compression options.  You do not have this option with a modem configured as a Class 2 or 2.0 fax modem in WinFax PRO.

When receiving faxes, you do not have control how they are received, if a fax is transmitted by the sender to you in high resolution, you will receive the fax in high resolution and it may take additional time to receive it. If two 14,400 bps machines are connecting, the entire fax transmission speed should be 14,400 bps unless there are some problems with the connection. Speeds such as 9,600 bps, 4,800 bps and 2,400 bps are also possible during error conditions. There are also 9,600 bps fax machines, so you may be receiving from an older fax machine where the maximum speed is 9,600 bps and it may be a normal condition.

Conclusion

Faxes are slow, regardless of the fax specification you’re using.  There is not much else you can do about this. Computers don’t normally come bundled with a fax modem that support Super G3, so you can’t take advantage of the speed increase unless you spend money on an expensive fax board and use software that will support the Super G3 specification.

At the time of the writing of this article, we found a reasonably priced hardware based internal PCI and PCI express fax modem that also supports Super G3, the MultiTech Multimodem ZXP.   Multitech has been in the fax modem business for many years, and are known for reliable products. They are one of the few manufacturers that produce an internal Super G3 fax modem.

If you use this fax modem with WinFax, it will not support the Super G3 fax setting, you will have to configure this fax modem as a Class 1, Class 2, or Class 2.0 fax device.

Information regarding use of WinFax with Microsoft Vista and Microsoft Windows 7 from the WinFax Forums:  http://www.getfaxing.com/forums/viewtopic.php?f=17&t=718

Technical article on Microsoft Vista and WinFax PRO: http://www.getfaxing.com/winfax/2008/11/29/winfax-pro-and-microsoft-vista-compatibility/

Technical article on Microsoft Windows 7 and WinFax PRO: http://www.getfaxing.com/winfax/2009/06/03/symantec-winfax-pro-and-microsoft-windows-7-compatibility/

Alternative to WinFax PRO is FaxTalk FaxCenter Pro 7.5, it is compatible with Windows 7 & VISTA. More details here: http://www.getfaxing.com

This is an error that causes an uninstall of WinFax PRO to fail.  This file is an uninstallation log file that is generated by a third party installation tool called Install Shield. Its automatically generated when you first installed WinFax PRO, so you won’t find this file on the WinFax PRO installation CD ROM. This log file contains all the information and settings that the uninstall program requires to remove WinFax, such as the program folder locations and features that you added or removed during the install process.

The problem is if you don’t have this file, or it is bad/corrupt, you won’t be able to successfully uninstall WinFax PRO.  The uninstall halts, and you can’t continue. You’re left with WinFax that may be partially installed.

Possible Solutions:

If you have an installation of WinFax on another working computer, you could copy the WFXUNIST.ISU to the computer where the problem is occuring.  However, both computers must be using the same folders and features.  If you installed the software in the same way on both machines, to the same folders, then this may  solve the problem.

The preferred solution is to reinstall WinFax PRO to the same installation folder, so the uninstall log file is recreated and any corrupt or missing files are recreated.  You should then be able to perform a proper uninstall after you’ve reinstalled successfully. We always recommend making a backup of your entire WinFax folder including any Data folders before attempting this if you require any WinFax information.

NOTE: WinFax PRO versions 10.02 and 10.03 also require that you must uninstall before you can reinstall the software, so the above method will not work for these versions as it will display a message that an existing version of WinFax is installed, and it will halt the install process. Since you can’t uninstall, you can’t reinstall.

If you are a premium support subscriber, we have our own tools available within our WinFax Tools program and in our premium download area to bypass this message and allow an install overtop the existing version.

Another option is to bypass the WinFax PRO uninstall completely and use the WinFax Clean utility, available in the Premium Downloads area. This program will completely remove WinFax and all related registry keys.

Symantec has released this document regarding this issue, and include a tool to remove WinFax and also steps for performing a manual (and tedious) uninstallation of WinFax.

This error message can be corrected with WinFax Tools.  Click “Install & Setup Tools”, then click “Fix Start Up Errors” option in WinFax Tools.

One of the main components of WinFax PRO is its printer driver, the printer driver allows you to fax from other applications. Without this driver, you cannot send faxes from other applications. WinFax PRO is crippled without the installation of the included printer (WinFax) driver, without it, all you can fax are single cover pages that are built into WinFax.

The first problem with installation of WinFax PRO under Windows 2003 is that the printer driver support in the operating system was moved from kernel to user mode. The reason is that the use of kernel mode printer drivers can possibily cause a server to hang, result in a blue screen and require a reboot. This isn’t something you want happening on a server. Because of this possibility, Microsoft decided to block the installation of all kernel mode printer drivers in Windows 2003.

During the installation of WinFax PRO, a kernel mode printer driver (also called version 2 printer driver) is added to your list of installed printers. By default, Windows 2003 won’t allow you to add this printer, and during the installation it is either ignored silently or a printer driver related error message is displayed.

Fortunately, in Windows 2003 you can bypass this restriction. You can set a group policy in Windows 2003 to allow the installation of kernel mode printers. Once you’ve done this, you should be able to successfully install WinFax PRO under Windows 2003.

Using Terminal Services / Remote Desktop Services with WinFax

One of the reasons of a Windows 2003 Server installation is because you can then use Terminal Services/Remote Desktop Services to have users connect remotely. We get a lot of requests regarding using WinFax with Terminal Services/Remote Desktop Services. This article may save you a lot of time and headaches.

Many printer drivers just don’t support terminal services (now called Remote Desktop Services), and WinFax PRO’s kernel mode drivers are no exception. If you attempt to print to the WinFax PRO printer driver, the output results will only appear on the console session (session 0), not the users remote connection. There is a document from Microsoft which explains how to shadow the console session 0 with a remote session here. Not a solution, but you can see what is going on here.

So the problem here is anyone using Remote Desktop Services trying to send a fax from their local machine are not going to see the WinFax Send screen asking them enter a fax number/name for the document they want to fax. While you could shadow the console session 0, its not always a good solution.

Alternative solution and sharing WinFax PRO with other clients

WinFax PRO includes a feature called Fax Sharing. It allows you to configure one computer to be a “WinFax Host”, and then you can connect (up to 25) other “WinFax clients” to it. The clients you connect don’t require a fax modem, they just require WinFax PRO to be installed on the local machine. Faxes are then routed to the Host from the client and are sent through the installed fax modem on the Windows 2003 server. Each client has its own send & receive log, and installed WinFax printer driver so everything is generated on the client computer. Remember that each client must be using an OS that WinFax can support, like Windows XP.

With Fax Sharing, you can configure the Windows 2003 machine as a WinFax Host. You can then install WinFax PRO on each user’s machine, and then connect to the Host. The Host machine doesn’t even need the have the WinFax PRO printer drivers, they are not required if all the faxes are going to be processed from the client machines print drivers. We’ve not experienced any problems with the WinFax PRO printer drivers, they are fairly stable, but if you don’t want to stay clear of Kernel mode drivers installed under Windows 2003, then you can remove them or just leave blocking of kernel mode printers on during the installation of WinFax.

I hope this article provides you a better understanding how WinFax interacts with Terminal Services/Remote Desktop Services, and some of the issues with using WinFax with Windows 2003 Server machines. There are of course other technical requirements when dealing with Fax Sharing and Windows XP SP2 or SP3 clients, which will be covered in another article.

Every so often, about once per week, we’ll be offering an eBay auction for our flat rate WinFax Remote Technical Support Service starting at an opening bid of only $24.95.  Here’s your chance to save up to $15.00 from our regular flat rate at $39.99. You’ll get the same great service at a reduced rate.

Go ahead and visit our eBay page for a listing of any current WinFax service offers we might have available :  http://shop.ebay.com/merchant/getfaxing

As this is an online auction and you’re be competing with other bidders, we can only offer the service after the auction is completed and if you are the final winning bidder.  While we don’t guarantee you’ll win at the final price at $24.95, we’ll guarantee you a final price lower then $39.99.  WinFax Fax Sharing and any development support is not included in this auction.

Need some support as soon as possible? order our service here http://www.getfaxing.com/services.htm

This error message, along with the “ WinFax is not active for this User Account. Please start the controller and try again.” error message are both related. They can only occur with version 10.02 and higher of WinFax PRO that is operating in the Windows XP environment.  This error does not appear under Windows 2000 or Windows 9x environments, or versions 10.0 or 10.01 of WinFax PRO. To determine the version of WinFax PRO you are using, click “WinFax Info” button in WinFax Tools.

This error message can occur when you are using the Windows XP Fast User Switching feature.  The reason these messages only appear under Windows XP and versions 10.02 and higher is because these versions included support for Windows XP and specifically checked for the use of the fast user switching feature under Windows XP. This feature allows you to switch between users that are logged into Windows XP, while keeping that users applications running in the background.

The problem is that if another user already has the WinFax Controller running in the background, you can’t start another WinFax instance from another users account. (If you could, it would mess up the database and probably cause data failure).  In this specific case, this message is normal. You can’t start another copy of WinFax if someone else is running it in the background.

While this is the most common situation where this message can appear, its also possible something else is wrong and you don’t use Windows XP Fast User Switching, or don’t even have other users logged into Windows. 

Usually, when you run into this message you may need to reboot of the computer. Its possible that specific WinFax PRO startup programs and service were closed down prematurely, or didn’t execute or startup properly under the current user.  A reboot of the computer should successfully restart these programs that WinFax requires to use.  If this does not solve the problem, then your installation of WinFax is likely corrupt and needs repair. 

If you continue to encounter this error we recommend using the “Fix Start Up Errors” option in WinFax Tools. ]]> http://www.getfaxing.com/winfax/2009/07/14/error-another-user-on-this-computer-is-using-winfax-please-try-again-later/feed/ 0