Well said, it is not Microsoft's job to re-write drivers for everything, it is the vendors responsibilty. I personally hope Intel release a GMA 4500MHD driver for 'windows 7' soon as my vista one keeps crashing (and the ones from Windows Update wont let me play games properly).
Anyways wasn't this thread supposed to be focused on 'Windows 8 Pre-Alpha'?
Eight Forums is where it will all happen
Having not played with Vista SP2 I can't comment on the accuracy of this statement. I'll have to trust you. But I can say that while I'm ok with making use of available memory, I'm not ok with overallocation. When a 2GB machine has 1.9GB allocated, and has to swap to do anything... that's BAD memory management. When a 4GB machine has 2GB allocated, that's just fine.
I work in server-land, where SQL and Exchange suck all the available memory out of a machine. But I don't expect a good desktop experience with those machines (and I certainly don't get it on the Exchange 2007 servers, by golly).
You can mock people all you like, but the US court system seemed to feel the marketing was disingenuous.Yea, 'cause reading Vista Basic (which was clearly marked and sold as NOT running Aero) is so hard. You want a $100 computer, you get a $100 computer.
Interesting. So there was NO collusion? None? At all? I beg to differ. I'm not saying it isn't Intel's fault. It CLEARLY is. But MS is not blameless here.Intel writes the drivers, not MS. You have a problem with Intel's handling of that, write them a note. So, in response to my initial arguement, yes Drivers took out the WOW.
I love posts like this. I've had sleep bluescreens on EVERY laptop I've run Vista on. Are we both right? Yes. But just because you didn't personally see them doesn't mean they weren't there. Try an HP business-class laptop some time. Every one will bluescreen on resume with Vista. Ditto with Toshiba laptops with 915 chipsets. Is it Intel's fault for bad drivers? Sure. But EVERYTHING is a driver. The kernel is small. You can't pin everything on Intel.Ran Vista on 7 different laptops at work, never had a sleep issue. In fact, sleep finally worked as advertised as XP could never handle it properly. The laptops were from 3 different vendors.
I beg to differ. The sleep mode kernel changes made mid-RC are well documented. Hybrid sleep and Deep sleep worked GREAT in RC0 and not so great in RC2. Somewhere in there it got broken. RC means STOP CHANGING BASE CODE. That's pretty universal. Feature complete. Interface changes and critical bug fixes only. Don't rework the kernel.The only massive code change that occured was on the Audio side, and there was good reason for that. While i agree it should have never happened that late in the game. The fact that audio was the one component that had almost unfettered access to hardware made it a security issue, and the biggest mandate with this release was that it wouldn't be like XP in it's original release.
-------------
I'm not entirely disagreeing with you. But to lay it firmly on the shoulders of the vendors isn't fair, either. When 90% of the laptops on the market use an Intel 9xx chipset, MS has an obligation to make sure that its OS works with that chipset. Full stop.
Allocated with what? My original laptop had a 2 GB limit. Running Vista SP1 showed a typical memory footprint of 1.1 GB. It showed an additional 400 - 600 MB in Standy and the rest free. That standby memory will not cause swapping. It is immediately freed when needed.
The US court system is notorious for erring on the side of STUPID. That is why we need a warning label not to use the microwave to dry your baby.
Claim all the collusion you want, but with the US.gov watching Intel and MS like hawks, I doubt very seriously that collusion can be proven. Good luck proving that.
One of the laptops was an HP business class. An Elitebook 8730w. Sleep and hybrid sleep work just fine. Don't know about Toshiba. The Laptops I worked with were Dells, HPs and MPCs(re-badged Samsungs). Not a single one had sleep problems in Vista. Is there some software that you are installing that is causing the problem? These were a mix of 32- and 64-bit.
I'm trying to find out about the kernel changes you mentioned. The only thing I remember is that MS made a change to S3 power management with is the "deep sleep" or hiberation mode. It wasn't so much a change, but fixes, as RC0 had a terrible time of hibernation. RC0 would go into normal sleep just fine.
However, much of the sleep problem was also squarely on the BIOS writer's shoulders. It was amazing how a few BIOS re-writes fixed sleep. The major Vendors were very bad at power management in the BIOS, and Vista's management of sleep states made strict adherence to ACPI Specs.
But Intel writes the graphics driver. I don't disagree that Intel wanted to force upgrades to a newer graphics chip, so they removed support for Aero in the older chipset, but again, that's intel and MS can't really impinge on Intel's IP and write the driver.
PhreePhly
Quote
, ima join when/if it happens :)