Thanks Steve. I'm curious if you'd experience the same exact issue. I suspect everyone would, and the confirmation that it isn't unique to my setup would be great.
One scenario would be to a DOS-ON based "Load 0:" of a .DO form of a huge basic program from BASIC which will tokenize it on the way in, and then try to do a "Save 0:FILE.BA" from there, and see that only 20480 bytes are present on disk in your ROOT folder on the host machine. And then if you can confirm that the Close opcode isn't getting sent when the Save completes, then we have our culprit. On Fri, May 21, 2021 at 5:02 PM Stephen Adolph <twospru...@gmail.com> wrote: > I think I just made a testbed for that. > Happy to set up and capture traces > > On Friday, May 21, 2021, Gary Weber <g...@web8201.com> wrote: > >> Yeah, that's interesting. Suppose we could "sniff" what TS-DOS is doing, >> as this is 100% repeatable. In my case, every test I've done results in >> the file handle not being closed, so it must never be sending the opcode. >> That just seems very weird to me, though. >> >> On Fri, May 21, 2021 at 4:39 PM John R. Hogerhuis <jho...@pobox.com> >> wrote: >> >>> Which would be a bug in TSDOS. Which either would have to be fixed there >>> or we close the file after a timeout or some other TPDD command can be used >>> as an indication the file is no longer being written. Like if the directory >>> starts being enumerated. >>> >>> -- John. >>> >>
