Closed GoogleCodeExporter closed 9 years ago
This may be the same issue I just reported as #57. See if installing the 64-bit
version of MSVCR100.DLL fixes it.
Original comment by btcoooo...@gmail.com
on 12 Jun 2013 at 9:29
Following btcoooo...'s advice in issue #57, I attempted to install a 64-bit
version of MSVCR100.DLL. Either I was not successful (do not have admin, so
copied a similar DLL from c:\windows\SysWOW64) or the problem lies elsewhere.
Every attempt to open a any python results in a 0xc000007b error.
Except, oddly, py.exe in python-3.3.2-amd64 folder opens another (32-bit 2.6.6)
instance of python on the same machine and python.exe in same folder tries to
open the winpython 3.3.2.0 instance and fails. Is that behavior expected? I
expected all facets of winpython to be isolated from all other versions of
python.
Nothing changes for 3.3.2.1--still broken for me.
Original comment by haven...@gmail.com
on 14 Jun 2013 at 3:00
I believe the DLLs in SysWOW64 are 32-bit. Try getting the DLL from here:
http://www.microsoft.com/en-us/download/details.aspx?id=14632
If you already have Python 3.3 installed on your machine then the behavior you
describe in your second paragraph is probably due to the new Python launcher
for Windows, as described here:
http://docs.python.org/3/whatsnew/3.3.html#pep-397-python-launcher-for-windows
Original comment by btcoooo...@gmail.com
on 17 Jun 2013 at 3:19
I confirm that, on a 64-bit Windows platform, DLLs located in SysWOW64 are
32-bit whereas DLLs located in System32 are 64-bit (odd but true...).
Original comment by pierre.raybaut
on 17 Jun 2013 at 3:39
Original comment by pierre.raybaut
on 15 Aug 2013 at 7:45
Original issue reported on code.google.com by
haven...@gmail.com
on 5 Jun 2013 at 12:41