Nobody is a born Device driver writer

>> To coin a phrase:

>“There will be poor driver writers always, pathetically struggling” to
>their code. Why not just make it so that the consequence of their
>doesn’t cause the REST of us to look bad.

Nah Peter…Nobody is born writing drivers in her mothers womb everybody
learns it here right on this
place but that ofcourse is a slow and gradual process.
But the onus lies on their seniors like you to share their immense
knowledge with them
and help them grow up so that above mentioned stupidity can be stopped.

Aashish Kaushik
TEL : 0120-4777881(Extn. 2390)

If there is righteosuness in the heart,  
there is beauty in character and if there  
is beauty in character there will be harmony  
in the home.  
 ---- Sai Baba  

“Peter Viscarola”
To: “NT Developers Interest List”
Sent by:
xxxxx@lis cc: Subject: [ntdev] Re: Philosophical Rant [was
Re: Writing Drivers in Java]

29-04-2002 12:13 PM
Please respond to “NT
Developers Interest

“Gregory G. Dyess” wrote in message news:xxxxx@ntdev…
> VMS, despite its reputation as a CPU and memory hog, ran circles around
> in terms of responsiveness and it NEVER crashed on the exact same
> [snip]
> Everyone should start buying only hardware that has successfully passed
> MS quality tests.

Let’s not wax too nostalgic about VMS, OK? I mean, RSX-11M crashed less
than VMS. Maybe we should go back to using RSX-11M Plus?

VMS is a simpler operating system than NT. It was pretty cool in the
when it was designed but, like RSX before it, it’s features do not allow it
to compete with NT.

In addition, VMS supports a tiny subset of peripheral devices compared to
NT. Further, Compaq nee Digital writes practically all the drivers.

And, of course, the world has changed very substantially from the days when
vendors could command huge sums for proprietary workstations. While much
that money went to profit, and was subsequently invested in expensive suits
for the CEO, lots of that money want to “quality assurance.” The
in terms of money and time for qualifying a driver for NT the way we
qualified drivers for VMS would literally bankrupt most IHVs and make them
miss their market window. For example, ten years ago, it cost a couple of
hundred thousand dollars a year (1992 dollars) just to do the protocol
conformance testing for a DECnet VMS release. A four month testing period
was not at all unusual. This doesn’t include unit test, QA, and the rest.
And this was all using Digital-developed hardware.

In terms of the “MS quality tests” (I assume you mean tests for the Windows
Logo, right?)… do you really think they’re stringent enough to ensure
drivers don’t crash the system? I have personally loaded Logo’ed drivers
the checked build of the system, and seen such drivers fail to even get
through the boot processes without assert-ing.

Nah. Times have changed. 80% correct drivers are all that we can hope
The O/S has to be resilient to Stupid Driver Writers. To coin a phrase:
“There will be poor driver writers always, pathetically struggling” to ship
their code. Why not just make it so that the consequence of their
doesn’t cause the REST of us to look bad.


You are currently subscribed to ntdev as:
To unsubscribe send a blank email to %%email.unsub%%