Problem: Some fax software prevents the successful use of EZ-Remote. Listed below are a couple of known problems related to fax software and suggestions for resolving the trouble.

Solution:

If a fax modem seems to be setup correctly but gives a busy signal instead of a dial tone when trying to use it and/or it sometimes fails to report "no carrier" if it is not plugged in, the problem may be related to the fax software:

• Check the boot section of the SYSTEM.INI file for a line which says "comm.drv=flxcomm.drv". Look for it by going to Start | Find | Files or Folders , and typing in "system.ini" in the "named" field, and then hitting "enter". The file will be in the lower screen. Double-click on it to open it.
• Change the "comm.drv=flxcomm.drv" line to "comm.drv=comm.drv"
• Copy the "comm.drv" file from someone else's computer to your c:\windows\system directory if it's not already there.
• Restart your computer after saving the edited SYSTEM.INI file.

If you need a copy of the "comm.drv" file, the HelpDesk can supply you with one via e-mail or if you bring a diskette in on which to copy it.

When it seems like a defective modem and nothing else works, check the SYSTEM.INI file to ensure that some fax installation program didn't replace the default comm.drv with something incompatible with EZ Remote.

It appears that WP6.0 for DOS comes with some fax software that loads a device driver that grabs the comm port and won't allow people to use it while running Windows. The key to the problem is the existence of the following two lines in the AUTOEXEC.BAT file c:\wp60\faxdir.exe and c:\wp60\faxb.com. If these lines exist, then there may be trouble using Windows Bear Access via EZ Remote. We therefore recommend that they be removed.