X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: <cygwin AT cygwin DOT com>
References: <48D3B01F DOT 5080200 AT oracle DOT com> <9721D18815A74E3790E86A5BC19A461A AT collinsdirect DOT com> <48D74687 DOT 80002 AT oracle DOT com> <B932A0FA75EB4E3791300D2E33218FE8 AT collinsdirect DOT com> <48D83EF8 DOT 5040401 AT cwilson DOT fastmail DOT fm> <29E315C686404A6D8696F355E283DD56 AT collinsdirect DOT com> <48D8F8AC DOT F1774B58 AT dessent DOT net>
Subject: RE: [OT] polite response to polite response - Brian...
Date: Tue, 23 Sep 2008 14:45:54 -0400
Message-ID: <124BDC78EB534CE084916FC3E6C2A96B@collinsdirect.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <48D8F8AC.F1774B58@dessent.net>
From: Barry Smith at SourceLink <barrysmith DOT sourcelink AT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> That doesn't mean that 'run' was at fault. 
Yet it could have been at fault, or the cygwin memory 
allocation could be at fault, or Windoze, or the tool 
that you're RUN-ing.
If the tool runs in Windows correctly, then the Windows
"Command Prompt" success tends to point back to CygWIN 
or "Run.exe", unfortunately.

*grin*
Yes, I understand all of the components that might have
failed. 
If _I_ had received the BSOD, I would have checked 
Windoze' stability before pointing the finger at 
CygWIN and "RUN".  
I would have probably tinkerred with the RAM allocated to 
CygWIN, and other things (like the size of the datafile 
that I was trying to process) and MANY other things before 
posting anything to any CygWIN list.
As a programmer, my first assumption is that I messed up,
not that the compiler is broken or Windoze is broken (like 
there has ever been a stable version of Windoze). 

Unfortunately, I was refering to a cygwin-xfree post 
(see response to Chris for references and age of post)
that someone else wrote, that was corroborated by the 
Web in general, documenting CygWIN and Vista problems.     

I am STILL trying to help the user who can't unzip their
file. *smile*

Barry Smith
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Brian Dessent
Sent: Tuesday, September 23, 2008 10:10 AM
To: cygwin AT cygwin DOT com
Subject: Re: [OT] polite response to rather rude reponse...

Barry Smith at SourceLink wrote:

> > Stop spreading FUD. There is no way a userland app like "run.exe" 
> > can
> "cause"
> > a blue screen. Only something running in kernel space -- like 
> > windows core
> code,
> > or certain device drivers -- can ever do that.
> 
> Then I guess you don't read the cygwin archives, because that's where 
> I read the entire thread while I was researching RUN/START execution 
> under cygwin.

That doesn't mean that 'run' was at fault.  If a user-mode program results
in a BSOD that means it exercised a bug in a kernel-mode driver, such as a
faulty virus scanner or other "security" type crapware.  There is simply no
way that a user-mode program can cause a BSOD on its own.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/