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 Message-ID: <021301c20c92$7c0c61e0$6132bc3e@BABEL> From: "Conrad Scott" To: Subject: /proc/registry issues Date: Wed, 5 Jun 2002 14:11:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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. (BTW, an enum would be nice for the return codes from fhandler_registry::exists -- it's a little hard to decode fhandler_registry::fstat without that.) *) The files for REG_SZ values have the trailing '\0' in the file (I've not checked any of the REG_???_SZ types). Since that's just a representation issue, shouldn't it be omitted from the file? (i.e. the null char is not part of the value as such, just part of the way it's stored). *) Not all of the top-level keys exist on all windows versions (for example, HKEY_DYN_DATA is only available in 95/98/Me) but they all appear in /proc/registry regardless of the underlying windows version (as an empty directory). It would be nice, but presumably not critical, if only those that existed actually appeared. Is anyone else working on this? If not, I'll have a look at (at least) the zero size issue (and assuming that Red Hat have my assignment by now). // Conrad -- 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/