Corinna Vinschen wrote: > On Jul 13 23:01, K L wrote: > > > > Hi Tony, > > > > I used cmd.exe as administrator. I don't think its a permission issue. > > Because the bug reproducing steps, I can use notepad to create ddd.txt > > in %system32%. I can reproduce the bug on Vista and Win 7, both on > > x64. > > > > Also, I tried Vim 64 from http://code.google.com/p/vim-win3264/. > > There's no problem with this build. However, it seems not to be an > > official build. > > This is not Vista specific. The effect you're seeing is a result of the > path redirection for 32 bit processes on a 64 bit system. The system32 > folder is invisible to 32 bit processes. If they try to access that > folder, they get redirected to the syswow64 folder, which is the folder > containing the 32 bit DLLs and 32 bit executables which are in system32 > on 32 bit systems. > > See http://msdn.microsoft.com/en-us/library/aa384187(VS.85).aspx > > Note especially the last paragraph, which describes how you can access > the system32 folder from 32 bit processes using the %windir%\Sysnative > substitute starting with Vista.
Using %windir%\Sysnative is a last resort for getting around FS redirection, when using an app that doesn't know better. If we wanted to actually make Vim aware of the redirection and disable it, we could add a call to Wow64DisableWow64FsRedirection() during Vim's initialization. See http://msdn.microsoft.com/en-us/library/aa365743(VS.85).aspx. Craig --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
