|11 Aug 2012||#11|
Microsoft programmers have been using system32 since the early windows (32-bit). All the application programmers used this system32 program for their applications.
When windows is upgraded to 64-bit, these old applications still look for system32 folder in windows folder. Hence for application compatibility sake, Microsoft has kept the system32 folder for 64-bit portion of windows.
For 32-bit applications compatibility in windows 64 bit, windows implements WOW (windows on windows) technology, Hence the name sysWOW64 for 32 bit system folder. Even though the system folder for 32-bit programs is sysWOW64 in reality, this folder's name is mapped as system32 to those processes with the real 64-bit system32 hidden.
The windows folder also has a system folder for 16-bit applications. As Windows 64-bit does not support 16 bit code, this folder is empty.
Command.com was a 16 bit program, and as most of the people are used to it, it was left as it is, but in reality it is a 32 bit command interpreter like CMD.exe.
Some quirks of virtual programming at Microsoft.
|My System Specs|
|Similar help and support threads for2: 32 bit command prompt running on a 64 bit version of windows|
|Old version of command prompt and cannot run scannow||System Security|
|Help me to get my command prompt working in Windows 7||General Discussion|
|Run administrative command prompt from command prompt||General Discussion|
|Running an elevated command prompt (from the Recovery DVD)||General Discussion|
|Running command prompt commands elsewhere...||General Discussion|
|Command Prompt From The Windows DVD||Performance & Maintenance|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 07:49 AM.