[Administrator]

TalkWorks is installed with WinFax PRO 8 if you selected the option (i believe Typical or Full install) option during installation .
You need a compatible voice modem for this feature to work. It was designed for Windows 95 and Windows NT 4.0, so it may not work with Windows XP. The only version I am aware that will work with Windows XP is TalkWorks PRO 3.0 .

[Administrator]

Simply, TAPI mode allows you to share the modem with other communication programs. This feature is of no use if WinFax is the only communication program that uses the fax modem on the computer. So for most purposes, you’ll see no difference between choosing TAPI or COM port mode. You can try selecting the actual COM port where the modem is installed instead of TAPI to see if the problem is avoided.

[Administrator]

you can change the Com port in the Advanced Port Settings in the Modem Properties.
I don’t recall the steps in Windows 2000, but they should be similar to Windows XP as outlined here:
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/mode_changecomport.mspx?mfr=true

There are two ways to communicate with a modem in Windows. Using TAPI (using the Windows OS) or directly using COM port mode. You can try changing the TAPI/COM settings in WinFax from TAPI to the specific com port. This doesn’t change the com port where your modem is installed, it just tells WinFax to communicate with the fax modem using the com port directly (do not use the Windows TAPI method). The com port you select must be where your modem is installed or WinFax will display “cannot communicate with modem” error messages.

[Administrator]

USR’s web site for support is here:
http://www.usr.com/en/support/

You can determine your model # by following these instructions
http://www.usr.com/en/support/support-101?cat=int56k#findcode
If these are older models, they might be listed under the Legacy Products / Internal Analog Modems or OEM Modems if the modem was bundled with a computer.

and from there, you can determine what drivers are required and if they are hardware based/controllerless or software modems.

If com3 is available, it is preferred to have the modem on com 3 instead of com 4. The IRQ should be automatically selected for you, and it should not conflict with any other device installed in your system. Also, the motherboard bios can also limit specific IRQs for specific PCI slots on the motherboard, so which slot the modem is inserted into can limit the IRQ that will be assigned to it. The most common (manual) assignment for COM3 is IRQ 5 (assuming you don’t use a 2nd Printer Port (LPT2) – that is reserved for IRQ 5).

[Administrator]

Are both these computers setup as WinFax Host machines? Do the versions match for each system? And, what version are you using?

Crashing when you try to open the modem setup indicates some sort of modem issue. You should see if Control Panel in Windows detects and is able to query the modem from within the Modem/Phone options in Control Panel. Those 2 USR modems may be “software” modems. You might want to try replacing them with a different model modem, or make sure you have the updated drivers for them installed for the OS you are using (Windows 2000) You can also try changing the modem com port to 3 if it is available to you. Devices active/conflicts with other com ports can cause WinFax to crash/hang. If you have a screen saver, or power saving features turned on in Windows 2000 you should turn them off.

[Administrator]

start WinFax PRO Manager, click the Outbox folder. In the list, you should see the fax. Right click the fax, click “Send Now”

[Administrator]

click WinFax Service Options – disable the WinFax Service and the Windows Fax Service.
click Logs and Phonebooks, Check send/rec limits in WinFax Tools. Report the Receive Log status
also in Logs and Phonebooks, Click Call Logging Options. Uncheck both options here (if checked), if unchecked (try checking both). Click Apply, then OK.
also in Logs and Phonebooks, click Rebuild Logs & Phonebooks, Select the “status.wfb” file and click Open to start the rebuild process.
Exit from Logs and Phonebooks.
Click Start Controller button to start WinFax.

[Administrator]

your e-mail provider is blocking delivery of the message.You can try using a different e-mail address — gmail, yahoo, comcast, hotmail accounts usually have this problem.

[Administrator]

was WinFax attempting to answer an incoming fax or voice call when it failed?
What type of fax modem (model) are you using? and it support voice features?
Do any of the WinFax PRO processes show “Not Responding” – If you display the Task Manager when in a hung state, with Windows 2000 it should display processes wfxctl32.exe, faxmng32.exe (if WinFax Fax Manager is active) , wfxmod32.exe, and wfxsnt.exe ) wfxsvc.exe may be present if you are using the WinFax Service

[Administrator]

The Backup program that is included with WinFax PRO? If you use that, don’t rely on it as your sole backup method for WinFax PRO. It is unreliable when dealing with large volume of files, and sometimes can fail to do a complete backup. In addition to using WinFax Backup, you should always backup the entire “C:Program FilesWinFax” and sub folders manually or by using an automated software backup tool.

[Administrator]

This is the process we use to repair this problem. It is a tedious and manual process, it will allow you to open WinFax PRO and clean up your send log. if you don’t care much of the faxes or data you can skip the back up copy of the WinFax folder.

Step 1 – close WinFax processes and make a backup copy of the WinFax folder.

As a precaution , you should first make a backup of your c:program fileswinfax folder. To do this. you should first close/shut down all active WinFax processes, this can be done by clicking “End all WinFax Tasks” in WinFax Tools. The WinFax Tools window will show active WinFax processes when you press “refresh” (some possible WinFax active processes include: wfxmod32.exe, wfxsvc.exe, wfxctl32.exe, faxmng32.exe, wfxsnt40.exe, and wfxswtch.exe ) . wfxsnt40.exe is optional, it can be left active and running.

