as explain before. Windows 7 has some of Vista problems fix but a large part of Vista problems was out of Microsoft's hands. Namely driver and software support.
True, and what should be pointed out is that this failure was by Plan, not by Accident.
MS's Business Plan has been is to be "hands off" because they didn't want to pay for it. They offloaded the cost of writing the drivers to the 3rd party hardware manufactuers, which effectively was MS once again leveraging their monopoly for profit, because no hardware vendor can "Afford" to ignore the 800lb gorilla, hence they had to pay out-of-pocket to maintain compatibility...and also more money that stays in MS's pocket.
A lot of companies did not update their drivers to work with their hardware and others just refused to update their software or people got hit with the legacy software that had not been updated for years.
Yes, but to be fair to the ones actually paying for the work, because of MS's repeated stumbling in OS creation (eg, Longhorn), these same 3rd party vendors got tired of wasting their money. So they simply chose to wait on MS for Vista to become real, so as to minimize their in-house financial losses from yet another MS-created stillbirth. This is particularly the case for existing (legacy) hardware since there was no profit to be made by the hardware vendor by writing a new Vista driver.
This is a classic example of where the motivational self-interests would be that a delay should only cause a few months of lost sales disadvantage at the individual level, but when everyone took the same course of action, it resulted in a crash -n- burn for the entire Vista release.
This is easily forseen as a consequence and it should be clearly identified as the fault of MS's business plan. When MS chose to dump the work (& expense) on the hardware vendors, all at the vendors' expense, MS effectively abdicated Vista's delivery schedule and quality to these unpaid vendors.
In summary, MS failed with Vista because MS refused to pay for that which was product- and milestone-critical.
Moving forward to Win7...
One should take notice that by not changing the APIs, MS won't have this same problem in this rollout ... but more importantly, MS hasn't fixed this flaw in their business plan: they've merely side-stepped the problem for the moment.
shh....this is good news for Apple and other MS OS competitors.
(change of gears)
It sounds like it's designed to act as a repeater. So you stick a computer on the outer fringe of a wireless network's coverage area and it'll extend the coverage: Say ABC is the wireless router connected to the internet and the rest are computers, you could have something like this:
ABC----------DEF----------GHI----------JKL----------MNO
So the 2nd computer is connected to ABC and sharing out the connection on DEF, the 3rd computer is connected to DEF and sharing out on GHI, etc. And at the end, a computer can connect to the wireless network MNO and get online even though it's far out of range of ABC, the original wireless router.
Its an interesting idea...and one that is fraught with gotchas.
Taking the above example:
A) the laptop user DEF will get saddled with poor WiFi performance, because in addition to his own bandwidth consumption, the bandwidth being used by GHI, JKL and MNO are all being passed through him too.
B) the laptop user DEF finishes his Latte at the fringe of the coffee shop's WIFI coverage, shuts down his laptop and goes back to work ... the rest of the tag-along 'hitchhikers' go from a decent relay signal to zero signal and their sessions crash and burn.
C) if I'm paying for bandwidth and have this turned on, did I not just invite freeloaders to hitchhike on my connection ... and for which I'm footing the bill? When one of them does something illegal, am I liable?
D) suppose that the laptop user GHI has a WiFi eavesdropper (either malware, or he's not a white hat). Would this not mean that all of the traffic that he's helping "pass through" from/to JKL and MNO has now had its security compromised?
Now, why you would do this with Windows 7 is beyond me....wireless routers that are capable of extending networks like this can be had for as little as $50 and are small and compact and purpose built for this sort of thing. Using computers seems like major overkill.
IMO, it is obvious that this feature is going to be used as a marketing hype advertisement, to illustrate how Windows is "better" than other systems. The commercial will be to show a Mac getting zero bars and the PC getting a solid connection...
Granted, it could be a reasonably decent idea in a trusting, benevolent IT setting (particularly if there's not one node at each DEF but dozens...preventing single point of failure in a network web), but the unfortunate reality is that this sort of computing environment hasn't existed for well over a decade, plus its creation of coverage relies on statistics, both for the availability of users as well as the ubiquity of that particular version of Windows. Even if it technically works, it will take time for broad adoption to pragmatically make it reliably available.
-hh