NET Commands Don't Have Hex 0D at the End of Lines

 Last reviewed: June 6, 1995
Article ID: Q129849
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

If you run an application that reads in text files and depends on carriage return Hex 0D or CHR$(13) at the end of each line of text, the application may fail when it reads text files created from NET commands.

CAUSE

Windows NT 3.5 places only a linefeed Hex 0A, or CHR$(10), at the end of each line of text generated from the NET commands.

WORKAROUND

If possible, modify the application you are using to look for Hex 0A or CHR$(10) at the end of each line (instead of the Hex 0D or CHR$(13)).

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in Windows NT version 3.51.

KBCategory: kbother kbbug3.50 kbfix3.51
KBSubcategory: ntgeneral
Additional reference words: 3.50 prodnt command line eol eof end of line

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