From: "Sander Pool" Newsgroups: comp.os.msdos.djgpp Subject: Re: call to 'open' causes all sleeping drives to awaken! Date: Thu, 20 Feb 2003 17:34:08 -0800 Organization: http://extra.newsguy.com Lines: 61 Message-ID: References: <4D19136444628A40840EFE8C5AE04147017A2F AT ELTIMAIL1 DOT elta DOT co DOT il> NNTP-Posting-Host: p-755.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 "A. Sinan Unur" wrote in message news:Xns9327D1A2E5342asu1cornelledu AT 132 DOT 236 DOT 56 DOT 8... >> 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. I have 2 IDE controllers on my motherboard and an additional one in a PCI slot. I use a lot of space for digital video editing. As my original email said, I use Win2K. Other than that I have a whole bunch of peripherals on the USB bus but let's not get into that level of detail until we're sure the problem is unique to my setup. > 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. True. I listed items I felt were pertinent to a first attempt at reproducing. Once it can not be reproduced we can add details. > > 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. Great, I will try to provide the information requested. > 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. Look, this was a first mention of the problem into an unknown community. I spent considerable time debugging this darn problem which I regret already. I provided a source code example (has anyone compiled and tried it on a system with sleeping drives?) and an accurate description of the symptom. If someone had said 'hey thanks for reporting but I can't reproduce it here, tell me X Y and Z about your system' I would have been more than happy to reply. > > 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. Right now I'm just here because I don't like running away. I realize I may need DJGPP at some point in the future. More importantly I was hoping to pre-empt this problem from affecting someone else, not me. Sander