TMPLee@DOCKMASTER.NCSC.MIL (08/10/89)
We (some other kind soul who's address my system won't recognize) and I tracked it down. It only APPEARED that the hard drive was writing every 20 or 30 or 40 blocks. He had noted that on someone else's system if the writes are quick enough you won't able to see the drive light go on. (That probably is also why I thought block warden wasn't writing either when it really was.) When I downloaded to the 3.5 disk instead of the hard drive you could clearly see the light come on every two or three packets. Now, the real moral of the story is: just because you don't see the light on your hard drive flicker doesn't mean it isn't being written to. TMPLee@dockmaster.arpa p.s. -- re the kermit block sizes (someone said what you set didn't matter since the length was negotiated between sender and receiver and so I might have been getting 9K packters afterall) -- what you get is the smaller of whatever is specified, so in this case I know it was 250 bytes; one can also tell by looking at the send/receive byte count. and I know it can't be more than 255 bytes because Ted Medin said that was as large as he would let it go since he didn't want to have to handle two-byte pointers/counts.