Vista an Uneasy Sleeper

Emmy King writes "

One thing we just can't wrap our mind about is the terrible, broken, and completely pitiful support for waking Vista up from a Deep Sleep or hibernation.

Anytime you attempt to wake Vista up from Hibernation or "Deep Sleep" (S3-induced sleep mode), it dies. It's either a BSOD, or a driver error, or a broken network, no DWM, lack of sound... the list goes on, and on. So much for an operating system to "power" the future! (No pun intended!) That's with properly-signed drivers and no buggy software on multiple PCs..."

Comments

S3 is not hibernate/deep sleep.

[Junta]

S3 is plain old suspend/sleep. hibernate/deep sleep implies suspend to disk and total power down, and is S4. And the word S3-induced makes no sense, S3 is a state entered into, not an active thing.

Blame ACPI, not Vista

[Anonymous Coward]

I'm vociferously anti-MS; but in this case, I believe they deserve a small pardon. Go read the ACPI specifications sometime. You will cry and beg for mercy. ACPI is horrible. Considering the small number of requirements the real world has for such an interface, the specification is vast beyond imagining. Linux has also had long standing problems producing a proper ACPI layer, for this very reason: ACPI is a pig.

Now it is worth noting that MS themselves contributed to the development of this specification. The cynical side of me believes that confounding the competition by way of impenetrable specifications is simply Microsoft's modis operandi. Look at Microsoft's OpenXML specification for example: while in theory it meets the European requirement for documenting file formats and protocols, in practice it's ~6,000 pages will certainly confound all but the most determined attempts at interoperability. But here's the rub: Microsoft has to eat their own dog food, and they are suffering the consequences. Microsoft's operating system and applications are becoming so piggish that even Microsoft can't manage them.