Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!cs.utexas.edu!sun-barr!newstop!sun!stpeter!cmcmanis
From: cmcmanis@stpeter.Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining disk devices
Message-ID: <129936@sun.Eng.Sun.COM>
Date: 5 Jan 90 21:34:59 GMT
References: <331@sed170.HAC.COM> <9223@cbmvax.commodore.com>
Sender: news@sun.Eng.Sun.COM
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 25

In article <9223@cbmvax.commodore.com> (Andy Finkel) writes:
>For now (and, if you always want to be safe) run through the list
>twice, and only report the devices that have matching volume nodes.

Uh Andy, there is this problem that if there isn't a disk in the
floppy drive you would never put it's button up on the screen using
your method no? So people running DPAINT from the ram disk without
having any floppies in drives would just get RAM: ? Hmmm, looks a 
little weak to me. Lets just say in the documentation "Well, we can't
be totally sure that every button we put up is a disk drive, but we
guarantee that all of your disk devices will be up there. Just as soon
as C/A gives us the real answer we will fix it."

On another note (* * * D E V E L O P E R   A L E R T * * *)
If you are counting on the device name such as DH0: being only three
characters then you are in for a RUDE suprise when people like MicroBotics
let you set the names of the devices to things like HardDisk0: or even
Sources:. Be aware that this can (and does) happen, and your file requesters
will live a happier life.


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@Eng.Sun.COM
These opinions are my own and no one elses, but you knew that didn't you.
"If it didn't have bones in it, it wouldn't be crunchy now would it?!"