From: "Daniel H. Luecking" 
On Sat, 7 Feb 1998, Dom Ciccotto wrote:
> I found the  saved  copy to be 2 bytes larger and slightly different.
> I viewed this file along side of a known good file, using TSE32 in hex
> mode and found no
> changes.  I then used a copy of   Norton's  Disk Edit   (  DiskEdit.exe
> )  and found the
> following :    Starting in the 8th position ( in HEX ) I had.
> 
>                 77   0A   E5              (Good File starting in 8th
> position)
> 
>                 77   0D   0A   E5      ( Bad File  starting in 8th
> position)
> 
> Questions:
>        1)  WHAT IS   0D  (in HEX)
It is a carriage return (CR), ctrl-M. The combination 0D 0A (CR-LF) 
is a line end in DOS, and is normally not displayed. Open the file in
binary mode to see them. A single 0A denotes a line end for text files
in UNIX. TSE will normally convert one to the other, but there seems to
be a configuration option (or editor variable) to change that behavior.
>        2)   How come it can't be seen in  TSE32 (Hex mode).
I guess it is a choice: should EOL's be shown in hex view when not in
binary mode. They _can_ be seen in binary mode (in my configuration,
which I don't think is any different from TSE as delivered).
>        3)   How can it be removed using TSE32.
Open in binary mode. You can combine binary mode with hex view. In one
window you see whatever is in position 13 in the screen font, in the hex
window you see the corresponding hex. I usually use 16 for binary line
width, so the display looks similar to standard hex listings (as in
list, for example).
Dan Luecking                           Dept. of Mathematical Sciences     
luecking@comp.uark.edu                 University of Arkansas      
http://comp.uark.edu/~luecking/        Fayetteville, AR 72101
---
---------------