Article View: comp.sys.ibm.pc.misc
Article #191Parity error - HALT - a better NMI handler?
From: Chuck Colford
Date: Tue, 03 Nov 1992 22:18
Date: Tue, 03 Nov 1992 22:18
24 lines
1484 bytes
1484 bytes
To: comp.sys.ibm.pc.misc
From: chuck.colford@synapse.isis.org
Alas; I am not alone. I am plagued by the occasional parity error too.
Chris Granitz recently recanted his story & it sounds all too familier.
I'm a H/W engineer, so I've gone through most of what I can check (mem
speeds, cache data/tag ram speeds, bus speeds, looked for "pushed
parts", etc). Still they persist, but I hate to turn off checking.
Speeds of 33 MHz and up are challenging & require good design & layout
practice. Perhaps all the clone designs do not all allow adequate
margins.
What I would really like to see is a program (TSR or config.sys driver)
that would intrcept the NMI and report the address & byte where it
thinks the error occurred. This should be a protected mode program &
windows compatable. This would be more inspiring than PARITY ERROR -
SYSTEM HALTED.
Does anyone have such a program? If so, I would appreciate an email
copy.
...Chuck
Technical Details
Message-ID:
<3132.2404.uupcb@synapse.org>Path:
arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!uunet.ca!synapse!chuck.colfordShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ogicse!uwm.edu!zaphod.mps.ohio-state.edu!uunet.ca!synapse!chuck.colford From: chuck.colford@synapse.org (Chuck Colford) Newsgroups: comp.sys.ibm.pc.misc Subject: Parity error - HALT - a better NMI handler? Message-ID: <3132.2404.uupcb@synapse.org> Date: 3 Nov 92 22:18:00 GMT Article-I.D.: synapse.3132.2404.uupcb Reply-To: chuck.colford@synapse.org (Chuck Colford) Distribution: world Organization: SYNAPSE BBS - GATINEAU, QUEBEC - 819-561-4321 Lines: 24