Date: Sun, 7 Jan 2001 14:29:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: djgpp-workers AT delorie DOT com
Subject: Re: df <-> df r:/
In-Reply-To: <200101071222.NAA23273@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.1010107142324.25836F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 7 Jan 2001, Martin Str|mberg wrote:

> > Why is the BUSY bit set?  Did you wait until the drive LED went off,
> > after you inserted the disk, before running the tests?
> 
> I sure did. But stooopid WINDOZE tries to launch a DVD player as soon
> I insert a DVD-ROM, that fails to start because I use to high a
> resolution on the screen.

You could try to break the association of a DVD with the player, and see 
if that helps to get the BUSY bit cleared.

> But I don't understand why we shouldn't report busy drives?

Since we cannot find a way to distinguish between a CD and a DVD, I'm 
afraid we will break the code wrt to CDs.  That code was tricky to get 
right (it took at least two major rewrites), so I'd hate to break it.

If you can find any way to change that code so that it only accepts the 
BUSY bit in the case of DVD, it's okay with me.