Anomalies in the Intel® Pentium® III Processor Specification Update

Reply 20 of 131, by red-ray

Posted on 2025-05-04, 14:02

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-04, 13:30:
Do you have all the CPUID's in the same look-up database ?

It's actually a constant C structure and all the CPUID/S-Spec SIV knowns about are in the same structure, but it does not have "all the CPUID's" there are only 689 entries starting with 0400 486DX and currently ending with 068A SL5QK, the same CPUID is usually there multiple times, once for each S-Spec. It started with i486 ones to populate the dropdown and I have added more over time.

file.php?id=218567

Reply 21 of 131, by PARKE

Posted on 2025-05-05, 11:11

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

Yes, sorry, I meant S-Spec but wrote CPUID.
'Costant C structure' is above my head.
I have started working on my P2/P3 database to reduce the number of (possible) discrepancies. Btw, I think there is some suspect stuff on CPUW too.

Reply 22 of 131, by red-ray

Posted on 2025-05-05, 15:40

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-05, 11:11:
'Costant C structure' is above my head.

It's quite simple, I defined a structure with all the components and then populated it. F400 means the CPUID is unknown.

What form does your database take, I suspect I could get SIV to cross check it with it's.

CONST C Structure

1typedef struct _CPU_SSPEC                       // CPU S-Spec Block
2{                                               //
3           BYTE         otf;                    // On The Fly
4           BYTE         sle;                    // SL Enhanced
5           WORD         cid;                    // CPUID
6           WORD         rev;                    // Revision
7  CONST    TCHAR       *nam;                    // CPU Name
8  CONST    TCHAR       *ssp;                    // CPU S-Spec
9  CONST    TCHAR       *stg;                    // CPU Stepping
10  CONST    TCHAR       *dat;                    // CPU Date
11  CONST    TCHAR       *not;                    // CPU Notes
12} CPU_SSPEC;                                    //
13
14#define INI_SSPEC( otf, sle, cid, rev, nam, ssp, dat, stg, not ) { otf, 0x ## sle, 0x ## cid, 0x ## rev, TEXT( #nam ), TEXT( #ssp ), TEXT( #dat ), TEXT( #stg ), TEXT( not ) }
15
16CONST    CPU_SSPEC    ssb[] =                   //
17{ //               CPUID  Rev   Processor         S-Spec     Stepping  Date    Notes
18  INI_SSPEC( 0, 00, 0400, 0000, 486DX,            ?,         A0+A1,    ?,      ""                           ),
19  INI_SSPEC( 0, 00, 0401, FFB0, 486DX-25,         SX308,     B2-B6,    89,     ""                           ),
20  INI_SSPEC( 0, 00, F400, 0000, 486DX-25,         SX249,     ?,        89,     ""                           ),
21  INI_SSPEC( 0, 00, F400, 0000, 486DX-25,         SX250,     ?,        89,     ""                           ),
22  INI_SSPEC( 0, 00, F400, 0000, 486DX-25,         SX493,     ?,        89,     "Low Power"                  ),
23  INI_SSPEC( 0, 00, F400, 0000, 486DX-33,         NA,        ?,        89,     "IBM PN 63G9145"             ),
24...

Reply 23 of 131, by PARKE

Posted on 2025-05-06, 10:58

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

I use an old Paradox database program but I can export into the common formats for you - spreadsheet or comma delimited txt etc.
Are you in contact with people from CPUW ? I wonder where they got the S-Specs from that do not occur in the spec updates that we have.

Reply 24 of 131, by red-ray

Posted on 2025-05-06, 11:35

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-06, 10:58:
comma delimited txt
I wonder where they got the S-Specs from that do not occur in the spec updates that we have.

Thank you, for me a .CSV file would be simplest, once I get it I suspect it won't take long for me to get SIV to import it into I suspect a CPU_SSPEC table and cross check things.

I have never managed to get in contact with them, it's also possible if they have it's NDA. Some time ago I sent them an e-mail asking if it was OK for SIV to open such as https://www.cpu-world.com/sspec/SX/SX308.html and as yet have not got a reply.

Reply 25 of 131, by PARKE

Posted on 2025-05-06, 13:22

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

red-ray wrote on 2025-05-06, 11:35:

PARKE wrote on 2025-05-06, 10:58:
comma delimited txt
I wonder where they got the S-Specs from that do not occur in the spec updates that we have.

Thank you, for me a .CSV file would be simplest, once I get it I suspect it won't take long for me to get SIV to import it into I suspect a CPU_SSPEC table and cross check things.

I have never managed to get in contact with them, it's also possible if they have it's NDA. Some time ago I sent them an e-mail asking if it was OK for SIV to open such as https://www.cpu-world.com/sspec/SX/SX308.html and as yet have not got a reply.

Will let you know when I am done checking - may take a day or so.
I ran into a site where someone stored what seems to be the entire S-Spec collection of CPUW (or at some point entire):
https://github.com/zymos/cpu-db/blob/master/s … pec_numbers.csv
I downloaded this csv version and it imported seamlessly (the columns are only delimited with a comma).

Reply 26 of 131, by red-ray

Posted on 2025-05-06, 13:37

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-06, 13:22:
Will let you know when I am done checking - may take a day or so.

I ran into a site where someone stored what seems to be the entire S-Spec collection of CPUW (or at some point entire):
https://github.com/zymos/cpu-db/blob/master/s … pec_numbers.csv

OK, may I have say say the first 20 lines so I can write the code so I am ready please?

I have a quick look at this and it does not seem to have the CPUID which makes to next to useless for SIV, does your database have the CPUID?

Reply 27 of 131, by PARKE

Posted on 2025-05-06, 14:40

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

Yes, my database contains some 450 PII/PII/Celeron entries but 24 CPUID's are missing. Here a comma delimited txt file with the Deschutes. First line contains the titles.
SL2SP is, btw, interesting. Cannot find anything on it but for one mention by a Vogons member:
Re: Which Pentium IIs can be underclocked?

The attachment ANSWER.txt is no longer available

Reply 28 of 131, by red-ray

Posted on 2025-05-06, 17:53

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-06, 14:40:
Here a comma delimited txt file with the Deschutes.
SL2SP is, btw, interesting. Cannot find anything on it but for one mention by a Vogons member:
Re: Which Pentium IIs can be underclocked?

Thank you, as I suspected it was simple enough to get SIV to read it, but when I opened it in Excel the columns were wonky, I wonder do some of the entries contain commas? If so can it be exported as a .TSV (Tab Separated Values) file? It's usual to generate such as one,two,"three , 3", four when there are commas, but a .TSV is easier to parse.

SIV did not find any conflicts, but I had not added a couple of the 66 MHz FSB P-IIs so I did. Below is what I got after adding a couple of 🐛 to the .CSV file.

Last edited by red-ray on 2025-05-06, 20:37. Edited 1 time in total.

Reply 29 of 131, by PARKE

Posted on 2025-05-06, 18:45

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

Sorry for the comma issue I'm a bit rusty. The column with notes contains comma's and I should have used another delimiter. The original file was started with tables that came one on one from the Intel spec sheets and the notes refers to the originl notes at the end of the tables.
It is probably simpler for you if I sent you a file with just the columns that you need and in the order from left to right that works the best for you. et me know.
I do not see the problem in the output that you posted above here ?

Reply 30 of 131, by red-ray

Posted on 2025-05-06, 20:37

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-06, 18:45:
I do not see the problem in the output that you posted above here ?

file.php?id=218709

I edited the [dB0] + [dA1] in the .CSV file to [dBo 🐛] + [dA1 🐛] so I could check that SIV reported an issue.

Can't I just have a TAB rather than COMMA separated values file, see https://en.wikipedia.org/wiki/Tab-separated_values, I can't imagine you have tabs in the data.

Reply 31 of 131, by PC Hoarder Patrol

Posted on 2025-05-07, 04:42

PC Hoarder Patrol Offline

Rank l33t

Rank: l33t
Posts: 2355
Joined: 2018-03-04, 19:59

Finally got round to the promised check!...

The attachment SL49G.jpg is no longer available

The attachment SIV_SL49G.png is no longer available

Reply 32 of 131, by red-ray

Posted on 2025-05-07, 05:26

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PC Hoarder Patrol wrote on 2025-05-07, 04:42:
Finally got round to the promised check!...

Thank you it's [cB0] as I suspected it would be and not [cD0], the images also confirm the year as 2000.

I wonder why SIV didn't report much for GPU-1 + GPU-2, what are they please? What does Menu->Machine->GPU Info report? At a guess Voodoo 1 or 2.

Reply 33 of 131, by PARKE

Posted on 2025-05-07, 07:54

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

red-ray wrote on 2025-05-06, 20:37:

I edited the [dB0] + [dA1] in the .CSV file to [dBo 🐛] + [dA1 🐛] so I could check that SIV reported an issue.
Can't I just have a TAB rather than COMMA separated values file, see https://en.wikipedia.org/wiki/Tab-separated_values, I can't imagine you have tabs in the data.

Oh, I see... you introduced some marker thingy for issues.
Tabs are fine, try this - see attached

The attachment SSpec.txt is no longer available

In the second column [issue] stands for problem or for untraceable (besides CPUW/Wiki) and checked means that I found proof of existance.

Reply 34 of 131, by red-ray

Posted on 2025-05-07, 10:16

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-07, 07:54:
Tabs are fine, try this - see attached

Thank you, I feel TABs work well and the file is way easier to read.

I am still working on my parsing, but noted SL27Z is not in the SIV table or Intel .PDF file, but SL2Z7 is, I feel this is a typo, do you?

Reply 35 of 131, by PARKE

Posted on 2025-05-07, 10:59

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

Yes, they are both listed at CPUW but only SL2Z7 seems legit to me. This sort of thing gets a life of its own when hardware sellers and database copyers start to repost them. SL27Z is f.e. still for sale 😀

Reply 36 of 131, by PARKE

Posted on 2025-05-07, 11:13

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

But for your purpose it is not a big deal when you have couple of n0n-existing S-Specs in there - nobody will ever run into them, right ? Double entries are your main pain in the butt.

Reply 37 of 131, by red-ray

Posted on 2025-05-07, 12:37

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-07, 11:13:
Double entries are your main pain in the butt.

Not really, they just seem wrong to me so I comment them out.

There are a couple with stepping cB0c in the S-Spec update, I feel it's an Intel typo, do you. In your file one is cB0c and the other cB0.

SIV does not as yet have Celerons so it's skipping them. I have got as far as below and will think about these later. With such as SL5BR there is not CPUID so what does checked mean?

Checkout of S-Spec

1[Check CPU S-Spec] <- SIV32L - System Information Viewer V5.81 Beta-07 RED::ray
2
3SIV32L - Checkout of S-Spec on \\RED - Windows 10 x64 Enterprise  V10.00  Build 19045  22H2
4
5CPUID  Processor              S-Spec    Expected  Actual  CPUID  Reason                Description
6
7?      Coppermine-600 [cD0]   SL5BR                                                    Unknown - checked
8?      Coppermine-650 [cD0]   SL5BU                                                    Unknown - checked
9?      Coppermine-666 [cD0]   SL5B6                                                    Unknown - issue
10?      Coppermine-800 []      SL65C                                                    Unknown - issue
11068A   Coppermine-850 [cD0]   SL49G(2)                                                 Unknown - issue
12068A   Coppermine-866 [cD0]   SL49H(2)                                                 Unknown - issue
13?      Coppermine-866 []      SL5HK                                                    Unknown - issue
140683   Coppermine-933 [cB0]   SL49J                                                    Unknown - checked
15?      Coppermine-933 [cD0]   SL5B4                                                    Unknown - checked
16?      Coppermine-933 []      SL5HL                                                    Unknown - issue
17?      Coppermine-500 [cA0]   SL3US                                                    Unknown - issue
180683   Coppermine-533 [cB0c]  SL44W     cB0       cB0c    0683   Coppermine-533 [cB0]  Pentium IIIEB 256K
190681   Coppermine-650 [cA2]   SL3NC                                                    Unknown - checked
20?      Coppermine-666 [cC0]   SL4G6                                                    Unknown -
210681   Coppermine-700 [cA2]   SL3SB(2)                                                 Unknown - issue
220681   Coppermine-800 [cA2]   SL4G7(2)                                                 Unknown - issue
230683   Coppermine-866 [cB0]   SL47S                                                    Unknown - checked
24?      Coppermine-1000 [cD0]  SL5L7                                                    Unknown - issue
25?      Coppermine-866 [cD0]   SL5HG                                                    Unknown - issue
26?      Coppermine-933 [cD0]   SL5HH                                                    Unknown - issue
270633   Klamath-233 [C0]       SL2TK                                                    Unknown - checked
280633   Klamath-266 [C0]       SL2PV                                                    Unknown - issue
290634   Klamath-266 [C1]       SL2QD                                                    Unknown - issue
3006B4   Tualatin-1133 [tB1]    SL6JK                                                    Unknown -
3106B4   Tualatin-1200 [tB1]    SL6JL                                                    Unknown -
32?      Tualatin-1333 []       SL6HS                                                    Unknown - issue
3306B4   Tualatin-1400 [tB1]    SL6C2                                                    Unknown - checked
34?      Tualatin-1400 []       SL6HR                                                    Unknown - issue
3506B4   Tualatin-1133 [tB1]    SL6JM                                                    Unknown -
3606B4   Tualatin-1266 [tB1]    SL6JN                                                    Unknown -
3706B1   Tualatin-1400 [tA1]    SL5XL                                                    Unknown - checked
3806B4   Tualatin-1400 [tB1]    SL6JP                                                    Unknown -
39?      Tualatin-1000 [tA1]    SL5PS                                                    Unknown - issue
40
41Checked 315 entries from D:\SIV\SSpec.tsv in 0.000 seconds, found 1 issue and 32 missing
42
43[  OK ]  [ Copy]   [i486 S-Spec][Pentium Spec][Skt 8 S-Spec][Slot S-Spec][CuMine Spec][Chk S-Spec][CPU S-Spec]

Reply 38 of 131, by PARKE

Posted on 2025-05-07, 13:38

PARKE Online

Rank Oldbie

Rank: Oldbie
Posts: 1133
Joined: 2015-07-31, 12:46

I don't know if the extra c's mean anything; maybe if you ever run into such cpu it would show ?
The [checked] means that I found photo's or dead Intel links via Google that prove that they exist(ed) outside of CPUW or Wiki. In the past I also picked up a couple from the Intel ARK website
[[https://ark.intel.com/content/www/us/en/ark/p … 00-mhz-fsb.html]]
which does not exist in that format anymore plus that Intel has stopped providing info on pre-Pentium 4 cpu's.
The ARK website info did not come with CPUID's.
You can take a look at the 'checked' ones in this Word file.

The attachment CheckSSpec.doc is no longer available

Reply 39 of 131, by red-ray

Posted on 2025-05-07, 15:45

red-ray Offline

Rank Oldbie

Rank: Oldbie
Posts: 1636
Joined: 2019-05-21, 07:08
Location: England

PARKE wrote on 2025-05-07, 13:38:
I don't know if the extra c's mean anything; maybe if you ever run into such cpu it would show ?

They are Intel typos, if you lave them there it should say typo where is says checked.

I am down to as below and I also added the check to see if you have any missing, found four which are all in the S-Spec update along with 100 Xeons which I did not list, do you plan to add Xeons, Pentium Pro, Pentium or i486?

Checkout of S-Spec on \\RED

1[Check CPU S-Spec] <- SIV32L - System Information Viewer V5.81 Beta-07 RED::ray
2
3SIV32L - Checkout of S-Spec on \\RED - Windows 10 x64 Enterprise  V10.00  Build 19045  22H2
4
5CPUID  Processor              S-Spec    Expected  Actual  CPUID  Reason  Description
6
70650   Covington-300 [A0]     SL27Z                                      Unknown - issue
8?      Coppermine-600 [cD0]   SL5BR                                      Unknown - checked
9?      Coppermine-650 [cD0]   SL5BU                                      Unknown - checked
10?      Coppermine-666 [cD0]   SL5B6                                      Unknown - issue
11?      Coppermine-800 []      SL65C                                      Unknown - issue
12068A   Coppermine-850 [cD0]   SL49G(2)                                   Unknown - issue
13068A   Coppermine-866 [cD0]   SL49H(2)                                   Unknown - issue
14?      Coppermine-866 []      SL5HK                                      Unknown - issue
15?      Coppermine-933 [cD0]   SL5B4                                      Unknown - checked
16?      Coppermine-933 []      SL5HL                                      Unknown - issue
17?      Coppermine-500 [cA0]   SL3US                                      Unknown - issue
18?      Coppermine-666 [cC0]   SL4G6                                      Unknown -
190681   Coppermine-700 [cA2]   SL3SB(2)                                   Unknown - issue
200681   Coppermine-800 [cA2]   SL4G7(2)                                   Unknown - issue
21?      Coppermine-1000 [cD0]  SL5L7                                      Unknown - issue
22?      Coppermine-866 [cD0]   SL5HG                                      Unknown - issue
23?      Coppermine-933 [cD0]   SL5HH                                      Unknown - issue
240633   Klamath-266 [C0]       SL2PV                                      Unknown - issue
250634   Klamath-266 [C1]       SL2QD                                      Unknown - issue
26?      Tualatin-1333 []       SL6HS                                      Unknown - issue
27?      Tualatin-1400 []       SL6HR                                      Unknown - issue
2806B4   Tualatin-1133 [tB1]    SL6JM                                      Unknown -
2906B4   Tualatin-1266 [tB1]    SL6JN                                      Unknown -
3006B4   Tualatin-1400 [tB1]    SL6JP                                      Unknown -
31?      Tualatin-1000 [tA1]    SL5PS                                      Unknown - issue
3206B1   Tualatin-800 [tA1]     SL66D                                      Pentium III 256K - Unknown
3306B4   Tualatin-800 [tB1]     SL6HC                                      Pentium III-S 512K - Unknown
3406B4   Tualatin-933 [tB1]     SL69K                                      Pentium III-S 512K - Unknown
3506B4   Tualatin-1000 [tB1]    SL6QU                                      Pentium III-S 512K - Unknown
36
37Checked 326 entries from D:\SIV\SSpec.tsv in 0.005 seconds, found 0 issues, 25 + 104 missing (100 Xeons) and 120 skipped
38
39[  OK ]  [ Copy]   [i486 S-Spec][Pentium Spec][Skt 8 S-Spec][Slot S-Spec][CuMine Spec][Chk S-Spec][CPU S-Spec]

Main menu