From:	"Sander Pool" <dutchguy DOT removethis AT nospam DOT pacbell DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: call to 'open' causes all sleeping drives to awaken!
Date:	Wed, 19 Feb 2003 11:05:41 -0800
Organization:	http://extra.newsguy.com
Lines:	27
Message-ID:	<b30ki601hek@enews1.newsguy.com>
References:	<b2v0tc02dt0 AT enews4 DOT newsguy DOT com> <QqK4a.51044$jM5 DOT 127842 AT newsfeeds DOT bigpond DOT com>
NNTP-Posting-Host:	p-069.newsdawg.com
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"Ben Peddell" <lightspeed85 AT hotmail DOT com> wrote in message
news:QqK4a.51044$jM5 DOT 127842 AT newsfeeds DOT bigpond DOT com...
>> Why not find out whether the drives are spinning-up before or after the
> open() is issued, by printing something before the open(), and waiting for
> user input.

I could do that but I suspect that printf uses open() as well so it wouldn't
prove anything. It would be better to remove the open() call and see if the
same thing happens.

> If it is occurring before the open(), then it is probably the stub loader
> searching for CWSDPMI.EXE on the path. If you don't want this to happen,
> then ensure that DPMI is active before running the program.

I'll check it out but like I reported, MinGW doesn't have this problem so I
see no reason to change my system config to make DJGPP work. I know there
are probably a lot of good reasons to use DJGPP over MinGW but I don't want
to (re)start a religious war over that :-) I'm merely reporting a problem
that someone may want to reproduce and fix.

Thanks,

  Sander

- Raw text -