Date:	Fri, 14 Feb 1997 17:55:48 -0600 (CST)
From:	"Colin W. Glenn" <cwg01 AT gnofn DOT org>
To:	"'OpenDOS newsgroup'" <opendos AT mail DOT tacoma DOT net>
Subject:	Re: [opendos] Re: [opendos-developer] Caching
In-Reply-To:	<Pine.LNX.3.95.970213214537.1576F-100000@206.248.78.17>
Message-ID:	<Pine.GSO.3.95.970214175002.16495E-100000@sparkie.gnofn.org>
MIME-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

On Thu, 13 Feb 1997 mharris AT blackwidow DOT saultc DOT on DOT ca wrote:

Question!  If this is such a monster problem, why not have the software
tweak the disk drive as to keep the silly little light lit till done?  Or
would this be bypassing the bios too much?

> $mount /dev/fd0 /a -t msdos
> $cp txt/* /a/
> A 3 second wait for a 1.3Mb transfer to floppy.
> Now the drive light is off, and you pull the disk out (like you
> would in DOS).  However, the command prompt *IS* back, and the
> cache hasn't written the data to disk.  Kiss the disk goodbye.
> 
> Also, even if you could make the command prompt come back, this
> would just delay the copy operation so that you'd have to wait
> for it before doing anything else.  What? In a multitasking OS?
> Heck, any commands that don't give me my prompt back get shoved
> in the background, so that copy command becomes:
> 
> $cp txt/* /a/ &
> 
> And the prompt is back.
> 
> I'm going to scour the mount manpage again. I tried the following
> "mount -o async", but it doesn't work.
> 

<! PrePared HTML!  Just export as a HTML file and Click!>
A Christian Web Site!  The Light 
<a href="http://www.thelight.org/">.</a><br>
A neat place to visit. HotSpot 
<a href="http://www.hspro.com/hotspot/">.</a><br>
Caldera, Inc. / Makers of OpenDOS
<a href="http://www.caldera.com/">.</a><br>
Caldera's OpenDOS page
<a href="http://www.caldera.com/dos/dos.htm">.</a><br>

- Raw text -