From owner-freebsd-questions  Thu Feb 27 20:06:42 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA13094
          for questions-outgoing; Thu, 27 Feb 1997 20:06:42 -0800 (PST)
Received: from rma.edu (rma.edu [207.0.141.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA13086
          for <questions@freebsd.org>; Thu, 27 Feb 1997 20:06:30 -0800 (PST)
Received: from alwan.rma.edu ([207.0.141.30]) by rma.edu
	with SMTP (IPAD 1.51) id 4203200 ; Thu, 27 Feb 1997 22:58:08 EST
Message-Id: <3.0.1.32.19970227225139.0068809c@rma.edu>
X-Sender: alwan@rma.edu
X-Mailer: Windows Eudora Light Version 3.0.1 (32)
Date: Thu, 27 Feb 1997 22:51:39 -0500
To: questions@freebsd.org
From: Michael Alwan <alwan@rma.edu>
Subject: buffer overrun on download
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

To all:

I downloaded the xemacs-19.14.tgz package using user ppp and Netscape
Communicator 4.0b2.  I noticed after the download was finished some consol
messages about buffer overruns.

When I tried to install the package, I got a lot of error messages saying
various files "don't really exist."  Anybody think this had to do with a
communications problem, e.g. the buffer overruns?  Could the size of the
file (about 13mb) have anything to do with this, or the default speed
(115200) of my ppp connection?

I'm downloading the file again with the  Windows ftp program that I got the
2.1.7 BSD distribution with, but while I wait, just wondering what went
wrong the first time.

Thanks,

Michael Alwan