[Python-bugs-list] [ python-Bugs-487317 ] tcl83.dll is corrupt
noreply@sourceforge.net
noreply@sourceforge.net
Fri, 30 Nov 2001 19:48:12 -0800
Bugs item #487317, was opened at 2001-11-29 17:11
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=487317&group_id=5470
Category: Installation
>Group: Not a Bug
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Barry Kumnick (barryk)
Assigned to: Tim Peters (tim_one)
Summary: tcl83.dll is corrupt
Initial Comment:
On NT4 SP6, installation of Python-2.1.1.exe fails
with an error message saying tcl83.dll is corrupt.
The downloaded file size is correct - 6,310,277 bytes.
----------------------------------------------------------------------
>Comment By: Tim Peters (tim_one)
Date: 2001-11-30 19:48
Message:
Logged In: YES
user_id=31435
I'm closing this now since your other unique bug was traced
to a corrupt installer. From the Pythonic point of vies,
Download Accelerator Plus is clearly too fancy to trust
<wink>.
----------------------------------------------------------------------
Comment By: Barry Kumnick (barryk)
Date: 2001-11-30 18:02
Message:
Logged In: YES
user_id=389562
I downloaded it from python.org via ftp using the
registered version of Download Accelerator Plus (DAP)
version 5.0.0.1.
This utility simultaneously establishes four different
connections to four different mirror sites and merges the
files when the download is complete. It also supports
suspend and resume. Alas, I don't have a record of the
mirror sites the download actually came from. I did have
some problems with the TCP connection timing out a couple
of times and I had to restart the download. Perhaps that
caused some problem. I don't know. I'll try the download
using straight ftp from python.org and let you know how it
goes.
Thanks,
Barry Kumnick
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-11-30 15:50
Message:
Logged In: YES
user_id=31435
Barry, from exactly where are you downloading the
installer? SourceForge? python.org? If the latter, via
HTTP or via FTP? Which program are you using to download?
It's remotely possible that one of the master copies
recently got corrupted, and if you tell me where you're
getting it from, I'd be happy to try downloading it myself
too.
I hate to mention it, but some corporations are known to
run firewalls that systematically corrupt binary downloads.
----------------------------------------------------------------------
Comment By: Barry Kumnick (barryk)
Date: 2001-11-30 15:11
Message:
Logged In: YES
user_id=389562
I got the md5sum to work. It is reporting a different
checksum than the one you provided, so the downloaded file
must have been corrupted. I'll try to download a new copy.
Thanks for your help.
Barry Kumnick
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-11-30 14:54
Message:
Logged In: YES
user_id=31435
It sounds like you were trying to run md5sum with its "-c"
switch: don't. Do it like so:
C:\Code>\updates\md5sum Python-2.1.1.exe
39ef54d3e29ea402c8b693b4f3fedd4a *Python-2.1.1.exe
C:\Code>
There are no corrupt files in the installers we ship, so
stop trying to pursue that path: you'll just get in worse
trouble if you do. Something else is hosed on your system.
BTW, you can open the installer (as a file!) in WinZip, and
use WinZip's Action -> Test to test for corruption. md5 is
a more powerful whole-file check, but the installer saves a
CRC code for each individual file and that's what the
WinZip Test looks at. If either md5 or WinZip complains,
your installer got corrupted during (or maybe even after)
downloading.
----------------------------------------------------------------------
Comment By: Barry Kumnick (barryk)
Date: 2001-11-30 14:34
Message:
Logged In: YES
user_id=389562
Hi,
Thanks for getting back to me.
First I have a correction to make: it was the tk83.dll not
the tcl83.dll that was reported as corrupt.
Actually, I am running NT 4 Enterprise Server SP6 on a dual
processor PIII box.
I tried to install on another box running NT 4 Enterprise
Server SP5 with a single processor, and got the same error.
However, on that machine I was able to keep pressing retry,
and the progress bar kept advancing. In fact it went up a
few percent every time I pressed the retry button on the
error dialog. It continued to advance past 100%. I stopped
trying after it got to around 113% and it said the system
needed to be rebooted to complete the installation. I did
that. Apparently, everything installed except the tk83.dll.
I also tried the md5sum.exe application Martin suggested,
but it reports:
md5sum: Python-2.1.1.exe: no properly formated MD5 checksum
lines found.
Do you have another suggestion for computing the MD5
checksum? I don't have md5sum.py on my system.
BTW: With the current 2.1.1 installation, I was able to get
the Python command shell to execute, but when attempting to
launch IDLE, it fails with an error message saying the
tk83.dll can not be found.
Is there somewhere I can download the tk83.dll separately
as a workaround?
Thanks,
Barry Kumnick
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-11-30 09:43
Message:
Logged In: YES
user_id=31435
Thanks for finding that program, Martin! This should be
received much better than my usual advice to compute MD5
with md5sum.py <wink>.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2001-11-30 08:19
Message:
Logged In: YES
user_id=21627
Can you please verify the md5sum of the file you've
downloaded? It is
39ef54d3e29ea402c8b693b4f3fedd4a Python-2.1.1.exe
You can get an md5sum executable from
http://etree.org/md5com.html
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2001-11-29 18:25
Message:
Logged In: YES
user_id=31435
Tens of thousands of Windows users have run this installer
without problems, so-- and especially given your other bug
report about 2.2b2 --the presumption has to be that
something is uniquely screwed up on the specific box you
tried it on. Can you reproduce on another (physically
distinct) machine?
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=487317&group_id=5470