From owner-freebsd-hardware  Tue Jul  8 12:42:08 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA03805
          for hardware-outgoing; Tue, 8 Jul 1997 12:42:08 -0700 (PDT)
Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03794
          for <freebsd-hardware@FreeBSD.ORG>; Tue, 8 Jul 1997 12:41:57 -0700 (PDT)
Received: by gw1.asacomputers.com id JAA09129; Tue, 8 Jul 1997 09:42:01 -0700 (PDT)
Message-Id: <2.2.32.19970708193828.008a0004@gw1>
X-Sender: rajadnya@gw1
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 08 Jul 1997 12:38:28 -0700
To: dburr@POBoxes.com
From: Kedar <kedar@asacomputers.com>
Subject: Re: more about my hardware problem - could it be EDO related?
Cc: freebsd-hardware@FreeBSD.ORG
Sender: owner-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

        If you're board is a 486/66, I very much doubt if it'll be
EDO-compatible.  Frankly, I'm surprised that the system even works close to
"properly".
        Try to get a regular FPM module.  Parity might be recommended in the
motherboard manual.

Best,
Kedar.

At 10:40 AM 7/6/97 GMT, you wrote:
>The memory installed in my machine is a 16MB 60ns 72-pin SIMM module.
>Nothing terribly unusual about this, except that this is an EDO SIMM.
>And the motherboard's manual mentions nothing about EDO.

>Well, the system hasn't died or burst into flames (yet...), but
>neither is it working 100% "properly" either.  So could this be my
>problem?  And does anyone out there know more about this issue (use of
>EDO memory in a possibly non-EDO motherboard, etc.)