home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!emory!athena.cs.uga.edu!mcovingt
- From: mcovingt@athena.cs.uga.edu (Michael A. Covington)
- Newsgroups: comp.os.ms-windows.misc
- Subject: Re: Memory parity error detected. SYSTEM HALTED.
- Summary: Resembles a problem I've seen before...
- Keywords: WINDOWS 3.1, CRASH
- Message-ID: <1992Sep16.014400.18619@athena.cs.uga.edu>
- Date: 16 Sep 92 01:44:00 GMT
- References: <1992Sep12.234254.6893@techbook.com> <1992Sep13.061626.8684@ee.ubc.ca> <1992Sep15.212248.6309@techbook.com>
- Organization: University of Georgia, Athens
- Lines: 20
-
- In article <1992Sep15.212248.6309@techbook.com> jwettern@techbook.com (Joern Wettern) writes:
-
- >>>>> SYSTEM ERROR: Memory parity error detected. System halted.
- >
- >It doesn't seem like it. Any kind of memory test reports no error. Floppy
- >access under Win 3.1 is the only thing that makes the system crash.
-
- Aha! Very similar to a design defect in the original Zenith Z-201, which
- crashes with a parity error _only_ when you copy diskette files under
- Word Perfect!
-
- The problem was that the designers did not allow enough time for memory
- access. Even when you use chips of the rated speed, at _certain_ high
- addresses you get _frequent_ (not every time) crashes.
-
- We solved it by getting new memory boards.
-
- --
- + Michael Covington - Artificial Intelligence Programs - U of Georgia - USA
- + Unless otherwise noted, these are private opinions, not official statements.
-