KS> I was wondering what would cause windows 3.1 to give me a
KS> memory parity error?
It's the hardware that detects the parity error and the BIOS that reports it, 
not the software or OS, I believe.  May not happen under DOS because DOS 
isn't using the part of memory that is flaky.
I suggest you try removing and reseating your SIMMs -- the  contacts 
sometimes get corrosion on them, esp. if you have gold-tip SIMMs in a tin 
socket.  Ground yourself before touching SIMMs or any electronics.  Push the 
clips on each end of the SIMM outward then swing the SIMM forward about 30 
degrees to release it from its slot.  A pencil eraser can be used (gently!) 
to remove any visible crud on the SIMMs.
Try running a memory test program like in Norton's NDIAGAS if  you still have 
problems.  Or replace your SIMMs one-by-one with  a know good SIMM until the 
problem goes away.  If it doesn't I'd suspect the mo'board. 
KS> Ive heard that if the memorys wait states are to fast, you
KS> can get this, but it still does it when its set to 3WS
Yup, but 3 WS should be plenty.
... OFFLINE 1.50
--- InterEcho 1.19
---------------