Article View: comp.os.msdos.programmer
Article #1621Re: Detecting an 80486
From: exilied in my own office
Date: Thu, 19 Jul 1990 21:45
Date: Thu, 19 Jul 1990 21:45
21 lines
1643 bytes
1643 bytes
In article <1990Jul19.025150.6150@looking.on.ca> brad@looking.on.ca (Brad Templeton) writes: >For status programs that wish to detect what sort of processor they >are running on, does anybody have the scoop on official detection >procedure for an 80486? Assuming, for example, that one already knows >that one is on a 386 or better. I already have code to detect >8086, 8088, 80186, 80286, 80386, 8087, 80287 and 80387 -- I want to make >it complete. I spoke with an engineer at SCO (whose remains unnamed) who sadly told me that there was no way to tell an 80386 from an 80486. SCO wanted to market a higher-priced version of Xenix for 80486, but they could find no way to detect the difference. Pete Gregory : uucp: uunet!bally!pete | Bally Systems : domain: pete@bally.bally.com ---|--- 5270 Neil Rd, Suite 301: phone: 702-689-2485 | Reno, NV 89502 : FAX: 702-689-2417 | "God so loved the world, that he gave his only begotten son, that whosoever believes in him should not perish, but have everlasting life." John 3:16
Technical Details
Message-ID:
<315@bally.Bally.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!snorkelwacker!apple!tahoe!bally!peteReferences:
<ECOLLINS.90Jul9182101@teewi.nmsu.edu> <1990Jul19.025150.6150@looking.on.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!snorkelwacker!apple!tahoe!bally!pete From: pete@bally.Bally.COM (exilied in my own office) Newsgroups: comp.os.msdos.programmer Subject: Re: Detecting an 80486 Message-ID: <315@bally.Bally.COM> Date: 19 Jul 90 21:45:53 GMT References: <ECOLLINS.90Jul9182101@teewi.nmsu.edu> <1990Jul19.025150.6150@looking.on.ca> Reply-To: pete@bally.UUCP (exilied in my own office) Distribution: comp.os.msdos.programmer Organization: Jacks of Everything, Masters of None Lines: 21