Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!news.funet.fi!tukki.jyu.fi!jyu.fi!otto From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: popadbug for 386sx or merely dx? Message-ID: Date: 7 Jan 91 05:56:44 GMT References: Sender: news@tukki.jyu.fi (News articles) Organization: Turing Police, Criminal AI section Lines: 16 In-Reply-To: sophist@brainiac.raidernet.com's message of 5 Jan 91 06:41:54 GMT Nntp-Posting-Host: jyu.fi In article 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 * * * * * * * * * * * * * * * * * * */ /* 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 * * * * * * * * * * * * * * * * */