|
Yah, there's always a cynic in the crowd! ;-) And then he said, "But Microsoft is unlike any other vendor in the universe." Oh stop, enough preaching to the choir! Anyway, took John's advice, and ran MemTest86 overnight; no problems showed on the standard tests after 14 passes. Running the extended tests today while I'm at work. Based on the web site documentation, it *sounds* like this is about as thorough a memory tester as one's gonna find anywhere. John, the Mersenne.org link: I understand that this app probably exercises the CPU pretty well, but how does one know whether it finds problems with the CPU? It's not a "tester" per se. db > -----Original Message----- > From: pctech-bounces@xxxxxxxxxxxx / Tom Liotta > > Hmmm... of course, that _would_ make Windows seem a bit nicer if what MS > says is true. If it was just some marketecture b.s. as it sounds like, > it'd just be a way to divert attention. But I'm _sure_ no vendor would > ever do anything like that. > > OTOH, a google on "ram execute write read cycle" brings up quite a few > non-MS technical docs that don't seem to show a significant difference > in memory itself between normal memory reads/writes and what happens > during a fetch/execute cycle... > > Tom Liotta > > > Dan Bale wrote: > > That's what I would think, as well, but M$ seems to go out of > its way to say > > otherwise. > > > > Thanks, > > db
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.