This may seem like a dumb reason, but apparently Microsoft skipped Windows 9 for fear of sloppy programmers.<\/p>\n
You see, if a program is designed to look for, say, Windows 95 or Windows 98, then it may simply search for the text “Windows 9” and stop there. If so, the program could misidentify Windows 9 as Windows 95 or Windows 98. At least that’s the reason postulated by the article, link below.<\/p>\n
I’m not buying it.<\/p>\n
My reason is that programmers use the internal Windows version number, or vernum<\/em>, to determine which Windows version is being used. Now some just might use the Windows name, but that’s not the coding practices I’m familiar with. There is historical evidence for this reasoning as well.<\/p>\n When DOS 4.0 came out, it was terrible. Many programs wouldn’t run, so the programmers began coding a DOS version test. The problem was that DOS 4.1 was okay, but the version tested only for the “4” and not any “.1” part. Also, numerous developers checked for only a single version of DOS or perhaps only the current version and any earlier versions. This version-checking nonsense drove people nuts as programs wouldn’t run or would refuse to run, despite the DOS version being okay.<\/p>\n To counter the version correction madness, Microsoft introduced a new command for DOS 5, Regardless of the reason, the next release of Windows will be known as version 10, not 9.<\/p>\nSETVER<\/code>. It would fool a given program into accepting the current DOS version. I wrote about this command years ago in various books. Anyway, if Microsoft were serious about the “Windows 9” issue, I would think it could devise a similar solution.<\/p>\n