WinFax PRO Support

You’ve upgraded to Office 2010 or Office 2007 and now third party Microsoft Office Add-ins or templates fail to run, this includes the FaxTalk Fax Merge Macro for Microsoft Word 2007 and 2010. You may see the following error message when you attempt to activate the macro.You have confirmed that your security settings are properly configured, however the macro does not run.

“The macro cannot be found or has been disabled because of your Macro security settings….”

additionally, one the following error messages might also appear:

“Word has encountered a problem.”

or, when attempting to compile a VBA project:

“Object library invalid or contains references to object definitions that could not be found.”

If you have determined that this error is not due to any security settings you have configured in Office 2010 or 2007 Trust Center, then you may need to delete some temporary .exd  files to correct this issue.

1. Close Microsoft Word (or other Microsoft Office product)
2. Click Start, and Run.  Then type
   %APPDATA%\MICROSOFT\FORMS
   and click OK. This will open the folder where these .exd files are located.
3. Locate any files with .exd extension and delete them.  These will be recreated as needed.
4. Restart Microsoft Word.

If all is well, no more  macro error messages!

NOTE: This fix may not apply to “Click-To-Run” versions of Office 2010.  Microsoft has acknowledged that some third party add-ins and templates will not function properly with “Click-To-Run” versions of Office 2010.

• Import WinFax PRO faxes and contacts. (*does not import WinFax cover pages)
• 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. (as PDF, TIFF or proprietary .FAX format)
• Operates as a network fax client for FaxTalk Multiline Server.
• Broadcast faxes to fax numbers and email addresses.
• Fax Merge with Microsoft Word using optional FaxTalk Merge Macro software.
• Block the reception of unwanted junk faxes.
• Developer Fax SDK to integrate FaxTalk with your custom software application.
• Voice mail and Fax back capability with a compatible voice modem using FaxTalk Messenger Pro 7.5 software.

Bundle with the FaxTalk Merge Macro for Microsoft Word

We offer a bundle package with FaxTalk Merge Macro for Microsoft Word.  Automate your faxing from Microsoft Word™ and FaxTalk FaxCenter Pro or FaxTalk Messenger Pro™. Fax broadcast from your Windows desktop by using the power of FaxTalk Fax Messenger and the FaxTalk Merge Macro for Microsoft Word. You can send faxes directly from Microsoft Word by clicking an icon. Select your prepared mail merge document with a data source, click on Send a Fax merge, select your recipients & optional cover sheet and click Merge. Send a few faxes or thousands of faxes, directly from Microsoft Word.

More info here http://www.getfaxing.com/faxtalk

Requirements:

• Compatible Windows operating system (Windows 7, Vista, 2008, 2003, XP, 2000)
• Compatible Class 1, 1.0, 2, 2.0, 2.1 fax modem.
• Compatible Voice/Fax Modem for FaxTalk Messenger Pro
• Microsoft Word XP/2003/2007/2010 for FaxTalk Fax Merge Macro option.
  

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.

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.

Notice to WinFax PRO users that are using WinFax PRO clients with NET SatisFAXtion server software and are considering upgrading to version 8.5 or 8.6.

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.

We do know that  NET SatisFAXtion version 8.0 will be retired December 31, 2009.

Unfortunately, like Microsoft Vista, Windows 7 is not compatible with WinFax PRO due to some of the changes made to the operating system.  With the release of Windows 7, Microsoft has acknowledged that many are still using legacy Windows XP applications, like WinFax PRO, and require a method to run these applications on a Windows 7 based PC.  A possible solution to run these legacy “XP” applications on your Windows 7 desktop is a feature that is available in some versions of Windows 7 called Windows XP Mode. 

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,  more details here

 More on Windows XP Mode with Windows 7.

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

Don’t get duped into buying a counterfeit WinFax PRO 10 CD ROM.  Here is how you can tell the difference from a “real” CD ROM and the obvious fakes. If you purchased your Symantec WinFax PRO with a box and manual, chances are it is the genuine item. If you purchased a “loose” CD ROM, usually referred as “OEM”, then you should check for the following:

• 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  and genuine WinFax PRO 10 CD ROM. 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.

This is a counterfeit poor quality copy of WinFax PRO 10.03 that appears to be created on a home deskjet printer. Note the non-reflective matte finish on the CD ROM.

 Here is the original design of the WnFax PRO 10 CD ROM used for North American releases of WinFax PRO 10.0 and WinFax PRO 10.01. This has a different design, yellow with silver (reflective) images.  This version uses 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. Symantec updated most of its design & software boxes when they changed logo designs. Version 10.02 and 10.03 use the updated design & Symantec logo. This design also uses a reflective mirror finish on portions of the CD ROM. Lack of reflective mirror finish would indicate a counterfeit CD, or a version with the 10.04 update included on the same install CD would indicate a counterfeit.

WinFax PRO 10.04 update is a patch file released from Symantec in 2005 that updates the Fax Sharing features of WinFax PRO.  After the patch is applied, the following WinFax PRO 10.03 files are updated in the WinFax installation folder:

• 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 does not use fixed TCP or UDP ports when using Fax or Message Sharing. Fax Sharing is accomplished using Microsoft DCOM technology. DCOM dynamically assigns one TCP port and one UDP port to each executable process serving DCOM objects on a computer. DCOM initially uses Port 135, once this connection is established, other ports are used. To ensure proper Fax Sharing, you need to ensure port 135 is not blocked and that wfxctl32.exe process is not blocked in your firewall or anti-virus settings.

