Microsoft KB Archive/129849

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

Article ID: 129849

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Server 3.5

-



This article was previously published under Q129849



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.

Additional query words: 3.50 prodnt command line eol eof end of

Keywords: KB129849

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.