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."
And you thought saying "Windoze" was a stale joke...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
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.
When will they learn that Microsoft has a very bad Beta Testing Routine.
First they have people pay them to be Beta Testers (for the privilege of being able to use the OS before the general public, and being those jerks who put 3 years of MS Vista experience on their resume). This doesn't attract people who want to thoroughly test the product, this only attracts people who think it is still the 1990s and wants to inflate their resume. So if they did report any bugs or problems it was probably for more minor things or the most major things. Sleep Problems are kinda in the middle annoying but not enough to put a bug report on.
Second poor response from my when bug testers do report a bug. Either they state that it isn't important or the conditions to get it are to off. In contrast I remember putting a bug in for Mozilla years back for an obscure problem on sizing the app across multiple displays of different resolutions. They weren't able to fix it quickly but they kept track of it until it was fixed.
Third Beta Testing is not used as much for Bug Testing but for product evaluation. It is used to see if the product is liked by the general population not as a method of fixing problems. This creates the problem 2 ways because Microsoft Beta Testers are of the following.
1. Love MS so much that they like everything that it does no matter how crappy it is, or make excuses for it problems (Don't get me wrong there are these type of people for every OS)
2. Wants to keep their Resume up to spec to keep in demand of stupid employers so they can have 3 years of Vista Experience. They don't want to report bugs or difficult to use problems because it gives them the advantage over people who just started using production Vista.
3. College Students/Professors mostly because they have extra time during the day to research these things. This group is most likely to report problems and give feedback. But that is only one segment of of the user base. And most college students and professors don't use the sleep options as much because they are on Campus which pays their electricity bills.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I've never been in a car accident and neither have any of my friends as far as I know, but I still don't doubt their existence. Requiring seat belts is pure FUD.
It's a useful abbreviation for x86-64. Get over it.
It's not exactly rocket surgery.
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
Bad analogy. A better one would be a comparison to car recalls. There are two pending for mine but I haven't had the problem (they are minor ones, nothing saftey related)so I keep putting it off. That doesn't mean the design problem doesn't exist; just that it hasn't affected me.
It seems you can enable msahci.sys after you've installed Vista: http://support.microsoft.com/kb/922976
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.
I'm not even considering jumping ship to Vista until the first SP is out (XP works beautifully for me).
Exactly the same. Especially since IE7 is more or less the same for me as a webdev, I can test all of my stuff on XP.
And we gotta realize: early adotpers always get stuffed with higher prices and lower quality. It's just the way things are, even if the product is developed under most stringent quality requirements, a bunch of undetected defects will be known soon after a wide launch.
The only thing that bothers me here is that on many consumer offers, companies FORCE you to get OEM Vista with a new PC. This early after launch, and with so many known flaws, how could you possibly require your customers to buy Vista PC when XP is much better right now?!
Do you have such experiences yourself? How easy it is to get a "downgrade" and in which hardware vendors it's easiest to do so?
... and they want their PNP problems back
Why UNIX?
ie - create the new DRM free Vista - they could call it the "Vista PUDRMFE" - Vista Penultimate Digital Rights Management Free Edition
Of course, they'll probably claim they can't take out the DRM because it's a crucial part of the operating system.
Hmmm - wonder how ReactOS is doing lately....
Who is general failure, and why is he reading my hard drive?
The implication is that it's a far more widespread problem than it is.
I don't know why anyone would think a problem would be common in a monoculture OS, do you?
You're right about it not being widespread. Vista's not selling. How's that for FUD?
There's a massive conspiracy to not purchase Vista! It's kind of like the one I launched against SCO, the infamous Distributed Lack of Purchasing (DLoP) attack. It's all the FUDster's fault. It has nothing to do with the thing taking six years to get here and sucking on arrival. You know, people having done just fine without it for the better part of a decade thinking they don't need a DRM downgrade. No, it's just the wingnuts keeping the man down.
Friends don't help friends install M$ junk.
But what about Windows' narcolopsy problems? What will fix those?
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
Well, this situation sounds ripe for lampooning in a new one of Apple's "Mac & PC" ads:
Mac and PC in twin beds, an alarm goes off. Mac wakes up but PC was sitting up in bed twitching nervously.
"Good morning--"
"AH!"
"I'm a... Mac."
"And I'm a p-p-PC."
"Hey, PC, haven't you been sleeping?"
"No! No, I, uh, I-I can't sleep."
"Really, do you need something?"
"No, it's not that. I-I mustn't go to sleep because I'm afraid I won't wake up. There have been reports, you know, that since the release of Vista, PCs have had problems with not waking up from sleep."
"Gee, that's too bad. Me, I have no problems waking up from sleep. I mean, within two seconds, I'm up and fully alert. That isn't true for you?"
"..."
"Uh, PC? PC, hello? Hey, PC, wake up!"
"..."
"Oh my."
Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
The sleep problems that plague Macbooks take the cake. When you shut the lid, it's a crapshoot whether or not it will actually shut down at all. And you have to wait about a minute to find out, because it spends that long dumping RAM to disk for some twisted reason (I know the reason, so no flames. It's just that it's a lame reason.) I don't know how many times I've shut the lid and stuffed it in my pack, only to find that the damn thing has been running for an hour full tilt in a closed space. It's so hot it can't be touched without pain when this happens.
This is just about the lamest thing about Macs. And it's been this way a long time. I finally had to disable the safe sleep functionality, which means you can't swap batteries w/o losing state. And they don't make it easy to do this. A small price to pay for not frying your computer, though. Does Vista do anything this lame? Probably not.