Windoze crash (was Re: Well, I was at Fry's in CA...)

From: Philip Pemberton <philpem_at_dsl.pipex.com>
Date: Sun Jul 6 16:17:01 2003

In message <Pine.BSO.4.44.0307061801500.20123-100000_at_vaxlab.pdp11.nl>
          "Fred N. van Kempen" <waltje_at_pdp11.nl> wrote:

> On Sun, 6 Jul 2003, J.C. Wren wrote:
> > CAD software, IE, ProComm, CD ripping, a few other things), and I don't get
> > BSODs or crashes.
> Likewise. Fucked-up drivers are sometimes an issue, especially those
> for network, sound and video, but if you're careful with those, no real
> BSOD-ish situations.
I find the "big guys" like Creative are utterly crap when it comes to drivers
and tech support. "There's nothing wrong with the driver, it must be your
PC." Oh, is that why I saw a good hundred people badmouthing a certain
Soundblaster on the newsgroups?
Well, speaking of SBs, I had an AWE64. The PnP E2PROM got trashed by a bug in
their driver. Their "techie" said, and I quote:
  "Well, your guarantee's void. You used unapproved drivers and it broke, so
you're on your own".
I asked how they could tell that I had used unapproved drivers. The techie
said "Well, you obviously used the beta drivers on our website, 'cos that's a
known bug". Despite the fact that at this point I had no internet access and
had heard many a horror story about beta drivers...

Then there was the fun I had with a D-Link network card (based on a Realtek
chipset). Here's a tip - grab Realtek's latest driver kit and install it. I
had lost packets, Windows networking errors, you name it. Upgraded the
drivers and the network card suddenly started working properly...

Later.
-- 
Phil.
philpem_at_dsl.pipex.com
http://www.philpem.dsl.pipex.com/
Error 8472. Borg dumped.
Received on Sun Jul 06 2003 - 16:17:01 BST

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:36:04 BST