Article View: alt.comp.hardware
Article #2111Re: Q - Parity Error, System Halted
From: James Navas
Date: Fri, 22 Nov 1996 00:00
Date: Fri, 22 Nov 1996 00:00
12 lines
1482 bytes
1482 bytes
First, you're wrong about the color of the contacts indicating parity vs. non-parity. The color (silver or gold) depends completely on the manufacturer and how they plated the DRAM module. Second, non-parity are known as ...x32, parity modules as ...x36. Third, there are even faster DRAM chips (modules) than you quoted, i.e. 50ns. Fourth, with modern mobos and BIOS, parity is becoming a thing of the past. Error checking is done in other ways (too long to go into here), and reliably so. Thus parity checking, especially with non-parity modules can lead to false errors. Hope this helps.
Technical Details
Message-ID:
<3296A85B.58E3@pacbell.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3290B0A7.3215@swbell.net> <3290BEAD.7457@pacbell.net> <3292AB4D.3551@thenet.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f8e37,b9ac55a17ca536c8 X-Google-Attributes: gidf8e37,public X-Google-Thread: 10265e,b9ac55a17ca536c8 X-Google-Attributes: gid10265e,public X-Google-Thread: f5f89,b9ac55a17ca536c8 X-Google-Attributes: gidf5f89,public X-Google-Thread: 112149,b9ac55a17ca536c8 X-Google-Attributes: gid112149,public From: James Navas <JNavas1@pacbell.net> Subject: Re: Q - Parity Error, System Halted Date: 1996/11/22 Message-ID: <3296A85B.58E3@pacbell.net> X-Deja-AN: 198225549 references: <3290B0A7.3215@swbell.net> <3290BEAD.7457@pacbell.net> <3292AB4D.3551@thenet.net> content-type: text/plain; charset=us-ascii organization: Navas & Associates mime-version: 1.0 reply-to: JNavas1@pacbell.net newsgroups: alt.comp.hardware,biz.comp.hardware,comp.hardware,comp.ibm.pc.hardware, x-mailer: Mozilla 3.0Gold (Win16; U)