From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: call to 'open' causes all sleeping drives to awaken! Date: 20 Feb 2003 01:36:39 GMT Organization: Cornell University Lines: 64 Sender: asu1 AT cornell DOT invalid (on pool-141-149-207-114.syr.east.verizon.net) Message-ID: References: <4D19136444628A40840EFE8C5AE04147017A2F AT ELTIMAIL1 DOT elta DOT co DOT il> NNTP-Posting-Host: pool-141-149-207-114.syr.east.verizon.net X-Trace: news01.cit.cornell.edu 1045704999 3750 141.149.207.114 (20 Feb 2003 01:36:39 GMT) X-Complaints-To: usenet AT news01 DOT cit DOT cornell DOT edu NNTP-Posting-Date: 20 Feb 2003 01:36:39 GMT User-Agent: Xnews/5.04.25 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Sander Pool" wrote in news:b311q7029h9 AT enews1 DOT newsguy DOT com: > > "A. Sinan Unur" wrote in message > news:Xns93278CC415AB7asu1cornelledu AT 132 DOT 236 DOT 56 DOT 8... >>> what are each of these drives? is each one a separate physical >>> drive, or >> a partition? are these drives on you path? > > Two drive letters are partitions of a single disk, the other ones are > all separate. Only C: is on my path. Obviously once a single partition > on a drive is in use the whole drive is spun up. That is curious. In usual configurations, a maximum of four physical drives is the norm, so it would be great if you gave more detailed information about the specific configuration of your machine, as well as OS etc. >> > The original email contained more than enough information to at >> > least try to reproduce the bug. If you can't, well in that case we >> > can start digging. >> >> what bug? > > Look, if you don't care then don't ask. The original post contains the > information. And if you think this is intended behavior then you're > not doing DJGPP a service. I do care. But the fact is, the original post does not give enough information: You did not list your config, give a hint of what is in your path (which likely is different than the path under mingw), if any drives are subst'tituted so on and so forth. There are many potential explanations for the behavior you are observing, most of which are not bugs. I am not claiming there are no bugs in DJGPP, but to be able to identify the issue, more information is needed. So, I apologize if you found the question insensitive, but that wasn't what I had intended. More information would help us understand and explain the behavior your are observing. > But, like I said before it doesn't really matter. An alternative tool > works better so I'm set. Whoever maintains DJGPP can address this or > not. A good tool community would have been thankful for a problem > report like this but I guess DJGPP is different. Second strike. > Congrats. It would be your loss if you gave up on DJGPP because you did not like my response. After all, I have not contributed to DJGPP at all. However, I do not think any community would be that thankful for such a fuzzy problem report. Note that DJGPP and mingw have different capabilities, and if you think you might need the features offered by DJGPP, it would be in your interest to follow-up with more information, so someone can identify the cause of the behavior you are observing, and if it is indeed a bug, fix it. Sinan. -- A. Sinan Unur asu1 AT c-o-r-n-e-l-l DOT edu Remove dashes for address Spam bait: mailto:uce AT ftc DOT gov