Itanium, the first IA-64 CPU, was supposed to be released around 1998. Since 1997 or so, it seems to have been clear to Intel that the x86 line of CPUs (retroactively named “IA-32”) was to be eventually replaced by IA-64. On every modern x86 processor, the CPUID instruction returns, among other things, the family code of the CPU. Everything went right.Īt Intel, everything went wrong. It was not until Windows XP (version 5.10) that consumers actually switched to the NT line, but the numbering was still consistent. ![]() After all, Windows ME had the user interface and Win32 API version close to that of Windows 2000, so it was somewhere between 98 (4.10) and 2000 (5.0). ![]() With Windows, Microsoft’s versioning scheme was quite adventurous: After Windows 95 (internal version number 4.0) and Windows 98 (version 4.10), Microsoft chose the version number 4.90 for Windows ME, the last operating system of the Win9X line, which was supposed to be replaced by Windows NT version 5.0 a.k.a Windows 2000. Assigning internal version/family/model IDs to products is a non-trivial task, especially if there are several different families/architectures on your roadmap, and if the marketing names and target markets have no real correlation to the internal architecture.
0 Comments
Leave a Reply. |