Article View: comp.sys.next.misc
Article #1538Re: Exception #2 (0.0) at 0x10037d4
From: Paul B. Verket
Date: Fri, 10 Apr 1992 15:00
Date: Fri, 10 Apr 1992 15:00
10 lines
864 bytes
864 bytes
mdw@cbnewsg.cb.att.com (mark.d.wuest) writes: : : 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)... I've heard about the performance hit before as well but I haven't heard how much of a hit? What are your impressions? Paul Verket (NeXTmail ok)
Technical Details
Message-ID:
<29E5ADA2.6F04@deneva.sdd.trw.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!zephyr.ens.tek.com!uw-beaver!micro-heart-of-gold.mit.edu!wupost!usc!trwind!venice!gumby.dsd.trw.com!deneva!verketReferences:
<1992Apr9.213857.4117@cbfsb.cb.att.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zephyr.ens.tek.com!uw-beaver!micro-heart-of-gold.mit.edu!wupost!usc!trwind!venice!gumby.dsd.trw.com!deneva!verket From: verket@venice.sedd.trw.com (Paul B. Verket) Newsgroups: comp.sys.next.misc Subject: Re: Exception #2 (0.0) at 0x10037d4 Message-ID: <29E5ADA2.6F04@deneva.sdd.trw.com> Date: 10 Apr 92 15:00:49 GMT References: <1992Apr9.213857.4117@cbfsb.cb.att.com> Sender: news@deneva.sdd.trw.com Organization: TRW Inc., Redondo Beach, CA Lines: 10