[dr.rocket]

What modems are defined for each location? Try unchecking them if they are active elsewhere.

The only options for define Active device for location are Default or Dial as entered. Nothing is checked, but when I check the Standard 14400 bps modem I get the error message about 2 devices…

BTW, all the items in the Connection Device list are :
ISDN Device (CAPI 2.0)
WinFax PRO Fax Sharing
Concord Internet Fax
NetCentric Internet Fax

I’m at a loss for how to correct what is messed up. I can’t use WinFax for anything now, not even sending a fax. ;(

[dr.rocket]

A new wrinkle — I am unable to set the Standard 14400 modem as active (neither as TAPI nor as COM3). I get an error dialogue box stating, Only 2 devices requiring dialing rules may be active at a given location.

One step forward and two steps back. ;(

[dr.rocket]

I don’t know why WinFaxTools is reporting 10.0; I know at one point I was using WinFaxPRO 10.04. Maybe it used to display under Help/About Message Manager?

If you are using a serial modem, you should have a serial port on your PC. This can be accomplished by use of an add-on card with serial ports on them. Have you always been using this setup? Has it worked before with the same hardware configuration?

My current motherboard has no serial ports, but the USB–>Serial adapter hardware configuration did used to work well. I had reseached the adapters (I’ve tried 2 different ones — Belkin, Keyspan) prior to purchase, and they got good reviews. I’ll look to buy a serial port PCI card now if you think that is preferrable; but, like I said previously, it used to work with the USB–>Serial adapters.

Using the TAPI setting, the computer locked up during Answering. After rebooting, I got a dialogue box about applying Symantec KB-ID 200309015493306. A Google search revealed nothing about this KB. What’s it trying to fix?

[dr.rocket]

WinFax Tools reports:
WinFax About.Cfg Version : 10.0
WinFax About.Cfg Display Version : 10.0
WinFax registry version reported : 10.0

Program Path : C:WINFAX
Data/Fax default Path : c:WINFAXData
Cover Pages Path : c:WINFAXCover

Base Operating System : XP
Logged in as Administrator account : True

Wfxmnt40.dll: 2/14/2000 4:36:18 PM Size: 131072
Wfxmnthq.dll: 2/14/2000 4:36:20 PM Size: 132608
Wfxsnt40.exe: 2/14/2000 4:36:22 PM Size: 43008

No mention is made about the 10.04 update.

Under known running fax tasks:
wfxsnt40.exe
WinFaxTools130.exe

No other fax software is running or waiting for calls.
It is a dedicated POTS phone line.
The dialogue box says “Answering…” very briefly, then disconnects. It never gets to Negotiating or Training.

The modem is hooked up correctly.
The motherboard does not have any serial ports, so a Serial –> USB adapter is being used.

Device Manager is not showing COM2 at all, just COMs 1,3,5,6; if I recall correctly, the UPS monitor is on COM2.
Device Manager is not seeing my Practical Peripherals modem, and WinFaxPRO keeps clearing the checkbox so no Active modem is found, even though the Practical Peripherals is listed (–it’s listed but not checked in WinFax; it’s not even listed in Device Manager).

Why is WinFaxPRO not saving the Practical Peripherals as an active modem?

[dr.rocket]

I was mistaken about WinFax not waiting until after the 2nd ring to answer. It does seem to be answering after whatever number of rings is specified, but then it quickly disconnects without any data transfer.

[dr.rocket]

check the maximum transmission speed in the modem properties (in WinFax) it should be set to 14,400 or As Fast As Possible.

It is set to As Fast As Possible. But I still get the warning that no Active modem is selected!

Check your Send / Receive limits count using WinFax Tools. If your receive log is over 50% capacity it could cause receive problems. Check under Logs & Phonebooks, Check Send/Rec Limits button. What does it report here?

Your default send log folder is 5% full.
Your default receive log folder is 2% full.

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

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

[dr.rocket]

I followed your instructions multiple times, but to no avail. While it now has Practical Peripherals PM14400FXSA listed as the modem (instead of Standard 14400), the receive behavior has not changed — it still picks up on the first ring, says Answering, and then the dialogue box disappears. ;(

A new wrinkle is that now when I choose Modems and Communications Devices inside Program Setup, I get a warning that there is NO active modem! No matter how many times I have checked the Practical Peripherals box, hit Apply, then hit Close, when I go back to verify, no modem is designated as Active.

Another observation is that when the Active modem was set to Standard 14400 modem, the sending speed to HP Fax Back Testing Service was 14400; but with the Practical Peripherals setting, the sending speed has been defaulting to 9600. Why did that happen?

This problem-solving exercise is starting to feel like, One step forward and two steps back. I eagerly await your next instructions.

[dr.rocket]

No, it doesn’t answer when auto-receive is off. It was when I then clicked Manual Receive now that the call got answered immediately, then dropped. In either scenario (Auto-receive on, or Manual Receive Now), when attempting to receive an incoming fax, the WinFax dialogue box says Answering and then the box disappears.

[dr.rocket]

I tried your suggestions, but nothing has changed. WinFax still answers on the first ring and then disconnects. Even with Manual Receive Now, the call is answered immediately and then dropped. What esle can I try?

Thanks for your help.

[dr.rocket]

The problem appears to be an issue with the number-of-rings setting; it’s not taking effect. Despite having it set to 2-rings, or even 3-rings, for some some reason WinFax is answering immediately on the first ring, then disconnecting. This had never been a problem before. I don’t know what is suddenly preventing the ring-number setting from working. Could it have been a Win XP update?

Thanks for any instructions as to how to resolve this issue.

[dr.rocket]

Oops, I celebrated too soon. Although my computer no longer locks up when receiving a fax, it appears the connection is being terminated before any info is transferred (the Connecting dialogue box displays only briefly, and no fax is ultimately displayed in the Receive log). Could a recent Win XP update have broken WinFax yet again? Any idea what I should try next in order to successfully receive a fax?

Thanks in advance.

[dr.rocket]

Woohoo!! The critical fix was changing the modem’s Communications Port setting from TAPI to COM3. Now everything appears to be working properly.

Thank you so much. 😀

[Author]

Posts