Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!asuvax!mcdphx!mcdchg!ddsw1!tronsbox!dsoft!groo
From: groo@dsoft.UUCP (Bill Squier)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining disk devices
Keywords: Auto-disk reading, drive contention
Message-ID: <485@dsoft.UUCP>
Date: 11 Jan 90 03:01:51 GMT
References: <2924@dogie.macc.wisc.edu> <572@shodha.dec.com>
Lines: 21

In article <572@shodha.dec.com> ridder@elvira.enet.dec.com (Hans Ridder)
writes:
>
>Something I thought of a while back was that a file requester could
>*automatically* select a volume when it was inserted.  The assumption
>would be that if you just stuck it in, you probably want to access it.

That's a bad idea on a multitasking machine.  How would the process know
that there wasn't some other application that you were inserting the
disk for.

Even worse, what if all applications followed this strategy?  Imagine
the disk contention as VirusX, ProcessA, ProcessB, ProcessC, and the
validator all started reading the disk at once!

Just having VirusX and the validator on my machine is bad enough.

-- 
Bill Squier - Stevens Inst. of Tech  |   //  "Only Amiga makes it possible"
Bitnet: u93_wsquier@stevens          | \X/
Internet: u93_wsquier@vaxc.stevens-tech.edu
Temporary Inet (Please use until Jan. 13):  ...uunet!tronsbox!dsoft!groo