4 Aug
2006
4 Aug
'06
11:11 p.m.
Chuck Guzis wrote:
On 8/3/2006 at 12:11 PM Roy J. Tellason wrote:
The ACPI "implementation" on my machine is either physically damaged, or
so fucking broken that there is not a single OS in existence that can
use it.
Good job HP, for making my system break with just about every bootable
CD unless I bend over ass-backards with a 5-mile long bootloader command
which breaks what little that does run.
By the way, if anyone's intrested, the system is a Pavilion a414x.
--
The real problem with C++ for kernel modules is: the language just sucks.
-- Linus Torvalds
A floppy driver? Why? This isn't making
sense to me at the moment (gotta
go get that second cup of coffee I guess...)
'Cause the OS says you have to. There was a huge grumble of displeasure in
the NT community after MS assured developers that NT 4.0 kernel-mode
drivers would work just fine with 2K. And they did--until RC1, when, just
a month or two before official launch, you discovered that you had to
implement the complete litany of power management services or you'd get a
BSOD.
I haven't even looked at Vista requirements yet--and probably won't until
Vista's released because MS is making the same claim "You can use XP
drivers on Vista". Sometimes, it seems to me that OS software at Microsoft
is created as a sort of involuntary spasm.
But as to why software is buggy and complex, consider ACPI. One of the
densest, most incomprehensible, violated-in-practice "standards" that
exists on the face of the planet. Or, consider the way the already-complex
USB standard has "bloomed" since 1.0.
Cheers,
Chuck