>>This one was especially wrong
Michal, I am sorry, but your posting is especially wrong.
You said data and code. There is no much difference between the two. m-w.com
defines code as “a set of instructions for a computer”, data as “information
in numerical form that can be digitally transmitted or processed”. According
to these definitions, code is a superset of data. It’s the data which tells
the computer what to do. A TV signal is a set of instructions for a TV set
to turn its pixels on and off, so it’s code. The TV firmware is OS.
–
“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
All analogies are misleading, less or more. This one was especially wrong
and I’m curious how long thread it’ll start. Now we have 2 replies, not
counting mine 
Why wrong? Because bad show is just data whereas driver is code. Try to load
bad firmware to your TV.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
> ----------
> From:
> xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> on behalf of cristalink[SMTP:xxxxx@cristalink.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Tuesday, March 27, 2007 12:36 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Re:Driver Programming Fundamentals/Philosophy, was:
> Re: Calling NdisRequest() from ProtoclBi
>
>
> “Martin O’Brien” wrote in message
> news:xxxxx@ntdev…
> pact.
> > Microsoft contents that most system crashes are 3rd party drivers, and
> > all
> > evidence is this is true.
>
>
> I am glad my TV does not crash every time they load a bad show into it.
> That’s what I call a good design.
>
> —
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>