Using the Terminal Application as a Debugging Aid

You can use TERMINAL.EXE from Windows 3.1 for simple init and AT command debugging. This is useful if a modem event log file indicates an error immediately after a specific init or command.

1. Copy the program TERMINAL.EXE from Windows 3.1 to your computer (if not already present).
2. Close MCT if it is running.
3. Set up Terminal to access the modem.
4. Issue various AT commands until you find one or more commands which do not produce an OK response in Terminal.
5. Modify these commands in your INF, or remove them from the INF entirely.
6. Uninstall the modem from the Control Panel and reinstall it again so the newly modified INF is in use.
7. Rerun the MCT.

Another debugging shortcut is to cut and paste, through the Windows clipboard, init strings from an INF into Terminal and then connect to a slave modem to see what verbose or numeric responses you receive.