From: SourceForge.net <no...@so...> - 2004-05-26 18:21:38
|
Feature Requests item #958995, was opened at 2004-05-23 10:06 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=958995&group_id=22049 Category: General Group: 2.0 Series Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Need AMD64 support Initial Comment: At some point NSIS will need to support AMD64. You can't install 64-bit Windows apps with a 32-bit installer. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-05-26 11:21 Message: Logged In: NO A real 64-bit installer isn't just nice, it will become an absolute requirement. Only a 64-bit installer can place 64-bit DLL's in System32 or install device drivers. 32-bit processes running on Win64 do not have access to the real \Windows\System32 directory. They think they do, but behind the scenes Windows is redirecting them to \Windows\SysWOW64. On Win64, the System32 directory contains the 64-bit binaries, while SysWOW64 contains the 32-bit binaries (I know this sounds completely backwards, but that is the way it works! Leave it to Microsoft!). ---------------------------------------------------------------------- Comment By: Amir Szekely (kichik) Date: 2004-05-25 04:01 Message: Logged In: YES user_id=584402 Why wouldn't you be able to install 64-bit applications using 32-bit installers? As far as I know 32-bit applications will still work on 64-bit operations systems just like 16-bit applications still work on 32-bit operation systems. An installer is a regular application. It is, however, agreed that a native 64-bit version would be nice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373088&aid=958995&group_id=22049 |