Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!plains!jnelson
From: jnelson@plains.NoDak.edu (Jim Nelson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: insert diskette in drive B
Keywords: diskette, drive
Message-ID: <8326@plains.NoDak.edu>
Date: 15 Feb 91 18:52:11 GMT
References: <090905.3866@timbuk.cray.com>
Organization: North Dakota State University, Fargo, ND
Lines: 19

In article <090905.3866@timbuk.cray.com> dp@hemlock.cray.com (David Polansky) writes:
>I am writing an application which will be reading from diskettes quite
>frequently.  On systems which have only one diskette drive I don't want
>the message requeting that the user insert the diskette in drive B (or A)
>and then push any key to continue to mess up my display.  Is there any way 
>to intercept this message.  If not I know how to detect that there is only
>one diskette drive.  Is there some way to determine whether it is considered
>drive A or drive B at the time the program starts?  (The optimal solution is
>to trap the message and deal with it from there.)  Thanks for any help.

Check the Bios Equipment Word.  I'm not sure of it's exact location, but
Turbo C has a function called biosequip that will grab it for you.  If your
not using C, grab any good book on DOS.

-- 
.sig?  What .sig?  Ohhhh, *THIS* .sig.

	Jim, in the Land of the Lost. 
disclaimer:  These are just opinions.  If you want 'em, you can have 'em.