Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <013a01c1ab96$839eefc0$0100a8c0@advent02> From: "Chris January" To: "Corinna Vinschen" Cc: References: <006e01c1a96a$f60429a0$aace0544@CX535256D> <20020130131416.D11608@cygbert.vinschen.de> Subject: Re: A real fork() on NT Date: Sat, 2 Feb 2002 03:05:47 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > That isn't really new. I'd like to point you to the example 6.1, > "Forking a Win32 Process" on p. 161ff of Gary Nebbett's excellent > book "Windows NT/2000 Native API Reference", published by MTP, > ISBN 1-57870-199-6, which also describes the problem with kernel32.dll > initialization of the child process. Are you referring to the CsrpConnectToServer function? I have a working implementation which replaces this with CsrClientConnectToServer which is exported from the DLL. Are their any other pitfalls I should be aware of? Regards Chris -- 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/