Linked by Adam S on Tue 14th Oct 2008 12:30 UTC
Windows According to the official Windows Vista Blog, Microsoft has decided that, in order to keep things simple, the OS code-named "Windows 7" will officially be called "Windows 7." Sayeth the poster: "since we began development of the next version of the Windows client operating system we have been referring to it by a codename, "Windows 7." But now is a good time to announce that we've decided to officially call the next version of Windows, "Windows 7."" Of course, this introduces a major issue - if the version number of Windows 7 is, in fact, 6.1 or 6.2, as many expect, how can you call it Windows 7? And if the kernel version is updated to version 7, how many apps and drivers might fail due to poor version checking? I'm sure the upcoming PDC and WinHEC events will shed some light on this.
Thread beginning with comment 333795
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Drivers
by lemur2 on Wed 15th Oct 2008 07:18 UTC in reply to "RE[6]: Drivers"
lemur2
Member since:
2007-02-17

Your implied claim that Intel sells alpha quality hardware to the public makes you seem pretty desperate to come up with a defense


Its alpha quality hardware if it doesn't have a working driver on release.

A Windows-only driver is not acceptable. Motherboards for IBM-PCs and derivatives are not designed to run only OS from one vendor. Linux, Mac OSX and Windows all run on x86 and x86_64 architecture machines.

Even with Windows ... if you get new hardware, newer than the OS with which you try to run it ... then problems may well be evident.

This is not a valid argument to put forward against Linux. If there is a working Windows version of drivers, and not a working Linux version (even though it should be more or less only a slight adjustment to the code and a recompile to provide that) ... then that is an argument against that Intel motherboard, and not against Linux at all.

Windows Vista driver problems are, after all, always blamed on the hardware manufacturer, and never on Microsoft.

What is good for the goose is good for the gander.

Reply Parent Score: 0