🚀 go-pugleaf

> An addition to the following request:
>
Speaking of which, does anyone know how the TRSDOS system calls
(on disk, NOT the ROM calls) work? I've been going freaky trying
to get my program to simply copy from one file to another, later
to become a few filter routines. I've gotten as far as opening
both files (specified in the command line), checking the syntax,
reporting any errors that might occur, etc, but I have _not_
been able to even get a physical record into RAM.

Since the TRSDOS 1.3 manual doesn't have any sample programs that
are of any help, I decided to try to find the source code and
figure it out for myself.

Do any AL wizzes know how to do it? For my purposes, I am dealing
with physical records from the disk (not logical records), with
the LRL (logical record length) being 256 bytes (a disk sector).

Everything assembles just fine, with a clean exit to the DOS,
except that the newly-created file has nothing written out!

A "hunch" tells me that somehow the $POSN routine has to be called
after/before every $READ and/or $WRITE. Any clues???

By the way, if I get the basic filters working, I'd be glad to
share them on the net. As an enticement, think about using
Scripsit or SuperScripsit (ASCII file output) to edit a BASIC
file, EDTASM file, etc. Using BASIC to filter out a long file
takes just about years for a substantial file. I found out that's
the only way to mask out eighth_bits, entab/detab, and so on.
Doing it in AL will kill that time to practically nothing.

Like I said, just ask, and ye shall receive. For now, I guess I
have to do the asking...


	Usenet (UUCP) Address:
			   harvard!cmcl2\
		 {ihnp4 | seismo}!allegra>!phri!cooper!gene
				columbia/
				philabs/