This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [OT] polite response to polite response - Brian...


> 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@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of
Brian Dessent
Sent: Tuesday, September 23, 2008 10:10 AM
To: cygwin@cygwin.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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]