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 333773
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Drivers
by bornagainenguin on Wed 15th Oct 2008 04:01 UTC in reply to "RE[5]: Drivers"
bornagainenguin
Member since:
2005-08-07

lemur2 said...

If you are going to bolt bleeding edge beta or even alpha quality hardware into your machine, you may well have to put up with very recent and not-well-tested versions of software.

That's life. Deal with it.


We're not talking about hardware that is bleeding edge, just the realities behind having to develop drivers independently and usually without the support of manufacturers.

I don't think its fair to call retail hardware bleeding edge or alpha unless there are issues with the actual hardware independent of the drivers used in whichever OS.

So do I understand the realities of the situation, I just think it sucks and people shouldn't be so hard on those who find themselves stuck due to the unavailability of tested and stable drivers.

Its actually pretty cool that as many people put up with the current situation as do...

--bornagainpenguin

Reply Parent Score: 2