[shrumishi]

Nope, no send fax dialog at all when manually printing to either Winfax printer from an app.

Dale.

[shrumishi]

Thanks for the pointer. Don’t know why that didn’t come up in my initial forum search.

Can you believe that now I have almost the exact opposite problem?

I’ve got the drivers installed, but when I use the SDK, either COM or DDE, to print from an app, the print job goes through the print queue but never gets to the fax outbox. As a test, I tried to manually print to the WinFax printer and the same thing happened. The Send Fax Wizard never came up to prompt me for where to send it.

So I think that I am still missing something in my install. Any ideas?

Dale.

[shrumishi]

After looking for this all day, I finally figured it out. (I think).

The Send Fax Wizard that is showing up is actually from the OS Faxing Service, not from Winfax. During installation of Winfax 10.03, the Winfax printer drivers failed, but wasn’t noticed. When a coworker went to manually add the Winfax printer driver, they wound up selecting the default Microsoft faxing service driver instead. So when the call would go out to print to the printer named “Winfax”, it wouldn’t even go to the Winfax software.

Trying to manually install the Winfax printer drivers failed, even running INSPRINT.EXE. The Event Viewer gives the reason, “Kernel Mode Printer blocking policy is enabled. The attempt for WinFax to use a Kernel Mode driver failed.” Disabling the “Disallow installation of printers using kernel-mode drivers” policy in local computer policy allowed the installation to complete.

Whew.

Dale.

[Author]

Posts