sophist@brainiac.raidernet.com (Phillip McReynolds) (01/05/91)
Does the popadbug.zoo program (386bugs[.exe,.asm] indicate a problem if a 386sx has failed it? Mine did. Should I worry? I'm hoping that this program merely detects problems with 386dx's. Regards, = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Phillip A. McReynolds, sophist@brainiac.raidernet.com Licensed Philosopher org: Phillip's Philosophy Shop, Inc. (MPA Certified) "Quality Philosophy Products Since 1990" = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
otto@tukki.jyu.fi (Otto J. Makela) (01/07/91)
In article <JggaV1w163w@brainiac.raidernet.com> sophist@brainiac.raidernet.com (Phillip McReynolds) writes:
Does the popadbug.zoo program (386bugs[.exe,.asm] indicate a problem if
a 386sx has failed it? Mine did. Should I worry? I'm hoping that this
program merely detects problems with 386dx's.
Yes, it does mean that your 386sx has the same problem than the 386dx's.
No, it is not a serious problem. You needn't lose any sleep over it...
PS. My work 386sx didn't have the problem, unfortunately the CPU is covered
by the disk drive rack so I can't see the chip revision number. I'll have to
try it on my home machine, a 386dx (which will most probably have it...)
--
/* * * Otto J. Makela <otto@jyu.fi> * * * * * * * * * * * * * * * * * * */
/* Phone: +358 41 613 847, BBS: +358 41 211 562 (CCITT, Bell 24/12/300) */
/* Mail: Kauppakatu 1 B 18, SF-40100 Jyvaskyla, Finland, EUROPE */
/* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */