Thanks Willard, I'll take a look at that when I get home. I was testing last night and I think this may be a TS-DOS issue as well. If I write to a file on a TPDD device one byte at a time, no data is written until I get to the 129th byte. Which would indicate 128 bytes is the buffer size and going over that forces TS-DOS to write the buffer and clear it. But that may just be TS-DOS and not RAM or CAS files. I'll keep digging but your info should definitely help. Kurt
On Mon, Nov 26, 2018, at 9:52 PM, Willard Goosey wrote: > On Mon, 26 Nov 2018 14:44:44 -0800 > Kurt McCullum <[email protected]> wrote: > >> When opening a file in BASIC, a file buffer gets created. Does anyone>> >> happen to know the size of each file buffer? I can't seem to >> find that>> in any of the manuals. >> Kurt > > I believe you mean this... > > /* from covington map... > * - File Descriptor Block (Address Given by VARPTR(#file)) Format - > * > *Byte: > * 0 - File status (0-not open, 1-open for input, 2 open for > * output or append) > * 2 & 3 - Address of file directory entry > * 4 - File device (248-RAM, 249-MoDeM, 250-LinePrinTer, > * 251-WAND, 252-COM, 253-CASsette, 254-CRT, 255-LCD) > * 6 - Offset from buffer start (see bytes 9) for start of next > record > * 7 & 8 - Relative position of next 256 byte block from beginning of > file > * 9 - Start of 256 byte buffer for data transfer > */ > > > Willard > -- > Willard Goosey [email protected] > Socorro, New Mexico, USA > I search my heart and find Cimmeria, land of Darkness and the Night. > -- R.E. Howard
