Are you actually trying to assert that your marketing dwebes would
let you put “Caution: don’t use this product if you have USB printers,
or any other unusual other devices connected to your PC” on the outside of the box?
Did the infamous “video card that locked the bus” come with such a warning?
Plus, if you violate the rules, how would you be able to predict
exactly what the user will sacrifice?
You could make a similar argument in favor of dumping sewage into
a stream. Since it flows downstream, your town doesn’t have to
deal with it, but the someother town will (i.e., poor printer manufacturer (and also the OS vendor,
but they won’t get much sympathy) has to handle support calls and
frustrated customers because of you).
-DH
PS. On the other hand, if you sell a turnkey system, and you handle all
of the support calls, etc., then there is no reason why you shouldn’t
do whatever it is that you please.
----- Original Message -----
From: “Everhart, Glenn (FUSA)”
To: “NT Developers Interest List”
Sent: Monday, August 06, 2001 4:16 PM
Subject: [ntdev] Re: AW: RE: Mapping scattered pages into process addr ess space
> Would it not make more sense to just document that a driver uses more high
> IRQ time than standard, more mapping registers than standard, etc. etc.,
> but allow such drivers to be loaded by a user after the sacrifice of a goat
> or something 
with the understanding that such drivers may disable
> other things in odd ways?
>
> Forcing driver writers to use a global standard would in practice mean that
> some unusual cases cannot be handled. If I want my fishfinder to run a
> little
> faster, perhaps I don’t care if some USB printer will fail completely. As
> long
> as I am told about a driver that is anti-social wrt other drivers, seems
> like a choice I as a customer should be able to have.
>
>
> -----Original Message-----
> From: Peter Viscarola [mailto:xxxxx@osr.com]
> Sent: Monday, August 06, 2001 3:28 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: AW: RE: Mapping scattered pages into process addr
> ess space
>
>
> “Dan Partelly” wrote in message news:xxxxx@ntdev…
> >
> > What is interesting is things I heard about Win XP that it will “block”
> > device drivers which causes more than “X” OS crashes , and also I heard
> > there is
> > a list with already “banned” device drivers.
> >
>
> As far as I know, XP has no facility to block a driver that crashes the
> system more than x times… I haven’t seen any code that does that. That
> doesn’t mean it doesn’t exist, but this is the first I’ve heard of it.
>
> As far as the list of “banned” device drivers, there’s a “bad” (not banned)
> “drivers list” that’s put together for every upgrade scenario. This is
> nothing more than the list of drivers that are known, by experience, not to
> work after an upgrade of the system (from Win2K to XP, for example). During
> upgrade of XP, the installation procedure warns you if you have such a
> driver, and warns you of the driver being disabled after installation.
>
> Peter
> OSR
>
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@FirstUSA.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law.
If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the
information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in
error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy
format. Thank you
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com