Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 5 Jun 2002 11:11:14 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /proc/registry issues Message-ID: <20020605151114.GG15167@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <021301c20c92$7c0c61e0$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <021301c20c92$7c0c61e0$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i On Wed, Jun 05, 2002 at 02:11:19PM +0100, Conrad Scott wrote: >Some more or less minor issues w/ /proc/registry: > >*) All the files have a size of 0, regardless of their contents. (This might >explain why if you open a registry file in XEmacs, it comes up empty.) You >can get the size of a value's data is accessible, without retrieving the >data itself, via RegQueryValueEx. This is similar to most of the files in /proc on linux. cgf -- 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/