Rewritten CPUID algo for testing instruction sets.

[Ficko]

...little bit mis-leading for you as English is a foriegn language to you

Damn! - I need some English lessions. :toothy -

[MichaelW]

I have a K5 system, but when the fan in the power supply on my P3 started making noise I robbed the power supply from the K5, and I keep forgetting to pick up a new one.

I don't recall anything unusual about how the K5 does CPUID.

[hutch--]

Here are the results on a Compaq AMD K6 450 running win98se. Seems to recognise MMX and 3DNow OK, AMD string is correct but no processor string.

Code Select Expand


Manufacturer = AuthenticAMD

Model ID string = i486 or early Pentium Processor

-----
INTEL
-----
0 sse4.2
0 sse4.1
0 ssse3
0 sse3
0 sse2
0 sse
1 mmx

---
AMD
---
0 sse4a
0 mmx_ex
1 3DNow
0 3DNow_ex

Press any key to continue ...


[dedndave]

try this one Hutch...

[sinsi]

I was thinking, I fix a couple of computers a fortnight and could run an info program on each of them. We could build up a database.
One thing I would like to see is family/model/stepping info to narrow it down more.

[dedndave]

Clive had written a program that did a complete CPUID dump into a file
that would be ideal for data-base collection, as all the details are there   :U
as a side-effect, it tells you which standard/extended leaves are supported, for example
the only thing you can't do programmatically is to read the part numbers on the physical package - lol

[hutch--]

Dave,

You are out of luck, it wads a junk laptop a lady gave me so I messed around and formatted a floppy, tried out a couple of test apps then it stopped. Screen went blank and it would not start. It did the only thing it could be useful for, gave me the results on an old K6.

Heading for the scrapheap real soon.  :bg

[dedndave]

lol - you always get the winners, Hutch
well - there is a little bug fix there, anyways

Ficko had 2 out of 3 right i think...

http://www.masm32.com/board/index.php?topic=13894.msg111160#msg111160

if it was sitting in her closet, the battery may have gone south (or north, down there, i guess)