![]() ![]() ![]() ![]() (Ironically, there was the same issue when migrating from 16-bit Windows to 32-bit Windows. The 16-bit "System" directory was \Windows\System, usually.) As a consequence, a whole lot of programs were looking for 64-bitexecutables and libraries in the \Windows\System32 directory, whose name they had hardwired. But too many people foolishly hardwired the actual name of the directory, \Windows\System32, into their programs, and then ported those programs from 32-bit Windows to 64-bit Windows. Windows programs are supposed to locate them using system API functions such as SHGetKnownFolderPath() and GetSystemDirectory() and if everyone had done that the world would be quite different at this point. In Windows, there is a "Windows" directory and a "System" directory, and this has been true all of the way back to when Windows was 16-bit. Microsoft does things backwards sometimes, and this is yet another example of this. System32 is the 64-bit Windows system directory and SysWOW64 is the 32-bit Windows system directory - entirely the opposite way around to what the directory names would suggest. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |