Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Stephen Powell <me@privacy.net>
Subject: Re: BSOD on WinXP?
Date: Wed, 28 Apr 2004 17:10:23 +1000	[thread overview]
Message-ID: <ubrlch928.fsf@privacy.net> (raw)
In-Reply-To: <v9brld7upc.fsf@marauder.physik.uni-ulm.de>

On Tue, 27 Apr 2004, 4.uce.03.r.s@nurfuerspam.de wrote:

On Tue, Apr 27 2004, David Rogoff wrote:

>> However, for months now
>> (since installing WinXP) gnus has been crashing my PC about once or
>> twice a week. It always seems to be when I hit g
>> (gnus-group-get-new-news).  I get a quick Blue Screen and then the
>> PC reboots.
> 
> Lisp code like Gnus should never crash (X)Emacs.

User code should never crash windows¹. Perhaps the user should check
for a faulty device driver or similar operating system problem that
gnus is triggering. Are there any other programs that cause this
problem?

I think from the user's point of view what happens is "I run program x,
the system blue screens, therefore program x is the problem".

> From my point of view what happens is "I run program x, program x
calls device driver y to do something (write to the screen, access the
network ... whatever), device driver y has a problem and blue screens
the system, therefore device driver y is the problem".

Anyway it's not a problem with gnus and therefore not a problem for
this group.


Footnotes: 
¹ HA! HA! funny joke I hear you say.
-- 
Stephen Powell
stephen_powell <at> optusnet.com.au


      parent reply	other threads:[~2004-04-28  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <llkiun76.fsf@therogoffs.com>
2004-04-27  7:20 ` Reiner Steib
2004-04-28  1:07   ` David Rogoff
2004-04-28  7:10   ` Stephen Powell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ubrlch928.fsf@privacy.net \
    --to=me@privacy.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).