How are you looking at the result file? If HexEdit is showing you only those 6 bytes then that is all that is really in the file. Most text editing programs will interpret 0x0A as an end of line character with or without as 0x0D next to it.

>I am writing to a binary data stream using CHR(#). ie lcdata = CHR(1) + CHR(10) + CHR(12). When the number 10 comes up I output CHR(10). When I look at the file there is a CHR(13) directly in front of the CHR(10). Anyone know how to prevent this from happening?
>
>I am running VFP6 on NT.
>
>Another person and I ran the following test:
>
>>>n=fcreate("test.tmp")
>>>?fwrite(n,chr(1))
>>>?fwrite(n,chr(10))
>>>?fwrite(n,chr(12))
>>>?fwrite(n,chr(1))
>>>?fwrite(n,chr(10))
>>>?fwrite(n,chr(12))
>>>?fclose(n)
>>>do sys(2004)+"tools\hexedit\hexedit" with "test.tmp"
>>>
>>>HexEdit shows only 6 bytes in the file:
>>>0x01 0x0A 0x0C 0x01 0x0A 0x0C
>
>This is what I have after running the same test test:
>
>0x01 0x0D 0x0A 0x0C 0x01 0x0D 0x0A 0x0C
>
>I looked through options, SYS commands and SET commands and didn't find anything related to carridge returns with line feeds that could be causing this problem.
>
>Any suggestions or ideas?