Re: EOF location?

I did. Some files include the X'1A' byte as part of the recorded file
length, some don't. That's the confusion.

You are only confused in thinking that x'1A' has any significance to
MS-DOS/Windows, it neither knows nor cares whether a file has one or
not. Actually Windows/DOS does not care about CR/LF in disk files
either, the console does action various control characters though so
copying a file to the console shows the file in lines.

It may be relevant whether a particular program thinks that x'1a' does
end the file, but only where there are significant characters beyond
that.

The x'1a's found in some files are likely to be the remnants of using
old DOS editors, possibly ones originally designed for CP/M where the
x'1a' is useful. Strip them all out and forget about it.

.

Relevant Pages

  • Re: How get to OK-prompt via serial terminal?
    ... > should be equivalent to stop-a on the console, ... Another possibility is confusion due to a .uk keyboard ...
    (comp.sys.sun.admin)
  • Re: [PATCH] Input: Support for a less exclusive grab.
    ... text console. ... The current solution sucks for things like rfkill. ... I'm not convinced that Ryan's fix is any better, but just saying that X ... A 'filter' cares about a key or two, and might even want to remove it ...
    (Linux-Kernel)
  • Re: Birthday cake
    ... And it avoids ... confusion, naturally. ... What was it you were harassing Ray about? ... as if you believe anyone really cares. ...
    (rec.arts.bodyart)