Once the WinFax processes are shut down (only wfxsnt40.exe of the 6 WinFax processes can be active, everything else should be closed) , Copy the “Program FilesWinFax” folder using Windows Explorer. DO NOT MOVE the folder, only copy it to another location. This may take a while as you’ll have at least 10,000 individual files to copy from the Program FilesWinFaxData folder.
Leave WinFax Tools open, as you will need this later.

Step 2 – Open the Program FilesWinFaxData folder in Windows Explorer and search for “FXD” files.
You need to open the folder where your WinFax Data is located using Windows Explorer. This is in “C:Program FilesWinFaxData”
In this folder you’ll have thousands of files, you should sort the files as follows: By Type and By Date. Take note of the “FXD” files and their dates, these are the only files you should be concerned about.

Step 3 – Create a new temporary folder to store older “FXD” files.
Create a new folder somewhere on your hard drive so you can store(move) these older “FXD” files. This is a temporary storage location, as you’ll need move these files back to the Program FilesWinFaxData folder.
You can name the folder “FXD Files”

Step 4 – Move (not copy) the older FXD files from (Step 2) to the folder you created in (Step 3.). Repeat this step for as many older FXD files you can. Move only FXD files. You probably want to start from the oldest FXD files and work from there. You’ll notice that FXD files contain a series of numbers along with FXD extension name. For example. 0033001.FXD, 0033002.FXD, 0033003.FXD, 0033004.FXD … The last 3 numbers are the page number (001, 002, 003, 004) so this is a 4 page fax. So you should move them in set groups, and a few hundred or so at a time. The goal here is that you need to move enough FXD files out of the “C:Program FIlesWinFaxData” folder into this new temporary folder you created. Once you’ve moved enough (you probably have to move at least 2000-3000 of them)
Do a check using WinFax Tools (Check Send/Rec Limits) from Logs & Phonebooks button. Once your send logs shows 50% or less usage you can STOP moving the FXD files.

Step 5 – You now have to close down any open Windows explorer windows, this is important that no WinFax folders are open. Now use WinFax Tools ONLY to start WinFax again. Click the “Start Controller” button and wait for the controller to appear in the taskbar. Then click on “Start Fax Manager” to start the WinFax Fax Manager. WinFax Fax Messanger should now open, and your send log should now be visible. You should be able to use WinFax normally now .

Step 6 – The next step requires you to MOVE the “FXD” files that you copied into your temporary storage location back into the “C:Program FilesWinFaxData” folder. You have to do this while WinFax is open and active.

Step 7 – Now you can start deleting faxes that are no longer required from your WinFax Send Log. You’ll have to manually go through the faxes from the send log from within WinFax to do this. Only do this after you moved all the FXD files back to the C:Program FilesWinFaxData” folder. Use WinFax Tools Check Send/Rec Limits to verify the percentage used. Do not close WinFax! Once you are back to 50% or less, then the problem should be resolved. IF YOU shut down WinFax PRO before deleting the appropriate amount of faxes from within WinFax you will not be able to start WinFax again, and you’ll be back to the original problem.

[Administrator]

@Elliot wrote:

One other diagnostic fact. My feature to print a document through my Epson printer/fax also is not working. It is telling me that there is a communication error. That did not cause the WinFax problem. I only tried to use because WinFax is down. The printer/fax is printing fine and faxing out paper documents just fine.

Thanks,
~ Elliot

Not familiar with the Epson, but I would guess the error is not related to WinFax .

[Administrator]

@Elliot wrote:

Dear Moderator,
WinFax opens up and then hangs up. I have already used WinFax Tools to rebuild the logs.

Here are the stats when I check limits:
Your default send log folder is 76% full.
Your default receive log folder is 10% full.

WARNING: Your send log folder is 76% full.
You should consider moving faxes or deleting older faxes.

Received Fax (*.FXR files) slots available (Maximum of 10,000) : 8909
Send Fax slots (.FXD Files) available (Maximum of 10,000) : 2399

Cover Page Text files (*.CVR files) total count is : 1485

I would clean up my send log if I could get into it.

Thanks for your help,
~ Elliot

72% usage of the send log could be the problem, but before that can be fixed you should do these steps first:

Click on “Set Default Fax View” button in WinFax Tools . This will set WinFax to the default info view settings. Sometimes if you receive a corrupt fax and have WinFax set to automatically display the image, it can crash — preventing you from opening WinFax PRO. This button will switch the view back to Info only, so you can open WinFax. If this allows you to open WinFax, then it is likely that you have a bad/corrupt fax in your send, receive log or outbox. You need to determine which one it is and delete/remove it, and it was probably the last fax you received, opened or sent.

If this does not solve the problem, then the next step is to make sure you apply the “Move/Copy Logs Disk Space Error” patch by clicking this button found in the “Logs & Phonebooks” area of WinFax Tools.

Also, make sure that the “WinFax Service” is disabled. Do this by clicking the WinFax Service Options button and click the “Disable” button. You can also disable the Windows Fax Service, if that is active.

Now click “WinFax Info” , then click “Yes” to show more information. Copy and paste that information to your next reply.

[Administrator]

Can you provide more details? Can you open WinFax? Is the problem sending the fax or preparing the fax?

[Administrator]

Zoom External which model? is it a serial or USB modem? What com port / IRQ setting is it connected to? Are you using TAPI settings or COM port settings in WinFax PRO?

[Author]

Posts