home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!linac!att!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: OS2 WINS!! I give up!
- Message-ID: <1992Aug28.200235.7250@njitgw.njit.edu>
- Date: 28 Aug 92 20:02:35 GMT
- References: <1992Aug27.015416.6882@maccs.dcss.mcmaster.ca> <1992Aug27.030506.4609@midway.uchicago.edu> <liuyu.714945700@kramden>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 27
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <liuyu.714945700@kramden> liuyu@kramden.nyu.edu (Liuyu) writes:
- >>Due to some recent experience one should also suspect the RAM cache.
- >>Some vendors, it seems, cut corners and supply slightly out of spec
- >>cache memory, substituting cache that is too slow for the system.
- >>This, too, can result in memory parity errors.
- >
- >Can you explain why this happens only under OS/2? Is it just another excuse,
- >blaming hardware? Does it happen under other complex programs like Unix or
- >Novell? Thanks.
-
- OS/2, due to it s high amount of context switching, has some strange
- ability to push intermittently bad memory over the edge. It's
- happened on many computers. Replacing the memory usually works to
- cure it.
-
- My father's computer at work had its memory "pushed over the edge" by
- Windows 3.1. So it's nothing inherent in OS/2. (And when Windows 3.1
- died, it took most of his /Windows directory with it - a complete
- re-install of Windows and all Windows apps had to be performed).
- Again, replacing the memory cured everything.
-
-
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-