Avoiding Common INF Item Problems

• INF responses within an INF must be accurate and comprehensive for the modem. For example, an incomplete response such as "CONNECT 14400" instead of "CONNECT 14400" will cause a failure. If MCT fails to run to completion and you have not already enabled logging of modem events, then enable modem event logging and rerun the MCT. Study the log entries for bad or incomplete responses such as the example incomplete response shown previously. Complete instructions for enabling logging of modem events is in Full Debugging of a Modem INF File Using Modem Event Logs.
• A common modem INF syntax mistake is to include \ (backslash) or other prohibited characters in a modem's name within the Strings section of the INF.
• A common INF mistake is an incorrect init string applied to all modems. For example one of your modems may require AT&F1 instead of AT&F. Perhaps one of your modems uses \Tn for inactivity timer instead of S30. Make sure you are using a fully robust init string. An example of a fully-robust init string is AT&FE0&C1&D2S95=47. An example of a nonrobust init string is AT&FE0.
• If you suspect that your INF numeric response section is incorrect, consider switching to verbose responses.