Error: WFXCTL32.EXE caused an invalid page fault in module WFXIFWPP.DLL when connecting to a WinFax PRO or TalkWorks PRO Fax Sharing host.

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.

Your own dedicated incoming fax line for $1.00 a month ($12.00 a year)  Yes it is true. Forget those other services that charge $10 to $20 a month! Available in the USA and Canada!

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.

An ActiveX security flaw has been detected in the WinFax PRO Viewer Control. This bulletin applies to the following versions of WinFax:

• WinFax PRO 8.0x
• WinFax PRO 9.0x
• WinFax PRO 10.0x
• TalkWorks PRO 2.0x
• TalkWorks PRO 3.0
• WinFax Basic Edition (all versions)
• TalkWorks Basic Edition (all versions)
• Delrina Fax (French release, version 8.0x and above)

More details on this security flaw by clicking here

Symantec has released this official Security Bulletin for WinFax PRO, technical details can be found at Symantec’s Web site

If you use a Norton product for security, such as Norton 360 and Norton Internet Security 2009, this threat is detected with current definitions. Other security software from other vendors  may also detect this threat.

Regardless of the type of security you are using, We recommend setting the KillBit for this specific ActiveX control to always prevent it from activating. Setting this KillBit does NOT effect the normal operation of WinFax PRO. 

This is recommended if you have or do not have an installation of WinFax PRO.

If you have prior experience in setting a KillBit in the Windows registry, the CSLID for the WinFax PRO Viewer Control is {C05A1FBC-1413-11D1-B05F-00805F4945F6}

or, you can use our tool to do this for you, download our Free version of WinFax Tools.  Click “Fix Security DLL” button and the KillBit will be set automatically.

UPDATE: In a Windows XP update that was released February 9th, 2010, this security flaw was finally addressed. The actual update released by Microsoft is: Microsoft Security Bulletin MS10-008 – Critical Cumulative Security Update of ActiveX Kill Bits (978262).   If you have already downloaded this security update for Windows XP, then your system will already have the necessary ActiveX Kill bits set for the WinFax PRO ActiveX control.  You can still download WinFax Tools and confirm if the ActiveX kill bit was applied properly by this Windows XP Update. If your system has the Killbit set, the WinFax Tools program will indicate it has already been applied.

Why are faxes so slow to complete when sending or receiving?

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.) Read the rest of this entry »

WinFax PRO will support up to 2 modems on a single PC. If you need to have dual modems, I’d recommend ensuring both modems are different, otherwise, you may run into difficulties. Two external controller based modems are best, or one external controller-based and one internal controller-less. You can try two controller-less modems, but make sure they are different models/manufacturers. Never use two softmodem based modems on a single machine, you’re just asking for trouble.

When you reboot your computer, the WinFax PRO configuration wizard setup screen appears. You need to cancel or complete the setup to continue using the computer.  The next time you reboot the computer, this setup appears again. This error can be easily fixed with WinFax Tools. To repair this problem follow these steps: Read the rest of this entry »

If you’re experiencing problems with winfax where faxes are not displayed in your send dialog window, you will need to use the “WinFax No Pages fix” button in WinFax Tools.  This fix is for all versions of WinFax PRO 8,9,10 and TalkWorks PRO 2,3 that are using Windows NT, Windows 2000, Windows XP, or Windows 2003.  Read the rest of this entry »

Sometimes a fax can appear stuck or faxes fail to send when you submit them. This can be caused due to corruption in the default WinFax send, receive and outbox log.

Repairing a log or phonebook database in WinFax can now be accomplished with ease using WinFax Tools.

Before rebuilding any data in WinFax please backup your entire DATA folder (or entire WinFax folder) where all your WinFax files are located.  We recommend this in case of any failure during the rebuild/repair process.  If you’re not sure where your WinFax files are located, WinFax Tools can determine the location of your DATA folder for you, click on WinFax Info. Read the rest of this entry »

You may have a need for fax software and remember WinFax PRO from Symantec, or even remember “Delrina”, the company that started the faxing via computer craze.  Yes, fax is still alive and this software is still around and being used today!  Symantec discontinued the software back in 2006. The last version is WinFax PRO 10,  and Symantec  no longer sells it.  To purchase WinFax PRO, you’ll need to buy from a liquidator/distributor who has NOS (New Old Stock) on hand, or buy from a third-party 2nd hand.  Read the rest of this entry »

If you’ve sent a large number of faxes and you want to stop all of them, you can do a simple “HOLD ALL” in WinFax to stop the sending of all faxes in your outbox. Read the rest of this entry »

So you’re looking for fax software for your Windows based computer? WinFax PRO is a good choice, its the leading Windows desktop software for faxing and has been for over 15 years, it has many features, outstanding management capabilities, and is very easy to learn.

Here’s a Video of some of WinFax’s features.  It was incorrectly named Norton WinFax in the video, WinFax Features Video

Before you purchase WinFax PRO software (eBay is one source), I’d recommend you read the following guide, so you know what you are buying. Read the rest of this entry »

Many of you held off upgrading from XP to Vista are considering the upgrade to Microsoft’s latest operating system Windows 7, but are wondering if many of your existing applications such as WinFax PRO will work.

WinFax PRO and TalkWorks PRO (the fax/voice version of Symantec’s popular fax software) still have a strong user base and many of you don’t want to give up this powerful and easy to use desktop faxing software.

Unfortunately, Windows 7, doesn’t change the compatibility issues with WinFax PRO that were introduced with Microsoft Vista.  As expected, the same compatibility issues with WinFax PRO and TalkWorks PRO also exist with Windows 7. Read the rest of this entry »