From owner-freebsd-questions Fri May 19 12:36:12 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA02713 for questions-outgoing; Fri, 19 May 1995 12:36:12 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA02701 for ; Fri, 19 May 1995 12:36:09 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id PAA12886; Fri, 19 May 1995 15:36:42 -0400 From: Peter Dufault Message-Id: <199505191936.PAA12886@hda.com> Subject: Stupid DOS programs and NFS write buffering To: questions@FreeBSD.org Date: Fri, 19 May 1995 15:36:41 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 785 Sender: questions-owner@FreeBSD.org Precedence: bulk I have to use some Intel development tools that run on DOS only. Unfortunately, pcemu dies on them with unimplemented op codes. I've been using a PC and PC-NFS to do this work, and these unfortunate tools do line based writes to their output files over NFS. I say this both because of the chattering of the disk and because the "nfsstat" writes were 63440 before running the program and 68456 when it finished writing a 4455 line text file. (68456 - 63440 = 5016). Is there a way to buffer the writes for these incredibly stupid programs? I'll even consider some sort of DOS cache that works with PCNFS. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267