Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 7 May 2004 23:29:29 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: /dev/mem & /dev/kmem CYGWIN_NT-5.0 1.5.9(0.112/4/2) 2004-03-18 23:05 Message-ID: <20040507212929.GP26372@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <409BF54E.7060102@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <409BF54E.7060102@gmx.de> User-Agent: Mutt/1.4.2i On May 7 22:45, h.h wrote: > I have used cygwin for several years. I vuagly remember that I could do > strings or grep on /dev/mem and /dev/kmem. I think it does not work > anymore under Windows 2000. I'm unsure if this is due to the security > hotfixes from microsoft or some other code change. > > In the process of trying different things out I also applied the > special-devices.sh as in an other newsgroup message. I did not work. I > did then login as administrator to redo the script. I also played around > with export CYGWIN=ntsec and starting the cygserver. Still no success. Nope, that's not your fault. /dev/mem doesn't work up to and including the current developers snapshot. I've fixed it in CVS now. It should work again in the next snapshot and the upcoming 1.5.10 version. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/