From owner-freebsd-questions Sun Mar 30 19:14:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA09318 for questions-outgoing; Sun, 30 Mar 1997 19:14:25 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09312 for ; Sun, 30 Mar 1997 19:14:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id TAA06364; Sun, 30 Mar 1997 19:15:31 -0800 (PST) Message-Id: <199703310315.TAA06364@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: adam@choice.net (Mark Knipfer) cc: interrupt request , freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD v2.1.7 In-reply-to: Your message of "Sun, 30 Mar 1997 21:44:14 EST." <33402451.6995721@mail.choice.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 30 Mar 1997 19:15:31 -0800 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >why I am having the problems. You can rule out memory, unless FreeBSD is= > not >compatible with EDO memory. It's compatible, but FreeBSD is a much higher user of memory (every last bit) than most other operating systems. This wouldn't be the first time that someone said that it worked fine with Windows, but nonetheless turned out to be bad. There really aren't a lot of possibilities here. I have two P5/133 machines here - Triton II, 64MB, EIDE mode 4...nearly identical to your configuration. Needless to say, we wouldn't have done a release if I had any problems here on these machines. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project