MSVCRT.DLL screws up the system

[pholmstrom]

BPO	824016
Nosy	@theller

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/theller'
closed_at = <Date 2003-10-16.19:16:21.000>
created_at = <Date 2003-10-15.10:05:30.000>
labels = ['OS-windows']
title = 'MSVCRT.DLL screws up the system'
updated_at = <Date 2003-10-16.19:16:21.000>
user = 'https://bugs.python.org/pholmstrom'

bugs.python.org fields:

activity = <Date 2003-10-16.19:16:21.000>
actor = 'theller'
assignee = 'theller'
closed = True
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2003-10-15.10:05:30.000>
creator = 'pholmstrom'
dependencies = []
files = []
hgrepos = []
issue_num = 824016
keywords = []
message_count = 2.0
messages = ['18640', '18641']
nosy_count = 2.0
nosy_names = ['theller', 'pholmstrom']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue824016'
versions = []

[pholmstrom]

This applies to the Windows version of Python 2.3.2.

When a friend of mine installed Python onto his
computer (running Windows NT 4) the entire system got
screwed up and he had to reinstall the operating system
and all applications. The errors reported all had to do
with unresolved symbols in the MSVCRT.DLL -file.
Uninstalling Python did not help.

I also encountered a similar problem. After installing
Python on a Windows NT 4 machine Quattro Pro 9 would
not start, complaining about unresolved symbols in the
MSVCRT.DLL -file. When I uninstalled Python and rolled
back the changes QP started just fine.

[theller]

Logged In: YES
user_id=11105

I'm really sorry for this - there were wrong MS dlls
included in the installer for Python 2.3.2.

A new installer has been created, and can be downloaded in
the usual place. The filename has changed to Python-2.3.2-1.exe.