I have a Win 3.1 modem app too. How does that complicate things?
The original COMM.DRV still exists, and if a Win 3.1 app opens a COM port through this device, TAPI won’t try to open it. You won’t have any of the TAPI benefits with this app, and you’ll have to manually configure its dialing properties, manually close it so other TAPI apps can use the modem, etc… Non-standard COMM.DRV replacements usually won’t interfere with TAPI, because TAPI does not refer to this device at all. In fact, there are separate VxDs and SERIALXX.DLL files (and the TAPI.DLLs of course) for 32-bit access to COM ports. The non-standard driver better not be calling un-supported stuff in Win95 though. In general, try to avoid Win 3.1 modem apps. As much as I lay the crap on WinFax Pro 7.0, for example, it’s a far better solution than WinFax Pro 4.0 for Win 3.1. Hold out as long as practical for Win95 voice mail apps too, so there’s no argument between non-standard apps trying to use the modem and conflicting with TAPI. Win95’s supposed to make using modems easier, and Win
