X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=lXtyZfK/UiQbcB3I yRLQ515Rf3L5frkYz8A6R0xdD/c+L8lo0E92mPaQq+2XC9lbA253zmmnZ9zsBLDs MyvRn+alPgHI5iFjGiy4+PcfiFZE7bD7lkGQleBWHU9MFEzgaiIySsZJiHF1JXFU jriqLR6t+30SvTMF/HdWbu47l0Y= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=dnsHSjTU3pDVNgQ/G6rIPu NbFH4=; b=k9PLKs25aHpkuvR2vy3ODquNj0fzYNe3uyaJewGkHrASO4+PPNgKv9 JDcZRTIgr03tZMg/bb60L/ldrphN+L+V+bxFNjn2Zbc70kpQpZta+/8Z9f6uQEks +bvqjuU2mx/Gd8aS7UymKx3hOJ3ZdCMp1csLmHUK+F+ALMLWHdv0U= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=alberta, Hx-spam-relays-external:sk:smtp-ou, Hx-spam-relays-external:shaw.ca, H*r:shaw.ca X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.2 cv=cNuQihWN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=yMhMjlubAAAA:8 a=b4eMD0GmHX_ZvWjD-W0A:9 a=QEXdDO2ut3YA:10 a=BKKCjISod1eDJeS0ORpz:22 Subject: Re: can't access /cygdrive/c/Windows/Sysnative ? References: <20161221170917 DOT GA16104 AT ingber DOT com> To: cygwin AT cygwin DOT com From: Brian Inglis Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Message-ID: <4a128e20-666e-5366-d432-456c67270d57@SystematicSw.ab.ca> Date: Wed, 21 Dec 2016 11:11:57 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161221170917.GA16104@ingber.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfJOBHkZ7nV//9DobQA9eFaeu8ErvU8SeXGs568Jx9ZcAapngs1eTk4PnZFsZ8NZCmyVr7mTbOPZjrFSVDEKEJvr+tRr9qfV52WBEFDhGqPQ8xlI7ApQg lkctQADET2khDtu8KcuAIEvMihg6Nyyq06J+hxlmkOZGfX77Ioal831FdONE1abV2CNuJ1RqNkl7yQ== X-IsSubscribed: yes On 2016-12-21 10:09, Lester Ingber wrote: > In some older cygwin posts, I see cygwin use of Sysnative for 64-bit > access to System32 files. In my Cygwin64 installation on my Thinkpad > Windows 10 x64 Pro PC I cannot see Sysnative at all under cygwin. > However, for example, using windows opened by Malwarebytes I can > access this directory just fine. > How can I see/access Sysnative under cygwin? Run Cygwin 32 - there only used to be 32 bit Cygwin and old posts assume that environment. Native 64 bit directories are: C:\Windows\System32 (64 bit) C:\Windows\SysWOW64 (32 bit) under 32 bit redirection these become: C:\Windows\SysNative (64 bit) C:\Windows\System32 (32 bit) to support poorly written programs that don't use the proper API call to get the directory name; see: https://msdn.microsoft.com/en-us/library/windows/desktop/aa384187(v=vs.85).aspx for full list of paths redirected from 32 bit code on a 64 bit system. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple