How to Open and Run 32-bit Command Prompt in 64-bit (x64) Windows ¿±â¸¦ ½ÇÇàÇÏ´Â ¹æ¹ýÀ» 32 - ºñÆ® ¸í·É ÇÁ·ÒÇÁÆ®¿¡¼ 64 - ºñÆ® (64 ºñÆ®) windows
64-bit or x64 version of Windows operating system such as Windows Server 2003, Windows XP Professional x64 Edition, Windows Vista and Windows Server 2008 uses the Microsoft Windows-32-on-Windows-64 (WOW64) subsystem layer to run 32-bit programs, binaries or drivers without modifications, change or transition to 64-bit based binaries, as the 64-bit OS is optimized to run native 64-bit programs and does not provide support for 16-bit binaries or 32-bit drivers. 64 - ºñÆ® ¶Ç´Â x64 ¹öÀü À©µµ¿ì °°Àº ¿î¿µ üÁ¦¸¦ ¼¹ö 2003, XP ¿ë Àü¹® x64 ¹öÀü, windows ºñ½ºÅ¸¿Í windows ¼¹ö 2008À» »ç¿ë microsoft windows - 32 -ÀÌ - windows - 64 (wow64) ÇÏÀ§ ½Ã½ºÅÛ ·¹À̾ ½ÇÇàÇÏ´Â 32 - ºñÆ® ÇÁ·Î±×·¥, ¹ÙÀ̳ʸ® ¶Ç´Â µå¶óÀ̹ö¸¦ ¼öÁ¤, º¯°æ ¶Ç´Â ¸¶ÀÌ ±× ·¹À̼ÇÀ» 64 - ºñÆ® ±â¹Ý ¹ÙÀ̳ʸ®·Î 64 - ºñÆ® ¿î¿µ üÁ¦°¡ ÃÖÀûÀÇ ³×ÀÌÆ¼ºê 64 - ºñÆ® ÇÁ·Î±×·¥°ú ½ÇÇà¿¡ ´ëÇÑ Áö¿øÀ» Á¦°øÇÏÁö ¾Ê½À´Ï´Ù 16 - ºñÆ® ¹ÙÀ̳ʸ® ¶Ç´Â 32 - ºñÆ® µå¶óÀ̹ö¸¦ÇÕ´Ï´Ù.
To reduce compatibility issue and prevent a 32-bit program from accidentally accessing data from 64-bit application, WOW64 subsystem isolates 32-bit binaries from 64-bit binaries by redirecting registry calls and some file system calls. ȣȯ¼º ¹®Á¦¸¦ ÁÙÀ̱âÀ» ¹æÁöÇÏ´Â 32 - ºñÆ® ÇÁ·Î±×·¥ÀÇ ½Ç¼ö·Î µ¥ÀÌÅ͸¦ ¾×¼¼½ºÇÏ´Â 64 - ºñÆ® ÀÀ¿ë ÇÁ·Î±×·¥, 32 - ºñÆ® wow64 ¼ºê ½Ã½ºÅÛ ¹ÙÀ̳ʸ®¸¦ ºÐ¸®ÇÏ¿© 64 - ºñÆ® ÀÌÁø ·¹Áö½ºÆ®¸®¸¦ È£Ãâ°ú ÀϺΠÆÄÀÏÀÌ ½Ã½ºÅÛ È£ÃâÀ» ¸®µð·º¼ÇÇÕ´Ï´Ù. Other than separate registry hive for WOW64 redirected 32-bit values, %systemroot%\System32 and Program Files folder is designated as 64-bit DLLs only too, and all access or I/O of 32-bit binaries been redirected from %windir%\System32 folder to the %windir%\SysWOW64 folder, and from Program Files to Program Files (x86) directory. ÀÌ¿ÜÀÇ ·¹Áö½ºÆ®¸® ÇÏÀ̺긦À§ÇÑ º°µµÀÇ wow64 ¸®µð·º¼Ç 32 - ºñÆ® °ª, % systemroot % \ system32 ¹× ÇÁ·Î±×·¥ ÆÄÀÏÀ» Æú´õ´Â 64 - ºñÆ® dlls¿¡¸¸·Î ÁöÁ¤µÇ¾îµµ, ¸ðµç ¾×¼¼½ºÇϰųª / ¿ÀÀÇ 32 - ºñÆ® ÀÌÁøÀÌ ³¹¸» »çÀü, % windir % \ system32 Æú´õ¸¦ % windir % \ syswow64 Æú´õ ¹× ÇÁ·Î±×·¥¿¡ ÆÄÀÏÀ» ÇÁ·Î±×·¥ ÆÄÀÏ (x86) µð·ºÅ丮ÇÕ´Ï´Ù.
The command prompt (cmd.exe) is also affected by ¸í·É ÇÁ·ÒÇÁÆ® (cmd.exe)µµ ¿µÇâÀ»¹Þ½À´Ï´Ù File System Redirection ÆÄÀÏ ½Ã½ºÅÛ ¸®µð·º¼Ç feature, where command line commands or .bat and .cmd batch script may not be able to access, install, change, modify, delete or write to ¡°Program Files¡± or ¡°%windir%\System32¡È folder. ±â´ÉÀ» ¾îµð¿¡ Ä¿¸Çµå ¶óÀÎ ¸í·É ¶Ç´ÂÇÕ´Ï´Ù. ¹æ¸ÁÀÌ¿ÍÇÕ´Ï´Ù. cmd Àϰý ó¸® ½ºÅ©¸³Æ®¿¡ ¾×¼¼½ºÇÏÁö ¸øÇÒ ¼öµµÀÖ½À´Ï´Ù, ¼³Ä¡, º¯°æ, ¼öÁ¤, »èÁ¦ ¶Ç´Â ¾²±â¸¦ "ÇÁ·Î±×·¥ ÆÄÀÏ"¶Ç´Â "% windir % \ system32"Æú´õ¿¡ÀÖ½À´Ï´Ù. The WOW64 subsystem redirects and installs 32-bit programs in the ¡°Program Files (x86)¡± and ¡°%systemroot%\SysWOW64¡È folder. the wow64 ¼ºê ½Ã½ºÅÛ ¹× ¼³Ä¡ 32 - ºñÆ® ÇÁ·Î±×·¥¿¡¼ ¸®µð·º¼Ç "ÇÁ·Î±×·¥ ÆÄÀÏ (x86)"¹× "% systemroot % \ syswow64"Æú´õ¿¡ÀÖ½À´Ï´Ù.
To access the correct folder, programmer or developer must change the command-line script, or using ¿Ã¹Ù¸¥ Æú´õ¿¡ ¾×¼¼½ºÇÏ·Á¸é ÇÁ·Î±×·¡¸Ó ¶Ç´Â °³¹ßÀÚÀÇ ¸í·É - ¶óÀÎÀ» º¯°æÇؾßÇÏ´Â ½ºÅ©¸³Æ®, ¶Ç´Â »ç¿ë Sysnative virtual directory alias to access %windir%\System32 °¡»ó µð·ºÅ丮 º°ÄªÀ» sysnative¿¡ Á¢±ÙÇÒ % windir % \ system32 instead of %windir%\SysWOW64. ´ë½Å¿¡ % windir % \ syswow64ÇÕ´Ï´Ù. When this is not possible, or when have to access original native Program Files folder, user can type the command-line script at a 32-bit command prompt. ÀÌ ¸ðµç ÀÛ¾÷ÀÌ ºÒ°¡ ´ÉÇØ, ¾Æ´Ï¸é ±âÁ¸ ¿ø½Ã ÇÁ·Î±×·¥ ÆÄÀÏ Æú´õ¿¡ Á¢¼ÓÀ»Çϸé, »ç¿ëÀÚÀÇ ¸í·É - ¶óÀÎ ½ºÅ©¸³Æ®¸¦ ÀÔ·ÂÇÒ ¼öÀÖ½À´Ï´Ù¿¡¼ 32 - ºñÆ® ¸í·É ÇÁ·ÒÇÁÆ®¸¦ÇÕ´Ï´Ù. The 32-bit command prompt automatically redirects file system calls to the correct 32-bit directory. ¸í·É ÇÁ·ÒÇÁÆ®¸¦ ÀÚµ¿À¸·Î ¹æÇâÀ» ¹Ù²Û´Ù´Â 32 - ºñÆ® ÆÄÀÏ ½Ã½ºÅÛ È£Ãâ¿¡ ´ëÇÑ ¿Ã¹Ù¸¥ 32 - ºñÆ® µð·ºÅ丮ÇÕ´Ï´Ù.
To start and open a 32-bit command prompt, follow these steps: ¸¦ ½ÃÀÛÇϰí 32 - ºñÆ® ¸í·É ÇÁ·ÒÇÁÆ®¸¦ ¿°í ´ÙÀ½°ú °°ÀÌ ´Ü°è :
- Click Start . ½ÃÀÛÀ» ´©¸¨´Ï´Ù.
- Type %windir%\SysWoW64\cmd.exe in Start Search box. À¯Çü % windir % \ syswow64 \ cmd.exe¿¡¼ °Ë»ö »óÀÚ¸¦ ½ÃÀÛÇÕ´Ï´Ù.
Alternatively, press Win + R keys (or type Run in Start Search) to open Run dialog, and type %windir%\SysWoW64\cmd.exe . ¶Ç´Â, ¾ð·Ð ½Â + ¿¬±¸ Ű (¶Ç´Â À¯Çü¿¡¼ ½ÇÇàÀ» ½ÃÀÛ °Ë»ö)¸¦ ½ÇÇà ´ëÈ »óÀÚ¸¦ ¿±´Ï´Ù¸¦ ÀÔ·Â % windir % \ syswow64 \ cmd.exeÇÕ´Ï´Ù.
- Press Enter . ¾ð·ÐÀ» ÀÔ·ÂÇÕ´Ï´Ù.

In 32-bit command prompt, the %programfiles% path variable will point to Program Files (x86) folder which stores all 32-bit binaries. 32 - ºñÆ® ¸í·É ÇÁ·ÒÇÁÆ®¿¡¼, % programfiles % °æ·Î¸¦ ¸Å°³ º¯¼ö¸¦ Â÷·Ê·Î ÇÁ·Î±×·¥ ÆÄÀÏ (x86) Æú´õÀÇ ¸ðµç 32 - ºñÆ® ¹ÙÀ̳ʸ®¸¦ ÀúÀåÇÕ´Ï´Ù.
IMPORTANT : You're reading a machine translated page which is provided "as is" without warranty. Áß¿ä »çÇ× : ´ç½ÅÀº ±â°è ¹ø¿ª ÆäÀÌÁö¸¦ ÀаíÀÌ Á¦°ø¾øÀÌ "ÀÖ´Â ±×´ë·Î"ǰÁú º¸ÁõÇÕ´Ï´Ù. Unlike human translation, machine translation does not understand the grammar, semantics, syntax, idioms of natural language, thus often produce inaccurate and low quality text which is misleading and incomprehensible. Àΰ£ÀÇ ¹ø¿ª°ú´Â ´Þ¸®, ±â°è ¹ø¿ªÀ» ÀÌÇØÇÏÁö ¾Ê½À´Ï´Ù ¹®¹ý, Àǹ̷Ð, ¹®¹ý, ¼÷¾îÀÇ Ãµ¿¬ ¾ð¾î, ±×·¡¼ Á¾Á¾ ºÎÁ¤ È®ÇѰú ³·Àº ǰÁú ÅØ½ºÆ®¸¦ »ý»êÇϰí ÀÌÇØÇÒ ¼ö¾ø´Â ¿ÀÇØ°¡ÀÖ½À´Ï´Ù. Thus, please refer to µû¶ó¼¸¦ ÂüÁ¶ÇϽñ⠹ٶø´Ï´Ù original English article ±âÁ¸ ¿µ¾î ÀÚ·á when in doubt. ÀǽÉÀÌ ³ª¸éÇÕ´Ï´Ù.
Related Articles °ü·Ã ±â»ç
- How to Suppress and Bypass System32 File System Redirect to SysWOW64 Folder with Sysnative ¿ìȸÇÏ´Â ¹æ¹ýÀ» ¾ïÁ¦Çϰí system32 Æú´õ¿¡ ÆÄÀÏ ½Ã½ºÅÛÀ» sysnative·Î ¸®µð·º¼Ç syswow64
- Error 1721: There Is A Problem With This Windows Installer Package When Install or Uninstall on Vista ¿À·ù 1721 :ÀÌ Ã¢ ¼³Ä¡ ÇÁ·Î±×·¥ ÆÐŰÁö¿¡ ¹®Á¦°¡ ºñ½ºÅ¸¸¦ ¼³Ä¡Çϰųª Á¦°ÅÇϸé
- How Open Command Prompt as Administrator on Elevation in Vista ¸í·É ÇÁ·ÒÇÁÆ®¸¦ ¿±´Ï´Ù °ü¸®ÀÚ ±ÇÇÑÀ¸·ÎÇÏ´Â ¹æ¹ýÀ» ÇØ¹ß °íµµ¿¡ ºñ½ºÅ¸
- Microsoft Releases MUI Language Packs for Windows Vista Ultimate SP1 microsoft windows ºñ½ºÅ¸ ±Ã±ØÀûÀÎ SP1À»À§ÇÑ ¾ð¾î ÆÑÀ» Ãâ½Ã mui
- Fix Setup Installer Package Access Denied Failure Error Code 0¡¿80070005 (Or 5 Or 0¡¿5) ¼³Ä¡ ÇÁ·Î±×·¥À» ¼³Ä¡ ÇÁ·Î±×·¥ ÆÐŰÁö¸¦ ¾×¼¼½º °ÅºÎ ¿À·ù ¼öÁ¤ Äڵ带 0 ¡¿ 80070005 (¶Ç´Â 5 ¶Ç´Â 0 ¡¿ 5)
- Microsoft Virtual PC (VPC) 2007 SP1 Free Download microsoft °¡»ó ÄÄÇ»ÅÍ (°¡»ó PC) 2007¿¡¼ ¹«·á·Î ´Ù¿î·Îµå
- ImageX 6001.18000 (x86 and x64 for Windows Server 2008 and Vista SP1) Standalone Download imagex 6001.18000 (x86 ¹× x64 ¿ë SP1À» ºñ½ºÅ¸ 2008 ³â) µ¶¸³ ½ÇÇàÇü ´Ù¿î·Îµå
- Workaround to Run VMWare Server on Windows Vista ÇØ°á ¹æ¹ý windows ºñ½ºÅ¸¸¦ ½ÇÇàÇÏ´Â ¼¹ö¿¡¼ vmware
- Windows Vista Startup Hang and Boot Failure after SP1 on Corrupt Driver File (atapi.sys and ataport.sys) SP1À» ½ÃÀÛ ÁßÁö ¹× ºÎÆ® ½ÇÆÐ ÈÄ windows ºñ½ºÅ¸¿¡ ¼Õ»ó µå¶óÀ̹ö ÆÄÀÏ (atapi.sys ¹× ataport.sys)
- Windows Cannot Hibernate Computer with More Than 4 GB Memory ÄÄÇ»Å͸¦ ÃÖ´ë ÀýÀü ¸ðµå ¼ö¾ø½À´Ï´Ù °³ ÀÌ»óÀÇ ¸Þ¸ð¸®¸¦ »ç±â°¡¹ÙÀÌÆ®

































May 23rd, 2008 14:29 2008³â 5¿ù 23ÀÏ 14½Ã 29ºÐ
As you described in the article, the original %SystemRoot%\System32 is not accessible to 32-bit processes. ÀÌ ¹®¼¿¡ ¼³¸íµÈ¸¦ ¿ø·¡ÀÇ % systemroot % \ system32´Â 32 - ºñÆ® ÇÁ·Î¼¼½º¸¦ ¾×¼¼½ºÇÒ ¼ö ÀÖµµ·ÏÇÕ´Ï´Ù. Unfortunately, there are several tools existing uniquely as 64-bit binaries (eg logogg.exe and tsshutdn.exe). ºÒÇàÈ÷µµ, ¿©·¯ µµ±¸°¡ ±âÁ¸ÀÇ °íÀ¯À¸·Î 64 - ºñÆ® ¹ÙÀ̳ʸ® (¿¹ : logogg.exe ¹× tsshutdn.exe). In one of my articles, I describe two techniques circumventing the limitation of launching 64-bit system tools from 32-bit processes: º»ÀÎÀÇ ±â»ç Áß Çϳª¿¡¼, ³ªÀÇ Á¦ÇÑÀ» ¿ìȸÇÏ´Â ¹æ¹ýÀ» ¼³¸í ½ÃÀÛÇÏ´Â µÎ °³ÀÇ 64 - ºñÆ® ½Ã½ºÅÛ °ü¸® µµ±¸¿¡¼ 32 - ºñÆ® ÇÁ·Î¼¼½º : http://blogs.sepago.de/nicholas/2008/03/13/jailed-32-bit-processes-on-windows-x64/
Enjoy, Áñ±â´Ù,
Nicholas. ´ÏÄݶó½ºÇÕ´Ï´Ù.
August 21st, 2008 11:37 2008³â 8¿ù 21ÀÏ 11:37
i tried using your advice to try and get some 32bit apps to run a bit better on my 64bit box. ±ÍÇÏÀÇ Á¶¾ðÀ» »ç¿ëÇÏ´Â ³ë·ÂÀ» ½ÃµµÇϰí Á» ´õ ³ªÀº ³» ºñÆ® 32 ºñÆ® ¾ÖÇà ¸®ÄÉÀ̼ÇÀ» ½ÇÇàÇÏ´Â 64 ºñÆ® ¹Ú½ºÇÕ´Ï´Ù. problem is, now i get weird errors from some key software. ¹®Á¦´Â, ÀÌÁ¦ºÎÅÍ Á» ÀÌ»óÇÑ ¿À·ù°¡ ¸î¸î ÁÖ¿ä ¼ÒÇÁÆ®¿þ¾î¸¦ÇÕ´Ï´Ù. i don¡¯t know how to undo the change¡¦ which may serve me right for swimming in deep waters¡¦ º¯°æÀ» Ãë¼ÒÇÏ´Â ¹æ¹ýÀ» Àß ¸ð¸£°Ú¡¦ ¾î´À ³¯ Á¦´ë·Î ¼öÀÖ½À´Ï´Ù ±íÀº ¹Ù´Ù ¼ö¿µÀ» À§ÇØ¡¦
throw me a raft, ya? ¶Â¸ñÀ» ´øÁ® ³×?
here¡¯sa sample error that showed up mid-execution after i¡¯d run the %windir%\SysWoW64\cmd.exe command: ´ÙÀ½Àº »ùÇà ¿À·ù°¡ ³ªÅ¸³ª±â Áß¹Ý - ½ÇÇàÀ» ½ÇÇàÇÏ¿© % windir Áö³ª¼ % \ syswow64 \ cmd.exe ¸í·É :
Error: can¡¯t define ¡°ProgramFiles(x86)¡±: name refers to an element in an array ¿À·ù : Á¤ÀÇÇÒ ¼ö ¾ø´Ù "programfiles (x86)": À̸§À» ¹è¿ÇÏ´Â ¿ä¼Ò¿¡ °ü·ÃµÈ
while evaluating script: namespace eval :: {source {C:/Program Files (x86)/[directory tree]/RMSExpression.tcl}} Æò°¡¸¦ÇÏ´Â µ¿¾È ½ºÅ©¸³Æ® : ³×ÀÓ ½ºÆäÀ̽º¸¦ Æò°¡ : : (¼Ò½º (c : / ÇÁ·Î±×·¥ ÆÄÀÏ (x86) / [µð·ºÅ丮 Æ®¸®] / rmsexpression.tcl))
August 21st, 2008 14:34 2008³â 8¿ù 21ÀÏ 14:34
I may be dipping the raft but I reckon the TCL interpreter does not allow brackets in the path to a file which it is about to source. ³ª´Â ¶Â¸ñÇÏÁö¸¸ Àü ÆÈ¸ñÀÇ ÀåÄ¡ÀÇ °æ»ç ¼öÀÖ½À´Ï´Ù tcl ÀÎÅÍÇÁ¸®ÅÍÀÇ °æ·Î¸¦ Çã¿ëÇÏÁö ¾Ê´Â ÆÄÀÏÀ» °ýÈ£´Â ¼Ò½º¿¡ ´ëÇØÇÕ´Ï´Ù.
Does it help to move the installation directory to a location outside of ¡°c:\Program Files (x86)¡±, eg ¡°c:\progs¡±? ±×·¸Áö µµ¿òÀ» ¹ÛÀ¸·Î ÇÑ À§Ä¡¿¡ ¼³Ä¡ µð·ºÅ丮·Î À̵¿ÇÏ¿© "c : \ ÇÁ·Î±×·¥ ÆÄÀÏ (x86)", ¿¹ : "c : \ ¼ÒÇÁÆ®"?
Hope that helps, Èñ¸ÁÇÏ´Â µ¥ µµ¿ò,
Nicholas. ´ÏÄݶó½ºÇÕ´Ï´Ù.
August 21st, 2008 17:42 2008³â 8¿ù 21ÀÏ 17½Ã 42ºÐ
i thought that might be a solution, but before i tried it, i tried just running it from a normal shell, instead of through the batchfile that launched the app in question, and it worked fine. ³» »ý°¢¿¡ ÇØ°áÃ¥À» ¼öµµ ÀÖÁö¸¸ ³ª´Â ±×°ÍÀ» ½ÃµµÇß´ÙÇϱâ Àü¿¡, ³ª´Â ±×°ÍÀ» ½ÇÇàÇÏ´Â ½Ãµµ ´ÜÁö ÀϹÝÀûÀÎ ½©, ´ë½Å¿¡ ÀÀ¿ë ÇÁ·Î±×·¥À» ÅëÇØ batchfileÀÌ ¹®Á¦ÀÇ ½ÃÀÛ, ±×¸®°í È¿°ú°¡ ÁÁ¾ÆÇÕ´Ï´Ù. so much weirdness. ³Ê¹« ¸¹Àº ±â±«ÇÔÇÕ´Ï´Ù.
the batchfile no longer works, but direct command line does. the batchfile ´õ ÀÌ»ó ÀÛµ¿ÇÏÁö ¾Ê½À´Ï´Ù,ÇÏÁö¸¸ Á÷Á¢ÀûÀ¸·Î Ä¿¸Çµå ¶óÀÎÀÌÀÖ½À´Ï´Ù. how weird is that?! ¹¦ÇÏÁÒ?!
i¡¯ll also try a different path without brackets to see if that re-enables my batchfile¡¯s ability to launch. ³»°¡ ºê·¡Å¶À»ÇÏÁö ¾Ê°íµµ ´Ù¸¥ °æ·Î¸¦ ½Ãµµ -À» »ç¿ëµÇ´ÂÁö È®ÀÎÇϽʽÿÀ ³» batchfileÀÇ ±â´ÉÀ» ´Ù½Ã ½ÃÀÛÇÕ´Ï´Ù. reaaaly need the batchfile to work again¡¦ batchfileÀ» ´Ù½Ã ÀÛµ¿ÀÌ ÇÊ¿ä reaaaly¡¦
thank Nicholas. ´ÏÄÝ¶ó½º °¨»çÇÕ´Ï´Ù. i¡¯ll keep you posted. ³ªÁß¿¡ ¿¬¶ô µå¸±°Ô¿ä.
WR! wr!