Route Command Directs Output to Stderr

Last reviewed: May 15, 1995
Article ID: Q130151

The information in this article applies to:

Microsoft Windows NT Workstation version 3.5
Microsoft Windows NT Server version 3.5

SYMPTOMS

When you use the ROUTE command, attempts to re-direct stdout fail. In addition, "ROUTE /? | MORE" fails to pause after each page.

CAUSE

The ROUTE command is writing output to stderr instead of stdout.

STATUS

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

WORKAROUND

Because stderr is defined as "2", the following command will work correctly:

   route /? 2>myfile.txt

This instructs the route command to redirect stderr to the file MYFILE.TXT. The file may then be viewed with Notepad or any other text editor.

KBCategory: kbnetwork
KBSubcategory: ntnetserv
Additional reference words: 3.50 prodnt standard in out

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 15, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.