What is the URL / path to the iso that you are downloading from that has
this problem?
On Fri, 14 Jul 2006, Austin English wrote:
That's what I thought, so yesterday I downloaded the iso on a completely
different connection/computer and it still failed the checksum. Today, r2
failed the checksum, but is installing fine (just finished installing the
kernel in fact). I didn't check to see if the checksums from yesterday's
downloads were the same or not, but I'm inclined to think they were.
Justin Piszcz <[EMAIL PROTECTED]> wrote: Perhaps some kind of network/router
issue then that is corrupting the
packets? Really strange problem there, what if you download to a
different machine that is not on the same network/connection?
On Fri, 14 Jul 2006, Austin English wrote:
Doubtful. I tried again today, downloading r2 from two different servers on two
different computers with clean ram. Both failed the checksum, but the installer
seems to be happy this time, it hasn't quit yet (it is installing the base
system from a mirror as of right now). Attached is the checksum I have for the
iso's (both matched), which seems to be correct compared to the checksum on the
debian servers.
2746efa7425b58c231327084545f0db5 *debian-31r2-i386-businesscard.iso
Justin Piszcz wrote:
On Thu, 13 Jul 2006, Austin English wrote:
I've been trying to download debian to setup a samba
server. I've downloaded the base install and the
business card net install cd's several times, from
several different mirrors, on 3 different computers,
in Firefox, Internet Explorer, and wget, with ftp and
http, but every time, the md5 checksum fails. When
attempting to install, it fails while loading
component files off the cdrom or installing the base
system (can't recall which file off hand, I'll check
tommorow). Is this a known problem for 3.1? Or are all
of my computers and internet connections coordinating
to drive me insane?
Thanks,
Austin E
Texas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Probably bad RAM.
Run memtest86.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
