Groups | Search | Server Info | Login | Register
| Date | 2025-07-23 12:06 +1000 |
|---|---|
| Subject | Re: Transferring text files to CP/M ? |
| Newsgroups | comp.os.cpm |
| References | <687f914f$1@news.ausics.net> <1854a6b2e7fe52fd$82327$1040375$70dd3a6b@news.thundernews.com> |
| From | dxf <dxforth@gmail.com> |
| Message-ID | <688043ab$1@news.ausics.net> (permalink) |
| Organization | Ausics - https://newsgroups.ausics.net |
On 23/07/2025 4:37 am, John wrote: > > A properly written program will stop at the EOF marker ($1A), so there is no need to pad additional $1As after the first one. All that data is 'don't care' mode as it will never be processed. That's the way I've always done it. > ... I think I'll do that from now on. Padding the file length out to a record was done out of an abundance of caution. But if nobody else has found it necessary, then it's less work for me. I had a utility to pad files but being an extra step, it was more hassle than worth.
Back to comp.os.cpm | Previous | Next — Previous in thread | Next in thread | Find similar
Transferring text files to CP/M ? dxf <dxforth@gmail.com> - 2025-07-22 23:25 +1000
Re: Transferring text files to CP/M ? John <john@somewhere> - 2025-07-22 13:37 -0500
Re: Transferring text files to CP/M ? dxf <dxforth@gmail.com> - 2025-07-23 12:06 +1000
Re: Transferring text files to CP/M ? Nils M Holm <nmh@sraddha.invalid> - 2025-07-23 09:14 +0000
csiph-web