Re: Exception #2 (0.0) at 0x10037d4

Article View: comp.sys.next.misc

Article #1146

Back to comp.sys.next.misc Previous Next

#1146

From: mark.d.wuest
Date: Thu, 09 Apr 1992 21:38

17 lines
886 bytes

Thanks to all the kind souls who responded to my plea!

Felix Lugo,
Neal Fowler,
Michael B. Johnson, and
Martin Bokaemper.

The problem was that I had not enable parity checking. Though
NeXTAnswers says it is not required (and even points out that you take
a performance hit by enabling it), Martin had experiences where parity
being enabled worked on some '040 machines, but not on others. A "bug"
in the early (ENIAC sp?) meaning of the word! ;-)

Thanks again!

Mark Wuest
mark.wuest@att.com

Technical Details

Message-ID: <1992Apr9.213857.4117@cbfsb.cb.att.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsg.cb.att.com!mdw

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsg.cb.att.com!mdw
From: mdw@cbnewsg.cb.att.com (mark.d.wuest)
Newsgroups: comp.sys.next.misc
Subject: Re: Exception #2 (0.0) at 0x10037d4
Message-ID: <1992Apr9.213857.4117@cbfsb.cb.att.com>
Date: 9 Apr 92 21:38:57 GMT
Sender: news@cbfsb.cb.att.com
Organization: AT&T
Lines: 17