Slashdot Mirror
Prescription Meds For Vista Sleep Disorder
Arnold O'Connor writes "NeoSmart Technologies has compiled a list of hotfixes and patches provided by Microsoft for Windows Vista that address a large number of issues related to waking/resuming a Vista PC (both x86 and x64) from sleep or hibernation. Sleep-related disorders have plagued Vista since its release, though they were not present in earlier betas. Most of these fixes are due to be included in Windows Vista SP1 — codenamed Fiji."
I'd be interested to know how widespread these sleeping disorders are.
... although I have had hypochondriac computers in the past ;)
Our next generation of software is being tested under Vista and we have a number of dedicated test machines and dual boot development machines of different vintages. None of them have any problems at all with suspend or hibernate.
Just because there is a cure it doesn't mean that the problem affects everybody
--I thought I was wrong once, but I was mistaken.
Maybe it's just me, but I'd think that I didn't do enough testing on a product that already has a codename for it's SP1 within a few months of its release.
Not all conservatives are stupid,
but it is true that most stupid people are conservative.
- Hume
How is it FUD if Microsoft is issuing patches for it?
The implication is that it's a far more widespread problem than it is.
I'm not doubting the existence of a problem, I'm doubting its prevalence.
Deep sleep/hibernate problems? Oh wow I didn't see this coming except for the RC1 release I tried and reviewed months ago. http://it.slashdot.org/comments.pl?sid=209542&cid= 17088628
What's odd is that none of those patches or things mentioned going wrong is what I was dealing with. I was getting the click of death from my hard drives until I rebooted the computer.
I guess I can see this as very unfinished hardware drivers but for something as serious as this, Vista should have never been released in this pitiful state.
For once I'm not so sure we should blame Microsoft for all these sleep related problems. I would say hardware manufacturers is just as much to blame. They test their ACPI stuff and make sure it works in the current version of windows, and not that it follows the standard.
When Microsoft creates a new version of windows they most likely develop it to follow the ACPI standard. By doing so, the functionality may break on non compliant boxes, and Microsoft will have to go back to add quirks to make it work.
Being the dominant OS vender, Microsoft at usually manage to get full specs to the failing devices, and have a fair chance of compensate for the errors in the hardware and BIOS.
Developers of other less common OSes, such as Linux may not be that lucky. So I really wish Microsoft hadn't bothered to fix this, unless of course they really are the ones that are responsible for this screw up, and left it to the hardware vendors. That way it would be easier for all OS vendors, including Microsoft, in the long run.
God is REAL! Unless explicitly declared INTEGER