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
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	Ultra slow disk access and xterm memory failure
X-MimeOLE:	Produced By Microsoft Exchange V6.0.6249.0
Date:	Wed, 5 Feb 2003 14:31:54 +0100
Message-ID:	<AEECF2FBB179D044B2B1E93F1C98BEAF27A516@lin0018.RosenInspection.net>
X-MS-Has-Attach:
From:	"Dieter Meinert" <DMeinert AT RosenInspection DOT net>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id h15DW5R25901

-----BEGIN PGP SIGNED MESSAGE-----

Hi all,

Firstofall, I'm completely ignorant of anything windoze
related, 
but currently put into a completely *IX ignorant
environment, 
so cygwin is my only hope. 

I use cygwin (version of about April 2002, BTW how can I
get the Cygwin version number ?) 
and tcsh v6.11.00 (cygwin version) for about half a year
now,
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"."

This in itself is not alarming to me since after pushing
"OK" the message
and the xterm vanish. But since the same time my xemacs
(under XFree86) 
went slooooooow whenever it accesses the disk, esp.
annoying when autosaving. 

Also, any reactions from the Cygwin Window became slow at
that time. 

I reduced the path to the necessary minimum(no network
disks, no redundancies), 
assuming that some network disks are regularly accessed,
but to no avail;although
the problem gets better when cutting the network
connection, it does not disappear 
completely.  

I cannot say if something changed in the windoze
environment, which AFAIK may happen without my knowledge,
and I have no more clues on where my problem may originate.

Maybe some of you have experienced a similar behaviour and
may offer some more clues.

BTW. I'm not in a position to upgrade cygwin or any
packages myself, lacking access to important internet
protocols.


 
 Regards
 							Dieter Meinert
 
 

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQEVAwUBPkEEOrYBkYAdGmPFAQHGlQf8DCuPsCGZZfZ5NWf7HVAG3EmmlTS/npcp
wLXb3cHSiQUvDEncuBndaOIc7lJJrPROE1errva3ULgjVEE21SZdh1RdaLR1ExKs
gCWPfSYghpC6oG0cNMXEWig2lDdNeEaGGCY/BlbjJ5vY2n4QW8rvszyP7j9zpNfC
NZqF8JrvjcrEvDX7F0eDI/LKN9RL11jJMRucxqxkUe3auOTY3xHQ45gZP6YzCB19
JGoawdeNyx9Mw7FMQBwCTiBZGGNNnaV/14E3DQXh03v07GDRuJYQrkOJmv4jQq3w
0Ujf0cy/sf3m01BfBfWV1CYf/3RCmR/wk5XTYJEx5WulD01pADKykA==
=Z5Se
-----END PGP SIGNATURE-----


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

- Raw text -