Remote Access Error 661: Modem.inf COMMAND

 Last reviewed: May 12, 1997
Article ID: Q107061
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

After you edit Windows NT Remote Access MODEM.INF, PAD.INF, or SWITCH.INF file, you receive the following error message: 

   Error 661: The device .INF file is missing a command.

CAUSE

The "command" and "command_init" line in the .INF files must be in all uppercase. If they are written lowercase or mixed case, you will receive the above error message.

RESOLUTION

All command lines in MODEM.INF, PAD.INF, and SWITCH.INF should be in all uppercase. They must be listed as "COMMAND" and "COMMAND_INIT" exactly.

Usually, Windows NT configuration files are not case-sensitive. No other commands lines in the RAS .INF files are case sensitive. However, as a precaution, you should specify all your RAS commands in upper case.

STATUS

Microsoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prodnt
Keywords : kbbug3.10 kbnetwork ntras NTSrvWkst
Version : 3.1
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.