On Sun, 24 Nov 2002, Randall R Schulz wrote:
> Hi, Chuck,
Hi All!
> Do I have to say it?
> D'Oh!
I feel this is really just masking the real problem. In my experiences
doing development and testing under Windows, I feel that fault drivers
are mostly what causes problems (someone else mentioned this earlier and
I tend to agree). Occasionally hardware does go bad. I once had a
machine that the specs claimed it could take 128Mb of memory using 32Mb
SIMMs, but actually could only handle 64Mb using 16Mb SIMMs. With 128Mb
it became very unstable and BSOD'ed often. In that specific case, the
problem was the memory controller. If you are using fairly new hardware,
it's less likely that hardware is the problem, but more likely that OS
drivers are faulty. This is *Windows* we're talking about, here, so what
did you expect :)
> At 14:35 2002-11-24, Charles Wilson wrote:
> >Guys, I'm really surprised nobody has mentioned the obvious culprit (or
> >asked the obvious question):
> >
> >Anti virus software? Was McAfee or Norton (but esp. McAfee) running while
> >setup.exe was executed?
> >
> >I *always* disable McAfee before running setup. Every time I forget, I
> >get a bluescreen. Minidump analysis shows that the fault is in fact
> >McAfee -- which runs in kernel mode -- and not setup.
>
> I use Norton AntiVirus (2002) and I *never* enable automatic / background
> scanning. I always stick to manual scanning. Mostly I apply it to email
> attachments and occasionally to file downloads when I don't know or trust
> the source.
And, just to provide a counter example: I always run Norton AntiVirus
with automatic / background scanning enabled. I generally have to,
because of infected machines at work which probe the network whenever we
get hit with the latest rash of viruses :(. I've done all my Cygwin
installs/updates with AntiVirus enabled and never had a BSOD (I'm running
NT4 on fairly stable hardware and up to date drivers). So, it is
possible and if something does fail, it more like a driver fault than an
application fault.
The KB article (195857) is interesting in that the system needs
additional resources to be able to free up handles. I kinda find that
funny (and prefectly inline with the way MS does things :). Also, I'd
think that unless the machine in question is suffering from a shortage of
resources to begin with, that it's not likely setup.exe's fault. Anyone
know of a tool (besides Purify) which could track all the resource usages
of a given program?
> >(I also turn off McAfee when compiling; it really slows down disk IO)
> >--Chuck
> Randall
--
Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
