[Administrator]

you can try wiping out the attach.db file, sometimes corruption in the file causes attachments to fail. Also check the temporary attachments folder if you have one (within the attachments area in WinFax)

Here is how to reset the attach.db file ** note you will lose all attachments library information in WinFax when you do this ***

Rename the file Attach.db, then reconstruct the Attachments library as follows:

1. Exit WinFax and the Controller.
2. Click Start, point to Find, then click Files or Folders. The Find: All Files dialog box appears.
3. In the Named field enter ATTACH.DB.
4. In the Look In dropdown menu, select the drive on which WinFax or TalkWorks is installed.
5. Click ‘Find Now’.
6. Select the file, right click, then click Rename.
7. Rename ATTACH.DB to ATTACH.OLD, then press Enter.
8. Restart WinFax and relink all existing attachments back into WinFax.

[Administrator]

there is no real solution to this, because when you change the printer driver to WinFax, you are really changing the output to match 200×100 or 200×200 dpi resolution. If you have a 600dpi printer driver, and switch to the fax driver (200dpi) you will notice this change in formatting.

Once suggestion would be to set the driver to WinFax first, then create your document.

here are some things to check first:

page orientation in Word (for 8.5×11 faxing)
try sending to other fax machines (may be a problem with the machine you are sending to, or a problem with compatibility with your fax modem and the specific fax machine.)

[Administrator]

Microsoft has a solution for this

http://support.microsoft.com/support/kb/articles/Q165/8/60.ASP

[Administrator]

You need to have WinFax installed on each machine, or else none of the SDK objects get installed (therefore you will get the ActiveX error messages)

Eric

[Administrator]

printfromapp does not work with 10.02 under XP. This causes mail-merge to fail and anything else that uses printfromapp.

[Administrator]

I haven’t seen any modems that support Super G3 protocol, in fact, I don’t know of any software that supports it — so even if they had a modem, we would need software to support it.

[Administrator]

For whats its worth, I installed WinFax PRO 10.0 on a Windows XP machine and it seems to install and function perfectly. I don’t do any Outlook integration or have Office XP, so I don’t see those problems. Plus I only send maybe 1 or 2 faxes a week, so it would be unlikely to find a problem 🙂

[Administrator]

I sent you a private message about this with my configuration. I am using TalkWorks PRO 3.0 but it should be the same for WinFax 9.0 or 10.

[Administrator]

thats what I am using, the only difference is my Host is on Win98 and my client is W2k pro. It works well, and its TalkWorks PRO 3.0 too!

you might want to try shutting down other apps on the client machine when you try to connect. There might be a conflict with other software on the client.

[Administrator]

are these faxes that have been received from the host, or are they emailed faxes?

try opening the fax image in the viewer, then click Save As save the fax image overtop the existing fax image. If you have multiple pages, you have to do each page at a time. Now try printing the fax.

When you save the fax, it generates a new “header” within the fax image. If the original header was damaged in anyway, printing would fail (or be compressed etc.) by overwriting the fax image again, it will rewrite this header and you should be OK.

This is just a workaround, not a solution. If you continue to receive faxes and you can’t print them there is a problem on the receiving end. ( or a bug in WinFax)

[Administrator]

BTW Paul, were you at the new support site in Eugene before you quit?

Actually, I mean Springfield, OR. I was at the Eugene site a few years ago, nice building and city.

[Administrator]

If SDK is broken with XP, you’ll find a lot of problems with other software that links with WinFax too. Not good!

Maybe QA and Dev are working on that now? 🙂

BTW Paul, were you at the new support site in Eugene before you quit?

[Administrator]

that is possible, but usually the fax received and the OCR output are NEVER 100% accurate, unless the fax was sent by another PC and is using a simple font & design layout.
Also the OCR technology built into WinFax is a few years old (Xerox Textbridge)

[Administrator]

Hi DrT glad that worked out for you

[Administrator]

Quote: from darthphiber on 6:03 pm on Jan. 3, 2002
I recently migrated the network from 98 to 2000. all the clients and host are on w2k pro machines running winfax pro 10.0. In the morning when a client tries to connect to the host machine to pull the newly received faxes the client barfs and throws a wfxctl32.exe error and shuts winfax down. Only after I mark all the currently ‘new’ faxes as read can I then connect. None of the faxes are marked as having a problem with being received. I have spoken with Symantec who has suggested that I reinstall, which I have numerous times with the same results. Any suggestions would be greatly appreciated.

thank you

I have seen these problems with W2k and service packs for IE. Are you using IE 5.5? or 6.0? When I upgraded to Ie 5.5 I was having connect problems, once I downgraded to 5.0 all was working fine. I didn’t really do any further investigating on this problem, but you might want to consider it.
Also, when this happens you have to completely shut down the Host machine, and restart. You can then connect with the Clients.

Hope that helps

[Author]

Posts