Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: <20050130182916.55154.qmail@web80109.mail.yahoo.com>
Date: Sun, 30 Jan 2005 10:29:16 -0800 (PST)
From: Dan Ch <force296-cygwin AT yahoo DOT com>
Reply-To: force296-cygwin AT yahoo DOT com
Subject: Why does cygwin1.dll use NtCreateFile() instead of CreateFile()
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes

I noticed that cygwin-1.5.12-1/winsup/cygwin/fhandler.cc
uses NtCreateFile() instead of CreateFile() on Windows NT based
operating systems (NT, 2000, 2003, XP) for opening files.  Why?  I
checked the archives for this mailing list and noted some activity
that discuses some side affects caused by using NtCreateFile()
instead of CreateFile() such as being able to use file names that are
off limits to normal Windows applications.  But I could not find
anything that explains the benefits of using NtCreateFile() instead
of CreateFile().


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