Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <200302051401.h15E14eN272552@pimout3-ext.prodigy.net>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Tim Prince <timothyprince AT sbcglobal DOT net>
Reply-To: tprince AT computer DOT org
To: "Dieter Meinert" <DMeinert AT RosenInspection DOT net>, <cygwin AT cygwin DOT com>
Subject: Re: Ultra slow disk access and xterm memory failure
Date: Wed, 5 Feb 2003 06:01:03 -0800
References: <AEECF2FBB179D044B2B1E93F1C98BEAF27A516 AT lin0018 DOT RosenInspection DOT net>
In-Reply-To: <AEECF2FBB179D044B2B1E93F1C98BEAF27A516@lin0018.RosenInspection.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On Wednesday 05 February 2003 05:31, Dieter Meinert wrote:

> but about a month ago something changed:
> When closing an xterm I get the following windoze error
> message:
>
>    "The instruction at "0x6106f3be" referenced memory at
> "0x00000058".
>     The memory could not be "read"."
>
Surely, this is in every FAQ.  You need to know enough about Windows to run 
CHKDSK.
-- 
Tim Prince

--
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/